Summary or problem description
Currently the platform exposes and optional name field on contract deployment. This field is CRITICAL for end-user platforms which have a human readable component (like explorers, exchanges, and wallets). We cannot expect users to decipher script hashes when using the ecosystem tooling and this small change has a very minimal workflow impact for a substantial improvement to the tooling experience.
Do you have any solution you want to propose?
Enforce required metadata for smart contracts
Neo Version
Where in the software does this update applies to?
- Compiler
- CLI
- Network Policy
- VM
Summary or problem description
Currently the platform exposes and optional name field on contract deployment. This field is CRITICAL for end-user platforms which have a human readable component (like explorers, exchanges, and wallets). We cannot expect users to decipher script hashes when using the ecosystem tooling and this small change has a very minimal workflow impact for a substantial improvement to the tooling experience.
Do you have any solution you want to propose?
Enforce required metadata for smart contracts
Neo Version
Where in the software does this update applies to?