Quote from: ShiftyTripster on November 19, 2018, 01:37:49 AM

Quote from: MetaHash on November 16, 2018, 09:00:06 AM

Quote from: ShiftyTripster on November 16, 2018, 08:55:03 AM

Quote from: MetaHash on November 16, 2018, 08:35:11 AM

Quote from: ShiftyTripster on November 16, 2018, 08:11:13 AM

Quote from: MetaHash on November 16, 2018, 06:48:30 AM

Quote from: ShiftyTripster on November 16, 2018, 06:25:50 AM

Quote from: MetaHash on November 16, 2018, 05:55:01 AM

Quote from: ShiftyTripster on November 16, 2018, 04:48:29 AM

hello

Hello and welcome to #MetaHash topic!
We'll be happy to answer your questions about the project Wink

Whats difference btw dpos and multipos? For me it sound similar

DPoS is actually very different from PoS. In DPoS, token hodlers dont vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21100 elected delegates in a DPoS system. The delegates are shuffled periodically and given an order to deliver their blocks in. Having few delegates allows them to organize themselves efficiently and create designated time slots for each delegate to publish their block. If delegates continually miss their blocks or publish invalid transactions, the stakers vote them out and replace them with a better delegate.

What is the role of voting in the metahash?

Page 39-40 of WhitePaper - https://static.metahash.org/docs/MetaHash_WhitePaper_EN.pdf?v=5
Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4

Okay... One more question.
I made a transactions. Which path did it pass to be success?

Here is what happens to a transaction:

- 0.2-0.4 seconds transmission between Peer Nodes.
- The peer nodes maintain connections to slow clients and reject transactions with invalid signatures.
- 0.8-1.2 seconds transmission to Verification Nodes.
- Verification Nodes are organized into latency clusters with Masters/Slaves spanning geographically remote areas.
- Verification Nodes check if there are enough funds to complete the transaction and carry the load associated with high-latency cross-continental peer connections.
- 0.4-0.6 seconds transmission to Master Nodes.
- The Master Nodes sync lost transactions and build a block from correct transactions.
- 0.3-0.5 seconds Slaves check the validity of the block created by the Master Nodes and send it on to the torrents.
- 0.6-0.8 seconds blocks from the nearest Slave Nodes are propagated via torrents, from which the client can collect transaction confirmation and current balances.
- If torrents consider themselves invalid, they launch the process of role redistribution and verification of what Master/Slave Nodes have been corrupted.

Does it happen within 3 seconds? I don't believe!

No, it is real Wink

You can try how fast our blockchain, just make a TestMetaHash wallet and receive 10 TMH to test the speed of our transactions!