Shortly
FactoryDAO needed a DAO development company capable of building an interconnected product ecosystem rather than a single governance contract. Neti helped deliver three user-facing dApps: Influence.Vote for multichain governance, Bank.Vote for scalable token distribution and Yield.Vote for staking and liquidity incentives. The project combined Solidity smart contracts, EVM-compatible architecture and full-stack blockchain dApp development.
The Challenge: One Ecosystem, Three Different DAO Needs
FactoryDAO wanted to provide decentralized communities with tools for three critical areas:
- making collective decisions
- distributing tokens at scale
- creating staking and liquidity incentives.
Each product required different smart contract logic and user flows. At the same time, all three applications had to work as part of one consistent ecosystem.
The team also had to address several blockchain-specific constraints:
- large token distributions could generate prohibitive gas costs;
- communities operated on different networks and used different tokens;
- voting and staking mechanics had to remain understandable to end users;
- the architecture needed to support future integrations and deployments.
This is why FactoryDAO needed more than contract development. It needed a partner capable of connecting blockchain logic, frontend applications and product architecture.
Three dApps, One DAO Ecosystem
| Product | Business purpose | What Neti delivered |
|---|---|---|
| Influence.Vote | Flexible governance and community voting | Multichain voting application with linear and quadratic voting models |
| Bank.Vote | Scalable token distribution and airdrops | Merkle Tree-based token claims designed to reduce on-chain data and gas costs |
| Yield.Vote | Staking and liquidity incentives | Configurable staking pools, liquidity mining and token reward mechanics |
DAO Development Services Delivered by Neti
Neti worked across both the smart contract and application layers.
The project covered multichain governance, scalable token distribution and DeFi staking platform development. Each application solved a different problem within the wider FactoryDAO ecosystem.
Influence.Vote: Multichain DAO Governance
Influence.Vote was designed to help decentralized communities organize voting without building their own governance platform from scratch.
The application supported:
- multiple voting models;
- linear and quadratic voting;
- different token-based communities;
- EVM-compatible blockchain networks;
- wallet-based participation;
- integrations with external applications.
The multichain approach allowed DAO teams to use governance tools without moving their existing token or rebuilding their community around one required network.
Supporting different voting models was equally important. Instead of assuming that every DAO should use the same governance mechanism, Influence.Vote gave communities greater flexibility in how voting power was calculated.
Bank.Vote: Scalable Token Distribution
Bank.Vote addressed a different challenge: distributing tokens to large groups of wallet addresses without making the operation unnecessarily expensive.
Publishing thousands of recipient addresses directly on-chain would increase storage and transaction costs. Neti therefore implemented a distribution model based on Merkle Trees.
How did Neti reduce the cost of large token airdrops?
Instead of storing the complete recipient list in a smart contract, the system generated a Merkle Tree and published only its root on-chain.
Each eligible user received a Merkle proof confirming that their wallet and allocation belonged to the approved distribution. The smart contract could verify that proof without storing the full dataset.
This approach:
- reduced the amount of data written to the blockchain;
- preserved cryptographic verification;
- allowed the distribution to scale to significantly more recipients.
The Merkle Tree and proofs were calculated in advance, so users did not have to wait for the entire dataset to be processed when claiming tokens.
Bank.Vote also supported broader token distribution use cases, including scheduled releases and vesting mechanics.
This was Neti’s first production implementation using Merkle Trees. The approach reduced the expected cost of large-scale token distribution beyond the initial estimates.
Yield.Vote: Staking and Liquidity Incentives
Yield.Vote extended the ecosystem into staking and liquidity mining.
The application allowed communities to create configurable incentive pools rather than rely on one fixed staking model. Its scope included:
- staking pools;
- liquidity mining;
- token-based rewards;
- configurable pool parameters;
- gamification mechanics;
- support for EVM-compatible networks.
This made Yield.Vote more than a standalone DeFi product. It connected community participation with the broader governance ecosystem being developed by FactoryDAO.
End-to-End Blockchain dApp Development
Neti’s role extended beyond writing Solidity code. The scope covered end-to-end blockchain dApp development, including smart contracts, frontend interfaces, wallet interactions and blockchain integrations.
Each product required coordination between:
- smart contracts;
- frontend interfaces;
- wallet interactions;
- transaction states;
- blockchain integrations;
- deployment environments;
- user experience.
This matters because a smart contract can work correctly and still fail as a product.
Users need to understand what action they are taking, what is happening to their transaction and what they should do next. The application layer has to hide unnecessary blockchain complexity without removing transparency or control.
The FactoryDAO ecosystem was therefore designed around reusable application patterns rather than three completely disconnected implementations.
That approach made it easier to support multiple networks, extend the portfolio and adapt components for future products.
The Result: One Ecosystem for Governance, Distribution and Staking
FactoryDAO gained a reusable product foundation covering three core areas of decentralized community operations.
Instead of building separate tools for each new use case, the client could develop its portfolio around shared blockchain and application patterns.
The delivered ecosystem enabled:
- flexible governance across EVM-compatible environments;
- verifiable token distribution without storing full recipient lists on-chain;
- configurable staking and liquidity incentive mechanisms;
- user-facing applications built around shared wallet and transaction patterns.
The project demonstrated that Neti could connect smart contract logic, multichain architecture and frontend delivery within one product ecosystem.
What This Project Proves About Neti
The FactoryDAO project shows that Neti can support Web3 teams building products that extend beyond a single smart contract.
Our work combined:
- DAO governance development;
- scalable token distribution;
- staking and liquidity mechanics;
- multichain application design;
- smart contracts and user-facing dApps.
The technical decisions were driven by product constraints. Merkle Trees reduced the cost of token distribution, multichain patterns gave communities greater network flexibility, and dedicated interfaces made voting, token claims and staking easier to use.
That is the difference between delivering contract code and delivering a blockchain product.
Building a DAO Product That Needs More Than a Governance Contract?
Whether you are designing governance, token distribution or staking mechanics, Neti can help you connect the smart contracts, application architecture and user experience into one production-ready product.
Frequently Asked Questions
What did Neti build for FactoryDAO?
Neti helped FactoryDAO deliver three DAO applications: Influence.Vote for multichain governance, Bank.Vote for scalable token distributions and Yield.Vote for staking and liquidity incentives. The scope included smart contracts, blockchain integrations and user-facing web applications.
How did Neti reduce the cost of large token airdrops?
Neti used a Merkle Tree-based model. Instead of storing the complete list of recipients on-chain, Bank.Vote stored one Merkle root. Each eligible wallet could then prove its allocation using a Merkle proof, reducing blockchain storage and transaction costs.
What does a DAO development company deliver beyond smart contracts?
A DAO development company can provide end-to-end blockchain dApp development, including governance architecture, voting mechanics, wallet integrations, frontend applications, multichain support and transaction handling.
