core-geth/community

meowsbits

@meowsbits

beep boop

@chunfuyang

hello everybody

Christian Xu

@ChrisXK

Hi There！

Bob Summerwill

@bobsummerwill

Has anybody got a running Core-Geth (or Multi-Geth) archival node?
That is required for running the second 1884 impact analysis.

@meowsbits @shanejonas @BelfordZ @stevanlohja @tzdybal @zcstarr?

Yaz and I got booted off the ETC Labs Discord today so I cannot ask there.

Stevan Lohja

@stevanlohja

@bobsummerwill Isn't Google Query an hosting archival node?

I'm not running an archival node, but I got a spare 1 TB drive that could be put to good use

Bob Summerwill

@bobsummerwill

Hey @stevanlohja,
It really depends what the guy needs.
He has something which ran against a Geth node for the ETH queries.
Which should just work against a Core-Geth archival node.

BigQuery might have enough data to logically support the same kind of analysis, but the interface would be completely different.

Hence easiest path is for anybody on the planet who is running an ETC *-Geth archival node (if there is anybody doing that!) to just run the existing script on their machine.

@meowsbits just replied on ETC Discord.

Stevan Lohja

@stevanlohja

New page in the project site https://core-geth.org/install

Stevan Lohja

@stevanlohja

How to contribute to Mordor testnet
https://medium.com/etc-core/how-to-contribute-to-mordor-testnet-ethereum-classic-881490bdd121

Stevan Lohja

@stevanlohja

New page to the Core-geth docs https://core-geth.org/how-to

Bob Summerwill

@bobsummerwill

Greetings, everyone!

@stevanlohja WRT to the Archival node question above, Yaz ended up starting a Core-Geth archival node and that has caught up now, so we should be able to run the 1884 queries on that very soon.

Chris Hobcroft

@chrishobcroft

Hey all, I'm seeing a load of WARN when running geth -rinkeby -rpc -rpcapi eth,net,web3 --syncmode "light" on 1.9.13-stable

WARN [04-22|12:07:01.574] Served eth_getBlockByNumber              conn=127.0.0.1:55380 reqid=19 t=224.274µs err="no trusted canonical hash trie"
WARN [04-22|12:07:05.776] Served eth_getBlockByNumber              conn=127.0.0.1:55222 reqid=23 t=178.691µs err="no trusted canonical hash trie"
WARN [04-22|12:07:06.574] Served eth_getBlockByNumber              conn=127.0.0.1:55380 reqid=20 t=103.525µs err="no trusted canonical hash trie"
WARN [04-22|12:07:10.776] Served eth_getBlockByNumber              conn=127.0.0.1:55222 reqid=24 t=181.235µs err="no trusted canonical hash trie"
WARN [04-22|12:07:11.575] Served eth_getBlockByNumber              conn=127.0.0.1:55380 reqid=21 t=233.229µs err="no trusted canonical hash trie"

Transactions are still being published successfully, but can someone help me understand what this WARN means, and how I eliminate it?

Vie

@VieYang

How etc fork at block 10,500,839, the config in https://github.com/etclabscore/core-geth/blob/v1.11.9/params/config.go is all eth?

Vie

@VieYang

With flag " --classic", thanks.

bitcodernull

@bitcodernull

i change my node from openeth to core-geth, i need to resync the all blockchain data, it is too slow
where can i download a snapshot for geth,

Yoni Moses

@yonimo

Hi, we're also trying to transition from OpenEthereum to CoreGeth, but it runs out of RAM (32GB) and crashes before it finishes syncing.
I think it happens around the time the sync reaches last Saturday's massive chain reorg.

Where communities thrive

People

Repo info

Activity