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.

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

Leverage sharded origin keys #275

Closed
4 tasks done
ghost opened this issue Apr 7, 2022 · 1 comment
Closed
4 tasks done

Leverage sharded origin keys #275

ghost opened this issue Apr 7, 2022 · 1 comment
Assignees
Labels
breaking change Identify a change with a breaking API core team Assigned to the core team feature New feature request shared secrets Involve SharedSecrets

Comments

@ghost
Copy link

ghost commented Apr 7, 2022

Right now we are using an hardcoded origin shared key, but we should use this hardcoded key as an authorized public key key for the initial origin private keys.

So the initial origin shared private keys will be encrypted for the hardcoded software public key.

This requires:

  • create first origin shared secrets transaction during the network initialization
  • add the initial private keys encrypted for the hardcoded genesis software public key
  • add an origin shared chain by family
  • add test files

This will have an impact on libjs and wallet as #158 should be implemented to test it.

@ghost ghost added breaking change Identify a change with a breaking API feature New feature request shared secrets Involve SharedSecrets core team Assigned to the core team labels Apr 7, 2022
@apoorv-2204
Copy link
Contributor

Hey team! Please add your planning poker estimate with ZenHub @imnik11 @samuel-uniris @blackode

@Neylix Neylix self-assigned this Apr 22, 2022
Neylix added a commit to Neylix/archethic-node that referenced this issue Apr 26, 2022
Neylix added a commit to Neylix/archethic-node that referenced this issue Apr 26, 2022
ghost pushed a commit that referenced this issue May 3, 2022
@ghost ghost closed this as completed May 4, 2022
ghost pushed a commit that referenced this issue May 6, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Identify a change with a breaking API core team Assigned to the core team feature New feature request shared secrets Involve SharedSecrets
Projects
None yet
Development

No branches or pull requests

2 participants