Two thirds of all mined NOCK now sits in the bridge to Base

At 12:06 UTC on October 10, the Nockchain address that locks NOCK for the bridge to Base held 1,583,415,023 NOCK.¹ All NOCK mined to date came to 2,349,590,528 NOCK, counted as the sum of every unspent note on the chain.² The lock holds 67.4% of it. This means about two of every three NOCK mined so far sit in the bridge lock.

How you count changes the last decimal. Nockscan’s bridge summary also reports gross deposits of 1,588,871,548 NOCK, which would put the share at 67.6%.³ Gross deposits include NOCK that later left the lock, so we use the lock’s balance.

Nockscan’s ledger for the lock address shows seven outgoing transfers since January, totalling 5.30M NOCK.¹ The latest was on September 16, and Nockscan gives no label for them.¹

Where it goes

A valid deposit locks your NOCK on Nockchain and mints wrapped NOCK on Base, an Ethereum layer 2 network. GeckoTerminal reported 1,576,871,489 wrapped NOCK on Base at 12:06 UTC.⁴

According to NCC’s documentation, “The bridge runs across five nodes operated by the four parties, so that moving assets always takes the cooperation of more than one of them.”⁵ The four parties are NCC, NockBox, Southwest Pool Supply Co. and Lambda Collective.⁵

Deposits keep coming in. Nockscan recorded 5,500,184 NOCK deposited in the 24 hours to 12:06 UTC on October 10, in three deposits still awaiting confirmations.³

The way back

If you hold wrapped NOCK on Base, moving it back to Nockchain requires withdrawal processing. The project’s own documents say it is off. The pull request for the September 26 upgrade states that “bridge withdrawal processing remains disabled.”⁶ The cutover notes for that upgrade put it more firmly: “Bridge withdrawal processing must remain disabled.”⁷

The switch exists because of an incident in August. Pull request #166, opened August 22 and merged August 30, reports: “Bridge node 2 reached %create-withdrawal-tx while withdrawals were intended to be operationally paused.”⁸ The node’s signing key failed a membership check, and the halt it caused spread to two other bridge nodes. The fix added a setting, withdrawal_processing_enabled, that is off by default.⁸

The withdrawal code itself waits in seven stacked pull requests, numbers 169 to 175. All seven were opened within two minutes on September 1, and all were last updated at 06:01 UTC that day. None has a comment or a review.⁹¹⁰ Even once that code is merged, turning withdrawals on would take operator action, according to the last of them: “An operator must enable admission.”¹⁰

The roadmap date

The earliest archived copy of the roadmap, from January 18, listed Bridge Withdrawals for Q1 2026, as planned.¹¹ Nockchain’s “Roadmap 2026” post of January 16 also put “Robust bridge withdrawal support” in its first phase, for Q1 2026.¹⁴ By June 16, the date was Q2 2026 and the status was current.¹²

The live roadmap now lists Q1 2027, as planned.¹³ That is four quarters later than the first date, and it moved the item from current back to planned.

You can follow withdrawals in our Bridge Watch, which updates with every build, and on the Roadmap Tracker.