Why a small Bitcoin deposit never became RenBridge renBTC
A Bitcoin deposit below RenBridge’s minimum was not minted into renBTC, because the deposit had to cover the mint fee and Bitcoin network costs as well as the amount being converted. The deciding measure was the value of that single deposit output against the minimum in force at the time. If it was below that threshold, confirmation alone could not make it eligible.
Could a second small deposit have made up the difference?
No: RenVM assessed each deposit output on its own, so a later top-up did not combine with the first. A Bitcoin transaction can contain separate outputs, and the relevant amount was the output sent to the deposit address, not the total of separate deposits you made over time. Two outputs that were each under the minimum therefore remained two ineligible deposits.
The minimum existed because processing a small amount could cost more in mint fees and Bitcoin network charges than the deposit was worth. The threshold could vary with those costs, so today’s fee conditions cannot establish what the minimum was for an old deposit. To assess yours, you need the amount of the specific output and reliable information about the minimum that applied then.
How can I tell a size failure from an unfinished mint?
A confirmed output below the applicable minimum, followed by no mint on the destination network, points to a size failure. RenVM controlled the deposit address’s key and used it to manage the mint, so a Bitcoin confirmation only showed that the funds reached that address; it did not show that the output qualified or that renBTC had been issued.
That distinction matters because an eligible deposit could still have been waiting on confirmations or a later step on the destination chain. If the output exceeded the minimum, size alone does not explain the missing renBTC; the cause would lie in confirmations or a skipped host-chain step. In that case, the amount clears the size test, but the intended mint remains unproven.
For a below-minimum output, RenBridge could not turn the confirmed Bitcoin into renBTC, and the sender had no private key with which to reclaim it. The deposit address belonged to RenVM’s key, not to the wallet that sent the Bitcoin. This is why a transaction can be confirmed and visible on Bitcoin while leaving no minted asset and no sender-controlled refund route.
Can the old deposit be processed or returned now?
No: RenVM’s original network has shut down, so there is no service now able to process an old below-minimum deposit or return it. A second small deposit would not have corrected the first at the time, and making another deposit now cannot restart the original mint process.
The specific evidence that would justify revisiting a size-failure diagnosis is proof that the original output exceeded the minimum in force then. That would change the likely cause from amount to an unfinished confirmation or destination-chain step, though the shutdown still means the old deposit cannot be processed through RenVM now.
Comments
Post a Comment