ava-labs / avalanche-faucet-legacy Goto Github PK

While trying to fund my Metamask address on the local C-Chain I get this error:

Error: Returned error: nonce too low
    at Object.ErrorResponse (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/web3-core-helpers/src/errors.js:29:16)
    at /usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/web3-core-requestmanager/src/index.js:170:36
    at XMLHttpRequest.request.onreadystatechange (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/web3-providers-http/src/index.js:111:13)
    at XMLHttpRequestEventTarget.dispatchEvent (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/xhr2-cookies/dist/xml-http-request-event-target.js:34:22)
    at XMLHttpRequest._setReadyState (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/xhr2-cookies/dist/xml-http-request.js:208:14)
    at XMLHttpRequest._onHttpResponseEnd (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/xhr2-cookies/dist/xml-http-request.js:318:14)
    at IncomingMessage.<anonymous> (/usr/local/go/bin/src/github.com/ava-labs/ava-faucet/node_modules/xhr2-cookies/dist/xml-http-request.js:289:61)
    at IncomingMessage.emit (events.js:327:22)
    at endReadableNT (_stream_readable.js:1221:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

which makes the transaction failed altogether. Tried a couple of things and saw the nonce is actually 0 when doing web3.eth.getTransactionCount(myAddress), but I am not sure is this is the nonce from Ethereum mainnet? Actually, it should be 0 too on the local C-Chain since I didn't make any transaction from that address.

Then it worked once when restarting the faucet (npm run serve) but I didn't do anything special 🤷 Strange

"Can the faucet URL take a wallet address as input so I can more easily script it in to an semi automated setup? Captcha would still be manual of course."

Hey there,

Testnet deployment is on pause because we cannot get any faucet avax from https://faucet.avax-test.network/

Gas is very high on fuji and complete deployment takes us around 25 faucet avax to complete...

Could you please help us?

We are getting all sorts of errors regarding nonce and tx failed. And after first failed try, ip gets blocked which is so annoying.

Does not recognize "localhost" as a domain, but does local IP.

I'm getting this error each time i try to get faucet from a local installation.
Here are the logs and the error:
INFO Starting development server...
10% building 2/2 modules 0 active(X) Droplet size: 1000000000
Asset Id: AVAX
Faucet Address: X-local18jma8ppw3nhx5r4ap8clazz0dps7rv5u00z96u
(C) Available Balance: 0
(C) Droplet size: 200000000000000000
(C) Address: 0x751A0B96e1042BeE789452ECb20253Fba40dbE85
Updated Asset Id: 2fombhL7aGPwj3KH4bfrmJwW6PVnMobf9Y2fn9GwxiAAJyFDbe
(X) Available Balance: 300000000000000000
(X) Droplet size: 1000000000
(X) Tx Fee: 100000
40% building 33/71 modules 38 active ...er\lib\index.js??vue-loader-options!-------\faucet-site\node_modules\eslint-loader\index.js??ref--13-0!-------\faucet-site\src\views\Index.vueBrowserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
98% after emitting CopyPlugin

DONE Compiled successfully in 11089ms 14:42:40

App running at:

• Local: http://localhost:8080/
• Network: http://X.X.X.X:8080/

Note that the development build is not optimized.
To create a production build, run npm run build.

(node:8268) UnhandledPromiseRejectionWarning: Error: Returned error: insufficient funds for gas * price + value, balance: 0, cost: 210500000000000000
at Object.ErrorResponse (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\web3-core-helpers\src\errors.js:29:16)
at D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\web3-core-requestmanager\src\index.js:140:36
at XMLHttpRequest.request.onreadystatechange (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\web3-providers-http\src\index.js:110:13)
at XMLHttpRequestEventTarget.dispatchEvent (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\xhr2-cookies\dist\xml-http-request-event-target.js:34:22)
at XMLHttpRequest._setReadyState (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\xhr2-cookies\dist\xml-http-request.js:208:14)
at XMLHttpRequest._onHttpResponseEnd (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\xhr2-cookies\dist\xml-http-request.js:318:14)
at IncomingMessage. (D:\Projets\blockchain\PACTE\faucet\faucet-site\node_modules\xhr2-cookies\dist\xml-http-request.js:289:61)
at IncomingMessage.emit (events.js:214:15)
at endReadableNT (_stream_readable.js:1178:12)
at processTicksAndRejections (internal/process/task_queues.js:77:11)
(node:8268) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8268) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I'm running a local test network with avash and the five_node_stakin.lua script.

getting this error while running yarn serve

On the official faucet website, after google recaptcha validation, when clicking on "Request ...", I got the following JS error :

    at t.exports (createError.js:16)
    at XMLHttpRequest.l.ontimeout (xhr.js:95)```

Tried both on mobile, wifi and wired connexion. 

This is a minor bug and not breaking anything. When you start the faucet in production mode it says it has no balance. In fact it really has.

If you query the balance you get the real amount:
{
"jsonrpc": "2.0",
"result": {
"balance": "45000000000000000"
},
"id": 2
}

Description:
Instead of giving a copy-paste response, I will add the link
https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/11-Client_Side_Testing/09-Testing_for_Clickjacking

Impact:
An attacker can iframe the website and gain unwanted clicks over. With the level of creativity can allow an attacker to create an iframe change the transparency of the iframe to gain clicks on the website and make a transaction.

Suggested Fix:
Add x-frame-option header and set it to deny or the same origin

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options

I try the QR code reader and found two issues :

1. If the context is not https, camera won't be loaded. It is mostly a deployment problem, however I did not find an advice saying you should deploy on https and the official faucet website does not redirect to https although it is available.

2. When you are on a mobile phone, it load the front camera without option to change it to the back. There is an option to specify you would like the back camera, and it could be nice to offer a way to change the camera.
   I did not found the repo ava-labs/vue_components.

I'm following the 'quickstart' guide and am trying to get some fund from the Ava test faucet to my newly created address and it always fails :

Yarn install fails due to a conflicting versions of "Vuetify-loader" package in dependencies and in "devDependencies" section.

After a successful transaction the faucet should display the transaction id.