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

Generalize metadata schemas for wawaka common contracts #351

Open
marcelamelara opened this issue Jan 26, 2022 · 3 comments
Open

Generalize metadata schemas for wawaka common contracts #351

marcelamelara opened this issue Jan 26, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request wawaka Issues related to contract development with wawaka

Comments

@marcelamelara
Copy link
Member

marcelamelara commented Jan 26, 2022

Currently, the contract code metadata focuses on validating the code hash on the ledger. However, it would be useful to include more general metadata about contracts such as contract type (wasm vs native), or CDI-type metadata.

This issue may also be related to #294 .

@marcelamelara marcelamelara added the enhancement New feature or request label Jan 26, 2022
@marcelamelara marcelamelara self-assigned this Jan 26, 2022
@cmickeyb cmickeyb changed the title Generalize contract code metadata schema Generalize metadata schemas for wawaka common contracts Jan 27, 2022
@cmickeyb
Copy link
Contributor

Contract metadata schema is currently defined as:
{ "verifying_key" : "", "encryption_key" : "" }

Contract code metadata schema is currently defined as:
{ "code_nonce" : "" }

These reflect the information that is necessary to verify attestations generated by the ledger as to the identity of a contract object (and to bind an encryption key to that object).

@cmickeyb cmickeyb added the wawaka Issues related to contract development with wawaka label Mar 30, 2023
@cmickeyb
Copy link
Contributor

@marcelamelara do you have a more specific request? i would expect any application/contract that wants to use the additional data to extend this function. It would be rather constraining to force all applications to use the additional metadata.

@cmickeyb
Copy link
Contributor

And I think this issue is completely independent of #294. One occurs in the enclave and is part of the fundamental trust relationship between the contract, the ledger and the user. This code is about establishing run-time trust between two separate contracts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wawaka Issues related to contract development with wawaka
Projects
None yet
Development

No branches or pull requests

2 participants