by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:55
    prylabs-bulldozer[bot] synchronize #6922
  • 20:55
    prylabs-bulldozer[bot] synchronize #6922
  • 20:55
    prylabs-bulldozer[bot] synchronize #6919
  • 20:55
    prylabs-bulldozer[bot] synchronize #6919
  • 20:55
    prylabs-bulldozer[bot] synchronize #6928
  • 20:55
    prylabs-bulldozer[bot] synchronize #6928
  • 20:55

    prylabs-bulldozer[bot] on invertStateLocksFlag

    Subscriber: use target epoch fo… Merge refs/heads/master into in… (compare)

  • 20:55

    prylabs-bulldozer[bot] on invertStateLocksFlag

    Subscriber: use target epoch fo… Merge refs/heads/master into in… (compare)

  • 20:55

    prylabs-bulldozer[bot] on aggregate-unaggregated

    Subscriber: use target epoch fo… Merge refs/heads/master into ag… (compare)

  • 20:55

    prylabs-bulldozer[bot] on aggregate-unaggregated

    Subscriber: use target epoch fo… Merge refs/heads/master into ag… (compare)

  • 20:55
    prylabs-bulldozer[bot] synchronize #6920
  • 20:55
    prylabs-bulldozer[bot] synchronize #6920
  • 20:55
    prylabs-bulldozer[bot] synchronize #6929
  • 20:55
    prylabs-bulldozer[bot] synchronize #6929
  • 20:55

    prylabs-bulldozer[bot] on peer-scorer-weighted-sorter

    Subscriber: use target epoch fo… Merge refs/heads/master into pe… (compare)

  • 20:55

    prylabs-bulldozer[bot] on peer-scorer-weighted-sorter

    Subscriber: use target epoch fo… Merge refs/heads/master into pe… (compare)

  • 20:55
    prylabs-bulldozer[bot] synchronize #6933
  • 20:55
    prylabs-bulldozer[bot] synchronize #6933
  • 20:55

    prylabs-bulldozer[bot] on change-log-level

    Subscriber: use target epoch fo… Merge refs/heads/master into ch… (compare)

  • 20:55

    prylabs-bulldozer[bot] on change-log-level

    Subscriber: use target epoch fo… Merge refs/heads/master into ch… (compare)

Raul Jordan
@rauljordan
[discord] <prestonvanloon> this is how I cross compile for windows with bazel
./bazel.sh build --config=release --config=windows_amd64_docker  //beacon-chain //validator //slasher
Raul Jordan
@rauljordan
[discord] <Bare> can someone walk me thru the set up tutorial?
[discord] <Bare> im confused
[discord] <Bare> ive dloaded beacon chain
[discord] <Bare> but cannot pass the password bit
[discord] <Bare> keeps saying Could not create validator at path: C:\Users\clayb\AppData\Local.eth2validator err=path "C:\Users\clayb\AppData\Local\.eth2validator" does not exist
1 reply
[discord] <Bare> what am i doing wrong?
1768012206
@1768012206
hello, i deploy my beacon node on a remote server and i want visit the port 3500 for interaction, however i get connection refused when type curl -X GET "serverip:3500/eth/v1alpha1/beacon/attestations?epoch=9871" -H "accept: application/json", could someone help...
Vins Ship
@VinsShip_twitter
Hello guys, is it possible to get 100 GoETH in order to start 3 validators?
Vins Ship
@VinsShip_twitter
It's fine I got it, thx
Lion - dapplion
@dapplion
I see in the repo work around Accounts-V2. Will this module replace the current workflow with ethdo? If so, is there an approximate timeline for its landing?
S Ξ Λ N
@wetdirtmud_twitter
Why am I getting these errors ?
Could not request attestation to sign at slot error=rpc error: code = DeadlineExceeded desc = context deadline exceeded Could not report validator's rewards/penalties error=rpc error: code = DeadlineExceeded desc = context deadline exceeded
Bigmotherfuckingrob2304
@Bigmotherfuckingrob2304
im having problems with eneteim
i am having problems entering my password
impact4him
@impact4him
hi I'm running Ubuntu & launched beacon node from docker. i', getting this msg: INFO roughtime: New calculated roughtime offset is -17744575 ns. has anyone else seen this msg?
swkim109
@swkim109

I'm just running Prysm for Medalla. I have keystore file from Medalla launchpad but I can't find right options for the keystore file in validator parameters. Here is the keystore files:

-rw-rw-r-- 1 ubuntu ubuntu  647 Jul 31 09:59 deposit_data-1596189588.json
-rw-rw-r-- 1 ubuntu ubuntu  710 Jul 31 09:59 keystore-m_12381_3600_0_0_0-1596189587.json

Just use --keystore-path?

GaryTopHat
@GaryTopHat
@swkim109 I tried the same thing and couldn't make it work. Here is what I did instead:
  1. Import your LaunchPad account using this command: prysm.sh validator accounts-v2 import --keys-dir=/validator-keys --wallet-dir=/validator-wallet --passwords-dir=/validator-wallet-passwords
keys-dir should contain your keystore json file. The two other folder are destination folder for the account import
@swkim109
  1. Then you start prysm referencing the wallet et password folders from the previous step:
    prysm.sh validator --config-file=/validator-config/config.yaml --wallet-dir=/validator-wallet --passwords-dir=/validator-wallet-passwords
@swkim109 You could omit specifying the wallet-dir and passwords-dir in both commands. It would prompt fyou for a value, but suggest default folders
Vins Ship
@VinsShip_twitter
Hello guys
I keep getting "error=no signing key found in keys cache" when trying to start a validator on Medalla
here is a stack trace
github.com/prysmaticlabs/prysm/validator/keymanager/v2/direct.(*Keymanager).Sign
        validator/keymanager/v2/direct/direct.go:268
github.com/prysmaticlabs/prysm/validator/client.(*validator).signObject
        validator/client/service.go:205
github.com/prysmaticlabs/prysm/validator/client.(*validator).signSlot
        validator/client/aggregate.go:114
github.com/prysmaticlabs/prysm/validator/client.(*validator).isAggregator
        validator/client/validator.go:520
github.com/prysmaticlabs/prysm/validator/client.(*validator).UpdateDuties
        validator/client/validator.go:382
github.com/prysmaticlabs/prysm/validator/client.run
        validator/client/runner.go:77
runtime.goexit
        GOROOT/src/runtime/asm_amd64.s:1373
Failed to sign slot
github.com/prysmaticlabs/prysm/validator/client.(*validator).signSlot
        validator/client/aggregate.go:116
github.com/prysmaticlabs/prysm/validator/client.(*validator).isAggregator
        validator/client/validator.go:520
github.com/prysmaticlabs/prysm/validator/client.(*validator).UpdateDuties
        validator/client/validator.go:382
github.com/prysmaticlabs/prysm/validator/client.run
        validator/client/runner.go:77
runtime.goexit
        GOROOT/src/runtime/asm_amd64.s:1373
could not check if a validator is an aggregator
github.com/prysmaticlabs/prysm/validator/client.(*validator).UpdateDuties
        validator/client/validator.go:384
github.com/prysmaticlabs/prysm/validator/client.run
        validator/client/runner.go:77
runtime.goexit
        GOROOT/src/runtime/asm_amd64.s:1373
is it a known issue?
looks like it fails when trying to check if it is an aggregator
swkim109
@swkim109
@GaryTopHat Thank you for the answer!
I have tried my own way before I saw your answer. I just recovered wallet by mnemonics from Medalla launchpad ./prysm.sh validator wallet-v2 recover and then typed some information of wallet dir, password and so on interactively. It generated $HOME/prysm/wallet/derived/keymanageropts.json so I set the validator parameter keymanageropts: $HOME/prysm/wallet/derived/keymanageropts.json.
Now, prysm says the following logs,
[2020-08-02 11:43:23]  INFO powchain: Processing deposits from Ethereum 1 chain deposits=15360 genesisValidators=14864
[2020-08-02 11:43:50]  INFO powchain: Processing deposits from Ethereum 1 chain deposits=15872 genesisValidators=15366
swkim109
@swkim109
[2020-08-02 22:43:40]  INFO powchain: Minimum number of validators reached for beacon-chain to start ChainStartTime=2020-08-04 13:00:08 +0000 UTC
swkim109
@swkim109
@GaryTopHat Your guide looks right. Thanks a lot!
swkim109
@swkim109
What is default RPC port? 4000?
Raul Jordan
@rauljordan
[discord] <rauljordan> yes thats right
[discord] <rauljordan> but thats for the gRPC server
[discord] <rauljordan> the default http gateway RPC port is
[discord] <rauljordan> 3500
swkim109
@swkim109
@rauljordan Thanks.
swkim109
@swkim109
[2020-08-04 04:31:01] INFO validator: Attestation schedule attesters=1 pubKeys=[0x89931ac13526] slot=13
What does it mean by slot=13? The validator will participate in attestation at 13th slot in every epoch? I remembered every epoch has 64 slots.
Raul Jordan
@rauljordan
[discord] <Nishant> it means your validator will participate in slot 13
[discord] <Nishant> not for every epoch
[discord] <Nishant> just the first one
Raul Jordan
@rauljordan
[discord] <scbuergel> cross-post from the #🐞-bug-report channel: it seems that all commands a running into GPG issues for me. can anyone help me out?
[discord] <scbuergel> $ ./prysm.sh beacon-chain Latest Prysm version is v1.0.0-alpha.18. Downloading beacon chain@v1.0.0-alpha.18 to /home/seb/prysm/dist/beacon-chain-v1.0.0-alpha.18-linux-amd64 (automatically selected latest available version) % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 42.5M 100 42.5M 0 0 2594k 0 0:00:16 0:00:16 --:--:-- 2838k Verifying binary integrity. gpg: no writable keyring found: Not found gpg: error reading '[stdin]': General error gpg: import from '[stdin]' failed: General error gpg: Total number processed: 0 seb@SebThink:~/prysm$
knight-star
@kaitoukidd
I got a error.
FATAL validator: Could not determine if beacon chain started: could not setup beacon chain ChainStart streaming client: rpc error: code = Unavailable desc = all .
The beacon is running.
Brano Vlasic
@brano_vlasic_twitter

Beaconchain error, can you help me narrow down the error?

Aug 07 00:32:27 cola systemd[1]: Started Beaconchain.
Aug 07 00:33:13 cola bash[716]: time="2020-08-06T22:33:13Z" level=error msg="Could not get rough time result: lookup caesium.tannerryan.ca: Temporary failure in name resolution" >
Aug 07 00:33:16 cola bash[716]: 2020/08/06 22:33:16 exit status 128
Aug 07 00:33:16 cola bash[716]: time="2020-08-06 22:33:16" level=info msg="Checking DB" database-path="/var/lib/prysm/beaconchain/beaconchaindata" prefix=node
Aug 07 00:33:19 cola bash[716]: 2020/08/06 22:33:19 exit status 128
Aug 07 00:33:19 cola bash[716]: 2020/08/06 22:33:19 exit status 128
Aug 07 00:33:19 cola bash[716]: time="2020-08-06 22:33:19" level=info msg="Starting beacon node" prefix=node version="Prysm/{STABLE_GIT_TAG}/{STABLE_GIT_COMMIT}. Built at: 2020-0>
Aug 07 00:33:19 cola bash[716]: time="2020-08-06 22:33:19" level=info msg="Waiting to reach the validator deposit threshold to start the beacon chain..." prefix=blockchain
Aug 07 00:33:19 cola bash[716]: time="2020-08-06 22:33:19" level=info msg="RPC-API listening on port" address="127.0.0.1:4000" prefix=rpc
Aug 07 00:33:19 cola bash[716]: time="2020-08-06 22:33:19" level=warning msg="You are using an insecure gRPC server. If you are running your beacon node and validator on the same>
Aug 07 00:33:19 cola bash[716]: time="2020-08-06 22:33:19" level=info msg="Starting JSON-HTTP API" address="127.0.0.1:3500" prefix=gateway
Aug 07 00:33:22 cola bash[716]: time="2020-08-06 22:33:22" level=info msg="New gRPC client connected to beacon node" addr="127.0.0.1:43994" prefix=rpc
Aug 07 01:33:25 cola bash[716]: time="2020-08-06 23:33:25" level=error msg="Could not get rough time result: lookup caesium.tannerryan.ca: Temporary failure in name resolution" p>
Aug 07 03:33:14 cola bash[716]: time="2020-08-07 01:33:14" level=error msg="Could not get rough time result: reading from socket: read udp 192.168.0.132:36535->172.105.97.188:200>

Vie
@VieYang
@brano_vlasic_twitter Could not get rough time result: lookup caesium.tannerryan.ca: Temporary failure in name resolution, maybe the problem of network .
Brano Vlasic
@brano_vlasic_twitter

@brano_vlasic_twitter Could not get rough time result: lookup caesium.tannerryan.ca: Temporary failure in name resolution, maybe the problem of network .

but system time sync works fine, how the beacon.chain service is trying to get the time out of non-working peer?

Vie
@VieYang
can you ping -c 10 caesium.tannerryan.ca?
Brano Vlasic
@brano_vlasic_twitter

can you ping -c 10 caesium.tannerryan.ca?

YES
ping -c 10 caesium.tannerryan.ca
--- time.0xt.ca ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9004ms
rtt min/avg/max/mdev = 164.935/168.867/175.363/3.847 ms

Vie
@VieYang
ok,
@brano_vlasic_twitter You can ask people in https://discord.gg/p3eyzG
Brano Vlasic
@brano_vlasic_twitter

@brano_vlasic_twitter You can ask people in https://discord.gg/p3eyzG

thanks!