RenBridge redemption is verified only when a successful renBTC gateway burn links to a confirmed Bitcoin output for its intended recipient; the burn alone does not prove BTC arrived. RenBridge handled the burn and release as separate transactions on different blockchains, so a RenBridge burn receipt is just the starting record. Missing historical linkage can leave the answer inconclusive.
How do you find the successful gateway burn?
Start with the chain on which you held renBTC, your wallet address, and any transaction hash or saved redemption session. Search that chain’s transaction history in a read-only explorer. If you no longer have the hash, look around the date you attempted the redemption and follow the relevant renBTC activity to its transaction details. A saved session can help identify the attempt, but the public transaction receipt establishes what happened on that chain.
Separate the steps shown in that receipt. An approval gave a contract permission to spend renBTC; it did not redeem any. An ordinary token transfer moved renBTC on the host chain. A reverted call failed, even if your wallet displayed a redemption prompt or charged gas. For a successful redemption, identify the gateway burn in a successful transaction’s logs. The token movement alone is less useful than the gateway event, which ties the burned amount to the release request.
Record the host chain, transaction hash, gateway contract, block number, burn event or identifier, and burned amount. Recover the Bitcoin recipient from the burn’s decoded event or input data, using the contract’s historical format if the explorer displays it as encoded bytes. Copy the resulting address carefully: the Bitcoin address you remember intending to use is not evidence of the address actually submitted.
RenBridge burn and Bitcoin release were separate
A successful gateway burn started a burn-and-release operation. RenVM had to observe and process that burn, then authorize and broadcast a separate Bitcoin transaction. Bitcoin records outputs—specific amounts paid to specific addresses—rather than a change to your renBTC balance. Releases could share one Bitcoin transaction with other payouts, so the transaction hash alone does not identify which output was yours.
Consider two attempts with the same successful burn status, amount, and encoded recipient. For the first, a retained RenVM release record associates its burn with a Bitcoin transaction whose confirmed output pays that recipient. That establishes the payout. For the second, you find a similar-sized Bitcoin payment near the burn time but no record connecting it to this burn. The payment may be real, yet its timing and amount cannot establish that it fulfilled this redemption.
How do you prove the Bitcoin payout?
Use a retained release record, transaction history, or archived session that associates the burn identifier or host-chain transaction hash with a Bitcoin transaction ID. Treat that association as the cross-chain link, then inspect the Bitcoin transaction independently in a read-only explorer. Find the output paying the exact recipient encoded in the burn, and record its output index, amount, block height, and confirmations. A confirmed output is the evidence that native BTC reached that address.
Do not require the Bitcoin output to equal the burned renBTC amount exactly. Protocol and Bitcoin transaction fees affected the net release, and a batched transaction may contain several recipient outputs plus change. Compare the recorded release details and the output addressed to your recipient; a matching total transaction value or nearby timestamp proves little when other redemptions share that transaction.
An empty receiving wallet today does not undo a historical payout. Inspect the address’s transaction history for an incoming output at the release time and any later spend of that output. If the address was supplied by an exchange or custodian, the confirmed output establishes delivery to that address; whether the service credited your account is a separate question for its deposit records.
What if the historical link is missing?
Record the missing link precisely. Save the burn transaction and decoded recipient, then note whether you have a release record, a candidate Bitcoin transaction, and a confirmed recipient output. If you can see an output to the address but cannot connect it to the burn, describe it as an unlinked payment. If the address history shows no relevant output, say that no on-chain payout to the submitted address was found in the history examined.
Keep the paired transaction IDs, output index, and explorer details together when the link is established. When old RenVM or session records are unavailable, matching amounts and times may leave this specific redemption unresolved. The distinction matters: the burn proves renBTC was destroyed on its host chain, while the linked, confirmed Bitcoin output proves the historical payout.
Related questions about the old bridge
Why was the service shut down?
The original RenVM 1.0 service was sunset in 2022 after its development funding was disrupted. An audit of an earlier redemption therefore depends on historical transaction records, not on starting a new release through the old service.
Which blockchains did it support?
Bitcoin was the native chain for BTC payouts; renBTC appeared on host chains including Ethereum and BNB Chain. Support expanded over time. Use the chain shown by your burn transaction to identify where this particular attempt began.
How did it convert Bitcoin to renBTC?
For a mint, RenVM observed BTC deposited on Bitcoin and authorized renBTC to be minted on a host chain. Redemption reversed the direction: burn renBTC on the host chain, then release native BTC on Bitcoin.
How should you assess RenBridge alternatives?
For a new transfer, identify whether a route delivers native BTC or another wrapped token, which chains it supports, who controls the backing assets, and how redemption works. Those criteria tell you whether its outcome matches the one you need.
Top comments (0)