Providing a predictable, on-chain fundraising protocol to mission driven organizations.
Joined October 2025
- Tweets536
- Following326
- Followers59
- Likes33
One of the decisions we made when designing the Impact Protocol was how funds would move from each cohort's Vault to its nonprofit beneficiaries.
Rather than converting everything accumulated in the Vault each month, we designed a process that gradually converts a fixed percentage of its holdings.
Each month, the protocol is designed to convert approximately 2% of the Vault's token holdings into USDC for distribution to its three nonprofit beneficiaries, while burning approximately another 2%, subject to predefined thresholds and safety checks.
This creates a consistent, bounded process governed by predetermined rules, rather than requiring us to make ongoing decisions about how much to convert or where funds should go.
The goal was to make recurring distributions predictable in their mechanics, transparent in their execution, and independent of discretionary management.
馃 Made with AI
When we started designing the Impact Protocol, we wanted to build something that worked for both nonprofits and the communities supporting them.
That meant considering three questions:
How do we give supporters the freedom to choose which causes they support?
How do we create recurring funding opportunities for nonprofits without adding operational responsibilities?
How do we build a transparent system that can scale across different causes and communities?
For supporters, those same rules provide transparency and consistency.
Each cohort has predetermined beneficiaries, distribution splits, and economic parameters that EvolveNP cannot change after deployment.
Supporters choose which missions to participate in, and the protocol determines how the resulting funds are distributed.
Ultimately, that's what guided the architecture.
Different causes, different nonprofit beneficiaries, and communities choosing what matters to them, all operating through the same underlying system.
We wanted to create an ecosystem that gives supporters choice, nonprofits greater access to recurring funding, and both a transparent process they can independently verify.
When an Impact Protocol cohort launches, its nonprofit beneficiaries and distribution percentages are permanently defined in the smart contracts.
That means no administrator, including EvolveNP, can later replace beneficiaries, change their allocations, or redirect their distributions.
This is an intentional part of our design.
Rather than asking nonprofits to trust that funding decisions won't change, we're building infrastructure where those commitments are enforced by code.
The result is a transparent, predictable funding structure that nonprofits and participants can independently verify.
Automation shouldn't come at the expense of safety.
Our Impact Protocol is designed to automate recurring funding for nonprofits, but that doesn't mean executing trades regardless of market conditions.
Every scheduled conversion is subject to predefined safeguards, including liquidity, pricing, and slippage checks.
If market conditions fall outside acceptable parameters, the system is designed to delay execution rather than force an unfavorable trade.
Because automation should remove the need for manual intervention, not the safeguards that protect the process.
After a successful funding cycle, the Treasury holds fewer tokens. When its balance drops below 30% of supply, the Impact Fee resumes on subsequent trades.
Collect below the threshold. Stop at the threshold. Distribute from reserves. Resume when the balance falls.
Stopping the Impact Fee doesn't stop nonprofit funding.
During scheduled funding cycles, the Treasury can convert 2% of its Cohort-token holdings into USDC for its nonprofits, when safety checks permit.
Those distributions use reserves already collected.
Charity tokens have long used transaction fees to fund their causes. But in many models, those fees continue collecting regardless of how much funding the project has accumulated or directed toward its cause.
We took a different approach: a fee that turns off automatically.
Every Cohort in EvolveNP's Impact Protocol collects a 1% Impact Fee on buys and sells to build its Protocol Treasury.
Once that Treasury holds at least 30% of total token supply, the fee automatically shuts off. It's a rule established at launch.
What happens when the person managing a nonprofit鈥檚 wallet leaves?
That matters when you鈥檙e building a protocol whose beneficiary addresses cannot change after launch. The organization may receive funding for years. Its staff and board may look very different along the way.
Every nonprofit beneficiary in an EvolveNP Cohort must use a Safe multisig wallet, set up before deployment.
This allows the organization to share responsibility for its funds through multiple approvals. With the required approvals, it can also add or replace authorized signers without changing the wallet address.
When a treasurer leaves or responsibilities change, the nonprofit can update who manages the wallet. The protocol continues sending USDC to the same address.
We cannot redirect that funding to a different wallet. The nonprofit can manage who is authorized to access it.
Fixed beneficiaries should not mean being tied forever to the people who happened to work there on launch day.
馃 Made with AI
Charity tokens showed that Web3 communities will rally around real causes. But each project built its own rules for fees, treasury decisions, beneficiaries, and reporting.
You could love the mission but not trust the token. Or trust the token鈥檚 design but feel nothing for the mission. Finding a cause you connected with meant evaluating another project鈥檚 rules all over again.
We鈥檙e standardizing Impact Tokens through the Impact Protocol: one core funding structure reused across missions. Each Cohort has its own community and verified nonprofits. Beneficiaries and allocations are fixed at deployment, and USDC distributions are visible onchain.
As new missions launch, the core funding rules stay the same. What you learn about how one Cohort funds its nonprofits carries over to the next.
Know the rules. Verify where the funds go. Choose a mission you believe in.
We are excited to announce that we have officially joined @stofdn as a Corporate Founding Member! 馃帀
We鈥檙e looking forward to connecting with the broader tokenized asset ecosystem and sharing how we鈥檙e applying onchain infrastructure to nonprofit funding and philanthropy.
A big step for EvolveNP, and we鈥檙e excited for what鈥檚 ahead! 馃殌
馃 Made with AI
A meme can bring thousands of people together. They give it an identity, build a culture around it, and keep it alive through their participation.
That ability to turn a shared idea into a community is powerful. What could it do for a cause those people believe in?
We鈥檙e building the Impact Protocol to connect that community activity to nonprofit funding.
Each community has a token tied to a mission. Trading activity generates an Impact Fee, which accumulates in its Treasury. Under preset conditions, funding cycles convert a fixed portion of those holdings into USDC for verified nonprofits.
People get a mission to rally around. Nonprofits get an additional source of funding. And the community can verify where those funds go.
That鈥檚 what we鈥檙e building Impact Tokens for: communities whose activity can help change something beyond the market.
Before trusting any token, ask: who can change its rules after launch?
If an admin can replace the contract code, they can rewrite the system people joined. The fees, transfer rules, and control over funds can all change after you鈥檝e decided to participate.
So we built a narrowly limited emergency process for updating approved Uniswap endpoint addresses.
It requires preset failure conditions and a third-party co-sign. The permission extends only to those integration addresses. It does not unlock the core contracts for upgrades.
The fee, funding-cycle rules, nonprofit wallets, and allocations remain fixed throughout the repair. Once the connection passes the required checks, normal operation can resume.
We designed the protocol to limit how much the community needs to trust us, while keeping a way to respond if an external integration fails. Fixing that connection should never require giving us control over everything else.