Repository navigation
feat(account): remove the automatic testnet top-up on sign-up - #858
Merged
Merged
Conversation
New accounts are not topped up: people may want to fund an external address instead, and the portal now tells new users to request testnet CHEQ. The top-up never ran for new sign-ups since 3.18.0 anyway, because the testnet account already exists when it is checked. Removes the top-up code, ENABLE_ACCOUNT_TOPUP, TESTNET_INITIAL_TOPUP_CHEQ, TESTNET_MINIMUM_BALANCE and the BootStrapAccountResponse testnetMinimumBalance field. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
🎉 This PR is included in version 3.19.0-develop.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Oct 28, 2026
Closed
fraseragain
added a commit
to cheqd/product-docs
that referenced
this pull request
Oct 28, 2026
> **Merge after [studio-portal #268](cheqd/studio-portal#268) is deployed.** The pages say the dashboard shows a "Get testnet CHEQ" notice, which only exists once that PR is live. ## What changed Three pages said, or implied, that a new Studio account gets testnet CHEQ automatically. That isn't true, and it's now deliberate: people may want to fund an external wallet instead (see cheqd/studio#858). - **Testnet Faucet**: replaces "New Studio accounts also receive a one-time top-up" with: accounts start with no testnet CHEQ, nothing is sent automatically, and the dashboard tells you when your testnet account is empty. - **Token Top Up**: same correction. It also says Studio calls that write to testnet, such as creating a DID, fail until you request tokens. - **Set Up Your Account**: new **Step 4: Get testnet CHEQ**. It describes the dashboard notice and the Balances & Faucet page, and the later steps are renumbered (Start using cheqd is now Step 5 and Choose a billing plan is Step 6). ## Why On 27 Oct a fresh production account had a testnet balance of 0, and Studio's create-a-DID call failed with a 500. The earlier text from #84 and #88 promised a top-up that never ran for new sign-ups. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
New accounts are not topped up with testnet CHEQ. People may want to fund an external address instead, and the portal now tells new users, on the dashboard, to request tokens from Balances & Faucet (studio-portal PR to follow).
Removed:
bootstrapand inPOST /account/create, and thetopupTestnetanddelegateWithinQuotahelpers.ENABLE_ACCOUNT_TOPUP,TESTNET_INITIAL_TOPUP_CHEQandTESTNET_MINIMUM_BALANCE, from the constants, env types,example.env, the Dockerfile and the README.testnetMinimumBalancefield of the bootstrap status object, which only the top-up set.Unchanged:
POST /account/faucetand its limits.Why
CustomerService.createalready creates it, so the check was always false for new sign-ups. A fresh production account had a balance of 0. Removing the code makes today's behaviour deliberate, so nobody later "fixes" the check and turns auto top-ups on, as production setsENABLE_ACCOUNT_TOPUP=true.Deploy note
Production and staging may still set
ENABLE_ACCOUNT_TOPUP,TESTNET_INITIAL_TOPUP_CHEQorTESTNET_MINIMUM_BALANCEin the DigitalOcean app spec. They are ignored now and can be deleted.How to test
npm run test:unit: 23 suites and 213 tests pass.tsc --noEmitexits 0.src/typesreports only existingno-explicit-anyerrors: 55 ondevelop, 47 with this change (the removed code accounts for the difference). None are new.GET /account/balancesshows testnet balance 0, andPOST /account/faucetwith no body funds the account.Risks
Anything that reads
testnetMinimumBalancefrom the bootstrap response would now see it missing. I found no consumer in this repo.🤖 Generated with Claude Code