Straight Answers About How EvolveNP Works.
Quick answers about custody, fees, safety checks, and verification.
Where Funds Live and Move
Who holds the money?
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.
Does EvolveNP ever take custody?
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.
What if someone sends USDC directly to the Vault?
Direct deposits are ignored for distribution purposes. The Vault distributes only USDC produced by its own swap execution.
What Can and Cannot Change
What is the Impact Fee? Can you turn it on or off?
The Impact Fee is a small, fixed protocol fee of 1% that routes tokens into the Vault under deterministic rules. There is no admin switch to toggle it on or off; it applies, or becomes zero, automatically based on hard-coded conditions such as the Vault balance threshold.
Can you pause the system?
Not in normal operation. There are no pause or unpause controls in NORMAL mode. The only privileged capability is emergency-time, allowlisted Uniswap endpoint repair during a time-bounded emergency window.
Can the team change the fee rate, cadence, recipients, or splits later?
No. Core parameters are immutable in normal operation. Any change to those requires redeployment or migration. The only post-deploy mutable surface is emergency-only Uniswap endpoint updates through the IntegrationRegistry.
How Monthly Events Stay Reliable
Who runs the monthly event?
It is permissionless. Anyone can execute the monthly swap and distribution when it is due and safety checks pass. A standard monitoring bot can be used for reliability, but it has no special permissions and cannot change the rules or funds flow.
What happens if markets are volatile?
The monthly event is guarded by deterministic safety checks, including TWAP and tick-deviation checks. If conditions are unsafe, execution simply fails and can be retried later.
What if Uniswap integrations break or endpoints change?
Objective failures can ARM the system onchain. Only then can a short EMERGENCY_ACTIVE window be opened to update allowlisted Uniswap endpoints through the IntegrationRegistry. All updates are recorded with onchain events.
How to Check the Activity Yourself
How can I verify what is happening?
We publish contract addresses and a dashboard showing Impact Fee inflows, monthly swap events, and distributions—all derived from onchain events.
Still Have a Question?
Explore the deeper protocol mechanics or reach out to the EvolveNP team.