Topic: [old thread] - RISE | DPOS | APPS & DAPPS - page 173. (Read 653289 times)

Copy paste is very #simple money for rise team. We hope you can do something original code.

Actually, we are a Lisk fork. We are in the process of revising code and have been working diligently. We'll keep you posted as things develop!

damn,
every time i come in this topic i see things getting worse to rise team... so now they do a copy and paste and dont even revise the code? lol.

Thanks for the question! Everything is at this link: http://forum.rise.vision/category/3/blogs

As for the second ico?

so there is no progress at the moment beside the copied code?

Will send a PM to you the next time, not to the official RISE account. Thanks.

Hey ZimSET, this is what we've been working on: http://forum.rise.vision/category/3/blogs Everything you need to know is there!

It means I'm always here, reading the comments! It also means that I'm going to be the one interacting with you guys during the day, answering questions and sharing news.

Thanks for the warning, but who said I was sane in the first place?  I'm excited to talk RISE with everyone, so thanks for the warm welcome!

Welcome RiseGal, word of warning though, you will not stay sane long in bitcointalk, it's just a flood of trolls one day after another.

There will something good happen if you contribute codes to lisk, and lisk gave you 1700 btc fund, you should thank them.

Alty is correct with everything he said.

Max, I never received a PM from you directly. If you have any issues with our code, please PM Me directly.

I'll update the commit with the node syncing items to reflect the pull from Lisk, and properly attribute to Oliver and Lisk itself, and we did notice a few pieces of code that we are not using, and will be cleaning it up prior to releasing to production.

We will definitely be pushing some code changes up that you and Oliver can of course feel free to swipe. Just follow our forum (forum.rise.vision) for my dev updates.

Justin D.

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.

https://youtu.be/-iZqS5lc-Qg?t=2508

Gives these guys a break. It will take years to build something good.

ROFL    Maybe they enjoy the show in the strip club, smoke weeds, and have sex with the new community ninja girl?     

Luckily I dumped this shit with losses earlier, not now. And another coin made me a fortune, I have covered my losses in this shit RISE.

Wow, Lisk God Max is coming here. Yeah you are right, I hope Rise can do innovation and you can copy from rise.  

It's funny Rise became a copy & paste driven development.  Don't rely too much on the work of others Rise team.

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 / Lisk


I'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.