webb-tools/webb-faucet

A faucet for testnet bridges.

webb-faucet's Issues

[BUG] First claim was error but recorded as claimed

I requested ttnt, it gave an error, I requested it again, this time it gave me the warning that you have already requested it. So I couldn't get ttnt
5FyJdNappo2WWYYAm1G7y6JzJwbqkhEhCpcCZKJzGhDHZm9q

[TASK] Deploy Webb Faucet

Overview

We need to deploy the faucet so we can use it four our internal testing. that will require few steps and tasks first, I listed all of them blew:

Task checklist

• Move the time to wait between two claims to the config; so that we can configure it with less than 24h for testing.
• Move the amount of tokens that the faucet sends to the config
• Create a basic CI/lints for the faucet project
• Create a release process that will create a new container image when we push to main branch or a new tag.
• Deploy the faucet on of the boxes (probably next to the Orbit Network itself)
• Allocate a subdomain for the faucet backend and the frontend.
• Test everything once it is done.

[TASK] Add secret key abstraction for reading values from toml file

Overview

The current repository simply uses a toml file to set and read secret values but currently there is no abstraction to protect those values when it is in a hosted environment.

We will need to implement an abstraction to read secret values from the toml file similarly as we do on the relayer.

Task Checklist

• Add secret key abstraction for reading values from toml file

[TASK] Authenticated routes for authorization token in header

Checklist

• Ensure that routes are protected w/ OAuth token authorization.

[BUG] Time rate limit check is wrong

This check here:

webb-faucet/src/faucet.rs

Line 269 in a775d00

if last_claim_date <= now.checked_add_signed(v).unwrap() {

it should be:

now < last_claim_date + v

Bug Playground
Fixed code Playground

API for Getting Supported Tokens Info on the Faucet

Description

Currently, the cryptocurrency faucet does not have an API to retrieve information on supported tokens. This feature is necessary for developers who are building on top of the faucet and need to programmatically get the list of supported tokens.

Proposed Solution

Add a new API to the Faucet Backend repo to get supported tokens info. Ideally, the endpoint will return a list of supported tokens with their corresponding information such as token name, symbol, address, and supported typed chain ID.

Acceptance Criteria

• A new endpoint is added to the Faucet Backend repo that returns supported tokens info.
• The response should include the token name, symbol, address, and supported typed chain ID.
• Documentation for the new endpoint should be added to the API documentation.

[TASK] Add a separate CLI tool to export `UserInfo` data as a json file

• Given the database path as an argument, read all the UserInfo data from the database.
• Convert these UserInfo as a hashmap from adresses to twitter user Id
• Encode the result and output them as json format for later processing.

Enabling Users to Request the Native Token

Currently, when requesting to mint a token on the faucet, the request only contains the chain ID and wallet address. The faucet should also support the token address in the request.

On some self-hosted chains, such as Orbit chains, it is necessary to fund the native token in addition to fungible tokens, as users may need native tokens to pay transaction fees.

Task

• Adding the token address to the request allows the user to request a specific token.
• Adding logic to allow users to mint the native token on self-hosted chains when the requested token address is the zero address.

[BUG] The server cannot handle two simultaneous requests

Details :

When two requests are sent at the same time, the first request fails and only the second request is processed. In the below example the first user's request timedout in UI and couldnt claim again since the server recorded the claim but the actual transaction did not complete

Possible Solutions:

• Enable simultaneous processing
• Record claimed only if transaction is successful

[TASK] Disperse faucet funds

Checklist

• Create connections to all chains that we use
• Send the faucet tx to the recipient

EVM chains

EVM chains will have wtTNT. When we disperse this wtTNT it implies the deposit of funds on the bridge from the Tangle testnet. Therefore, we need to actually deposit funds into the bridge so that these wtTNT effectively exist.

Tangle

For Tangle, when we disperse faucet funds, we should simply disperse tTNT.

[BUG] TNT substrate transfers don't work

CC @AtelyPham who has described this to me.

[TASK] Allow to skip twitter verification

[TASK] Add support for Tangle evm new chainid

[TASK] Add support for Tangle Substrate

Checklist

• Add Support for Substrate based chains
• Add support for Tangle Substrate