{"type":"rich","version":"1.0","author_name":"npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","author_url":"https://nostr.ae/npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-06\n📝 Original message:Hi Mike\n\n\nNot sure if you've seen it, but here is how we do NFC right now\nhttp://www.youtube.com/watch?v=DGOMIG9JUY8 with XBTerminal.\nFor now this is just an NDEF URI message with Bitcoin URI inside, and then\ntransaction itself propagated to the network by the phone using it's own\nInternet connection. Far not ideal, but even this is supported only by\nAndreas' Wallet, so we cannot move ahead alot really until other wallets\nwill have some support in this area.\nAs you see - it's taking just few seconds, most of which is manual payment\nconfirmation. Btw, ignore my first screen tap, where I'm selecting wallets\n- it's an unlikely thing to happen IRL to have several wallets installed at\nthe same time.\n\n​Also, I think many people may not know about Oyster cards, so this might\nneed little bit of explanation. And btw, have you been to London lately?\nOyster readers now accept contactless cards directly along with Oyster\ncards itself. I wonder if eventually in future we could add bitcoin support\ninto that system directly, without hardware replacements.\n\nI cannot put much into the actual protocol discussion, but I'm happy to\nprovide feedback on the side of actual POS implementation needed and\ntestbase if required.\n\nHave an ​idea - it's a good thing to cap confirmationless payments, but the\nactual cap value definition can be tricky considering Bitcoin volatility.\nInless you want to tie it to some external price definition thirdparty\nservice it could be tied to transaction fees. I mean - if with Bitcoin v0.9\ntransaction fees will become really floating, and it should eventually\nreach equilibrium that will reflect some real world value. Probably a tiny\nvalue, but probably also rather stable value. So confirmationless payment\ncap may be defined as \u003ccurrent_average_transaction_fee\u003ex10000.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140306/38cc0863/attachment.html\u003e"}