How ivelinweb/jaga works
Project type and purpose
• This is a full-stack decentralized insurance dApp monorepo:
• Frontend: Next.js 14 app for user interactions (buy coverage, stake, file claims).
• Indexer: Ponder-powered GraphQL API to listen for on-chain events and serve data.
• Smart-contracts: Foundry project defining InsuranceManager, JagaStake, DAOGovernance, ClaimManager, MorphoReinvest.
File structure
• Top-level folders:
• frontend/: Next.js 14, TypeScript, React hooks, viem/wagmi clients, Apollo GraphQL.
• indexer/: Ponder config, event listeners, generated GraphQL schema, Hono HTTP server.
• smart-contracts/: Solidity contracts, tests, scripts, forge config.
• Key patterns:
• Frontend “src/app” follows Next.js routing & Server Actions.
• “hooks” call JSON-RPC for transactions; “components” render UI.
• Indexer listens to emitted events and populates on-chain tables in a DB.
• Smart-contracts emit events for indexing, and implement business logic on Hedera EVM.
• Config & deployment:
• frontend/next.config.js, Tailwind, tsconfig.
• indexer/ponder.config.ts, .env for DATABASE_SCHEMA.
• smart-contracts/foundry.toml, remappings, scripts for deployment.
README for additional insights
1) Staking & indexing
2) Premium payment & revenue split
3) Claims governance & payout
• Tech stack callouts: Next.js, Ponder, Foundry, Hedera EVM.
Detailed component breakdown (as many as possible)
• Under Frontend:
• UI layer: pages, components, theme-provider.
• Hooks: useStake, useInsuranceManager, useDAOGovernance, useChat.
• GraphQL client: Apollo.
• MCP (Jagabot): ChatInterface, MCP client code.
• Under Indexer:
• Ponder event listeners for each contract.
• On-chain tables: stakes, reward_claims, policies, claims.
• GraphQL / SQL endpoints.
• Under Hedera EVM:
• InsuranceManager, JagaStake, JagaToken, DAOGovernance, ClaimManager, MorphoReinvest.
• External tokens: USDC, Morpho Vault.
• Database:
• Schema “app” managed in indexer/.env.
• Tables for each event type.