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

teerex refactor 3 #193

Closed
wants to merge 26 commits into from
Closed

teerex refactor 3 #193

wants to merge 26 commits into from

Conversation

brenzi
Copy link
Contributor

@brenzi brenzi commented Jul 8, 2023

closes #188

  • introduce ProxiedEnclaves storage
  • allow proxied enclaves to be registered (for use by attesteer)
  • ..and unregistered when timestamp outdated

TODO:

@brenzi brenzi requested a review from clangenb July 8, 2023 15:40
@brenzi brenzi marked this pull request as ready for review July 8, 2023 15:40

impl From<[u8; 32]> for AnySigner {
fn from(pubkey: [u8; 32]) -> Self {
// zero padding is necessary because the chain storage does that anyway for bounded vec
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this concerns me. if we don't zero-pad, the tests fail. but why are BoundedVecs bloated by the onchain state backend?

@brenzi brenzi changed the base branch from ab/teerex-refactor-186-2 to master July 10, 2023 09:53
@brenzi brenzi closed this Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[teerex] introduce separate storage for proxied enclaves
1 participant