The last few weeks have been very informative on how DPoS works under stress....I set up the rocket delegates to replace the non-performing delegates - Cryptikit and Olivier's help made this much, much easier, 48 new delegates in all....At Max's suggestion, Boris added the ability for a delegate to see which accounts voted for him to the Crypti API. This, along with the new Lisk forging rewards, opens up the possibility for delegates to do profit sharing with those who vote for him. What I have in mind is how I originally thought DPoS would operate with Bitshares and should have run with Crypti. I would like to offer to split the delegate earnings with the people who vote for my delegates based on how much they have in the Lisk accounts they vote from on a running basis and how much they dilute their votes by voting for other delegates. So this would be truly a PoS type system where stake holders receive a return on their holdings with a portion going to the delegates they choose to represent them. This will also incentivize people to hold Lisk since it can offer them a return.
Mike, you've done us all a favor, more so than most people realize...so thanks!
Did you have any gotchas with the latest version of Crypti Docker? My node was forging great but it wouldn't display the client at Port 8040. So I took it offline to reload it and never got it back up. Every time I loaded my local IP address in the whitelist area of the config.json file, but when I flipped the forging switch in the Port 8040 client it would say I was coming from an unauthorized IP. I finally gave up when I saw your massive effort come online. I guess I'm done forging Crypti.
I did not realize we could do forging co-ops like you suggest. As you say, this will become very popular and attract votes. But then...how does the forger earn his server fees back if he has to give them out to those who voted for him?
DPoS is a great system philosophically and even theoretically. But it never achieved true, actual operation at Crypti. Lisk is going to have its own challenges with DPos when the time comes, that will be fascinating to watch.
Hey, folks, I'm MalReynolds. When the time comes, I would appreciate your vote to become a DPoS Active Delegate of Lisk.
I'm using Cryptikit on Vultr servers,
https://github.com/crypti/cryptikit . This makes it a lot easier. Once Cryptikit is installed on a server, installation is very automated on any other servers you create, using that initial Cryptikit as a console. Adding delegates after setting up nodes is also simple - just command "rake start_forging servers=2" and you enter the passphrases for the delegates you want to add to that node, one at a time at the prompts. There is also a config.yml file which can be edited with nano or offline with notepad++ but I find it more fool proof to use the prompts.
Olivier said he is adding more features to it, so I expect the Lisk version (Liskit?) to be able to do even more.
On delegates earning while paying rewards to their voters, the operator can retain a portion of the proceeds. The market will determine the rates operators can charge, along with the reputation and reliability of the delegate operator.
I have a fresh new Bitseed unit to try Lisk on as well,
https://bitseed.org/ . We currently ship units with up to 2 Tb storage, looking at 3 Tb for use as distributed storage nodes, also have a lite version with no hard drive. We're looking at the distributed storage market, but waiting for the user interface to improve.