{"type":"rich","version":"1.0","author_name":"npub136rmper0tszp8xxttyzsa27tjrvx36drtpucg0544mq8cxlha6wshgpezn","author_url":"https://nostr.ae/npub136rmper0tszp8xxttyzsa27tjrvx36drtpucg0544mq8cxlha6wshgpezn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2023-05-24\n🗒️ Summary of this message: 0-conf transactions are risky due to the possibility of double-spending, but Ark may use an opcode to prevent this. Lightning payments can still be made with zero-conf coins.\n📝 Original message:\u003e 0-conf transactions are unsafe since it is possible to double-spend the inputs they consume, invalidating the 0-conf transaction.\n\nA future extension of Ark can potentially utilize a hypothetical data manipulation opcode (OP_XOR or OP_CAT) to constrain the ASP's nonce in their signatures to disincentivize double-spending. If a double-spend occurs in a pool transaction, users can forge ASP's signature to claim their previously redeemed vTXOs. This is effectively an inbound liquidity-like tradeoff without compromising on the protocol design.\n\nFor the time being, you have to wait for on-chain confirmations to consider a payment 'final'. However, this doesn't prevent you from paying lightning invoices with your zero-conf coins. Ark has immediate availability with delayed finality.\n\nBest,\nBurak"}