Your browser encrypts the amount with AES-256-GCM and wraps the key with RSA-OAEP-2048, bound to one auction.
- AES-256-GCM
- RSA-OAEP-2048
Your amount is encrypted in your browser and locked with a deposit. Only the winning bid is ever revealed.
How it works
Your deposit and the encrypted bid travel in one transaction. The receipt's commitment is checked against the one your browser computed.
Every accepted bid extends one ordered keccak digest, so the complete set is pinned on chain before anyone ranks it.
After the close the solver decrypts the whole set and ranks it. A missing or altered bid stops the run; there is never a partial winner.
The winner pays the remainder and receives the token in the same transaction. Every other deposit is refundable right away.
The stack
Nothing here asks you to trust a black box. Each stage runs on a public standard you can read and test.
Your browser encrypts the amount with AES-256-GCM and wraps the key with RSA-OAEP-2048, bound to one auction.
Every accepted bid extends one ordered keccak-256 digest, so the whole set is pinned on chain before anyone ranks it.
After the close, the contract on NEAR hands the complete bid set to the solver in an OutLayer TEE worker and takes its answer as the result of that call.
Deposits, the asset token and the final payment stay in one NEAR contract. Money moves as a NEP-141 token, and each lot is one token with NEP-171 views.
Sealed in your browser
Runs in this tab
Each keystroke makes a fresh envelope, even for the same amount. The key is thrown away; nothing leaves this tab.
AES-256-GCM for the amount, RSA-OAEP-2048 for the key, bound to one auction.
Fresh key, IV and nonce on every seal, so equal bids look unrelated.
The commitment on chain must equal the one computed here.
Register it, have a verifier approve it, then list it. Bidders compete on price without ever seeing each other's numbers.