UTXOSUITE — home
ABOUT / UTXO SUITE

Security infrastructure for the moment before authorization.

UTXO Suite focuses on a narrow problem with large consequences: helping people and software understand a wallet request before authority is granted.

ABOUT / HOW THE WORK IS DONEA research desk with notes, instruments and a lit screen.
MISSION

Make signing context inspectable.

SafeSign is the human review surface. Security Core is the reusable analysis and policy layer. UTXO Academy teaches the concepts needed to reason about approvals, typed data, destinations, simulations and transaction authority.

NO CUSTODY

SafeSign and Security Core do not need seed phrases or private-key custody to explain a request.

EXPLICIT AUTHORIZATION

Analysis can inform a decision; it must not silently replace the user's signing boundary.

LOCAL-FIRST WHERE PRACTICAL

Sensitive preferences and analysis stay on-device when the integration permits it.

EVIDENCE-LED STATUS

A scaffold is called a scaffold. Audit, peer-review and production claims require actual evidence.

BUILD ORGANIZATION

A focused product inside a wider research ecosystem.

UTXO Labs Team works on security, transaction analysis, routing and systems research. Idovio Team works on application and product software. Sibling networks and experiments remain visible through Projects and Labs without becoming implicit UTXO Suite features.

SCOPE

Product promise and research scope are deliberately separate.

UTXO Suite is not presented as every system built by the teams. That separation keeps product expectations, security boundaries and technical status understandable.

Core UTXO Suite

SafeSign · Security Core · UTXO Academy · Guard/Wallet/Relay integration surfaces.

Wider project index

Networks, infrastructure, languages, productivity experiments and sibling products keep their own status and identity.

Explore the product system
TRUST CHARTER

The product boundary is a security control.

UTXO Suite is intentionally narrow: inspect authority before execution, expose uncertainty and preserve the external signing boundary. Everything else must remain explicitly outside that promise.

01

AUTHORITY

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

method · spender · scope · outputs
02

UNCERTAINTY

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

unknowns · freshness · contradictions
03

NON-CUSTODY

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

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

EVIDENCE STATUS

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

artifact · test · review · operations
PRODUCT TRUST LOOPThe product explains authority; the wallet or signer retains authority.
  1. 01INTENT
  2. 02EVIDENCE
  3. 03BOUNDARY
  4. 04DECISION
  5. 05AUTHORIZATION