Monorepo Structure

Aqua Stark follows a monorepo architecture, streamlining development across multiple components.

📌 Structure

• Frontend – Next.js-based interface for the game and marketplace.

• Backend – Node.js server handling API calls and Starknet interactions.

• Smart Contracts – Cairo-based contracts deployed on Starknet.

• Shared Utilities – Reusable libraries for blockchain integration and game mechanics.

/aquarium-game
│── /backend # Backend with Node.js + Express
│ ├── /src
│ │ ├── /controllers # Business logic (management of users, aquariums, marketplace)
│ │ ├── /models # Database models (Fish, Users, Transactions)
│ │ ├── /routes # API routes (REST Endpoints)
│ │ ├── /services # Connection to blockchain and contract logic
│ │ ├── /utils # Helpers and auxiliary functions
│ │ ├── app.ts # Server configuration Express
│ ├── package.json # Backend dependencies
│ ├── tsconfig.json # TypeScript configuration
│
│── /frontend # Frontend with React + Next.js
│ ├── /public # Images, fonts, icons
│ ├── /src
│ │ ├── /app # Next.js main pages
│ │ ├── /components # Reusable components (Aquarium, PezCard, Marketplace, etc.)
│ │ ├── /context # Global state with React Context
│ │ ├── /hooks # Custom hooks for logic specific
│ │ ├── /services # Connection to backend and blockchain
│ │ ├── /styles # Style files (TailwindCSS)
│ │ ├── /utils # Helper functions
│ │ ├── /assets # Sprites, images, decorations
│ ├── next.config.js # Next.js configuration
│ ├── package.json # Frontend dependencies
│ ├── tsconfig.json # TypeScript configuration
│
│── /smart-contracts # Smart contracts in Cairo
│ ├── /contracts # Contracts code (Fish, Marketplace, Evolution)
│ ├── /tests # Testing contracts in Cairo
│ ├── compile.sh # Script to compile the contracts
│ ├── deploy.sh # Script to deploy to StarkNet
│ ├── README.md # Documentation about smart contracts
│
│── .github # CI/CD configuration (optional)
│── .env # Environment variables
│── README.md # General project documentation

🔥 Why Use a Monorepo?

• Unified Codebase – Easier management of interdependent components.

• Improved Collaboration – Developers work within a centralized structure.

• Consistent Dependencies – Reduces version conflicts across services.

• Faster Deployment – Automated CI/CD pipelines improve efficiency.

😂 Fish Joke: Why don’t fish like basketball?

• Because they’re afraid of the net!