{"blyg":"0.4","id":"52xqj1pcgh7v0hzn7216rrwme8","kind":"fragment","origin":"https://suryakasturi.com/blyg/","page":"f/52xqj1pcgh7v0hzn7216rrwme8/","author":{"name":"Surya Kasturi","url":"https://suryakasturi.com"},"created":"2026-11-11T18:32:17Z","updated":"2026-11-11T18:57:21Z","version":2,"content_md":"Digital wallets cannot easily do one thing paper wallets do: offline payments. \n\nWe could technically setup device bound wallets and asynchronously update the ledger with one-time use private keys to sign the device ledger, but there's a problem called double spending, wherein someone could restore their device to a previous state to reuse the keys. \n\nApple seems to offer select organizations to be able to write Java applets and save on tamper resistent memory but they do not confirm atomicity, rollback operations on compromised (unlocked) devices. There seems to be much broader support in Android ecosystem, but the protocol seems edgy. ","content_html":"<p>Digital wallets cannot easily do one thing paper wallets do: offline payments.</p>\n<p>We could technically setup device bound wallets and asynchronously update the ledger with one-time use private keys to sign the device ledger, but there's a problem called double spending, wherein someone could restore their device to a previous state to reuse the keys.</p>\n<p>Apple seems to offer select organizations to be able to write Java applets and save on tamper resistent memory but they do not confirm atomicity, rollback operations on compromised (unlocked) devices. There seems to be much broader support in Android ecosystem, but the protocol seems edgy.</p>\n","content_hash":"sha256:737c46e0df484ee799d33daefa520333a0573ab3b1e33ea0a241fcbda3e3b319","media":[],"changelog":[{"version":1,"at":"2026-11-11T18:56:20Z","note":null},{"version":2,"at":"2026-11-11T18:57:21Z","note":null}]}