Mayflower AI
Mayflower AI — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
Mayflower AI — an AI/Agents / DeFi project on Solana, token (symbol: MAY).
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: an AI browser extension (“AI Navigator”) and an AI co‑pilot for simplifying interaction with DeFi (per the litepaper).
- Who it’s for: DeFi users (especially on Solana) who need an “AI assistant” for analyzing and executing onchain actions.
- Why onchain/token: onchain is needed for executing transactions and DeFi actions; the MAY token is the ecosystem’s governance token (per the litepaper).
How it works (very briefly)
- The user does: sets an intent (for example, “find low‑risk USDC yield” or “make a swap”) in the extension.
- The system does: provides AI insights, analyzes the transaction/contract and guides the user through a safe flow; in the future — automates actions (“Titan AI”).
- The user gets: hints/analytics and simplified execution of onchain actions.
- Where the blockchain is: Solana (execution of swap/supply/withdraw and other DeFi actions), the MAY token (SPL).
- Token role (if any): governance; expansion of the utility — via governance per the roadmap.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Mayflower AI |
| Also known as (aliases) | MAY; Mayflower AI Navigator |
| Logo (logo) | ../assets/181_mayflower-ai_logo.svg |
| Token symbol (ticker) | MAY |
| Category | AI/Agents | DeFi |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | 2025 |
| Project status (status) | in development |
| Token (standard) | SPL |
| Token contract | FJz7ptUR1FwxSHbb8Sfd5Cn6Zt4TqucJZKLqU4n66gdq |
| Token model (token_type) | utility (governance) |
| Max supply | 1,000,000,000 MAY (fixed) |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | 1:1 migration NPT→MAY; mint/freeze revoked (per the litepaper) |
| Governance | DAO/Foundation treasury (per the litepaper) |
| Admins/keys | mint/freeze authority revoked (per the litepaper) |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI co-pilot for DeFi + on-chain actions |
| Use‑case (use_case) | help + automation of DeFi actions |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 0 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://mayflower.fyi/ |
| Docs | https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf |
| GitHub | https://github.com/Neopin/Contracts |
| Releases / Changelog | https://medium.com/neopin-official |
| Whitepaper | https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://solscan.io/token/FJz7ptUR1FwxSHbb8Sfd5Cn6Zt4TqucJZKLqU4n66gdq |
| X | https://twitter.com/Mayflower_AI |
| Discord | https://discord.com/invite/mayflowerai |
| Telegram | https://t.me/neopin_eng |
| Medium | https://medium.com/@mayflowerai |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/neopin |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/mayflower-ai/ |
General project overview
Mayflower AI describes the “AI‑Navigator” as a browser extension that helps the user explore DeFi, analyze transaction risks and execute onchain actions. The litepaper contains a roadmap for 2025 (test agent, testnet core actions, mainnet MVP, etc.).
Features/modules
Getting started (wallet/network)
- What you need: a browser/extension (as it launches) and a Solana wallet.
- Network/chain: Solana.
- Fees: Solana fees for onchain actions.
AI component of the project
- What is real AI here? an AI assistant/co‑pilot that answers questions, provides insights and helps execute onchain actions (described in the litepaper).
- What is truly onchain? execution of swap/supply/withdraw and other actions on Solana + the MAY token.
- Why is a token needed? governance; expansion of the utility — via governance (per the litepaper).
- Red flags (based on the information found): there are no public quality metrics/benchmarks yet; many “future” features per the roadmap.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as a product feature (AI_1), not only an “intent”.
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): there is a description of AI features → AI_1.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI Navigator provides insights and helps analyze/execute DeFi actions, including “transaction analysis” and guided execution (described).
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): there are specific features and scenarios.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): the roadmap mentions a “Test Agent/closed testnet”, but there is no public demo “via a link” in this card.
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): plans/stages ≠ a public demo.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): quality metrics are not published.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): there is a product architecture/stages, but no technical description at the level of models/versions/benchmarks.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient artifacts for AI_4=1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: MAY mint: FJz7ptUR1FwxSHbb8Sfd5Cn6Zt4TqucJZKLqU4n66gdq
- Evidence: Tier‑1 — https://solscan.io/token/FJz7ptUR1FwxSHbb8Sfd5Cn6Zt4TqucJZKLqU4n66gdq
- Why sufficient / why not (one line): the token and its parameters are verifiable in the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: the product describes the execution of DeFi actions (swap/supply/withdraw) as a key part.
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): onchain actions beyond the token are explicitly described.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: onchain is needed for DeFi, but the “criticality” as a trustless property for the AI layer itself is not proven.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficiently strict argument for OC_3=1.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the MAY token exists.
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): described in the litepaper and there is an onchain mint.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): a payment necessity of the token for the operation of AI Navigator is not recorded in the litepaper as mandatory.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): the token is designated as governance.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): collateral/penalty mechanics for the protocol are not described as mandatory.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): insufficient data.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): MAY is the ecosystem’s governance token (claimed).
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): governance is explicitly specified in the tokenomics.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): governance can be implemented without a separate token as well; product‑level irreplaceability is not proven.
- Evidence: Tier‑1 — https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf
- Why sufficient / why not (one line): the utility is claimed as expandable and “future”.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://cdn.prod.website-files.com/680dd391ae58387b8b91fdb1/6852e6f356a3d9fe68c58db2_91a339a4aa4d006ea5bdaedbd03a0b18_Mayflower%20Whitepaper%20%28English%29.pdf | AI Navigator, tokenomics and roadmap |
| Tier‑1 | https://solscan.io/token/FJz7ptUR1FwxSHbb8Sfd5Cn6Zt4TqucJZKLqU4n66gdq | onchain facts about the MAY token |
No comments to display
No comments to display