Skip to main content

​
Overview

shyshares is the governance embodiment of shyware. The current reference deployment lives under dao/, and the first product surface is bigglom. It applies the same anonymous canonical wrapper to weighted governance:
  • anonymous ballot direction on canonical state
  • eligibility and weighting from wallet stake, delegation, or allowlist policy
  • hidden wallet-to-direction linkage in public outputs
  • canonical queued governance actions after proposal passage

​
Identity And Weighting

Unlike the civic voting deployments, shyshares derives voting weight from governance membership sources rather than document identity alone. Typical inputs are:
  • wallet ownership
  • token balance snapshot
  • delegation snapshot
  • allowlist or org policy
That does not mean KYC is irrelevant. Product policy may still require Didit-backed admission or admin-role verification, but the canonical tally weighting source is governance membership, not civic identity.

​
Execution Model

shyshares is not voting-only. Passed proposals create canonical queued governance actions on the shyware layer. Those actions may then be:
  • dispatched internally
  • routed through shywire
  • sent through BYODAO execution adapters
Canonical truth remains proposal state, tally state, and queued-action state on shyware itself.

​
Product Surface

The first SaaS example is:
  • bigglom.com for the public splash
  • quorum.bigglom.com for the member/admin governance dashboard
The product surface is multi-organization governance. The embodiment is shyshares.