open-standards/smart-byte
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science 268171ffd5
All checks were successful
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 2m18s
standards workspaces build + test / aac-rs (pull_request) Successful in 1m17s
smart-byte conformance gate / Validate conformance JSON files (pull_request) Successful in 4s
smart-byte conformance gate / Second implementation reproduces every vector (pull_request) Successful in 4s
smart-byte conformance gate / Spec changes require vector-pack updates (pull_request) Successful in 3s
smart-byte conformance gate / VERSIONS.md and README.md must exist (pull_request) Successful in 3s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 45s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 33s
standards workspaces build + test / map-rs (pull_request) Successful in 34s
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Successful in 1m27s
standards workspaces build + test / mesh-rs (pull_request) Successful in 30s
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 57s
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
standards workspaces build + test / openpay (pull_request) Successful in 1m43s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m49s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m20s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m12s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m8s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m4s
standards workspaces build + test / arl-rs (pull_request) Successful in 5m10s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 14m41s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m35s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 3m57s
standards workspaces build + test / sense-rs (pull_request) Successful in 9m51s
standards workspaces build + test / macOS energy backend (jcp-energy) (pull_request) Successful in 17m0s
Merge main into smart-byte-cluster-state
# Conflicts:
#	smart-byte/conformance/v1/regeneration.md
2026-10-01 06:21:29 -04:00
..
conformance Merge main into smart-byte-cluster-state 2026-10-01 06:21:29 -04:00
smart-byte-rs smart-byte: the cluster state machine, and its conformance vectors 2026-10-01 06:19:03 -04:00
spec Merge main into smart-byte-cluster-state 2026-10-01 06:21:29 -04:00
vocab vocab v1 SHACL shapes across sister standards (wave-23 #4/#5) 2026-06-02 18:55:56 -04:00
LICENSE Initial import — three open standards under one shelf 2026-05-23 07:58:09 -04:00
README.md Initial import — three open standards under one shelf 2026-05-23 07:58:09 -04:00
SECURITY.md Initial import — three open standards under one shelf 2026-05-23 07:58:09 -04:00
THREE_FACES.md Initial import — three open standards under one shelf 2026-05-23 07:58:09 -04:00

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.

  • 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.