RISE SMART CONTRACTS
Smart Contracts enable a new era of legal and business dealings
and are arguably one of the hottest features in crypto at the moment.
RISE will support the creation and execution of Smart Contracts on its
blockchain.
Connect your contract to external data sources through REST APIs,
and allow them to execute actions automatically when criteria are met.
Development of Smart Contracts will be handled through a Graphical
User Interface, and will allow for currency transactions, actions via APIs,
and more.
RISE UTILIZATION OF LINUX CONTAINERSDid you know Rise Dapps are executed using
Docker, a Linux Container based system?
Containers isolate applications from each other and the underlying operating system,
while providing a repeatable build process. Communication between Dapps is done through
an internal network. Select the Dapp you want to connect to, and Rise will connect the Dapp
to your Dapp internally, and allow you to communicate with the Rise API.
Upon launching a new Dapp, the Rise Node spins up a new container, and runs your Dapp in
that container. The container can auto-detect the code you are trying to run, identify the
language, and install dependencies.
If you so choose, you can also isolate your Dapp from all others, so that communication is restricted.
HOW TO USE ARISE DAPPHave you ever wondered exactly how to open and use a Decentralized Rise Application
on your computer or mobile device?
Before we dive into that, let's go over some other details first:
Developers write Dapps in whatever language they want, using language specific SDKs,
with whichever UI framework they want (including Rise UI), or using Rise API endpoints.
Each Dapp runs in its own container on a Rise Node, which reduces much of the potential
attack surface for malicious actors. We described and explained the use of containers here
a couple of days ago. Each Dapp Container is connected internally to the Rise API endpoint,
so API calls to Rise are all done internally to the Rise Node, instead of using the public Internet
to send API requests.
The API includes a request/reponse mode, and a streaming mode, enabling realtime updates
to Dapps from the Rise Node, and the Rise Node from the Dapps.
Now to answer the question we started with:
To open a Rise Dapp , you simply enter a URL in the following format:
https://dapp..rise.vision/ RISE NODE MONETIZATIONRise Resource Billing System ExplainedRise Node owners will be able to monetize the hosting of Dapps on their Nodes
using the
Rise Resource Billing System. This system will be built into the
Rise Dapp Store and allows billing for the use of system resources by Dapps
hosted on the Rise Node.
Resources that can be billed for are:
1) CPU
2) RAM
3) Storage
4) Network I/O
What is billed for, and how much, is determined completely by the Node Owner.
Any Dapp registered on the Rise network will be available for Node Owners to use
on their own Nodes.
Invoicing will be done in Rise, and automation will be available. If invoices aren't
paid, automatic shut-downs, and deletion is possible. This is all customizable by
the Node owner.
thanks for this above, its a good info and tutorial, slowly i learn about blockchain and etc
RISE DAPP CONSENSUSEach Rise Dapp has its own unique
private side chain which operates in synchronization with
the Rise block time and current block height.
Dapp sidechains are managed by a group of up to 101
master nodes, each of which have block
generation enabled specifically for an individual dapp. The primary role of each master node is
to process transactions and signify the validity of each block generated on the sidechain.
The signing of blocks by a master node against a given dapp is restricted by the dapp owners.
Dapp owners approve individual Rise accounts as master nodes, which then are allowed to forge
on the Dapp’s side chain.
Sidechain consensus is maintained among the 101 master nodes using the same Delegated
Proof-of-Stake (DPOS) method used to secure the Rise blockchain. This allows individual master
nodes to collect fees from each transaction as reward for securing the dapp's side chain.
The motivations behind this form of consensus are:1) to prevent unnecessary enlargement of the Rise blockchain
2) to retain individual sidechain autonomy
3) to ensure that the integrity of each side chain is constantly upheld
In previous posts we have discussed Dapp Development, Computation (Resource Billing System) & Dapp Consensus.
Today we're going to look more closely at Master Nodes and Dapp Storage. But before we do,
let's recap what we understand a Rise Dapp to be:
A
Rise Dapp is a decentralized application that utilizes the Rise SDK and runs in a container on a Rise Node.
It works with the Rise Node using the Rise consensus algorithm. With current web technologies (HTML5/CSS3/JavaScript)
the developer is able to create a powerful UI.
Dapps can use any technology that runs on Linux in their development of the server side of the application.
Regular users can launch the Dapps on any Rise Client.
Dapp Master NodesDapp master nodes are Rise nodes with an installed Dapp and with block generation enabled specifically for that Dapp.
Dapp owners need to approve individual Rise accounts to be permitted to be a master node.
The nodes process transactions and generate new blocks which are then secured by the Rise Blockchain,
making them the core of the dapp system.
Dapp StorageDapp storage is handled by git repositories. When a Dapp is registered with the main network,
it's master branch on the git repository is used whenever the Dapp is installed.
Web hooks are available to push changes to all Rise Nodes that have the Dapps installed.
File Storage can be handled with local storage in the container utilizing docker volumes,
or can use file storage systems on the web served by cloud providers.
For latest info on Rise:
- Official Rise forum:
http://forum.rise.vision- Rise Slack channel:
http://slack.rise.vision- Upcoming new website with Rise 2.0 content (in progress)