shyware

anonymous by design. auditable by law.

Anonymous distributed-ledger protocol. Structural non-linkability across voting, wire transfer, custody, contracts, and governance — one invariant, thirteen embodiments.

Read the docs How structural anonymity works Get a license

Protocol properties

Non-linkabilitystructural — no join key between List 1 (payload) and List 2 (identity hash)

Verifiabilitypublic count-match + disjoint Merkle roots; signatures are an optional attestation layer

Recoverycredential-free biometric re-derivation when the recovery layer is deployed; no seed phrase or password

Authority model3–4 structurally separated parties; dual co-authorization enforced at validation layer

Latency1–6 s block finality (Hyperledger Fabric / CometBFT BFT, no proof overhead)

GDPR379/379 assertions pass on web, iOS, and Android stacks

Embodiment examples

13 contract variants. Each is a reference implementation — build your own on any variant.

shyvoting-v1Elections

Coercion-resistant anonymous ballots. Write-only posture on attested device. Hostile-regime ready.

shyvoting-v1Civic Referenda

Anonymous civic votes with public count-match verification and optional signed attestation.

shywire-v1Private Value Transfer

Conservation-auditable stablecoin transfers. Amount and sender unlinked in canonical state.

shycustody-v1Commodity Custody

Warehouse receipt system. Holder identity absent from canonical lot records.

shycontracts-v1Anonymous Smart Contracts

Arbitrary anonymous bilateral contracts. Party identity non-derivable from canonical state. RBF is one contractType.

shyshares-v1DAO Governance

Wallet-weighted anonymous proposals. Delegation mapping structurally non-enumerable.

shychat-v1Private Messaging

Anonymous dispatch. Sender identity structurally absent from canonical payload records.

Trust tiers

"Who else has to agree with you?" has three honest answers, not two. A deployment should state which tier it's actually running at each layer, not the strongest-sounding adjective available. Full writeup →

Tier 3 — Self-assumedOne party controls the ledger and vouches for it. The honest floor every deployment starts from — not a flaw, just a starting state that should be labeled as what it is.

Tier 2 — Independent providerA party you don’t control attests to it — an RFC 3161 Time Stamp Authority, a hardware attestation independently verified against the manufacturer’s own certificate chain. Standard practice, not novel.

Tier 1 — Consensus (N≥4)No single party, trusted or not, can act unilaterally. Not a different mechanism from Tier 2 — Tier 2, generalized past the Byzantine fault-tolerance threshold (N ≥ 3f+1).

Install

npm install @shyware/sdk

⬡ ShywareLLC/sdk JavaScript ⬡ ShywareLLC/sdk-ios Swift ⬡ ShywareLLC/sdk-android Kotlin

How it works

// Submission: two unlinked atomic writes
//   List 1 (payload record)     — no identity
//   List 2 (participant record) — no payload, no submission ID
//
// Count-match invariant checked before canonical state commits:
//   |L1(S)| === |L2(S)|   ← verifiable by arithmetic
//
// Optional signed period-close attestation:
//   σ = Sign( H(root_L1 ‖ root_L2 ‖ N ‖ domain_aggregate) )
//   Any signing key can supply this additional layer.
//   KMS/HSM is not required for the protocol guarantees.

Explore the two-list architecture, recovery, and trust tiers →