gobitfly/beaconchain-explorer

mkinney

@mkinney

Is there a reason why these are unsigned ints?

func GetLastPendingAndProposedBlocks(startEpoch, endEpoch uint64) ([]*types.MinimalBlock, error) {

mkinney

@mkinney

I think the problem is that the code does not expect zeros for the start epoch and will -1, which would cause the overflow. I mucked around with it for a bit, but I think it would be better after they re-start their testnet. (lighthouse)

Peter Pratscher

@ppratscher

AFAIK those are all unsigned ints as the Prysm data types were only using them and we started from them

mkinney

@mkinney

Those are fine... it is the sql interface only allows for signed ints, so when you have something like foo := uint64(0) - 1 and use foo as an arg to a sql statement, then you run into that error with hight bit set above.

Peter Pratscher

@ppratscher

hm it looks like somehow the start epoch parameter underflows for some reason

this might happen if head.FinalizedEpoch is 0

will add a fix for that cases

mkinney

@mkinney

Thanks. That'd be great. If you take a look at mkinney/eth2-beaconchain-explorer@79e04d3 you'll be able to see that db error. I am going to wait until Lighthouse re-launches their testnet before doing much more.

Peter Pratscher

@ppratscher

you can try their testnet3 branch

the explorer should be compatible with that one

mkinney

@mkinney

not sure how to use their testnet3 from docker image

lighthouse bn --http-address 0.0.0.0 --ws-address 0.0.0.0 --http testnet -r -t 1000 recent 16

change testnet to testnet3 ?

Peter Pratscher

@ppratscher

no, check out the testnet3 branch, build the docker image and run it normally

mkinney

@mkinney

ok, will do. thx

Peter Pratscher

@ppratscher

imo the lighthouse testnet is currently a bit more interresting as it runs under mainnet condition with 16k validators

mkinney

@mkinney

I agree that is more interesting, but I'm trying to put together some integration-like testing... kinda hard when things are not "ready"... but I think your idea to build off their testnet3 branch locally might work... will see in 15 minutes or so...

Peter Pratscher

@ppratscher

sounds good

mkinney

@mkinney

the finalized epoch is still 0 so I'm still hitting that db error

I guess I'll wait until you can add a fix for that case

I see there is no description for https://hub.docker.com/repository/docker/gobitfly/eth2-beaconchain-explorer/general . I just recently figured out how to update that info. Want me to do a PR against it?

you have to fork off of https://github.com/docker-library/docs

mkinney

@mkinney

hmm.. that's for official docker images...

Peter Pratscher

@ppratscher

Hm let me take a look at that and get back to you tomorrow re the docket docs

mkinney

@mkinney

ok. no worries. no rush...

Peter Pratscher

@ppratscher

Finalized epoch should not be 0 in the testnet

mkinney

@mkinney

oh, then it could be something stupid I'm doing then...

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

Peter Pratscher

@ppratscher

If you start a local testnet you will likely also need validators that Attest on blocks

mkinney

@mkinney

hmm... k

Peter Pratscher

@ppratscher

@mkinney I've just pushed a fix for the db error you were seeing

mkinney

@mkinney

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

mkinney

@mkinney

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.

mkinney

@mkinney

Created a PR on their repo. Once they have that merged, I think we can use it to spin up Lighthouse testnet easier than what I was attempting.

Peter Pratscher

@ppratscher

nice, thanks :+1:

Sergio Rios

@peepoman12_twitter

I hope this helps me get this right

Tom_Wang

@TomWang10

https://files.gitter.im/ethereum/remix/yoLB/image.png

Hi, How to get these parameters on my private beaconchain

Peter Pratscher

@ppratscher

Hi, you should get them from the chain config of your beacon node

Peter Pratscher

@ppratscher

@mkinney we finaly have a fix for the error you are experiencing, will ship it today

Peter Pratscher

@ppratscher

fix is now released

also the explorer is now compatible with the new prysm testnet to be launched tomorrow

Peter Pratscher

@ppratscher

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

Peter Pratscher

@ppratscher

Wohooo our new design is now live at https://beaconcha.in/ thanks @stefan_star_twitter for your awesome work!

Stefan Star

@stefan_star_twitter

Arash

@arash009

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.

Peter Pratscher

@ppratscher

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

Arash

@arash009

Ahh perfect, thank you. That will do us just fine as a starting point. We are trying to be as aligned with the other clients as possible.

Where communities thrive

People

Repo info

Activity