Badger @BadgerCrypto - Twitter Profile

Pinned Tweet

7 months ago

$ZEC and $XMR were the first to take our privacy rights on chain Now $NOX is building on that same mission, just at a different layer of the stack. let’s dive in @nonossystems 1/7

BadgerCrypto's tweet photo. $ZEC and $XMR were the first to take our privacy rights on chain
Now $NOX is building on that same mission, just at a different layer of the stack.
let’s dive in
@nonossystems
1/7 https://t.co/60quwLoKhE

NØNOS

@nonossystems

7 months ago

The next stage of NØNOS: Implementation of the deterministic attestation and verification layer. As the bootloader moves towards v0.1 completion, focus moves to embedding the cryptographic verification path directly inside the initialization chain. The objective is a fully self-contained execution environment where proof verification, circuit integrity and provenance exist at the firmware boundary and before any dynamic subsystem runs. The new contributor-driven workflow enables external developers to create and verify circuits that extend the attestation layer. Each contribution includes reproducible build instructions, verifying keys (VKs), metadata and optional zk-ceremony transcripts for Groth16 setups. Our deterministic CI replays each circuit build in a hermetic sandbox, ensuring byte-for-byte reproducibility of the VK. The CI also generates a reference proof to confirm functional validity. Once validated, the VK is compressed, hashed and serialized through zk-embed, producing a canonical Rust snippet containing: i) PROGRAM_HASH constant (domain-separated by namespace) ii) normalized compressed VK bytes iii) a lookup function that binds the proof program to its verifier That snippet is compiled into the bootloader, producing an image that embeds a verifiable registry of circuits, every verifier linked to its exact source and ceremony transcript. At runtime, devices can verify proofs entirely offline, using embedded VKs with no external fetches, no trust in remote servers and no mutable key sources. Each build of the bootloader is a cryptographic snapshot of trust, deterministically reproducible by any third party. Security mechanisms are being extended to handle revocation of compromised VKs through signed capsule updates and memory-safe deprecation lists at boot. On constrained systems, proof verification can be delegated to companion secure elements via a future co-processor handshake protocol, while maintaining deterministic attestations at the kernel boundary. The reward layer begins with verified merge bounties deterministic payouts triggered on successful CI validation and maintainer review and evolves into usage-based and maintenance incentives that measure actual proof activity in the field. The NØNOS bootloader thus becomes the first stage in a self-contained trust pipeline: source > reproducible verifier > compiled boot image > hardware-level validation. This is what decentralization looks like when engineered at the silicon boundary not in contracts, but in the boot chain itself.

nonossystems's tweet photo. The next stage of NØNOS: Implementation of the deterministic attestation and verification layer.

As the bootloader moves towards v0.1 completion, focus moves to embedding the cryptographic verification path directly inside the initialization chain. The objective is a fully self-contained execution environment where proof verification, circuit integrity and provenance exist at the firmware boundary and before any dynamic subsystem runs.

The new contributor-driven workflow enables external developers to create and verify circuits that extend the attestation layer. Each contribution includes reproducible build instructions, verifying keys (VKs), metadata and optional zk-ceremony transcripts for Groth16 setups.

Our deterministic CI replays each circuit build in a hermetic sandbox, ensuring byte-for-byte reproducibility of the VK. The CI also generates a reference proof to confirm functional validity. Once validated, the VK is compressed, hashed and serialized through zk-embed, producing a canonical Rust snippet containing:

i) PROGRAM_HASH constant (domain-separated by namespace)

ii) normalized compressed VK bytes

iii) a lookup function that binds the proof program to its verifier

That snippet is compiled into the bootloader, producing an image that embeds a verifiable registry of circuits, every verifier linked to its exact source and ceremony transcript. At runtime, devices can verify proofs entirely offline, using embedded VKs with no external fetches, no trust in remote servers and no mutable key sources. Each build of the bootloader is a cryptographic snapshot of trust, deterministically reproducible by any third party.

Security mechanisms are being extended to handle revocation of compromised VKs through signed capsule updates and memory-safe deprecation lists at boot. On constrained systems, proof verification can be delegated to companion secure elements via a future co-processor handshake protocol, while maintaining deterministic attestations at the kernel boundary.

The reward layer begins with verified merge bounties deterministic payouts triggered on successful CI validation and maintainer review and evolves into usage-based and maintenance incentives that measure actual proof activity in the field.

The NØNOS bootloader thus becomes the first stage in a self-contained trust pipeline:

source > reproducible verifier > compiled boot image > hardware-level validation.

This is what decentralization looks like when engineered at the silicon boundary not in contracts, but in the boot chain itself.

19

112

34

5

21K

2

47

6

2

7K

Badger

@BadgerCrypto

Who to follow

Last Seen Users on Sotwe

Trends for you

Most Popular Users