BitShares Forum

Main => General Discussion => Topic started by: testz on May 26, 2014, 09:48:14 am

Title: BTT: Which PoS approach will win out?
Post by: testz on May 26, 2014, 09:48:14 am
Vote here:
https://bitcointalk.org/index.php?topic=584703.0

 :)
Title: Re: BTT: Which PoS approach will win out?
Post by: liondani on May 26, 2014, 04:48:21 pm
Vote here:
https://bitcointalk.org/index.php?topic=584703.0

 :)

We need about 20 more votes to win place one!
Visit the poll guys  ;)
Title: Re: BTT: Which PoS approach will win out?
Post by: onceuponatime on May 26, 2014, 11:28:06 pm
Vote here:
https://bitcointalk.org/index.php?topic=584703.0

 :)

We need about 20 more votes to win place one!
Visit the poll guys  ;)

Voted.
Title: Re: BTT: Which PoS approach will win out?
Post by: CLains on May 27, 2014, 01:01:26 am
Clever. I like it.  +5%
Title: Re: BTT: Which PoS approach will win out?
Post by: xeroc on May 27, 2014, 06:37:32 am
I have the feeling most btt users have outdated information about DPOS ..
Can we please collect all infos about DPOS for a newsletter article to educate them?

Anyway: I have the feeling the DPOS stands between NXT and ripple, technologically. Is that feeling correct?
Title: Re: BTT: Which PoS approach will win out?
Post by: santaclause102 on May 27, 2014, 08:20:47 am
I have the feeling most btt users have outdated information about DPOS ..
Can we please collect all infos about DPOS for a newsletter article to educate them?

Anyway: I have the feeling the DPOS stands between NXT and ripple, technologically. Is that feeling correct?

Can you say that DPOS is exactly like ripple except for the number of nodes/delegates and the process by which they are selected (voting vs. unique node list)?
Title: Re: BTT: Which PoS approach will win out?
Post by: CLains on May 27, 2014, 12:18:21 pm
From: https://bitcointalk.org/index.php?topic=584703.0

  • Bitshares  (DPoS - http://bitshares.org/security/delegated-proof-of-stake.php)

Link broken. Which also means link in https://bitcointalk.org/index.php?topic=558316.0 is broken.