Introduction | Overview | Local Testnet | Public Testnet | Misc
Remme Protocol is a blockchain-based protocol focused on digital key and identity lifecycle management to resolve issues related to cybersecurity, IoT connectivity, data integrity, digital copyright protection, transparency etc.
Some of the groundbreaking features include:
- Free Rate Limited Transactions
- Low Latency Block confirmation (0.5 seconds)
- Attribute-based identity and access control
- Designed for Sparse Header Light Client Validation
- Time Delay Security
- Hierarchical Role Based Permissions
- Support for Biometric Hardware Secured Keys (e.g. Apple Secure Enclave)
- Designed for Parallel Execution of Context Free Validation Logic
- Designed for Inter Blockchain Communication
Remme Protocol currently supports the following operating systems:
- Amazon Linux 2
- CentOS 7
- Ubuntu 16.04
- Ubuntu 18.04
- Ubuntu 19.04
- MacOS 10.14 (Mojave)
To get a general architecture overview and understanding of how the basic blockchain components interact, please refer to the developer documentation. Within the Remprotocol context: Nodeos is Remnode; Cleos is Remcli; Keosd is Remvault. Configuration, settings, options and usage patterns remain compatible with the original EOSIO approach.
If you are a developer, depending on your context, you would probably need an independent local network to work on your dApp. Instructions detailing the process of getting the software, building it, running a simple local test network that produces blocks, account creation and uploading a sample contract to the blockchain can be found on the Developer Portal.
Before you begin, install EOSIO.CDT v1.7+ from the EOSIO.CDT repository.
git clone --recursive https://github.com/Remmeauth/remprotocol
cd remprotocol/
./scripts/eosio_build.sh -ymAlternatively, you may install pre-built binaries from the archive.
To spin up an independent node that is connected to the Public Testnet, refer to this blog post.
The faucet bot helps you with getting set up and creating an account with some tokens on it. With the help of this bot you will get the following data about your testnet account:
- Account name
- Public and private keys to be able to create transactions
See LICENSE for copyright and license terms. Remme makes its contribution on a voluntary basis as a member of the Remme community and is not responsible for ensuring the overall performance of the software or any related applications. We make no representation, warranty, guarantee or undertaking in respect of the software or any related documentation, whether expressed or implied, including but not limited to the warranties or merchantability, fitness for a particular purpose and noninfringement. In no event shall we be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or documentation or the use or other dealings in the software or documentation. Any test results or performance figures are indicative and will not reflect performance under all conditions. Any reference to any third party or third-party product, service or other resource is not an endorsement or recommendation by Remme. We are not responsible, and disclaim any and all responsibility and liability, for your use of or reliance on any of these resources. Third-party resources may be updated, changed or terminated at any time, so the information here may be out of date or inaccurate.
The Remme Protocol software is released under the open source MIT license and is offered “AS IS” without warranty of any kind, express or implied. Any security provided by the Remme Protocol software depends in part on how it is used, configured, and deployed. Remme Protocol is built upon many third-party libraries such as WABT (Apache License) and WAVM (BSD 3-clause) which are also provided “AS IS” without warranty of any kind. Without limiting the generality of the foregoing, Remme makes no representation or guarantee that Remme Protocol or any third-party libraries will perform as intended or will be free of errors, bugs or faulty code. Both may fail in large or small ways that could completely or partially limit functionality or compromise computer systems. If you use or implement Remme Protocol, you do so at your own risk. In no event will Remme be liable to any party for any damages whatsoever, even if it had been advised of the possibility of damage.
Remme is not operating any mainnet blockchains based upon the Remme Protocol software. We caution those who wish to use blockchains built on Remme Protocol to carefully vet the companies and organizations launching blockchains based on Remme Protocol before disclosing any private keys to their derivative software.