| Filename | Latest commit message | Latest commit date |
|---|---|---|
8fc1d07940
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 2m30s
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
standards workspaces build + test / smart-byte-rs (smart-byte/smart-byte-rs, smart-byte-rs, linux) (pull_request) Successful in 3m35s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 22m1s
Two follow-ups to my own work in #449. **The fix shipped on a yanked release.** #449 bumped crypto-bigint 0.7.3 -> 0.7.6 in smart-byte to clear RUSTSEC-2026-0387 (secret-dependent branches in operations meant to be constant-time). The author has since yanked every 0.7.x below 0.7.9 — 0.7.1 through 0.7.8, 0.7.6 among them — so the version chosen to fix an advisory is now withdrawn. Moved to 0.7.10, which is not yanked and still satisfies the advisory's `>=0.7.6`. No yanked dependency remains anywhere in the tree. The pin was correct when it was made and went stale for a reason outside the tree, which is the argument for re-reading the yanked list after advisory work rather than once. **An omission in the gate, turned into a decision.** The header said warnings are not gated because they are "advice about maintenance, not a reachable defect". That is honest for `unmaintained` and evasive for the other two, both of which have been worth acting on. It now says what is true: - unsound-with-a-fix is a real defect a bump would close; one was a use-after-free in `LruCache::pop()`. It is not gated *today* only because every current instance is either pinned by a dependent (zstd-safe under wasmtime 49's module cache, which nothing here configures) or needs a semver-major move of a transitive crate (lru, rand, glib). A gate that is red for things nobody can act on teaches people to bypass it, which costs more than it catches. The trigger to gate it is those becoming movable. - yanked can happen to a version that was correct when chosen, as above. Gating it would turn every PR red for a decision made outside the tree, so it stays a warning — but it is a standing review item, which is how this one was caught. Recorded decisions with trigger conditions, rather than an unexamined gap. 60 lockfiles, the same 19 allowances, self-test green on all six cases, lockfile check current, smart-byte checks clean. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| conformance | ||
| smart-byte-rs | ||
| spec | ||
| vocab | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| THREE_FACES.md | ||
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 2026SECURITY.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).
Reference implementation in smart-byte-rs/: Apache-2.0 (see 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.