[Testing] Database Seeding Engine for Deterministic Local Environments

[AlAfiz]

Description: Develop a CLI seeding script (npm run seed) that populates the local development database with deterministic, realistic historical protocol data (users, pools, and thousands of swaps).
Context / Motivation: Frontend developers and new open-source contributors need a fully populated local API to work on charting or UI features without having to manually trigger hundreds of on-chain transactions first.
Acceptance Criteria: - [ ] Create a seeding script utilizing the project's ORM (Prisma/TypeORM).

• Generate mock users, 3 distinct liquidity pools, and at least 5,000 historical swap records spread across a 30-day simulated timeline.
• Ensure the script idempotently clears existing local data before applying the new seed to prevent primary key collisions.
  Technical Pointers: Use a library like faker.js to generate realistic Stellar G-addresses and randomized (but mathematically valid) swap amounts. Wrap the massive array of inserts in a single database transaction to speed up the seeding execution.

[lahdlahd]

I've built database seeding scripts with Prisma and TypeORM before, including generating large deterministic datasets using faker.js for DeFi and full-stack projects. I can implement the npm run seed script to generate mock users, 3 liquidity pools, and 5,000+ historical swaps across a 30-day timeline, wrapped in a single transaction for performance, with idempotent clearing to prevent key collisions. I'll ensure Stellar G-addresses are realistic and swap amounts are mathematically valid. Can deliver clean, well-documented code ready for immediate use by frontend contributors

[YfengJ]

Hi maintainers, I would like to apply for this issue if it is available.\n\nIf assigned, I will keep the implementation scoped to a deterministic local seeding path: inspect the current ORM/schema first, add an npm seed script, generate stable users/pools/swaps with seeded randomness, clear only local seed-owned data idempotently to avoid primary-key collisions, batch inserts inside a transaction where the ORM supports it, and add a small validation/test path that confirms record counts and repeatable output.\n\nI will wait for maintainer or GrantFox assignment/confirmation before cloning, implementing, or opening a PR.

[grantfox-oss]

🦊 GrantFox — @lahdlahd has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #169)
2. Your PR will be reviewed by the BETAIL-BOYS maintainers

Good luck! Track your progress on GrantFox.

[YfengJ]

Thanks for the update. I see @lahdlahd has been assigned, so I will step back and not work on this issue. Good luck with the implementation.