@kunxian-xia @AlverLyu @mooorex @Honglei-Cong this should be ready to go

@javajoker this one too - any other comments?

Thanks for your proposal.
We are working to draft a new standard version since current implementation is not that proper.

Yes, it is a de facto implementation, but some items will make people confuse in this specification, such as the Control object includes an unexpected item "address". Besides, we have own encrypted key format rather than NEP-2 format.
it is not very flexible, such as it supports only one type of KDF. Is it necessary to support more cryptographic algorithms, especially different KDFs in this standard?
So, in a nutshell, is it more suitable to define a new version?

@AlverLyu @mooorex gotcha, makes sense. Would be happy to help contribute to the new standards.

As discussed, close this PR and starting a new one when new wallet standard draft available?

@Honglei-Cong We should put the conversation on the new standard here. The conversation should be open to the public - so this can act as a starting point