ReleaseNotes – the previous version of Metaverse and its download address

Version 0.6.8 release notes:

  1. Now displays transaction hash.
  2. Added the function to send ETP from a specified address.
  3. Fixed the issue of too much ETP being frozen when assets are launched.
  4. Added a feature showing all issued assets.
  5. Added designated block height - checkpoint.
  6. “listtxs”command now orders transactions sequentially, and fixed the bug of inquiring in accordance with address.
  7. Added designated address for small change for “sendmore” command.
  8. Removed the “forgot password” function
  9. Updated non-functional features.

Version 0.6.8b:

  1. Rollback: randomly distributing the search for small change among the trading body.
  2. Repaired some user-facing functionalities.

Version 0.6.8c:

  1. Repaired bug that didn’t allow assets to be transferred on the front page.
    Download address for Linux: http://newmetaverse.org/mvs-download/mvs068c-linux-x86_64.zip
    Download address for OSX: http://newmetaverse.org/mvs-download/mvs068c-OSX-x86_64.zip
    Download address for Windows: http://newmetaverse.org/mvs-download/mvs068c-win64.zip
    This version is a patch that aims to repair bugs and improve functionality. Users do not need to re-synchronize block data.

Version 0.6.7:

  1. Amended some functionality issues.
  2. Decreased the number of logs generated while synchronizing blocks.
  3. Added the function to deposit into a specified address.
  4. Other known issues.

The updated version, which serves as a patch, aims to repair bugs and improve functions. It is not involved in any account’s data migration. If you want to download the latest version, please visit our official website: http://mvs.live.

Version 0.6.6:

  1. Added “gettransaction” command. The command takes a transaction hash as input and returns the corresponding transaction’s information and block height.
  2. Modified listtx command. After the modification, the command now returns 100 lines of an account’s transaction records by default rather than the account’s entire transaction history.
  3. Added utxo limitation. If the UTXO of an address contains assets, the ETP in that UTXO can only be used for asset transactions and cannot be used for ETP -> ETP transactions.
  4. Added a function to borrow ETP. When you transfer assets, if an address has insufficient ETP to complete the transfer, you can borrow ETP from other addresses in your account with sufficient ETP to finish the asset transfer.
  5. Updated content indicators on WebUI, making it more user-friendly
  6. Added wrong prompt content on WebUI
    Download address for Linux: http://newmetaverse.org/mvs-download/mvs066-linux-x86_64.tar.gz
    Download address for OSX: http://newmetaverse.org/mvs-download/mvs066-OSX-x86_64.tar.gz

The updated version, which serves as a patch, aims to repair bugs and improve functions. It is not involved in any account’s data migration. If you want to download the latest version, please visit our official website http://mvs.live.

Version 0.6.5:

Amending some known issues.
Download address for Linux: http://newmetaverse.org/mvs-download/mvs065-linux-x86_64.tar.gz
Download address for OSX: http://newmetaverse.org/mvs-download/mvs065-OSX-x86_64.tar.gz

The updated version, which serves as a patch, aims to repair bugs and improve functions. It is not involved in any account’s data migration. If you want to download the latest version, please visit our official website: http://mvs.live.

Version 0.6.4

Amending some known issues.
The updated version, which serves as a patch, aims to repair bugs and improve functions. It is not involved in any account’s data migration. If you want to download the latest version, please visit our official website: http://mvs.live.

Read More

Introduction to Metaverse input/output limitation and the rectifying of small change

When the Metaverse was first introduced this week, we realized that miners could not transfer out ETP obtained through mining. After debugging and testing, we found that there was a bug in the group transaction algorithm resulting from a lack of restriction on input/output.

Problems arose with the group transaction algorithm because Metaverse uses address rather than input as the most granular during the process of looking for input. Hence, if an account’s balance is sufficient, all ETP will be transferred retuning 0 to the address. This has led to a particularly large number of problems occurring with input, and too much input will cause a large transaction.
Metaverse uses the UTXO model. In the UTXO model, the number of inputs / outputs is limited.

In Bitcoin, transactions with one proven input and one output occupies about 161 - 250 bytes.
In Bitcoin, transactions smaller than 100kb are termed standard transactions while those larger than 100kb are termed non-standard transactions.
So in Bitcoin, the maximum number of inputs / ouputs is limited to 100KB / 161B ~ = 600 per transaction.

There are similar limitations on transaction sizes on Metaverse. However, due to the asset issue function, the number of inputs / ouputs per transaction is limited to around 333 instead.
For ordinary users, large numbers of small amounts (input) should not appear frequently. If they do, you can manually send the rectified transaction (for large denominations):
You have 900 inputs, and each input contains an ETP. When you want to return the 900 ETP, it is better to divide it into three transactions. Each transactions transfers 300 ETP to the same address A which will contain 3 inputs, with each input containing 300ETP.
This is the same for miners, and each coinbase only generates three ETP.

In other words, miners not only do mining, but also need to undertake the rectification of tokens by swapping small ETP for larger denominations of ETP then lastly placing the ETP into circulation after rectification.

Considering the limitation of around 330 ETP, each transaction can be rectified to 1,000 ETP.
For example, if miners have gotten 20,000 ETP as a reward for mining, they would require about 20 transactions sent to the same address (that is, 20 inputs; the following transactions will become normal).

We fixed the problem in updated 0.6.3 version.
The updated version, which serves as a patch, aims to repair bugs and improve functions. It is not involved in any account’s data migration. If you want to download the latest version, please visit our official website http://mvs.live.

Read More
Skip to toolbar