SNARKSTRRead the label
on the machine.
What exists, what doesn't, who would hold authority, and what could go wrong — stated plainly.
Contracts
The planned contract architecture. None of these are deployed. No address exists; anything claiming to be a SNARKSTR contract address today is not ours.
| Contract | Responsibility | Address | Status |
|---|---|---|---|
| SnarkstrLaunchController | Pons launch binding & config hash commitment | — | NOT DEPLOYED |
| FeeCollector | Pulls creator fees from the Pons fee escrow | — | NOT DEPLOYED |
| AcquisitionVault | Holds acquisition funds; enforces capped exports | — | NOT DEPLOYED |
| CustodyRegistry | Records holdings and evidence references | — | NOT DEPLOYED |
| StakeEscrow | Opt-in staking, 7-day maturity, checkpoints | — | NOT DEPLOYED |
| Governor + Timelock | Typed bounded-sale proposals only | — | NOT DEPLOYED |
| SaleController | Executes authorized bounded sales within bounds | — | NOT DEPLOYED |
| ProfitLedger | Cost basis, realized gains, loss carryforward | — | NOT DEPLOYED |
| DistributionVault | Funded epochs and pull claims | — | NOT DEPLOYED |
Authority & roles
- EVM vault rules — enforced on-chain once deployed: capped exports, one active purchase, no percentage extraction.
- Operator (disclosed) — runs the off-chain workers: fee indexing, conversion orchestration, listing scans, purchase submission, custody attestations. Cannot rewrite claim entitlements or reorder settled sales.
- Governance (participants) — authorizes bounded sales only. The initial policy authorizes no upgrades, no delegatecall, no arbitrary transfers, no claim rewrites.
- Upstream platform owner — retains real powers over the launch platform (e.g. a creator-fee-recipient override with a 3-day execution window in the pinned source). Monitored, not removable.
- The public — reads everything, refreshes data, claims funded distributions. No public action can spend treasury funds.
Custody model
Two evidence classes, always labeled:
- Operator attestation — the operator states custody and publishes references. This is the default class until independent verification exists on the native side.
- Independent verification — a third party or on-chain mechanism verifies ownership cryptographically. Nothing is labeled “on-chain proof” unless it actually is.
A receipt hash is not, by itself, proof of ownership. Custody mismatches pause new outflows for reconciliation.
Source freshness
| Source | Status |
|---|---|
| Pons V2 source | source-verified, pinned commit 162310fbd1217717e2f5e4cde794d6a11322b469, fetched 2026-09-18. Deployment unverified — deployed bytecode may differ; live fee ceilings are mutable state. |
| Robinhood Chain | unverified — chain ID, RPC, explorer and finality policy unknown. |
| Zilkroad marketplace | unverified — site showed an auction/terminal UI, no documented API. No purchase endpoint will be synthesized. |
| zkSNARKs collection identity / X account | unverified — canonical collection identity and artwork provenance not established; X inaccessible at last pass. |
| Conversion provider | unverified — documentation pointer only; route, asset IDs and refunds untested. Production adapter disabled. |
Summarized from the repository's verified-integrations register (docs/VERIFIED_INTEGRATIONS.md). Legend: “source-verified” means the source code was fetched, pinned and read — it says nothing about any deployment. No integration is deployment-verified.
Allocation policy
- 100% of net creator receipts → acquisition strategy.
- 0% developer allocation · 0% token buyback · 0% dividends from trading taxes.
- Documented conversion/network/marketplace execution costs may be paid within capped acquisition orders — nothing uncapped.
- On a settled gain: capital + prior losses recovered first, then a 50/50 split between acquisitions and eligible participants.
Source artwork provenance
The character images shown across this site as “collection examples” are 15 files downloaded from X's media CDN (pbs.twimg.com), located via the public Sotwe index of @zksnarks_. Every file's SHA-256 hash was verified against the source manifest on 2026-09-18. Downloading a public image proves which bytes were retrieved — it does not establish collection membership, item identity, current ownership, reuse permission, or endorsement. Rights are not verified for any of them; public availability is not a blanket permission. Community reposts are labeled community-source and are never presented as official posts or treasury holdings. Historical official figures visible in reference media (auction results, supply counts, clearing prices, countdowns) are never shown as SNARKSTR metrics.
| File | Category | Indexed author | Used on site | Rights |
|---|---|---|---|---|
profile-banner | official-account reference | @zksnarks_ | no — reference only (references/source-assets) | NOT VERIFIED |
profile-avatar | official-account reference | @zksnarks_ | no — reference only (references/source-assets) | NOT VERIFIED |
auction-results | official-account reference | @zksnarks_ | no — reference only (references/source-assets) | NOT VERIFIED |
terminal-final-post | official-account reference | @zksnarks_ | no — reference only (references/source-assets) | NOT VERIFIED |
terminal-two-hours | official-account reference | @zksnarks_ | no — reference only (references/source-assets) | NOT VERIFIED |
twenty-character-collage | community-source repost | @AdamWeitsman | yes — as a labeled collection example | NOT VERIFIED |
red-face-white-cap | community-source repost | @mattmedved | yes — as a labeled collection example | NOT VERIFIED |
lime-red-eyes | community-source repost | @BrenzGarage | yes — as a labeled collection example | NOT VERIFIED |
brown-white-cap | community-source repost | @CryptoVonDoom | yes — as a labeled collection example | NOT VERIFIED |
lavender-hood-red-eyes | community-source repost | @rajj_s23 | yes — as a labeled collection example | NOT VERIFIED |
blue-orange-beanie | community-source repost | @skominers | yes — as a labeled collection example | NOT VERIFIED |
cyan-purple-beanie | community-source repost | @austinoakes | yes — as a labeled collection example | NOT VERIFIED |
lime-metal-mask | community-source repost | @coffeedev | yes — as a labeled collection example | NOT VERIFIED |
white-hood-red-cap | community-source repost | @0xQuit | yes — as a labeled collection example | NOT VERIFIED |
brown-black-cap | community-source repost | @bicepcurl | yes — as a labeled collection example | NOT VERIFIED |
Typed manifest: apps/web/lib/sourcedArt.ts · full download record with hashes and URLs: references/source-assets/SOURCE_MANIFEST.json. The twenty-character collage is shown only as a collage and never split into individual item records.
Risks
- Total loss of traded value: an experimental token can go to zero.
- Unverified dependencies: chain, launchpad deployment, marketplace, conversion route and custody verification all remain unverified; any of them may never materialize.
- Marketplace risk: without a documented listing/purchase API, the buyer cannot activate at all.
- Custody risk: native-side holdings are operator-custodied; operator attestation is weaker evidence than independent verification, and loss or compromise of custody is possible.
- Upstream authority risk: the launch platform's owner retains powers (e.g. fee-recipient override with an execution window) that SNARKSTR must monitor but cannot remove.
- NFT market risk: floor prices can fall; realized losses carry forward and delay any future distribution.
- No yield: distributions require an actually settled, gain-making, participant-approved sale — which may never happen.
- Regulatory and legal uncertainty for token, NFT and distribution mechanics.
- Smart-contract and operational bugs, including in off-chain workers.
Live gate states: /status · machine readable: /api/status.