📅 Original date posted:2023-05-24
🗒️ 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.
📝 Original message:> 0-conf transactions are unsafe since it is possible to double-spend the inputs they consume, invalidating the 0-conf transaction.
A 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.
For 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.
Best,
Burak
Burak Keceli [ARCHIVE] /
npub136…gpezn
2023-06-07 23:21:53
in reply to nevent1q…2u49
Author Public Key
npub136rmper0tszp8xxttyzsa27tjrvx36drtpucg0544mq8cxlha6wshgpeznPublished at
2023-06-07 23:21:53Event JSON
{
"id": "cde3689df64a1f7d86ce1e02f7292eb8b8d75a60cc9897f82ffc074fd356c9d4",
"pubkey": "8e87b0e46f5c041398cb59050eabcb90d868e9a35879843e95aec07c1bf7ee9d",
"created_at": 1686180113,
"kind": 1,
"tags": [
[
"e",
"e32c7f103abd16fde90ee98ca26651bd467d7c8d2ac01ef385cc5a044f4c88f6",
"",
"root"
],
[
"e",
"853e3ac3ba0a6c66cecacad37266189a2339123728362910d44426166e01eb20",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 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",
"sig": "885d4da134a65b1c4ceeae6c5350e7ef617cb81bf014bc7a5251d2a19e958a1960001a861da30085bb1f7cd2bbc8c25a67852bf08f7446f9469ff8d684f73dcc"
}