#nil $NIL @Nillion Sealing your bid keeps the number hidden. It doesn't make the auction fair.
Nillion is the project behind Covenants, a product for locking a payload—like a bid amount—to a release condition on-chain. Under intended honest-node operation, shares are released after that condition is met. Dusk is the foundation phase of Covenants on Ethereum L1, establishing the cryptography, node network, and developer tooling. It's groundwork being laid, not a finished platform.
How it works: your payload is split into Shamir shares across a committee. Fewer than k shares reveal nothing about the content. That's meaningful privacy—but it has edges.
Hypothetical example: imagine Alice seals a 2 ETH bid on a tokenized asset via Covenants, tied to a deadline block. No group smaller than k can see her amount. But here's what sealing does not cover:
→ If k or more nodes collude, they can reconstruct Alice's bid before the deadline. Honest-node operation is assumed, not absolute.
→ Timing and metadata stay public—observers know Alice transacted, just not how much.
→ Unsealing doesn't mean Alice wins or gets a favorable price. Auction rules and contract logic are separate layers.
The docs present sealed-bid auctions as an example use case, not as evidence of a specific deployed auction application.
Practical takeaway: before trusting any sealed-bid system, check the threshold assumptions, what metadata remains visible, and whether the auction's smart-contract logic is independently audited. Cryptographic sealing is one layer, not the whole stack.
Nillion is the project behind Covenants, a product for locking a payload—like a bid amount—to a release condition on-chain. Under intended honest-node operation, shares are released after that condition is met. Dusk is the foundation phase of Covenants on Ethereum L1, establishing the cryptography, node network, and developer tooling. It's groundwork being laid, not a finished platform.
How it works: your payload is split into Shamir shares across a committee. Fewer than k shares reveal nothing about the content. That's meaningful privacy—but it has edges.
Hypothetical example: imagine Alice seals a 2 ETH bid on a tokenized asset via Covenants, tied to a deadline block. No group smaller than k can see her amount. But here's what sealing does not cover:
→ If k or more nodes collude, they can reconstruct Alice's bid before the deadline. Honest-node operation is assumed, not absolute.
→ Timing and metadata stay public—observers know Alice transacted, just not how much.
→ Unsealing doesn't mean Alice wins or gets a favorable price. Auction rules and contract logic are separate layers.
The docs present sealed-bid auctions as an example use case, not as evidence of a specific deployed auction application.
Practical takeaway: before trusting any sealed-bid system, check the threshold assumptions, what metadata remains visible, and whether the auction's smart-contract logic is independently audited. Cryptographic sealing is one layer, not the whole stack.