Deploy Faucet

[carterqw2]

Tasks

Beta Give feedback

1. Create a feature branch of the Faucet app
2. Get a faucet account
3. Deploy the faucet app #80
   +0
4. Embed faucet into Block Explorer #81
   +0
5. Monitor faucet funds and alert on low funds

[carterqw2]

Blocked by https://celo-org.slack.com/archives/C0117G4T96W/p1695905547607849

[lvpeschke]

@carterqw2 the link in #54 (comment) is broken, could you explain the blocker?

[aaronmgdr]

@carterqw2 If we fund 0x22579CA45eE22E2E16dDF72D955D6cf4c767B0eF on the testnet with lots of celo (but not too much*) we can use existing setup. especially if the node url and chain id remain the same as alajores

• want to avoid draining the faucet and not having a source of funds to top up.

[aaronmgdr]

One TODO to add might be to add a low level alert on grafana when the faucet gets down to about 15,000 tokens. together with a way any eng at clabs can refill it

[aaronmgdr]

After talking it turns out that

A) there is already alerting https://github.com/celo-org/devrel-x-product-clabs/issues/2.
B) since we are migrating instead of starting up from scratch that super faucet account will not exist
C) since MintCeloTokenSchedule still sends funds to carbonOffsetFund the faucet will stll recieve new funds each time that is called. so yay. nothing to do here

[lvpeschke]

@aaronmgdr is #81 still desirable? Should there be a task for updated documentation around the faucet?

[aaronmgdr]

I never thought 81 was needed.

I dont see there being anything that must happen here.