{"type":"rich","version":"1.0","title":"toxicbitcoiner wrote","author_name":"toxicbitcoiner (npub1u8…m93f7)","author_url":"https://yabu.me/npub1u87g378r0puytp7zxdl5awg2gmqvqc3vgtnh6a0vfgm4y8es7c3qam93f7","provider_name":"njump","provider_url":"https://yabu.me","html":"What appears on Bitcoin:\n- A standard Bitcoin transaction\nBTC sent to a federation-controlled multisig address\n- Often includes a small metadata commitment (via OP_RETURN) referencing the peg-in claim on Liquid.\nWhat it proves:\n- BTC has been locked on Bitcoin\nA corresponding amount of L-BTC is issued on Liquid.\nWhat is not stored on Bitcoin:\n- Liquid transaction details\n- Liquid addresses\n- Confidential amounts or assets on Liquid\n\nIs this okay with you then or no? The issue could be the opreturn for peg-ins, which is typically ~36–40 bytes."}