Project MANTA NETWORK - Plan “B” in the security system
Anonymous transactions
Users are provided with the MantaDAP format related to decentralized anonymous payment (DAP). In fact, the payment protocol hides the identifiers of the assets, which is why any fraudster is not able to transfer the fundamental type of assets in his favor. Combining a pool of private transactions into one shared volume provides the best privacy, as well as guarantees for those long-term assets that may have low trading volume per se.
Based on this, issuance and recovery allow for two-way transfers between private base coins.
This business process idea applies to other types of decentralized exchanges as well. Therefore, we rely on the fact that a decentralized exchange has three main features:
– Users participating in the exchange;
– The volume of trading pairs, which determines the ratio of trading;
– A liquidity provider that supplies equal values to the pool
The essence of the activity originates from the basic design, in which liquidity providers are publicly available and where the method of providing liquidity is excluded. The next stage is a more sophisticated version that ensures the privacy of liquidity providers.All of these are quite compatible with each other. In the current world, it is possible to provide liquidity through a public or private channel.Available private coins can be transferred and spent using a transfer operation that takes a set of input private coins. It is important to note that the coins for consumption are translated into a total value in a set of new output coins, and the total value of the output coins equals the total value of the input coins
Conductivity
Initially, the payload that needs to be sent for each type of financial and other transactions in the network is reported. Fundamentally, one token is created in the amount of 112 bytes of payload. In transfer and exchange, each consumes two old tokens and creates two new tokens, which in turn requires more than 600 bytes of payload. When restoring, two old tokens are consumed and one new token is created already at 512 bytes of payload.
Based on this, test results are generated. This process is based on an AMD 5900x processor, 32 GB of memory, and an Ubuntu 20.04 system.
In this case, there are two sets of standards. The first is unit benchmarks, in which we measure the cost and creation with zero-knowledge proofs for each set of claims. In general, the verification time is about 15 seconds and 6 milliseconds proportionally.
#createwithmantanetwork #polkadot
The task of the second test is to integrate the protocol into the blockchain, deploy the test network and evaluate the end-to-end latency. The information is collected from the local host and this factor helps eliminate network latency and increase viewing latency associated with zk-SNARKs.
In general, transactions related to ZKP, such as transfer and exchange, take about 10ms. This data measures transactions per second (TPS) in both the native runtime and WASM. The block completion time is set to 6 seconds, during which 2 seconds are dedicated to the validation operation itself. This is due to the configuration result from the Polkadot network. But it should be noted that individual settings will give, ceteris paribus, different performance
Author Evgeniy Ivanov
