Quote from: MetaHash on June 22, 2018, 10:05:46 AM

Quote from: N0XyJeamBeam on June 22, 2018, 08:39:53 AM

Quote from: MetaHash on June 22, 2018, 08:14:15 AM

Quote from: N0XyJeamBeam on June 22, 2018, 07:12:12 AM

Quote from: MetaHash on June 22, 2018, 06:14:50 AM

Quote from: drontus on June 22, 2018, 05:48:47 AM

Quote from: MetaHash on June 22, 2018, 05:45:44 AM

Quote from: drontus on June 22, 2018, 05:21:57 AM

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 dont 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 its 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 doesnt 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 its 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 its the hardest problem to solve
well 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