UTXOSUITE — home
CHANGELOG / DEVELOPMENT TRACK

Changes with status attached.

This page records meaningful product-direction changes without presenting branch work as a production release. The transaction-security redesign remains unreleased until it is reviewed, merged to main and deployed.

CURRENT STATUS

Working branch: utxo-transaction-security-academy · Production branch: main · No automatic claim of release, audit or production readiness follows from a commit.

2026-08-26 · DEV 01

Transaction-security product architecture

Reframed UTXO Suite around SafeSign, Security Core and explicit authorization. Homepage, Products, About, Docs, Research, Labs and Projects now share the same product boundary.

2026-08-26 · DEV 02

UTXO Academy learning system

Introduced five courses, twenty modules, forty theory lessons, twenty labs, persistent progress and local completion records across fourteen locales.

2026-08-26 · DEV 03

Truthful integration surfaces

Guard, Wallet and Relay now expose their actual implementation boundary: Manifest V3 scaffold, current wallet UI with SafeSign integration requirement, and current route/PSBT analysis with future signing/execution respectively.

2026-08-26 · DEV 04

Evidence-led public documentation

Removed unsupported publication identifiers and broad production claims. Research distinguishes idea/spec/scaffold/product status, while docs state non-custodial invariants and uncertainty explicitly.

RELEASE DISCIPLINE

A future release entry should be created only after the relevant commit is on the production branch and the deployed surface has been verified. Security review, audit and peer-review labels require separate evidence.

Review product surfacesReview research status
RELEASE EVIDENCE

A changelog should describe risk, not only features.

Security-sensitive releases record changed authority, affected surfaces, migration requirements, validation evidence and rollback assumptions.

01

AUTHORITY CHANGE

Describe what the request can authorize: transfer, allowance, operator rights, typed-data authority or Bitcoin outputs.

method · spender · scope · outputs
02

SURFACE IMPACT

Unknown implementation, stale context or unavailable simulation remains visible and can raise REVIEW instead of becoming an implicit allow.

unknowns · freshness · contradictions
03

VALIDATION

Analysis must not require seeds or private keys and must never silently become signing authority.

no seed · no key custody · no auto-sign
04

ROLLBACK

Released, audited, peer-reviewed and production-ready are evidence claims, not marketing adjectives.

artifact · test · review · operations
PRODUCT TRUST LOOPNo security-sensitive change is complete without a validation and rollback story.
  1. 01CHANGE
  2. 02THREAT REVIEW
  3. 03TEST
  4. 04RELEASE
  5. 05OBSERVE