Claim Without bc1q21

Smart Contract Giving, powered by bc1q21.com

A Smart Contract Gift is not stored inside bc1q21.com.

The Bitcoin and the time-lock rules live directly on the Bitcoin blockchain.

bc1q21 is a convenience tool that makes creating and claiming gifts easier, but it does not hold Bitcoin, control user funds, or store seed words.

If bc1q21.com disappeared tomorrow, a gift could still be recovered after the release date using the original 12 seed words, public blockchain data, and standard Bitcoin transaction tools.

This page explains that recovery process at three different levels:

• Everyday User Recovery Process
• Professional Recovery Process
• Complete Real-World Recovery Example

1. Everyday User Recovery Process

“How to Recover Gift Without bc1q21”
for Average Bob/Betty (Everyday User Recovery Process)

A gift can be claimed using only the 12 seed words, even if the gift card or QR code has been lost or bc1q21.com is no longer in operation.

The Bitcoin contained in a Smart Contract Gift is not stored inside bc1q21.com. The funds and time-lock rules live directly on the Bitcoin blockchain.

AFTER THE RELEASE DATE HAS PASSED, the recovery process is:

1. Use the 12 seed words to recreate the original Bitcoin keys.
2. Find the related blockchain transactions.
3. Locate the time-locked contract address.
4. Recover the on-chain contract information.
5. Rebuild and sign the release transaction.
6. Broadcast that transaction to the Bitcoin network.
7. Send the Bitcoin to a wallet address you control.

This is not a simple “click one button” process. It is technical. But it is absolutely doable.

We have already successfully tested this exact process using only the 12 seed words, public blockchain data, and Bitcoin transaction tools. No bc1q21 backend, server, QR code, or gift card is required.

In plain English: the 12 seed words are the key. The blockchain contains the rest of the information. A Bitcoin-knowledgeable person, or someone guided carefully by ChatGPT or another AI tool, can recover the gift after the unlock date.

2. Professional Recovery Process

“How to Recover Gift Without bc1q21”
for Professionals (Coder to Coder)

Time-Locked Smart Contract Gifts are not stored “inside” bc1q21.com. The funds and time-lock conditions exist directly on the Bitcoin blockchain itself.

bc1q21 simply makes the creation and claiming process easy and user-friendly.

Coder to coder, the recovery process is straightforward:

The funds are locked in a Bitcoin P2SH address with three requirements that must be satisfied before the funds can be spent:

1. The unlock date/time must have been reached.
2. You must have access to the redeem script used to create the address (this information is encoded on-chain in the OP_RETURN data).
3. You must have the correct private key / seed phrase controlling the address.

Once those three conditions are met, a technically capable Bitcoin developer can rebuild, sign, and broadcast the release transaction directly to the Bitcoin network without needing bc1q21.com to exist.

In simple terms:

The website is a convenience tool. The actual Bitcoin and time-lock logic live permanently on the Bitcoin blockchain.

3. Complete Real-World Recovery Example

The following is the complete real-world recovery example from the successful manual redemption test.

This process was completed using only the original 12 seed words, public blockchain data, publicly accessible bc1q21 frontend logic, and Bitcoin transaction inspection tools.

No bc1q21 backend, server, QR code, gift card, or normal website claiming function was used.

Redeeming a bc1q21 Smart Contract Gift WITHOUT bc1q21.com

IMPORTANT

These notes are for personal archival and educational purposes only.

This process was successfully completed manually using:

• ONLY the 12 seed words
• Public blockchain data
• Publicly accessible bc1q21 frontend logic
• Bitcoin transaction inspection tools

No bc1q21 backend, server, QR code, or website functions were used during redemption.

OBJECTIVE

Redeem a bc1q21 Smart Contract Gift manually if:

• bc1q21.com no longer exists
• The QR code is gone
• The gift card is lost
• No TXID is known
• No wallet address is known
• No release date is known
• ONLY the 12 seed words remain

WHAT WAS PROVEN

The following was successfully completed manually:

1. Rediscovered the funding wallet from the seed words
2. Located the funding transaction on-chain
3. Located the smart contract creation transaction
4. Located the P2SH time-lock contract address
5. Extracted the OP_RETURN recovery payload
6. Decrypted the OP_RETURN payload
7. Reconstructed the redeem script
8. Built a raw Bitcoin transaction manually
9. Signed the transaction manually
10. Broadcast the transaction directly to the Bitcoin network
11. Received confirmed Bitcoin into a new receiving address

TOOLS USED

Website Used

https://mempool.space

Specifically:

• Address explorer
• Transaction explorer
• Raw transaction hex viewer
• Transaction broadcaster

STARTING INFORMATION

ONLY the following was initially available:

The 12 Seed Words

Original seed phrase omitted for security best practices.

STEP 1 — VERIFY THE WORDS ARE VALID BIP39

Confirm the 12 words are legitimate Bitcoin BIP39 seed words.

Result:

• The words were valid.

This confirms that the phrase can deterministically derive Bitcoin keys.

STEP 2 — DERIVE THE FUNDING ADDRESS

The bc1q21 frontend logic was inspected.

Important discovery:

• bc1q21 derives the funding address from the seed.
• The derivation path used was:

m/84'/0'/0'/0/0

Using the seed words, the derived funding address was:

bc1q45w9p0g5shtltw0jxrcvptdep337h4wh0rg2cz

STEP 3 — SEARCH THE BLOCKCHAIN FOR THE FUNDING ADDRESS

Open:

https://mempool.space/address/bc1q45w9p0g5shtltw0jxrcvptdep337h4wh0rg2cz

This revealed:

• Incoming funding transaction
• Outgoing smart contract creation transaction

STEP 4 — IDENTIFY THE FUNDING TRANSACTION

Funding TXID discovered:

57845bc7acc06385047d57d6ba43b5c2bd6ecb4c64a5ed6208a428fdba9b2cde

This transaction funded the derived wallet address.

STEP 5 — IDENTIFY THE SMART CONTRACT CREATION TRANSACTION

Outgoing contract TXID discovered:

b9a10edd4faf53d74027010eba7cf03b2040041979f45b167c08d48a812d8bfe

This transaction:

• Created the P2SH time-lock contract
• Included an OP_RETURN output

STEP 6 — IDENTIFY THE P2SH CONTRACT ADDRESS

Inside the contract transaction outputs, the following P2SH address was found:

32nSGLXgiWBurycQjUXhXoVCMVsqm8nY3c

This was the actual time-locked contract holding the Bitcoin.

STEP 7 — IDENTIFY THE OP_RETURN OUTPUT

Inside the same transaction, an OP_RETURN output existed.

This matched Edgar's explanation that recovery metadata was encoded on-chain.

STEP 8 — VIEW THE RAW TRANSACTION HEX

Open:

https://mempool.space/api/tx/b9a10edd4faf53d74027010eba7cf03b2040041979f45b167c08d48a812d8bfe/hex

The raw transaction hex revealed:

53616c7465645f5f

Decoded ASCII:

Salted__

This is the standard OpenSSL encrypted payload marker.

Critical discovery:

• The OP_RETURN payload was encrypted.

STEP 9 — DETERMINE THE ENCRYPTION MODEL

By inspecting bc1q21 frontend logic, the following was determined:

• The OP_RETURN payload uses encrypted recovery metadata.
• The decryption key is derived deterministically from the seed phrase.
• The blockchain itself contains the recovery package.

The process effectively became:

seed words
→ derive AES key
→ decrypt OP_RETURN payload
→ recover redeem script
→ spend P2SH contract

STEP 10 — RECOVER THE AES KEY ADDRESS

Using the seed-derived logic, the following AES-related address was derived:

bc1q8suf7rspze76d9p8u6sp5f2m30qjxgsvj3h02v

This was used as part of the decryption process.

STEP 11 — DECRYPT THE OP_RETURN PAYLOAD

The encrypted OP_RETURN payload was successfully decrypted.

Recovered information included:

• Unlock Date: 2026-04-15
• Redeem Script: 0400d5de69b17521021f4b545e3a308da9862d1972ac79152f19930de3b8ac40bd25663611c262c1e6ac
• Reconstructed P2SH Address: 32nSGLXgiWBurycQjUXhXoVCMVsqm8nY3c

The reconstructed P2SH address matched the live blockchain contract address exactly.

This confirmed the recovery process was working correctly.

STEP 12 — CREATE A NEW RECEIVING ADDRESS

A normal Bitcoin receiving address controlled by the redeemer was created.

Receiving address used:

bc1qpslvteq5hrtp9k9vprsq9r7ztuvzu7dj756nep

STEP 13 — BUILD THE MANUAL RELEASE TRANSACTION

A raw Bitcoin transaction was manually constructed.

The transaction:

• Spent the P2SH contract output
• Sent funds to the new receiving address
• Included a mining fee
• Included the reconstructed redeem script
• Included the proper signature

STEP 14 — BROADCAST THE RAW TRANSACTION

Open:

https://mempool.space/tx/push

Paste the raw signed transaction into the broadcast window.

Click:

Broadcast Transaction

STEP 15 — CONFIRM THE TRANSACTION

After broadcast:

• mempool.space returned a TXID
• Transaction entered the mempool as "Unconfirmed"
• Shortly afterward the transaction confirmed successfully
• Bitcoin arrived in the receiving wallet

Final redemption TXID:

16cf7d57b7bbe8cca23d27c2b8000432da078fb08df5821b3ef84bfefe95366f

FINAL RESULT

The Smart Contract Gift was successfully redeemed manually WITHOUT bc1q21.com.

The process required:

• the 12 seed words
• public blockchain data
• understanding of Bitcoin transactions and scripts
• inspection of public frontend logic

No backend systems were required.

IMPORTANT CONCLUSION

This does NOT mean the average person could manually redeem a bc1q21 gift.

However, this test strongly demonstrated that a competent Bitcoin engineer can independently recover and redeem a bc1q21 Smart Contract Gift directly from the Bitcoin blockchain and the original 12 seed words — even if bc1q21.com disappeared permanently.

---

Important:

This example does not mean the average person is expected to manually recover a gift on their own.

It does demonstrate that Smart Contract Gifts created using bc1q21 are not dependent on the continued operation of bc1q21.com.

The Bitcoin remains on the Bitcoin blockchain, and the original 12 seed words remain the most important recovery information.

Protect your seed words carefully.