Testnet Faucet?

TestNet
1

Hi–

Are there plans for a “faucet” of some kind during testnet, to supply accounts with funds?

Thanks,
Nick

1 Like
2

Never mind, I found it:

https://bank.testnet.algorand.network/

I think it might make sense to include this earlier in the docs, around install and account creation, as later docs refer to sending transactions etc which you can only do if you have a balance

1 Like
3

Ah, I actually see it now

https://bank.testnet.algorand.network

I think it would make sense to include a link to this higher up in the docs, after account creation but before send

4

I am hesitant to move that further up as it is in the testing link and in the developer faq. The goal docs should work with any network ie TestNet, MainNet and Private Networks. I would like to keep them more generic.

5

Testnet Faucet is not working as of 12/19. please fix. https://bank.testnet.algorand.network/

6

We have someone working on it now. They will update here when fixed. Thanks!

7

The testnet faucet is back online.

8

Yes. Thanks. it is working now.

9

Testnet faucet is temporary offline. I will bring it back online within the hour.

10

Testnet fault maintenance is complete.

11

Unable to add microalgos to my testnet account in my testnetwallet.

I get a 200 OK success response when I dispense cash for my test net account created but when i run the command `goal account balance -a ’
it shows 0 microalgos

Any help is appreciated

12

@ron_ron,

two questions -

  1. is your node is caught up ?
  2. can you see the account balance updated correctly on algoexplorer ?
13

2> Yes the account balance in algoexplorer is updated.
1> The testnode is not caught up but it shows the foll result:-
Last committed block: 636047
Time since last block: 0.0s
Sync Time: 0.0s
Last consensus protocol: https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0
Next consensus protocol: https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0
Round for next consensus protocol: 636048
Next consensus protocol supported: true
Genesis ID: testnet-v1.0

I see the last committed block on algoexplorer different than what I have on my local but have observed here that neither the next committed block nor the sync time changes even after running for several hours.

Also whenever I try to change the status of my test accounts to online, it throws an error.

Couldn’t sign tx: HTTP 400 Bad Request: TransactionPool.Remember: transaction SLIZBRF4VQPQJ5JRLWXC2CRDK64KVNLVWNUFNJVYCHYBYFZXXULQ: overspend (account WEJOSGOGK45VAS4AQHY77TFOGVX4ZQQKNJQHRM3FN7NGZ6IBQRYBEM6EDY, data {_struct:{} Status:Offline MicroAlgos:{Raw:0} RewardsBase:0 RewardedMicroAlgos:{Raw:0} VoteID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] SelectionID:[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] VoteFirstValid:0 VoteLastValid:0 VoteKeyDilution:0 AssetParams:map Assets:map}, tried to spend {1000}) (for multisig accounts, write tx to file and sign manually)

14

The reason you get the error is because the local node doesn’t know that your account has algo because it is stuck so far in the past of the ledger.

Have you tried updating your test node?

15

How do you update it? I thought whenever I run testnet it should update by itself just like mainnet does

16

Given that your local node is at round 636047, and the testnet is at round 7 million( https://testnet.algoexplorer.io), it’s not entirely surprising.
You won’t be able to send any transaction, nor to see any updated account information until your node is synchronized with the testnet.

17

Both TestNet and MainNet nodes need to be kept updated. See https://developer.algorand.org/docs/run-a-node/setup/install/#updating-node for details about how to keep your node updated.