Add a `network` column across all Prisma models

[Miracle656]

Background

Wraith's schema has no network dimension — every table keys on contract/address/ledger only. If a mainnet instance and a testnet instance ever share a database, records collide: eventId is globally @unique on TokenTransfer/HostFnLog/NftTransfer (RPC paging tokens can repeat across networks and silently overwrite), and IndexerState/BackfillCursor are singleton rows (@id @default(1)) — one cursor for the whole DB. Dual-network is impossible until storage is network-aware.

What to build

Add a network field ("testnet" | "mainnet") to every model and fold it into every uniqueness constraint and query.

Key files

• prisma/schema.prisma — add network to TokenTransfer, HostFnLog, NftTransfer, NftMetadata, AccountSummary, WebhookSubscription/Delivery, IndexerState, IndexerCheckpoint, BackfillCursor, RetentionJobRun
• src/db.ts — thread network into every read/write
• a new Prisma migration

Suggested execution

git checkout -b feat/network-column

1. Add network String @default("testnet") to each model
2. Change eventId @unique → @@unique([network, eventId]); make IndexerState/BackfillCursor keyed by network instead of the singleton id=1
3. Update AccountSummary (@@unique([network, address])) and NftMetadata (@@unique([network, contractId, tokenId]))
4. Regenerate: npx prisma migrate dev --name add-network
5. Update every query in src/db.ts to pass/filter network

Acceptance criteria

• Every model carries network; all @unique/@@unique keys include it
• IndexerState/BackfillCursor are per-network, not singleton rows
• Migration applies cleanly on a fresh DB
• Existing queries updated and tests green

Drips Wave · Complexity: Advanced · 200 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Chinonso-Peter]

@Chinonso-Peter has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Can i work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chinonso-Peter to this issue.

[Salmatcre8]

@Salmatcre8 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to claim this issue. Refactoring Wraith’s schema to be network-aware is a critical architectural upgrade to prevent cross-network collisions, unique constraint violations on shared RPC event IDs, and cursor collisions between mainnet and testnet.

My implementation plan includes:

Schema Overhaul (prisma/schema.prisma): Adding network String @default("testnet") across all 11 models (TokenTransfer, HostFnLog, NftTransfer, NftMetadata, AccountSummary, WebhookSubscription, WebhookDelivery, IndexerState, IndexerCheckpoint, BackfillCursor, RetentionJobRun).

Composite Uniqueness & Multi-Network Cursors:

Converting single-column unique keys to composite constraints (e.g., @@unique([network, eventId]), @@unique([network, address]), @@unique([network, contractId, tokenId])).

Converting singleton tracking models (IndexerState, BackfillCursor) from single fixed integer IDs (@id @default(1)) to be primary-keyed on network (@id @default("testnet")).

Clean Migration Workflow: Generating a clean Prisma migration (add-network) with backward-compatible defaults for existing environments.

Query Layer Threading (src/db.ts): Updating every database helper, reader, and writer method in src/db.ts to accept network: 'testnet' | 'mainnet' and filter/insert accordingly.

Comprehensive Test Verification: Updating existing test suites to assert proper network isolation, confirming testnet and mainnet records with matching event IDs coexist cleanly without overwrites.

I have deep experience with Prisma schema migrations, complex composite indexing strategies, and multi-network indexer pipelines. Please assign this to me!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Salmatcre8 to this issue.

[drips-wave]

Congratulations, @Salmatcre8! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Salmatcre8: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊