Overview
Persistent item storage tied to a player's wallet address. Items survive across sessions and can be equipped, used, or traded.
Scope
- Server-side inventory model (items per wallet address)
- Database schema for inventory (PostgreSQL, with in-memory fallback)
- API endpoints: list inventory, equip item, use item
- Client-side inventory UI panel
- Integration with Privy auth (wallet address as player identity)
- Optional: on-chain inventory sync with NFT contract
Notes
The auth system uses Privy embedded wallets — see `src/server/auth.js` and `src/client/auth.js`. Player identity is already wallet-based, so inventory can key off `walletAddress`.
Database access is in `src/server/db.js` with automatic fallback to in-memory when PostgreSQL is unavailable.
Overview
Persistent item storage tied to a player's wallet address. Items survive across sessions and can be equipped, used, or traded.
Scope
Notes
The auth system uses Privy embedded wallets — see `src/server/auth.js` and `src/client/auth.js`. Player identity is already wallet-based, so inventory can key off `walletAddress`.
Database access is in `src/server/db.js` with automatic fallback to in-memory when PostgreSQL is unavailable.