[ANN][ICO]⚡ Metahash - cryptocurrency for decentralized apps⚡

[MetaHash]

Hi, i'm looking forward at your project. What will be the minimum participation amount for round A?

There will be no minimums.

There will be 2 Pools.

1st Pool - under 50 ETH. And 2nd Pool - over 50 ETH
2nd Pool is limited. So once it closes, only under 50 ETH will be allowed.

Thanks, what is about hardcap?

Our hardcap is 36M

[1715278906]

1715278906

[1715278906]

1715278906

[1715278906]

1715278906

[gembira]

Which advantages you have before other blockchains like Ethereum, EOS, Ziliqua and many other? Do you have a compare with other similar projects?

yeah, sure. you can have a look at our WP from page 9. or, general aspects here. and about Zillqa it's based on PoW. #MetaHash is based on multi-POS. Multi-POS - a hybrid POS system. It combines traditional POS (proof of stake) with a voting system. SO every computer in blockchain can vote

Thank you, but I dont see there any compare with other projects. Just a few words that you project "better", but no explaine why. 

[drontus]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

[MetaHash]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

[drontus]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

[MetaHash]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

[N0XyJeamBeam]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

Hello, so peers being these 'common nodes, right? who then pass it down the chain

[MetaHash]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

Hello, so peers being these 'common nodes, right? who then pass it down the chain

wallet connects to 3 peers, they broadcast it and send to verification nodes
if the wallet doesn’t receive a reply that   masters and backups got the tx it resends it
we understand that an attack to slow down the network is a serious issue
so we check not only if the node works correctly but also it’s speed

[N0XyJeamBeam]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

Hello, so peers being these 'common nodes, right? who then pass it down the chain

wallet connects to 3 peers, they broadcast it and send to verification nodes
if the wallet doesn’t receive a reply that   masters and backups got the tx it resends it
we understand that an attack to slow down the network is a serious issue
so we check not only if the node works correctly but also it’s speed

The wallet/lite client itself connects to other peers? not just to its host?
but, this open to a sybil attack the power of spam is fearsome

[MetaHash]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

Hello, so peers being these 'common nodes, right? who then pass it down the chain

wallet connects to 3 peers, they broadcast it and send to verification nodes
if the wallet doesn’t receive a reply that   masters and backups got the tx it resends it
we understand that an attack to slow down the network is a serious issue
so we check not only if the node works correctly but also it’s speed

The wallet/lite client itself connects to other peers? not just to its host?
but, this open to a sybil attack the power of spam is fearsome

yes it’s the hardest problem to solve
we’ll make a public bounty for hackers to test the network against different types of attacks
the wallet can be a full node, but usually its lite
so it checks the data from multiple full nodes to verify if data is correct

[lennymat86]

How will you know if a tx is incorrect? aka how are txs broadcasted to the network as if there's 1 receiver

all network votes if masters did their job right

Then you're in a problem spot
.so it sounds like common nodes are comparable to lite clients, with the exception that they do some minor processing of txs. but the challenge is who's the receiver. it's like a message being passed around. common nodes are full clients. anytime a message hits a bottleneck it can be intercepted and stopped

common nodes don’t have the speed to check all, so they check only the part they transferred but all together they check 100% of all txs more over there are 2 networks of master nodes: sync and backup. one checks another. the verification checks them both and peers check them partly. masters can make a block together, but if it’s wrong, the network will decline it

Hello, so peers being these 'common nodes, right? who then pass it down the chain

wallet connects to 3 peers, they broadcast it and send to verification nodes
if the wallet doesn’t receive a reply that   masters and backups got the tx it resends it
we understand that an attack to slow down the network is a serious issue
so we check not only if the node works correctly but also it’s speed

The wallet/lite client itself connects to other peers? not just to its host?
but, this open to a sybil attack the power of spam is fearsome

yes it’s the hardest problem to solve
we’ll make a public bounty for hackers to test the network against different types of attacks
the wallet can be a full node, but usually its lite
so it checks the data from multiple full nodes to verify if data is correct

The big challenge is brute forcing. since it seems like the only cost is time aka patience. and setting up a bunch of servers and then blasting simultaneously

[CryptoCause]

what's necessary to do to participate at the ico?

[MetaHash]

what's necessary to do to participate at the ico?

You have to download our wallet and just wait to June 29th. to ICO Round start
Also you can leave an application for participation on our site
Later we will post detailed instructions

[ShiftyTripster]

how to make dApp for metahash?

[MetaHash]

how to make dApp for metahash?

If you write web apps, you would easily make a dApp for metahash.
You make a standard web app and pack it as an image. It gets distributed in cloud.
There would be an API to send and get data to store in the network. MetaHash will handle distribution.
Data can be stored in side networks leaving only hashes in main network, so it won’t get too expensive.
If you’ll need token creation we’ll have smart contracts examples in different languages and decentrilized oracles to react to transactions in different blockchains.
Using all this lets you create apps of any complexity serving millions of users in real time.
More apps in network - more servers people add.

[uberua]

How does a node become a #MetaApp node? It's assigned by #TraceAI ?
By the WP looks like it's a different role

[Chimsley]

If a trusted masternode decides to block TX from antes specific address, the peers detect it?

[MetaHash]

If a trusted masternode decides to block TX from antes specific address, the peers detect it?

yes, if a valid tx doesn’t go through, peers will vote to lower masters trust and master will become a common peer from there a master can slowly gain trust again over time.

[Chimsley]

If a trusted masternode decides to block TX from antes specific address, the peers detect it?

yes, if a valid tx doesn’t go through, peers will vote to lower masters trust and master will become a common peer from there a master can slowly gain trust again over time.

And if a trusted masternode decides to stop processing transactions or behave bad, how long does it take to the network to recover to normal throughoutput?

[MetaHash]

If a trusted masternode decides to block TX from antes specific address, the peers detect it?

yes, if a valid tx doesn’t go through, peers will vote to lower masters trust and master will become a common peer from there a master can slowly gain trust again over time.

And if a trusted masternode decides to stop processing transactions or behave bad, how long does it take to the network to recover to normal throughoutput?

no time, slaves will take masters place
slaves are there to change roles with masters on the fly slaves are really masters that are put on hold and verify masters work