Ethereum nodes as JSON-RPC / WebSockets API for developers. Endpoints as a TOR hidden service. Front-running as a service. Global TX Mempool. The distributed cluster of Ethereum nodes designed for speed, peak performance and high availability.
Getting started with ZMOK (https://zmok.io) takes just a few minutes once you connected your wallet.
Seamlessly access Ethereum via the ZMOK load-balanced nodes and smart architecture the same way you would via your nodes. We have built services and APIs around JSON RPC over HTTPS that you can use with your favourite libraries and frameworks, on Ethereum networks - Mainnet, Goerli and Mainnet enhanced with Front-running.
ZMOK's Ethereum APIs require a valid APP ID to be included with your request traffic. This identifier should be appended to the request URL.
curl https://api.zmok.io/<NETWORK>/<your-app-ID>Use one of these endpoints as your Ethereum client provider.
?> NOTE: Be sure to replace your-app-ID with an APP ID from your ZMOK dashboard
| Network | Endpoint |
|---|---|
| MAINNET | https://api.zmok.io/mainnet/your-app-ID wss://api.zmok.io/mainnet/your-app-ID |
| MAINNET - ARCHIVE | https://api.zmok.io/archive/your-app-ID wss://api.zmok.io/archive/your-app-ID |
| MAINNET - FRONT RUNNING | https://api.zmok.io/fr/your-app-ID wss://api.zmok.io/fr/your-app-ID |
| GOERLI | https://api.zmok.io/testnet/your-app-ID wss://api.zmok.io/testnet/your-app-ID |
Below is a quick command-line example using curl:
?> NOTE: Be sure to replace your-app-ID with an APP ID from your ZMOK dashboard
curl "https://api.zmok.io/mainnet/your-app-ID" \
-X POST \
-H "Content-Type: application/json" \
--data '{"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []}'The result should look something like this:
{"jsonrpc": "2.0","result": "0x657abc", "id":1}Same request could be also made with WebSocket:
wscat -c wss://api.zmok.io/mainnet/your-app-ID
> {"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []}
< {"jsonrpc":"2.0","id":1,"result":"0x657abc"}| Method |
|---|
| eth_accounts |
| eth_blockNumber |
| eth_call |
| eth_chainId |
| eth_estimateGas - "to" parameter is mandatory |
| eth_gasPrice |
| eth_getBalance |
| eth_getBlockByHash |
| eth_getBlockByNumber |
| eth_getBlockTransactionCountByHash |
| eth_getBlockTransactionCountByNumber |
| eth_getCode |
| eth_getLogs |
| eth_getProof |
| eth_getStorageAt |
| eth_getTransactionByBlockHashAndIndex |
| eth_getTransactionByBlockNumberAndIndex |
| eth_getTransactionByHash |
| eth_getTransactionCount |
| eth_getTransactionReceipt |
| eth_getUncleByBlockHashAndIndex |
| eth_getUncleByBlockNumberAndIndex |
| eth_getUncleCountByBlockHash |
| eth_getUncleCountByBlockNumber |
| eth_getWork |
| eth_hashrate |
| eth_mining |
| eth_protocolVersion |
| eth_sendRawTransaction |
| eth_submitWork |
| eth_syncing |
| net_listening |
| net_peerCount |
| net_version |
| web3_clientVersion |
| web3_sha3 |
| Method |
|---|
| eth_newFilter |
| eth_newBlockFilter |
| eth_getFilterChanges |
| eth_uninstallFilter |
Mempool is a waiting area for the transactions that haven't been added to a block and are still unconfirmed. When an Ethereum node receives a transaction, it will propagate the transaction to peer nodes until a Validator approves the transaction and adds it to a new block. Before it’s added to the next block, the pending transaction remains in a staging/waiting area called mempool or txpool.
?> INFO: MAINNET ARCHIVE endpoints do not support mempool methods.
| Method |
|---|
| txpool_content |
| txpool_inspect |
| txpool_status |
| zmk_txpool_status |
| zmk_txpool_content |
| zmk_txpool_search |
| zmk_txpool_query |
?> INFO: ZMOK global Tx mempool - methods zmk_txpool_* are available only for users with Front-running extension.
?> NOTE: Ethereum Pub/Sub subscription support is only supported over "stateful" transports such as WebSocket.
| Method |
|---|
| eth_subscribe |
| eth_unsubscribe |
WebSocket connection drops after 60 seconds of no activity. Can be kept active by calling the latest block every 50 seconds for example. The maximum number of open connections is 25 simultaneously.
Example of how to subscribe to pending transactions from the mempool using Web3.js:
// checker.js
const Web3 = require('web3');
class TransactionChecker {
web3;
web3ws;
watchAddress;
subscription;
constructor(appId, watchAddress) {
this.web3ws = new Web3(new Web3.providers.WebsocketProvider('wss://api.zmok.io/mainnet/' + appId));
this.web3 = new Web3(new Web3.providers.HttpProvider('https://api.zmok.io/mainnet/' + appId));
this.watchAddress = watchAddress.toLowerCase();
}
subscribe(topic) {
this.subscription = this.web3ws.eth.subscribe(topic, (err, res) => {
if (err) console.error(err);
});
}
watchTransactions() {
console.log('Watching all pending transactions...');
this.subscription.on('data', (txHash) => {
setTimeout(async () => {
try {
// console.log("txHash: " + txHash)
let tx = await this.web3.eth.getTransaction(txHash);
if (tx != null) {
if (this.watchAddress == tx.to.toLowerCase()) {
console.log("found: " + {
address: tx.from,
value: this.web3.utils.fromWei(tx.value, 'ether'),
timestamp: new Date()
});
} else {
console.log({
address: tx.from,
value: this.web3.utils.fromWei(tx.value, 'ether'),
timestamp: new Date()
});
}
}
} catch (err) {
console.error(err);
}
}, 60000)
});
}
}
let txChecker = new TransactionChecker( "your-app-ID", '0x3685a78D5b3DB714e74Ea53C072c81CAD9434246');
txChecker.subscribe('pendingTransactions');
txChecker.watchTransactions();Archive nodes are full nodes running with a special option known as "archive mode". Archive nodes have all the historical data of the blockchain since the genesis block. If you need data from blocks before the last 128 blocks, you’ll want to access an archive node. For example, to use calls like eth_getBalance of an ancient address will only be possible with an archive node, to interact with smart contracts deployed much earlier in the blockchain, etc.
?> Archive calls are available for all users and packages. Supported networks are: Mainnet Archive, Goerli.
Mainnet and Mainnet Front-Running (FR) endpoints do not support archive calls, because these endpoints are optimized for performance and their nodes contain only the pruned data.
If you are interested in inspecting historical data (data outside of the most recent 128 blocks), use the following methods:
| Method |
|---|
| eth_getBalance |
| eth_getCode |
| eth_getTransactionCount |
| eth_getStorageAt |
| eth_call |
For support, please email to: support@zmok.io.