Built for Build Before Q-Day. Live on the QoreChain testnet, qorechain-diana. Read the source
New Try to rob it: 13 live attacks in the attack lab

How far does your key reach right now?

On QoreChain a stolen classical key can only do what your post-quantum key has left open. Fenestella shows you that opening, cuts it down to the contracts, amount and time you need, and gives dApps and agents one way to ask for it.

Read-only. Nothing is signed.
OR
Finds QoreX, Keplr, Leap, Cosmostation, MetaMask, Rabby and other wallets in this browser.

Reading an account needs no wallet and no gas. Works on testnet and mainnet.

▶ Watch the 2:55 demo
Live, not a mock-up

What it has proven, right now

Read from the chain and from the real test runs each time this page refreshes. Swipe, or let it play.

Attack lab · live on testnet
13 of 13 refused

Real attacks you can run yourself. Each one names the layer that stopped it.

  • Stolen classical key 3
  • Stolen agent key 3
  • Forged, tampered or replayed 5
  • Fooling the AI 2
Try to rob it →
One answer per account

Every account is in one of four states

Fenestella reads the chain and tells you which, in a sentence you can act on. If something could not be read, it says so instead of guessing.

Sealed

Post-quantum key registered, no window open. A stolen classical key moves nothing.

Scoped opening

A window for named contracts or plain transfers only, with a count, a cap and an expiry.

Wide open

A window with no scope. Any contract, any recipient, until it runs out.

Can be taken over

No post-quantum key yet. Whoever holds the classical key can register theirs first.

How it works

See it. Narrow it. Let apps ask for it.

01

See the truth

Post-quantum key, proof of possession, encryption key, live window, linked keys and their limits, read straight from the chain.

See a live account →
02

Open a fenestella

A window limited to named contracts or to plain transfers. Your wallet signs it with the hybrid ML-DSA-87 signature; the chain enforces every bound.

How windows work →
03

Let apps ask

One call, requestWindow(). The app states what it needs, you see its address and the bounds in plain words, and you approve in your own wallet.

Try the request flow →
Checked on testnet

Enforced by the chain, not by this page

We play the attacker ourselves, and you can too. In the attack lab every attempt runs live on testnet and is refused by the chain, the vault, the seal or the AI, with a receipt when a transaction reached the chain.

13 of 13
real attacks refused live: a stolen classical key, a stolen agent key, forged post-quantum signatures, phishing and prompt injection. Run them →
54
contract tests passing: 6 fuzz tests, 6 invariants held over thousands of random attacker moves, and fail-closed checks for inactive precompiles
91
unit tests on the exposure answer, the request checks, the AI's guard, autopay and plain-English rules
0
of your keys held by Fenestella. Your wallet signs everything you approve.