Skip to content

Local dev: friendbot, funded test accounts, and one-command Stellar testnet bring-up #137

@greatest0fallt1me

Description

@greatest0fallt1me

Dev onboarding: make stellar-dev with funded accounts and documented fixtures

    ## Description

    **Lower friction** for contributors: document and script **one command** to run API +

DB + (optional) Soroban local env or testnet, create funded accounts, and
seed sample streams. Include .env templates and no secrets in git.
This does not replace production escrow keys—only testnet.

    ## Requirements and context

    - **Script** in `scripts/stellar-dev.sh` (or `Makefile` target) with clear logs.
  • .env.testnet.example with every variable; validation on first run.

  • Test account creation must not be runnable in prod profile (assert).

  • Docs in docs/local-stellar.md with troubleshooting.

  • Time to “first successful stream in UI against local” as success metric in PR.

      ## Suggested execution
    
      1. `git checkout -b docs/stellar-dev-bringup`
    
  1. Add Docker compose service for optional quickstart, or use public testnet only.

  2. PR with screen recording optional (not required) or transcript of commands.

  3. Security check: no default seed phrases; never commit keys.

  4. 96h; split Soroban local node if too heavy to follow-up.

     ## Test and commit
    
  • Run the full test suite; add or update tests until the agreed coverage bar is met.
  • Cover edge cases listed in this issue; document any intentional exclusions with brief rationale in the PR.
  • Include relevant test output (e.g. test runner summary) or a link to a passing CI run in the pull request.
  • Add security notes for auth, keys, PII, chain settlement, or money movement (assumptions verified, out-of-scope items).

Example commit message

chore(dev): one-command Stellar testnet bring-up and funded fixture accounts for StreamPay

Guidelines

  • Target: at least 95% coverage on new or meaningfully changed code (per the repo’s standard tooling).
  • Documentation: update contributor-facing or API documentation where a reviewer would be blocked without it.
  • Timeframe: 96 hours to ready-for-review (surface blockers early).

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-stellarStreamPay ghit: area-stellardomain-dxStreamPay ghit: domain-dxpriority-p3StreamPay ghit: priority-p3type-toolingStreamPay ghit: type-tooling

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions