NEP: NeoContract Manifest

[bettybao1209]

close #110

[vncoelho]

Such a fine piece of art! Well written and described.
Thanks for the consideration and inclusion as author,

[shargon]

Thanks for my inclusion @bettybao1209 ! I think that the document describe well the manifest format. Good work!

[igormcoelho]

I'm honored for the inclusion, thanks!

[erikzhang]

Merge?

[erikzhang]

It should be merged after #119.

[shargon]

How will now the user that NEP3 and NEP6 it's obsolete? we should add a line for redirect to the new one

[luc10921]

#2060 removed features and #2024 added name, but NEP-15 did not change it Specification to address those changes. Also, #2044 removed hash from ABI.

[gsmachado]

I was discussing With devhawk in this issue the need of specifying the file name suffix .manifest.json as a standard, to our community.

What I observe is that compilers give the option to developers to specify any kind of file name they want (which is not bad!), but then, at least the default output filename name should be set with a standardized suffix (i.e., .manifest.json).

This gains even more importance to developer experience if we consider that key tools in our community, like https://github.com/ngdenterprise/neo3-visual-tracker, relies on discovering contracts to be deployed based on the manifest filename.

I suggest adding, somewhere in this NEP:

The default filename suffix that compilers and tools should output is .manifest.json.

or something in this direction.

[erikzhang]

Does anyone have any comments or suggestions? @neo-project/everyone