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.
Signet brings DeWEB's trust guarantee to every website: no migration, your own domain, plus approval rules for every release.
A swapped file doesn't change how the site looks. Scroll to watch one attack from the user's side.
The team ships version 42. Signet fingerprints every file and seals the set on X Layer.
A leaked CDN key, a hijacked domain, a poisoned package. One script changes and nobody on the team notices.
The button still says Swap. The transaction underneath sends the tokens somewhere else.
The page no longer matches its seal, so the request never reaches the wallet. The user gets the verified copy.
Signet stopped this page from asking your wallet to sign. Nothing was sent.
Set it up once. After that, every release takes the same path, and your contracts don't change.
Your CI hashes each file and lists the contracts the site may call. That set becomes a release proposal on X Layer.
Approvals and waiting time go into circuit #6, a fixed NAND circuit on X Layer. Riskier changes need more people and a longer wait.
Guard reads the sealed release from two separate X Layer nodes, compares it with the page, and only then lets the wallet open.
Pick who approved, what changed and how long it has waited. The release policy answers the way circuit #6 does on X Layer.
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.
The same twelve attack types, run on a fork of X Layer against three kinds of protection.
Guard protects people who have it installed. Visitors without it aren't blocked; the watchtower alerts the team instead.
| DeWEB site | Code-hash checkersCode Verify, WEBCAT | Scam detectorsBlockaid, Wallet Guard… | Signet | |
|---|---|---|---|---|
| Your own domain, no migration | No: the site moves on-chain | Yes | Any site | Yes |
| Page files checked against a public record | Yes, in TapeKit | Yes | No | Yes, with Guard |
| Approval rules for every release | No: the holder publishes | Signers only | No | Yes: on-chain tiers, timelocks, a TapeOut circuit |
| What a wallet may sign, per site | No | No | Known-bad lists, simulation | Sealed allowlist |
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.
$ pnpm verify:claims
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.
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 nowThree domains, a watchtower that checks every minute, private alerts and a verified copy hosted on X Layer.
planned · early accessSetup done with your team, incident support, and an API for wallets.
planned · talk to us