Ordinals · Ethereum
Teleburn Verifier
Paste a Bitcoin inscription ID to get its Ethereum teleburn address. Add an NFT collection and token ID to check whether that token was teleburned to the inscription.
Teleburn address
Show the derivation
- Txid as displayed
- Txid, internal byte order (what gets hashed)
- Index (4 bytes, big-endian)
How it works
Teleburning moves an Ethereum NFT to Bitcoin by sending it to an address derived from an inscription ID. Nobody holds a key for that address, so the token can never move again, and anyone can recompute the address to confirm which inscription it points to.
Per the Ordinal Theory Handbook, the address is the first 20 bytes of the SHA-256 hash of the inscription ID serialized as 36 bytes: the 32-byte transaction ID, then the inscription index as 4 big-endian bytes.
The byte-order trap
The transaction ID goes in reversed. Bitcoin stores txids in the
opposite byte order from the hex shown in inscription IDs and block
explorers. Hash the displayed hex directly and you get a wrong address
that looks perfectly valid. For inscription zero, the correct address
is 0xe43A…dA9e; the displayed-order mistake
gives 0x1c11…b0ef.
What leaves your browser
The derivation runs entirely in this page. If you add a collection and
token ID, those two values go to a public Ethereum RPC endpoint for
one read-only ownerOf call. There is no
wallet connection, no sign-in, and nothing to approve or sign.
On-chain verifier
The same check is deployed on Ethereum mainnet as a contract any other
contract can call, with no owner and no state:
0x58b0acCf5C68E99fA0424c0A30EAA1a6BfeaBDdC. Its source is verified on Etherscan. Call
isTeleburnedTo with a collection, token ID,
and txid in internal byte order, or
deriveAddressFromDisplayTxid with the txid
as displayed.