Public production documentation

Live utility on Base today. Governed ownership for the next stage.

MapleFi AIONEX is a non-custodial Base-mainnet liquidity intelligence and swap workspace. It compares supported Uniswap and Aerodrome routes, explains route conditions before a wallet signature, and is being structured for a single MetaDAO ownership coin rather than fragmented EVM and Solana tokens.

● Base mainnet liveBase chain ID 8453Uniswap v3 + Aerodrome ClassicNo active supported MapleFi token

Open live route workspace ↗Ownership strategy Submitted raise model Meet the team ↗

Base LIVEProduction network

2 venuesDirect route comparison

0% betaAIONEX interface fee

5 factorsExplainable route score

The thesis

ProductIntelligence before execution

Users inspect depth, impact, activity, venue coverage and data availability before they decide to connect and sign.

EconomicsOwn the decision layer

AIONEX does not need to claim third-party TVL. It can own the interface, methodology, data products and partner relationships.

OwnershipOne economic unit

The proposed MetaDAO coin would govern treasury, IP, revenue policy and future issuance while the product remains Base-first.

AIONEX is not positioned as another token-first DEX. It is positioned as explainable liquidity intelligence, direct execution context and programmable market infrastructure.

What is live, and what is proposed

Capability	Status	Public position
Base route intelligence	Live	Public pair analysis, score components, timestamps and limitations.
Direct DEX execution	Live	Verified Uniswap v3 and Aerodrome Classic router paths; user signs in wallet.
Liquidity explorer	Live	Supported exact-pair liquidity and external venue activity, not MapleFi-owned TVL.
Agent/API product	Direction	REST-first, timestamped intelligence designed for future Base apps and agents.
MetaDAO ownership coin	Proposed	Canonical Solana ownership coin; no sale or contract is live.
Additional chains	Evaluation	One governed expansion at a time after Base reliability and demand are proven.

Built for users, reviewers and partners

Users

Clear route evidence, slippage protection and wallet-controlled execution.

MetaDAO

A working crypto product, public team and a clean single-token ownership plan.

VCs

Capital-efficient product, proposed governance protections and multiple revenue paths.

Ecosystems

Composable market intelligence that can support wallets, DEXes, launch platforms and chains.

Current production scope

What MapleFi AIONEX has live on Base mainnet.

The current product is Base-specific and product-first: public intelligence without a wallet, direct route comparison across supported venues, user-controlled slippage, wallet-signed execution and BaseScan verification.

Open product ↗Liquidity explorer ↗Execution guide ↗

8453Base chain ID

Public firstNo wallet for research

Direct routesDEX router execution

WhitelistPublished token set

Observe → Compare → Execute → Verify

Observe

Select a supported pair and review liquidity, activity, venue coverage and freshness without a wallet.

Compare

Enter an amount and compare expected output, protected minimum, impact and score evidence.

Execute

Connect only when ready; confirm Base, allowance target, route, gas and minimum output.

Verify

Review transaction status, route used and the final BaseScan record after confirmation.

Supported production venues

Uniswap v3SwapRouter02

Direct quote and execution path through the verified Base router.

0x2626664c2603336E57B271c5C0b26F421741e481

AerodromeClassic Router

Direct quote and execution path through the verified Base router.

0xcF77a3Ba9A5CA399B7c97c74d54e5b1Beb874E43

Base utilityCanonical WETH

ETH/WETH wrap utility uses Base’s canonical wrapped Ether contract.

0x4200000000000000000000000000000000000006

Current execution is direct multi-venue comparison. External aggregator integrations may be added later through adapters, but they are not presented here as live production capability.

Production boundaries

Non-custodial

MapleFi does not take custody of user funds and never requests seed phrases or private keys.

External liquidity labelled

Displayed liquidity and volume belong to supported third-party Base venues and are not MapleFi-owned TVL.

0% interface fee in beta

DEX and gas costs may still apply. Any future AIONEX fee requires clear disclosure and governance policy.

No guarantee

A score describes observed conditions. It does not guarantee best execution, safety or future outcomes.

Explainable market context

A score should show its evidence.

AIONEX translates fragmented liquidity and quote data into a reviewable route-health context. The score is accompanied by components, reason codes, retrieval time and limitations rather than presented as an unexplained recommendation.

Open intelligence page ↗Compare a live route ↗

30%Liquidity depth

25%Estimated impact

15% × 3Activity, coverage, data

TimestampedFreshness visible

Current market-intelligence methodology

Liquidity depth

30%

Estimated price impact

25%

Market activity

15%

Venue coverage

15%

Data availability

15%

Route Health = 0.30D + 0.25I + 0.15A + 0.15V + 0.15FD = depth · I = impact quality · A = activity · V = venue coverage · F = data availability/freshnessIllustrative check: 0.30(92) + 0.25(88) + 0.15(76) + 0.15(82) + 0.15(91) = 86.95 → 87

Weights describe the current methodology and may be versioned as real usage, testing and partner feedback improve calibration. The 87-point example is illustrative and is not a live quote or safety certification.

Execution math users can verify

Protected minimum

minimum = quote × (1 − slippage)

Example: 1,000 USDC expected with 0.5% tolerance gives a 995 USDC protected minimum.

Price impact

impact% = (reference − execution) ÷ reference × 100

Impact is trade-size dependent and should be refreshed before execution.

Data freshness

age = now − snapshot timestamp

Stale data lowers confidence and should trigger a new comparison.

Human-readable today, agent-readable next

AIONEX already structures pair, trade-size, venue, score-component, freshness and reason-code context. The next product layer is a REST-first interface for wallets, partner applications and AI agents.

The agent direction is data infrastructure, not an autonomous trading promise. Users or integrating applications remain responsible for execution policy and transaction approval.

GET /api/v1/base/pairs/WETH/USDC/intelligence
{
  "network": "base",
  "pair": "WETH/USDC",
  "tradeSize": "1 ETH",
  "routeHealth": 87,
  "components": {"depth":92,"impact":88,"activity":76,"coverage":82,"freshness":91},
  "timestamp": "...Z",
  "reasonCodes": []
}

Composable infrastructure

Base-first implementation. Adapter-driven expansion.

The architecture separates market data, normalization, intelligence, execution and verification so new venues or chains can be evaluated without rewriting the entire product.

DataPairs, pools, activity

NormalizeComparable route objects

ExplainScores and reason codes

ExecuteUser-approved actions

Layered product stack

Market data

Exact-pair references, venue liquidity, activity, block and retrieval time.

Normalization

Convert venue-specific results into one comparable route and pair schema.

Intelligence

Apply score components, reason codes, freshness and product boundaries.

Execution

Validate network, approval target, minimum output and transaction destination.

Core normalized objects

Chain manifest

Chain ID, native currency, RPC/explorer, supported venues, contracts and feature flags.

Route object

Venue, expected output, minimum output, gas context, spender, target, expiry and warnings.

Pair snapshot

Observed depth, activity, coverage, impact context, block reference and freshness.

Trust record

Official addresses, review status, known limitations, incident status and version history.

net execution value (USD) = output value (USD) − disclosed interface fee (USD) − estimated gas cost (USD)AIONEX-routed volume = Σ USD value of one side of each unique confirmed swap initiated through AIONEX

24h venue volume = Σ unique exact-pair pool volume reported for the window; do not add both swap legs or duplicate the same pool/feed

Accounting boundary: Third-party venue volume is market context, not MapleFi revenue or AIONEX-routed volume. AIONEX attribution requires a unique transaction hash initiated through the product, one-side USD notional, a consistent execution-time valuation and duplicate removal.

Where defensibility compounds

Methodology

Versioned route-health logic, calibration history and explainable reason codes.

Data history

Time-series route, depth, impact, freshness and execution-quality observations.

Distribution

Embedded partner widgets, APIs, ecosystem integrations and trusted public market pages.

AI-assisted interpretation & intellectual property

Real-time market evidence, translated into decision context.

AIONEX combines timestamped Base-market data with AI-assisted interpretation workflows. MapleFi states that Microsoft AI models and services are used in those workflows; this does not imply Microsoft investment, certification, partnership or endorsement.

Public AI wording and team ↗

Real-time dataOnchain and venue context

AI-assistedInterpretation workflow

ExplainableReason codes visible

IP captureCounsel-review workstream

What AI does—and does not do

RoleInterpret and explain

Translate route, liquidity, impact, freshness and warning inputs into concise human-readable context.

BoundaryNot an oracle of outcomes

AI does not guarantee safety, price performance, execution quality or loss prevention.

EvidenceInputs remain visible

Scores are accompanied by components, timestamps, venue scope and limitations.

ControlUser signs every action

The wallet remains the final approval layer for supported onchain transactions.

Patent-readiness and IP workstream

MapleFi can prepare a formal IP package around the system architecture and documented methods. This is a readiness program for professional prior-art, patentability and legal review—not a claim that a patent has been filed or granted.

Pre-signature intelligence flow

Observe, normalize, score, explain, execute and verify as one reviewable workflow.

Cross-venue confidence model

Weighted route context combining depth, impact, activity, coverage and data quality.

Agent-readable evidence

Timestamped route context with reason codes and explicit limitations for programmable consumers.

Public wording: “Patent-readiness workstream in progress.” Do not use “patented,” “patent pending” or “proprietary patent” unless supported by a formal filing or grant.

IP proposed for governed ownership

AIONEX software and product repositories assigned or exclusively controlled under the project structure.
MapleFi/AIONEX domains, brand assets, data methodologies and related documentation.
Revenue rights from interfaces, APIs, integrations and partner products.
Future patents or applications created for the governed project, subject to legal structuring.

Proposed MetaDAO architecture

One canonical ownership coin. Product execution across governed chains.

The recommended structure is not an EVM utility token plus a separate Solana governance token. It is one canonical ownership coin launched through MetaDAO on Solana, with AIONEX continuing on Base and any future EVM representation approved through governance.

Proposed, not launchedProduct remains Base-firstNo independent second token

1 tokenCanonical economic unit

SolanaMetaDAO ownership layer

BaseLive product execution

GovernedIP, treasury, revenue

Recommended structure

MetaDAO · Solana

Canonical MapleFi AIONEX ownership coin

Market-governed treasury
Mint authority and future issuance
IP and domain control
Revenue and operator policy

governs⇄services

Base & future EVMs

AIONEX product and execution layer

Base-mainnet route intelligence
Direct supported DEX execution
Partner APIs and widgets
Governance-approved expansion

Data Intelligence Protocol Inc. can remain the operating and development service provider under a documented budget, deliverables, IP and replacement framework.

What ownership must mean

Treasury control

Accepted raise capital is governed; the team receives an approved monthly operating budget.

Revenue alignment

Base and future chain revenues follow a public policy controlled by the project structure.

IP enforceability

Software, domains and brand rights cannot remain economically detached from the ownership coin.

Mint discipline

No team-controlled hidden inflation; future issuance requires transparent governance.

Operator accountability

Major contracts, spending and replacement rights are documented rather than implied.

Cross-chain discipline

Any EVM representation shares one supply model and does not compete with the canonical coin.

Legacy MPFI and future ticker treatment

LegacyDeprecated and unsupported

Any previous MPFI contract is not part of the current AIONEX product, future governance or proposed token economics.

FutureMPFI remains a proposed ticker

Final name, ticker, legal treatment and mint address require MetaDAO, legal and collision review before publication.

There is no active supported MapleFi native token and no new token contract is announced in this document. Users should ignore unofficial migration, claim or presale messages.

Submitted MetaDAO fundraising configuration

$750K minimum. $40K monthly budget. 15-month baseline.

The MetaDAO application submitted on July 29, 2026 uses one defensible minimum-case model. It is designed to fund Base reliability, security work, measurable product analytics, API commercialization and partner integrations without publishing a separate target or ceiling as though additional acceptance were guaranteed.

Application submittedMinimum $750KMonthly budget $40K15-month baseline runway

4 daysStandard commitment window

10MTokens to sale participants

20%Treasury-provided USDC to LP

2.9MTokens paired for liquidity

Submitted minimum-case math

Application-aligned configuration

Accepted minimum$750,000

Initial LP funding · 20%$150,000

Governed operating treasury$600,000

Runway at $40K / month15 months

Initial liquidity contribution = $750,000 × 20% = $150,000Operating treasury after initial liquidity = $750,000 − $150,000 = $600,000Baseline runway = $600,000 ÷ $40,000 per month = 15 monthsMetaDAO monthly-budget limit = $750,000 ÷ 6 = $125,000; proposed budget uses 32% of that limit

MetaDAO’s standard sequence places accepted USDC in the market-governed treasury, which then provides 20% of accepted USDC plus 2.9M tokens to liquidity. This baseline excludes the optional experimental bid wall; selecting it would require a separate allocation model and disclosure.

Budget and runway sensitivity at the submitted minimum

Monthly operating budget	Runway from $600K treasury	Position
$30,000	20 months	Illustrative lower-spend case
$40,000	15 months	Submitted application budget
$50,000	12 months	Illustrative sensitivity only
$60,000	10 months	Illustrative sensitivity only

These rows change only the operating-budget assumption. The submitted minimum raise remains $750,000 and the submitted monthly operating budget remains $40,000.

Runway sensitivity

Submitted accepted-minimum reference$750,000

Monthly operating budget $40,000

ICO price reference$0.075

USDC to initial LP$150K

Operating treasury$600K

Runway15.0 mo

Configured reference FDV$1.57M

Budget vs. allowed maximum$40K / $125K

Submitted $600K operating-treasury mandate

40% · $240KEngineering, security & reliability

Production hardening, independent review, wallet flows, route integrity, monitoring and execution reliability.

18% · $108KData & infrastructure

RPCs, indexing, provider services, observability, storage and production API operations.

12% · $72KProduct, mobile UX & calibration

Mobile wallet reliability, accessibility, analytics and route-intelligence calibration.

12% · $72KEcosystem integrations

Partner pilots, integration engineering, documentation and developer support.

10% · $60KLegal, IP, tax & structuring

Entity and operator structure, IP assignment, tax, regulatory and cross-chain review.

8% · $48KSecurity and operating contingency

Unexpected infrastructure, security, compliance or production requirements.

$240K + $108K + $72K + $72K + $60K + $48K = $600K40% + 18% + 12% + 12% + 10% + 8% = 100%

Why the structure remains accountable

Discretionary acceptance

Commitments can exceed the amount accepted; final allocations and refunds are pro rata under MetaDAO’s mechanism.

Monthly operating control

Normal operations use the disclosed budget. Larger spending and new issuance require governance action.

One governed value system

IP, treasury, revenue policy and mint authority are intended to remain economically connected to the ownership coin.

Proposed application-aligned single-token model

High market availability. No team liquidity at launch.

This remains a discussion configuration rather than final token terms. The reference model uses 10M sale tokens, 2.9M liquidity tokens and an 8M price-based performance package, with all economics unified around one canonical ownership coin.

20.9M configured reference supply12.9M market-available reference8M performance packageNo team unlock at launch

47.8469%Sale participants / configured supply

13.8756%Liquidity / configured supply

38.2775%Performance package / configured supply

77.52%Sale share of market-available supply

Proposed configured allocation

20.9Mconfigured reference supply

Sale participants10.0M · 47.8469%

Initial market liquidity2.9M · 13.8756%

Price-based performance package8.0M · 38.2775%

Configured reference supply = 10.0M + 2.9M + 8.0M = 20.9M tokensInitial market-available reference = 10.0M + 2.9M = 12.9M tokensSale-participant share of market-available reference = 10.0M ÷ 12.9M = 77.5194%At $750K accepted: ICO price reference = $750,000 ÷ 10,000,000 = $0.075Configured reference FDV = 20.9M × $0.075 = $1,567,500

“Configured reference supply” includes the unearned 8M performance package. It is not a statement that all 20.9M tokens are circulating. Percentages are displayed to four decimal places to avoid a rounding total above or below 100%.

Proposed performance-package thresholds

Tranche	Threshold	Tokens	Price at $0.075 ICO reference	Earliest process
1	2×	1.6M	$0.15	After month 24, then 3-month TWAP
2	4×	1.6M	$0.30	After month 24, then 3-month TWAP
3	8×	1.6M	$0.60	After month 24, then 3-month TWAP
4	16×	1.6M	$1.20	After month 24, then 3-month TWAP
5	32×	1.6M	$2.40	After month 24, then 3-month TWAP

8.0M ÷ 5 equal tranches = 1.6M tokens per tranche

Earliest possible completion if a threshold is sustained: approximately month 27, subject to final MetaDAO rules and successful TWAP measurement

The proposed 8M package is below MetaDAO’s documented maximum of 12.9M. No performance-package token is treated as liquid or earned merely because time has passed; the applicable price threshold and measurement process must also be satisfied.

Token design principles

No independent EVM sale

Future EVM availability should represent the same canonical economic asset and unified supply, subject to bridge, legal and governance review.

No hidden allocation

Any guaranteed strategic allocation, advisor arrangement or future issuance must be disclosed and governed.

No contractual hard-cap claim

The configured reference supply is not an immutable token-program cap. Future issuance requires a public governance proposal.

Long-term business model

Revenue can grow from product use, not token speculation.

AIONEX can monetize transparent execution, market intelligence, partner integrations and programmable data. Current beta interface fees are 0%; any future fee policy should be disclosed and governed.

0% nowBeta interface fee

B2COptional route fee

B2BMonitoring and widgets

APIAgent and data access

Revenue pathways

Interface execution fee

A small transparent basis-point fee on eligible routes after beta, subject to governance and competitive execution.

Liquidity intelligence API

Paid access for wallets, agents, funds and applications requiring normalized route and pair context.

Partner monitoring

Recurring dashboards and alerts for projects, launch platforms, ecosystems and treasury teams.

Embedded widgets

White-label route-intelligence, market-card and execution components for partner interfaces.

Integration services

Chain, DEX, wallet or launch-partner implementation packages and ongoing support.

Enterprise intelligence

Custom datasets, historical analysis, route-quality reports and risk-context feeds.

Illustrative revenue calculator

interface revenue = routed volume × fee bps ÷ 10,000total monthly revenue = interface revenue + partner revenue + API revenueillustrative annual run rate = total monthly revenue × 12

Monthly routed volume ($)

Interface fee (bps)

Monitored partners

Average partner fee ($/mo)

API customers

Average API fee ($/mo)

Interface revenue$5,000

Partner revenue$12,500

API revenue$9,000

Total monthly$26,500

Illustrative annual run rate$318,000

Illustrative stage	Volume + fee	B2B assumptions	Monthly total
Validation	$2M × 3 bps = $600	10 × $250 + 1 API × $1,500	$4,600
Growth	$10M × 5 bps = $5,000	25 × $500 + 3 APIs × $3,000	$26,500
Scale	$50M × 5 bps = $25,000	60 × $750 + 8 APIs × $5,000	$110,000

These are mathematical illustrations, not forecasts or guaranteed outcomes.

Revenue alignment under ownership governance

Revenue generated on Base or any future chain should follow a disclosed policy covering operating costs, security reserves, treasury inflows and approved ecosystem incentives. It should not be privately detached from the ownership coin.

Governed multichain roadmap

Prove Base. Productize the data. Expand one chain at a time.

AIONEX is live on Base. Additional EVM chains are candidates, not commitments. Solana is proposed as the MetaDAO ownership layer; it does not require abandoning Base execution.

Stage 0Base live today

Stage 1Reliability + API

Stage 2Partner pilots

Stage 3One governed EVM

Execution roadmap

Live now

Base-mainnet intelligence and direct execution

Uniswap v3 and Aerodrome Classic route comparison, public liquidity context, wallet-signed actions and BaseScan verification.

Next operating phase

Base hardening and measurable adoption

Security review, mobile reliability, observability, execution analytics, methodology calibration and public KPIs.

Commercial phase

REST-first data and partner products

API pilots, embedded widgets, monitoring dashboards and partner case studies.

Governance proposal

Select one additional EVM chain

Deploy only after route coverage, users, infrastructure, partner value and operating cost pass the scorecard.

Later

Governance-approved cross-chain ownership representation

Extend the canonical ownership asset only after bridge, supply, legal and security reviews.

Chain selection scorecard

Liquidity and route coverage

30%

User and wallet access

20%

Infrastructure reliability

15%

Partner and ecosystem support

15%

Fees and user experience

10%

Legal and operational fit

10%

Expansion categories—not launch announcements

High-liquidity EVM environments

Evaluate only where route depth, wallet access, infrastructure maturity and partner distribution support a measurable product case.

Partner-led institutional or ecosystem pilots

Consider integrations where a chain, wallet, launch platform or project can supply technical support, distribution and verifiable demand.

Solana product research

Ownership governance on Solana does not automatically imply a Solana execution launch; product integration requires its own evidence, security and operating review.

No additional chain, bridge, token representation, integration, partnership or launch date is announced in this documentation.

Public, bootstrapped builders

A visible team behind a working Base product.

MapleFi states that development has continued since December 2025 through founder-funded, bootstrapped work. The public team page identifies product, operations, community and engineering responsibilities.

Open direct team diligence page ↗Review the product ↗

Since Dec 2025Continuous development

Founder-fundedBootstrapped build

Canada builtOperating company

Public rolesTeam diligence

Core public team

Founder & CEORahul Sharma

Product vision, security architecture, AI intelligence direction and ecosystem strategy.

Project OfficerNeeraj Bhardwaj

Delivery, release readiness, partnerships, roadmap tracking and operational coordination.

Leadership & OperationsBhavya Sharma

Documentation quality, internal workflows, team alignment and execution systems.

Community ManagerMr. Sutik

Community communication, user onboarding and ecosystem engagement.

Senior Software DeveloperAndre

Frontend systems, wallet flows, APIs, blockchain integrations and performance.

DiligenceVerify on the official page

Names, photos, biographies and future updates should be checked from MapleFi’s direct team page.

What MapleFi is seeking

MetaDAO review

Ownership structure, raise configuration, IP transfer and public launch readiness.

Security partners

Architecture review, direct-route testing, wallet safety and production monitoring.

Base ecosystem

Technical feedback, ecosystem listing, wallet integrations and product visibility.

Data design partners

Wallets, agents, funds and applications that need explainable liquidity context.

Launch and project partners

Market pages, monitoring, route widgets and post-launch liquidity analytics.

Future chain teams

One evidence-based expansion after Base KPIs and integration value are demonstrated.

Official channels

Trust through explicit boundaries

Transparent about what is reviewed, live and not yet complete.

AIONEX is non-custodial and uses verified third-party Base routers for supported direct execution. A formal external MapleFi audit has not yet been published, so the product must not be represented as audited.

Open live security status ↗System status JSON ↗

Non-custodialUser-controlled wallet

Verified routersThird-party contracts

No audit yetFormal report unpublished

No token liveNo active supported contract

Current security model

Control	Current treatment	User-visible outcome
Wallet custody	Users retain keys and sign actions directly.	No deposits into a MapleFi custodial wallet.
Network control	Execution requires Base mainnet, chain ID 8453.	Wrong-network prompts before action.
Router verification	Supported direct routes use published Uniswap and Aerodrome addresses.	Users can compare wallet destination with BaseScan.
Slippage protection	User-controlled tolerance generates a protected minimum.	Minimum output is visible before signing.
Public intelligence	Market research works without wallet access.	Wallet connection is delayed until account data or execution is needed.
Fee disclosure	AIONEX interface fee is 0% in beta.	No hidden AIONEX interface charge; DEX/gas costs may apply.

Review status

PublishedProduct boundaries and router links

Live security page identifies the external contracts and states that no audit report is published.

Required before scaleIndependent security review

Review route construction, approval handling, quote integrity, frontend supply chain and incident procedures.

Required before tokenOwnership and contract audit

Governance, cross-chain, vesting, mint and treasury contracts require dedicated review.

OngoingStatus and incident communication

Maintain public service status, known limitations and time-stamped updates.

Public disclosures

AIONEX information is not investment advice and does not certify token, pool or route safety.
Markets and onchain state can change after a snapshot and before transaction confirmation.
External DEXes, RPCs, wallets, APIs and bridges are independent systems with their own risks.
No new MapleFi token contract, sale, migration or claim is announced in these documents.
The MetaDAO application has been submitted, but the raise and token parameters remain proposed, subject to review, and are not a live sale, offer or commitment.
Microsoft AI usage does not imply Microsoft investment, partnership, certification or endorsement.
Patent-readiness language does not mean a patent has been filed or granted.

Official references

Verify the product, team, contracts and MetaDAO mechanics.

These links support the public statements and planning mechanics in this documentation. Live values and final launch parameters should always be rechecked before publication or execution.

MapleFiLive product sources

BaseScanContract verification

MetaDAOOfficial mechanics

July 29Documentation date

MapleFi official product resources

MapleFi AIONEX overview ↗

Base-mainnet product position, route methodology, live boundaries and product links.

Route workspace ↗

Supported direct route comparison and wallet-signed execution flow.

Liquidity explorer ↗

Exact-pair liquidity, volume, impact and freshness context.

Intelligence dashboard ↗

Explainable route-health evidence and agent-ready direction.

Security status ↗

Router links, review state and trust boundaries.

Public team page ↗

Team identities, roles, bootstrapped history and Microsoft AI wording.

MetaDAO official references

The ICO ↗

Four-day commitments, discretionary acceptance, 10M sale tokens, treasury-provided 20% USDC plus 2.9M tokens for liquidity, and the optional performance package.

Getting listed ↗

Minimum raise, monthly budget limit, performance configuration and IP requirements.

Are you ready? ↗

Working-product fit, public communication and KPI expectations.

Governance proposals ↗

Treasury spending, token issuance, metadata and liquidity controls.

Investor protections ↗

Market-governed treasury and legal alignment of business revenue and IP.

Optional bid wall ↗

Experimental alternative that changes treasury allocation above the minimum goal.

Base contract references

Uniswap SwapRouter02 ↗

0x2626664c2603336E57B271c5C0b26F421741e481

Aerodrome Router ↗

0xcF77a3Ba9A5CA399B7c97c74d54e5b1Beb874E43

Base WETH ↗

0x4200000000000000000000000000000000000006

Public system status ↗

Machine-readable MapleFi service status endpoint.

Version note

Version 7.1 · Updated July 29, 2026 after MetaDAO application submission. The financial model now matches the submitted $750,000 minimum, $40,000 monthly budget, $600,000 operating treasury and 15-month baseline. Token-price, FDV and performance-threshold math use the same $0.075 ICO reference. Volume attribution, net-value formulas, initial market availability and public claim boundaries were also tightened.