Beersy

4 standards

Risks and limitations

The documents whose job is to say what breaks: the limits of a scheme, the risk of depending on one interface, the cases a format does not cover, and the clarifications that exist because people assumed wrongly.

Also searched as limitation, risk, threat model, security analysis, criticism, caveat, withdrawn.

Filed under

4 standards, spread across 3 of the 12 topics.

Start with

BRC-151

BRC-100 Risk Assessment and Best Integration Practices

A single interface every application uses is convenient, and convenience is how ecosystems end up depending on one provider. This names the risks honestly and gives implementers practical ways to avoid them.

Filed under Opinions

Standards about this

Risks and limitations is the main subject of this one.

Standards that touch it

These are about something else, and deal with risks and limitations on the way.

  • 18

    Pay to False Return

    The blockchain can carry data as well as money, but data has to be attached to an output nobody can spend. This defines how to write such an output and the practices to follow when putting data in one.

    No author credited2023Scripts
  • 234

    A Shared Schedule for Reducing Free Blockchain Index Coverage

    Free blockchain explorer lookups (finding a transaction or checking an address's history by typing its ID) feel like a permanent utility, but someone pays in storage, bandwidth and recovery costs for every address and transaction they index forever. Apps and wallets that rely entirely on a provider's free lookups have no warning if that provider decides to narrow what it indexes for free, and no shared playbook for what "narrower" would even mean. This proposal gives providers a common, predictable schedule for shrinking free coverage, so apps can plan ahead instead of being surprised.

Usually read alongside

Concepts that keep appearing on the same standards as this one.

Was this helpful?

Search Beersy

Search standards by number, title, author or topic