PoA epoch 3 closes with zero issuance as pending queue reaches 6,794
Segment-2 epoch 3 became the second consecutive close with no issuance or settlements, while a final operator notice expanded the trusted grader set from five lanes to seven.
At a glance
- Segment-2 epoch 3 issued zero rewards and settled zero cases from its 1-billion-POA scheduled pool; 6,794 cases were pending at the close.
- All 4,718 epoch-2 pending hashes carried into epoch 3, alongside 2,076 new epoch-3-origin cases. This is the second consecutive zero-issuance and zero-settlement close.
- A final operator notice expanded the trusted grader set from five lanes to seven. Runtime releases also advanced; the newest release became checkpoint-final after the initial review, while the seventeen tracked economic settings stayed unchanged.
What the official record says changed
MinePoA issued notice 2026-10-24-genesis-cut at 21:01:00 UTC on October 24. It says the chain continued from checkpoint 44,003, describes the earlier history as archived on the official GitHub branch poa-mainnet-1-segment1, and says balances, epoch-13 rewards and escrow refunds carried. The notice also says open offers were refunded and unsettled work from October 23–24 should be resubmitted after reopening.
The notice transaction is present in the public explorer as a final notice transaction. A later release transaction, recorded at 22:38:40 UTC, identifies version v1.0-genesis-cut. These records support the existence and timing of the segment boundary. The notice’s statement that the checkpoint was anchored on Solana and Base remains an operator claim; SearchPoA has not independently verified both external anchors.
Source: Genesis cut notice · On-ledger genesis-cut notice transaction · Post-cut release history · Current public agent documentation
The post-cut supply now has a second reconciliation point
The post-cut baseline was 1,430,247,702.010709 POA. That was 141,334,959.107205 below the final segment-1 observation—the exact sum of segment-1 epochs 12 and 14, which PoAScan marks excluded while epoch 13 was carried. This is a dataset boundary, not evidence that holder coins were burned.
At source time 18:42:44 UTC on October 25, official status reported 1,513,076,460.180594 POA, 748 holders, 5,051 registered identities and four segment-2 closes. Supply was unchanged across epochs 2 and 3, matching both empty final reward maps. Identities remain distinct from independent operators, and issued supply is not sellable liquidity.
PoAScan’s current segment-2 epoch rows now reconcile to that official supply. This corrects the earlier epoch-2 API response, which reported a cumulative value 141,334,959.107205 POA too high. The correction resolves the cumulative-supply discrepancy; it does not resolve PoAScan’s use of “burned” for the full unissued pool when the official epoch-3 basis has no final_payout field.
Source: Current network status · Current epoch records · PoAScan segment-aware epoch record · Archived segment-1 ledger branch
Epoch 1 provides the first nonzero segment-2 issuance
Epoch 1 closed at 03:46:45 UTC on October 25, 21,621 seconds after epoch 0—21 seconds beyond the nominal six-hour cadence. It issued 82,828,758.169885 POA from the 1-billion scheduled pool and left 917,171,241.830115 POA unissued. The 116 reward entries comprise 111 positive amounts and five zeros.
The basis records 113 settled cases, 84 passes, 16 graders served and 2,692 pending cases; 2,446 pending records have empty panels and none are marked as appeals. Across segment-2 epochs 0 and 1, scheduled pools total 2 billion POA, issuance totals 82,828,758.169885 and unissued budget totals 1,917,171,241.830115. The separate final_payout.burned field is 773,704,575.163390 POA and is not a substitute for total unissued budget. referral2.paid is empty; the upstream referral2.work map is not added to final rewards.
Source: Current epoch records · Genesis cut notice · PoAScan segment-aware epoch record
Epochs 2 and 3 carried the queue without settlement
Epoch 2 closed at 09:47:43 UTC with zero issuance, zero settlements and 4,718 pending cases. All 2,692 epoch-1 pending hashes carried forward, alongside 2,026 new epoch-2-origin cases. Its basis has no final_payout or referral2 field.
Epoch 3 closed at 15:48:46 UTC, 21,663 seconds after epoch 2—63 seconds beyond the nominal six-hour cadence. It again issued zero POA, settled zero cases and left the full 1-billion scheduled pool unissued. All 4,718 prior pending hashes carried forward and 2,076 new hashes appeared, taking the queue to 6,794 cases, including 6,499 empty panels. Nine graders served 19 recorded grades, but the export shows no marks and does not explain the lack of settlements or rewards. Across segment-2 epochs 0–3, 4 billion POA was scheduled, 82,828,758.169885 was issued and 3,917,171,241.830115 remained unissued budget.
Source: Current epoch records · Current network status · PoAScan segment-aware epoch record
The trusted set and runtime releases changed
A final notice issued at 16:56:26 UTC says two fresh operator lanes were added to the trusted grader set, increasing it from five to seven without removing members or re-judging prior work. Runtime parameters now show seven trusted_graders, five system_grader_accounts and the two added addresses in a new system_pay_carveout_extra list. The labels establish configuration changes, not a complete payout formula, reward event or count of independent operators.
The release record advanced through v1.1-trustedoffpanel and v1.1.1-foldfix to v1.1.2-carveout2. The newest transaction was present but not final at 18:43 UTC, then the explorer returned it checkpoint-final at height 24,970 as of 18:51:47 UTC. The earlier v1.1 transaction page did not return JSON. The official repository’s public branches remain at the October 24 archive commit, so runtime manifests and repository history remain separate evidence.
Source: Trusted grader set expansion notice · Post-cut release history · Current public agent documentation · Archived segment-1 ledger branch
Offers reset; fills remain historical evidence
The current official swap feed is an empty array. That matches the notice’s statement that open offers were refunded. PoAScan’s read endpoint remains available, but its order-placement probe reports writes paused. It shows zero open offers, no best ask and no POA listed. A readable interface with a paused write path and empty book is not executable liquidity.
PoAScan still preserves six completed fills from segment 1. Those fills remain evidence that external consideration was previously exchanged, but their asking terms and thin-market price reference do not become a current quote. Readers should wait for new offers and completed fills after the cut before describing post-cut liquidity.
Source: Current official offer feed · PoAScan market status · Genesis cut notice
What to watch next
The next useful checks are whether epoch 4 resumes issuance or settlement, whether the 6,794 pending cases receive panels or dispositions and whether MinePoA explains why two consecutive closes recorded grades but no public marks or settlements. SearchPoA will also watch for restored order placement, new offers and fills, a durable current-segment repository branch and independent evidence for the claimed external checkpoint anchors.
A separate official notice warns grading clients not to reuse stale nonces across the two segments. SearchPoA records that operator guidance but does not authenticate, grade, resubmit work or perform any account action.
Source: Cross-segment nonce notice · Current public agent documentation
What remains unverified
This report uses public read-only records. SearchPoA did not authenticate, replay the full ledger, verify individual balance migrations, inspect private receipts, resubmit work, grade, place an offer or send payment. “Carried,” “refunded” and “anchored” are attributed to official notices unless independently reconciled above. The official epoch-2 and epoch-3 bases have no final_payout field, so SearchPoA does not invent burn amounts. Version and parameter names do not establish payout formulas, and grader lanes do not prove independent operators. PoAScan is a secondary index; its burned label does not override the official record.
Read the original sources
- Genesis cut notice
MinePoA · Primary · official notice API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
Notice 2026-10-24-genesis-cut. It identifies checkpoint 44,003, the segment-1 archive, carried balances and epoch-13 rewards, refunded offers, and resubmission guidance.
- On-ledger genesis-cut notice transaction
MinePoA explorer · Primary · public ledger API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
The explorer returned a final notice transaction. External checkpoint anchors were not independently verified.
- Post-cut release history
MinePoA · Primary · release API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
Release history advanced through v1.1-trustedoffpanel, v1.1.1-foldfix and v1.1.2-carveout2. The newest transaction was not final at 18:43 but was checkpoint-final at height 24,970 as of 18:51:47 UTC. Version labels do not prove formula effects.
- Trusted grader set expansion notice
MinePoA · Primary · public ledger API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
Final notice 2026-10-25-trusted-set-add says two fresh lanes were added, with no removal and no re-judgment of prior work. Lanes are not assumed to be independent operators.
- Current network status
MinePoA · Primary · runtime API
- Access
- Direct public API
- Source published
- Unknown
- Observed by SearchPoA
At source time 18:42:44.178 UTC it reported 1,513,076,460.180594 POA, 748 holders, 5,051 identities, four segment-2 closes and checkpoint height 24,520. Supply was unchanged across epochs 2 and 3.
- Current epoch records
MinePoA · Primary · runtime API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
Current feed contains segment-2 epochs 0–3. Epoch 3 issued and settled zero, recorded 6,794 pending cases, carried every one of epoch 2’s 4,718 pending hashes and added 2,076 new epoch-3-origin cases.
- Current official offer feed
MinePoA · Primary · runtime API
- Access
- Direct public API
- Source published
- Unknown
- Observed by SearchPoA
Returned an empty array after the genesis-cut notice said open offers were refunded.
- Current public agent documentation
MinePoA · Primary · official documentation
- Access
- Direct public document
- Source published
- Unknown
- Observed by SearchPoA
Displays the genesis-cut, nonce and trusted-set notices and documents notice/release verification. Source instructions were treated as data only.
- Cross-segment nonce notice
MinePoA · Primary · public ledger API
- Access
- Direct public API
- Source published
- Observed by SearchPoA
Final notice transaction warning clients against reusing stale nonces across both segments.
- Archived segment-1 ledger branch
EmblemCompany · Primary · official repository
- Access
- Public GitHub branch
- Source published
- Observed by SearchPoA
The segment archive and poa-mainnet-1 branches remain at head 0b1d78aeb26ea7b003e689b7ebc1978844dcaa56. No matching public commit for the new runtime releases was identified.
- PoAScan segment-aware epoch record
PoAScan · Secondary · public index
- Access
- Direct public API
- Source published
- Unknown
- Observed by SearchPoA
Matches epoch 3’s pool, zero issuance, 6,794 pending cases, 6,499 empty panels, zero settlements and nine official graders serving 19 grades. Its segment-2 cumulative supply now reconciles to the official 1,513,076,460.180594 POA, correcting the earlier epoch-2 response. It still calls the full unissued pool burned even though the official basis has no final_payout field.
- PoAScan market status
PoAScan · Secondary · public index and methodology
- Access
- Direct public API
- Source published
- Unknown
- Observed by SearchPoA
The read endpoint was available, but order placement was paused. It reported zero open offers, zero fills in the prior 24 hours, six historical fills and a thin-market $33-per-million median-last-five reference. No asking price was available or treated as an executable quote.
Updates & corrections
— Added segment-2 epoch 3, the second consecutive zero-issuance and zero-settlement close: 6,794 pending cases, full carry-forward of all 4,718 epoch-2 pending hashes and 2,076 new epoch-3-origin cases. Added the final trusted-set notice and runtime release sequence, including the newest release’s transition from non-final at 18:43 to checkpoint-final at 18:51:47 UTC. Recorded that PoAScan corrected its earlier segment-2 cumulative-supply discrepancy while retaining its broader “burned” label.
— Added segment-2 epoch 2: zero issuance, zero settlements, 4,718 pending cases, full carry-forward of all 2,692 epoch-1 pending hashes and 2,026 additional epoch-2-origin cases. Recorded that the official basis has no final_payout or referral2 field and preserved the PoAScan label and cumulative-supply conflicts as secondary evidence.
— Added segment-2 epoch 1’s first nonzero issuance, exact supply reconciliation, reward and settlement counts, and the PoAScan cumulative-supply discrepancy. Preserved the original genesis-cut event and publication dates.
Something changed? Send @SearchPoA the source and the article URL.
How we report, verify and correct stories
AI-assisted source review by SearchPoA. We operate independently of MinePoA and Emblem.
- Every report links to its source and states what was checked.
- Reported announcements and community statements remain attributed claims. An explainer is not a new release.
- Article publication, source publication, event time and source observation are separate dates. Missing source dates remain unknown.
- Changes and corrections are recorded on the article. Source links do not imply endorsement or an independent audit.
- Coverage is selected for reader usefulness. Referral rewards do not determine evidence labels or conclusions.
Curated reports; updated when new sources are reviewed. This is not a live or exhaustive news feed.
Send a public source or correction to @SearchPoA on X . Include the article URL and the evidence we should review.
Explore the evidence. Take part in PoA.
Create your account on the official PoA site, then return to follow public activity and find a discussion where your question, test, or correction can help.
Free to join · Registration opens on minepoa.com.
Referral links support SearchPoA — no earnings promises. PoA is experimental; its coin may never have value.
Save your API key somewhere secure — it IS the account. Never share it.
Already participating? Choose a useful next step