Beersy

Crumbs

Beered by 1 person

12 standards · 4 topics

What Crumbs writes about

Wallet

2
  • 325

    User-Initiated Browser Permission Requests for Wallet Discovery

    A web app can only find the Bitcoin wallet running on a user's own computer by poking a handful of local addresses, and newer browsers treat that poke as suspicious and interrupt the user with a security dialog that never mentions the word "wallet". If the user clicks the wrong button, nothing explains what just happened, and the browser locks out that discovery permanently for that site. This leaves developers needing a way to prepare the user before that dialog appears, so a refusal is recoverable instead of final.

    2026
  • 326

    Wallet Failure Presentation

    When a wallet request fails, today's wallets each write their own error sentence and hand it straight to the app, which has no choice but to show it to the user unchanged. That sentence rarely says whose fault the failure was, whether trying again is safe, or whether the payment might actually have gone through anyway. The result is users double-spending after a timeout, support tickets full of mismatched wording, and apps that cannot translate or shorten a message they did not write.

    2026

Peer to peer

2
  • 369

    Keyed Content and Conditional Key Release

    Imagine selling a locked box online, but the "lock" is really just a sign that says "please don't look inside" while the contents sit in plain view for anyone who peeks at the underlying data. That's how paid content has actually been built on this chain: the restriction is a polite fiction, not a real barrier. This makes it possible to actually encrypt content once, publish it openly, and hand out the key only to people who paid or otherwise qualify, so access is real, survives the seller going offline, and gets more reliable the more people buy it.

    Elon Moist, Ty Everett +12026

Applications

6
  • 168

    Verifiable Time Allocation

    Timesheets are just typed claims that nobody can check after the fact, so disputes about hours worked come down to trust in whichever party controls the record. There was no way to make a weekly time claim that was both unforgeable in its total and private until the person who made it chose to reveal part of it. This closes that gap by anchoring a fixed, 168-hour-bounded claim on chain and letting disclosure happen hour by hour, to whoever the holder picks.

    Luke Rohenaz2026
  • 190

    Access Gates for Metanet Rooms

    Letting people into a group chat or forum usually means keeping a list of names someone approved, and whoever approves them isn't the one who pays if a bad actor gets in or a good one gets shut out. Lists also go stale, can't be audited by the people they exclude, and live in whatever platform's database, so they don't travel if the room moves. This describes a way for a room to admit people based on facts they can prove about themselves, recomputed fresh every time, instead of a name written in a table somewhere.

    zer0_dt_2026
  • 210

    Derived Collectibles

    A digital collectible is normally just a picture plus a boring list of past owners nobody looks at. This standard describes a way for the picture itself to change over time and with use, so that a piece can visibly age, shift with the seasons, or wear a mark its owner chose, all computed fresh by anyone looking rather than fetched from a server.

    root, Kuro2026
  • 222

    Consent Envelope: Verifiable Multi-Party Document Signing with On-Chain Signing Order

    Signing a contract online today means trusting one company's database to say who signed, in what order, and when. If that company shuts down, gets bought, or gets compelled by a court, the "proof" you have is just whatever it says it is. This makes it possible for the proof of a signing to survive and be checked by anyone, long after the company that ran the signing is gone.

    2026
  • 300

    Sponsored Onboarding and Wallet Choice

    A visitor with no wallet lands on an app and has nowhere to go: pick the one wallet the app happens to recommend, or leave. Nobody is paying to get that person set up, so sites either force a single choice that quietly favors one vendor or lose the visitor at the install step. This describes how an app can offer a real choice of wallets and let vendors compete to fund the newcomer's first wallet, without the amount being readable or harvestable by bots.

    Siggi Oskarsson, Luke Rohenaz2026

Opinions

2

Search Beersy

Search standards by number, title, author or topic