-
Notifications
You must be signed in to change notification settings - Fork 1k
Add NEO2-style contract metadata to NEO3 ContractManifest #1143
Copy link
Copy link
Closed
Labels
EnhancementType - Changes that may affect performance, usability or add new features to existing modules.Type - Changes that may affect performance, usability or add new features to existing modules.LedgerModule - The ledger is our 'database', this is used to tag changes about how we store informationModule - The ledger is our 'database', this is used to tag changes about how we store informationReady-to-ImplementIssue state: Ready to be implemented or implementation in progressIssue state: Ready to be implemented or implementation in progress
Metadata
Metadata
Assignees
Labels
EnhancementType - Changes that may affect performance, usability or add new features to existing modules.Type - Changes that may affect performance, usability or add new features to existing modules.LedgerModule - The ledger is our 'database', this is used to tag changes about how we store informationModule - The ledger is our 'database', this is used to tag changes about how we store informationReady-to-ImplementIssue state: Ready to be implemented or implementation in progressIssue state: Ready to be implemented or implementation in progress
Summary
In NEO2 all contracts had the following (optional) fields as part of
ContractState:NEO3 has removed most fields of
ContractStateand added the more comprehensiveContractManifestobject. However, the manifest does not seem to contain or store any of the above fields.Do you have any solution you want to propose?
Add Name, CodeVersion, Author, Email and Description to the
ContractManifestclass so that explorers/dApp trackers can obtain human-readable context for the contracts deployed on NEO3.Where in the software does this update applies to?