XDAG needs mnemonic for password, backup and restore.
Specification
To be continue
Rationale
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
To be continue
Backwards Compatibility
All XIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The XIP must explain how the author proposes to deal with these incompatibilities. XIP submissions without a sufficient backwards compatibility treatise may be rejected outright.
To be continue
Test Cases
N/A
Implementation
The implementations must be completed before any XIP is given status "Final", but it need not be completed before the XIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.
To be continue
Copyright
Copyright and related rights are discribed in MIT license.
Simple Summary
Describe the mnemonic for XDAG wallets.
Abstract
Describe the mnemonic for XDAG wallets.
Motivation
XDAG needs mnemonic for password, backup and restore.
Specification
To be continue
Rationale
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
To be continue
Backwards Compatibility
All XIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The XIP must explain how the author proposes to deal with these incompatibilities. XIP submissions without a sufficient backwards compatibility treatise may be rejected outright.
To be continue
Test Cases
N/A
Implementation
The implementations must be completed before any XIP is given status "Final", but it need not be completed before the XIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.
To be continue
Copyright
Copyright and related rights are discribed in MIT license.