š
Original date posted:2014-03-23
š Original message:I know that general approach to interaction design in Bitcoin assumes
minimal to no difference between payer and payee, and generally I agree
with this approach.
However, for the sake of my PoS development this assumption is wrong by
default, as PoS is a specialized hardware, and one who cared to buy and
install it is probably not in the same situation as the other party that
didn't care to by anything dedicated.
In short - from PoS point of view there is a customer and a merchant. And
my goal is to make thing work in assumption of fast and reliable connection
on merchant side and no connection requirement at all from customer side.
I didn't put a silly example, as of my experience there are really a lot of
places where cellphone connection isn't good enough for reliable Bitcoin
operation. However, if we're talking about merchant establishments - we can
hope for private local WiFi or wired connection on PoS side, so PoS
internet connection shouldn't be an issue. So this is the use case I'm
designing around and this is why bluetooth based BIP70 implementation is
important for me.
I partly agree with Mike on user interface and IOU idea, but I have no
intention to implement anything like that right now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140323/de4912b2/attachment.html>;
Alex Kotenko [ARCHIVE] /
npub14jā¦h00t4
2023-06-07 15:14:22
in reply to nevent1qā¦z433
Author Public Key
npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4Published at
2023-06-07 15:14:22Event JSON
{
"id": "5d1c1a4b48684ccc2cb769dd2211325f9b8415dab54de704f5f79fd3bd274690",
"pubkey": "ac99e5ca3122fca258fbfcb6cb62d10d4dba423b3243251cbc0c4e0042656dec",
"created_at": 1686150862,
"kind": 1,
"tags": [
[
"e",
"d70d8d12a406cb1c9a067111bb9c717b35fd85b951e12f89e562fccc2fad4277",
"",
"root"
],
[
"e",
"3dc982cde0ad3cc382148a2c51ddccd6f3ea430f58b2b8f1a87bdbd5abd53fc6",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "š
Original date posted:2014-03-23\nš Original message:I know that general approach to interaction design in Bitcoin assumes\nminimal to no difference between payer and payee, and generally I agree\nwith this approach.\nHowever, for the sake of my PoS development this assumption is wrong by\ndefault, as PoS is a specialized hardware, and one who cared to buy and\ninstall it is probably not in the same situation as the other party that\ndidn't care to by anything dedicated.\n\nIn short - from PoS point of view there is a customer and a merchant. And\nmy goal is to make thing work in assumption of fast and reliable connection\non merchant side and no connection requirement at all from customer side.\n\nI didn't put a silly example, as of my experience there are really a lot of\nplaces where cellphone connection isn't good enough for reliable Bitcoin\noperation. However, if we're talking about merchant establishments - we can\nhope for private local WiFi or wired connection on PoS side, so PoS\ninternet connection shouldn't be an issue. So this is the use case I'm\ndesigning around and this is why bluetooth based BIP70 implementation is\nimportant for me.\n\nI partly agree with Mike on user interface and IOU idea, but I have no\nintention to implement anything like that right now.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140323/de4912b2/attachment.html\u003e",
"sig": "0cc1ec91dfa2d9dfac0f69a3fee15565bc33a664b187ea62dd2112f77332f16e7c1bc33a0bb43b7339ed98faedebb0816f3b6be4cd43f888b01617d7545802f8"
}