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
Copy file name to clipboardExpand all lines: cmd/faucet/README.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,38 +10,40 @@ The `faucet` is a single binary app (everything included) with all configuration
10
10
11
11
First thing's first, the `faucet` needs to connect to an Ethereum network, for which it needs the necessary genesis and network infos. Each of the following flags must be set:
12
12
13
-
-`--genesis` is a path to a file containin the network `genesis.json`
14
-
-`--network` is the devp2p network id used during connection
15
-
-`--bootnodes` is a list of `enode://` ids to join the network through
13
+
-`-genesis` is a path to a file containin the network `genesis.json`. or using:
14
+
-`-goerli` with the faucet with Görli network config
15
+
-`-rinkeby` with the faucet with Rinkeby network config
16
+
-`-network` is the devp2p network id used during connection
17
+
-`-bootnodes` is a list of `enode://` ids to join the network through
16
18
17
19
The `faucet` will use the `les` protocol to join the configured Ethereum network and will store its data in `$HOME/.faucet` (currently not configurable).
18
20
19
21
## Funding
20
22
21
23
To be able to distribute funds, the `faucet` needs access to an already funded Ethereum account. This can be configured via:
22
24
23
-
-`--account.json` is a path to the Ethereum account's JSON key file
24
-
-`--account.pass` is a path to a text file with the decryption passphrase
25
+
-`-account.json` is a path to the Ethereum account's JSON key file
26
+
-`-account.pass` is a path to a text file with the decryption passphrase
25
27
26
28
The faucet is able to distribute various amounts of Ether in exchange for various timeouts. These can be configured via:
27
29
28
-
-`--faucet.amount` is the number of Ethers to send by default
29
-
-`--faucet.minutes` is the time to wait before allowing a rerequest
30
-
-`--faucet.tiers` is the funding tiers to support (x3 time, x2.5 funds)
30
+
-`-faucet.amount` is the number of Ethers to send by default
31
+
-`-faucet.minutes` is the time to wait before allowing a rerequest
32
+
-`-faucet.tiers` is the funding tiers to support (x3 time, x2.5 funds)
31
33
32
34
## Sybil protection
33
35
34
36
To prevent the same user from exhausting funds in a loop, the `faucet` ties requests to social networks and captcha resolvers.
35
37
36
38
Captcha protection uses Google's invisible ReCaptcha, thus the `faucet` needs to run on a live domain. The domain needs to be registered in Google's systems to retrieve the captcha API token and secrets. After doing so, captcha protection may be enabled via:
37
39
38
-
-`--captcha.token` is the API token for ReCaptcha
39
-
-`--captcha.secret` is the API secret for ReCaptcha
40
+
-`-captcha.token` is the API token for ReCaptcha
41
+
-`-captcha.secret` is the API secret for ReCaptcha
40
42
41
43
Sybil protection via Twitter requires an API key as of 15th December, 2020. To obtain it, a Twitter user must be upgraded to developer status and a new Twitter App deployed with it. The app's `Bearer` token is required by the faucet to retrieve tweet data:
42
44
43
-
-`--twitter.token` is the Bearer token for `v2` API access
44
-
-`--twitter.token.v1` is the Bearer token for `v1` API access
45
+
-`-twitter.token` is the Bearer token for `v2` API access
46
+
-`-twitter.token.v1` is the Bearer token for `v1` API access
45
47
46
48
Sybil protection via Facebook uses the website to directly download post data thus does not currently require an API configuration.
0 commit comments