Talk:Consensus Process (voting pools) - Revision history

Justusranvier at 12:44, 22 September 2014

2014-09-22T12:44:57Z

Larshesel: Which wallet issues the transaction?

2014-09-22T12:14:45Z

Which wallet issues the transaction?

Justusranvier at 14:41, 16 September 2014

2014-09-16T14:41:07Z

Larshesel at 14:34, 16 September 2014

2014-09-16T14:34:42Z

Justusranvier at 14:18, 16 September 2014

2014-09-16T14:18:19Z

Larshesel: Created page with "In computer science anything based on consensus in a distributed network is an incredibly complicated thing to implement. There are some tools out there like zookeeper (never ..."

2014-09-16T13:03:15Z

Created page with "In computer science anything based on consensus in a distributed network is an incredibly complicated thing to implement. There are some tools out there like zookeeper (never ..."

New page

In computer science anything based on consensus in a distributed network is an incredibly complicated thing to implement. There are some tools out there like zookeeper (never used it) which I understand can be used for this kind of thing.

Something to keep in mind is, that roughly speaking you cannot get consensus, (two generals problem etc), but you can get consensus with some degree of certainty.

Would there be any way where we could change this such that we do not need concensus?

Why do the peers have to agree on the addresses every 5 minutes?

← Older revision		Revision as of 12:44, 22 September 2014
Line 26:		Line 26:

	So if each audit-server gets this list of withdrawals. And after they have all exchanged signatures and gotten consensus, which one of the wallets does actually issue a transaction to the blockchain? Do they all do that?		So if each audit-server gets this list of withdrawals. And after they have all exchanged signatures and gotten consensus, which one of the wallets does actually issue a transaction to the blockchain? Do they all do that?
		+
		+	<hr>
		+	[[User:Justusranvier\|Justusranvier]] ([[User talk:Justusranvier\|talk]])
		+
		+	All wallets process all transactions and broadcast them to the blockchain independently of every other wallet.

← Older revision		Revision as of 12:14, 22 September 2014
Line 20:		Line 20:

	Yes, but it will probably be until after more of the auditor is documented before this page is filled out.		Yes, but it will probably be until after more of the auditor is documented before this page is filled out.
		+
		+	<hr>
		+	Lars:
		+	bullet 3: A list of valid withdrawals to be processed, sorted in TBD order, which may be an empty list.
		+
		+	So if each audit-server gets this list of withdrawals. And after they have all exchanged signatures and gotten consensus, which one of the wallets does actually issue a transaction to the blockchain? Do they all do that?

← Older revision		Revision as of 14:41, 16 September 2014
Line 16:		Line 16:

	Good to know the consensus has been scoped to be as minimal as possible. Can we add a reference to the algorithm we're going to use?		Good to know the consensus has been scoped to be as minimal as possible. Can we add a reference to the algorithm we're going to use?
		+
		+	<hr>
		+
		+	Yes, but it will probably be until after more of the auditor is documented before this page is filled out.

← Older revision		Revision as of 14:34, 16 September 2014
Line 12:		Line 12:

	As far as the algorithm, we'll be using a system similar to what Ripple uses. Last year Chris was contracted to produce a custom cryptocurrency and the algorithm he used for them is compatible with what we need for voting pools.		As far as the algorithm, we'll be using a system similar to what Ripple uses. Last year Chris was contracted to produce a custom cryptocurrency and the algorithm he used for them is compatible with what we need for voting pools.
		+
		+	<hr>
		+
		+	Good to know the consensus has been scoped to be as minimal as possible. Can we add a reference to the algorithm we're going to use?

← Older revision		Revision as of 14:18, 16 September 2014
Line 6:		Line 6:

	Why do the peers have to agree on the addresses every 5 minutes?		Why do the peers have to agree on the addresses every 5 minutes?
		+
		+	<hr>
		+
		+	We need consensus because each member of the voting pool to take the same actions. We're tried to restrict the scope of consensus to the bare minimum possible in order to make the withdrawal process work.
		+
		+	As far as the algorithm, we'll be using a system similar to what Ripple uses. Last year Chris was contracted to produce a custom cryptocurrency and the algorithm he used for them is compatible with what we need for voting pools.