Skip to main content

​
Anonymous systems that can still be verified

shyware is a blockchain wrapper for organizations that need privacy without giving up auditability. It starts with the hardest public-trust problem first:
  • anonymous and auditable voting
  • weighted anonymous governance
  • custody and transfer flows that keep public state clean while preserving policy-gated recovery and verification
The result is a shared architecture for systems where participants need plausible privacy, operators need bounded authority, and third parties still need something they can independently verify.

​
Why it matters

Most systems force a bad tradeoff:
  • public blockchains are legible but expose too much
  • private systems protect too much but ask users to trust the operator
shyware is built for the middle ground:
  • anonymous canonical state
  • public aggregate verification
  • off-chain rematch or recovery only where policy allows it
  • no operator-side authority to rewrite canonical truth

​
Embodiments

The platform is being deployed through five embodiment families:
  • shyvoting for anonymous public-interest voting
  • shyshares for weighted governance and queued execution
  • shycontracts for private-facing contracts and financing flows
  • shycustody for pooled custody claims and redemption
  • shywire for wrapped transfer and issuer rails

​
Current posture

This docs site is intentionally compact while the fuller public packet is being staged. The underlying SDK, embodiment examples, and deployment materials are being organized into a cleaner public release.

​
Request access

For pilot conversations, private walkthroughs, or licensing inquiries, contact hello@sayists.com.