DEVsthere is any news ??  We've recently finished the SDK part of the roadmap and provided documentation on them. Unfortunately a lot of time and resources has been spent dealing with the same problems Lisk has encountered with public delegates and forging, therefore the roadmap has been pushed back quite considerably. Progress has been made alongside trying to solve the delegate problem and despite this we were able to get the SDK's complete and can now advance on other parts of the roadmap. A technical run down on where we are, the next steps and how we intend to deal with the delegate issues will be released in the next update from Justin (our lead developer) early next week. |
|
|
|
|
As much as I hate replying to the negative comments sometimes it feels necessary.
Please be assured that the Rise team is here for good and to grow this project into something we can all be proud of.
Updates coming when the developers are confident enough to make them public.
|
|
|
|
Update:Here's a link to our Python SDK. Please do test it out and provide us with feedback. https://github.com/RiseVision/Rise-SDK-PythonPlenty more updates to come as we roll out the entire roadmap over the coming months. New delegate code coming very soon to open up public delegate forging. Good job, but how to use it... Do you have documentation of python sdk. Sure, here it is!  https://github.com/RiseVision/Rise-SDK-Python/wikiJust look for the wiki tab in the Rise github for our docs. |
|
|
|
Update:Here's a link to our Python SDK. Please do test it out and provide us with feedback. https://github.com/RiseVision/Rise-SDK-PythonPlenty more updates to come as we roll out the entire roadmap over the coming months. New delegate code coming very soon to open up public delegate forging.
|
|
|
|
why no commits to GitHub though, strange way of working...check out for example Waves platform GitHub, crazy commits daily. Or is rise seriously just stall development till lisk team pushes updates pffff,
Their devs are missing, alty is missing, they run away with those funds. What a pity.  I posted on Twitter just yesterday, there are new commits coming very soon related to delegate nodes and new SDK's. https://twitter.com/CryptoPioneer/status/776809107445735424Please remember that development takes time to complete properly. |
|
|
|
what's the ICO price?
2061 sats - 0.00002061 BTC per Rise dear Gal, you said 2061 was the ICO price, but you know this is a departure from the truth. At ICO stage you have collected 1716 BTC, emited 100.000.000 coins, which gives only 1716 sats per coin I think 0.00001716 BTC is the real ICO price. Please correct me if i'm wrong. Once you factor in the bonuses you will arrive at 2061 Satoshis  |
|
|
|
How do I actually get on to the platform? I can't find it, and my RISE are on there. Please help.
https://rise.vision/Sign in and you can send your Rise from there. |
|
|
|
ICOOCUNTDOWN wanted 10 BTC for listing RISE on their website. RISE dev refused. hence the retaliation article from icocountdown.
You pay to news editors you are legit. you dont pay you are scam. Unfortunately thats the way it is.
Thats pretty much it, he hasn't even bothered to update with all the infomation we gave him months back since he posted that misleading article. We will keep working away on this project, the developers are working flat out and will continue to do so for a very long time to come. SDK's are being coded now the delegate issue has been resolved and we aim to have new code released to demonstrate this in the next couple of weeks. You guys are all bad.  A hype to lure investors to invest, and icocountdown blackmail you.  You alty also has black history. I don't want to get too drawn into conversation with a shill / noob account that seems to be deliberately typing badly but nevertheless. The hype you are referring to is called "selling our project to potential investors" that's kind of the whole point of a crowdfund, if we didn't sell our crowdfund then it wouldn't be very successful would it? Please remember that there are many team members in Rise that are dedicated to advancing this project... I do have plenty of documented past experience in cryptocurrency which is of benefit however it's hilarious that certain people keep talking like I'm the only person here. Check our team profile to see we have lots of team members and please do ask questions on our forum for the upcoming question and answer session (first week of September).
http://forum.rise.vision/topic/33/q-and-a-event-with-rise-developers-in-september-submit-your-questions-here/2 |
|
|
|
ICOOCUNTDOWN wanted 10 BTC for listing RISE on their website. RISE dev refused. hence the retaliation article from icocountdown.
You pay to news editors you are legit. you dont pay you are scam. Unfortunately thats the way it is.
Thats pretty much it, he hasn't even bothered to update with all the infomation we gave him months back since he posted that misleading article. We will keep working away on this project, the developers are working flat out and will continue to do so for a very long time to come. SDK's are being coded now the delegate issue has been resolved and we aim to have new code released to demonstrate this in the next couple of weeks. |
|
|
|
This is actually a carefully planned scam. This way you can funnel money from the non-profit organization into the other company and have clean funds and use it for what you wish, legally. quite crafty, this guy is basically moolah 2.0
Absolute rubbish...Just wait to see what we deliver over the coming weeks and months. |
|
|
|
Risehasfallen, how much btc did you lose in rise project? I see you daily post here, i think you have been lost a lot here.
actually only newbie gamblers lost their money, who have sold less than ico price. Risehasfallen is so called 1-BTC-whale. He wanted instant 300% return but it did not happen. So he withdraw his funds accepting 50% loss and reinvested all in Oracle coin Now it is obvious he lost all his money and he is blaming Rise team and community for his irrational behavior. We have a forum away from the trolls here at forum.rise.visionSDK development is going to get underway very soon and we'll post updates on the status of that on a regular basis. Please remember it's only been a few weeks since we've had the new full time developers on board. and what have these full time developers done in a few weeks? claim to have fixed the delegate system but actually just copied the fix from LISK, what are they actually doing? seriously? We've posted updates reguarly explaining what the developers have been doing but in short the first couple of weeks was spent getting to grips with the code then the last week testing like crazy the new implentations. |
|
|
|
Risehasfallen, how much btc did you lose in rise project? I see you daily post here, i think you have been lost a lot here.
actually only newbie gamblers lost their money, who have sold less than ico price. Risehasfallen is so called 1-BTC-whale. He wanted instant 300% return but it did not happen. So he withdraw his funds accepting 50% loss and reinvested all in Oracle coin Now it is obvious he lost all his money and he is blaming Rise team and community for his irrational behavior. We have a forum away from the trolls here at forum.rise.visionSDK development is going to get underway very soon and we'll post updates on the status of that on a regular basis. Please remember it's only been a few weeks since we've had the new full time developers on board. |
|
|
|
From our lead developer in teamchat just now. [11:17 PM] Justin Donnaruma: Just to point something out, here is the diff statistics between current Development branch of Lisk and rise-core /code 745 files changed, 93717 insertions(+), 424976 deletions(-) 745 files changed, 93717 insertions(+), 424976 deletions(-) |
|
|
|
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. |
|
|
|
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. |
|
|
|
how soon we will see some progress? do you follow your roadmap? or have upgraded version of it?
Dev team has been expanding (non-anonymously) and has posted updates rather frequently. I know this but i don't see anything new and want to see new roadmap with new targets because previous roadmap is wasted in time now Hi, Sorry for the delay in getting the new roadmap out (due to delegate forking issues), we'll have a new one for public viewing released this week! |
|
|
|
Thanks for supporting Rise with this! I would upvote you but never got round to creating an account on steemit, however you'll get my vote to be a delegate for Rise once we have public delegates open again. |
|
|
|
Hi all, I configured port 4242 for the rise wallet. The Wallet didn't honor the setting from the config and I found these lines in the app.js which override the config.json. is this the intended behavior ? if (process.env.NODE_ENV != 'production') {
appConfig.port = 4444
} else
if (program.port) {
appConfig.port = program.port;
}
if (program.address) {
appConfig.address = program.address;
}
if (process.env.NODE_ENV != 'production') {
appConfig.port = 4444
}
regards Did you end up with a working wallet on different ports? Edit: clearly it's fine based on your next post has anyone seen https://LiskDice.com ? if the RISE community supports them I'm sure they'd port the Dapp to work with RISE when it's finished! If enough people want to get a dice game going for Rise I'm sure we can get that made... for now, afaik there is one available on Yobit. |
|
|
|
|
Show Posts
