SCOPED SHARING
Share one file without
handing over everything.
Give a named person read access to a single encrypted object, enforced by the protocol rather than promised in a policy, and revoke it whenever you want. Your master key never moves.
1
OBJECT AT A TIME
0
MASTER KEYS HANDED OVER
YES
REVOCABLE
THE GAP IT CLOSES
Public ledgers force all or nothing.
On a standard public ledger you either expose an object to everyone or you keep the keys and can't share it at all. There's no native way to say that one named party may read one specific thing.
That gap is the reason valuable records have stayed off these systems entirely. Not because encryption was missing, but because selective disclosure was.
HOW IT'S DONE
Permission as a protocol primitive.
Access is granted to a named party against a specific encrypted object, and it's enforced where the data lives rather than by an application that could be bypassed. Revoking it removes the access rather than asking an application to stop showing it.
In practice, a patient can open one scan to one clinic, a company can hand an auditor one contract and take it back when the audit ends, and a graduate can prove a degree without showing the rest of the record.
WHAT THIS ENABLES
