Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 09 12:57

    qu0b on master

    fix slot viz (#753) Co-authore… (compare)

  • Apr 09 12:52

    qu0b on slotviz

    fix slot viz (compare)

  • Apr 09 12:51

    qu0b on slotviz

    fix slot viz (compare)

  • Apr 08 13:16

    qu0b on master

    fix stats export buttons (#751)… (compare)

  • Apr 08 12:57

    qu0b on stats

    fix stats export buttons (compare)

  • Apr 08 11:27

    guybrush on master

    Widget (#750) * added widget s… (compare)

  • Apr 08 09:37

    guybrush on master

    api: encode nil values as null … (compare)

  • Apr 07 13:54

    qu0b on master

    Update layout.html (#748) (compare)

  • Apr 07 13:45

    qu0b on master

    Update layout.html (#747) Co-a… (compare)

  • Apr 07 13:35

    qu0b on master

    fix mobile banner (#745) Co-au… (compare)

  • Apr 07 09:38

    qu0b on master

    gitignore: only css and js not … (compare)

  • Apr 07 09:36

    qu0b on bundle

    Merge branch 'master' into fix/… readd webfonts Merge branch 'fix/bundle' of gi… (compare)

  • Apr 07 09:35

    qu0b on bundle

    fix/banners (#743) * add new a… Merge branch 'master' into fix/… (compare)

  • Apr 07 09:34

    qu0b on bundle

    gitignore: only css and js not … (compare)

  • Apr 06 15:29

    qu0b on master

    fix/banners (#743) * add new a… (compare)

  • Apr 06 15:12

    qu0b on banners

    add new ad-zone, fix stakingSer… merge master (compare)

  • Apr 06 15:11

    qu0b on banners

    add new ad-zone, fix stakingSer… Update stakingServices.html Merge branch 'newbanners' of ht… and 2 more (compare)

  • Apr 06 15:05

    qu0b on revert-740-newbanners

    Revert "add new ad-zone, fix st… (compare)

  • Apr 06 15:05

    qu0b on master

    add new ad-zone, fix stakingSer… (compare)

  • Apr 06 11:43

    qu0b on master

    add berlin HF banner (#722) * … (compare)

mkinney
@mkinney
so... we may just use that... heh he heh
Peter (bitfly)
@peterbitfly
That looks promising
mkinney
@mkinney
What indexer config values do you use for lighthouse? port "5052"? host "http://somehost"?
and to start the lighthouse beacon node, I'm using lighthouse bn --http-address 0.0.0.0 --ws-address 0.0.0.0 --http testnet -r quick 8 $(date +%s)
mkinney
@mkinney
I think I'm getting closer... but I'm getting this error, explorerlighthouse_1 | time="2019-12-20T20:10:01Z" 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
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
no, check out the testnet3 branch, build the docker image and run it normally
mkinney
@mkinney
ok, will do. thx
Peter (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
If you start a local testnet you will likely also need validators that Attest on blocks
mkinney
@mkinney
hmm... k
Peter (bitfly)
@peterbitfly
@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 (bitfly)
@peterbitfly
nice, thanks :+1:
Sergio Rios
@peepoman12_twitter
I hope this helps me get this right
Hi, How to get these parameters on my private beaconchain
Peter (bitfly)
@peterbitfly
Hi, you should get them from the chain config of your beacon node
Peter (bitfly)
@peterbitfly
@mkinney we finaly have a fix for the error you are experiencing, will ship it today
Peter (bitfly)
@peterbitfly
fix is now released
also the explorer is now compatible with the new prysm testnet to be launched tomorrow
Peter (bitfly)
@peterbitfly
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 (bitfly)
@peterbitfly
Wohooo our new design is now live at https://beaconcha.in/ thanks @stefan_star_twitter for your awesome work!