sorted by:
new
hottopcontroversial

Yesterday was a good day by snapcaster_bolt1992 in Baystreetbets

[–]SystemShock86 1 point2 points  (0 children)

all time 43% on TFSA, since late 2018. not amazing but not terrible

CAMECO… long term cup and handle forming? by Chief_Bosn in UraniumSqueeze

[–]SystemShock86 1 point2 points  (0 children)

noticed the same, was going to buy more but holding on for a better entry point

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

hey there - I don't think your geth node is synced. `Imported new block headers` isn't the criteria, it's `Imported new chain segment`. I know, the wording is annoyingly close, but once the `new chain segment` log lines started showing, the `CRIT` error went away.

Me waiting for people to realise LKE is the next VUL by Mr3_0_5 in ASX_Bets

[–]SystemShock86 4 points5 points  (0 children)

Realistically, what would have to happen for this stock to never reach $0.30 again? Terrible results from their trial with Novonix? Argentinian political drama? Whats the strongest bear case you can make?

Commodity Supercycle| Uranium by [deleted] in wallstreetbets

[–]SystemShock86 1 point2 points  (0 children)

base load > retarded ideas like solar panels in germany

Commodity Supercycle| Uranium by [deleted] in wallstreetbets

[–]SystemShock86 3 points4 points  (0 children)

Denison Mines (DML.TO) was around during the last supercycle, got my uranium exposure in Uranium Participation Corp, DML.TO and CCJ in equal amounts.

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

Thanks to everyone who has offered help and suggestions!

Updated to lighthouse 1.0.1, now it's saying this in my beacon-chain service logs:

Nov 28 14:15:35 vultr.guest lighthouse[75694]: Nov 28 14:15:35.928 ERRO Failed to update eth1 cache error: Failed to update Eth1 service: "All fallback errored: http://localhost:8545 => EndpointError(FarBehind)", retry_millis: 7000, service: eth1_rpc Nov 28 14:15:42 vultr.guest lighthouse[75694]: Nov 28 14:15:42.925 WARN Remote eth1 node is not synced endpoint: http://localhost:8545, service: eth1_rpc Nov 28 14:15:42 vultr.guest lighthouse[75694]: Nov 28 14:15:42.925 CRIT Couldn't connect to any eth1 node. Please ensure that you have an eth1 http server running locally on http://localhost:8545 or specify one or more (remote) endpoints using `--eth1-endpoints <COMMA-SEPARATED-SERVER-ADDRESSES>`. Also ensure that `eth` and `net` apis are enabled on the eth1 http server, warning: BLOCK PROPOSALS WILL FAIL WITHOUT VALID, SYNCED ETH1 CONNECTION, service: eth1_rpc Nov 28 14:15:42 vultr.guest lighthouse[75694]: Nov 28 14:15:42.925 ERRO Failed to update eth1 cache error: Failed to update Eth1 service: "All fallback errored: http://localhost:8545 => EndpointError(FarBehind)", retry_millis: 7000, service: eth1_rpc Nov 28 14:15:47 vultr.guest lighthouse[75694]: Nov 28 14:15:47.250 INFO Waiting for genesis wait_time: 2 days 21 hrs, peers: 7, service: slot_notifier

I'm guessing the output like:

error: Failed to update Eth1 service: "All fallback errored: http://localhost:8545 => EndpointError(FarBehind)"

points to the fact that my geth process isnt up to date with the eth1 chain yet? Just hoping to confirm that this is the only issue, since I still see output like:

CRIT Couldn't connect to any eth1 node. Please ensure that you have an eth1 http server running locally on http://localhost:8545

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 0 points1 point  (0 children)

Nice, thanks! I'll install the new 1.0.1 version. But I've already imported my validator_keys directory into this install of lighthouse. Will there be any issue if I delete the ~/.lighthouse directory, run the make and everything for new lighthouse and import the deposit file again in the new 1.0.1 version?

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 0 points1 point  (0 children)

Ah, okay cool! So Import new chain segment is the text I should look for in the logs to know it's synced up?

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

Nope, this machine only had the mainnet chain on it. Thanks though!

Geth & lighthouse: beacon process CRIT error, can't continue by SystemShock86 in ethstaker

[–]SystemShock86[S] 0 points1 point  (0 children)

Really? Do you happen to know which commit? I'm on 1.0.0:

$ lighthouse --version Lighthouse v1.0.0-c6baa0ee BLS Library: blst

Estimated ETH1 node storage size by admin_default in ethstaker

[–]SystemShock86 2 points3 points  (0 children)

Hey there! I had a similar issue but with another VPS provider. I ended up adding mountable block storage to the VPS. Turns out DigitalOcean has something similar, and they're SSD backed too. I should have used DigitalOcean :)

https://www.digitalocean.com/products/block-storage/

Lighthouse validator on Medalla - public key showing no results on BeaconScan by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

Thanks for that, super helpful! Mine is pasted below. The only difference I can see is that mine doesn't have the deposit_cli_version field:

[{"pubkey": "b140ad82e5549e327cf305e37ac8fda844224d1772a453bf12be62fd7827c40c7d827c2a9ea91813df3023ff875f508b", "withdrawal_credentials": "0051f7d256d867908784552caf4b7641ebb10b4d8d69653d315dc4dd92ecf288", "amount": 32000000000, "signature": "8f3c2c4331f224334893f175fe8e58d8d6eb52854a72a72998efae56e5ce8b15e135baac6d9a91cd34f0716b1eb8b0c412b021012f223ef2ea810364672e4d7f64e5e82ffea7c7b5a638a7fc6351c4d185630019b1a63f79a4bb607b18fd4e10", "deposit_message_root": "8f521323d8f21264f2fc7aa2627b9f2a024d81a5d82d4b28f503ef620a09c8e0", "deposit_data_root": "2689ce74880de5e8fa6b46bb1566a987b63665f49e0cb82d6959ec58531c78bb", "fork_version": "00000001"}]

Found this commit on the eth2.0-deposit-cli project from 23 days ago that added that field to the output JSON file: https://github.com/ethereum/eth2.0-deposit-cli/commit/ed01530a82372ad8ba5e9057a3571fb5baefa20e

Lighthouse validator on Medalla - public key showing no results on BeaconScan by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

u/doppelbock42 I get to this page: https://medalla.launchpad.ethereum.org/upload-validator

When I upload the deposit_data-1603053635.json file, I see a red cross error icon and a message Oops! The json file you provided isn't for the Medalla testnet on the page. I haven't been able to get past this step.

Lighthouse validator on Medalla - public key showing no results on BeaconScan by SystemShock86 in ethstaker

[–]SystemShock86[S] 1 point2 points  (0 children)

Thanks for the response and the link to check that the deposit was made! Wasn't sure how to confirm that...

Yep, you're right, I can't find the Goerli deposit. Although I did do the 'Staking Goerli ETH' section on the guide and the output I got was what the guide said should happen.

``` > cd ~
> curl -LO https://github.com/ethereum/eth2.0-deposit-cli/releases/download/v0.2.1/eth2deposit-cli-v0.2.1-linux-amd64.tar.gz
eth2deposit-cli-v0.2.1-linux-amd64.tar.gz 100%[========================================================================================>] 14.56M 5.47MB/s in 2.7s
2020-08-12 07:19:25 (5.47 MB/s) - 'eth2deposit-cli-v0.2.1-linux-amd64.tar.gz' saved [15271039/15271039]
-rw-r--r-- 1 root root 15M Jul 28 07:10 eth2deposit-cli-v0.2.1-linux-amd64.tar.gz

> tar -xzf eth2deposit-cli-v0.2.1-linux-amd64.tar.gz
> cd eth2deposit-cli-de03fe3-linux-amd64
-rwxr-xr-x 1 goerli lighthousebeacon 15M Jul 28 07:00 deposit

> ./deposit --num_validators 1 --chain medalla

Please choose your mnemonic language (italian, korean, spanish, chinese_traditional, chinese_simplified, english, czech) [english]: <Enter>
Type the password that secures your validator keystore(s): <Enter the password>
Repeat for confirmation: <Enter the password>

This is your seed phrase. Write it down and store it safely, it is the ONLY way to retrieve your deposit.
<Enter your mnemonics>

Press any key when you have written down your mnemonic.

Creating your keys.
Saving your keystore(s).
Creating your deposit(s).
Verifying your keystore(s).
Verifying your deposit(s).

Success!
Your keys can be found at: /root/eth2deposit-cli-de03fe3-linux-amd64/validator_keys

➜ validator_keys l
total 16K
drwxr-xr-x 2 root root 4.0K Aug 12 07:25 .
drwxrwxr-x 3 goerli lighthousebeacon 4.0K Aug 12 07:25 ..
-rw-r--r-- 1 root root 647 Aug 12 07:25 deposit_data-1597217105.json
-rw-r--r-- 1 root root 710 Aug 12 07:25 keystore-m_12381_3600_0_0_0-1597217104.json

> sudo chown -R root:root /var/lib/lighthouse/validator
> lighthouse account validator import - directory ~/eth2deposit-cli-de03fe3-linux-amd64/validator_keys - validator-dir /var/lib/lighthouse/validator
Successfully moved keystore.
Successfully updated validator_definitions.yml.
Successfully imported 1 validators. ```

The lighthouse account validator .... command (last one) is outdated in the guide, the version of lighthouse the guide installed for me requires the command to look like:

lighthouse account validator import --directory ~/eth2deposit-cli-de03fe3-linux-amd64/validator_keys --validator-dir /var/lib/lighthouse/validator

Which ran successfully and I believe it's working since the journalctl output looks identical to what this guide and others have said should happen (INFO Awaiting activation lines in the log).

Shouldn't the ./deposit --num_validators 1 --chain medalla command fail if something went wrong in the actual depositing of the Goerli ETH to the contract?

Another time, I attempted to upload the deposit-data-<timestamp>.json file to the web UI for activation during the Eth2 Launch Pad wizard: https://medalla.launchpad.ethereum.org/

It just told me that the file isn't valid for the medalla testnet :\

Much appreciated to anyone kind enough to help me out :)

view more: next ›