[Backend] Seed data uses invalid Stellar public keys / contract addresses

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

backend/prisma/seed.ts inserts demo rows with strings that are not valid Stellar keys:

• GDRS6N3K7DQ6GKH47O6E5K5G7B7H7I7J7K7L7M7N7O7P7Q7R7S7T7U7V (repeating, non-checksummed)
• tokenAddress: 'CBTM5D262F6VQY4A6E4F6G7H8I9J0K1L2M3N4O5P6Q7R8S9T0U1V2W3X' — contains 0,1,8,9, which are not in Stellar's base32 alphabet (A-Z2-7).

These insert fine (they're plain string columns) but produce unrealistic demo data: any frontend isValidStellarPublicKey/StrKey decode on seeded rows fails, and the token symbol won't resolve via TOKEN_ADDRESSES. New contributors seeding a local DB then see broken-looking demo streams.

Acceptance criteria

• Replace seed keys/addresses with valid testnet StrKeys (e.g. real G…/C… values, or generated valid keypairs)
• Optionally use the real TOKEN_ADDRESSES token contract values so symbols resolve
• npm run prisma:seed (or equivalent) inserts data the frontend renders correctly

Files to touch

• backend/prisma/seed.ts

Out of scope

• Schema changes.

[Agbasimere]

Can I work on this issue please??

[barry01-hash]

@barry01-hash has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would love to work on this project

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

[drips-wave]

Congratulations, @barry01-hash! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @barry01-hash: 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 🌊