Minimum disclosure
Documented architectureA verifier receives a decision-relevant proof, not a document set.
Layers
Identity Layer / eIDspot
Documented architecture
eIDspot is the working name for the identity concept in the ByteShares architecture. This page records the concept as written. No identity service exists, none is issuing or verifying credentials, and no personal data is processed by this platform.
- Source / verification
- Owner-asserted canon; credential formats not specified
- Document version
- Not yet assigned
- Last reviewed
- 19 September 2026
Concept as documented
The identity layer holds a subject identifier and a set of credentials that can be presented as proofs, so a participant can demonstrate an attribute without disclosing the underlying record. Presentation is selective: a verifier receives the minimum needed for the decision at hand.
The identifier, the credential issued about it, and the presentation made from that credential are kept distinct. That separation is what allows a credential to be reused without re-exposing its contents.
Subject classes
| Class | What identity establishes | State |
|---|---|---|
| Verified human | A natural person whose verification was performed by a named issuer. | Documented; issuer model undecided |
| Institution | An organisation, its representatives and the limits of their mandates. | Documented |
| Contributor | A participant whose contribution is recognised under a defined scope. | Documented |
| AI-adjacent agent | An agent acting under a named curator and a bounded authority, per the F.I.P. concept. | Planned; specification unavailable |
Identity to evidence
Documented architecture
01
Identity
A verified subject exists and can be referenced without re-disclosing its source records.
02
Mandate
An authority is granted to that subject, with an explicit scope, issuer and validity period.
03
Policy
Rules determine which mandates permit which actions under which conditions.
04
Action
The subject acts, presenting only the proofs the rule requires.
05
Evidence
A proof object records who acted, under which mandate and rule version, and with what outcome.
Credential and verification lifecycle
| Stage | Intended behaviour | State |
|---|---|---|
| Verification | A named issuer verifies an attribute against its own evidence. | Issuer model undecided |
| Issuance | A credential is issued to the subject, held by the subject. | Format not specified |
| Presentation | A scoped proof is derived for a specific decision. | Format not specified |
| Renewal | Validity periods expire and are renewed rather than assumed permanent. | Policy not set |
| Revocation | Status becomes checkable and immediate for later evaluations, while prior proofs remain valid for their time. | Planned; mechanism undecided |
Privacy and data minimization
Custody stays with the source
Documented architectureUnderlying identity evidence remains with its custodian and is not published to any ledger.
No correlation by default
PlannedAvoiding cross-context linkability is a stated goal; the mechanism is undecided.
Account and key
Documented architectureAn account is the subject of record; a key is a control mechanism. Key rotation must not change the subject, and wallet-as-account never means a bare address grants entitlement.
Relationship to VPLedger and governance
The identity layer supplies subject, eligibility and delegated-authority proofs; governance grants and withdraws mandates; the ledger records what was accepted and under which authority. Each keeps its own responsibility: identity never decides policy, and the ledger never grants authority.
Boundaries
- No sign-in exists on ByteShares.org. Member sign-in belongs to ByteShares.dk.
- No credential issuance, revocation or verification is running.
- No conformance with any national or EU identity scheme is claimed; such alignment would require formal assessment first.
Open questions
- Credential format
- Not decided
- Revocation mechanism
- Not decided
- Issuer model
- Not decided
- Key custody
- Not decided
- External assessment
- Not started
- Operational service
- None
Evidence register
Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.
| Claim | Source type | Verification | Note |
|---|---|---|---|
| eIDspot is the name of the identity concept | Owner instruction | Verified source on file | Name provided by the project owner. |
| Subject classes, mandate chain and lifecycle model | Master Business Plan v2.1 / aligned canon | Source claimed, not yet verified | Owner-asserted; the cited document has not been supplied for inspection. |
| Credential and revocation formats | Specification | No source on file | Marked to be specified rather than invented. |
| Compliance with any identity regulation or scheme | Formal assessment | No source on file | No assessment has taken place; no compliance is claimed. |