7 standards
Encrypting data so that only the holder of the right key can read it: the wallet calls that do it, portable encrypted message formats, and releasing a key only once some condition is met.
Also searched as decrypt, cipher, confidential, key release, sealed.
7 standards, spread across 5 of the 12 topics.
Two parties who want to exchange private data normally have to agree on a key first, and looking after that key is where most systems go wrong. This lets an application ask a wallet to encrypt something for one specific recipient without the application ever handling a key itself.
Filed under Wallet
Encryption is the main subject of these 2.
Two parties who want to exchange private data normally have to agree on a key first, and looking after that key is where most systems go wrong. This lets an application ask a wallet to encrypt something for one specific recipient without the application ever handling a key itself.
An encrypted message is only portable if the recipient can work out how to decrypt it from the message itself. This defines a self-describing container so an encrypted message can be stored or forwarded and still be opened later.
These are about something else, and deal with encryption on the way.
A file containing everything about your wallet is not something to leave lying around unprotected. This defines the encrypted wrapper around such an export, so a backup can be stored safely and restored with a password.
Revealing how two parties' keys are linked hands over something genuinely sensitive, and sending it in the clear defeats the purpose. This adds encryption around that revelation so only the intended recipient learns it.
Different proof systems will be used to back up key-linkage claims, and hard-coding one of them makes the format a dead end. This defines a container that names which proof type it carries, so new ones can be added later.
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.
A 1Sat Ordinal normally has its content sitting in plain view on the blockchain forever, which is useless for anything meant to stay private until a chosen moment or a chosen person, like an unopened collectible, a licensed file, or a credential. Before this, there was no agreed way to publish such content as encrypted data on that ordinal and later unlock it, either for everyone or for one named recipient, without putting the content back on chain again. This closes that gap so an owner can seal an ordinal once and decide later, and separately, whether the world or one person gets to read it.
Concepts that keep appearing on the same standards as this one.
Search standards by number, title, author or topic