Shargon
Shargon
https://github.com/neo-project/neo/pull/3531 and https://github.com/neo-project/neo/pull/3532 (but already closed)
> The problem is that some of existing contracts expose update(nef, manifest) method with two arguments only and call native Management's update with two arguments. Yes, a lot of devs...
I think it's almost impossible to get 0x0 as an address, so it should be treated as null, indeed.
Yes, we should follow NEP-25 also in native contracts
We can store the struct instead just the value
I will do it today or tomorrow > This is good to be done before 3.9.0
Please @neo-project/core take a look to this PR, we should decide the right values for PoW and frequency. Maybe we should move this values to policy: Difficult and frequency
> Could you give a detailed description for this feature ? https://github.com/neo-project/proposals/pull/211
> @shargon , how about information for current state of MPT? The problem I see is that almost all the information can be easily accessed via RPC. That's the reason...
Could you show the content of start_node.sh?