NØNOS ✓

@nonossystems

NØNOS ~ a microkernel that forgets. RAM-resident and signed, built so no trace survives a reboot. Privacy as default. $NOX

3 087Followers

68Following

1 326Posts total

4.3KViews on collected posts

Against accounts of the same size

9 posts from the last 90 days, next to the under 10K follower range. reaches fewer people than peers, but engages them much harder.

Median views108this account3 808median for under 10K

Reach, %3.50%this account249.49%median for under 10K

Engagement, %5.08%this account1.30%median for under 10K

Metric	This account	Median for under 10K	Ratio
Median views per post	108	3 808	0.03×
Reach (views ÷ followers)	3.50%	2.5× audience	0.01×
Engagement rate	5.08%	1.30%	3.91×

Others in this range → Compare with another account → How these benchmarks are built →

Growth & engagement

How the posts we collected actually performed: views and reaction rate post by post, what the audience did with them, and where the follower count goes.

Views per post

3.2K3 Sep

252

161

118

108

100

Last 9 collected posts, oldest on the left. The scale is logarithmic: one post can outrun the rest a hundred times over.

Engagement rate per post

2.44%3 Sep

4.37%

5.59%

5.08%

6.67%

6.12%

5.56%

5.00%

4.17%

Reactions — likes, reposts, replies and quotes — divided by views. Median for under 10K accounts is 1.30%.

What the audience does

Likes70.7%94 in total

Reposts15.0%20 in total

Replies11.3%15 in total

Quotes2.3%3 in total

Bookmarks0.8%1 in total

Share of every reaction we collected for this account. Replies mean argument, reposts mean endorsement, bookmarks mean the post was worth keeping.

The follower curve appears once this account has two daily snapshots — we take one a day, and this one is on its first.

Latest posts

@nonossystems #defend #privacy #atallcosts 96 views · 4 likes · 0 reposts · 0 replies 03 Sep 2026 8/ Proof, sha256, structure files, benchmarks, manifest, code: https://t.co/CD78y9BINy branch outer-shrink to proofs/ sha256: bbeaed2923f4b4e9c4aa80317dea16f6f0f81e0f2b41473dfe14f2b07ae35368 100 views · 5 likes · 0 reposts · 0 replies 03 Sep 2026 7/ What stands between this file and the closed beta, wallets registered, live: the on-chain verifier finishes its port and must accept these exact bytes while rejecting every staged forgery. + One gas receipt on testnet. The 2 speed optimizations land and the 108 views · 5 likes · 0 reposts · 1 replies 03 Sep 2026 5/ The on-chain verifier is being ported element for element from same constraint definitions the recursion executes in-circuit. Same algebra, two languages, zero transcription. All 9 region bodies are now ported, 31 known-answer tests green. On day 1 its constants check 98 views · 5 likes · 0 reposts · 1 replies 03 Sep 2026 6/ The honest line, because it is the home-brand: this artifacts outer proof runs at development rate. The settlement version needs 2 optimizations, both designed, both public, both underway and the manifest sitting beside the proof says exactly that, so the file can never be 90 views · 5 likes · 0 reposts · 1 replies 03 Sep 2026 4/ Every constant a verifier needs is now emitted by the prover itself derived from the circuit into a JSON file and emitter refuses to write it unless the full witness satisfies first. Nobody types numbers anymore. A hardcoded 64 once hid a 128x bug from every test we had. 118 views · 5 likes · 0 reposts · 1 replies 03 Sep 2026 3/ 10 days ago the circuit doing this was half waste: 524,288 rows spent recomputing a schedule that never changes. We replaced the recomputation with 32byte commitment and the circuit halved. Most of engineering a proof system is deleting what a proof never needed. 161 views · 8 likes · 0 reposts · 1 replies 03 Sep 2026 2/ Inside it: a real shielded transfer, proven valid and that proof then verified inside a second STARK (all 32 queries of the inner verifier re-executed as pure arithmetic) One proof, carrying the whole argument. Our machine re-verified it from its own bytes in 29 seconds. 252 views · 9 likes · 1 reposts · 1 replies 03 Sep 2026 🧵 899,196 bytes settle an argument that has run for a decade: whether Ethereum can have private transfers with no ceremony behind them, no operator inside them and no quantum computer ahead of them. The file is public. Anyone can re-verify it. The rest of this thread is ht 3.2K views · 48 likes · 19 reposts · 9 replies 03 Sep 2026