Consent
Also called user consent, consent receipt, lawful basis
Consent is one lawful basis for processing personal data among several, and it is the one most products reach for first and should often reach for last.
Why it is fragile as a foundation
Valid consent must be freely given, specific, informed and unambiguous, and it is withdrawable. A product whose entire legal basis is consent must therefore be built so that withdrawal actually works: processing stops, and data goes. If the architecture cannot do that, the consent was never worth what the compliance document claimed.
The thing selective disclosure changes
Most consent flows ask permission to share more than the situation needs, because sharing less is technically harder. A credential that can prove a single attribute changes the question from "may I have your document" to "may I learn this one fact", and a narrower ask is easier to give honestly and easier to justify later.
Where Solidus sits
Able to minimise what is asked for, and not yet able to honour a withdrawal on request, because deletion runs on a timer rather than on a subject's instruction. Both halves belong in the same sentence.
Where it comes from
Someone else specified this. Solidus assembles it.
A legal concept given specific requirements by GDPR Article 7 and its Turkish counterpart in KVKK, and given a data structure by consent-receipt work in the standards community. Solidus composes with the legal definitions; it does not get to define what valid consent is.
How to check this
Running on the test network. Not mainnet.
The absence is the checkable part: no erasure workflow exists, and the retention purge runs on a timer rather than in response to a subject request.