RChain is a fundamentally new blockchain platform rooted in a formal model of concurrent and decentralized computation. The RChain Cooperative is leveraging that model through correct-by-construction software development to produce a concurrent, compositional, and infinitely scalable blockchain.
A roadmap is being worked on, as a result of the Developer Retreat in November. You can see the milestones and dependency graph at: https://rchain.atlassian.net/roadmap
RChain is an ambitious project, involving research, not just writing code. Dates are not finalized until communicated explicitly.
RChain was the culmination of a number of innovations by founder Greg Meredith. The core of RChain is based on mobile process calculi, a branch of mathematics with approximately 30 years of history. Together with the experience of other blockchains and other technology, the RChain architecture was documented in July of 2016 and at that time, the goal was to create a blockchain-based social network with inbuilt micropayments functionality i.e. attention economy. Due to the complexity of the project and disagreement between the team members, it was decided that Greg would focus on realizing the vision of RChain. The RChain organizations (the Co-op
and Holdings company
) were formed in December 2016 - January 2017.
is the organization that develops the open-source RChain platform software. It’s an open and community-driven initiative with multiple communication channels through which all are welcome to participate. RChain Holdings
is a for-profit entity whose mission is to grow the ecosystem around the RChain platform, through incubating startups, forming joint ventures, developing products, and delivering professional services.
The RChain Cooperative and RChain Holdings are both Internet companies and have participants around the world. They are Washington State USA companies and the founders live in Seattle.
The Co-op is a member-driven organization with an elected nine-person Board of Directors
. Board seats have 3, 2, or 1 year terms. The board is composed of:
- 3 years: Greg Meredith, Vlad Zamfir, Ian Bloom
- 2 years: Kenny Rowe, Evan Jensen, Alexander Bulkin
- 1 year: Navneet Suman, Hendrik Jan Hilbolling, David Currin
The Co-op officers are: Greg Meredith, President; Evan Jensen, Secretary; Lisa Rice, Treasurer.
There are three steering committees where Members collaborate to shape and organize the Cooperative: the Executive Committee, the Governance Committee, and the Compensation Committee. All committees have open participation but some are limited to 11 working members plus a chair.
RHOCs are an Ethereum ERC20 token issued by the Co-op in early 2017 intended as a vehicle for people to get access to the technology. There are 861,185,194 RHOCs in existence. No more will be minted. RHOCs will be 1:1 redeemable for REVs, a future RChain platform native staking token.
No. Contrary to fraudulent reports circulating on Twitter, no airdrop is in the works or planned.
This is a somewhat outdated financial summary, distribution, and other information
. This is the current distribution.
At the first Member Meeting in October 2017 the Members voted that "The Cooperative should sell from its treasury to put no more than 200 million RHOC tokens in circulation (tokens held by anyone, other than; 1) held by the Cooperative, or 2) burned) during the next calendar year." The full voting results are reported on Medium
Click “Add Custom Token”, then fill in:
Contract Address: 0x168296bb09e24a88805cb9c33356536b980d3fc5
Token Symbol: RHOC
RChain can not endorse RHOC trading because of the structure of our private sale.
Not directly; the redemption period ended in April 2017. AMPs and RHOCs are tradable on exchanges.
RHOCs will be 1:1 redeemable for REVs. REVs are the native staking token for the RChain platform. Learn more about the RHOC/REV swap.
Join one of the public discussion forums (see the comm channels above). People who want to play a more active role can collaborate on code and community development projects, create Co-op infrastructure, and work out its governance. See CONTRIBUTING.md
for full information.
Interested individuals can become a Member of the Co-op. Benefits include: access to all channels of the Discord server where the RChain developers and community collaborate, electing the board members, participating in governance committees, being eligible to propose and collaborate on projects, and deciding about project approval and budget allocation. Additional benefits will be defined over time such as patronage dividends. Membership requires a one-time $20 membership fee and proof of identity in the form of government issued id and video verification with the Cooperative. If you'd like to join please register at: https://member.rchain.coop
Yes, unless you reside in a region sanctioned by the US. The registration process will check that.
Yes. Bounties are task based with peer review. Tasks vary, but typically bounties are available for core development, community formation, marketing, business development, and channel operation. Github is used for issue tracking and project management
Yes. Read CONTRIBUTING.md
, then look for projects you’d like to participate in.
“In theoretical computer science, the π-calculus is a process calculus. The π-calculus allows channel names to be communicated along the channels themselves, and in this way it is able to describe concurrent computations whose network configuration may change during the computation.” (Ref.: https://en.wikipedia.org/wiki/Pi-calculus
). To better understand how it is being applied in the RChain development, check out the paper Mobile process calculi for programming the blockchain.
and put yourself in the Talent Pool.
An understanding of Pi Calculus will help. Join the RChain Discord
and inquire to find out more. The RChain YouTube channel
has videos that explain various aspects of the platform. Our developer subdomain also hosts a Rholang tutorial which can be found here
RChain's components are all under open source and free software licenses. Our license of choice is Apache v2. Rholang is the only component currently licensed under the MIT license.
There is a Dapp (Cryptofex) that intends to build an IDE on RChain that can support Rholang and solidity for a start so devs that are familiar with solidity can easily code smart contracts that would run on RChain's VM. The team behind the Dapp is same team leading the RChain's development; Pyrofex. Cryptofex White Paper
The storage layer is a fundamental part of the VM; it just happens to be something that's modular enough to break out into its own library. The storage layer is how message delivery between processes is implemented; it uses rholang patterns as keys. Sending on a pattern is putting data in the database; receiving on a pattern is querying the database. If there's no data to consume, a continuation is stored at the key instead. If there's already a continuation, and you're trying to store data, the continuation gets applied to the incoming data.
We're building an API backed by LMDB (Lightning Memory-Mapped Database
Rholang doesn't use a notion of transaction in the same way that ethereum does. Ethereum uses event-loop concurrency, and either the entire turn kicked off by a message succeeds or it doesn't (maybe you ran out of gas, maybe there was some other error). Rholang blocks, on the other hand, contain three kinds of data: individual synchronizations of names, new sends, and new contract deployments. If you want transactions, you have to write code that implements them.
In short, the main reason not to build on top of Ethereum is in order to have formal verification at all levels. i.e. There will always be some math which can prove to us that any given part of the system is bug-free. The foundation of RChain is Reflective Higher Order Calculus, which enables the creation of ‘correct-by-construction’ contracts. From system contracts to Casper Consensus, RChain contracts will be backed by formal verification- giving users some guarantees on what these contracts do.
A safety oracle looks at all the messages a node has received and says "at this point, no one can convince me that this subset of information is wrong". If the network converges on the value of that information, it must converge on what that node believes.