### How to make transfers with Metaverse Wallet

First select “My Assets” in the left navigation bar, then click “ETP”

The transfer interface shown below will be displayed on the right. Please input information as per the directions written in yellow. The transaction is complete when you click “Confirm to Transfer”.

The red arrow indicates that ETP is being transferred out of your Wallet, while the green arrow indicates that ETP is being transferred from elsewhere into your Wallet.

### Wallet synchronization guide

#### 1. how to determine whether the Wallet is being synchronized.

If the above interface is continually shown, and the number within the red box is increasing, the Wallet is being synchronized.

#### 2．How to determine whether the synchronization is completed?

In general, when the numbers on the screen are no longer updated and “connected to outbound channel” is continuously displayed, the synchronization has been completed.

Alternatively, click http://explorer.mvs.live/ to view the current number of blocks. If it matches the number of blocks shown in the synchronization program, the synchronization has been completed.

The time required for the entire synchronization lengthens with the number of blocks on the public chain. It typically takes two or three hours to complete, and also depends on your network speed. Once completed, you need only synchronize the latest data when opening the Wallet next time.

#### 3. How to proceed after the completion of synchronization?

Please do not close the synchronization program after the synchronization is completed. Open the link included in the set-up package to enter the Wallet page and register an account. (You cannot visit the site if you close the synchronization program)

Note: Please be sure to open the Wallet from this site, it is recommended to bookmark this site.
Note: You are required to open the synchronization program each time you use the Wallet. Please keep the synchronization program open during the whole transaction process.

### Detailed explanation of the uses of a mnemonic passphrase (private key)

When you apply for a new account in the Wallet, you can receive a set of mnemonic keywords:

As the red mosaic part shown above, the mnemonic passphrase is a string of English words.

This string of words is important. Please do not reveal parts or all of it to anyone, and please do not forget or lose your mnemonic keywords.

This is an important private key to store your account information. When you login to your account with another device or accidentally lose your account password or account information, the private key can help you retrieve all of it.

Usage method (to retrieve all your account information or login with another computer):

After selecting “New” on the login page, check “Import Account” on the new page and input your main account mnemonic words. The new account can retrieve all your original account information.

#### Version 0.6.9 contains the following updates:

1. Added the functionality of adding a specified number of decimal places (minimum transaction unit) to asset issuance.
2. Remarks can now be attached to transactions.
3. Optimized performance and network synchronization.
4. Repaired hash collision problems in database transactions.
5. Repaired asset transfer display problems.
6. Some other non-functional changes.

#### Regarding increasing the number of decimal places for asset issuance:

1) The default number of decimal places for assets already issued is zero, i.e. all of them are integers.
2) ETP transfer is not affected.
3) If you wish to use ‘Asset Transfer’ to send and receive assets with decimal places, please use v0.6.9.
4) After updating, if the explorer does not reflect the update, please use ‘command + shift + R’ to update the cache (OS X users) or ‘ctrl + F5’ (Windows users).

This release is a software upgrade, focusing on fixing Wallet bugs and enhancing functions. The local database index rebuild will automatically update the database (the blocks needs to re-sync). Please wait patiently.

Regards,
Core development and operations team of Metaverse Foundation.

### Metaverse main net parameters

Total amount：100,000,000 ETP

Current circulation: https://explorer.mvs.live/circulation

Mining algorithm: Improved version of ETHASH

Actual block generation time: 33 Seconds

ETP mining rewards: The initial reward is 3ETP. Mining rewards decrease by 5% every 500,000 blocks.

Main net go-live time: February 11, 2017

#### Preface

Metaverse’s network began operating on February 11th, 2017 and has been running safely for three months (89 days) now. Some of our network’s operating parameters are as follows.

◦ Total volume: 100 million
◦ Current turnover: 26.93 million
◦ Mining algorithm: ethash
◦ Average block generation speed: 33 seconds.
◦ PoW mining reward: the reward starts at 3 ETP and will decrease by 5% every 500,000 blocks.
◦ Date network went online: February 11th, 2017

For more details, interested readers can refer to our white paper: http://newmetaverse.org/white-paper/Metaverse-white-paper-v2.1-CN.pdf

#### MIPs (Metaverse Improvement Proposals)

Metaverse’s core development team has updated a total of 7 patch versions during this period, namely versions 0.6.6-0.6.8.

Most of the bug fixes have been posted on Github: https://github.com/mvs-live/metaverse/issues

With an increase in the number of users, we found some problems. Some problems are related to the wallet experience, while others concern compatibility issues. After discussing this, our core team has decided to focus on fixing non-functional bugs first. As for digital identity, asset pledges and other functions, Metaverse will release a process similar to BIPs , with the aim of building a better Metaverse by adopting community suggestions. This process will be called MIP and is currently being drafted. More detailed information can be found on Github: details.https://github.com/mvs-live/mips (continuously updated).

Regarding the MIP, Metaverse will provide ETP incentives. Please anticipate the release of more detailed information.

#### First MIP - digital identity (Avatar, Digital Identity)

The next goal of Metaverse’s core development team is to design and realize digital identities (Avatars).

The team has been researching on digital identity, and has drafted a working definition:

Digital identity is a general name for the Profile information of an account corresponding to the master private key owned by a user.

Profiles are assigned a unique identifier within the network. On Metaverse, this identifier will be called a DID (Digital Identity, similar to the concept of aliases in Bitshares).

A Profile contains the following information:

◦ Personal transaction records.
◦ Statistics and record details, does not require additional storage.
◦ Asset information.
◦ Statistics and record details, does not require additional storage.
◦ Feedback records from across the entire network.
◦ Statistics and record details, does not require additional storage.
◦ Customized field description.
◦ This customized field has a validity period. The field should indicate the height interval at which it is valid, and this field can be modified to correspond to different block heights.
◦ This field is presented in the form of key: value and has no upper limit. However, the fee incurred increases exponentially as the number of characters increases.

A digital identity’s core functions are authentication and transaction authorization.

Metaverse will successively release pieces of research and design related to digital identities.

Cheers,
Metaverse core development and operations team

### User guide for Metaverse ETP Wallet server

#### Preface

The Metaverse Wallet is built on Libbitcoin.
The use of rpc is similar to bitcoin’s, but they have different interfaces.

#### RPC Allocation

The default port for RPC initiation is 8820. Https is not supported for now.
You can configure to other ports on mvs.conf.
Please visit: https://github.com/ViewBTC/mvs-exchange-tools for code samples of PHP linking to ETP wallets. Sample codes in other languages will be available soon.

Mvs-cli also invokes port 8820 by default to execute RPC.
Hence, the data retrieved from the user explorer is the same as the call of mvs-cli.

#### Checking help information

All commands support the “help” command.
Mvs-cli can also be an operating console within the user explorer.
1. # Check all commands
2. mvs-cli help
3. # Check specific command parameters and descriptions
4. mvs-cli help send
5. # or
6. mvs-cli send -h

#### Commands traversing blocks

1. # Inquire the block hash corresponding to a block height
2. ./mvs-cli fetch-header -t $block_height 3. # Check the previous block structure for a corresponding block hash 4. ./mvs-cli getblock$block_hash --json=true

#### Creation of HD accounts and address management

Metaverse discarded the idea of using random keys since the beginning of its design process. All transactions are managed by sub-private keys of a master private key.

The master private key + index generates corresponding sub-private keys.

Your account number and password belong to the Wallet and is stored locally rather than as on-chain data. Hence, it cannot be imported using the mnemonic passphrase provided together with your Wallet (the 24-word or Mandarin character mnemonic passphrase provides a human-readable phrase to backup your Wallet in case you need to recover your it at a later date).

If you log in to a new wallet, you may not reuse your previous account name and password. A new account must be created. Lost account details are retrievable as long as you have a backup of the mnemonic passphrase.

1. # Create a new account
2. mvs-cli getnewaccount $name$password
3. # Use this account to generate addresses; these addresses absolutely belong to the account.
4. mvs-cli getnewaddress $name$password
5. # Check my account’s address
6. mvs-cli listaddresses $name #password An account’s name and password are equivalent to the main private key’s alias within a specified wallet. Account names have a one-to-one relationship with main private keys, and using an account’s name and password is equivalent to using its corresponding main private key. Hence, the commands listed above illustrate how a main private key can be used to generate new addresses. The total number of indexes for a main private key is about 4 billion. By default this increases from zero, so you only need to back up the main private key and should not create a backup for your account name and password. If you have lost or forgotten your login details, you may retrieve it using your mnemonic passphrase. Using the “importaccount” command, input the size of your designated index; the Wallet will then generate a corresponding digital address. For more details, please check “help”. On Metaverse, the only certificate of all personal assets (including assets issued by oneself) is the master private key’s mnemonic passphrase. Metaverse Wallet has yet to make file-level backups, so please make sure to keep a backup of the mnemonic passphrase for your master private key (the 24-word phrase). Backing up this phrase ensures that you will not lose any of your assets. There is no way to retrieve the mnemonic passphrase using your account’s username and password. #### Sending transactions (key points) 1. # “send” command 2. mvs-cli send$name $password$target_address $amount 3. # “sendfrom” command 4. mvs-cli send$name $password$from_address $target_address$amount

Detailed explanation for “send” command (key points):
The “send” command has been optimized for users. It supports regular transactions, breaks up the change into multiple outputs then sends those outputs to randomly chosen addresses belonging to the user. We do not recommend using this command on the back-end.

Application of the “send”command on the server side: when small change needs to be organized or entire amounts sent to other addresses. To send change with certainty, please use the “sendfrom” command instead.

Detailed explanation for “sendfrom” command:
The “sendfrom” command supports sending change to a specific address. It is very similar to implementations of this command in other wallets.

#### QA about assets and transaction management

1. How do I check assets using transaction history?
Transaction histories contain an attachment which has “type”. If the type is etp, it was an ETP transaction. If an asset was issued, the transaction is labeled with some other symbol. Currently there are some test tokens. To view these, use “listassets” without any added parameters.
2. How should I regard the relationship between ETP and other assets?
ETP is equivalent to Ethereum’s ETH, and other assets are equivalent to tokens.
3. What if someone obtains my account
Fail to get the private key of designated address. If the designated address issues transaction, we have “sendfrom” command to support the address, then the address belongs to the account.
4. How to create a raw transaction through transfer record? It is similar to the createrawtransaction of bitcoin.
For rawtransaction, it belongs to component transaction, which is supported by the native command, libbitcoin. We retain the function, but it is not recommended to use. For more details, please visit: https://github.com/libbitcoin/libbitcoin-explorer/wiki/How-to-Spend-Bitcoi. Replace the bitcoin part to the address and utxo of Metaverse, which remains valid.

5. How to use private key to sign the raw transaction?
As above, it is recommended to use HD address.

6. How to generate an address via HD?
/mvs-cli getnewaddress $account_name$account_password

Username and password are equivalent to alias of your main private key in the Wallet. Username and the main private key are one-to-one corresponding relations. The use of username and password is equivalent to the call of corresponding main private key, thus the command mentioned above is to use some main private key to generate a new address.