🗄️ Narrrfs Data Engine
```
The Narrrfs World database is the memory layer of the ecosystem.
It is where player identity, game scores, DSPOINC movement, roles, rewards,
NFT verification, staking state, Lab progress, inventory, marketplace activity,
and audit history are connected into one readable system.
In simple words: Narrrf’s World is not just a collection website.
It is a live web game and community platform with a SQL database, many API endpoints,
Discord bot services, wallet verification, profile dashboards, and backend sync systems working together.
Simple customer explanation:
The website, Discord bot, games, Stake Lab, Genesis Lab, Reward Chamber, marketplace,
and profile page all read from or write to the same protected backend data layer.
What kind of database system we use
Narrrf’s World uses a SQL database structure. SQL lets the project store connected records in tables,
search them quickly, compare them safely, and build reports for players, holders, admins, and backend tools.
A SQL database is useful because Narrrfs has many connected systems:
one player can have Discord identity, game scores, DSPOINC history, NFT ownership,
Genesis roles, Lab progress, marketplace listings, staking rows, and reward claims.
More than 100 APIs
Narrrf’s World uses a large API layer between the frontend pages and the database.
These APIs are the controlled gates that decide what the website, Discord bot, games,
and backend services are allowed to read or write.
- Game APIs: save scores, load leaderboards, and connect game activity to profiles.
- Profile APIs: load player identity, DSPOINC state, rewards, stats, and history.
- Reward APIs: open boxes, claim rewards, and write audit-safe reward history.
- Lab APIs: manage Genesis upgrades, trait progress, Genetic Inventory, boosters, and claims.
- Marketplace APIs: create listings, cancel listings, buy items, and transfer Genetic Item state.
- Staking APIs: freeze DSPOINC, complete stakes, claim rewards, unstake, and track V2 readiness.
- Genesis Mouse Freezer APIs: create wallet-proof challenges, freeze NFTs, unfreeze NFTs, and claim daily rewards.
- Admin APIs: support safe operations, reports, checks, fixes, audits, and controlled maintenance.
- Partner / bridge APIs: prepare controlled integrations such as SPOINC/DSPOINC balance checks and future partner routes.
This API structure keeps the frontend from becoming the authority.
The frontend can show buttons, previews, and dashboards, but the backend APIs decide final results.
Website, Discord bot, and backend sync
Narrrfs data does not live in only one page.
The ecosystem syncs across the website, Discord, games, and backend services.
Website sync
Pages like Profile, Leaderboard, Stake Lab, Genesis Lab, Reward Chamber,
Get Roles, and Nerd Lab all explain or display different parts of the same ecosystem data.
Discord bot sync
Discord bot systems can connect roles, events, races, rumbles, reward actions,
holder identity, and community activity back into the Narrrfs backend.
Player profile sync
The Profile page acts as the player hub. It shows scores, DSPOINC activity,
reward history, roles, holder state, and next actions based on backend data.
Backend service sync
Backend services, admin tools, and AI-assisted agent workflows help the team review state,
plan updates, inspect issues, write documentation, and keep systems synchronized.
Wallet and NFT verification
Narrrfs uses wallet and NFT verification to connect Discord players with holder utility.
This is important because player identity and NFT ownership are two different layers.
- Discord identity: who the player is inside Narrrfs World and Discord.
- Wallet identity: which Solana wallet the player controls.
- NFT ownership: which verified Genesis or VIP NFTs belong to that wallet/user connection.
- Holder utility: roles, Genesis Lab access, staking boost previews, and Genesis Mouse Freezer access.
For Solana/NFT checks, the backend can use trusted blockchain data routes such as Helius and Solana RPC providers.
These services help verify wallet and transaction information instead of trusting screenshots or frontend-only claims.
Helius, Solana RPC, and wallet-proof actions
Some advanced systems need proof from the Solana network.
For example, Genesis Mouse Freezer uses wallet-proof Memo transactions during freeze and unfreeze flows.
In that flow, the website helps the user sign a Solana Memo transaction.
The backend then verifies that the correct wallet signed the correct message before changing freezer state.
- The frontend does not decide that a wallet proof is valid.
- The backend checks the Memo transaction through Solana RPC routes.
- Helius or other RPC services can help the backend read Solana transaction data.
- Only after backend verification can freezer state change.
Season control
Seasons are controlled by the database so the website and APIs know which competition cycle is active.
The active season decides where current scores should go and what the current leaderboard cycle means.
- Current-season game scores belong to the active season.
- Leaderboards can reset for fresh competition.
- Historical rows preserve old season performance.
- Permanent economy and holder data do not reset like monthly scoreboards.
Seasonal data
Seasonal data is the part of the ecosystem that can reset or archive when a season changes.
This keeps competitions fresh without deleting long-term identity.
- Current season leaderboard scores.
- Game rows tied to season names.
- Competition stats for games like Tetris, Snake, Space Invaders, Cheese Runner, Glyph Memory, Labyrinth Blast, and other synced games.
- Season archive rows after a reset.
- Monthly or seasonal recognition data.
Permanent economy data
Permanent economy data should not disappear when a leaderboard season resets.
This protects long-term player history, holder state, and economy trust.
- DSPOINC ledger: earned, added, deducted, claimed, frozen, and audited DSPOINC movement.
- Staking state: active stakes, completed stakes, penalties, claim state, and future V2 data.
- Reward history: Reward Chamber actions, claim rows, prize logs, and audit trails.
- Genesis Lab progress: NFT-bound trait and ability progression.
- Genetic Inventory: Discord-user-bound Genetic Items and their item state.
- Genetic Marketplace: listings, purchases, cancellations, transfers, and ownership state.
- Wallet and NFT verification: holder access, Genesis roles, VIP roles, and ownership checks.
Profile data hub
The Profile page is the customer-facing view of the database.
It should help members understand who they are, what they played, what they earned,
what they own, what is frozen, what rewards are available, and where they should go next.
- Game scores and seasonal stats come from backend records.
- DSPOINC balance and history come from ledger rows.
- Roles come from Discord and verification systems.
- Genesis holder visibility comes from wallet/NFT verification.
- Reward, staking, freezer, and Lab state come from their own backend tables and APIs.
Audit trails and safety
A strong database system is not only about storing data.
It is also about proving what happened.
Narrrfs uses audit-style records so the team can review reward movement, balance changes,
claims, admin actions, and system history.
- Reward claims should have a readable reason and history.
- DSPOINC movements should be traceable.
- Admin or system actions should leave reviewable records.
- Marketplace and staking actions should be explainable after they happen.
- Backend checks should protect against duplicate claims, wrong ownership, and frontend manipulation.
AI-assisted backend and support workflow
The Narrrfs team also uses AI-assisted agent workflows to help document systems,
review status, plan safe changes, summarize complex updates, and keep development notes synchronized.
These agents do not replace the database as the source of truth.
They help the team understand, document, and safely operate the system.
Final ownership, reward, balance, role, and claim decisions still come from the backend, database, Discord bot logic, and verified APIs.
Why this makes Narrrfs unique
Many NFT projects only have a mint page and a Discord.
Narrrf’s World is building a connected data world: games, profiles, DSPOINC, Discord roles,
Genesis progression, inventory, marketplace, staking, reward systems, and partner routes all connected through one backend structure.
Short version:
Scoreboards can reset for fresh fun.
Player identity, holder status, Lab progress, DSPOINC history, staking, inventory,
marketplace state, and audit records stay as long-term ecosystem memory.
Safety rules
- The frontend displays data but should not be the final authority.
- APIs control what can be written to the database.
- Discord bot actions must stay synchronized with backend state.
- Wallet/NFT ownership must be verified through approved flows.
- AI-assisted agents can help the team document and review, but they do not override backend truth.
- No public page should expose secrets, private keys, database credentials, or protected admin logic.
Where members should go
Open Profile
Open Leaderboards
Verify NFTs
Open DSPOINC Staking
Open Genesis Mouse Freezer
Open Genesis Lab