Prysm v1.0 vs Prysm Pyrmont Question

i read on another post i should update dappmanager. I’ll tell you if it works.
http://my.dappnode/#/installer/dappmanager.dnp.dappnode.eth

EDIT: it worked. updating DappManager lets me see the featured package for prysm main net

If you are happy with your testing and are confident with Mainnet then the basic steps are

  1. Make sure you have installed the latest core DappNode packages
  2. Install GETH chain and wait for it to sync - upto two days
  3. Install Prysm Mainnet Package and wait for BeaconChain to sync. A couple of hours
  4. Create your keys and deposit your Eth
  5. Run the Prysm Onboarding Web UI and upload your keystore.json file ONLY. You don’t need the deposit.json file for the Web UI
  6. Set complex password for Wallet
  7. Check out the DMS dashboards to see if you are reporting stats
  8. That should be it

Basically have installed the Mainnet Prysm package and Beacon Chain synch’d.

The package has been updated on the DappStore now.

Just the keystore.JSON file is needed.
The process on Mainnet is exactly the same as Pyrmont

1 Like

Thanks a lot @AJR for all the explanations :smiley: :pray: , I have just question on this one, where/how I can check that those are synced?
I cannot open Prysm before importing my keystore.

How long do you recommend testing on the testnet for?

Here…

Where I have circled there is a drop down for the Validator logs

1 Like

Have you completed all your tests? What have you tested for?

I was just testing mainly my hardware and understanding the steps to get everything up and running pretty much. I only running the hardware for a couple days nothing much else than that.

Thanks @AJR, I checked it, but, I was getting this warning :sweat: , I reinstaled Prysm, but warning left.
Should I ignore it or not, and do you have any further suggestions for me what to do? :neutral_face:

And what should I expect to be written in log if the synchronization is successful?

Thanks

Have you tested things such as what happens in a power outage or you need to reboot your router? Does everything fire up okay, etc.

That just means you haven’t completed the onboarding through the Prysm Web UI. Once you complete that the error will disappear and you should see this. Well I hope this is what you should see.

1 Like

Thanks a lot bro! :pray:
I’ll let you know when I finish onboarding. :slightly_smiling_face:

No worries and good luck! :slightly_smiling_face:

1 Like

In case some here has not yet noticed, we have published a self-staking guide for yoooour reference :partying_face:

2 Likes

@ruvenni @AJR

Guide is fantastic :slight_smile:

Now, with depositing, everything went fine, ETHs are “deposited” now after almost 20 hours and still waiting to be in “pending”.

I even managed to connect Grafana, but in Grafana, I’ve got warning that I have been slashed :open_mouth:
Was that a false trigger, or not?
I haven’t done absolutely anything after depositing.

Everything looks fine when I check validators, and they still in “Deposited” phase. And no balance is under 32ETH when I look at blockexplorer, as te warning say…I think at least…

How this looks like to you, and do you have any suggestions what to do or check next…

Yikes that is the first slashing i have seen in real life. Have you configured your network time clock correctly?

i guess everything is on defult settings.
Where I am confused, is this just a false trigger from grafana, or not, and can check somehow on chain scanner to confirm slashing.
Also it is strange to me how slashing can happened before the validator is activated. All my validators are in “Deposited” state. Architecture of validating algorithm shouldn’t be different? As I understood, slashing and exiting should work after activation.

And, in worst case scenario, if this is really the real slashing, and not just some grafana trigger, what do I need to do to find out the cause and prevent it in the future, and how to know which of my validators is slashed, and can it continue entering to the network after then, because if it slashed, it has lower than 32 ETH?

@mihailo, is this slashing warning only happening to you with Pyrmont, right?

No, it happend on Prysm. :expressionless:
It sais on graffana.

Prysm is a just a client validator. There’s two versions currently available in our DAppStore, one for testing-validating on Pyrmont (a test-net) and one for the real deal of validating on ETH2.0 a.k.a Mainnet.

I’m sure there has been a misunderstanding and your question is about Pyrmont.

PS. Mainnet is currently being launched as I’m writing this post.

No dear @ruvenni , I deinstalled testnet Pyrmont.

I installed Mainnet Prysm, deposited, via Mainnet Launchpad, and imported keystores to Prysm. (mainnet).
Few hours after deposting and importing grafana wrote that error.

Validator itself recognize the keys, write that eths are deposited, and that it is awaiting genesis.

Is it technically possible to be slashed before network launching?