Giter Club home page Giter Club logo

ethstats-server's Introduction

Ropsten (2016) | Rinkeby (2017) | Goerli (2019) | Sepolia (2021) | Holešky (2023)

Goerli (Goerlitzer Testnet)

The --goerli cross-client proof-of-authority testnet configuration.

⚠️ Goerli will be deprecated as of January 2023. It will be supported long term for the longer of three months after the Dencun upgrade is activated on it, or one month after Dencun is activated on the Ethereum mainnet. No further network upgrade will be deployed to the network after this. Please consider using Sepolia moving forward.

To learn more about post-merge testnets check out the Ethereum website or this Devcon 6 talk.

History

Goerli Testnet was the first proof-of-authority cross-client testnet, synching Geth, Nethermind, Hyperledger Besu, and others. This testnet was a community-based project and completely open-source. It was born in September 2018 during ETHBerlin and has been growing in contributors ever since.

The Goerli testnet was merged with the Prater proof-of-stake beacon chain. This marked the end of the permissioned proof-of-authority phase and everyone is now able to run a validator for Goerli. Therefore, this repository contains both Goerli execution-layer and Prater consensus-layer configurations.

Meta data: Goerli

Meta-data: Prater

Prater Testnet (v1.0.1) is the beacon-chain to be merged with the Goerli testnet.

  • Minimum genesis Time: 1614588812 (Mar-01-2021 08:53:32 AM +UTC)
  • Genesis Delay: 1919188 (1616508000, Mar-23-2021 02:00:00 PM +UTC)
  • Genesis Fork Version: 0x00001020 (Prater area code, Vienna)
  • Fork Digest: 0x79df0428 (0xe4be9393 pre-genesis fork digest)
  • Initial State Root: 0x895390e92edc03df7096e9f51e51896e8dbe6e7e838180dadbfd869fdd77a659
  • Genesis Block Root:
    • Without state root update: 0xeade62f0457b2fdf48e7d3fc4b60736688286be7c7a3ac4c9a16a5e0600bd9e4
    • With state root update: 0x8c0ebce425ca04612f8a4c9b3d9b339121a62a8fe2baf8ff2c6f77b81194ee87
  • Genesis Validators Root: 0x043db0d9a83813551ee2f33450d23797757d430911a9320530ad8a0eabc43efb
  • Deposit Contract: 0xff50ed3d0ec03aC01D4C79aAd74928BFF48a7b2b (Goerli Testnet)
  • Deposit Contract Block: 4367322 (0x5ac670562dbf877a45039d65ec3c2e3402a40eda9b1dba931c2376ab7d0927c2)

Contribute

Run a node and report bugs!

ethstats-server's People

Contributors

5chdn avatar ayushyachitransh avatar bandrewk avatar bingochen87 avatar bryant1410 avatar chainsafesystems avatar cubedro avatar debris avatar dependabot[bot] avatar elasticroentgen avatar ethernomad avatar frozeman avatar g11tech avatar hackmod avatar jamesdave avatar jesuscript avatar jorisbontje avatar karalabe avatar petertheone avatar q9f avatar rmlearney-digicatapult avatar skylenet avatar soc1c avatar trustfarm-dev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ethstats-server's Issues

Cannot Show Node on Dashboard

Description

I don't see any nodes listed in the ethstats dashboard, but in ethstats-client it works fine. is there something wrong with my configuration?

Logs

0|node-app  | 2023-11-17 08:00 +00:00: [eth] =i= {
0|node-app  | 2023-11-17 08:00 +00:00:   id: 'engramTokio',
0|node-app  | 2023-11-17 08:00 +00:00:   stats: {
0|node-app  | 2023-11-17 08:00 +00:00:     active: true,
0|node-app  | 2023-11-17 08:00 +00:00:     syncing: false,
0|node-app  | 2023-11-17 08:00 +00:00:     mining: false,
0|node-app  | 2023-11-17 08:00 +00:00:     hashrate: 0,
0|node-app  | 2023-11-17 08:00 +00:00:     peers: 30,
0|node-app  | 2023-11-17 08:00 +00:00:     gasPrice: '1000000007',
0|node-app  | 2023-11-17 08:00 +00:00:     uptime: 100
0|node-app  | 2023-11-17 08:00 +00:00:   }
0|node-app  | 2023-11-17 08:00 +00:00: }
0|node-app  | 2023-11-17 08:00 +00:00: [eth] >>> Chain Filter triggered:  0x101d5b6c4c03e01e96f6910699785ea3c7589c38af261fa72c6cddd534f9e5e2 - last trigger: 12003
0|node-app  | 2023-11-17 08:00 +00:00: [eth] ==> Got block 0x101d5b6c4c03e01e96f6910699785ea3c7589c38af261fa72c6cddd534f9e5e2 in: 0.602ms
0|node-app  | 2023-11-17 08:00 +00:00: [eth] ==> Got block: 4438
0|node-app  | 2023-11-17 08:00 +00:00: [wsc] =s= Sending block update
0|node-app  | 2023-11-17 08:00 +00:00: [eth] =✓= Finished processing latest queue
0|node-app  | 2023-11-17 08:00 +00:00: [eth] ==> Getting Pending
0|node-app  | 2023-11-17 08:00 +00:00: [eth] ==> Got 0 pending txs in 1 m

display gets corrupted on bogus data

Reopen goerli/netstats-server#13 by @veox

Most commonly visible on bar-graphs for block time, difficulty, transaction count...

The most common cause is someone accidentally connecting a node from network X to dashboard of network Y; but this could also happen due to malice.

In general, the dashboard is overly trusting in accepting the data fed to it as correct, and does not gracefully handle conflicts.

Server crash due to response from one client

The error log is as follows:

/root/ethstats-server/lib/history.js:339
                .value();
                 ^

TypeError: _(...).sortBy(...).slice(...).forEach(...).reverse(...).value is not a function
    at History.getNodePropagation (/root/ethstats-server/lib/history.js:339:4)
    at Collection.addBlock (/root/ethstats-server/lib/collection.js:88:46)
    at Sparky.<anonymous> (/root/ethstats-server/app.js:185:10)
    at emitOne (events.js:116:13)
    at Sparky.emit (events.js:211:7)
    at Sparky.incoming (/root/ethstats-server/node_modules/primus-emit/index.js:72:44)
    at transform (/root/ethstats-server/node_modules/primus/spark.js:312:33)
    at Sparky.transforms (/root/ethstats-server/node_modules/primus/spark.js:330:4)
    at decoding (/root/ethstats-server/node_modules/primus/spark.js:215:13)
    at Sparky.decoder (/root/ethstats-server/node_modules/primus/parsers/json.js:34:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.

Another instance of failure resulted in different logs. This failure was caused when netstats server was restarted and client reconnected itself:

2019-03-12 07:45:31.368 [API] [CON] Connected auth03Localhost
/root/ethstats-server/lib/history.js:286
        if( !_.isUndefined(best.height) )
                                ^

TypeError: Cannot read property 'height' of undefined
    at History.bestBlockNumber (/root/ethstats-server/lib/history.js:286:26)
    at Collection.canNodeUpdate (/root/ethstats-server/lib/collection.js:305:55)
    at Collection.requiresUpdate (/root/ethstats-server/lib/collection.js:315:16)
    at Sparky.<anonymous> (/root/ethstats-server/app.js:335:14)
    at emitOne (events.js:116:13)
    at Sparky.emit (events.js:211:7)
    at Sparky.incoming (/root/ethstats-server/node_modules/primus-emit/index.js:72:44)
    at transform (/root/ethstats-server/node_modules/primus/spark.js:312:33)
    at Sparky.transforms (/root/ethstats-server/node_modules/primus/spark.js:330:4)
    at decoding (/root/ethstats-server/node_modules/primus/spark.js:215:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node ./bin/www`

Related to #10

LAST BLOCKS MINERS section doesn't show miner address

We are running this server for testnet chain (stats.mosaicdao.org). The LAST BLOCKS MINERS section on the UI shows 0000000000000000000000000000000000000000.

Looking at the code looks like it reads the miner key from the block info which is 0x0000000000000000000000000000000000000000 for POA chains.

However for goerli (https://stats.goerli.net/) which is also a POA, we see miner addresses being displayed. Are we using a different fork / branch for hosting the server for Goerli ?

Unable to run: SyntaxError: Unexpected token '>'

Unable to run after install. Followed all steps using { node: '16.17.0', npm: '8.15.0' }.

Any thoughts?

WS_SECRET="asdf" npm start

> [email protected] start
> node ./bin/www

/root/ethstats-server/lib/express.js:31
    await new Promise<void>((resolve) => {
                          ^

SyntaxError: Unexpected token '>'
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1055:15)
    at Module._compile (node:internal/modules/cjs/loader:1090:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/root/ethstats-server/app.js:39:12)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)

I don't see my node at localhost: 3000 - windows

  • Hi I am testing with app.json

[
{
"name" : "XXXXX",
"script" : "app.js",
"log_date_format" : "YYYY-MM-DD HH:mm Z",
"merge_logs" : false,
"watch" : false,
"max_restarts" : 10,
"exec_interpreter" : "node",
"exec_mode" : "fork_mode",
"env":
{
"NODE_ENV" : "production",
"RPC_HOST" : "localhost",
"RPC_PORT" : "8545",
"LISTENING_PORT" : "30303",
"INSTANCE_NAME" : "XXXXXX",
"CONTACT_DETAILS" : "",
"WS_SERVER" : "ws://stats.goerli.net:3000",
"WS_SECRET" : "asdf",
"VERBOSITY" : 2
}
}
]

  • I run npm and when I open localhost: 3000 it doesn't open the stats and I don't see my node in the list either ...
    What am I doing wrong?

CAN ANYONE SENT ME GOERLI TO THIS 0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e

0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e0xE834bf72F2df2F4E8e6fd2b9Cfeb0C3EcBdB8A4e

On goerli ethstats, one of the clients causes server to crash

Running the latest version of eth-net-intelligence-api.
Each time I bring back my client it crashes the server at: https://stats.goerli.net/

The crash causes ethstats to display first:
Bad Gateway message (just tex on empty screen)
then
Service Unavailable message

CONFIG:

{
"name" : "node-app-goerli",
"script" : "app.js",
"log_date_format" : "YYYY-MM-DD HH:mm Z",
"merge_logs" : false,
"watch" : false,
"max_restarts" : 10,
"exec_interpreter" : "node",
"exec_mode" : "fork_mode",
"env":
{
"NODE_ENV" : "production",
"RPC_HOST" : "localhost",
"RPC_PORT" : "8546",
"LISTENING_PORT" : "30313",
"INSTANCE_NAME" : "Nethermind-VM1-Goerli",
"CONTACT_DETAILS" : "https://gitter.im/nethermindeth/nethermind",
"WS_SERVER" : "https://stats.goerli.net",
"WS_SECRET" : "[removed]",
"VERBOSITY" : 2
}
}

rogress: 1 }
0|node-app-goerli | 2019-01-04 21:53 +00:00: [eth] =i= SYNC UPDATE: { startingBlock: 0,
0|node-app-goerli | 2019-01-04 21:53 +00:00: currentBlock: 317791,
0|node-app-goerli | 2019-01-04 21:53 +00:00: highestBlock: 317791,
0|node-app-goerli | 2019-01-04 21:53 +00:00: progress: 1 }
0|node-app-goerli | 2019-01-04 21:53 +00:00: [eth] =i= { id: 'nethermindVm1Goerli',
0|node-app-goerli | 2019-01-04 21:53 +00:00: stats:
0|node-app-goerli | 2019-01-04 21:53 +00:00: { active: true,
0|node-app-goerli | 2019-01-04 21:53 +00:00: syncing:
0|node-app-goerli | 2019-01-04 21:53 +00:00: { startingBlock: 0,
0|node-app-goerli | 2019-01-04 21:53 +00:00: currentBlock: 317792,
0|node-app-goerli | 2019-01-04 21:53 +00:00: highestBlock: 317792,
0|node-app-goerli | 2019-01-04 21:53 +00:00: progress: 1 },
0|node-app-goerli | 2019-01-04 21:53 +00:00: mining: false,
0|node-app-goerli | 2019-01-04 21:53 +00:00: hashrate: 0,
0|node-app-goerli | 2019-01-04 21:53 +00:00: peers: 13,
0|node-app-goerli | 2019-01-04 21:53 +00:00: gasPrice: '20000000000',
0|node-app-goerli | 2019-01-04 21:53 +00:00: uptime: 100 } }
0|node-app-goerli | 2019-01-04 21:53 +00:00: [eth] =i= SYNC UPDATE: { startingBlock: 0,
0|node-app-goerli | 2019-01-04 21:53 +00:00: currentBlock: 317792,

Connection undefined

Question one:

When the ethstats-server is running, nodes data can be displayed, but there is message like:
[API] [CON] Connection with: Lt1XrvDE3_ez61K_tV9Ng ended: undefined
what's its meaning?and how to fix?

Question two:

In the display web, LAST BLOCK MINERS item is always all zeros number, not the miner adddress. see below:
image

Please help.thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.