Shared Nodes are common infrastructure, allowing all DEPLOY shared node subscribers to access the same pool of blockchain nodes at a lower cost than purchasing owned node subscriptions. Your shared node subscription will use the shared DNS host name but your API key will authenticate your requests with the DEPLOY platform. All shared middleware will be available at the same shared DNS host name.
Each shared blockchain and network has its own host name within the DEPLOY infrastructure. This host name is unique to blockchain-network pair. Generally, host names follow the structure
shared-<chain daemon>-<network>.nodes.deploy.radar.tech, where
<blockchain daemon> is blockchain software the shared node is running (
btcd, etc) and
<network> is the blockchain network the shared node is connected to (
This fully qualified host name can be resolved by any public DNS server on the Internet and will serve as the base for any API URIs for both the blockchain node itself or any available middleware. For example, a Geth node on the Ethereum mainnet may have a host name similar to
shared-geth-mainnet.nodes.deploy.radar.tech, the JSON-RPC URI for querying the Ethereum node would be
https://shared-geth-mainnet.nodes.deploy.radar.tech/, and the GraphQL middleware installed on all shared Geth subscriptions is available at the URI
All DEPLOY node subscriptions use API keys as an authentication layer in order to ensure that only the subscribers has the ability to perform queries and send requests to the shared nodes. These API keys should be kept secret and must be provided with each API request.
Your node API keys must be added as a GET argument when performing any HTTP requests (including JSON-RPC) to either your shared node’s blockchain interfaces or its installed middleware. The GET parameter will be named
apikey. For example the full URI for the JSON-RPC interface on a Bitcoin shared node running BTCD would be
https://rpcuser:firstname.lastname@example.org/?apikey=aaaabbbbccccddddeeeeffff which includes the API key to access the owned node.
Your shared node subscription’s API key can be found under the Settings tab in your node’s detail view or as part of the connection information modal.
Your shared node subscription’s specific connection information is available from anywhere within the node detail view of the DEPLOY application. Simply navigate to your shared node from the DEPLOY application’s node list and click Connect to Node in the upper right-hand corner of the screen to view your detailed connection information. This will include the URI for making JSON-RPC requests to your shared node.
Bitcoin shared nodes include the HTTP basic authentication portion of the HTTP URI (
rpcuser:rpcpass@ must be included in all HTTP JSON-RPC requests.