Automatically fund a key on testnet when one is not set

Open
#2,048 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
blockchain, cli

Research direction

Start by tracing the stellar-cli flow for commands that interact with testnet, especially stellar contract deploy, and how keys are selected when none is provided. Define the default key and random-generation behavior, then verify that a testnet account is funded automatically and that deployment works without prior setup.

Written by the indexing model from the issue text.

Description

The stellar-cli could automatically fund a key on testnet when one is not set or provided for commands that interact with testnet.

That key could be named something general like 'default'.

The flow would mean that devs getting started would have less to do upfront before a stellar contract deploy would just work, especially when combined with:

Importantly, this would be a randomly generated key, not some zero value, or default value, or fixed test key.

cc @stellar/devx

Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.