beaconnode_lighthouse_1 | Dec 27 20:14:24.852 INFO Synced to current epoch current_slot: 18, head_slot: 0, finalized_epoch: 0, finalized_root: 0x0000…0000, peers: 0, service: slot_notifier
beaconnode_lighthouse_1 | Dec 27 20:14:36.830 WARN Low peer count
Thanks. Looks like there are other changes that would have to be made. I'm getting same error:
explorer_lighthouse_1 | 2019/12/30 16:07:15 Config file path: /app/config.yml
explorer_lighthouse_1 | 2019/12/30 16:07:15 HTTP servicer listinging on 0.0.0.0:3334
explorer_lighthouse_1 | time="2019-12-30T16:07:15Z" level=fatal msg="error retrieving last blocks from DB: sql: converting argument $1 type: uint64 values with high bit set are not supported" module=exporter
I'm going to look at adding cli params to https://github.com/sigp/lighthouse/blob/74b327b50d1b67782ae4b030297e0f6ea4b19d88/tests/beacon_chain_sim/src/main.rs#L45 so we can potentially use it for our testing.
Hi, How to get these parameters on my private beaconchain
also the explorer is now compatible with the new prysm testnet to be launched tomorrow
Today we pushed an update that fixes several issues:
- Work around slow RPC response times of the Prysm node under mainnet conditions
- Fix divide by zero crashbug
- Fix block graffiti utf decoding of invalid utf strings (will fall back to ascii decoding if utf8 decoding fails)
- Do not show blockts that are more than 10 seconds in the future in the index view
Wohooo our new design is now live at https://beaconcha.in/ thanks @stefan_star_twitter for your awesome work!
Hi all. Arash from the PegaSys team working on our Eth2 beacon chain client Teku. We're in the process of working through our APIs and one thing I'd like to make sure of is that we support the awesome chain explorers out there! Wondering if you have any docs or if you can share details of which APIs you make use of with Prysm and Lighthouse as we are trying to be as aligned with other clients as possible.
Hi @arash009 we don't have any docs available right now, I guess the best point to start is our rpc_client interface: https://github.com/gobitfly/eth2-beaconchain-explorer/blob/master/rpc/rpc_client.go
unfortunately lighthouse & prsym apis are not really aligned
Is graffiti being decoded properly (UTF)?
https://beaconcha.in/block/86239
https://beacon.etherscan.io/slot/86239
我叫宇少 来自中国
很荣幸认识大家
并且参与以太坊2.0的建设
hi, i'm not familiar with code etc. I tryed following the steps on https://kb.beaconcha.in/tutorial-eth2-multiclient/script-beaconnode-and-validator to become a testnet validator. But when i was in step 3 while waiting for the beaconnode to sync with the blockchain I shut my pc off by accident. How can I see if I'm connected to the blockchain or not? I tried doing the same process from zero but it doesn't seem to work...help anyone?
once you are in sync you will see a message like
INFO initial-sync: Synced up to slot XXXXX
Anyone up for some "ETH2 for dummies" talk
Should we be able to use the set custom name feature yet? Or is that still in progress? The reason I ask is because my 1st deposits were invalid, so I had to make a second valid deposit but the site still says
first valid deposit (0x000000…) for verification indicating that perhaps it didn't pick up the valid deposit yet? Or that feature has a bug, or it's not ready yet, just wondering which :)
Here's 1 of them:
https://beaconcha.in/validator/0x846bd6895e5a85d347b726a9df23a32d486d7082cc40dac37b6e0ea40d68132e52faf3e210d355935fd21ce958c89a73#deposits
It has 2 deposits, 1 invalid, 1 valid, but still says 0x0 under the set custom name popup
