Dear RISE Team,
We at Lisk are big fans of open source development. We after all forked the Crypti code which used The MIT License and therefore we are bound to the same license (we would have chosen the same one anyway). As a fork of Lisk you are under the same license as well.
There is not really a lot going on in your
core development branch on BitBucket. However, there was one large update called "Update for node syncing".
I see that you copied our code 1-for-1 without leaving any kind of credits, honours, or "copyright" to the Lisk team. This is mandatory with The MIT License and we ask you to please do so.
Furthermore, in order to support your project a little bit I need to say that a copy & paste you did makes zero sense. (There is theoretically another one which makes no sense, but I'm not the best developer so I'm not sure.)
The changes you did in the constants.js regarding voteExceptions, these votes never happened on the RISE network. Only on the Lisk network, so there is zero need for you to have these 3 votes inside there. Additionally, when you copied it you added an error. There is the following part missing:
",
Compare:
RISE /
LiskI'm hoping to see the deserved credits for the Lisk soon on BitBucket, especially for the database migration system Oliver put a lot of work into.
You collected a huge amount of money (probably 3x as much as Crypti which had good development going on for nearly 2 years) and I expect that you can contribute something on your own, so we at Lisk can copy it too.

PS: I would have kept this private, but you were not responding to my private message.
Thank you guys! Good luck with your efforts.
Max thanks for dropping by and appologies you didn't get a reply to your pm sooner.
For the update related to node syncing we'll absolutely get the credit listed asap where it's due.
In terms of not updating bitbucket with our own changes it's because we'd like to make sure on our devnet that we have stability prior to making changes public.
So atm we've been privately testing code for the delegate issue and have been experimenting with obtaining the maximum number of transactions per second per node before it breaks / forks.
Justin will explain a bit more in detail of the latest results but afaik we were able to obtain about 150 tx/s.
To go higher we may need to consider looking at a kind of "lightening network" solution.