Replace current NEAR Helper service with near-faucet.io

[frol]

Let's standardize a Faucet Interface and switch to using near-faucet.io

@flmel Can near-faucet.io create accounts with preloaded NEAR similar to how we currently use NEAR Helper endpoint?

[flmel]

Hey @frol I'm not exactly familiar how the current helper works, but the faucet and its web application have proven stable so I don't see complications doing so. However, the reserve of testnet tokens will deplete so there would be allocation needed.

[frol]

@flmel we just make a POST call to the helper with the following JSON data:

near-cli-rs/src/commands/account/create_account/sponsor_by_faucet_service/mod.rs

Lines 84 to 89 in 9872f3a

	let mut data = std::collections::HashMap::new();
	data.insert("newAccountId", new_account_id.to_string());
	data.insert("newAccountPublicKey", public_key.to_string());
	let client = reqwest::blocking::Client::new();
	let result = client.post(faucet_service_url.clone()).json(&data).send();

Here is the URL we currently use:

near-cli-rs/src/config/mod.rs

Line 53 in 9872f3a

faucet_url: Some("https://helper.nearprotocol.com/account".parse().unwrap()),

It would be great to replace only the URL. Would it be possible to make sure that Faucet Service endpoint supports the parameters?

[akorchyn]

The initiative is nice, but it's blocked right now. As discussed with @flmel, the faucet doesn't have enough capacity (in tokens) to support extended usage, so it's better to stay as is, as the current faucet mints tokens instead.