Short Whitepaper v1.0

1. Executive Summary

Poseidon Protocol (PSEA) is an ERC-20 token deployed on the Base network, conceived as a community-driven memecoin with a transparent and cautious approach. The goal is to build a community around PSEA and, over time, add simple, easy-to-understand utilities, without any promises of returns or guarantees of any kind.

PSEA is an experimental digital asset. It does not represent equity in any company, does not grant ownership rights, and does not constitute financial advice or an investment offer. Each user is solely responsible for their own decisions according to their individual risk profile.

2. Token Technical Data

• Name: Poseidon Protocol

• Symbol: PSEA

• Network: Base (mainnet)

• Standard: ERC-20

• Contract address: 0x06125ec0cb5715bBF49C1E3Ff675870A5f60440F

• Decimals: 18 (standard ERC-20; if the contract uses a different value, this section will be updated accordingly)

Supply:

• Initial total supply: 88,888,888 PSEA

• Supply type: non-mintable, fixed total supply; tokens can only be reduced via burn functions.

This document does not guarantee that the mint function will be used; it only states that the capability exists at the contract level.

3. Tokenomics and Distribution

Type: Fixed-supply ERC-20, burnable, with EIP-2612 permit.

Total supply: 88,888,888 PSEA

Minting: No further minting after deployment.

High-level structure:

• Initial circulation: 44,444,444 PSEA (50% of total)

• Initially locked tokens: 44,444,444 PSEA (50% of total)

Proposed breakdown (aligned with your numbers and structured clearly):

1. Initial DEX liquidity – 30%

   • 26,666,666 PSEA

   • Allocated to create the initial PSEA/ETH liquidity pair on a DEX on Base.

2. Community / marketing – 20%

   • 17,777,778 PSEA

   • To be used progressively for:

     • Community campaigns.

     • Participation rewards (memes, content, project support).

     • Basic collaborations.

3. Team (locked) – 10%

   • 8,888,888 PSEA

   • Assigned to the founder/small team.

   • Recommended lockup: at least 12 months, with gradual vesting afterwards (to reinforce trust).

4. Reserve / future (locked) – 40%

   • 35,555,556 PSEA

   • Potential uses:

     • Future products or utilities.

     • Additional liquidity if needed.

     • Future partnerships or integrations.

The percentages above add up to 100% of the supply. The exact lock conditions (locker platform, duration, and transaction details) should be published on-chain when executed, to keep the narrative aligned with reality.

4. Liquidity and Markets

• Target DEX on Base: a decentralized exchange on Base (for example, Aerodrome or Uniswap v3 on Base).

• Initial pair: PSEA/ETH

• Initial liquidity: part of the 30% allocated to liquidity will be paired with ETH to form the initial pool.

Liquidity lock policy:

• Initial lock: minimum 6 months.

• Goal: extend the lock up to 12 months, depending on project and community evolution.

When liquidity is effectively locked, the project will publish:

• Locker link.

• Pair address.

• Exact lock duration.

5. Token Utility (Initial Phase)

PSEA is launched as a community/memecoin-style token, inspired by models such as PEPE but with a focus on clarity and prudence.

Planned simple utilities:

1. Community token

   • PSEA acts as a symbolic “membership pass” to the Poseidon community.

   • Holders may access internal dynamics, memes, giveaways, and social activities (as they are implemented).

2. Basic participation in decisions

   • The token is used as a reference for off-chain polls and decisions (on X / Telegram) regarding:

     • Campaign focus.

     • Basic project priorities.

3. Future access to simple tools

   • Long-term goal: allow PSEA to be used to access or unlock simple utilities (for example, basic data dashboards or info bots), always without promising income or returns.

PSEA does not guarantee dividends, passive income, or rights over any entity’s cash flows.

6. Operational Roadmap

Since this is the founder’s first token and the learning process is ongoing, the roadmap is kept simple and realistic.

Phase 1 – Initial launch (~next 1 month)

• Contract deployment on Base (already completed).

• Setup of the PSEA/ETH liquidity pair on a DEX on Base.

• Launch of official communication channels (X, Telegram).

• Publication of this short whitepaper.

Phase 2 – Basic consolidation (0–6 months after launch)

• Building an active community on X and Telegram.

• Regular communication: key moves, risk explanations, DYOR reminders.

• Definition and execution of the first community campaigns (memes, content, small rewards using the marketing allocation).

Phase 3 – Simple tools and expansion (6–12 months)

• Implementation of at least one simple tool (for example, a basic data panel or an info bot for the token).

• Evaluation of extending liquidity lock up to 12 months.

• Roadmap adjustments based on real experience, community size, and available resources.

All milestones are goals, not guaranteed promises. They may be modified or cancelled depending on resources, risks, and market conditions.

7. Community, Team and Official Channels

Team model

Poseidon Protocol is built by a small team, consisting of:

• A pseudonymous founder, responsible for the project’s vision, key decisions, and day-to-day operations.

• Support from artificial intelligence tools (such as ChatGPT) for drafting, ideation, and organization, always under the founder’s criteria and responsibility.

The project is not presented as a formal company nor as a regulated organization. As the project grows, additional contributors (development, design, community) may be added in an open and transparent way.

Official channels

• X (Twitter): @PseaPoseidon

• Telegram: PoseidonProtocolPSEA

• Official website: to be added once it is live

Users should always verify that any link or contract address comes from these official channels before interacting or purchasing.

8. Risks

Interacting with PSEA carries significant risks:

• Extreme price volatility: the token’s value may rise or fall sharply and can go to zero.

• Liquidity risk: there may not be enough liquidity to buy or sell at the desired time.

• Technical risks: smart contract bugs, failures in third-party infrastructure (DEXs, bridges, RPC providers), or external attacks.

• Regulatory risks: legal or regulatory changes in different jurisdictions that affect holding or trading cryptoassets.

• Execution risk: as this is the founder’s first token and a learning project, there is additional risk of operational mistakes.

No one should participate with funds they cannot afford to lose entirely.

9. Legal Approach and Disclaimer

• PSEA is not presented as a security nor as a registered public offering in any jurisdiction.

• No promises of returns, passive income, or future profits are made.

• The project does not provide financial, legal, or tax advice.

• Each user is responsible for:

  • Doing their own research (DYOR).

  • Complying with applicable laws in their country regarding cryptoassets and taxation.

  • Assessing whether this type of asset fits their risk profile.

This document is for informational purposes only and may be updated over time. It does not replace consultation with qualified legal or financial professionals.

Contract Overview
Poseidon Protocol (PSEA) is an ERC-20 token built on top of OpenZeppelin Contracts v5.5. The contract extends ERC20, ERC20Burnable and ERC20Permit and does not introduce any custom logic in the transfer flow.

Supply and Functions
– Fixed total supply: 88,888,888 PSEA (18 decimals).
– The full supply is minted once in the constructor to a single recipient address.
– No additional mint function exists; supply can only decrease via burn and burnFrom.
– No transfer fees, no blacklist, no trading restrictions at contract level.

Admin Rights
– The contract does not use Ownable or any admin role.
– There is no owner function, no pause/unpause, and no ability to change fees or arbitrarily move user funds.
– The main risk is not in the code, but in how the initial supply and liquidity are managed by the recipient wallet.

Risk Notice
This contract is a thin wrapper around widely used OpenZeppelin implementations and does not contain complex custom logic. Nevertheless, it has not undergone a formal third-party audit, and users should always do their own research (DYOR) and understand that concentration of tokens in a few wallets and external factors (DEX liquidity, private keys management, etc.) are the main sources of risk.

RouteScan-style Contract Check (Summary)

Contract: 0x06125ec0cb5715bBF49C1E3Ff675870A5f60440F
Network: Base mainnet
Standard: ERC-20 (OpenZeppelin-based)

Source code

• Minimal ERC-20 implementation using OpenZeppelin libraries (ERC20, ERC20Burnable, ERC20Permit).

• No custom transfer logic, no tax/fee logic, no embedded DEX or complex financial mechanisms.

Supply model

• Fixed total supply: 88,888,888 PSEA (18 decimals).

• The full supply is minted once at deployment to a single recipient address.

• No additional mint function is available after deployment.

• Supply can only decrease via burn / burnFrom.

Admin & privileges

• No Ownable, no AccessControl – the contract has no owner/admin role.

• No pause/unpause functions.

• No ability to change fees, block addresses, or arbitrarily move user funds from the contract.

• Effective permissions are limited to standard ERC-20 transfers and burn functions.

Non-features / Controls

• No transfer taxes or trading fees.

• No blacklist/whitelist mechanism.

• No max wallet / max transaction limits at contract level.

• No upgradeability (no proxy pattern).

Risk considerations (from a scanner’s perspective)

• Code is simple and based on widely used OpenZeppelin components, reducing smart-contract logic risk.

• Main risks are off-chain and operational:

  • Initial supply is fully concentrated in one wallet at deployment.

  • Liquidity locks, token distribution and key management are handled outside the contract.

• The contract has not undergone a formal third-party security audit; users should always DYOR.