Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create one one operator account for each orderer and a shared submit key. #3

Open
donaldthibeau opened this issue Feb 18, 2020 · 3 comments
Open

Create one one operator account for each orderer and a shared submit key. #3

donaldthibeau opened this issue Feb 18, 2020 · 3 comments
Assignees
@xin-hedera

Comments

@donaldthibeau
Copy link

No description provided.

@donaldthibeau
Copy link
Author

donaldthibeau commented Feb 18, 2020 •
edited
Loading

Every orderer would sign with a unique operator key, and one submit key per topic.

@donaldthibeau donaldthibeau changed the title Create one account for each orderer Create one submit account for each orderer Feb 18, 2020
@donaldthibeau donaldthibeau changed the title Create one submit account for each orderer Create one one operatr account for each orderer and a shared submit key. Feb 18, 2020
@donaldthibeau donaldthibeau changed the title Create one one operatr account for each orderer and a shared submit key. Create one one operator account for each orderer and a shared submit key. Feb 18, 2020
@mike-burrage-hedera
Copy link

Having a distinct operator per-orderer means that each orderer maintains their own hbar cryptoaccount used to pay for transactions to the topic.
There may be a desire later on for either the submitKey and/or adminKey to be keylist/threshold keys, but having distinct operator/payer key is a good first step.

@xin-hedera
Copy link
Collaborator

No code change is needed, verified with the first-network sample configured to have distinct operator for different orderer instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xin-hedera xin-hedera

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@donaldthibeau @mike-burrage-hedera @xin-hedera