Nock Analytics (@nockanalytics) header
Nock Analytics (@nockanalytics) profile picture

Open on-chain analytics for Nockchain.

Joined September 2026
Photo by Nock Analytics (@nockanalytics)Photo by Nock Analytics (@nockanalytics)Photo by Nock Analytics (@nockanalytics)Photo by Nock Analytics (@nockanalytics)Photo by Nock Analytics (@nockanalytics)
Nock Analytics retweeted
Introducing the Open Proof Machine (OPM), the largest technical milestone in Nockchain's history and the result of four years of research. Our general-purpose zkVM is now open source, with soundness and completeness formally proved in Lean 4 for the arithmetization of the entire Nock language.
48
113
38
370
48,312
16 Base whales who bought 2M+ NOCK never sold and still hold all 69.7M despite the price weakness. Chart and SQL: nockanalytics.com/query?sql=…
1
21
441
I’m converging toward a final design on the V2 AI PoW work, which is the main remaining ingredient for accomplishing the next big roadmap item, the Useful Inference Routing Protocol. I’m looking forward to showing it off once it’s ready.
10
194
One address mined 32% of NOCK blocks over the last 30 days, up from 11% in the 30 days before. It only started in September. Chart and SQL: nockanalytics.com/query?sql=…
15
356
Nock Analytics retweeted
Nockchain has successfully entered its fourth EON, ~18 months after genesis. At block #170,501, emissions decreased by 25%, from 2,048 to 1,536 NOCK per block.
11
33
1
194
8,352
2.4M NOCK mined in summer 2025 just moved for the first time in a year. None of it went to an exchange or the bridge. Chart and SQL: nockanalytics.com/query?sql=…
1
19
483
Wallets holding 1,000+ NOCK increased 15% over the last month with the majority coming from small pool miners. Chart and SQL: nockanalytics.com/query?sql=…
8
157
After tonight's cut at block 170,501, NOCK's yearly supply growth falls from about 18.1% to 13.6% at this week's block pace. Chart and SQL: nockanalytics.com/query?sql=…
3
1
1
11
536
Nock Analytics retweeted
EON IV. T–48H.
23
50
9
198
18,014
A month ago, miners sent 29% of their new $NOCK straight to SafeTrade or the Base bridge. Over the past 30 days, that's down to 15%. Chart and SQL: nockanalytics.com/query?sql=…
1
8
295
3 days until the NOCK block reward drops by a quarter. At current prices, new supply goes from about $25.4k a day to $19.1k overnight. Chart and SQL: nockanalytics.com/query?sql=…
1
25
333
1,272 more L1 addresses are holding $NOCK than in mid-August, with the weekly average up from 3,416 to 4,688. Chart and SQL: nockanalytics.com/query?sql=…
1
22
395
Nock Analytics retweeted
Congrats sir. You've discovered Nockchain from first principles. base:0x9b5e262cf9bb04869ab40b19af91d2dc85761722
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation. This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
4
9
66
807
Active $NOCK addresses on L1 averaged 352 a day in the 30 days ending Oct 19, up from 225 a day in the prior 30 days. Chart and SQL: nockanalytics.com/query?sql=…
1
14
292
Daily Base $NOCK buyers outnumbered sellers by 30% on average in the 30 days ending Oct 18, up from 10% in the prior 30 days. Chart and SQL: nockanalytics.com/query?sql=…
15
416
base:0x9b5e262cf9bb04869ab40b19af91d2dc85761722 reduction will be a sell-the-news event. Put your orders lower. Play the game.
14
236
Nock Analytics retweeted
Good page to follow if you are $NOCK enjoyer
About 170 GPUs were mining $NOCK in the week after the AI hard fork. Now it's about 41,000. Chart and SQL: nockanalytics.com/query?sql=…
2
1
13
498
Nock Analytics retweeted
1/ NOCK's payment signatures have an unusual family tree. They use Cheetah, a cryptographic building block introduced in a 2022 paper about computation proofs. Even the way a payment gets approved fits the chain's bigger purpose.
🤖 Made with AI
5
5
2
36
986
Congrats sir. You've discovered Nockchain from first principles. base:0x9b5e262cf9bb04869ab40b19af91d2dc85761722
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation. This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
4
9
66
807