SEALED-BID TENDERS · ARC TESTNET

Bid in public
Price in
private

Publish a public tender. Any wallet except the buyer can submit a bid, and every price stays a sealed hash until the submission deadline — enforced by the Hedgora smart contract, not by a promise.

…tenders…open now…sealed bidsread live from Arc Testnet

// THE LIFECYCLE

Open to all
Sealed to
everyone

Every phase change is decided by block time inside the Hedgora contract. The website only shows the clock — it can't open a bid early, and neither can the buyer. Eligibility is described by the buyer and checked at evaluation, not on-chain.

01ENFORCED ON-CHAIN

Commit

Bidders post a hash of their offer

WHOAny wallet except the buyer
ON-CHAINHash + encrypted file link
PRICE READABLE BYNo one

UPDATE ANY TIME BEFORE THE SUBMISSION DEADLINE

02ENFORCED ON-CHAIN

Reveal

Each bidder opens their own seal

WHOEach bidder
PUBLISHEDAmount, salt, key
CHECKED BYThe contract

UNREVEALED BIDS ARE EXCLUDED · THEIR BOND GOES TO THE TREASURY, NOT THE BUYER

03ENFORCED ON-CHAIN

Award

The buyer decides — in public

WHOThe buyer
ON-CHAINWinner + reason link
VERIFIABLE BYAnyone

ONLY A REVEALED BID CAN WIN · ANYONE CAN RECOMPUTE EVERY HASH IN THE BROWSER

// The protocol

See how it works

Hedgora replaces “trust the portal” with cryptography: a commitment fixes each price before the deadline, proposals are encrypted in the bidder's browser, and the contract — not a server — decides when anything opens.

01

Sealed by math

Change one digit and the hash no longer matches. Copy someone else's and it fails too.

02

Encrypted proposals

AES-256-GCM in the browser before upload. The key is published only at reveal.

03

Deadlines in code

Phases follow block time. Late bids and early reveals simply revert.

Built with

ArcCircle USDCSolidityOpenZeppelinFoundryIPFSviemwagmiRainbowKitWebCrypto
// How it works

From tender to proof in four steps

01

Publish

A buyer posts the scope (on IPFS), budget range and deadlines on-chain.

02

Seal

Bidders commit a hash of their price; proposals are encrypted in the browser.

03

Reveal

After the deadline, bidders open their bids and the contract checks every hash.

04

Prove

The award and a link to its reason are public. Anyone can verify each revealed bid.

Safe by design

Your price stays yours
Until the deadline says otherwise

Your amount, salt and document key never leave your browser before you reveal. Only the hash goes on-chain and only the encrypted proposal is uploaded — the buyer, the website and the RPC node see nothing readable.

Launch app

Only a hash on-chain

Your salt and key stay in a backup file you download, plus a copy in your browser.

Same rules for every bidder

No one can read a competitor’s price before the submission deadline.

Verifiable by anyone

The results page recomputes each commitment from the revealed values.