miTgiB
Full Member
 
Offline
Activity: 251
Merit: 100
Du hast
|
 |
November 14, 2018, 05:27:01 AM |
|
Ok, thanks. And do you plan to start next round of ICO?
|
|
|
|
|
|
|
|
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
247mining (OP)
Member

Offline
Activity: 161
Merit: 13
|
 |
November 15, 2018, 04:23:53 AM |
|
#MetaWallet Beta test - Android 📲
CLICK THE PIC TO READ MORE
|
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 01:46:43 AM |
|
Thank you very much for sharing the link to article on Medium channel, specifically discloses details about Metahash ICO. All best wishes for future achivements of MetaHash. Please, feel free to ask any other questions!
|
|
|
|
miTgiB
Full Member
 
Offline
Activity: 251
Merit: 100
Du hast
|
 |
November 16, 2018, 02:35:56 AM |
|
#MetaWallet Beta test - Android 📲
CLICK THE PIC TO READ MORE
I'm not sure, that understand, how to test it and download. Could you explain?
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 04:15:32 AM |
|
#MetaWallet Beta test - Android 📲
CLICK THE PIC TO READ MORE
I'm not sure, that understand, how to test it and download. Could you explain? Please, follow the link - https://play.google.com/apps/testing/org.metahash.metawallet and choose "Download it on Google Play"
|
|
|
|
ShiftyTripster
Newbie
Offline
Activity: 93
Merit: 0
|
 |
November 16, 2018, 04:48:29 AM |
|
hello
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 05:55:01 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project 
|
|
|
|
ShiftyTripster
Newbie
Offline
Activity: 93
Merit: 0
|
 |
November 16, 2018, 06:25:50 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 06:48:30 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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.
|
|
|
|
ShiftyTripster
Newbie
Offline
Activity: 93
Merit: 0
|
 |
November 16, 2018, 08:11:13 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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?
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 08:35:11 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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=5Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4
|
|
|
|
ShiftyTripster
Newbie
Offline
Activity: 93
Merit: 0
|
 |
November 16, 2018, 08:55:03 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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=5Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4Okay... One more question. I made a transactions. Which path did it pass to be success?
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 16, 2018, 09:00:06 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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=5Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4Okay... 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.
|
|
|
|
ShiftyTripster
Newbie
Offline
Activity: 93
Merit: 0
|
 |
November 19, 2018, 01:37:49 AM |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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=5Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4Okay... 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!
|
|
|
|
Thanyaboon
Newbie
Offline
Activity: 39
Merit: 0
|
 |
November 19, 2018, 04:21:09 AM |
|
I love metahash
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 19, 2018, 04:49:48 AM Merited by lennymat86 (1) |
|
hello
Hello and welcome to #MetaHash topic! We'll be happy to answer your questions about the project  Whats difference btw dpos and multipos? For me it sound similar DPoS is actually very different from PoS. In DPoS, token hodlers don’t vote on the validity of the blocks themselves, but vote to elect delegates to do the validation on their behalf. There are generally between 21–100 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=5Page 24 of YellowPaper - https://static.metahash.org/docs/MetaHash_YellowPaper_EN.pdf?v=4Okay... 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  You can try how fast our blockchain, just make a TestMetaHash wallet and receive 10 TMH to test the speed of our transactions!
|
|
|
|
MetaHash
Member

Offline
Activity: 1159
Merit: 19
Join the ride!
|
 |
November 19, 2018, 05:34:53 AM |
|
I love metahash
Thank you for your support!
|
|
|
|
247mining (OP)
Member

Offline
Activity: 161
Merit: 13
|
 |
November 19, 2018, 06:52:31 AM |
|
Please, feel free to check the article about us!
CLICK THE PIC TO READ MORE
|
|
|
|
lennymat86
Member

Offline
Activity: 140
Merit: 10
|
 |
November 19, 2018, 08:42:31 AM |
|
Please, feel free to check the article about us!
CLICK THE PIC TO READ MORE
Blockchain 4.0? Can you tell about it more?
|
|
|
|
|