Bitcoin Cash is a hard fork of Bitcoin with a protocol upgrade to fix on-chain capacity. Bitcoin Cash intends to be a Bitcoin without Segregated Witness (SegWit) as soft fork, where upgrades of the protocol are done mainly through hard forks and without changing the original economic rules of the Bitcoin. Bitcoin Cash (BCH) is released on 1st August 2017 as an upgraded version of the original Bitcoin Core software. The main upgrade is the increase in the block size limit from 1MB to 8MB. This effectively allows miners on the BCH chain to process up to 8 times more payments per second in comparison to Bitcoin. This makes for faster, cheaper transactions and a much smoother user experience. Why was Bitcoin Cash Created? The main objective of Bitcoin Cash is to to bring back the essential qualities of money inherent in the original Bitcoin software. Over the years, these qualities were filtered out of Bitcoin Core and progress was stifled by various people, organizations, and companies involved in Bitcoin protocol development. The result is that Bitcoin Core is currently unusable as money due to increasingly high fees per transactions and transfer times taking hours to complete. This is all because of the 1MB limitation of Bitcoin Core’s block size, causing it unable to accommodate to large number of transactions. Essentially Bitcoin Cash is a community-activated upgrade (otherwise known as a hard fork) of Bitcoin that increased the block size to 8MB, solving the scaling issues that plague Bitcoin Core today. Nov 16th 2018: A hashwar resulted in a split between Bitcoin SV and Bitcoin ABC
RSK Infrastructure Framework (RIF) is a token developed on the RSK platform allowing holders to consume (and interact with) services within the RIFOS framework. The RIFOS framework, also built upon RSK, is a suite of distributed protocols built to enable fast, simple and scalable development of distributed applications within a highly-scalable, secure and unified environment. The RSK framework, in combination with the RIF token, allows developers to deploy and interact with the applications built atop the RIFOS framework. These include, amongst other things, third-party developed infrastructure services, as well as any additional applications deployed on the RSK framework. The RIF Token is intended to allow any token holder to consume any services that are compatible with RIF OS Protocols. Such services may include third party-developed infrastructure services, and any other apps that might be deployed on our framework that agrees to accept rif Tokens as a means of accessing / consuming the service or app.