Mosaic Faucet is a ethereum faucet that supports multiple chains simultaneously.
Send an HTTP request to a running service that supports the chain that you want to get funded on. Send a POST request like so:
curl -H "Content-Type: text/json" -d '{"beneficiary": "0x3e8880f88cf9a146a9d2c5001037d6d963224b8b@3"}' server:portNote that the beneficiary is of the format address@chain.
address is the address of the beneficiary.
chain is the chain identifier.
In the example above, chain id 3 refers to ropsten.
The service can run in "coin" or "eip20" mode for a chain. It can be different for different chains of the same service. In "coin" mode, the faucet will send base coins of the chain to the beneficiary. In "eip20" mode, the faucet will send a transaction to the configured EIP20 token to make a transfer to the beneficiary.
First, copy ./config/default.json.dist to ./config/default.json.
You can override configuration with environment variables, on the command line, or with environment specific configuration files.
For more help see the config package.
If your config does not include an account for a chain, faucet will ask you to provide a password for a new account.
Faucet will exit after it added a new account to the config, as the config cannot be updated at runtime.
You need to manually restart faucet until all accounts are available in the config.
Faucet will only check for accounts that you add as chain arguments, not for all configured chains.
Each chain in the config must have a Funds object, where Type can be Coin or EIP20.
If it is EIP20, it also requires an Address. The Fund's Amount is sent per request.
Coin means it sends base coins.
EIP20 means it makes a transaction to the EIP20Token at the given address to transfer tokens.
To start, run npm start -- <chains...>.
Chains are identified by their chain id.
E.g. npm start -- 3 200.
For each chain, there must exist a configuration.
The default configuration is in ./config/default.json.
Run npm start -- --help for help.
Mosaic faucet for base coins and EIP20 tokens.
- Server initiates EthNode connections.
- Server initiates Faucets with EthNodes.
- Server accepts HTTP requests.
- Server forwards to correct Faucet to fund address.
- Faucet uses EthNode to send funds.