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.

    Ubiquitous Currency

    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

    Community-driven Foundation

    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.









    Rise Vision Foundation Wiki

    Rise WhitePaper:

  • 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.

  • SHA-3 encryption

    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.

    Shared Tools:

    • 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:

    • Atom
      • ansible-galaxy
      • ansible-snippets
      • atom-beautify
      • color-picker
      • json-colorer
      • language-markdown
      • markdown-preview-plus
      • node-debugger
      • pretty-json
      • wakatime
      • webbox-color
      • UI Theme : One Dark
      • Syntax Theme : One Dark
    • iTerm
    • ZSH (Oh-My-ZSH with significant customization)
    • Webstorm
    • PyCharm Pro
    • RubyMine
    • Intellij
    • Slack
    • Hipchat
    • Skype
    • Lanscan
    • Postico
    • Paw
    • MongoHub

    Richard’s Tool List:

    • Atom
      • atom add-ons
        • atom-beautify
        • highlight-selected
        • todo-show
        • wakatime
      • atom theme
        • UI - Atom Soda Dark
        • Syntax - One Dark
          *GitHub Desktop
    • Project Tracking
      • Jira
      • GitHub
    • Messengers
      • Skype
      • Hipchat
      • Messages (Built in Apple messenger)
    • StackOverflow
    • Lots of terminal windows

    Nathan’s Tool List :

    • Atom
      • Packages
        • api-docs
        • atom-ternjs
        • tern-meteor
        • docblockr
        • file-icons
        • linter-eslint
        • nuclide
        • highlight-selected
        • merge-conflicts
        • minimap
        • minimap-bookmarks
        • minimap-find-and-replace
        • minimap-highlight-selected
        • minimap-pigments
        • pigments
        • simple-drag-drop-text
        • split-diff
        • todo-show
        • wakatime
      • Theme
        *UI: Atom Material
        • Syntax: Atom Material Dark
        • Font: FiraCode
    • iTerm2 with zsh and Bullet Train
    • Stack Overflow
    • MongoHub
    • Messages
    • Skype
    • Hipchat
    • Github
    • Github Desktop
    • Jira

    Nathan and his Workstation

    Richard and his Workstation

    Justin’s 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.


    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

    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!




  • RISE Status Update - February 27, 2017

    This last week has been very eventful for Rise and has left some people uncertain about the status. This post brings all the details together that were released spread out over a myriad of posts.

    • Justin (co-founder and lead developer of Rise) is no longer working on the Rise 2.0 platform, including his employees Nathan and Richard. The Rise team was dissatisfied with the lack of progress and denied Justin’s demand for more funds to continue developing.
    • Rise team is working on solidifying a contract to get Rise cloned to the latest LSK code
    • Putting Rise forging into the hands of the community as soon as possible is #1 priority
    • Rise 2.0 is not off the table, The ICO promise of adding multi-code language support and easy-to-use tools for buildings dapps will still be pursued.
    • Rise development funds were temporarily moved to Bittrex. The account was frozen by Bittrex as this is their standard security mechanism. The account is being verified in the next few days to be unfrozen and the funds will be moved to a permanent Rise wallet address for everyone to see. The Rise address will be announced here.
    • Rise team is working to reward Rise holders through the Chipz Project. Chipz was announced earlier this week and is in the beginning stages. Rise holders will be the beneficiaries of the Chipz airdrop. More details will be shared as it becomes available.
    • In a few days from now we will announce a competition for loyal Rise supporters with a total prize pot of 1 Million Rise. Stay tuned.

  • Rise Mainnet - Upcoming Launch Overview

    The new Rise mainnet is estimated to go live tentatively within the next few weeks, so it’s time to go over a quick list of things that are planned for this launch so far. More details for each listed item will follow as we’re drawing nearer to the time of launch.

    • The launch facilitates the transition Rise is making from Lisk to Ark code base.
    • It includes a coin swap via Bittrex
    • Most coins forged by Rise Team will be burned, which will help Rise value.
    • Public Delegates will take over forging of Rise to secure the blockchain and earn rewards.
    • Public Delegates get a fresh start with year-1 interest rates (see OP for full reward schedule)
    • Release of a full-featured Rise desktop wallet for Windows, Linux and MacOS
    • New Block Explorer
    • Rise Pool
    • New main Rise website (now in final stages of development)
    • Rise Forum (NodeBB based) upgrade

  • RISE Newsletter - Technology Developments, Wallet , Exchange Updates, Website Developments & Many More 

    Hello RISE community,

    As we are at the end of March, it is time to recap activities the team have been involved in this month. We hope this allows you to catch up with the progress we have made.

    Technology Developments

    We are very excited to share we are preparing for our core mainnet release of the rewritten and tested TypeScript code base in April. The magnitude of this milestone should be celebrated and is a culmination of months of hard work by the Development team. Further announcements will be made in due course to inform and showcase this achievement in RISE development.

    Delegate Update for Typescript

    As we prepare for the imminent release of our new TypeScript core to mainnet there will be some tasks if you run a node. Please update your nodes via `./rise_manager.bash update_client` as this update is mandatory for the upcoming TypeScript core release and further instructions may be requested in the #delegates channel in Slack.

    Wallet Updates

    We released a new version of the RISE desktop wallet as users mentioned they were having issues with this. If you use the desktop wallet please update it, you can find the new release here: https://github.com/RiseVision/rise-desktop/releases. If you use a Mac, please bear with us and use the web wallet for the time being. Thank you for your patience.

    TypeScript Updates

    A big thank you to the testers who completed the TypeScript testing program launched in January for running testnet nodes successfully and supporting our development team. We are currently arranging bounties for your dedication to the progress of RISE development. Please look out for further bounties which will be publicised on our new website.

    Furthermore, RISE is now on the ‘Friends of TypeScript’ page of the TypeScript website. This is an effort for RISE to integrate into the TypeScript community and be recognised together with some of the larger web development projects. If you are not sure what TypeScript is, it is an open source programming language developed and maintained by Microsoft and is known as ‘JavaScript that scales’.

    Friends of TypeScript: https://www.typescriptlang.org/community/friends.html

    Exchange Update

    We understand how anxious everyone is with regards to working with exchanges. As discussed previously, we need to maintain a balance with discussing listing conversations to ensure we do not jeopardise any partnerships. We have engaged multiple exchanges that we believe would be a good fit for RISE. Without going into each individual process, we can say there are a multitude of requirements to be considered, they can include listing fees, legal documents, volume and ERC20/non-ERC20 integrations. We will conclude this with mentioning that RISE is in a very unique position, being a non-ERC20 with low volume in the current climate is lengthening discussions. We will keep working hard on this and we hope to share more progress soon.

    In the meantime, check out this awesome blog post by our friends at OpenLedger DEX, a peer to peer platform based on Bitshares technology: https://steemit.com/openledger/@bloggersclub/rise-traded-on-openledger-dex. This month they opened the gateway for RISE. You can also follow them on Twitter at @OpenLedgerDC.

    RISE is now on Openledger DEX: https://openledger.io/

    Team Developments

    As discussed previously, it is imperative that RISE can attract great development and commercial talent for our continued growth. Therefore, I am delighted to say we have a new developer to add to the team, a further announcement on this hire will be shared in the first half of April.

    We are also expanding our community team, we will announce these community managers shortly after their their appointment is confirmed.

    Website Developments

    In March a considerable amount of time was spent working with our partnered creative design team on fine tuning the new website. The concept behind the redesign was to drive a more focused, concise message on the mission of RISE and how developers would engage with the project. This rationale led us to recreate and reorganise content for the website. We want our new website to be an open invitation for developers to access our developer tools and learn about the RISE DPOS blockchain.

    Ask Me Anything

    Many community members have asked for an ‘Asked Me Anything’. We aim for release of our mainnet and website first, after these milestones we will communicate the official process for our AMA for April, likely a subreddit. We look forward to answering your questions and gleaning feedback from dedicated community members.

    RISE Monthly Statistics

    The below chart highlights the number and percentage of RISE voted to elect the 101 Delegates and the 102-202 nodes securing the network and non-voting RISE.

    Total RISE Supply 122,542,070. Chart generated 31st March 2018.

    To close on this month, we thank our great community for their patience and encouragement during this time. We are all working hard every day to progress the vision of RISE.

    Make sure you follow us on Facebook, Twitter, Reddit and Linkedin for latest news.

    — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

    Disclaimer: RISE is not a security, and token holders are not investors. There is no guarantee you will make any money from holding RISE tokens, and you do not own any part of RISE VISION PLC or any entity as a result of owning RISE tokens.

  • RISE Newsletter  - April 2018 - Technology Developments, Exchanges Developments, Website Developments & Many More

    Hello RISE community,

    As we are at the end of April, it is time to recap activities the team have been involved in this month. We hope this allows you to catch up with the milestones we have reached this month.

    Technology Developments

    It has been a very notable month for the RISE development team, as we have released the RISE TypeScript Core 1.0.0 to mainnet.

    Technology Developments

    It has been a very notable month for the RISE development team, as we have released the RISE TypeScript Core 1.0.0 to mainnet.

    You can read more about the RISE journey to mainnet in this post here: RISE Core 1.0.0 Meets Mainnet. We invite everyone to download the new RISE core and help us continuously improve. Instructions are available in our Github repository.

    This milestone was picked up by various online outlets. You can read the Press Release here on CryptoNinjas and Coinatory. You will also be able to retweet mentions from XBTMoney, CryptoNewswire and BitcoinsGuide.

    We have already created GitHub projects that will be regularly updated with the issues and tasks we would like to implement for each new version.

    In addition, the Development team has worked on:

    • Improving our unit tests. Two key tasks were to increase coveralls, reviewing and improving the quality of the unit tests done. Unit testing involves subjecting each piece of code to a series of tests, after every change to the source code. The more often we run unit tests, the better as we can identify if there are any bugs or issues.
    • The code base has been checked with a static analysis tool (SonarTS) and several recommendations have been implemented.
    • Improving efficiency between node communications through enhanced Peers Logic by making sure that an invalid/lagging node is not constantly added and removed to the list. This should improve performance and reduce useless log entries.
    • We have migrated the codebase to support a newer version of NodeJS (version 8) compared to the previous version we were using (version 6). As well as, rewriting the whole database layer using a more robust JS library. This will bring us more efficiency.
    • We are working on new and improved RISE wallets.

    Finally, Andrea has been working on the integration for RISE support on the Ledger Nano. We need your help to vote for RISE on the Ledger roadmap. For reference, you will need a Trello account to comment and vote.

    Exchanges Developments

    In April RISE was listed on OctaEx (Octal Bit Exchanger), a new Chinese cryptocurrency exchange, which is quickly gaining popularity. In addition to English, OctaEx available in Thai, Mandarin and Cantonese.

    As also stated previously, RISE will be listed on Exrates.me. Due to listing policy we do not know the exact date, Exrates will announce when RISE is listed.

    To repeat from our last article, we have engaged multiple exchanges that we believe would be a good fit for RISE. Without going into each individual process, we can say there are a multitude of requirements to be considered, they can include listing fees, legal documents, volume and ERC20/non-ERC20 integrations. We will conclude this with mentioning that RISE is in a very unique position, being a non-ERC20 with low volume in the current climate is lengthening discussions. We will keep working hard on negotiating the best deals for RISE.

    In the meantime, you can check the Exchanges page on the RISE website for where RISE is available.

    Team Developments

    The RISE team would like to officially welcome two new members to the project. Firstly, Mart has joined the team this month, he is a polyglot developer, with over 15 years of experience crafting web, desktop, mobile applications and backend software. Mart will be creating new RISE wallets that will be user-friendly and easy to maintain going forward. Secondly, Rajesh has also joined the team as a Community Manager, with experience in managing crypto communities for over 20 ICO’s to date. He is also a programmer interested in adapting blockchain technology.

    RISE is actively seeking new recruits to further development, please check out our Careers page and we are offering a referral bounty for talented developers.

    Everyone can help us on our mission to develop an ecosystem for developers to build DAPPs, so please get in touch. You can contact us for suggestions, referrals and speculative applications via our website.

    Website Developments

    The new and improved RISE website was officially launched in April. You can read more about the design here: Welcome to the new RISE website. Please explore and share the site as we aim to keep this well maintained and updated. We have introduced Google Analytics, which will help us make more informed decisions on how to engage with our marketing channels going forward.


    A whitepaper is something nearly all projects must have before they start development. Our initial thinking was to completely rewrite the whitepaper, however, we believe it will be more beneficial to create a ‘Litepaper’. This will build on the initial whitepaper written in 2016, but cover more deeply the problems RISE is addressing today and how RISE can solve these problems in the future. We will include progress on development and features of the platform that will allow our audience to contextualise the entire project from a business/commercial viewpoint.

    RISE Question & Answer

    We wanted as many people as possible to participate in the Q&A without having to create an account on a specific social media platform, therefore,we have decided to simplify this with a Google form. You will be able to submit multiple times if you have more than 3 questions. This form will be open for questions until Thursday 3rd May 11pm GMT.


    We intend to publish all questions submitted the following week with answers depending on the volume of submissions.

    RISE Monthly Statistics

    The below chart highlights the number and percentage of RISE voted to elect the 101 Delegates and the 102–202 nodes securing the network and non-voting RISE.

    Total RISE Supply 123,828,995. Chart generated 30th April 2018.

    To close on this month, we thank the community for promoting RISE and we hope to give you more great news as we progress the vision of RISE.

    — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

    RISE Vision PLC (token symbol RISE) is an ecosystem for developers, offering a platform for the development of decentralised applications powered by a community driven Delegated Proof of Stake (DPoS) blockchain.

    Disclaimer: RISE is not a security, and token holders are not investors. There is no guarantee you will make any money from holding RISE tokens, and you do not own any part of RISE VISION PLC or any entity as a result of owning RISE tokens.

  • RISE Asked & Answered — May

    Hello RISE community,

    Thank you to the community members who submitted questions to us last week. Outlined below are all questions asked and their respective answers at present. If these answers develop or change we will aim to inform the community through future updates.

    “When can we see some blockchain partnerships?”

    There is no value in announcing a partnership for ‘hype’ if it is not mutually beneficial or strategically aligned with RISE. We wanted to focus on building technology first and gaining progress on these key milestones, some of which have been achieved, as RISE is now in mainnet. Our next phase will be to grow relationships with developers. As such we have begun very initial discussions with coding academies and universities in Europe.

    We are open to partnerships globally, so if you are reading this and have a great contact within a developer community or educational institution, fill out this form. This month we are creating a RISE overview one-pager, a pitch deck for partnership meetings/meetups and the ‘Litepaper’.

    “As a developer myself — but not specifically savvy in the blockchain space — can you spark a few examples of DAPP ideas that one could make on RISE blockchain? As ease of use is part of the mission — will there be tutorials planned to onboard say — hobbyist DAPPs making? Can the team make a few demo examples?”

    Yes, we aim to create tutorials/guides to help developers understand how to build on RISE once we are able to offer a more complete solution. Furthermore, we aim to ensure that our Github has easy instructions to follow in the ‘wiki’ section for developers of all levels to use. We are also able to give bounties for anyone who contributes to building applications, tutorials and technical documentation for RISE.

    As a starting point, you can create applications with the RISE APIs in Github and this will allow you to interact with the RISE blockchain. Any application created today, helps us to stress test the network and improve the RISE technology. Below are some examples of applications created using the APIs by developers in the RISE community. We hope that there will be more in the future as more developers learn about RISE.

    Examples of API applications: Telegram DPoSBOT, Google Ticker, Slack RISEBot and DPOS Tools.

    As an example, let us explore our thinking behind Interlet which was a DAPP idea for the vacation rentals market. The problem today is there are high fees for hosts and guest, as well as issues around currency transactions rates on existing centralised platforms. As a solution, the DAPP running on the RISE blockchain would have allowed for lower fees through the facilitation of peer to peer transactions with cryptocurrency as payment.

    A DAPP is designed to remove a central authority and reward users for contributions. DAPP ideas could be endless as it is possible to evolve existing applications that are currently controlled by a single entity. We believe as the market grows and matures the adoption of different blockchains will depend on the nature and purpose of the DAPP. Many elements will form part of the decision making process for developers, for example:

    • Transactions per second and fees
    • Semi-decentralised vs Decentralised
    • Programming languages supported
    • Private vs Public blockchain
    • Platform business model

    The beauty of DAPPs is that there are huge opportunities for developers to create the next ‘killer app’ and we aim to ensure RISE technology enables this.

    “What is now the Unique Selling Point of RISE? DPOS is still awesome — and now its typescript. Is airdrops + drag n drop tools for DAPPs still a thing? What do you consider now the competitive advantage of RISE?”

    Following on from the answer above, we see RISE USP’s at the moment as a combination of the 5 elements below:

    • Delegated Proof Of Stake — Through offering all RISE holders a opportunity to vote and partake in securing the network, this is one of the more decentralised blockchains available. We also believe that the RISE combination of 101 Delegates/block producers and 1 vote per wallet, makes RISE a unique blockchain. No other DPOS project has this exact protocol. Since the rewrite of the core, RISE is experimenting with transactions per second and we will publicly share this when our development team are happy with how far this has been pushed.
    • Typescript Code base — Internally, TypeScript helps RISE to develop quicker with less bugs and write more intuitive, maintainable code. Externally, Typescript offers reliable and readable code for developers to understand how the core has been created.

    USPs for the future:

    • Developer Tools — APIs and TypeScript SDK — Through offering a range of programming languages to interact with the RISE blockchain we believe this enables more developers to learn about blockchain. At present the more developers that can understand blockchain helps the entire industry to grow.
    • Sidechains — RISE aims to develop sidechain technology to allow developers and businesses to build distributed applications with token assets on RISE in the future. Each sidechain will link to the RISE mainchain. In theory this will enable communication between chains to execute different functions ultimately enhancing scalability of the RISE blockchain. This is scheduled for development later this year, however, completion is highly dependent on working with a cryptographer who understands blockchain technology.
    • Dynamic Fees — Dynamic fees will aim to detect changes in network volume and will raise or lower transaction fees accordingly.

    The combination of these 5 elements makes RISE a unique solution for developers to build DAPPs upon.

    “When can we see some DAPP tools?”

    Currently, there are APIs that can be used to create applications in Github. Following on from this there is a process of features that need to be built as part of a scalable platform for DAPPs to then be built upon. For example, dynamic fees and scalable enhancements need to be developed and released before sidechains and an SDK. These are larger milestones planned for this year, however it will depend on resources, testing and refinements which are not always easy to give an exact timeframe of completion. In the meantime, we recommend following Github projects for RISE development.

    “Can you explain succinctly how RISE will separate itself from larger DPOS projects like ARK, LISK, and SHIFT moving forward and pitch developers “why RISE” instead of these other platforms?”

    To an extent, the projects listed in the question have different goals to RISE. For example, connecting blockchains or JavaScript only or hosting website content. As explained previously, the 5 core elements that create RISE as a platform for developers is what we we believe separates RISE from other similar projects.

    RISE essentially aims to focus on offering tools for developers to learn and create applications on the RISE blockchain in multiple programming languages. Furthermore, from a blockchain protocol level no other project has the same network specifications as RISE: 1 vote per wallet and 101 Delegates/block producers. A combination of the RISE DPOS blockchain, a TypeScript code base and developer tools in multiple programming languages makes RISE advantageous for developers to explore the RISE platform.

    We would like to add RISE is a strong advocate of Delegated Proof of Stake as a blockchain protocol. Therefore, for the progression of the DPOS ecosystem we wish all projects using DPOS to be successful and where strategically aligned the opportunity to partner together.

    RISE blockchain has 101 Delegates/block producers and allows the community 1 vote per wallet equalling number of RISE held in wallet.

    What is your strategy for exchanges?

    Initially, we wanted to diversify across a range of exchanges that were logical to pay for with regards to volume and regional exposure. As a result today RISE is now on Openledger, Octaex, Godex and Exrates. Going forward RISE will be focusing efforts on top 25 exchanges. The team will always be evaluating new and innovative exchanges as they come up.

    Exchanges can be found here: https://rise.vision/exchanges/

    “Is Alty [Cormac] still working for RISE? Very passive lately.”

    Cormac and Steve are the co-founders of RISE. Essentially, they conduct three key areas of the business: legal, finances and exchanges. The technology lead is Andrea and our incredible development team, who based on their expertise make decisions to ensure we are building the best technology possible for RISE. The allocation of resources and operations are handled by Anjalee. MJ DeMarco was brought in to share his expertise in entrepreneurship with projects built on RISE. As we are currently focusing on the core technology, MJ’s advisory role will become more prominent at a later stage. So to conclude, yes Cormac is still working on RISE, but his role is less on the front line.

    “Is Interlet (and the other one incubator) resume-able to development, or probably won’t come back? Is Incubator in the plans of coming back — now that mainnet is active — or is it awaiting sidechain?”

    As stated previously for Interlet, the white paper, pre-ann website, first snapshot and product designs were already worked on. Development is not in progress at this present time. RISE initially planned to build our core blockchain technology in parallel however, we now have decided to focus entirely on core blockchain platform first. With regards to the online casino project, there are many regulations associated with the concept of online casinos and this could hinder the entire project. Once core technology is completed, we will review the regulatory environment at that point in time.

    Please note that for RISE to be successful in the long run, we must remain compliant in all activities going forward.

    “What ever happened to the Chipz airdrop?”

    As stated in the previous answer, all projects are on hold. With regards to the online casino project, there are many regulations associated with the concept of online casinos and this could hinder the entire project. Once core technology is completed, we will review the regulatory environment at that point in time.

    “Q1 was supposed to see at least two sidechains (Interlet and Chipz) what happened that now we are barely expecting 1 sidechains later this year. Maybe you did not realize it the selling point of RISE was actually side chains + airdrops coming and now it has nothing of that?”

    As previously explained, RISE will be focusing on the core technology at this current point in time and this should be the ‘selling point’. Yes, in the short term it has impacted the two projects scheduled for release this year. However, we see immense value in focusing on the core platform now to ensure DAPP creation on RISE is accelerated in the longer term.

    “Is Incubator in the plans of coming back — now that mainnet is active — or is it awaiting sidechain? Can you provide updates on the Airbnb DAPP competitor and any other developers still actively using RISE as their platform of choice?”

    For Interlet, please see earlier answer. To further clarify, Interlet was an ‘in-house’ DAPP that RISE initially planned to launch to showcase the RISE blockchain. At present we cannot give an answer on this as it will be reviewed once the core technology is completed. With regards to developers using RISE, we will be exploring different ways to attract and engage developers going forward. We will be leveraging a bounty program in the near future to drive contributions to RISE.

    Thank you for submitting your questions and we look forward to more great questions from the community. We understand the desire from the community for a live AMA and will aim to do this for early June.

  • RISE will be listed on RightBTC

    We are incredibly excited to announce that RISE will be available on RightBTC on 26th June 2018 with trading beginning on the 27th June 2018.

    RightBTC is a leading global digital assets management platform based in Dubai UAE. RightBTC has a strong loyal user base and plans to expand users rapidly both on their existing exchange and Tulipex, a new exchange which RISE will also be listed on in the future. RightBTC is available in English and Chinese.

    RightBTC makes use of technological advantages to continuously optimise their operational procedures, thus guaranteeing the stability and safety of their trading system and ensuring users can deposit, withdraw, and make transactions quickly and safely.

    1. Bank-level SSL Encryption Transmission

    RightBTC guarantees the safety of user information, and ensures user data will not be tampered with or stolen.

    2. Cold Storage of Digital Assets

    RightBTC store users’ digital assets in offline environments by using a cold wallet to guarantee the safety of capital.

    3. Distributed Server Cluster

    RightBTC have servers in several data centers and have adopted distributed cluster technology to optimize load balancing and ensure the stability of the platform.

    With RISE Mainnet live since April, we believe the RightBTC user base and their future growth plans align with the aim of diversifying the RISE DPOS blockchain offering all over the world.

    The trading pairs will be RISE/BTC, RISE/ETH, RISE/USDT

    Opening Deposit: Jun 26, 15:00 am (GMT+2)

    Opening Trading: Jun 27, 15:00 pm (GMT+2)

    Opening Withdraw: Jun 28, 15:00pm (GMT+2)

    To register a RightBTC account, you can visit: https://www.rightbtc.com/#!/register

    RightBTC Telegram group (Global): https://t.me/RightbtcExchange

    RightBTC Facebook: https://www.facebook.com/rightbtc/

    — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

    About RISE

    RISE Vision (token symbol RISE) is an ecosystem for developers, offering a platform for the development of decentralised applications powered by a community driven Delegated Proof of Stake (DPoS) blockchain.

    The RISE DPoS network is in mainnet and only 101 elected Delegates are given the authority to be block producers. Delegates are elected by the RISE community who cast their votes by staking and voting with their RISE wallets. The vote weight of each wallet is in proportion to the amount of RISE it contains.

    For more information, please visit the RISE website: https://rise.vision

  • RISE Newsletter — August 2018 - Technology Developments, Monthly Statistics & More

    Hello RISE Community,

    In this newsletter, we will give a roundup of what RISE has been up to in the month of August. To start off, we have a great new video explaining RISE technology and the future we are aiming to build. Please feel free to comment, like and share to help us expand the community.

    The Future on RISE — Video in collaboration with Darkroom Ltd.

    Technology Developments

    Node operators and Delegates should update their nodes as soon as possible following all releases and updates.
    • In August, we released an update on how the new RISE wallets are going to change the sign-in flow to protect users RISE even more than before. Do you want to help us make a great wallet? You can still sign up as a tester for future testing by filling out this form. Mart and Tobias have been continuously refactoring code and refining key usability elements of the new RISE web wallet. Together, in August they pushed 134 commits to master and 138 commits to all branches. On master, 90 files have changed and there have been 7,372 additions and 2,731 deletions.

    August AMA

    As part of our efforts to increase awareness of the RISE project and communication with the community we hosted our first Reddit AMA in August. You are able to read the August AMA on Reddit here.

    RISE Monthly Statistics — August

    The below chart highlights 74.74% of RISE (96,007,205) voted to elect the 101 Delegates and 2.36% of RISE (3,035,217) on 101 to 202 Delegates securing the network. 22.89% of RISE (29,406,582) is non-voting.

    Total RISE Supply 128,449,004. Chart generated 2nd September 2018.

    To close on this month, we thank the community for supporting RISE and we hope to give you more great news as we progress the vision of RISE. Join the RISE community:

    — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

    RISE Vision PLC (token symbol RISE) is an ecosystem for developers, offering a platform for the development of decentralised applications powered by a community driven Delegated Proof of Stake (DPoS) blockchain.

    Disclaimer: RISE is not a security, and token holders are not investors. There is no guarantee you will make any money from holding RISE tokens, and you do not own any part of RISE VISION PLC or any entity as a result of owning RISE tokens.

  • RISE Newsletter —  Technology Developments, RISE Web Wallet & More

    Hello RISE Community,

    In this newsletter, we will give a roundup of what RISE has been up to in the month of October.

    Technology Developments

    RISE Core version 1.2.0 featuring ProtoBuf network layer and many other improvements has been released to mainnet. Read about the release in Github here —RISE v1.2.0 — Mainnet. On the RISE node there have been 20 commits to development and 32 commits to all branches. On development, 63 files have changed and there have been 2,905 additions and 1,514 deletions.

    This month Andrea and Matteo have worked on a modification of the current consensus/delegate algorithm which aims at making the vote mechanism more fair towards delegates. You are invited to read the proposal here and please feel free to share your feedback with the dev team in Slack. The two main principles are:

    1. The vote weight of each delegate will be recalculated based on productivity. Delegates who miss multiple blocks will have their vote weight reduced progressively, depending on their productivity. For example, if vote weight is 100 and productivity is 70%, the recalculated weight will be 70. They will lose ranking and may even exit the pool of possible forgers if productivity is very low.
    2. The 101 forgers of each round will be picked from a larger “pool” of possible forgers, not only the top 101 sorted by recalculated vote weight, but from a larger subset of delegates (the size of the pool is yet to be determined) and their probability to forge is randomised but still dependent on their votes weight. Higher votes weight still means proportionally higher probability to forge, but does not give the full certainty for each round.

    RISE Web Wallet

    During the month of October, there has been great progress on the new web wallet. The RISE wallet now has an address book and support for contacts. This month, unit tests (besides end-to-end tests) were carried out and many more small bug fixes and optimisations. The team have also been preparing for the public beta release, more details will come in the next few weeks. On the RISE Wallet repository there have been 110 commits pushed to master and 125 commits to all branches. On master, 81 files have changed and there have been 8,956 additions and 2,192 deletions.


    This month RISE was integrated into IOV core repository in Github. IOV aims to provide a universal protocol for blockchains and wallet users. RISE is looking forward to being part of an interoperable ecosystem. The new version of IOV-Core — version 0.7.0 — enables cross-chain transactions with RISE. Andrea collaborated in the project by contributing a library to IOV-Core.

    Community Project

    One of our community members, Vergill Lemmert, has created a brand new app — the RISE browser extension! It is a notification app that allows you to follow RISE addresses in near real time. Vergill has also written a blog post to set up and customize the extension.

    To close on this month, we thank the community for supporting RISE and we hope to give you more great news as we progress the vision of RISE. Join the RISE community:

    — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

    RISE Vision PLC (token symbol RISE) is an ecosystem for developers, offering a platform for the development of decentralised applications powered by a community driven Delegated Proof of Stake (DPoS) blockchain.

    Disclaimer: RISE is not a security, and token holders are not investors. There is no guarantee you will make any money from holding RISE tokens, and you do not own any part of RISE VISION PLC or any entity as a result of owning RISE tokens.

  • RISE Wallet 1.0 Released

    After over half a year of active development, we’re pleased to announce RISE Wallet 1.0 being available on the web and for desktops. We wanted to make a secure, easy to use and modern wallet which would work seamlessly across all platforms. To achieve this, we used TypeScript (the same language the RISE blockchain is written in) along with React and Material-UI. This article will walk you through the the new features, as the new version brings many new features.

    New layout

    Redesigned with accessibility in mind and taking advantage of Google’s battle tested Material-UI components, the new wallet have a familiar look and it’s easy to use.

    Multiple accounts

    One of the biggest new features is support for multiple accounts. You can add as many as you wish and then customize the order by using names and pinning.

    New sign in flow

    Mart has already discussed the new sign in flow in details a while back. In a nutshell, we won’t ask for your secret mnemonic or the passphrase until the last moment, when it’s actually required. This reduces the risk of having it leaked.

    Support for Ledger Nano S

    You can now use your wallet for the Ledger Nano S hardware wallet allowing to import and sign transactions for the accounts stored on the device. This feature requires Google Chrome or a desktop version.

    Support for mobile

    Responsive design and carefully crafted password forms will let you easily send new transactions from your phone, while making use of your device’s secure keychain. The following video shows using Touch ID to sign a transaction with both the mnemonic and the second passphrase.

    Desktop versions

    To bring another level of security, you can download RISE Wallet as a desktop app for MacOS, Windows and Linux. Below is a screenshot on Win10. Downloadable binaries can be found on the project’s GitHub release page.


    We’re looking into translating the app to other languages through a CrowdIn campaign. At the time of writing this, only English and Estonian languages are complete. If you would like to participate for your own language, become a translation contributor.

    Address book

    You can now assign names to frequent contacts and then quickly fill the Send RISE form, even by using only your keyboard (SHIFT+S). Contact names also appear in transaction details. Important thing to note, that data is being persisted only on your local machine.

    Network switcher

    Last but not least, switching between networks (testnet / mainnet) is now much easier, being available at all times via Add an account -> Change node . You can also connect to your own network of choice, if that’s your use case.

    RISE Wallet 1.0 is available to download today from project’s GitHub release page. Please report any issues on the issue tracker or on the dedicated Slack channel.

    Web versions

    Desktop versions

  • Introducing RISE v2

    2018 was a very productive year for RISE. Let me recap some of the achievements the team was able to deliver during 2018:

    Along with all these updates, I started working in a private repository to create the new RISE v2.

    Why v2

    New v2 is built to have the following concepts in mind

    1. Extensible
    2. Modular
    3. Simpler
    4. More flexible

    The ones above are the 4 core features that I think were lacking in the old v1 codebase hence why I started the rewrite.

    What’s new in v2

    RISE v2 hosts several new improvements. Let’s start from the biggest change:

    RISE Modules

    Thanks to yarn and Lerna we were able to rewrite all main RISE functionalities separating the concerns of each module.

    This is not only a nice coding approach allowing to re-use components but will also allow third-party developers to override core modules by injecting their own replacing module.

    For example, there is a “consensus-dpos” module which provides all the code needed to handle the DPoS rules and API; If a developer wants to, they might write their own consensus module and re-use all the other core modules.

    You can think about modules like pieces of a puzzle. As long as your piece has the same shape as the “original” one, it will fit nicely creating a different picture.

    More info about modules here.

    Modules LifeCycle

    Since every module is an (almost)-self-contained piece of software it needs to follow a contract, or a so-called interface, in order to be a valid module.

    Module developers can also benefit from using the lifecycle declared within the above-mentioned interface. This is beneficial especially when modules need to initialize or teardown specific elements within their logic.

    The main 4 lifecycle events are (in order of execution): preBoot, boot, teardown, postTeardown.

    Modules can also override the configuration of other modules as well as adding specific commander options when booting the application.

    Modules resolution

    DAG — Source: Wikipedia

    Since Module ‘A’ could depend on ‘###em/em###’ a Directed-Acyclic-Graph is built on-startup so that the lifecycle and config override respects the expected natural flow.

    This also ensures that no 2 modules reference each-other (either directly or non-directly) leaving the codebase clean as well as making sure that different boot produces the same result in term of booting priority.

    Since I follow (as much as possible) the KISS principle, modules can declare that they depend on another module by exploiting the ‘package.jsoncapabilities that Node.js developers are already used to.

    Technology upgrades

    The underlying technology of the RISE core needs to be constantly updated to leverage both performance and security improvements.

    With this in mind we decided to update:

    • Node.JS from v8 to v10;
    • TypeScript from 2.8 to 3.4.5;
    • PostgresSQL from 10.4 to 11.3.

    We then decided to remove Redis entirely as it was no longer used in the codebase and there was no real reason to keep it as third-party dep.

    The WordPress-like Hook System

    If there’s something great about WordPress is its the plugin and hook system. Since one of the main assets of the whole WordPress ecosystem is the wide variety of plugins that are installable it seemed a good idea to copy the good concepts and bring them, for the first time, in the BlockChain eco-system.

    In RISE v2 we use “mangiafuoco”, a Node.JS library written by me that mimics the WordPress hook system by adding utility functions.

    Embracing this technology was kind of the next step when building a modular core since it allowed us to decouple modules inter-communication enhancing by several factors the maintainability and code clarity.

    To enhance and smoothen out the learning curve we even created TypeScript Decorators which you can apply on your methods. This will give you type-safety, the thing we all love about TypeScript.

    Example of multi-hooks usage.

    Of course, all filters and actions are declared in the “hooks” directory of each module allowing every developer to easily find exported actions and filters.

    Execution priorities you ask? We also support that and you can use it as well :).

    New Transaction Types and functionalities

    V1.x Transaction system has several design flaws and is not as flexible as I wanted it to be.

    The new tx schema has the following benefits compared to the previous version:

    • Streamlined serialization and deserialization
    • Ability to encode different address systems (more on this later)
    • Unequivocally encode-decode payload

    Before this update, we had several constraints and, for example, the Ledger Nano integration was painful to code and test.

    The new tx schema opens a lot of new possibilities for RISE enabling the amount of flexibility we need to satisfy almost all use cases.

    Another nice side-effect of the new transaction types is that they do natively support having dynamic fees. Even if RISE does not necessarily need dynamic fees now, we always need to anticipate needs to avoid unnecessary network bottlenecks.

    The new Send transaction type has a new field that can hold up to 128bytes of raw data

    Send transaction with “banana” string encoded in the payload

    This opens up a lot of new possibilities and scenarios developers could use to permanently store data in the RISE blockchain. EG: An eternity wall, a payment processor, a notary system, …

    Arbitrary precision library with bigint

    In v1 we used BigDecimal javascript library which has been a great resource against very-well-known javascript issues when handling math.

    It’s very crucial that the math is bullet-proof unless you are a fan of Thanos and its snap and wanted to see it applied to the blockchain :).

    With v2 we leverage “bigint” which provides integers with arbitrary precision with blazing fast (native) speed.

    So, by switching to this new feature, we got rid of a third party dependency (which is always a great thing) and we leverage native speeds when dealing with big numbers.

    Introducing RISE address v2.

    The “oldy” addresses look like “12345678R” while this might sound great as only numerical digits are used, the way the address system was initially designed comes with 2 coupled security flaws:

    1. Address space is “only” 2⁶⁴. (compared to 2²⁵⁶ public-key space)
    2. 2 public keys can result in the same address. (collision attack)

    Along with the 2 issues above, the current RISE address system does not allow any data encoding so it’s basically impossible to have special addresses with a different purpose.

    Let’s get straight to the point. What does the new Address will look like?


    OMG, that’s long… What are the PROs?

    1. State of the art technology (borrowed from Bitcoin — bech32),
    2. flexible,
    3. has checksum!!!! Meaning that if you had to type a long address and made up to 4 mistakes we would be able to find exactly where the error was made,
    4. by far more secure,
    5. QR code efficient — easier to read.

    Along with all the goodies, we are making a big change in the way the 2 address system will co-exist.

    Since V2. The primary account key will no longer be publicKey while rather the address itself. Since V2 is, by far, more secure than the previous address system, we will discourage using V1 by highering the TX fees when sending/receiving.

    New P2P Comm Layer (Again)

    Since ProtoBuf we basically solved most of the p2p bottlenecks. Unfortunately, some minor errors were made when designing the new p2p layer back then.

    The new P2P layer features:

    1. Same Transaction Per Second output
    2. Same Bandwidth efficiency
    3. More flexibility
    4. More robustness

    Let’s focus on the third and fourth elements above:

    The P2P layer has been decoupled and is now a separate module (“core-p2p”) which allows third-party devs to deploy their own p2p solution. Ex: just for fun a developer could use morse-signals over the infrared spectrum to send/receive data to/from neighbor nodes.

    About Robustness: we designed the p2p classes to be easy to use and rock solid. The p2p layer will treat your data as an opaque message to be sent and received, serialization and de-serialization are up to the developer. Multiple codec technologies might co-exist; for example, a module could register a p2p endpoint for sending/receiving data in “plain-text” and another could use binary or ProtoBuf as the encapsulation method.

    Furthermore, requests can now be batched and also eventually expire. Handy for many use-cases.

    Last breaking change for the RISE v2 would be the communication ports. In RISE v1.x we used the 5555 (or 5566) port for both public APIs and internal consensus communication. In V2 we decided to separate the 2 comm channels:

    • Port 5554 for consensus communication;
    • Port 5555 for APIs.

    This small change will improve even further the performances of the communication layer by removing the API bloatware from the consensus endpoints.

    Deprecating MultiSignature Accounts

    This might sound like a step back, right? No more multisig accounts… WhatTheHeck??

    Well, there are 2 reasons behind this move:

    1. The multisig functionality was, to say the least, over-engineered and poorly conceived (both in code and database)
    2. The new Address system is able to encapsulate multisig accounts such as in BTC.
    Note: you can’t really create multisig accounts in v2. (they’ll come soon™)

    To summarize, we removed a big chunk of codebase (and tests) that no-longer needs to be maintained :).

    In RISE we also have second signature accounts. That functionality will be maintained as a separate module named after its functionality (core-secondsignature). We decided to keep this feature since many accounts were actively using it compared to multisig which was not used at all.

    Changes to the consensus (Again)

    Improving current solution is crucial. That’s why we decided to stop distributing fees evenly to all delegates. “Wait what”?

    • In v1: All tx fees were collected and evenly distributed to all delegates who participated in the round.
    • in v2: delegates will be rewarded the fees they forge.

    In all honesty, the “v2 way” should have been “the way” as it provides an incentive for delegate nodes to keep their node up&running with proper networking.

    The Database

    Since RISE v2 is, besides many other things, a big refactor of v1.x, it was about time to change the Database structure to a more meaningful schema.

    A bunch of columns was removed from the accounts table and, at its base form, only 4 (vs over 10) column are needed.

    Furthermore, tables and some columns were properly renamed to follow a single standard convention.

    Idempotent DB Update Scripts

    Upgrading a blockchain isn’t as easy as you might expect. Database updates are no exception. In RISE v2 we decided to create “schema.sql” files which basically are idempotent. But what is idempotency? From wikipedia:

    Idempotence is the property of certain operations in mathematics and computer science whereby they can be applied multiple times without changing the result beyond the initial application.  (wikipedia)

    With this change of approach we now have the ability to:

    • Keep the current, most-up-to-date, database schema in a single place for easier maintenance and debugging.
    • run the schema.sql upon each startup and make sure we don’t break anything

    How/When will the update happen?

    Since the p2p layer is no longer backward compatible we’ll provide an update script that will take care of upgrading the blockchain core at a specific point in time (or better said, in height).

    All node operator will need to trigger the update script before the deadline to keep their node(s) synced with the network. Delegates failing to do so will be eventually banned by the consensus leaving space to worthy delegates that updated instead! (more info).

    Of course we’ll give it a go using testnet first that has been rebooted a couple of weeks ago to have the same features and configuration we have in mainnet.

    If interested, please join our Slack, and enter the #testnet channel to receive some testnet tokens to play with and instruction on how to set up a node.

    Thanks to Tobiasz Cudnik.

Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.