Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 18 07:56

    qu0b on staging

    Feature/rewards dashboard (#818… (compare)

  • May 18 07:55

    qu0b on master

    add 5 decimals for ETH (#819) (compare)

  • May 17 13:30

    guybrush on master

    api: add /api/healthz-loadbalan… (compare)

  • May 17 12:33

    qu0b on master

    using format income (#816) * u… (compare)

  • May 17 11:01

    qu0b on master

    change type to int64 (#815) (compare)

  • May 17 10:34

    qu0b on master

    add commas (#814) * add commas… (compare)

  • May 14 11:19

    qu0b on staging

    Feature/rewards UI update (#813… (compare)

  • May 12 11:20

    guybrush on master

    validator page: fix daily incom… (compare)

  • May 11 11:09

    qu0b on staging

    Feature/improve rewards securit… (compare)

  • May 10 13:04

    qu0b on staging

    update UI elements (#809) (compare)

  • May 10 11:30

    guybrush on master

    db: add index idx_blocks_epoch … (compare)

  • May 07 15:18

    qu0b on staging

    Cookie banner positioning (compare)

  • May 07 15:08

    qu0b on staging

    preload fonts (compare)

  • May 07 11:18

    qu0b on staging

    Fix/rewards css (#806) * updat… (compare)

  • May 07 07:12

    guybrush on staging

    update notifications.go for tes… (compare)

  • May 06 12:45

    qu0b on staging

    Feature/validator rewards (#804… (compare)

  • May 06 10:10

    qu0b on master

    staging (#803) * update/bundle… (compare)

  • May 06 10:03

    qu0b on staging

    Update build.yml (compare)

  • May 06 09:55

    qu0b on staging

    Actions: Generate docs on build (compare)

  • May 06 09:25

    qu0b on staging

    Actions: Generate docs on build (compare)

mkinney
@mkinney
the prysm tests do not allow http
--http-web3provider 'ws://localhost:8546'
gets closer... but not working
time="2019-12-19 19:15:16" level=error msg="Could not connect to powchain endpoint" error="could not dial eth1 nodes: dial tcp 127.0.0.1:8546: connect: connection refused" prefix=powchain
Peter (bitfly)
@peterbitfly
I guess it will need a eth1 node for the desposits
mkinney
@mkinney
I tried using docker run -it -p 8545:8545 0xorg/ganache-cli:latest
which gives a local testnet for eth1
<shrug>
mkinney
@mkinney
Can you use an external "indexer"?
in config.yml file
indexer:
enabled: true
node:
host: "beaconcha.in"
port: "4000"
type: "prysm"
(something like that?)
Peter (bitfly)
@peterbitfly
You mean to run the indexer independent of the frontend? Yes that’s possible
mkinney
@mkinney
does beaconcha.in have a lighthouse and/or prysm (or anyone else) have external ones avail?
Peter (bitfly)
@peterbitfly
Ah you mean a Remote node
mkinney
@mkinney
ya
Peter (bitfly)
@peterbitfly
It is possible but not very fast
We don’t have a public instance, maybe the Prysm guys are running one
The indexer talks to the node via http
mkinney
@mkinney
Ok. I was able to get the sync working...
Used docker-compose to spin up a postgres container (not persisting data), a prysm container (persisting data), and an eth2 beacon chain explorer instance... all so you can run docker-compose up and hit http://localhost:3333
mkinney
@mkinney
If I could figure out how to start either chain, I could start to do some integration-y tests.
(start either chain locally without using the testnets)
I want to do that so it would start quickly (no large wait for syncs) and it should be somewhat consistent with data.
mkinney
@mkinney
Lighthouse said to run: date +%s then lighthouse bn --http testnet -r quick 8 1576813592 (where 1576813592 was the output for the date command)
Seems to work...
Peter (bitfly)
@peterbitfly
Thanks for your efforts, for integration testing it would be good to have a somewhat predictable node state
mkinney
@mkinney
:-)
Peter (bitfly)
@peterbitfly
It could make sense to just use a pre filled node data directory as basis
mkinney
@mkinney
possible... but... kinda yucky too...
Peter (bitfly)
@peterbitfly
Like start a local testnet and generate 2-3 epochs
Then use that data directory
mkinney
@mkinney
Paul on lighthouse discord just shared this...

we have a simulator that you can spin up with a single command that has 4x nodes, 4x validator clients and eth1 chain
it lives in here:

https://github.com/sigp/lighthouse/tree/master/tests/beacon_chain_sim
GitHub
sigp/lighthouse
Rust Ethereum 2.0 Client. Contribute to sigp/lighthouse development by creating an account on GitHub.

its setup to end after it finishes running checks, but if you flip this bool it'll stay up:

https://github.com/sigp/lighthouse/blob/74b327b50d1b67782ae4b030297e0f6ea4b19d88/tests/beacon_chain_sim/src/main.rs#L45

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