When setting up futurenet for protocol 18, to send out to developers @rice2000 had to ask if there was a friendbot or a way to get funds. Then someone with the keys had to send out funds to devs "manually".
What would you like to see?
EVM chains have a github repo with chain metadata. For example, the avalanche testnet metadata, includes basic info about the chain as well as rpc servers, txn explorers (infoURL), and most importantly, a list of faucet urls (if there are any).
What alternatives are there?
Not sure if horizon is the best place for this info, but some standardized way of broadcasting faucet URLs for a network might make development, and wallet configuration easier.
Maybe we should use _links in root resource? I remember we had friendbot link in the past but it was removed once we moved the service outside Horizon package.
What problem does your feature solve?
When setting up futurenet for protocol 18, to send out to developers @rice2000 had to ask if there was a friendbot or a way to get funds. Then someone with the keys had to send out funds to devs "manually".
What would you like to see?
EVM chains have a github repo with chain metadata. For example, the avalanche testnet metadata, includes basic info about the chain as well as rpc servers, txn explorers (
infoURL
), and most importantly, a list of faucet urls (if there are any).What alternatives are there?
Not sure if horizon is the best place for this info, but some standardized way of broadcasting faucet URLs for a network might make development, and wallet configuration easier.