iExec RLC is a blockchain-based distributed computing platform that offers its users a decentralized cloud marketplace. The company was founded in 2016 by Gilles Fedak and Haiwu He, and is headquartered in Lyon, France. iExec RLC has a customer support number that users can call for assistance with the platform. The company also has a headquarters in the United States.
iExec RLC (RLC) phone number.
This is the number for the RLC phone app. You can use this number to contact RLC customer service.
iExec RLC (RLC) support.
This document describes the steps needed to add support for the RLC protocol in your node.
Requirements
Node.js 8.x or greater
Installation
To install the RLC module, use the following command:
npm install rlc
Usage
To use the RLC module, include it in your code as follows:
var RLC = require ( ' rlc ' );
Once you have included the module, you can create a new RLC object using the constructor function:
var rlc = new RLC ();
You can then use the various methods of the RLC object to communicate with the network. See the documentation for more information.
Note: When using the RLC module, you must always ensure that the peer you are communicating with is authorized to do so. For more information, see the RLC documentation.
Examples
Below are three simple examples that demonstrate how to use the RLC module.
Example 1: Registering a Peer
To register a peer with the RLC module, use the registerPeer function:
rlc . registerPeer ( 'PeerName' , { address : 'Address' });
The first argument is the name of the peer, and the second argument is an object containing the peer's address. You can also specify a port number if you want to connect to the peer using a different port.
Once you have registered the peer, you can use the getPeerStatus function to get information about the peer:
rlc . getPeerStatus ( 'PeerName' );
The first argument is the name of the peer, and the second argument is an object containing the various status values for the peer. The available status values are:
connected : The peer is currently connected to the network.
: The peer is currently connected to the network. disconnected : The peer is not currently connected to the network. This value will be true if the peer has been disconnected due to a failure or if it has been suspended by the RLC module.
: The peer is not currently connected to the network. This value will be if the peer has been disconnected due to a failure or if it has been suspended by the RLC module. idle : The peer is currently idle and not participating in any transactions.
: The peer is currently idle and not participating in any transactions. pending : The peer is currently waiting for transactions to be processed. This value will be true if there are pending transactions that need to be processed by the peer.
: The peer is currently waiting for transactions to be processed. This value will be if there are pending transactions that need to be processed by the peer. failed : The peer has failed and cannot be used for any further transactions. This value will be true if there has been a failure when trying to connect to or register with the peer.
: The peer has failed and cannot be used for any further transactions. This value will be if there has been a failure when trying to connect to or register with the peer. disconnectedPending : The peer is currently disconnected, but some pending transactions are still waiting to be processed. This value will be true if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to reconnect.
: The peer is currently disconnected, but some pending transactions are still waiting to be processed. This value will be if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to reconnect. connectedPending : The peer is currently connected, and all pending transactions have been processed. This value will be true if all pending transactions have successfully been processed by the peer.
: The peer is currently connected, and all pending transactions have been processed. This value will be if all pending transactions have successfully been processed by the peer. failedPending : The peer has failed, and some pending transactions are still waiting to be processed. This value will be true if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to reconnect.
: The peer has failed, and some pending transactions are still waiting to be processed. This value will be if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to reconnect. closed : The peer has closed its connection with the network and cannot be used anymore. This value will be true if the peer has been closed due to a failure or if it has been suspended by the RLC module.
: The peer has closed its connection with the network and cannot be used anymore. This value will be if the peer has been closed due to a failure or if it has been suspended by the RLC module. active : The peer is currently participating in transactions and is up and running. This value will be true if there are active transactions being processed by the peer.
: The peer is currently participating in transactions and is up and running. This value will be if there are active transactions being processed by the peer. idlePending : The peer is currently idle but some pending transactions are still waiting to be processed. This value will be true if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to become active again.
: The peer is currently idle but some pending transactions are still waiting to be processed. This value will be if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to become active again. failedPending : The peer has failed, and all pending transactions have been rejected. This value will be true if there are no more pending transactions that can be processed by the peer.
: The peer has failed, and all pending transactions have been rejected. This value will be if there are no more pending transactions that can be processed by the peer. closedPending : The peer has closed its connection with the network, but some pending transactions are still waiting to be processed. This value will be true if there are some pending transactions that have not yet been processed by the peer but are still waiting for it to become active again.
Example 2: Transactin
iExec RLC (RLC) customer care.
0xcert is a new blockchain-based certification platform that allows users to certify and verify the authenticity of digital assets.
0xcert is a new blockchain-based certification platform that allows users to certify and verify the authenticity of digital assets.
What is iExec RLC (RLC)?
iExec RLC is the native token of the iExec network. It is an ERC-20 token that allows users to purchase and sell services on the iExec network.
iExec RLC (RLC) headquarters.
The RLC token is a utility token that is used on the Ethereum blockchain to pay for services and products on the RLC platform. It is also used as a means of voting and governance on the platform.