EvolveNP Protocol — Simple, Transparent, Automated

• What it is: A fair-launch token on Ethereum that routes a small, rules-based portion of activity into a single Vault that periodically converts a fixed percentage to USDC and distributes it to predefined nonprofit multisigs — without platform custody.
• Who holds the funds: Nonprofit multisig beneficiaries (Safe wallets). The protocol distributes USDC only to predefined nonprofit-controlled addresses.
• What happens over time: On a fixed cadence (e.g., monthly), anyone can trigger a permissionless, rule-gated “swap + distribute” event when safety checks pass.
• Break-glass only changes In normal operation, there are no admin controls (no pausing, no parameter tuning, no routing changes). The only post-deploy changes are emergency-only Uniswap endpoint updates via a strict allowlist and a time-bounded emergency window.

• Traditional fundraising takes time, trust, and manual effort. Our protocol automates routine, rule-based support for nonprofits on-chain — transparent, non-custodial by design (no admin withdrawal or redirection), and auditable by anyone.

1. Fair Launch
   • No insider lists. No private allocations.
   • At launch, ~75% to public LP (DEX), ~25% to Treasury.
   • Initial liquidity is seeded (~3–7 ETH paired with tokens).
   • Short anti-sniping window (e.g., first hour) to promote fair access (cooldowns, per-tx max buy, brief launch limits).
2. Rules-Based Fee Routing (Impact Fee → Vault)
   • A small, fixed Impact Fee (think “tax-like fee” on qualifying transfers) routes token inflows into the Vault under deterministic rules.
   • Hard cap rule (non-discretionary): The Impact Fee applies only while the Vault’s token balance is below a fixed threshold (e.g., < 30% of total supply).
   • Once the Vault reaches the threshold, the Impact Fee automatically becomes zero by rule until the balance falls below the threshold again.
   • There is no admin switch to toggle the Impact Fee. It is applied (or not applied) automatically by hard-coded rules.
3. Vault (Conversion + Distribution)
   • Receives token inflows from the Impact Fee.
   • On a fixed cadence (e.g., monthly), swaps a fixed percentage of its token holdings (e.g., 2%) to USDC.
   • Distributes only the USDC produced by that swap to a predefined list of nonprofit multisig beneficiaries, using fixed splits.
4. Permissionless Monthly Execution (No privileged operator required)
   • The monthly event is callable by anyone, but only when the Vault’s rules allow it.
   • The Vault checks deterministic conditions such as: It is due (time interval elapsed), Emergency mode is not active, Minimum balance, Safety checks (e.g., TWAP/tick deviation bounds) pass.
   • If conditions fail, the call reverts and nothing changes. This ensures execution is open, but fully rule-gated.

1. Trading happens on a DEX
2. The impact tax(when applicable) routes tokens into the Vault under a hard-coded threshold rule (e.g., tax applies only while Vault balance < 30%).
3. When the cadence is due (e.g., monthly), anyone can call the Vault’s execution function.
4. The Vault runs deterministic safety checks (including price integrity checks).
5. If safe and due, the Vault swaps a fixed percentage of its token balance (e.g., 2%) into USDC using Uniswap endpoints from the IntegrationRegistry.
6. The Vault distributes only the swap-produced USDC delta to predefined nonprofit multisig beneficiaries using fixed splits.
7. Everything emits on-chain events: anyone can verify.

• Objective safety gating (execution skips rather than forces) The Vault executes only when due and when predefined price-integrity checks pass (e.g., TWAP/tick deviation bounds). Otherwise it skips.
• No normal-mode admin control
  • No pause/unpause.
  • No admin knobs to change tokenomics, recipients, thresholds, cadence, or splits.
  • No routing changes or “switching venues” at will.
  • No proxy/beacon upgrades.
• Objective safety gating (execution skips rather than forces) The Vault executes only when due and when predefined price-integrity checks pass (e.g., TWAP/tick deviation bounds). Otherwise it skips.
• Break-Glass Only Emergency Path (narrow + time-bounded) The protocol includes a global emergency state machine (EmergencyManager) with three modes:
  • NORMAL: default mode. No privileged actions exist.
  • ARMED: objective on-chain conditions indicate an integration failure (e.g., repeated swap/quote failures, oracle invalid/stale data if used, endpoint integrity failure, liveness failure).
  • EMERGENCY_ACTIVE: a short EMERGENCY_ACTIVE window can only be activated after ARMED, and only by an emergency multisig.
• During EMERGENCY_ACTIVE, the only permitted privileged action is: Updating allowlisted Uniswap integration endpoints in a single IntegrationRegistry. No other updates are possible.
  • No parameter edits (fee rate, thresholds, cadence, swap percent, beneficiary list, splits).
  • No pausing toggles in normal mode.
  • No “upgrade logic.”
• IntegrationRegistry (the only mutable surface)
  • Core contracts are immutable.
  • They read Uniswap endpoints (router/quoter/state view/permit2/pool manager as required) from the IntegrationRegistry.
  • The registry can be updated only during EMERGENCY_ACTIVE and only to pre-allowlisted endpoints (and optionally allowlisted bytecode hashes).
  • TEvery update emits an on-chain event for auditability.
• Public verification
  • Contract addresses (Token, Hook, Vault, EmergencyManager, IntegrationRegistry, nonprofit beneficiary safes)
  • Parameters and thresholds (fixed/immutable)
  • Flow-of-funds dashboard sourced from on-chain events

• Launch split: ~75% public liquidity, ~25% Vault.
• Initial liquidity seed: ~3–7 ETH equivalent.
• Impact Fee threshold: tax applies only while Vault token balance < 30% of total supply (hard-coded, non-mutable).
• Monthly event: swap ~2% of Vault token holdings to USDC (fixed).
• Distributions: only swap-produced USDC delta distributed to predefined nonprofit multisigs (fixed splits).
• Anti-sniping window: first hour post-launch (e.g., cooldowns, max buy/tx, brief launch limits.
• Emergency window: time-bounded EMERGENCY_ACTIVE, only after objective ARMED
• Exact parameters live on-chain. In normal operation they are not adjustable; changes require redeploy/migrate. The only post-deploy mutable surface is emergency-only allowlisted Uniswap endpoint updates.

• No admin controls in normal operation: Contracts run deterministically with no ability to change parameters, routing, or execution behavior.
• Permissionless monthly execution: Anyone can call the monthly execution, and it succeeds only when timing and safety conditions are satisfied.
• Emergency-only integration updates: The only post-deploy change is emergency-time replacement of allowlisted Uniswap integration endpoints via the IntegrationRegistry, allowed only during a time-bounded emergency mode and recorded via on-chain events.
• Informational disclaimer: This page is informational only and not legal, tax, or investment advice.

• FERC-20 Token
• Hook (routes Impact Fee to Vault under hard-coded threshold logic)
• Vault (custody + monthly swap + distribution; permissionless execution)
• EmergencyManager (NORMAL → ARMED → EMERGENCY_ACTIVE; objective arming; time-bounded emergency).
• IntegrationRegistry (only mutable surface; emergency-only updates to allowlisted Uniswap endpoints)
• Nonprofit beneficiary safes (multisig wallets)

• No privileged actions callable in NORMAL mode (no pausing, no parameter changes, no endpoint changes).
• IntegrationRegistry updates revert unless EmergencyManager is EMERGENCY_ACTIVE.
• Only allowlisted endpoints (and optionally allowlisted codehashes) can be set even in EMERGENCY_ACTIVE.
• PVault distributes only swap-produced USDC delta (unsolicited USDC remains inert).
• Monthly execution is permissionless but fully rule-gated (due + safety checks).

• Not required for correctness: anyone can execute the monthly event when it’s due and safety checks pass.
• Optional for reliability: a standard monitoring bot can be used to trigger execution on schedule, but it has no special permissions and cannot change rules or funds flow.

• Contract addresses: Token, Hook, Vault, EmergencyManager, IntegrationRegistry, nonprofit beneficiary safes
• Parameters & thresholds (immutable)
• Audit & bug bounty links
• Flow of Funds dashboard
• Emergency runbook (emergency conditions, objective arming triggers, and event meanings)

Disclaimer: This page is an informational summary of how the protocol is designed to operate. It is not legal, tax, or investment advice.