9f7566927c
All checks were successful
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
no-vanity-metrics / WAI public text names no comparison (pull_request) Successful in 4s
no-vanity-metrics / WAI public text names no company or product (pull_request) Successful in 4s
standards workspaces build + test / arl-rs (pull_request) Successful in 1m13s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m58s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m30s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m11s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m11s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m13s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m19s
standards workspaces build + test / sense-rs (pull_request) Successful in 1m7s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m50s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 28m1s
standards workspaces build + test / aac-rs (pull_request) Successful in 5m42s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 10m13s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 5m35s
standards workspaces build + test / map-rs (pull_request) Successful in 7m25s
standards workspaces build + test / mesh-rs (pull_request) Successful in 4m18s
standards workspaces build + test / openpay (pull_request) Successful in 16m8s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m15s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 7m53s
arl-rs, eoc-rs, smart-byte-rs and joule-ui-rs declare license = "Apache-2.0" in every crate, but each standard carried only its CC-BY-4.0 LICENSE for the specification text. Each Rust workspace now carries the Apache-2.0 text, and each README names both licences and where they live. jouleclaw's README pointed spec text at a spec/LICENSE that does not exist; it now points at LICENSE-SPEC. No licence changes: every file already declared these terms. Co-Authored-By: Claude Opus 5.5 <[email protected]>
27 lines
2.8 KiB
Markdown
27 lines
2.8 KiB
Markdown
# Smart Byte
|
||
|
||
A carrier for value. Settlement-agnostic, energy-attributed, no off switch.
|
||
|
||
The smart byte is not money — it is a **vesicle** (the cellular-biology sense): a content-addressed, signed envelope carrying exactly five things — identity (the blake3 hash of its origin attestation), provenance (the issuer's signed birth certificate), an ownership chain (signature-bound transitions), cargo (whatever value it represents — USD, joules, compute-hours, votes, attestations, claims; the substrate is agnostic), and a two-part joule cost (measured + estimated, cumulative over its life). Consensus is lockstep deterministic simulation with BFT supermajority commit; the substrate scales by federating many bounded clusters, not by growing one. It is TCP/IP for value: an open, application-agnostic carrier that any matching, clearing, or trust-signaling layer can build on.
|
||
|
||
The substrate is intentionally **ownerless**: no protocol-level token, permissive licensing on the spec text and reference code, conformance test vectors so any implementer can verify canonicity without a trust relationship with the authors. The protocol's identity lives in its conformance vectors and content-addressing, not in any brand. Transaction Science is one steward — it publishes the spec, ships a reference implementation, and operates commercial services around the substrate — not its proprietor.
|
||
|
||
## Contents
|
||
|
||
- `spec/treatise_v1_parts_I_II_III_combined.md` — *Smart Byte Substrate: A Treatise* (Parts I–III: the foundation, the substrate architecture, the security engineering; Parts IV–VII previewed)
|
||
- `strategic_context.docx` — *The Strategic Context: Why the Substrate Makes Sense in 2026*
|
||
- `SECURITY.md` — the working security-engineering summary: it's a digital system on the internet, secured the way digital systems on the internet are secured (conservative cryptography, encrypted transports, reproducible multiply-reviewed builds, standard layer-2 key custody, standard availability engineering, textbook BFT consensus) plus a handful of new compositions of those proven parts. Plus the vulnerability-reporting process.
|
||
|
||
## Status
|
||
|
||
Treatise v1.0 (May 2026). The conformance specification (byte-level wire formats) and the reference implementation referenced in the treatise as "v0.3" are to be brought into this repository.
|
||
|
||
## Licence
|
||
|
||
Specification text: CC-BY-4.0 (see [`LICENSE`](LICENSE)).
|
||
Reference implementation in `smart-byte-rs/`: Apache-2.0 (see [`smart-byte-rs/LICENSE`](smart-byte-rs/LICENSE)).
|
||
|
||
## Related
|
||
|
||
- EOC (`../eoc/`) — the energy-optimized AI compute substrate; the smart byte's energy attribution depends on an honest joules-per-task substrate.
|
||
- Settlement (`settlement.science`) — the flagship regulated financial institution running on the substrate as an issuer and consumer of smart bytes.
|