Check a Liquid peg-in candidate without broadcasting the claim
An operator can assemble a claim candidate from a Bitcoin deposit before deciding whether the deposit is mature enough to proceed. This separates bad proof data from later signing or relay failures.
Construct using the original deposit evidence
Use the raw Bitcoin transaction, a parent-chain gettxoutproof containing only that transaction, and the claim script committed to by the deposit address. The Elements call builds an unsigned raw transaction. The example displays only presence of transaction hex.
elements-cli createrawpegin "$BTC_TX_HEX" "$BTC_PROOF_HEX" "$CLAIM_SCRIPT" | jq '{has_hex: has("hex"),mature}'
Interpret the optional maturity field
When peg-in validation is enabled, mature indicates maturity at the node's observed parent-chain state. A missing field does not imply either success or failure of that check. A true value still does not mean that the sidechain transaction was signed, relayed or included. Track those steps independently.
elementsproject.org createrawpegin · elementsproject.org getpeginaddress