Funding and governance for humans and agents, built on Arc.
Fund USDC into the treasury, vote on proposals, and execute releases through contract-verified rules.
How it works
Fund treasury
Deposit USDC into the on-chain governance treasury. The balance is publicly readable at any time from the Arc explorer.
Vote on a proposal
Members vote For, Against, or Abstain on a proposal that specifies a payee, amount, and deliverable document pinned to IPFS.
AI verifier scores it
An AI agent scores the deliverable against the proposal document. The score is an input to the discussion — the vote is the only trigger for release.
Release to payee
Once the contract confirms the three-way match (vote passed, deliverable hash matches, cooldown elapsed), funds transfer to the payee address.
Architecture
Document-anchored treasury entries
Every treasury outflow must reference a pinned IPFS document. The contract stores the CID on-chain — no document hash, no release.
Contract-level three-way match
Release requires three things to agree at the contract level: the vote result, the deliverable CID, and the payee address recorded in the proposal.
48-hour payee-change cooldown
After a payee address is set or changed, a 48-hour delay is enforced before that address can receive funds — closing the last-minute address-swap attack.
AI verifier as input, not trigger
The AI agent reads the deliverable and scores it against the proposal. That score appears in the proposal thread. It has no write-access to the release function.
One SDK. Four Architectures.
Organizations
- Dual-treasury architecture: timelocked reserves & operating accounts
- Contract-enforced Three-Way Match for programmatic vendor payouts
- 48-hour payee-change cooldown to prevent address substitution attacks
- Automatic human multi-sig review gate on disbursements above 50 USDC
Businesses
- Milestone-gated customer escrows with verified deliverable checks
- Instant cross-chain customer invoicing via native Circle CCTP
- Automated working capital yield via curated Morpho vaults on Arc
- Sub-cent native USDC gas settlement with zero synthetic asset risk
Communities & DAOs
- Checkpointed OpenZeppelin ERC20Votes with delegated balance snapshots
- Custom voting strategies: Quadratic, Staked Duration, or Multi-Asset
- Milestone crowdfunds and creator launchpads with transparent tracking
- Public grant disbursements verified on-chain against IPFS deliverables
AI Agents
- Autonomous sub-cap execution (under 50 USDC) with zero human latency
- Canonical on-chain agent identity registered via ERC-8004
- Treasury Guard: automated health monitoring and cross-chain rebalancing
- Hardware-style bit-flip guards for deterministic idempotency protection
Pluggable Governance & Voting Weight
Determining Voting Weight
1 sARC = 1 vote. Balances are check-pointed by block height via ERC20Votes, eliminating flash-loan manipulation.
Stable asset holdings (USDC, EURC, cirBTC) provide economic multipliers to prevent purely speculative volatility.
Pluggable algorithms dampen whale dominance (weight = square root of tokens) and integrate ERC-8004 agent credentials.
import { SynArc, SYNARC_MAINNET } from 'synarc-agent-sdk';
// 1. Initialize client
const synarc = new SynArc(SYNARC_MAINNET);
// 2. Compute quadratic voting power
function getQuadraticWeight(rawTokens: bigint) {
return BigInt(Math.floor(Math.sqrt(Number(rawTokens))));
}
// 3. Verify on-chain snapshot balance
const votes = await synarc.getPastVotes(user, block);
const weight = getQuadraticWeight(votes);
Zero-Knowledge Privacy
ZK Confidential Ballots
Voters prove voting eligibility and voting power via client-side ZK-SNARK proofs without revealing their address or token balances.
Shielded Disbursements
Stealth address generation and private USDC transfers allow enterprise payroll and contractor retainers to remain confidential.
Selective Viewing Keys
Exportable cryptographic viewing keys allow authorized compliance auditors and tax authorities to inspect transaction records on demand.