FAQs

The protocol distributes USDC only to predefined beneficiary wallets (typically nonprofit-controlled multisigs). Those recipient wallets are outside the protocol and controlled by their owners.

No. There is no platform-controlled custody path and no admin withdrawal or redirection mechanism. Funds flow is determined by immutable rules and distributes to predefined recipients.

The Impact Fee is a small, fixed protocol fee (1%) that routes tokens into the Vault under deterministic rules. There is no admin switch to toggle it on/off; it applies (or becomes zero) automatically based on hard-coded conditions (e.g., the Vault balance threshold).

Not in normal operation. There are no pause/unpause controls in NORMAL mode. The only privileged capability is emergency-time, allowlisted Uniswap endpoint repair during a time-bounded emergency window.

No. Core parameters are immutable in normal operation. Any change to those requires redeploy/migration. The only post-deploy mutable surface is emergency-only Uniswap endpoint updates via the IntegrationRegistry.

It’s permissionless. Anyone can execute the monthly swap + distribution when it’s due and safety checks pass. A standard monitoring bot can be used for reliability, but it has no special permissions and cannot change rules or funds flow.

The monthly event is guarded by deterministic safety checks (e.g., TWAP/tick deviation). If conditions are unsafe, execution simply fails and can be retried later.

We publish contract addresses and a dashboard showing Impact Fee inflows, monthly swap events, and distributions — all derived from on-chain events.

Objective failures can ARM the system on-chain. Only then can a short EMERGENCY_ACTIVE window be opened to update allowlisted Uniswap endpoints via the IntegrationRegistry. All updates are recorded with on-chain events.

Direct deposits are ignored for distribution purposes. The Vault distributes only USDC produced by its own swap execution.