7.8 - The demo seed scripts cannot run, and only know testnet

[determined-001]

Complexity: Trivial - 100 Points · type:dx

Milestone: M5 - Distribution & grant

Band lever: none

Context
scripts/demo-seed.ts and scripts/demo-reset.ts back the pnpm demo:seed
workflow that the README and the demo page depend on.

Problem
Two things stop them being useful. They cannot resolve @stellar/stellar-sdk
from the repo root under pnpm's strict node_modules layout, so pnpm demo:seed
fails outright. And they hardcode Networks.TESTNET and friendbot, so even when
fixed they cannot seed a mainnet or self-hosted deployment.

What needs to be done

1. Fix resolution: move the scripts under apps/api/scripts/ (as
   gen-mainnet-secrets.mjs already was), or add the SDK to the root manifest —
   the first is preferred, it keeps the root manifest thin.
2. Read the network and Horizon URL from the same env the API uses, defaulting
   to testnet, instead of hardcoding.
3. Skip the friendbot funding step on any non-testnet network with a clear
   message rather than failing obscurely.
4. Seed the demo link id the demo page expects (see 5.11).

Key files

• scripts/demo-seed.ts, scripts/demo-reset.ts
• package.json — the demo:seed / demo:reset scripts
• apps/api/src/env.ts — the network/Horizon variables to reuse

Done when

• pnpm demo:seed succeeds from a clean install.
• Pointing it at a non-testnet network either works or refuses with a clear reason.

---

Tracked in ISSUES.md — issue 7.8.

[Otfrugger]

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

I’m interested in working on Issue #161 because the demo seed workflow is currently difficult to use from a clean installation and is tied specifically to Stellar testnet. Fixing this would make the development workflow more reliable and useful across different deployments.

I will first review scripts/demo-seed.ts, scripts/demo-reset.ts, the root package scripts, and apps/api/src/env.ts to understand the current dependency resolution and network configuration. I will then move the scripts into apps/api/scripts/ if appropriate, following the existing repository structure used by other API scripts and avoiding unnecessary root-level dependencies.

I will update the scripts to read the network and Horizon configuration from the same environment variables used by the API, with testnet remaining the default. This will allow the scripts to work with testnet as well as self-hosted or mainnet-style deployments.

The Friendbot funding step will only run for testnet. For other networks, the scripts will skip that step and provide a clear message explaining why funding was not attempted instead of failing unexpectedly.

I will also ensure the demo seed creates the expected demo link ID required by the demo page so the complete demo:seed workflow remains functional.

Finally, I will test both pnpm demo:seed and pnpm demo:reset from a clean installation, verify the SDK resolves correctly under pnpm's strict dependency layout, and test behavior with both testnet and a non-testnet configuration.

My goal is to make the demo tooling reliable from a fresh checkout while removing the hardcoded testnet assumptions and keeping the repository's existing dependency structure clean.

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

[drips-wave]

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

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