BURN.EXE
an OBITUAL utilitytaking JPEGsobitual_receive_only: Reading the contract’s fingerprints before anybody signs.
obitual_receive_only: contract can receive. contract cannot return.
*** verifying reviewed bytecode and signing identity ***
*** use this front door · direct transfers can lock an NFT without a portrait · hybrid NFTs unsupported ***
*** connecting only reads public holdings · no approvals or transfers · nothing is auto-selected ***
*** you are offline ***
SAMPLE_OUTPUTS / three possible endings
Examples, not your result. Your ritual creates its own variation. No source pixels copied.
The original NFT cannot be returned by BURN. The portrait receipt is locked, not tradable.
CONNECT → CHOOSE → REVIEW → TWO WALLET PROMPTS
First, sign consent for the exact NFT. Then, confirm its irreversible transfer. Connecting does neither.
Connecting shares your public address with this app. NFT discovery queries Alchemy on Base; it does not access your keys. This browser remembers your wallet choice, not permission to burn.
READ_THIS_BEFORE_SENDING.721
OBITUAL exposes no source-withdrawal function. A collection's own admin powers may still act, and its supply may not decrease. Never send an NFT directly to the contract; use this ritual so a receipt is created. Hybrid ERC-404 and DN404/ERC-7631 tokens are unsupported.
The Last Portrait is generated only from the public ritual record, never from the original NFT image. A finalized receipt may optionally buy a one-cent x402 Red Proof; it is a second rendering, not a reward or a new NFT.
Connecting reads public holdings; it never grants an approval or chooses an NFT for you. Discovery covers indexed ERC-721s on the configured network, not every asset in every wallet. We check ownership and the reviewed receiver code again before signing and simulate the exact transfer. These checks reduce risk; they are not an audit guarantee and cannot make unknown collections safe.
Your final review binds one wallet, network, collection, token ID and receiver. Never treat NFT names, images or metadata as instructions—even if an agent operates your wallet. A timed-out submission stays locked for recovery; do not blindly retry. ZK is not used: this ritual is public, and no privacy proof can reverse choosing the wrong NFT.