Proof-first, not record-first
Documented architectureAn integrator's primary artefact is the proof object, not a row in someone's database. Holding the proof is what lets you verify later without asking us.
Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.
Builders
What integrating with ByteShares is intended to look like. There is no endpoint to call, no package to install, no key to obtain and no sandbox to register for. Everything below is a model you can review and argue with, not something you can run.
Not live
The developer platform is not operating. Nothing on this page reports real activity, and no operational figures are shown, because no verified operational data source exists yet.
No base URL, hostname, package name or credential appears anywhere on this page. Any that you encounter elsewhere claiming to be ByteShares did not come from us.
Proposed / Non-operational: identity → scoped authority and rule context → decision outcome → evidence → bounded closure.
eIDspot describes identity/access; governance defines bounded mandates; VPLedger describes proof/evidence/audit relationships; nodes and DLT remain planned. AI City applications are intended consumers of this architecture, not deployed services. Cooperative membership and one-member-one-vote belong to ByteShares.dk; a ProductCo or application does not inherit cooperative authority.
Historical source editions describe earlier designs. Proposed models remain unadopted; the live documentation site is not evidence of a running DLT. Documentation 0.9 RC1, Proposed Canon v0.1 and historical paper editions are separate version contexts. “Last reviewed” records documentation review, not implementation acceptance.
Ask about documented architecture and readiness; answers cite the pages they draw from and do not verify a running platform.
Ask the documentation →The intended integration surface is narrow on purpose. A client presents identity and authority, submits an intent, and receives a proof object describing what the protocol did and under which rule version. Reads return accepted state and the evidence needed to check it independently.
An integrator's primary artefact is the proof object, not a row in someone's database. Holding the proof is what lets you verify later without asking us.
An API is a convenience over accepted state. If it disagrees with the protocol record, the protocol record is correct.
01
Obtain a verified identity and the mandate that scopes what you may do. Mechanism not yet specified.
02
Express the action, its inputs and the authority under which it is taken.
03
Present the intent with its proofs to an admission surface for rule evaluation.
04
Success or refusal both produce a verifiable record of what was evaluated.
05
Store the proof; verify inclusion against a later epoch snapshot without trusting any interface.
No step above can be performed today. The sequence is published so it can be reviewed before it is implemented.
| Concept | Intended behaviour | State |
|---|---|---|
| Client identity | Bound to a verified subject, not to an anonymous API key. | To be specified |
| Mandate | Explicit scope, issuer and validity period for what a client may do. | Documented concept |
| Delegation | An agent may act within a narrower scope than its principal, never wider. | Documented concept |
| Session | Short-lived and non-authoritative; authority always re-checked at evaluation. | To be specified |
| Revocation | Immediate effect on subsequent evaluation, with prior proofs remaining valid for their time. | To be specified |
Every interaction is expected to resolve to a proof object. Its fields conceptually cover the subject, the authority, the rule version, the inputs committed to, the outcome and the anchoring reference. The exact serialization, schema and hash construction are to be specified and are deliberately not invented here.
Proposed / Non-operational — conceptual relationships, not a finalized object schema.
| Concept | Relationship in the documented model | Boundary / requires source |
|---|---|---|
| Subject and credential | A subject presents identity or eligibility evidence issued within a defined scope. Identity alone does not authorize an action. | Credential format, issuer trust and verification method: TBD / Requires source. |
| Authority and mandate | A mandate links an issuer, subject, permitted scope and validity period. An agent's delegated scope must not exceed its principal's. | Mandate serialization and delegation checks: TBD / Requires source. |
| Intent and inputs | An intended action references the subject, applicable authority and inputs to be evaluated; inputs may be committed without exposing underlying material. | Input encoding, commitment construction and admission rules: TBD / Requires source. |
| Governance and rule version | Governance establishes the applicable roles, thresholds and rule context; evaluation should reference that context rather than infer authority from a client session. | Decision procedures, exception handling and rule-version format remain unspecified. |
| Outcome and proof object | The intended evaluation produces evidence linking subject, authority, rule version, committed inputs and outcome, including refusal. | No implemented evaluator, final proof schema or error vocabulary is verified. |
| Proof and snapshot | A retained proof's anchoring reference is intended to support inclusion checking against an epoch snapshot. | Snapshot format, hash/signature scheme and trust establishment remain unspecified. |
Supporting documentation: Identity / eIDspot · Governance Layer · VPLedger.
| Surface | Intended purpose | Status |
|---|---|---|
| Submission | Present an intent with proofs for rule evaluation. | Planned; not built |
| Proof retrieval | Fetch a proof object by its reference. | Planned; not built |
| Inclusion verification | Check a record against an epoch snapshot root. | Planned; not built |
| Governance read | Read authorized decisions and rule versions. | Planned; not built |
| Public evidence lookup | Explorer-style queries over disclosable records. | Planned; not built |
Surface names describe function. They are not paths, and no path structure is published.
Proof construction and verification, authority presentation, snapshot inclusion checks, and typed models of protocol objects.
Key custody, wallet UI and membership or payment flows. The last of those belongs to ByteShares.dk, not here.
Not decided. No package name, registry entry or version is reserved or claimed.
A stated goal: verification of a retained proof should not require a call to any ByteShares service.
Proposed / Non-operational — responsibility boundaries only, not library modules or package contracts.
| Responsibility | Existing model | Decision boundary |
|---|---|---|
| Authority presentation | Subject, credential and mandate chain | Present scoped evidence; key control or a session must not create authority. Encoding and issuer/status checks require specification. |
| Proof construction and interpretation | Inputs, authority, rule context and outcome | Preserve the intended bindings, including refusal; no finalized schema, hashing or signature profile is assigned. |
| Snapshot inclusion checking | Epoch closure and authorized decisions | A historical check needs a trusted root and time/rule context; it must not imply current eligibility or evidence truth. |
| Exclusions | Custody and authorization boundaries | No key custody, wallet UI, cooperative membership/payment or authority issuance is delegated to this conceptual SDK. |
Languages, typed representations, packages, verifier source and test vectors remain TBD / Requires source.
Proposed / Non-operational — reading aids only, not JSON fields, endpoint payloads, executable examples or implementation contracts.
| Request concept | Illustrative content | Not yet specified |
|---|---|---|
| Identity presentation | Evidence of the subject making the request. | Credential encoding and issuer validation. |
| Authority presentation | Mandate, permitted scope and any narrower delegation relevant to the intent. | Mandate format, revocation freshness and authority checks. |
| Intent and inputs | The action sought and the inputs or commitments evaluated under an applicable rule context. | Action vocabulary, serialization and commitment construction. |
Proposed / Non-operational response shape — no response is produced by an operating ByteShares DLT service.
| Response concept | Illustrative content | Not yet specified |
|---|---|---|
| Evaluation outcome | Acceptance or refusal tied to the rule version considered; refusal should explain the evaluated failure without unrelated disclosure. | Outcome vocabulary, refusal codes and disclosure rules. |
| Proof context | Subject, authority, committed inputs and applicable rule version associated with the result. | Final schema and signature scheme. |
| Anchoring reference | A reference intended to connect retained evidence to a later epoch snapshot for inclusion verification. | Reference format, snapshot construction and proof encoding. |
These shapes restate the existing proof-object model; they assign no field names, types, cardinalities or wire format. All unspecified details are TBD / Requires source.
Proposed / Non-operational — no verifier, test vector or successful offline result is claimed.
The documented goal is to retain a proof and check its inclusion against an epoch snapshot without calling a ByteShares service. This requires more than retaining an interface response.
Revocation and time semantics need a specification: an offline historical check must not be represented as proof of current eligibility. See snapshot and evidence boundaries, credential lifecycle and security requirements.
01
Read the documented model and raise gaps while it is still cheap to change.
02
Integration requires an authorized mandate, granted through governance rather than self-service.
03
An integration demonstrates that it constructs and verifies proofs correctly.
04
Integrations run against a published contract version with a stated support window.
05
Contract changes follow the versioning policy below, with notice before removal.
A refusal is expected to be as verifiable as an acceptance: it should state the rule version applied and why the evaluation failed, without disclosing unrelated data. Concrete codes, categories and payload shapes are to be specified.
| Element | Intended policy | State |
|---|---|---|
| Contract versioning | Explicit version on every interface and proof object. | Framework agreed; scheme not assigned |
| Breaking change | New version rather than mutation of an existing one. | Framework agreed |
| Deprecation notice | Announced period before removal, published in advance. | Period not set |
| Rule-version reference | Every proof names the rule version under which it was evaluated. | Documented concept |
| Historic verification | Old proofs remain verifiable after the contract moves on. | Requirement; unimplemented |
Proposed / Non-operational — policy framework, not assigned codes, versions or support commitments.
Awaiting GitHub connection. No repository is linked, named or implied, and the VPLedger source provenance audit is still open.
Publication follows a twelve-gate readiness process covering source inventory, integrity hashes, provenance classification, exclusion of sensitive material, licensing review, canonical repository mapping, build baseline, version baseline, documentation baseline, owner approval, import verification and future source/operational acceptance. The documentation site domain and public indexing are already active. A developer-docs repository is proposed for this material, and an sdk repository only if a distinct verified SDK codebase is found. Both remain proposals with no source accepted.
Proposed / Non-operational — review questions, not decisions or implementation contracts.
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 |
|---|---|---|---|
| Interaction model, surfaces and lifecycle | Interface drafts | Source claimed, not yet verified | Relationships, illustrative shapes and offline-verification intent restate existing identity, governance and VPLedger documentation. No implementation checked and no verification state upgraded. |
| Proof-object schema, error codes and SDK contents | Specification | No source on file | Conceptual shapes are not finalized schemas. Serialization, hashing, signature schemes, revocation semantics, trust establishment and verifier test vectors require source. |
| Endpoints, packages, keys or sandboxes | Running service | No source on file | None exist; none are published. |