HN user

swamp12

19 karma

[ my public key: https://keybase.io/jed; my proof: https://keybase.io/jed/sigs/IAUzv3A8uI7ZOEmfyjhYfcgA9HRibLlSnPcJ6EjWYns ]

Posts0
Comments12
View on HN
No posts found.

The Stellar network did fork when we running on a fork of legacy software. Since then, we have rebuilt the entire consensus system using a completely different consensus system. The underlying consensus system was designed by Prof. David Mazieres, head of Stanford University's Secure Computing group - you can read the white paper here: https://www.stellar.org/developers/learn/concepts/scp.html A completely new implementation of SCP in the form of stellar-core was completed earlier this year. You can read about it here: http://graydon.livejournal.com/227874.html

This is an example of an approach to smart contracts that uses the Stellar model which keeps the bulk of the logic outside of the system so only people that are interested need do any processing. This should make it more scalable.

I haven't thought through it yet but I think the most common case would actually be 1 directional. Curious if people agree or have another opinion?

Yes a node in the Stellar network doesn't need to know all the other nodes in the whole network and adding and removing nodes is a fluid and open process but yes there must be some transitive overlap in the quorum slices people choose. The details would be better explained in the paper.

All the coins(lumens) exist when the network starts up. The Stellar Foundation is distributing them in the following way: https://www.stellar.org/about/mandate/#Stellar_distribution

Oh I think it was misunderstood. The full quote is: "Byzantine agreement guarantees distributed consensus despite the Byzantine failure of participants. However, it requires unanimous agreement on system membership by all participants. Each node in the network must be known and verified ahead of time." It is comparing SCP to Byzantine agreement protocols like paxos.

As in Stellar doesn't have this requirement. Here is the white paper: https://www.stellar.org/papers/stellar-consensus-protocol.pd...

(Jed from stellar here) The fork you are describing occurred in the previous protocol when all the nodes had the same UNL; the failure had everything to do with that previous protocol's response to overloading (it diverges based on timeouts, rather than getting stuck, and discards the losing fork on healing) and nothing to do with trust topology. So it didn't have anything to do with improperly set up trust.

In SCP the topology is public and conveyed with each consensus packet. So people will be able to tell when the graph is vulnerable.

Improving the definition of topology requirements for correct consensus is, far from being 'ignored', exactly what Mazieres has been working on all this time. And as you admit, those requirements have now been formalized and the information to check them is conveyed in the consensus packets; they are just not trivial to check by hand, and we have not yet implemented a check for them in stellar-core (this will be forthcoming, see roadmap).

Well you can turn the feature off if you want. You can also set the "quality" of a given issuer. This means that you could apply a discount to the mtgox credit so it would swap out at a discount. But really it will probably just be turned off by default

Sorry that wasn't clear. What she means is the amount given to each person. We are still and always will be committed to giving away the total 95B stellars. I just edited her post to clarify what we were trying to say.

Stellar 12 years ago

Weird. I'm one of the Stellar devs -- could you email your stellar username to jed@stellar.org? Thanks!