Rise Updated Details
Rise Introductory Video
Rise Currency and Applications Everywhere.
Our number one goal is to make Rise accessible to everybody. This means we're putting massive effort into making our web interface scale across all devices. By keeping within cryptocurrency core values, you'll be able to transfer value, build applications, trade and even invest via an easy to use and decentralized UI.
We want to change the way you handle your money, and your wealth.
We have put a lot of thought into what we want RISE to be. We are going to provide tools to manage your RISE, your Bitcoins, and your investments with those currencies. Manage your CryptoCurrencies in one place, and in the future, pay your bills, pay your rent, or even buy your house. One of our first major Application projects is Project Acre, a real estate investment platform that will enable you to invest in a building project, and get a percent, based on your investment, of the profits. More details will be coming after our ICO
• Block Time: 30 seconds
• Round Time: ~17 minutes
• Confirmations for Final Transaction: 6-10
• Supply: 100 million Rise
• DPoS reward 15 Rise forged per block
• Rise's official ticker: RISE
The total coin supply is 100 milllion.
88 million coins will be distributed to ICO participants
12 million coins will be reserved for:
• 1 million for pre-ICO bounties.
• 2 million for post-ICO bounties as well as strategical partners and backers.
• 9 million to be withheld by the development team.
We are designing systems that will enable spending RISE just like traditional fiat currency. Pay your bills, buy food, and send money to your friends and family with RISE
We are a group of highly talented enthuiasts, but we don't know everything . We will be building a foundation, post ICO, to get the community involved. Voting on features we need, and where the foundation will go from the initial launch will be the job of the community.
Digital and Physical
We are working to bridge the gap between physical and virtual. RISE is our first step towards this goal. Ultimately, we want you to be able to pay for both Digital and Physical goods with RISE, as if it were your country's FIAT.
Upcoming Video Release of Dev Team
As some of you know we have received requests from within the RISE community
to create a video that introduces all members of our development team. The video shoot is
scheduled for Monday and we should have the video ready for you within a few days following. Aside from an introduction our developers will cover several topics such as the new Rise code base
currently under development, short-term and long-term vision for Rise and future applications.
You’ll also get a peak behind the scenes in terms of the development tools, configuration and
setup they use on a daily basis to build the RISE platform. Stay tuned. .
Rise Vision Foundation Dev Team Introduction Video
Let us take you behind the scenes of the Rise Vision Foundation. The following video presentation includes:
- Lead Developer Justin Donnaruma taking you on a tour of the current office space in Lewiston, Maine
- Introduction of the Rise developers team (Justin Donnaruma, Richard Hooper, Nathanael Burchill)
- Get briefed in the Rise War Room!
- Learn details about the new Rise Code Base
Coming up next week
We’ll be releasing a blog post giving detailed insight into the Developer’s screen setups, frameworks and tools used daily for developing the RISE platform.
Those who have watched the video we released last week may have noticed a revealing of a few new specifications for RISE 2.0 (the new code base currently under development). We already discussed the maximum TPS last week. Today I’d like to highlight another aspect that was mentioned in the video namely the changes on the cryptography side of things.Lisk uses SHA-256, which is a 256-bit version of SHA-2. Instead of staying with SHA-2, we are jumping to the current NIST standard instead. There isn’t anything technically “wrong” with SHA-2, other than that it is designed very similarly to SHA-1, which is susceptible to numerous technical flaws. SHA-2 doesn’t appear to be susceptible to the same flaws, however, much research over the past 10 years has been devoted to building SHA-3, instead of proofing SHA-2, so its holes may just not be known.So the benefit for RISE to go with SHA-3 is a potentially more secure platform. Another advantage of SHA-3 is that the message size is unlimited as compared to the 2^64 - 1 bits in SHA-2. Ofcourse 2^64 -1 bits is a LOT of data but there are scenarios in which this may be exceeded on our platform and where SHA-3’s unlimited message size could become a benefit. Our developers are still busy engineering parts of the Rise architecture so I can’t give much more on the specifics of this for now, but I’ll continue to update you as development is moving forward.
<Dev Team> Tools and Workstation configurations
Dev and Project Management tools
We use quite a few tools on a daily basis, some shared, some not.
- Atom - Code Editor
- Wakatime - Code / Terminal Time tracking
- Git / Github - Source code management / Public issue tracker
- Jira - Project Management / Portfolio Management
- Confluence - Internal Wiki / Product documentation
- Google Apps - Email / Collaborative documents
- Skype - Communication with former colleagues and friends
- Hipchat - Communication between teammates (Adoption in progress)
- Messages - Soon to be phased out communication between teammates
A few other tools we use, but have varied applications for, is Terminal (I use iTerm with ZSH, Nathan uses Terminal with ZSH, and Richard used Terminal with BASH.) Nathan and I predominately stick with git on the command line, while Richard uses the Github GUI. I also tend to live in Mail on my Mac, while Richard and Nathan use Gmail in Chrome.
Depending on the code in use, I also use a few more advanced debugging and editing tools for code, like Intellij IDE, and Meteor Toys.
For browsers, I live in Safari, while both Richard and Nathan use Chrome (Although I have been seriously contemplating switching to Chrome).
For Static site editing, I use C9.io, connected to Github directly so I can work collaboratively on code with my marketing team.
We three all have MacBook Pros connected to external displays.
I have 3 27" displays, 2 connected in Portrait, and 1 in landscape, and I use an external wireless keyboard and trackpad.
Richard has 2 27" displays, connected in landscape, and uses the laptop screen, keyboard and trackpad.
Nathan uses a 34" Ultrawide by LG, and his laptop screen, keyboard and trackpad.
Justin’s Tool List:
- UI Theme : One Dark
- Syntax Theme : One Dark
- ZSH (Oh-My-ZSH with significant customization)
- PyCharm Pro
Richard’s Tool List:
- atom add-ons
- atom theme
- UI - Atom Soda Dark
- Syntax - One Dark
- atom add-ons
- Project Tracking
- Messages (Built in Apple messenger)
- Lots of terminal windows
Nathan’s Tool List :
*UI: Atom Material
- Syntax: Atom Material Dark
- Font: FiraCode
- iTerm2 with zsh and Bullet Train
- Stack Overflow
- Github Desktop
Nathan and his Workstation
Richard and his Workstation
Rise Vision - Q&A with the Developers
Rise Development Update
Most of the architecture for Rise 2.0 is now completed. The team is still working on Side-chains and are then going to break down the architecture into specified user stories that they will push over to Github. At that point you will have a fairly accurate way to track progress on the new code base.
There is a basic Proof of Concept nearing completion, the team is working on the peering functions now and once that is complete they will be running some testing on speed to get a real-world measurement of what the network can handle.
More updates coming soon. Stay tuned.
RISE DEV TEAM UPDATE - JAN 24, 2017
And it’s time for the promised update. The dev team has begun to translate the completed Rise 2.0 architecture into user stories. This process is ongoing. Justin and Richard are writing the user stories and Nathan is working on turning these into code.
User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality.
What exactly is a user story?
User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
They typically follow a simple template: As a <type of user>, I want <some goal> so that <some reason>.
To give an example, here is an actual user story for Rise 2.0: “As a node i should be able to view the current blocks forging list and the prior forging delegates. Acceptance Requirements: Must see the function that will gather this information from the network config collection and collect into an object or array for viewing.”
The Rise Dev Team pushes each user story to Github so the community can look over their shoulders and follow exactly what is being worked on.
There are currently 49 user stories to be viewed right here: https://github.com/RiseVision/rise-core/issues
Rise and Chipz! Development Update
We have a fairly big announcement. We are in the process of restoring investor confidence and part of that process is to reward our current Rise token holders, as well as getting delegates forging as soon as possible. Even though we are currently on this path, it’s only fair to mention that we had hit a bumpy road.
Previously, we have been pulling teeth, trying to get updates from our development team. It had gotten to a point where we were instructed to formulate emails as the “method” to reach them. Days had turned into weeks and even after many promises of daily updates, we still didn’t see progress. Many of you guys had stressed your concern as well.
We were then told by Justin that his development team needed more funds to continue the project. After close examination, and to prevent our funds from becoming more depleted with little to show for it, we discontinued funds to Don’t Panic (Justin’s business). As a result, Don’t Panic including our co-founder Justin walked away from the project.
However, we have acted quickly and are working with another developer right now. We will let everyone know who this is in an upcoming announcement. All Rise 2.0 work so far has been transferred to our new developer. Before we move further on that, we have decided that we will push out Rise Classic by cloning Lisk to get delegates forging and earning rewards ASAP.
We had relied on Justin’s promises that Rise 2.0 code base was going to be “easy enough” for him and we counted on his insight, such as promising a working prototype by December. It was moved to January, and then to February. And nothing came to fruition. “More funds” was never part of our original agreement with him.
So we have decided to move quickly and get Lisk cloned and delegates forging (Rise Classic) while Rise 2.0 is looked at by our hired new developers. We don’t want to waste any more time on this. In addition, we will be rewarding our token holders by providing them with Chipz which is explained below.
We are in negotiations with an online casino software supplier with the aim to launch a fully operational online gaming platform that will operate using Chipz tokens as the currency. Rise holders will receive Chipz tokens based on their holdings. The value of Chipz will be determined by the free market as soon as it hits an exchange. In order to use the casino players will be required to purchase Chipz tokens… Chipz will be available for purchase direct from the casino converted at the current market price or from an exchange. As soon as fiat gateways are available on the Waves network the casino will begin accepting fiat tokens that can be used to instantly purchase chipz for use in the casino.
More details to be revealed as we advance the Chipz project.
McVenture and myself will check in regularly this week here at the forums to make sure we answer any questions you guys have. Thanks. And let’s get this project rockin’. Good things to come!