You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 3, 2024. It is now read-only.
Cooldown faucet controller does not work on HighAvailability setups due to design limitations.
At current implementation faucet authorizations are stored in each of the instance memories, so that same account could be funded twice by the same faucet just by requesting funds to different instances of chain-registry
Implemetation
Opt1: Postgres
A possible solution could be to store faucet authorization at database level which is shared across every chain-registry instance.
Opt2: tx-scheduler
Another possible alternative would be to query tx-scheduler to verify which was the latest funding txs.
Context
Cooldown faucet controller does not work on HighAvailability setups due to design limitations.
At current implementation faucet authorizations are stored in each of the instance memories, so that same account could be funded twice by the same faucet just by requesting funds to different instances of chain-registry
Implemetation
Opt1: Postgres
A possible solution could be to store faucet authorization at database level which is shared across every chain-registry instance.
Opt2: tx-scheduler
Another possible alternative would be to query tx-scheduler to verify which was the latest funding txs.