truebit-eth
truebit-eth copied to clipboard
TruebitProtocol
Ethereum POS update
Hello,
Is there going to be any update for Ethereum POS ? TruebitOS is not working right now on mainnet.
Hello guys, any update on this? Seriously disappointed in the wait time for a reply.
Same here!
On Wed, May 31, 2023 at 4:04 AM SoftlinerGmbH @.***> wrote:
Hello guys, any update on this? Seriously disappointed in the wait time for a reply.
— Reply to this email directly, view it on GitHub https://github.com/TruebitProtocol/truebit-eth/issues/24#issuecomment-1569693755, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACRVAMJYS7V6R6TSLGELUA3XI33RFANCNFSM6AAAAAAQYUZ2YA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Despite following all the instructions at https://docs.truebit.io/v1docs, I was unable to get it running. I seem to be having problems with the hardhat part and subsequently with syncing on the mainnet. The geth part keeps looking for peers, and I receive the following warning: "WARN [06-24|00:09:57.896] Post-merge network, but no beacon client seen. Please launch one to follow the chain!" Prysm keeps trying to sync and doesn't seem to be finishing anytime soon.
To understand the problem, let's discart the use of an old version by removing the Truebit docker image,try: docker image rm truebitprotocol/truebit-eth
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Despite following all the instructions at https://docs.truebit.io/v1docs, I was unable to get it running. I seem to be having problems with the hardhat part and subsequently with syncing on the mainnet. The geth part keeps looking for peers, and I receive the following warning: "WARN [06-24|00:09:57.896] Post-merge network, but no beacon client seen. Please launch one to follow the chain!" Prysm keeps trying to sync and doesn't seem to be finishing anytime soon.
To understand the problem, let's discart the use of an old version by removing the Truebit docker image,try: docker image rm truebitprotocol/truebit-eth
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Despite following all the instructions at https://docs.truebit.io/v1docs, I was unable to get it running. I seem to be having problems with the hardhat part and subsequently with syncing on the mainnet. The geth part keeps looking for peers, and I receive the following warning: "WARN [06-24|00:09:57.896] Post-merge network, but no beacon client seen. Please launch one to follow the chain!" Prysm keeps trying to sync and doesn't seem to be finishing anytime soon.
Is there any docs to follow up to install from scratch?
To understand the problem, let's discart the use of an old version by removing the Truebit docker image,try: docker image rm truebitprotocol/truebit-eth
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Despite following all the instructions at https://docs.truebit.io/v1docs, I was unable to get it running. I seem to be having problems with the hardhat part and subsequently with syncing on the mainnet. The geth part keeps looking for peers, and I receive the following warning: "WARN [06-24|00:09:57.896] Post-merge network, but no beacon client seen. Please launch one to follow the chain!" Prysm keeps trying to sync and doesn't seem to be finishing anytime soon.
Is there any docs to follow up to install from scratch?
Your issue is due to the consensus client not being fully synced yet.
According to the Geth documentation (https://geth.ethereum.org/docs/getting-started/consensus-clients): Syncing Geth cannot sync until the connected consensus client is synced. This is because Geth needs a target head to sync to.
Since the you encountered the same problem using Hardhat, which is unusual and inconsistent with our QA results using Hardhat, we recommended updating their Docker image.
To understand the problem, let's discart the use of an old version by removing the Truebit docker image,try: docker image rm truebitprotocol/truebit-eth
Sorry for the delay, but the POS update has already been pushed live. Any particular issues you need help with?
Despite following all the instructions at https://docs.truebit.io/v1docs, I was unable to get it running. I seem to be having problems with the hardhat part and subsequently with syncing on the mainnet. The geth part keeps looking for peers, and I receive the following warning: "WARN [06-24|00:09:57.896] Post-merge network, but no beacon client seen. Please launch one to follow the chain!" Prysm keeps trying to sync and doesn't seem to be finishing anytime soon.
Is there any docs to follow up to install from scratch?
Your issue is due to the consensus client not being fully synced yet.
According to the Geth documentation (https://geth.ethereum.org/docs/getting-started/consensus-clients): Syncing Geth cannot sync until the connected consensus client is synced. This is because Geth needs a target head to sync to.
Since the you encountered the same problem using Hardhat, which is unusual and inconsistent with our QA results using Hardhat, we recommended updating their Docker image.
I'm using truebit docker so both geth and Prysm are inside truebit docker image. There is no separate docker images. One thing I want to make sure, should I install and run hardhat on my local computer not inside truebit docker container right ?