Shulou(Shulou.com)06/01 Report--

The main content of this article is to explain "what is the standard of NEP6 wallet". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Now let the editor take you to learn "what is the standard of NEP6 wallet"?

NEP:NEO Enhancement Proposals, the NEO improvement proposal, describes the standards of the NEO platform, including core protocol specifications, client-side API and contract standards. The most familiar is the NEP-5 token standard.

At present, the NEP-6 wallet standard has been completed

Abstract

NEP-6 describes a wallet standard that will support the sharing of wallet files among NEO's various wallet clients.

target

Currently, different client programs generate different wallet files. They have different file formats, different storage methods, and different encryption methods. It is difficult for users to migrate between different client programs because the wallet file format is different. Although migration can be achieved by exporting private keys, this is very troublesome for wallets with multiple private keys. We need a common wallet format that allows users to safely and easily migrate to all platforms without having to change wallet files or export private keys.

Basic principles

Wallet standards should consider security and cross-platform compatibility. For security reasons, we require the implementation to use the NEP-2 (https://github.com/neo-project/proposals/blob/master/nep-2.mediawiki) mechanism to encrypt or decrypt the private key. To achieve cross-platform requirements, we use the JSON format to describe the wallet file so that the contents of the wallet file can be identified on each platform.

Standard

The wallet file in JSON format consists of the following basic structure

{"name": "MyWallet", "version": "1.0"," scrypt ": {}," accounts ":\ [\]," extra ": null}

Name is the mark made by the user to the wallet file.

Version has currently fixed 1. 0 and will be used for future feature upgrades.

Scrypt is a ScryptParameters object that describes the parameters of the SCrypt algorithm used to encrypt and decrypt the private key in the wallet.

Accounts is an array of Account objects that describe the details of each account in the wallet.

Extra is an object defined by the implementer of the customer to store additional data. This field can be null.

ScryptParameters

The ScryptParameters object has the following structure:

{"n": 16384, "r": 8, "p": 8}

N is the parameter that defines the CPU / memory cost. Must be a value of 2 ^ N.

R is an adjustment parameter.

P is an adjustment parameter (parallel parameter). A large p value increases the computational cost of SCrypt without increasing memory usage.

Account

The account object has the following structure:

{"address": "AQLASLtT6pWbThcSCYU1biVqhMnzhTgLFq", "label": "MyAddress", "isDefault": true, "lock": false, "key": "6PYWB8m1bCnu5bQkRUKAwbZp2BHNvQ3BQRLbpLdTuizpyLkQPSZbtZfoxx", "contract": {}, "extra": null}

Address is the base58-coded address of the account.

Label is the label that the user makes to the account.

IsDefault indicates whether the account is the default change account.

Lock indicates whether the account is locked by the user. Customers should not use the funds for locked accounts.

Key is the private key of an account in NEP-2 format. This field can be null (for monitoring addresses or non-standard addresses only).

Contract is the object of the contract that describes the details of the contract. This field can be null (address for viewing only).

Extra is an object defined by the implementer of the customer to store additional data. This field can be null.

contract

The contract object has the following structure:

{"script": "21036dc4bf8f0405dcf5d12a38487b359cb4bd693357a387d74fc438ffc7757948b0ac", "parameters":\ [\], "deployed": false}

Script is the script code for the contract. If the contract has been deployed to the blockchain, this field can be null.

Parameters is an array of Parameter objects that describes the details of each parameter in the contract function. For more information about the Parameter object, see the instructions in NEP-3:NeoContract ABI. (https://github.com/neo-project/proposals/blob/master/nep-3.mediawiki)

Deployed indicates whether the contract has been deployed to the blockchain.

Old version compatibility

All wallets in the old format should be easily converted to this new JSON format. If these wallet files contain some additional data, they can be stored in the file extra.

At this point, I believe you have a deeper understanding of "what is the standard of NEP6 wallet". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.