Your contracts are audited. Your website isn't.

Signet brings DeWEB's trust guarantee to every website: no migration, your own domain, plus approval rules for every release.

Bybit / Safe{Wallet}tampered JavaScript~$1.5B
BadgerDAOinjected script~$120M
Ledger Connect Kitpoisoned npm packagewallet drainer
Curve FinanceDNS hijackfrontend
CoW Swapdomain hijackfrontend
AerodromeDNS hijackfrontend
01 / What users see

Same page.
Different code.

A swapped file doesn't change how the site looks. Scroll to watch one attack from the user's side.

Step 1 of 4

A normal release.

The team ships version 42. Signet fingerprints every file and seals the set on X Layer.

Step 2 of 4

One file is swapped.

A leaked CDN key, a hijacked domain, a poisoned package. One script changes and nobody on the team notices.

Step 3 of 4

The wallet asks to sign.

The button still says Swap. The transaction underneath sends the tokens somewhere else.

$0left Bybit this way in February 2025
Step 4 of 4

Guard stops it.

The page no longer matches its seal, so the request never reaches the wallet. The user gets the verified copy.

$0sent by a user running Guard
app.demoswap.xyz
● Sealed #42 ● Seal broken

Swap

You pay2,500.00
USDT
You receive≈ market
OKB
Swap
Release #42 · sealed files
index.htmlmatch
assets/app-2aa5a3e0.jsmatch
assets/vendor-91c0.jsmatch
assets/style-77e1.cssmatch
manifest.jsonmatch
cdn-cgi/loader.jsnot sealed
assets/app-2aa5a3e0.js+1 line
const tx = buildSwap(route, amount);
+ if (amount > 1000) tx.to = "0x9f3c…e21a";
return wallet.sendTransaction(tx);
WalletX Layer
Confirm transaction
ActionSwap
Send to0x9f3c…e21a
Amount2,500 USDT
Reject
Confirm

Stop. This site's seal is broken.

Signet stopped this page from asking your wallet to sign. Nothing was sent.

Open the verified copyLeave this site
02 / How it works

Seal. Approve.
Guard.

Set it up once. After that, every release takes the same path, and your contracts don't change.

01

Every build gets a fingerprint.

Your CI hashes each file and lists the contracts the site may call. That set becomes a release proposal on X Layer.

A stolen CI key can propose a release. It can never approve one.
$ signet seal dist
hashing 7 files…
✓ index.html 9f2c…41aa
✓ assets/app-2aa5a3e0.js 51d0…c3e9
✓ assets/vendor-91c0.js 0be4…77d2
✓ allowlist 3 contracts
✓ origins no change
→ proposed release #43 · tier 00 · code only
02

A TapeOut circuit makes the call.

Approvals and waiting time go into circuit #6, a fixed NAND circuit on X Layer. Riskier changes need more people and a longer wait.

Its beacon has no owner. Nobody can change the rule, including us.
CICI key proposed #43can't approve
AApprover Awaiting
BApprover Bwaiting
CApprover Cwaiting
1:00:00timelock for this risk tier
circuit #6 → PUBLISH0
03

Users are checked as they sign.

Guard reads the sealed release from two separate X Layer nodes, compares it with the page, and only then lets the wallet open.

Built for browser wallets that use the standard EIP-1193 connection.
Node 1xlayerrpc.okx.comrelease #43 · 0x51d0…
Node 2xlayer.drpc.orgrelease #43 · 0x51d0…
both nodes agree
7 of 7 files match the seal
Contract is on the sealed allowlist
Signature request passed to the wallet
03 / The rule

A rule nobody
can change.

Pick who approved, what changed and how long it has waited. The release policy answers the way circuit #6 does on X Layer.

Who approved
What changed
under 1 h1 h+24 h+
Switches
PUBLISH0
UNFREEZE0

9 inputs, 34 NAND gates, 512 possible cases. UNFREEZE is 1 whenever two approve; the gate only uses it while frozen. The wiring above is drawn for clarity; the real netlist is public on X Layer.

04 / Benchmark

12 attacks.
12 stopped.

The same twelve attack types, run on a fork of X Layer against three kinds of protection.

0false blocks
16clean sessions tested

Guard protects people who have it installed. Visitors without it aren't blocked; the watchtower alerts the team instead.

2/12
7/12
12/12
Subresource IntegritySRI tags only
Page hash checkhash-only extension
Signetseal + Guard
How it compares
DeWEB siteCode-hash checkersCode Verify, WEBCATScam detectorsBlockaid, Wallet Guard…Signet
Your own domain, no migrationNo: the site moves on-chainYesAny siteYes
Page files checked against a public recordYes, in TapeKitYesNoYes, with Guard
Approval rules for every releaseNo: the holder publishesSigners onlyNoYes: on-chain tiers, timelocks, a TapeOut circuit
What a wallet may sign, per siteNoNoKnown-bad lists, simulationSealed allowlist
05 / Proof

Don't trust us.
Check it.

One read-only command checks the claims on this page: the on-chain ones against X Layer mainnet, the rest against this repo. No wallet, no keys.

signet
$ pnpm verify:claims
TapeOut processor #101 · X Layer mainnet
0x73153e5fd2Acac604D49d6ca9fea27b750718F22
Release policyCircuit #6 · 34 NAND · 9 inputs · 2 outputs
Upgrade keysNone on the circuit. Its beacon owner is 0x0.
In your browserOpen the proof page
06 / For teams

Set up in
an afternoon.

Five steps on the setup guide; one step added to your deploy. Nothing changes in your contracts. Your first release goes live after two approvals and 24 hours. Always free for your users.

Free

One domain, sealed releases with on-chain approvals, Diff Guard, the "Sealed by Signet" badge, and Guard protection for every visitor who has it.

$0 · start now

Pro

Three domains, a watchtower that checks every minute, private alerts and a verified copy hosted on X Layer.

planned · early access

Enterprise

Setup done with your team, incident support, and an API for wallets.

planned · talk to us