
The AVICI token is public, and MetaDAO records a passed team incentive proposal worth up to 8.24 million AVICI, or 25% of supply, if price milestones are met. That record does not support a zero tokenomics claim or identify institutional investors behind the project.
Founders researching Avici tokenomics need to separate token terms, product partners, and fundraising evidence. I checked MetaDAO’s current company profile and Avici’s official documentation on October 27, 2026.
The sources name product providers, but do not publish a list of institutional investors or strategic investment partners. They also do not disclose the full token allocation or show whether the proposal has paid out.
On-Chain and Data Findings
Avici token: what the current public record shows
For readers looking up the Avici token, MetaDAO identifies the asset as AVICI and links its token contract to a Solana market page. Its profile records a passed proposal dated March 30, 2026. The proposal creates a team performance package that could pay up to 8.24 million AVICI, or 25% of supply, if specified price milestones are reached.
The proposal is a documented incentive plan, not proof that the maximum amount was earned or paid. MetaDAO labels its outcomes market-resolved. The profile does not provide a complete allocation table, vesting schedule, or wallet-level distribution analysis. I therefore treat the proposal as evidence against a blanket claim of zero team-linked token incentives, not as a full account of tokenomics.
Avici’s official homepage currently positions the product as a secured credit card backed by crypto. It describes spending crypto without selling it and labels some product features “Coming Soon.” That page shows the company’s current public positioning. It does not prove that every feature is live, available in every region, or used by the people in MetaDAO’s growth claim.

Zero tokenomics: what the record says about allocation
The phrase “zero tokenomics” does not describe the public record now available. MetaDAO’s passed proposal links up to 25% of AVICI supply to a team performance package. The terms are conditional on price milestones, and the profile does not establish that any maximum payout occurred.
This is narrower than a complete allocation answer. The sources reviewed do not show all recipient categories, vesting terms, circulating supply, or wallet balances. I cannot verify a zero team allocation, but I also cannot infer total team ownership from one conditional proposal. The accurate conclusion is that a team-linked incentive exists in the recorded proposal, while overall allocation remains undisclosed in the sources checked.
A tokenomics analysis needs records that match the claim. Allocation requires a supply breakdown and relevant wallet or contract evidence. Vesting requires the schedule and unlock rules. Price performance needs a dated market source and a clear start and end point. Usage needs a defined event, period, and denominator. A number without those details may sound precise while remaining hard to test.
Pattern Recognition
Institutions and strategic partners: what Avici names publicly
Readers searching for Avici investment institutions and strategic partners can verify named product providers, but I found no public list of institutional investors on the company profile or in the reviewed documentation. Avici’s docs say its Visa credit cards are issued by Third National and describe virtual bank accounts powered by Iron, with Bridge linked as the provider. These are product relationships, not evidence of an investment round or strategic equity backing.
MetaDAO’s company profile shows Avici’s fundraising and governance record on its platform. It displays $3.5 million raised and a $3.3 million valuation when checked on October 27, 2026, while directing readers to the lifecycle record for authoritative fundraise terms. Those figures do not name investors. A platform record and a partner list answer different questions.
The same distinction matters when testing distribution. A founder would need to connect investor status with product events, then measure onboarding, first meaningful use, repeat activity, and referrals across defined cohorts. The public pages reviewed do not provide that user-level evidence.

A second pattern is the gap between a proposal and its execution. A conditional token incentive states what may be paid if milestones are met. It does not establish how much was ultimately received.
A third pattern is that product partners and investors are different categories. A card issuer or account provider can help operate a product. Neither relationship proves institutional investment, token ownership, or product adoption. Each claim needs evidence from the system that produced it.
Strategic Interpretation
For a founder, Avici is best treated as a case with partial token and partner evidence, not as a complete launch template. The public record identifies a conditional team incentive and product providers, but leaves the full allocation and investor roster open.
Key insight
A passed incentive proposal can describe a conditional token commitment, but only payout and allocation records can show what the team received.
That distinction changes how a team should plan. Before fundraising, record the terms, eligible recipients, milestone definitions, payout conditions, and on-chain evidence that will confirm delivery. For partner claims, label each relationship by function: issuer, payments provider, investor, or strategic adviser.
A zero team allocation can sound like a strong alignment signal, but it should only be stated when public records support it. Identify the supply source, allocation categories, wallet attribution method, and observation date. If those records are missing, say what remains unknown.
The case also shows why source quality belongs beside the result. MetaDAO is an interested platform describing a company that raised there. Its account is relevant, but readers should know who made the statement and what it does not establish. That is enough to preserve the claim without turning it into independent proof.
Growth Framework: Test the Investor-to-User Path
Teams can assess this kind of launch with a short evidence sequence. The goal is to link each conclusion to a source and a defined behavior.
| Question | Evidence to collect | What it can show | Limit to state |
|---|---|---|---|
| What was allocated? | Token documents, supply records, wallet analysis | Documented allocation categories | Wallet labels may be incomplete |
| Did investors become users? | Investor list linked to product activation events | Investor-to-user conversion | Correlation does not prove the raise caused use |
| Did users return? | Cohort activity with a defined event and period | Repeat use and retention | Metric choice changes the result |
| Did referrals matter? | Referral source and referred-user activation | Measured referral contribution | Self-reported referrals can miss other sources |
Start with the claim. Write down exactly what it says, who said it, and what date or period it covers. Then identify the system that could produce the evidence. A token contract may support supply analysis. Product analytics may support activation and retention. A founder interview can explain intent, but it does not replace usage records.
Next, define the denominator. “Investors who became users” needs a count of eligible investors and a rule for what qualifies as a user. “Retention” needs a return event and a time window. “Referral growth” needs a method to attribute new users to a referrer. If those definitions are not public, mark the result as unknown rather than filling the gap with an estimate.
Finally, compare cohorts and report limits. Investor users can be compared with users from other channels, but differences may reflect prior motivation or access. A comparison does not prove causality on its own. If the data supports only a descriptive result, state that clearly and use it to shape the next test.
- Record the original source and check date.
- Separate token allocation from product adoption.
- Define activation, repeat use, and referral before counting.
- Compare groups over the same observation window.
- Publish the denominator and any missing data.
FAQ
What is the Avici token?
MetaDAO identifies AVICI as Avici’s token and links its contract from the company profile. The same profile records a passed performance proposal with conditional token incentives, but it is not a complete allocation table.
Did Avici have zero team allocation?
The public record does not support a blanket zero team-linked incentive claim. A passed MetaDAO proposal allows up to 8.24 million AVICI, or 25% of supply, if price milestones are met. It does not show whether that maximum was paid.
Which institutions and strategic partners are named publicly?
Avici’s docs name Third National for card issuance and Iron, with Bridge linked for virtual accounts. I found no public institutional investor roster in the company profile or the reviewed docs. Product providers should not be described as investors.
What does MetaDAO report about Avici’s fundraising?
Its profile displays $3.5 million raised and a $3.3 million valuation on October 27, 2026. MetaDAO says authoritative terms come from the lifecycle record, and the profile does not list investor names.
Closing
The public record now answers part of the tokenomics question: Avici has a conditional team performance proposal, but the full distribution and investor roster remain unavailable in the sources reviewed. A payout record and complete allocation schedule would sharpen the case.
I’ll keep those gaps explicit. For a structured review of your protocol’s growth system, see my Web3 Growth Audit.
References
- MetaDAO, Avici company profile, token, proposal, and fundraising display, checked October 27, 2026.
- Avici official documentation, product providers, checked October 27, 2026.
- Avici, official product homepage, checked October 27, 2026.
- DeFi launch frameworks.
- Web3 SEO guide.
Need a clearer token and growth evidence base?
I review the claims, data sources, and measurement gaps a Web3 growth team can defend.
Explore the Web3 Growth Audit