Matthew Mitchell

less info
123 reputation
3
bio website
location
age
visits member for 1 year, 11 months
seen May 21 at 19:24

Aug
21
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
I would not want to put trust in a single data-centre. Any downtime would be very bad for the service I'm providing.
Aug
21
awarded  Supporter
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
let us continue this discussion in chat
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
What if you have nodes A, B and C. AB are connected and C is left on it's own. A client may be able to access A, B and C and use the AB partition or would that never be the case?
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
As long as the client can reach a node that can achieve a quorum that is.
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
I can program the client to try other nodes if one node cannot achieve a quorum. So if the client makes a request to a node in a partition without the quorum, it will eventually choose a node with a quorum. So the client will be able to spend.
Aug
19
awarded  Scholar
Aug
19
accepted Risks of Network Partitioning When a Split Brain Creates a Security Flaw
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
The solution does provide availability of the system in the cases where a minority of nodes are down or are not reachable between each other but not if a majority cannot be reached between each other. Still, what are the chances that the majority of nodes go down at the same time (unless a bug in the software)? This solution would also require more communication between nodes than longneck's solution but creating an extremely lightweight communication protocol should not be difficult and multiple requests/responses can be sent together when nodes are busy. Definitely worth experimenting with.
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
Thank you for the answer. The quorum solution is very appealing although quite complex to ensure correct communication between nodes. From how I understand it, to process a spend request a node would need approval by the majority of other nodes. Considerations would need to be in place where no nodes can achieve a quorum and thus needs to reset. And it must be ensured that nodes do not vote for more than one node to do work. However I feel it is indeed achievable.
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
I had the idea of dividing work between nodes. This is a simple solution and has some advantages. The advantages being that if a node is taken over by an attacker, the attacker wouldn't have complete access to all records; there would be some functionality for failures down to a single operating node and it is a reasonably simple solution without needing much communication between nodes since each node independently operates on their own records. However, the solution means if a node goes down, some of the records are not spendable.
Aug
19
comment Risks of Network Partitioning When a Split Brain Creates a Security Flaw
Thank you for the answer but your idea creates a single point of failure which is not what I want.
Aug
18
awarded  Student
Aug
18
asked Risks of Network Partitioning When a Split Brain Creates a Security Flaw