Topic: [old thread] - RISE | DPOS | APPS & DAPPS - page 173. (Read 653326 times)
As for the second ico?
so there is no progress at the moment beside the copied code?
If you have any issues with our code, please PM Me directly.
Will send a PM to you the next time, not to the official RISE account. Thanks.
hmm so.. RISE team... what exactly have you been doing in 1 whole months with 3 fulltime coders.. and millions of dollars?
the only coding was delegate fix.. which we find out now was a copy and paste...
are you guys taking the piss or what? GET moving on some development... are you guys just blowing cocaine up hookers areseholes with the money?
the only coding was delegate fix.. which we find out now was a copy and paste...
are you guys taking the piss or what? GET moving on some development... are you guys just blowing cocaine up hookers areseholes with the money?
Hey ZimSET, this is what we've been working on: http://forum.rise.vision/category/3/blogs Everything you need to know is there!
RiseGal Joins the Rise Team as Community Ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
Thanks for the introduction, McVenture!
Congratulations !
And you expect from regular good news
Thanks for the congrats! I'm excited to be on board the Rise team - and yes, I'll be the one helping to convey good news on a regular basis.
What does community ninja mean??? Any introduction? Big mouth beauty.
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.
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.
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.
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.
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:
Code:
",
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.
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.
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.
There will something good happen if you contribute codes to lisk, and lisk gave you 1700 btc fund, you should thank them.
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.
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:
Code:
",
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.
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.
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.
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.
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:
Code:
",
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.
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.
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.
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:
Code:
",
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.
https://youtu.be/-iZqS5lc-Qg?t=2508
Gives these guys a break. It will take years to build something good.
hmm so.. RISE team... what exactly have you been doing in 1 whole months with 3 fulltime coders.. and millions of dollars?
the only coding was delegate fix.. which we find out now was a copy and paste...
are you guys taking the piss or what? GET moving on some development... are you guys just blowing cocaine up hookers areseholes with the money?
the only coding was delegate fix.. which we find out now was a copy and paste...
are you guys taking the piss or what? GET moving on some development... are you guys just blowing cocaine up hookers areseholes with the money?
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.
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.
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:
Code:
",
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.
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.
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:
Code:
",
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.
RiseGal Joins the Rise Team as Community Ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
Thanks for the introduction, McVenture!
Congratulations !
And you expect from regular good news
Thanks for the congrats! I'm excited to be on board the Rise team - and yes, I'll be the one helping to convey good news on a regular basis.
What does community ninja mean??? Any introduction? Big mouth beauty.
RiseGal Joins the Rise Team as Community Ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
Thanks for the introduction, McVenture!
Congratulations !
And you expect from regular good news
Thanks for the congrats! I'm excited to be on board the Rise team - and yes, I'll be the one helping to convey good news on a regular basis.
Welcome aboard RiseGal!
RiseGal Joins the Rise Team as Community Ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
http://forum.rise.vision/topic/36/risegal-joins-the-rise-team-as-community-ninja
Thanks for the introduction, McVenture!
Congratulations !
And you expect from regular good news
Thanks for the congrats! I'm excited to be on board the Rise team - and yes, I'll be the one helping to convey good news on a regular basis.
So alty, whats the plan here man. Cloak style pump, or just slow dumping for years?
Hey,
Price increase and stability driven by consistant development are what we are aiming for at Rise, we can do the latter because we are well funded which is something that is lacking from many projects.
There is no one single event that we are building up to and relying on because it's "the best thing ever", for Rise there are lots of projects already on the roadmap and each of them may lead to new ones as we mature.
Right now we're working on maximising the transactions per second so we can scale as much as possible without completely changing everything, that was not on the roadmap initially but due to the way we are working we've decided it's better to get a solid foundation in terms of transaction scalibility and stability over rushing out plans on the roadmap then regretting not being able to handle enough tx to deal with demmand as we expand.
From the coding side, I don't see how there can be a massive point of failure that would create a panic selling event (dumping); but if people end up getting crazy with speculation and create a rapid pump scenario that's out of our hands. To reiterate we want to create long term stability over short term volitility.
That sounds fucking boring. Why the hell would I want to invest here? You got mad btc off that ico, lets use that shit to pump rise to da moon, cash out on everyones faces and then move on to the next one. You know. Like back in the day 2014 styles. Braaaaaaaaap!
Nahh for real. I been watching a bit. Im surprised this hustle is still going but then again I know that the long con is what all you scammy devs are doing these days so I assume they'll be a big payday somewhere down the line. I'll hold for now.
Every ICO now feels like a scam!!
Jump to: