Pages:
Author

Topic: [ANN][ICO]⚡ Metahash - cryptocurrency for decentralized apps⚡ - page 67. (Read 63668 times)

member
Activity: 161
Merit: 13
We have an idea we want to discuss with you.

Please tell what you think.

Idea against theft of crypto assets.


Idea abstract example:

Smart contract or special wallet with a second signature that can cancel a transaction within a certain period specified by a data-transaction in the network.

Simple example.
An exchange creates a wallet where it keeps its assets.
It sets 24 hours to cancel any outgoing transaction by an additional password.
The second password is stored securely and is not needed until a successful hacker attack happens.

Negative:
- you have to wait for 24 hours (or whatever time is specified)
- if you lose the second password your assets could be blocked by an attacker, but you keep the password securely stored for emergency and don't have to use it online until it happens

Positive:
even if you lose both passwords hacker can't use the funds, it will be a cat and mouse game that will discourage stealing


There can be multiple variations.

The same password can make transactions and cancel.
MultiPasswords for cancelation are needed.
And other. It's cool.

The main disadvantage is that no TX is really committed until X hours passed. For daily traders, this might not be something positive.
This mitigates the impact of the hacked exchange risk.
The hacking best strategy, in this case, would be to retire small amounts trying to minimize the chance that the exchange realizes it.
Other systems use some kind of blacklist to make the hacked assets unusable, but that requires some degree of centralization.
member
Activity: 1159
Merit: 19
Join the ride!
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


soo, there is no downtime, right?

a couple of seconds that corrupt masters will slow the network before they are voted out by peers. the point is that lots of peers that are common cheap nodes like 40$ a month virtual machines vote who becomes masters and verification nodes
peers are slow and can handle only part of tx but are good at protecting the network
in our tests low cost peers work at 10 000 second while expensive servers reach 500+k tx
Also it’s important that our consensus is protected by #MetaHash Coins
To become a master you need 100 000 coin votes. To get those you have to be trusted by community or invest 80eth at the price of ico. If you loose trust you loose a couple month worth of commissions and forging pool share


newbie
Activity: 75
Merit: 0
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


soo, there is no downtime, right?
member
Activity: 1159
Merit: 19
Join the ride!
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
newbie
Activity: 75
Merit: 0
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?
member
Activity: 1159
Merit: 19
Join the ride!
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.
member
Activity: 1159
Merit: 19
Join the ride!
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.  Huh

Ok, sent you a PM with more detailed comparison
newbie
Activity: 75
Merit: 0
If a trusted masternode decides to block TX from antes specific address, the peers detect it?
member
Activity: 179
Merit: 10
How does a node become a #MetaApp node? It's assigned by #TraceAI ?
By the WP looks like it's a different role
member
Activity: 1159
Merit: 19
Join the ride!
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.
newbie
Activity: 93
Merit: 0
how to make dApp for metahash?
member
Activity: 1159
Merit: 19
Join the ride!
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
newbie
Activity: 68
Merit: 0
what's necessary to do to participate at the ico?
member
Activity: 140
Merit: 10
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
member
Activity: 1159
Merit: 19
Join the ride!
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
newbie
Activity: 80
Merit: 0
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
member
Activity: 1159
Merit: 19
Join the ride!
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
newbie
Activity: 80
Merit: 0
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
member
Activity: 1159
Merit: 19
Join the ride!
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
newbie
Activity: 40
Merit: 0
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
Pages:
Jump to: