5 ms·

Thanks for the writeup and the whitepaper. I find it hard to follow the distinction between decentralised and distributed, especially since all of the points a

Thanks for the writeup and the whitepaper. I find it hard to follow the distinction between decentralised and distributed, especially since all of the points above would apply to your implementation, as well: All the decentralised networks rise and fall with enough political pressure, becasue they all have a weak spot - some form of organizational structure that needs to be kept alive by some entity. In your case (from the whitepaper): > A network map service that publishes information about nodes on the network. The legal entity that will maintain this service will be faced with enough pressure to shut it down once the state in which this entity happens to operate in implements laws that happen to render some of the content in the database illegal. If someone provides a solution to this, that would be groundbreaking. Until today, no such thing exists.

mike_hearn 8y ago
Why not jump on the Corda mailing lists and follow along as we work on these things? The network map is a component I've spent a lot of time thinking about and working on, to make it more and more decentralised over time. Because yes a lot of users flag the same thing you have. Corda has some simple features to mitigate this. For instance nodes have an additional-node-info directory where you can drop NodeInfo files. These act as overlays on the data received from the zone's network map. If the zone operator removes a party from the network map for some reason (maybe a court order, maybe a commercial dispute, or whatever) then you can just drop their NodeInfo file in this directory and it'll be as if they're still in the map. So the idea is that the zone operator acts as a coordinator and provider of advice, but it doesn't have real control - node operators can always override whatever advice it's giving out.

mike_hearn 8y ago

Why not jump on the Corda mailing lists and follow along as we work on these things? The network map is a component I've spent a lot of time thinking about and working on, to make it more and more decentralised over time. Because yes a lot of users flag the same thing you have. Corda has some simple features to mitigate this. For instance nodes have an additional-node-info directory where you can drop NodeInfo files. These act as overlays on the data received from the zone's network map. If the zone operator removes a party from the network map for some reason (maybe a court order, maybe a commercial dispute, or whatever) then you can just drop their NodeInfo file in this directory and it'll be as if they're still in the map. So the idea is that the zone operator acts as a coordinator and provider of advice, but it doesn't have real control - node operators can always override whatever advice it's giving out.