System Requirements Document for money-pool-solana

1. Introduction

money-pool-solana is a Solana-based currency token project. The product intent is to create a currency token called Money Pool on Solana and make it tradable on a live DEX in the same way BTC, ETH, and SOL are traded. The project owner and requester is Jhovany Beltran.

The product serves two audiences in one application:

• Jhovany Beltran, acting as the Token Creator, who needs a launch console to configure the Money Pool token and take it live on a DEX.
• The Token Trader, a market participant who wants to view Money Pool market information and swap Money Pool against live DEX liquidity.

The application is a first-party web product with a public Landing page, an identity access surface (Login), a role-restricted Token Setup workspace, a role-restricted Deployment surface, a public Market view, and a public Swap flow. Live DEX interactions are handled by an external service rather than built in-house.

2. System Overview

money-pool-solana is a dark, instrument-panel web application for launching and trading a Solana currency token called Money Pool. It combines:

• A public entry surface (Landing) that presents the Money Pool token and its live market readout.
• An identity access surface (Login) that establishes first-use identity for the Token Creator and verifies returning users.
• A role-restricted Token Setup workspace where Money Pool token parameters are configured.
• A role-restricted Deployment surface that takes the configured token live on the DEX.
• A public Market page showing Money Pool price and liquidity.
• A public Swap page for trading Money Pool against live DEX liquidity through the external DEX service.

Actors:

• Token Creator (Jhovany Beltran) — configures and deploys the Money Pool token.
• Token Trader — views market data and executes swaps.
• External DEX service — handles live DEX liquidity and swap execution (non-persona, external owner).

Narrow exclusions: The application does not build DEX liquidity or swap execution in-house; those are owned by the external DEX service. No adjacent account-management, portfolio, or unrelated DeFi capabilities are in scope.

2a. Product Interpretation and Delivery Boundary

The product is delivered as a first-party web application with custom UI. Identity is application-owned: the Token Creator establishes first-use identity through self-service enrollment and completes returning verification through Login. Token Setup and Deployment are protected and role-restricted; the Landing, Market, and Swap surfaces are publicly reachable. Live DEX liquidity and swap execution remain the responsibility of the external DEX service and are not reimplemented in-house. All behavior described in this document is current scope; no future-horizon features are included.

2c. Page Content and Component Coverage

Landing

• Information/state: Public entry surface presenting the Money Pool token. Displays the uppercase "MONEY POOL" stencil wordmark, the display headline "A CURRENCY BUILT ON SOLANA", a single line of body copy, and a live market readout panel (PRICE, 24H, LIQUIDITY, SUPPLY) with a pulsing magenta dot and "LIVE ON DEX" indicator. A persistent HUD rail carries the token contract address in monospace with a copy glyph.
• Primary actions: "SWAP MONEY POOL" CTA navigating to Swap; navigation to Login for the Token Creator.
• Supporting actions: Copy token contract address from the HUD rail.
• Domain entities: Money Pool token, contract address, market readout values.
• Component responsibilities: Full-viewport hero with 3D torus-knot liquidity pool subject; asymmetric headline block; glass market readout panel; HUD rail.
• States: Loading (market readout fetching), empty (readout unavailable), success (live values displayed), error (readout fetch failure with retry), recovery (retry restores readout).

Login

• Information/state: Identity access surface. Presents self-service enrollment for first-use identity establishment and returning verification for existing Token Creators.
• Primary actions: Enroll as a new Token Creator; sign in as a returning Token Creator.
• Supporting actions: Navigate back to Landing.
• Domain entities: Token Creator identity, role assignment.
• Component responsibilities: Enrollment form, sign-in form, role assignment on successful authentication.
• States: Loading (submitting credentials), empty (no input yet), success (authenticated and role assigned, redirect to Token Setup), error (invalid credentials or enrollment failure with message), recovery (retry submission).

Token Setup

• Information/state: Role-restricted workspace for configuring Money Pool token parameters. Two-rail layout with monospace labels on the left and values/gauges on the right.
• Primary actions: Configure token parameters; save configuration; proceed to Deployment.
• Supporting actions: View radial gauges for token supply.
• Domain entities: Money Pool token parameters, token supply.
• Component responsibilities: Parameter input fields, supply ring gauge, save control, navigation to Deployment.
• States: Loading (fetching existing configuration), empty (no configuration yet), success (configuration saved), error (save failure with message), recovery (retry save).

Deployment

• Information/state: Role-restricted surface that takes the configured Money Pool token live on the DEX. Scroll-scrubbed sequence with four monospace stage rows (MINT / METADATA / POOL / DEX LISTING) illuminating one by one, ending in a static "LIVE" state.
• Primary actions: Initiate deployment; scroll through deployment stages.
• Supporting actions: View deployment stage progress.
• Domain entities: Deployment stages, token contract, DEX listing.
• Component responsibilities: Stage row list, scroll-scrubbed camera sequence, full-viewport magenta flare on final stage, static "LIVE" confirmation state.
• States: Loading (deployment in progress), empty (not yet started), success (all stages complete, "LIVE" state), error (stage failure with message), recovery (retry failed stage).

Market

• Information/state: Public page showing Money Pool market information including price and liquidity. Two-rail layout with monospace labels and values/gauges. Radial gauges for liquidity depth and token supply.
• Primary actions: View price and liquidity data.
• Supporting actions: Navigate to Swap.
• Domain entities: Price, 24H change, liquidity depth, token supply.
• Component responsibilities: Price gauge, liquidity dial, supply ring, monospace data readouts.
• States: Loading (fetching market data), empty (no data available), success (data displayed), error (fetch failure with retry), recovery (retry restores data).

Swap

• Information/state: Public trading flow for swapping Money Pool against live DEX liquidity through the external service. Single glass slab with buy side lit cyan and sell side lit magenta, split by a 1px cyan rule. Rate rendered as monospace tabular numerals that re-count on input change.
• Primary actions: Enter swap amount; execute swap.
• Supporting actions: View slippage gauge; view quote refresh.
• Domain entities: Swap quote, rate, slippage, buy/sell sides.
• Component responsibilities: Swap panel, buy/sell sides, rate display, slippage radial gauge, light sweep on quote refresh.
• States: Loading (fetching quote), empty (no amount entered), success (swap executed), error (swap failure with message), recovery (retry swap).

3. Functional Requirements

FR-1: Create a Solana-based currency token named Money Pool (explicit) As a Token Creator, I should configure and create a Solana-based currency token named Money Pool so that the token exists as a real on-chain asset.

• Trigger/input: Token Creator signs in with the appropriate role and enters token parameters in Token Setup.
• Observable result: Money Pool token parameters are saved and ready for deployment.
• Access state: Role-restricted (Token Setup).
• Failure/recovery: Save failure shows an error message and allows retry.
• Continuation: Proceed to Deployment.

FR-2: Trade Money Pool on a live DEX (explicit) As a Token Trader, I should trade Money Pool on a live DEX comparable to how BTC, ETH, and SOL are traded so that Money Pool is a tradable currency.

• Trigger/input: Token Trader enters a swap amount on the Swap page.
• Observable result: Swap executes against live DEX liquidity through the external DEX service.
• Access state: Public (Swap).
• Failure/recovery: Swap failure shows an error message and allows retry.
• Continuation: View updated market data on Market.

FR-3: Landing page presents the Money Pool token (explicit) As a visitor, I should see a Landing page presenting the Money Pool token so that I understand what Money Pool is.

• Trigger/input: Navigate to Landing.
• Observable result: Landing displays the Money Pool token presentation and live market readout.
• Access state: Public.
• Failure/recovery: Readout fetch failure shows an error state with retry.
• Continuation: Navigate to Swap or Login.

FR-4: Token Setup page configures the token (explicit) As a Token Creator, I should use the Token Setup page to configure the Money Pool token so that its parameters are correct before deployment.

• Trigger/input: Token Creator signs in and navigates to Token Setup.
• Observable result: Token parameters are configured and saved.
• Access state: Role-restricted.
• Failure/recovery: Save failure shows an error message and allows retry.
• Continuation: Proceed to Deployment.

FR-5: Deployment page takes the token live (explicit) As a Token Creator, I should use the Deployment page to take the Money Pool token live so that it becomes tradable on the DEX.

• Trigger/input: Token Creator initiates deployment from Deployment.
• Observable result: Deployment stages complete and the token reaches a "LIVE" state on the DEX.
• Access state: Role-restricted.
• Failure/recovery: Stage failure shows an error message and allows retry of the failed stage.
• Continuation: Token is available for trading on Market and Swap.

FR-6: Market page shows the token's market (explicit) As a Token Trader, I should view the Market page showing Money Pool's market so that I can see price and liquidity.

• Trigger/input: Navigate to Market.
• Observable result: Market displays price, 24H change, liquidity depth, and token supply.
• Access state: Public.
• Failure/recovery: Fetch failure shows an error state with retry.
• Continuation: Navigate to Swap to trade.

FR-7: Swap page trades the token (explicit) As a Token Trader, I should use the Swap page to trade Money Pool so that I can buy and sell it.

• Trigger/input: Token Trader enters a swap amount on Swap.
• Observable result: Swap executes against live DEX liquidity through the external DEX service.
• Access state: Public.
• Failure/recovery: Swap failure shows an error message and allows retry.
• Continuation: View updated market data on Market.

FR-8: Token Setup and Deployment require sign-in and the appropriate role (explicit) As a Token Creator, I should sign in with the appropriate role before accessing Token Setup and Deployment so that only authorized users configure and deploy the token.

• Trigger/input: Attempt to access Token Setup or Deployment without sign-in or the appropriate role.
• Observable result: Access is denied and the user is directed to Login.
• Access state: Role-restricted.
• Failure/recovery: Invalid credentials show an error message and allow retry.
• Continuation: After successful sign-in with the appropriate role, access is granted.

FR-9: Live DEX interactions handled by external service (explicit) As a Token Trader, I should have my swaps executed through the external DEX service so that trading uses live DEX liquidity.

• Trigger/input: Token Trader executes a swap on Swap.
• Observable result: The external DEX service executes the swap against live liquidity.
• Access state: Public.
• Failure/recovery: External service failure shows an error message and allows retry.
• Continuation: Swap result is reflected in Market data.

FR-10: Token Creator self-service enrollment establishes first-use identity (required_inference) As a Token Creator, I should enroll through self-service on Login so that I establish my first-use identity.

• Trigger/input: New Token Creator submits enrollment on Login.
• Observable result: Identity is established and the appropriate role is assigned.
• Access state: Public (Login).
• Failure/recovery: Enrollment failure shows an error message and allows retry.
• Continuation: Proceed to Token Setup.

FR-11: Token Creator completes returning verification through Login (required_inference) As a Token Creator, I should sign in through Login so that I verify my returning identity.

• Trigger/input: Returning Token Creator submits credentials on Login.
• Observable result: Identity is verified and the appropriate role is confirmed.
• Access state: Public (Login).
• Failure/recovery: Invalid credentials show an error message and allow retry.
• Continuation: Proceed to Token Setup or Deployment.

FR-12: Token Creator is assigned or assumes the appropriate role (required_inference) As a Token Creator, I should have the appropriate role assigned before accessing Token Setup and Deployment so that protected work is authorized.

• Trigger/input: Successful enrollment or sign-in on Login.
• Observable result: The appropriate role is assigned or confirmed.
• Access state: Role-restricted.
• Failure/recovery: Role assignment failure shows an error message and allows retry.
• Continuation: Access Token Setup and Deployment.

FR-13: Live DEX liquidity and swap execution remain available through the external DEX service (required_inference) As a Token Trader, I should have live DEX liquidity and swap execution available through the external DEX service so that trading remains functional.

• Trigger/input: Token Trader requests a swap on Swap.
• Observable result: The external DEX service provides liquidity and executes the swap.
• Access state: Public.
• Failure/recovery: External service unavailability shows an error message and allows retry.
• Continuation: Swap result is reflected in Market data.

4. User Personas

Token Creator — Jhovany Beltran

Product context: Jhovany Beltran wants to create a Solana-based currency token called Money Pool and take it live on a DEX, comparable to BTC, ETH, and SOL. He is the project owner and requester.

Primary goal: Configure the Money Pool token's parameters and complete deployment so the token exists on-chain and is tradable on a live DEX.

Distinct accepted responsibilities:

• Enroll through self-service on Login to establish first-use identity.
• Sign in through Login to verify returning identity and assume the appropriate role.
• Configure the token's parameters in Token Setup.
• Complete Deployment so the token exists on-chain and is tradable.

Relevant inputs or decisions: Token parameters (supply, metadata), deployment initiation, stage progression.

Interactions with other accepted participants: The Token Creator's deployment makes Money Pool available for the Token Trader to view on Market and trade on Swap.

Observable success: Money Pool is deployed and available for trading on a live DEX.

Token Trader

Product context: A market participant who wants to buy and sell Money Pool the way BTC, ETH, and SOL are traded.

Primary goal: Trade Money Pool against live DEX liquidity.

Distinct accepted responsibilities:

• View the Market for Money Pool pricing and liquidity.
• Execute swaps through the Swap flow.

Relevant inputs or decisions: Swap amount, buy/sell side selection, slippage tolerance.

Interactions with other accepted participants: The Token Trader depends on the Token Creator's deployment for Money Pool to exist and be tradable.

Observable success: Trades in Money Pool complete against live DEX liquidity.

5. Core User Flows

Flow 1: Token Creator enrolls and configures the Money Pool token

1. Jhovany Beltran (Token Creator) navigates to the Landing page and sees the Money Pool token presentation.
2. He navigates to Login and submits self-service enrollment to establish first-use identity.
3. The system establishes his identity and assigns the appropriate role.
4. He is directed to Token Setup (role-restricted).
5. He enters Money Pool token parameters (supply, metadata) in the two-rail layout.
6. He saves the configuration; the system confirms the save.
7. Failure/recovery: If the save fails, an error message appears and he retries.
8. Continuation: He proceeds to Deployment.

Flow 2: Token Creator deploys the Money Pool token

1. Jhovany Beltran (Token Creator) is signed in with the appropriate role and navigates to Deployment (role-restricted).
2. He initiates deployment.
3. He scrolls through the deployment sequence; the four stage rows (MINT / METADATA / POOL / DEX LISTING) illuminate one by one.
4. The final stage fires a full-viewport magenta flare for 400ms before settling into a static "LIVE" state.
5. Failure/recovery: If a stage fails, an error message appears and he retries the failed stage.
6. Continuation: Money Pool is now available for trading on Market and Swap.

Flow 3: Token Creator returns and signs in

1. Jhovany Beltran (Token Creator) navigates to Login.
2. He submits his credentials for returning verification.
3. The system verifies his identity and confirms the appropriate role.
4. Failure/recovery: If credentials are invalid, an error message appears and he retries.
5. Continuation: He proceeds to Token Setup or Deployment.

Flow 4: Token Trader views the Money Pool market

1. A Token Trader navigates to the Market page (public).
2. The system fetches and displays Money Pool price, 24H change, liquidity depth, and token supply using radial gauges and monospace readouts.
3. Failure/recovery: If the fetch fails, an error state appears and he retries.
4. Continuation: He navigates to Swap to trade.

Flow 5: Token Trader swaps Money Pool

1. A Token Trader navigates to the Swap page (public).
2. He enters a swap amount; the rate re-counts as monospace tabular numerals.
3. He selects the buy side (lit cyan) or sell side (lit magenta).
4. He views the slippage radial gauge.
5. He executes the swap; the external DEX service executes it against live liquidity.
6. Failure/recovery: If the swap fails, an error message appears and he retries.
7. Continuation: The swap result is reflected in Market data.

6. Visuals Colors and Theme

Muse: Gleb Kuznetsov. Headline direction: Cinematic future-tech — a dark void where a liquidity pool glows like a star chart.

Palette (dark mode):

• Background (void): #05060C — covers ~65% of every screen.
• Surface (panel): #0C1020 at 70–85% opacity with 1px borders of rgba(0,229,255,0.22).
• Text: #E8ECFF at 92% for body; #6B7A99 for micro-labels and secondary data.
• Primary (signal): #00E5FF — pool glow, active nav, live price ticks, swap CTA fill.
• Accent (hot): #FF2E9A — used sparingly, never twice in one viewport: the 'LIVE ON DEX' pulse, the sell side of the swap, the deployment success flare.
• Muted: #6B7A99.
• Ratio: ~65% void / 25% panel / 8% cyan / 2% magenta.

Typography:

• Headings: Space Grotesk 500–700. Uppercase for section eyebrows with 0.22em tracking; sentence case for big statements with -0.03em tracking and 0.92 leading. Wordmark "MONEY POOL" always uppercase with 0.3em tracking. Numerals in headings switch to the mono face.
• Body: IBM Plex Sans.
• Scale: 1.25 modular on a 4px baseline. Display clamp(52px, 11vw, 148px); H1 36/56/72; H2 26/36/44; H3 20/24/26; body 16/16/17 with 1.65 leading; micro-label 11/11/12 uppercase 0.22em; data numerals 13/14/15 in IBM Plex Mono tabular. Every headline uses clamp() and wraps inside its column at 375px.

Shape language: Thin luminous strokes and glass, no soft blobs. Panels are 2px-radius rectangles with 1px cyan-tinted borders and a 1px inner top highlight. Circular elements reserved for real instrumentation: liquidity dial, price gauge, token supply ring. Diagonal 45° hairlines and radial tick marks as decoration behind panels. Corners stay sharp; the only curve is the arc of a gauge.

Layout: Full-bleed dark canvas with a fixed 12-column grid (24px gutters mobile, 40px desktop) drawn in faint cyan hairlines at 8% opacity. Hero is a single full-viewport 3D scene with HUD text overlaid asymmetrically. Data pages (Market, Swap, Deployment) use a two-rail layout: narrow left rail of monospace labels, wide right rail of values and gauges. Nothing is centred except a single confirmation state.

Imagery: One crafted real-time 3D subject: a torus-knot liquidity pool — a lattice of glowing cyan filaments with a magenta core, rendered on black, slowly rotating, with a particle field derived from the token's own supply numbers. Around it, abstract volumetric forms and thin luminous strokes only. No stock photography of people, laptops, rocket ships, or coin-with-a-dollar-sign clip art. Market surfaces use generated sparkline geometry and radial gauges rather than chart screenshots.

7. Signature Design Concept

The public entry (Landing) is a full-viewport #05060C void. The dominant element is a slowly rotating 3D torus-knot pool of cyan filaments with a magenta core, centred slightly right of frame and bleeding off the right and bottom edges — it occupies roughly 70% of the viewport and is the only lit object.

Overlaid on the left, an asymmetric 6-column block: the uppercase "MONEY POOL" stencil wordmark at 12px with 0.3em tracking, then the display headline "A CURRENCY BUILT ON SOLANA" at clamp(52px, 11vw, 148px) in Space Grotesk 600, three lines, tight 0.92 leading, with the words "ON SOLANA" in cyan #00E5FF and the rest in #E8ECFF. Beneath it a single line of body copy at 17px in #6B7A99 and one CTA — a sharp-cornered cyan-filled "SWAP MONEY POOL" button with a magenta 1px inner rim.

Top-right floats a glass readout panel with monospace tabular numerals: PRICE, 24H, LIQUIDITY, SUPPLY, each label 11px uppercase #6B7A99 over 15px #E8ECFF values, with a pulsing magenta dot and "LIVE ON DEX" above them. Faint cyan grid hairlines cross the void behind everything. No centred headline, no subtext-and-button stack, no gradient blob — the composition is a lit object with instrumentation wrapped around it.

A persistent HUD rail runs across the top of every page: a 1px cyan hairline carrying the token contract address in IBM Plex Mono, a copy-glyph, and a pulsing magenta "LIVE ON DEX" dot.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl

Landing Hero Motion Brief:

• Focal subject: A slowly rotating 3D torus-knot liquidity pool of cyan filaments with a magenta core, rendered on a #05060C void, with a particle field derived from the token's own supply numbers.
• Input → transformation → outcome thesis: As the user scrolls, the camera scrubs in toward the pool; the pool's slow orbit and particle drift continue, and the live market readout counts up on entry (price, liquidity, supply) over 600ms with cubic-bezier(0.16,1,0.3,1), settling into a stable instrument readout.
• Motion vocabulary: One continuous slow orbit of the hero subject with faint particle drift; scroll-scrubbed camera push; numbers count up on entry; light sweeps travel along panel top edges on hover (240ms); state changes flash cyan for 120ms then settle; page transitions are a 200ms opacity crossfade with a 1px scanline wipe.
• Composed first frame: The pool is centred slightly right of frame, bleeding off the right and bottom edges, occupying ~70% of the viewport. The headline block is anchored bottom-left in a 6-column block; the live market readout floats top-right in a glass panel; the swap CTA is pinned bottom-right. Faint cyan grid hairlines cross the void behind everything.
• Reduced-motion state: The hero renders as a single static frame of the pool render; all counters show final values immediately; the transaction ticker becomes a horizontally scrollable row that can be dragged to read every entry.

Landing Hero 3D Scene Brief — DIRECTION-DERIVED: A real-time WebGL/R3F scene of a torus-knot liquidity pool: a lattice of glowing cyan filaments with a magenta core, rendered on black, slowly rotating, with a particle field derived from the token's own supply numbers. The scene shows the product's defining state — a live liquidity pool — and is the only lit object in the void.

9. Non-Functional Requirements

NFR-1: Live DEX interactions handled by external service (explicit) Live DEX interactions are handled by an external service rather than built in-house. Rationale: explicit hard constraint in the authoritative user evidence.

NFR-2: Token Setup and Deployment require sign-in and the appropriate role (explicit) Token Setup and Deployment require sign-in and the appropriate user role. Rationale: explicit hard constraint in the authoritative user evidence.

NFR-3: Readable text and controls stay whole at every viewport (explicit) Headlines, wordmarks, labels, numbers, cards' text and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit. No other element covers any part of them. Rationale: explicit design constraint.

NFR-4: Reduced-motion support (explicit) With prefers-reduced-motion, the hero renders as a single static frame of the pool render, all counters show final values immediately, and the transaction ticker becomes a horizontally scrollable row that can be dragged to read every entry. Rationale: explicit design constraint.

NFR-5: Dark mode palette (explicit) The application uses the dark mode palette specified in the creative direction: background #05060C, surface #0C1020, text #E8ECFF, primary #00E5FF, accent #FF2E9A, muted #6B7A99. Rationale: explicit design constraint.

NFR-6: Typography (explicit) Headings use Space Grotesk; body uses IBM Plex Sans; data numerals use IBM Plex Mono tabular. Rationale: explicit design constraint.

10. Tech Stack

• Frontend: React (web application with custom UI).
• Backend: Python/FastAPI for application-owned identity, token configuration, and deployment orchestration.
• Storage: Appropriate storage for token configuration and deployment state.
• External service: Live DEX service for liquidity and swap execution (external owner, not built in-house).
• Containerization: Docker/docker-compose for local development and deployment.
• 3D rendering: WebGL/R3F for the Landing hero torus-knot liquidity pool.

11. Assumptions and Constraints

Assumptions:

• The Token Creator is Jhovany Beltran, the project owner and requester.
• The external DEX service provides live liquidity and swap execution.
• Application-owned identity is used for Token Setup and Deployment access.

Constraints:

• Token Setup and Deployment require sign-in and the appropriate user role.
• Live DEX interactions are handled by an external service rather than built in-house.
• The application uses the dark mode palette and typography specified in the creative direction.
• Readable text and controls stay whole at every viewport.
• Reduced-motion support is provided.

12. Glossary

• Money Pool: The Solana-based currency token created by this project.
• Token Creator: The persona who configures and deploys the Money Pool token (Jhovany Beltran).
• Token Trader: The persona who views market data and executes swaps.
• DEX: Decentralized exchange; the external service that provides live liquidity and swap execution.
• Token Setup: The role-restricted workspace for configuring Money Pool token parameters.
• Deployment: The role-restricted surface that takes the configured token live on the DEX.
• Market: The public page showing Money Pool price and liquidity.
• Swap: The public trading flow for swapping Money Pool against live DEX liquidity.
• HUD rail: The persistent 1px cyan hairline across the top of every page carrying the token contract address, a copy glyph, and a pulsing magenta "LIVE ON DEX" dot.
• Torus-knot liquidity pool: The 3D hero subject on the Landing page — a lattice of glowing cyan filaments with a magenta core.