Block —
🟠 UniSat Wallet
🔵 OP_NET Wallet
🔍 Diagnose wallets
0 Total Vaults
0 Active
0 Unlockable
— Next Unlock
5
Next Bitcoin Halving
Block #1,050,000
~162,588 blocks away · approx. 2026
Unlock Timeline
Genesis #0
Halving 4 #840,000
Now #—
Halving 5 #1,050,000
My Vaults 0
Connect your wallet to begin
Connect UniSat or OP_NET wallet to create
and manage your time-locked vaults.
Create New Anchor
Block Height
Date
Halving
Current block: loading...
Minimum: 546 sats (dust limit)
Encrypt Message
AES-256-GCM · Key shown once · Never stored
Preview
Your anchor will look like this
ID: — — — — — — — —
Your message here...
Set condition above
Wallet
Not connected
Protocol: SATANCHOR_V1
Script: P2WSH + CLTV
Network: Bitcoin Testnet
Commitment: OP_RETURN
Anchor Archive 0
Anchor ID Message Condition Status Type Network Created
⬡No vaults yet
Block —
Testnet
🟠 UniSat Wallet
🔵 OP_NET Wallet
New Message
Bitcoin testnet address (tb1...)
Stored in OP_RETURN · Permanent on-chain
0 / 80
⚠ Encryption Key — Save This!
Generating...
This key will NEVER be shown again. Without it, the message cannot be decrypted. Store it safely.
≈ 0 BTC
Fetching fee rate...
Preview
On-chain message will look like this
PUBLIC To: —
Your message here...
— sats
≈ — BTC
OP_RETURN · BITMSG_V1
Protocol: BITMSG_V1
Commitment: OP_RETURN (0 sats)
Network: Bitcoin Testnet
Encryption: None (public)
Est. total: — sats
0 Received
0 Sent
0 Public
0 Encrypted
Messages 0
Connect your wallet
Connect UniSat or OP_NET wallet to see
messages tied to your Bitcoin address.
How BitMessage Works
01
Write a Message
Choose your message type: public (readable by anyone) or encrypted (AES-256-GCM, only decryptable with your key). Up to 80 characters stored directly on Bitcoin.
02
Attach to Transaction
Your message is embedded in an OP_RETURN output alongside the Bitcoin transfer. One transaction — one payment — one permanent message on the blockchain.
03
Forever on Bitcoin
Once confirmed, the message is immutably anchored to the Bitcoin blockchain. Public messages are readable by anyone. Encrypted ones need the decryption key.
Protocol Specification
OP_RETURN Payload Format
BITMSG — 6-byte magic prefix
V1 — protocol version byte
TYPE — 0x00 = public, 0x01 = encrypted
MSG — UTF-8 message (max 73 bytes)
Notes
OP_RETURN outputs carry 0 BTC and are unspendable. They are used as a data carrier on Bitcoin.
Maximum OP_RETURN size: 80 bytes (Bitcoin relay policy).
Encrypted messages store base64-encoded AES-256-GCM ciphertext (IV + ciphertext) in the payload.
The decryption key is NEVER stored on-chain. Keep it safe or the message is lost forever.
Message Explorer
Enter a Bitcoin address to see all messages sent to it, or a TXID to inspect a specific transaction.