ebidz
01 / ProtocolArciumPowered by Arcium

The auction layer forconfidential onchain markets.

eBidz is a sealed-bid auction protocol where every bid is encrypted client-side, kept opaque onchain, and processed by Arcium's MPC cluster, so no validator, no other bidder, and not even the auction creator can read or front-run your bid before settlement.

Cluster status · live
Nodes online5 / 7
Thresholdt = 5
MPC versionarcium-v0.3.2
NetworkSolana devnet
Latency p50412ms
Cluster pubkey··········

Bids encrypted with this pubkey are decryptable only via threshold MPC across the cluster. No single node holds the full key.

BIDS SEALED · 1,247 IN LAST 24HTOTAL ESCROWED · 18,420 SOLAUCTIONS SETTLED · 89AVG BID PRIVACY · 100%MEV EXTRACTED · 0CLUSTER UPTIME · 99.97%AVG SETTLEMENT TIME · 47sCLEAR PRICE ACCURACY · CRYPTOGRAPHICBIDS SEALED · 1,247 IN LAST 24HTOTAL ESCROWED · 18,420 SOLAUCTIONS SETTLED · 89AVG BID PRIVACY · 100%MEV EXTRACTED · 0CLUSTER UPTIME · 99.97%AVG SETTLEMENT TIME · 47sCLEAR PRICE ACCURACY · CRYPTOGRAPHIC
02 / Problem

Onchain auctions are fundamentally broken.

Every transparent bid is a leak. Every plaintext mempool transaction is an invitation to extract. The auction is no longer a price-discovery mechanism, it’s a game for insiders.

/01
$0B+

MEV extracted in 2024

Every plaintext bid is a public price signal

When bid amounts hit the mempool, MEV bots front-run, sandwich, or reorder transactions to extract value from honest participants.

/02
0%

Privacy in current auctions

Sophisticated bidders watch and react

In open ascending auctions, every bid is visible. Retail bidders are at a permanent disadvantage versus actors monitoring the chain in real time.

/03
~0%

NFT auctions affected by shilling

Insider collusion and fake scarcity

Auction creators and coordinated groups place shill bids to inflate prices, suppress competition, or extract from legitimate participants.

/04
No theory

Vickrey auctions onchain, until now

Optimal mechanisms require bid privacy

Vickrey auctions are theoretically optimal for honest bidding, but require bid secrecy. Without MPC, they are impossible to run trustlessly onchain.

03 / Lifecycle

Trustless privacy, end to end.

Every step in the bid lifecycle is designed so no single party, not the creator, not validators, not Arcium itself, can read or front-run your bid.

01

Encrypt locally

Your bid is encrypted in your browser using the Arcium cluster’s threshold public key. The plaintext never leaves your machine.

02

Submit ciphertext

The encrypted bid and a SOL deposit are stored onchain in a per-bidder PDA. Nobody, including validators, can read the bid.

03

MPC computes the winner

At deadline, anyone calls close_auction. Arcium’s MPC cluster runs the winner-determination circuit across ciphertexts.

04

Onchain settlement

The cluster posts the cluster-signed result via callback. The program verifies the signature, settles the winner, opens refunds.

04 / Mechanisms

Three auction types. One privacy guarantee.

Each type uses a different MPC circuit, but all share the same property: bids are computed without ever being decrypted.

First-PriceLive

Highest bid wins, pays own bid.

Best for
NFT sales · fundraising · one-off assets
Bidder strategy
Strategic shading, bid below true valuation
VickreyComing soon

Highest bid wins, pays second-highest.

Best for
Token sales · governance · fair price discovery
Bidder strategy
Truthful bidding, dominant strategy
Uniform-PriceComing soon

K winners pay the same clearing price.

Best for
Token launches · NFT batches · allowlist slots
Bidder strategy
Bid your true marginal valuation
07 / Marketplace

Live auctions.

09 / Security

No admin keys. No backdoors. No trust me bro.

The protocol guarantees you a refund or your item, no matter what fails.

PDA-only escrow

Bid deposits live in a program-derived address. Neither the creator, eBidz Labs, nor any admin has withdrawal rights.

Permissionless settlement

close_auction is callable by anyone after the deadline. No trusted crank or relayer is needed for liveness.

MPC liveness fallback

If the cluster fails to deliver within MPC_TIMEOUT, force_cancel becomes callable, every bidder gets refunded.

Open source · onchain

The Anchor program, Arcium circuits, and the entire frontend are open source and reproducibly buildable.

10 / FAQ

Frequently asked.

01How is my bid actually encrypted?+

The frontend encrypts your bid using the Arcium cluster’s threshold X25519 public key. The encrypted bid is then submitted to the Solana program. Only a quorum of MPC nodes acting together can decrypt, and even then, only inside the MPC circuit, never to a single node.

02What if Arcium goes down?+

If MPC times out(default 24h) elapses after auction closes without a settled result, the force cancel instruction becomes callable by anyone. It refunds every bidder’s deposit and returns the item to the creator. Bidders never have funds permanently locked.

03Can the auction creator see bids?+

No. The creator has no read access to encrypted bid data, they’re just another participant from the protocol’s perspective. They configure the auction; they cannot influence or peek at it.

04Why not zk-SNARKs instead of MPC?+

SNARKs prove things about already-known data. The hard part of a sealed-bid auction is computing over data nobody has access to. MPC gives us correctness and privacy on encrypted inputs, exactly the primitive we need.

05What’s the gas cost?+

A standard Solana transaction for bid submission (~5,000 lamports), plus rent for the Bid PDA. Settlement is a single Arcium callback. Total cost per auction is roughly equivalent to a token transfer + a small CPI call.

06Can I update my bid?+

No. Bids are immutable once submitted. Raising a bid would require topping up the plaintext deposit, which leaks an upper bound on the new amount. For Vickrey auctions this isn’t a problem, truthful bidding is already optimal.

11 / Get started

Run an auction
no one can game.

Sealed-bid by default. Trustless settlement. Refunds guaranteed by program logic. Five minutes to launch.