Open Bill-Kunj opened 3 years ago
Proposal: put the private keys for the publisher, attestor, and buyer into genesis. Then our snapshot will already include the necessary balances
From what I know, this is the way it works right now.
Genesis will give REV to the validator, but 'publisher', 'attestor', and 'buyer' will not have rev. A demo requiring an initial transfer of REV to publisher, attestor, and buyer will not be as smooth as a demo in which these users already have rev.
I am trying to understand what this means
Genesis needs the private keys and initial balances. We need the keys first and then update the genesis to include them.
Genesis will give REV to the validator, but 'publisher', 'attestor', and 'buyer' will not have rev. A demo requiring an initial transfer of REV to publisher, attestor, and buyer will not be as smooth as a demo in which these users already have rev.
I am trying to understand what this means
It's an argument that the demo should not include a transfer of REV from the validator to the attestor/publisher/buyer as a part of official demos.
Genesis needs the private keys and initial balances. We need the keys first and then update the genesis to include them.
As I said, the keys are already inside genesis.
So, as I said earlier, I suggest we use the same rnode snapshot so we can all can all work with the same registry URI, what do you think?
So, as I said earlier, I suggest we use the same rnode snapshot so we can all can all work with the same registry URI, what do you think?
This is a great idea. Remember that the snapshot needs to be available to everyone, including the demo systems. Where shall we keep it?
Also, as I update and test the rholang, the URI will change. Which means we'll need to update the snapshot from time-to-time.
sorry about the closing, it was a mistake
I think https://docs.github.com/en/github/managing-large-files/versioning-large-files will work for snapshot storage.
@TheoXD @David405 This remains a technical issue we need to figure out. Once we release, upgrades are inevitable and the URI will be updated.
Genesis will give REV to the validator, but 'publisher', 'attestor', and 'buyer' will not have rev. A demo requiring an initial transfer of REV to publisher, attestor, and buyer will not be as smooth as a demo in which these users already have rev. Proposal: put the private keys for the publisher, attestor, and buyer into genesis. Then our snapshot will already include the necessary balances