diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum.md deleted file mode 100644 index e02fb194..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Arbitrum" -slug: "rpc-arbitrum" -excerpt: "" -category: 65c5e93c623cad004b45d505 -hidden: false -createdAt: "Wed Mar 06 2024 10:35:18 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Mar 06 2024 13:09:53 GMT+0000 (Coordinated Universal Time)" ---- diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_storagerangeat.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_storagerangeat.md deleted file mode 100644 index fe07260e..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_storagerangeat.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: "debug_storageRangeAt" -slug: "rpc-arbitrum-debug_storagerangeat" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - description: "Ethereum RPC" - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 06 2024 10:35:44 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:40:59 GMT+0000 (Coordinated Universal Time)" ---- -[block:html]{"html":"
\n
Archive Method
\n

Only on the full archive nodes. Complex queries might take longer and incur additional cost

\n
"}[/block] - -## Overview - -`debug_storageRangeAt` is an RPC method that allows you to retrieve the contract storage range for a given block and address. This can be useful for developers and auditors who want to inspect the storage state of a specific contract at a particular point in time. This method can also help in debugging and identifying potential issues with contract storage, as well as understanding how storage evolves as transactions are executed. - -## Parameters - -| Name | Type | Required | Description | -| :-------------------- | :------------ | :------- | :---------------------------------------------------------------------------------- | -| blockHash/blockNumber | string/object | yes | The block hash in string format or block number as hexadecimal in the object format | -| txIndex | integer | yes | The transaction index for the point in which we want the list of accounts | -| address | string | yes | The contract address | -| startKey | string | yes | The offset (hash of storage key) | -| limit | string | yes | The number of storage entries to return | - -## Returns - -- **Storage** - An object with hash values, and for each of them the key and value it represents. - - **hash** - The hash value. - - **key** - The key associated with the hash. - - **value** - The value associated with the hash. -- **nextkey** - The hash of next key if further storage in range. Otherwise, not included. - -## Request Example - -```json cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc":"2.0", - "method":"debug_storageRangeAt", - "params":[ - "0xe9793319714333112d41473d33bc06556b6d32d347517b782eb1cdaec296a20b", - 5, - "0xdAC17F958D2ee523a2206206994597C13D831ec7", - "0x00000000000000000000000000000000", - 2 - ], - "id":1 -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.debugStorageRangeAt( -'0x48dfcf43404dffdb3b93a0b0d9982b642b221187bc3ed5c023bdab6c0e863e3d', -1, '0xa41d19F4258a388c639B7CcD938FCE3fb7D05e86', "0x0000000000000000000000000000000000000000000000000000000000000000", 1) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_traceblockbyhash.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_traceblockbyhash.md deleted file mode 100644 index 38ea5d74..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_traceblockbyhash.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: "debug_traceBlockByHash" -slug: "rpc-arbitrum-debug_traceblockbyhash" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "Ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 13:51:30 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:41:16 GMT+0000 (Coordinated Universal Time)" ---- -[block:html]{"html":"
\n
Archive Method
\n

Only on the full archive nodes. Complex queries might take longer and incur additional cost

\n
"}[/block] - -## Overview - -`debug_traceBlockByHash`method allows developers to trace the execution of transactions within a block specified by its hash. This method is particularly useful for debugging purposes, as it provides detailed information about the execution of each transaction within the block, including the type of call, the addresses involved, the value transferred, the gas used, the input data, the output data, and any sub-calls made during the transaction. - -## Parameters - -### 1.blockHash (required) - -A string representing the hash of the block to be traced. - -### 2.tracer (required) - -An object that specifies the tracer to use for the transaction trace, one of the following: - -| Name | Type | Required | Description | -| :------------- | :----- | :------- | :--------------------------------------------------------------------------------------------------- | -| callTracer | string | Yes | Tracks all call frames generated during a transaction, including those at depth 0. | -| prestateTracer | string | Yes | Replays the transaction and monitors every aspect of the state that occurred throughout the process. | - -### tracerConfig - -An object that allows specifying configurations for the tracer: - -| Name | Type | Required | Description | -| :---------- | :------ | :------- | :------------------------------------------------------------------------------ | -| onlyTopCall | boolean | Yes | A boolean indicating whether to trace only the top-level call or all sub-calls. | - -## Returns - -`callTracer` response - -| Name | Description | -| :---------------- | :------------------------------------------------------------------------------------------------------------------------- | -| type of the call | The type of the call. | -| from | The address from which the transaction is sent. | -| to | The address to which the transaction is directed. | -| gas | The integer value of the gas used. | -| transaction value | The specific amount deducted from the sender's account per unit of gas consumed. | -| gasUsed | The total gas consumed during the call, represented in hexadecimal format. | -| input | The input data accompanying the transaction, optionally provided, typically utilised for interacting with smart contracts. | -| output | The data returned as output from the transaction. | -| error | The type of error encountered during the transaction, if any. | -| revertReason | The Solidity revert reason, if any. | -| calls | A list of sub-calls made during the transaction's execution. | - -`prestateTracer` response - -| Name | Description | -| :--------------------- | :------------------------------------------------------------------------------------------------------------------------ | -| smart contract address | The smart contract address linked to the outcome. | -| balance | The balance of the contract , shown in hexadecimal format, and measured in wei. | -| code | The contract's bytecode encoded as a hexadecimal string | -| nonce | The account's nonce connected to the contract, shown as a unsigned integer | -| storage | A collection of pairs showing the storage slots of the contract, with both keys and values encoded in hexadecimal format. | - -## Request Example - -```curl -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method": "debug_traceBlockByHash", - "params": [ - "0x97b49e43632ac70c46b4003434058b18db0ad809617bd29f3448d46ca9085576", - { - "tracer": "callTracer" - } - ], - "id": 1, - "jsonrpc": "2.0" -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.debugTraceBlockByHash( -'0x3c4523b7e8c21e3d68f1c3af3d18e8a87c0d43e35b2c1b7f8f4e87e4d4db9c82', -{ - tracer: 'callTracer', - tracerConfig: { - onlyTopCall: true, - timeout: '5s', - } -} -) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracecall.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracecall.md deleted file mode 100644 index 515859dd..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracecall.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: "debug_traceCall" -slug: "rpc-arbitrum-debug_tracecall" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "Ethereum, rpc" - robots: "index" -createdAt: "Thu Mar 07 2024 09:21:24 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:41:05 GMT+0000 (Coordinated Universal Time)" ---- -[block:html]{"html":"
\n
Archive Method
\n

Only on the full archive nodes. Complex queries might take longer and incur additional cost

\n
"}[/block] - -## Overview - -`debug_traceCall` is an Ethereum RPC method that allows you to execute a given call (message), tracing the steps of its execution. This can be helpful for developers and auditors who want to inspect and analyze the internal operations and state changes of a contract call without modifying the blockchain state. This method can assist in debugging and identifying potential issues with contract execution, as well as understanding how gas is consumed during the execution of a call. - -## Parameters - -### 1. Transaction call object (required) - -`object` - The eth_call data - -| Name | Type | Required | Description | -| :------- | :------ | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| from | string | no | The address the transaction is sent from | -| to | string | yes | The address the transaction is directed to | -| gas | integer | no | The integer of the gas provided for the transaction execution. Although eth_call consumes zero gas, this parameter may still be needed by some executions. | -| gasPrice | integer | no | The integer of the gasPrice used for each paid gas | -| value | integer | no | The integer of the value sent with this transaction | -| data | string | no | The hash of the method signature and encoded parameters. Additional information is available at [Ethereum Contract ABI](https://docs.soliditylang.org/en/v0.7.0/abi-spec.html) | - -### 2. Block parameter (required) - -- hexadecimal block number -- block hash -- The `Tag` "latest", "earliest", "pending", "safe" or "finalized" "Safe" and "finalized" are only available on Ethereum and Arbitrum One chain. [Ethereum documentation](https://ethereum.org/en/developers/docs/apis/json-rpc/#default-block). - -### 3. Trace type (optional) - -- ` The type of tracer` - String - It might be `callTracer` or `prestateTracer` - - `callTracer` - The calltracer keeps track of all call frames, including depth 0 calls, that are made during a transaction. - - `prestateTracer` - The prestateTracer replays the transaction and tracks every part of state that occured during the transaction. -- `tracerConfig` - The object to specify the configurations of the tracer - - `onlyTopCall` - When set to true, this will only trace the primary (top-level) call and not any sub-calls. It eliminates the additional processing for each call frame. - -#### Additional configuration parameters - -- `disableStorage` — when enabled, it prevents tracing of storage changes made by the transaction being analyzed, which can reduce the resource requirements of the analysis. By default, debug_traceTransaction traces both memory and storage changes, but storage tracing can be particularly resource-intensive, especially for large transactions. -- `disableStack` — when enabled, it skips tracing of stack changes made by the transaction being analyzed. -- `disableMemory` — when true, it stops tracing of memory changes made by the transaction being analyzed, reducing resource requirements. -- `disableReturnData` — when true, it prevents the method from tracing the return data of a transaction. This return data tracing can be very demanding on resources, as it requires a lot of time and processing power. -- `timeout` (default: 5s) — allows to customize the method's timeout period for JavaScript-based tracing calls. - -> 🚧 When using a tracer type , `disableMemory`, `disableStorage`, `disableStack`, or `disableReturnData` will not have any effect. When no tracer is selected, the response defaults to [Struct/opcode logger](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#structopcode-logger). - -## Returns - -`callTracer` response: - -| Name | Description | -| :---------------- | :-------------------------------------------------------------------------------------------------------- | -| type of the call | Type of the call | -| from | The transaction sender. | -| to | The address of the transaction recipient. | -| gas | The gas included in the transaction by the sender. | -| transaction value | The actual value per gas deducted from the sender's account. | -| gasUsed | The total used gas by the call. Encoded as hexadecimal. | -| input | The optional input data sent with the transaction, usually used to interact with smart contracts. | -| output | The return value of the call, encoded as a hexadecimal string. | -| error | An error message in case the execution failed. | -| calls | A list of sub-calls made by the contract during the call, each represented as a nested call frame object. | -| revertReason | The reason why the transaction was reverted, returned by the smart contract if any. | - -`prestateTracer` response - -- `smart contract address` — The address of the smart contract associated with the result. - - `balance` — The balance of the contract, expressed in wei and encoded as a hexadecimal string. - - `code` — The bytecode of the contract, encoded as a hexadecimal string. - - `nonce` — The nonce of the account associated with the contract, represented as an unsigned integer. - - `storage` — A map of key-value pairs representing the storage slots of the contract. The keys and values are both encoded as hexadecimal strings. - -`Struct/opcode` response - -- `The transaction trace object:` -- `failed` - Successful or failed -- `gas` - The total consumed gas in the transaction -- `returnValue` - The return value of the executed contract call -- `structLogs` - The trace result of each step: - - `pc` - The current index in bytecode. - - `op` - The name of current executing operation. - - `gas` - The available gas in the execution. - - `gasCost` - The gas cost of the operation. - - `depth` - The number of levels of calling functions. - - `stack` - An array of values in the current stack. - - `storage` - The mapping of the current storage. - - `refund` - The total of current refund value. - - `error` - The error of the execution. - - `memory` - An array of values in the current memory. - -## Request Example - -```json cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method":"debug_traceCall", - "params":[{ - "to":"0x742d35Cc6634C0532925a3b844Bc454e4438f44e" - }, - "latest" - ], - "id":1, - "jsonrpc":"2.0" -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.debugTraceCall({ - "from": "0xa7d9ddbe1f17865597fbd27ec712455208b6b76d", - "to": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "gas": "0x76c0", - "gasPrice": "0x9184e72a000", - "value": "0x9184e72a", - "data": "0x606060..." - }, - "0x1b4", - { - tracer: 'callTracer', - tracerConfig: { - onlyTopCall: true, - timeout: '5s', - } -} -) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracetransaction.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracetransaction.md deleted file mode 100644 index 276ef034..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-debug_tracetransaction.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -title: "debug_traceTransaction" -slug: "rpc-arbitrum-debug_tracetransaction" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "Ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 10:40:52 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:41:10 GMT+0000 (Coordinated Universal Time)" ---- -[block:html]{"html":"
\n
Archive Method
\n

Only on the full archive nodes. Complex queries might take longer and incur additional cost

\n
"}[/block] - -## Overview - -`debug_traceTransaction` RPC method is utilized to trace the execution of a transaction on the Ethereum blockchain. This method is highly beneficial for debugging purposes, as it furnishes comprehensive details regarding the transaction's execution. These details include the type of call, the involved addresses, the transferred value, the gas consumption, the input and output data, any encountered errors, and reasons for reverts if applicable. Moreover, it can enumerate sub-calls made during the transaction's execution. - -## Parameters - -### 1.Transaction Hash (required) - -A string representing the hash of the transaction you want to trace. - -### 2.tracer (required) - -An object that specifies the tracer to use for the transaction trace, one of the following: - -| Name | Type | Required | Description | -| :------------- | :----- | :------- | :--------------------------------------------------------------------------------------------------- | -| callTracer | string | Yes | Tracks all call frames generated during a transaction, including those at depth 0. | -| prestateTracer | string | Yes | Replays the transaction and monitors every aspect of the state that occurred throughout the process. | - -### tracerConfig: - -An object that allows specifying configurations for the tracer: - -| Name | Type | Required | Description | -| :---------- | :------ | :------- | :------------------------------------------------------------------------------ | -| onlyTopCall | boolean | Yes | A boolean indicating whether to trace only the top-level call or all sub-calls. | - -### 3.timeout - -A string specifying the timeout for the trace operation. It's optional. - -### Additional Configuration Parameters - -`disableStorage` — when activated, it blocks the tracking of storage alterations made by the transaction under review, thus diminishing the resources needed for analysis. By default, `debug_traceTransaction` tracks both memory and storage changes, yet storage tracing can be notably demanding on resources, especially with sizable transactions. - -`disableStack` — when enabled, it skips tracing of stack changes made by the transaction being analyzed. - -`disableMemory` — when set to true, it halts the tracing of memory alterations carried out by the transaction under examination, thereby diminishing the necessary resources. - -`disableReturnData` — when enabled, it disables the method from tracing the return data of a transaction. Tracing this return data can impose significant demands on resources, as it entails extensive time and processing power. - -## Returns - -`traceTransaction`response: - -| Name | Description | -| :----------- | :------------------------------------------------------------ | -| type | The type of the call. | -| from | The address from which the transaction is sent. | -| to | The address to which the transaction is directed. | -| value | The integer value sent with the transaction. | -| gas | The integer value of the gas used. | -| input | The data given as input to the transaction. | -| output | The data returned as output from the transaction. | -| error | The type of error encountered during the transaction, if any. | -| revertReason | The Solidity revert reason, if any. | -| calls | A list of sub-calls made during the transaction's execution. | - -## Request Example - -```curl -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method": "debug_traceTransaction", - "params": [ - "0x9e63085271890a141297039b3b711913699f1ee4db1acb667ad7ce304772036b", - { - "tracer": "callTracer" - } - ], - "id": 1, - "jsonrpc": "2.0" -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.debugTraceTransaction('0x920d562e886a0c7c1f07ecee2ee5557f72d3056b205f8811c57e2615a3b6adb0', { - tracer: 'callTracer', - tracerConfig: { - onlyTopCall: true, - timeout: '5s', - } -}) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_blocknumber.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_blocknumber.md deleted file mode 100644 index 15749786..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_blocknumber.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "eth_blockNumber" -slug: "rpc-arbitrum-eth_blocknumber" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 06:52:26 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:00:33 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`eth_blockNumber` method is part of the Ethereum JSON-RPC API, which is used to interact with the Ethereum blockchain. - -This method is particularly useful for various use cases within the blockchain ecosystem, including but not limited to: - -- Monitoring Blockchain Health: By regularly checking the latest block number, developers can monitor the health and activity of the Ethereum blockchain. This can be crucial for applications that rely on the blockchain for their operations, as it helps in identifying any potential issues or delays in block production. -- Synchronization Checks: For applications that interact with the Ethereum blockchain, knowing the latest block number can be essential for synchronization purposes. It helps in ensuring that the application's data is up-to-date with the blockchain's state. -- Transaction Verification: When submitting transactions to the blockchain, knowing the current block number can be useful for setting appropriate gas prices and for verifying transaction confirmations. - -## Parameters - - `eth_blockNumber` method does not accept any parameters, which simplifies its usage. This is because the method is designed to return the most recent block number without needing any additional input from the user. - -## Returns - -The response from the `eth_blockNumber` method is a JSON object containing the following fields: - -| Name | Description | -| :---------- | :------------------------------------------------------------------------------------------------------------- | -| blockNumber | The number of the most recent block on the Ethereum blockchain. The value is returned as a hexadecimal string. | - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_blockNumber", - "params": [] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const latestBlock = await tatum.rpc.blockNumber() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_call.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_call.md deleted file mode 100644 index 610ce884..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_call.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: "eth_call" -slug: "rpc-arbitrum-eth_call" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 06:56:46 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:01:00 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`eth_call` method in Ethereum's JSON-RPC API is used to execute a new message call immediately without creating a transaction on the blockchain. This method is particularly useful for testing and debugging smart contracts, as it allows developers to simulate the execution of contract methods without actually sending transactions to the network. This can help in identifying issues or understanding the behavior of contracts without incurring any gas costs or affecting the blockchain state. Please check the common use cases: - -- Testing Smart Contracts: Before deploying a smart contract, developers can use `eth_call` to test its functionality and ensure it behaves as expected. -- Debugging: It can be used to debug smart contracts by simulating transactions and observing the state changes or return values without affecting the live contract. -- Estimating Gas Costs: Although `eth_call` does not actually send a transaction, it can be used to estimate the gas costs of a transaction by simulating its execution. - -## Parameters - -`Object`: The transaction call object - -- `from`: DATA, 20 Bytes - (optional) The address the transaction is sent from. -- `to`: DATA, 20 Bytes - The address the transaction is directed to. -- `gas`: QUANTITY - (optional) Integer of the gas provided for the transaction execution. eth_call consumes zero gas, but this parameter may be needed by some executions. -- `gasPrice`: QUANTITY - (optional) Integer of the gasPrice used for each paid gas -- `value`: QUANTITY - (optional) Integer of the value sent with this transaction -- `data`: DATA - (optional) Hash of the method signature and encoded parameters. For details see Ethereum Contract ABI in the Solidity documentation ([opens in a new tab](https://docs.soliditylang.org/en/latest/abi-spec.html)) - -`QUANTITY|TAG` : Integer block number, or the string "latest", "earliest" or "pending", see the default block parameter - -## Returns - -The response from the `eth_call` method is a JSON object containing the following fields: - -| Name | Description | -| :--- | :------------------------------------- | -| DATA | The return value of executed contract. | - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "eth_call", - "params": [ - { - "from": "0x47ac0Fb4F2D84898e4D9E7b4DaB3C24507a6D503", - "to": "0xdAC17F958D2ee523a2206206994597C13D831ec7", - "gas": "0x92c0", - "gasPrice": "0x7896e72a000", - "value": "0x0", - "data": "0x70a0823100000000000000000000000047ac0fb4f2d84898e4d9e7b4dab3c24507a6d503" - }, - "latest" - ], - "id": 1 -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.call({ - "to": "0xD31a59c85aE9D8edEFeC411D448f90841571b89c", // Replace with the ERC-20 token contract address, in this case wrapped SOL on Ethereum - "data": "0x70a08231000000000000000000000000F22981C5bF0A717c98781Af04fdc8213fA789F1C" // The function signature for balanceOf(address), followed by the address (F22981C5bF0A717c98781Af04fdc8213fA789F1C) to query, in this case holder of wrapped SOL tokens -}, "latest") - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_chainid.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_chainid.md deleted file mode 100644 index b1d024ba..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_chainid.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: "eth_chainId" -slug: "rpc-arbitrum-eth_chainid" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 22:23:40 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:00:16 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`eth_chainId` method is part of the Ethereum JSON-RPC API, specifically designed to return the current network or chain ID. This method is crucial for ensuring the uniqueness of transactions across different Ethereum networks, as it helps in preventing replay attacks by distinguishing between transactions intended for different networks. The chain ID was introduced as part of EIP-155 to address the issue of transaction replay attacks across different Ethereum networks. - -## Parameters - -`eth_chainId` method does not accept any parameters. This simplicity in its request format allows for a straightforward query to retrieve the current chain ID of the Ethereum network you are interacting with. - -## Returns - -The response to the `eth_chainId` method will be the current chain ID of the Ethereum network you are connected to. This ID is a hexadecimal number that uniquely identifies the network. - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method": "eth_chainId", - "params": [], - "id": 1, - "jsonrpc": "2.0" -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const id = await tatum.rpc.chainId() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_estimategas.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_estimategas.md deleted file mode 100644 index 43709e23..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_estimategas.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: "eth_estimateGas" -slug: "rpc-arbitrum-eth_estimategas" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 07:00:08 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:04:13 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`eth_estimateGas` method in Ethereum's JSON-RPC API is used to estimate the amount of gas that would be required to execute a transaction without actually sending it. This method is particularly useful for determining the appropriate gas limit for a transaction before it is submitted to the network, helping to avoid out-of-gas errors and ensuring that transactions are processed efficiently. - -## Parameters - -`eth_estimateGas` method accepts a single parameter, which is an object containing the details of the transaction you wish to estimate. The object can include the following fields: - -| Name | Type | Required | Description | -| :-------- | :----- | :------- | :------------------------------------------------------------------------------------------------------ | -| from | String | Yes | The address that the transaction is sent from. | -| to | String | Yes | The address the transaction is sent to. | -| gas | String | No | The maximum amount of gas provided for the transaction. | -| gasPrice | String | No | The price of gas in wei. | -| value | String | No | The amount of ether to send in the transaction, in wei. | -| data | String | No | The data payload of the transaction, typically used for contract function calls or contract deployment. | -| nonce | String | No | A fake nonce to set for the account before executing the call. | -| code | String | No | The code to be executed. | -| state | String | No | The state to be used for the execution. | -| stateDiff | String | No | The state diff to be used for the execution | - -## Returns - -The response from the `eth_estimateGas` method is a single value representing the estimated amount of gas that would be used by the transaction. This value is returned as a hexadecimal string. - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/API_KEY/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_estimateGas", - "params": [ - { - "from": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "to": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "value": "0xde0b6b3a7640000", - "data": "0x606060" - } - ] -}' - -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const estimate = await tatum.rpc.estimateGas({ - "from": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "to": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "value": "0xde0b6b3a7640000", - "data": "0x606060" - }) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gasprice.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gasprice.md deleted file mode 100644 index 4b0b209d..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gasprice.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: "eth_gasPrice" -slug: "rpc-arbitrum-eth_gasprice" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 07:29:43 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:04:20 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`eth_gasPrice` method is part of the Ethereum JSON-RPC API, which is used to interact with the Ethereum blockchain. This method specifically returns the current gas price on the Ethereum network in wei. Wei is the smallest denomination of ether, the cryptocurrency used on the Ethereum network. The gas price is a critical parameter for transactions on the Ethereum network, as it determines how much a transaction is willing to pay per unit of gas, which is a measure of computational effort. - -## Parameters - -The` eth_gasPrice` method does not accept any parameters. This means that when you call this method, you do not need to provide any additional information besides the method name itself. - -## Returns - -The response from the` eth_gasPrice` method will be a JSON object containing the result, which is the hexadecimal value of the current gas price in wei. This value is crucial for setting the gas price for transactions, as it directly influences how quickly a transaction is processed by the network. - -## Request & Response Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/API_KEY/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_gasPrice", - "params": [] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const gasPrice = await tatum.rpc.gasPrice() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbyhash.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbyhash.md deleted file mode 100644 index 3e970ba7..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbyhash.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: "eth_getBlockByHash" -slug: "rpc-arbitrum-eth_getblockbyhash" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:05:48 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:01:20 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getBlockByHash` is an Ethereum JSON-RPC method that allows developers to query a specific block in the Ethereum blockchain by its block hash. This method can be used in various scenarios, such as analysing historical transactions, validating the state of the blockchain, or monitoring the progress of mining activities. - -## Parameters - -The `eth_getBlockByHash` method accepts two parameters: - -1. **blockHash**: The hash of the block you want to retrieve information about. - - Type: String - - Example: "0x75e58e08a9f3a23bac9788d5077a9365abb5c29ec1aab70891264051624720af" -2. **fullTransactionDetails**: A boolean value indicating whether to return full transaction details or just transaction hashes. - - Type: Boolean - - Example: True - -## Returns - -The response from the `eth_getBlockByHash` method is a JSON object containing the following fields: - -| Name | Description | -| :--------------- | :---------------------------------------------------------------------------------------------------------------- | -| number | The block number (hexadecimal string). | -| hash | The block hash (32-byte string). | -| parentHash | The hash of the parent block (32-byte string). | -| nonce | The nonce used to generate the block (8-byte string). | -| sha3Uncles | The SHA3 hash of the uncles in the block (32-byte string). | -| logsBloom | The logs bloom filter of the block (256-byte string). | -| transactionsRoot | The root of the transaction trie (32-byte string). | -| stateRoot | The root of the state trie (32-byte string). | -| miner | The address of the miner who mined the block (20-byte string). | -| difficulty | The difficulty of the block (hexadecimal string). | -| totalDifficulty | The total difficulty of the chain up to this block (hexadecimal string). | -| extraData | Extra data included by the miner in the block (byte string). | -| size | The block size in bytes (hexadecimal string). | -| gasLimit | The gas limit for the block (hexadecimal string). | -| gasUsed | The total gas used by all transactions in the block (hexadecimal string). | -| timestamp | The block timestamp (hexadecimal string). | -| transactions | An array of transaction objects or transaction hashes, depending on the `returnFullTransactionObjects` parameter. | -| uncles | An array of uncle block hashes (32-byte strings). | - -If `returnFullTransactionObjects `is true, the transactions field contains transaction objects with the following fields: - -| Name | Description | -| :--------------- | :---------------------------------------------------------------------------------- | -| hash | The block hash (32-byte string). | -| nonce | The nonce used to generate the block (8-byte string). | -| blockHash | The block hash where the transaction is included (32-byte string). | -| blockNumber | The block number where the transaction is included (hexadecimal string). | -| transactionIndex | The index of the transaction in the block (hexadecimal string). | -| from | The sender address (20-byte string). | -| to | The recipient address, or null for contract creation transactions (20-byte string). | -| value | The value being transferred (hexadecimal string). | -| gasPrice | The gas price in wei (hexadecimal string). | -| gas | The gas provided for the transaction (hexadecimal string).. | -| input | The input data for the transaction (byte string). | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "eth_getBlockByHash", - "params": ["0x75e58e08a9f3a23bac9788d5077a9365abb5c29ec1aab70891264051624720af", true], - "id": 1 -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const block = await tatum.rpc.getBlockByHash('0x75e58e08a9f3a23bac9788d5077a9365abb5c29ec1aab70891264051624720af', true) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbynumber.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbynumber.md deleted file mode 100644 index 7563e05f..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockbynumber.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: "eth_getBlockByNumber" -slug: "rpc-arbitrum-eth_getblockbynumber" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:18:55 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:01:37 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getBlockByNumber` is an Ethereum JSON-RPC method that allows developers to query a specific block in the Ethereum blockchain by its block number. This method can be used in various scenarios, such as analyzing historical transactions, validating the state of the blockchain, or monitoring the progress of mining activities. - -## Parameters - -There are two required parameters for this method: - -1. **blockNumber**: The block number of the block to be retrieved. This can be a hexadecimal string or one of the predefined aliases: `"earliest"`, `"latest"`, or `"pending"`. - - Example: "0x1b4" -2. **returnFullTransactionObjects**: A boolean value that determines whether the returned block contains complete transaction objects `(true)` or only transaction hashes `(false)`. - - Example: True - -## Returns - -The response from the `eth_getBlockByNumber` method is a JSON object containing the following fields: - -| Name | Description | -| :--------------- | :---------------------------------------------------------------------------------------------------------------- | -| number | The block number (hexadecimal string). | -| hash | The block hash (32-byte string). | -| parentHash | The hash of the parent block (32-byte string). | -| nonce | The nonce used to generate the block (8-byte string). | -| sha3Uncles | The SHA3 hash of the uncles in the block (32-byte string). | -| logsBloom | The logs bloom filter of the block (256-byte string). | -| transactionsRoot | The root of the transaction trie (32-byte string). | -| stateRoot | The root of the state trie (32-byte string). | -| miner | The address of the miner who mined the block (20-byte string). | -| difficulty | The difficulty of the block (hexadecimal string). | -| totalDifficulty | The total difficulty of the chain up to this block (hexadecimal string). | -| extraData | Extra data included by the miner in the block (byte string). | -| size | The block size in bytes (hexadecimal string). | -| gasLimit | The gas limit for the block (hexadecimal string). | -| gasUsed | The total gas used by all transactions in the block (hexadecimal string). | -| timestamp | The block timestamp (hexadecimal string). | -| transactions | An array of transaction objects or transaction hashes, depending on the `returnFullTransactionObjects` parameter. | -| uncles | An array of uncle block hashes (32-byte strings). | - -If `returnFullTransactionObjects `is true, the transactions field contains transaction objects with the following fields: - -| Name | Description | -| :--------------- | :---------------------------------------------------------------------------------- | -| hash | The block hash (32-byte string). | -| nonce | The nonce used to generate the block (8-byte string). | -| blockHash | The block hash where the transaction is included (32-byte string). | -| blockNumber | The block number where the transaction is included (hexadecimal string). | -| transactionIndex | The index of the transaction in the block (hexadecimal string). | -| from | The sender address (20-byte string). | -| to | The recipient address, or null for contract creation transactions (20-byte string). | -| value | The value being transferred (hexadecimal string). | -| gasPrice | The gas price in wei (hexadecimal string). | -| gas | The gas provided for the transaction (hexadecimal string).. | -| input | The input data for the transaction (byte string). | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getBlockByNumber", - "params": ["latest", true] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const block = await tatum.rpc.getBlockByNumber('latest', true) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockreceipts.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockreceipts.md deleted file mode 100644 index c4b3c4b4..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblockreceipts.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: "eth_getBlockReceipts" -slug: "rpc-arbitrum-eth_getblockreceipts" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "Ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 10:46:43 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:41:22 GMT+0000 (Coordinated Universal Time)" ---- -[block:html]{"html":"
\n
Archive Method
\n

Only on the full archive nodes. Complex queries might take longer and incur additional cost

\n
"}[/block] - -## Overview - -`eth_getBlockReceipts` RPC method is a powerful tool for retrieving the receipts of all transactions included in a block, along with the block header. This method is particularly useful for applications that require detailed information about transactions, such as event logs, gas usage, and the status of transactions. It is supported on nodes running the Erigon client. - -## Parameters - - `eth_getBlockReceipts` method takes a single parameter: the block identifier. This can be a block number (in hex format), a block hash, or one of the special strings "latest" or "earliest". The block identifier specifies which block's transaction receipts you want to retrieve. For example, to get the receipts for the latest block, you would use "latest" as the parameter. - -## Returns - -The response from `eth_getBlockReceipts` includes an array of transaction receipt objects, each containing detailed information about a transaction. Key fields in the response include: - -| Name | Description | -| :---------------- | :------------------------------------------------------------------------------------------------------------------------------------- | -| blockHash | The hash of the block containing the transaction. | -| blockNumber | The number of the block containing the transaction. | -| contractAddress | The address of the contract created by the transaction, if applicable. | -| cumulativeGasUsed | The total amount of gas used in the block up to this transaction. | -| effectiveGasPrice | The actual gas price paid for the transaction. | -| from | The address of the sender of the transaction. | -| gasUsed | The amount of gas used by the transaction. | -| logs | An array of log objects generated by the transaction, including the address, topics, and data of each log. | -| logsBloom | A bloom filter used by light clients to quickly retrieve logs related to the transaction. | -| status | The success status of the transaction, represented as 1 for success or 0 for failure. | -| to | The address of the recipient of the transaction, if applicable. | -| transactionHash | The hash of the transaction. | -| transactionIndex | The index of the transaction within the block. | -| type | The type of the transaction, with 0 indicating a regular transfer and 2 indicating a contract creation or smart contract function call | - -## Request Example - -```curl -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc":"2.0", - "method":"eth_getBlockReceipts", - "params":["0x10f5d58"], - "id":1 -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.getBlockReceipts(10123321) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbyhash.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbyhash.md deleted file mode 100644 index 0a0b5728..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbyhash.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "eth_getBlockTransactionCountByHash" -slug: "rpc-arbitrum-eth_getblocktransactioncountbyhash" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:23:14 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:01:56 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getBlockTransactionCountByHash` is an Ethereum RPC method used to fetch the number of transactions in a block by the block's hash. It is useful when you want to know the total number of transactions included in a specific block and don't want to retrieve the entire block data. This method can be used in various scenarios, such as monitoring the network activity or estimating transaction confirmation times. - -## Parameters - -This method requires a single parameter: - -**blockHash**: The hash of the target block for which the transaction count will be retrieved. It should be a valid 32-byte hex string. - -- Example: `blockHash` :"0x2907402477167193008a0cbbaa8073278c48e8b97bf9ed1a2101f6ad2130dbaf" - -## Returns - -The method returns a single value: - -| Name | Description | -| :--------------- | :------------------------------------------------------------------------------------------------------- | -| transactionCount | The total number of transactions included in the specified block. It is returned as a hexadecimal value. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getBlockTransactionCountByHash", - "params": [ - "0x2907402477167193008a0cbbaa8073278c48e8b97bf9ed1a2101f6ad2130dbaf" - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const response = await tatum.rpc.getBlockTransactionCountByHash('0x2907402477167193008a0cbbaa8073278c48e8b97bf9ed1a2101f6ad2130dbaf') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbynumber.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbynumber.md deleted file mode 100644 index df3ef169..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getblocktransactioncountbynumber.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: "eth_getBlockTransactionCountByNumber" -slug: "rpc-arbitrum-eth_getblocktransactioncountbynumber" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:26:28 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:02:07 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getBlockTransactionCountByNumber` Ethereum JSON-RPC method allows you to retrieve the number of transactions in a specified block. This method is particularly useful when you need to analyze the transaction activity of a specific block. You can use it to gain insights into network usage, analyze the impact of specific events on the Ethereum network, or monitor transaction congestion in certain blocks. - -## Parameters - -This method requires a single parameter: - -**blockNumber**: The block number for which the transaction count should be retrieved. It should be a hex-encoded value representing the block number. - -- Example: block number 0x110E3F0 (17884144) - -## Returns - -The return object is a hex-encoded value representing the number of transactions in the specified block. - -- Example: 0x86 (134 transactions) - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_getBlockTransactionCountByNumber", - "params": ["0x110E3F0"] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const response = await tatum.rpc.getBlockTransactionCountByNumber(17884144) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getcode.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getcode.md deleted file mode 100644 index dde31aba..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getcode.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "eth_getCode" -slug: "rpc-arbitrum-eth_getcode" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:29:35 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:02:16 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getCode` method is part of the Ethereum JSON-RPC API and is used to retrieve the contract code (bytecode) of an account at a specific block number. This method is particularly useful for developers who need to examine the bytecode of a deployed contract, verify the integrity of a deployed contract, analyze contract bytecode for security vulnerabilities, or debug a smart contract. - -## Parameters - -The `eth_getCode` method accepts two parameters: - -1. **address**(string): The address of the contract whose bytecode you want to retrieve. This should be a 20-byte Ethereum address, formatted as a hex string with a 0x prefix. - - Example: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e" -2. **block**(string): The block number at which you want to retrieve the contract code. This can be specified as a hex string or one of the following special keywords: - - `"earliest"`: The first block in the blockchain - - `"latest"`: The most recent block in the blockchain - - `"pending"`: The upcoming block that is being mined - - Example: `"0x1"` or `"latest"` - -## Returns - -The `eth_getCode` method returns a string representing the contract bytecode. The returned value is a hex string with a 0x prefix. - -- If the account has contract code, the returned string will contain the bytecode. -- If the account is not a contract or does not exist, the returned string will be `0x`. - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getCode", - "params": [ - "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "latest" - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const code = await tatum.rpc.getCode('0x742d35Cc6634C0532925a3b844Bc454e4438f44e') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getlogs.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getlogs.md deleted file mode 100644 index e77bcb02..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getlogs.md +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: "eth_getLogs" -slug: "rpc-arbitrum-eth_getlogs" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 07:36:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:02:26 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getLogs` method is an Ethereum JSON-RPC method that allows developers to query logs generated by the Ethereum network, specifically event logs emitted by smart contracts. These logs are an essential part of the Ethereum ecosystem as they provide a way for developers to monitor contract events and track contract state changes. - -This method is particularly useful when building decentralized applications (dApps) that rely on events emitted by smart contracts, as it enables developers to retrieve logs based on specific filter criteria. By using `eth_getLogs`, developers can efficiently track and react to events happening on the Ethereum blockchain. - -## Parameters - -The` eth_getLogs` method takes a single input parameter: an object containing the filter criteria. The filter object can have the following fields: - -- `fromBlock`: (optional) The starting block number for the search. Can be a block number or one of the following strings: `"earliest"`, `"latest"`, or "`pending"`. - - Example: "fromBlock": "0x1" -- `toBlock`: (optional) The ending block number for the search. Can be a block number or one of the following strings: `"earliest"`, `"latest"`, or "`pending"`. - - Example: "toBlock": "0x1" -- `address`: (optional) The address or list of addresses of the contracts to filter logs from. Can be a single address or an array of addresses. - - Example: "address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e" -- `topics`: (optional) An array of up to four 32-byte topics. Topics are order-dependent, and each topic can be an array of topic hashes or null. - - Example: "topics": ["0x123..."] -- `blockhash`: (optional) The block hash to filter logs from. If provided, fromBlock and toBlock are ignored. - - Example: "blockhash": "0xc6ef9..." - -In addition to the above fields, the transactions field in the filter object can be specified to include full transaction details instead of just transaction hashes. This is useful when you need more information about the transactions in which the events were emitted. - -## Returns - -TThe eth_getLogs method returns an array of log objects. Each log object contains the following fields: - -| Name | Description | Example | -| :--------------- | :------------------------------------------------------------------------------ | :-------------------------------------------------------------------------- | -| removed | A boolean indicating whether the log was removed due to a chain reorganization. | "removed": false | -| logIndex | The log index position in the block. | "logIndex": "0x1" | -| transactionIndex | The transaction index position in the block. | "transactionIndex": "0x0" | -| transactionHash | The hash of the transaction that emitted the log. | "transactionHash": "0x88eef..." | -| blockHash | The hash of the block containing the log. | "blockHash": "0xc6ef9..." | -| blockNumber | The block number containing the log. | "blockNumber": "0x1" | -| address | The address of the contract that emitted the log. | "address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e"v | -| data | The data associated with the log. | "data":"0x0000000000000000000000000000000000000000000000000000000000000020" | -| topics | An array of topics (order-dependent) associated with the log. | "topics": ["0x123..."] | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getLogs", - "params": [ - { - "fromBlock": "0x1", - "toBlock": "0x2", - "address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "topics": ["0x123..."] - } - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const logs = await tatum.rpc.getLogs({ address : '0x742d35Cc6634C0532925a3b844Bc454e4438f44e'}) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getproof.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getproof.md deleted file mode 100644 index 6262da3e..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getproof.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: "eth_getProof" -slug: "rpc-arbitrum-eth_getproof" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:01:07 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:02:38 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getProof` is an Ethereum JSON-RPC method that retrieves the Merkle-Patricia proof for an account, storage key-value pairs, and account transaction count. It allows developers to verify the state of an account or storage value at a specific block without needing the entire Ethereum state trie. This method is particularly useful for light clients or off-chain applications that require proof of an account's state or specific storage values. - -## Parameters - -The` eth_getProof` requieres following parameters: : - -- `address`: Data, 20 Bytes - - The address of the account. - - Example: "fromBlock": "0x1" -- `keys`: Array of Data - - An array of storage keys for which the proof should be generated. - - Example: ["0x0000000000000000000000000000000000000000000000000000000000000000"] -- `blockNumber`: Quantity or String - - The block number for which the proof should be generated. - - Example: "0x1" or "latest" - -## Returns - -TThe eth_getProof method returns an object, that contains the following fields: - -[block:parameters] -{ - "data": { - "h-0": "Name", - "h-1": "Description", - "h-2": "Type", - "0-0": "accountProof", - "0-1": "The serialized Merkle-Patricia proof for the account.", - "0-2": "Array of Data", - "1-0": "balance", - "1-1": "The balance of the account at the specified block.", - "1-2": "Quantity", - "2-0": "codeHash", - "2-1": "The hash of the code for the account at the specified block.", - "2-2": "Data, 32 Bytes", - "3-0": "nonce", - "3-1": "The transaction count of the account at the specified block.", - "3-2": "Quantity", - "4-0": "storageProof", - "4-1": "An array of storage proof objects, one for each requested key, containing the following fields: \n`key` - Data, 32 Bytes: The storage key. \n`value` - Quantity: The storage value. \n`proof `- Array of Data: The serialized Merkle-Patricia proof for the key-value pair.", - "4-2": "Array of Object" - }, - "cols": 3, - "rows": 5, - "align": [ - "left", - "left", - "left" - ] -} -[/block] - - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getProof", - "params": [ - "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - [ - "0x0000000000000000000000000000000000000000000000000000000000000000" - ], - "latest" - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.getProof("0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - ["0x0000000000000000000000000000000000000000000000000000000000000000"], - "latest") - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getstorageat.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getstorageat.md deleted file mode 100644 index cb162502..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getstorageat.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: "eth_getStorageAt" -slug: "rpc-arbitrum-eth_getstorageat" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:28:04 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:02:47 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getStorageAt` is an Ethereum JSON-RPC method that allows you to query the storage value of a contract at a given position. It can be used to inspect the internal state of a smart contract. This method is particularly useful for developers, auditors, and analysts who want to examine contract storage values for various purposes, such as debugging, verifying contract behavior, or analyzing data. - -## Parameters - -The` eth_getStorageAt` accepts following parameters: : - -- `address`: The address of the contract you want to query. - - Example: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e" -- `position`: The storage position (slot) you want to query. - - Example: "0x0" -- `blockParameter`: The block number, block hash, or one of the string literals (`"earliest"`,`"latest"`or `"pending"`), representing the point in the blockchain to query the storage value. - - Example: `"latest"` - -## Returns - -The return object is a single string value, representing the storage value at the given position in the contract. - -| Name | Description | -| :----- | :---------------------------------------------------------------- | -| result | The storage value in a 32-byte (64 character) hexadecimal format. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getStorageAt", - "params": [ - "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "0x0", - "latest" - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const response = await tatum.rpc.getStorageAt('0x742d35Cc6634C0532925a3b844Bc454e4438f44e', '0x0') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblockhashandindex.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblockhashandindex.md deleted file mode 100644 index aa1ee6b1..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblockhashandindex.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: "eth_getTransactionByBlockHashAndIndex" -slug: "rpc-arbitrum-eth_gettransactionbyblockhashandindex" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:35:20 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:01 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getTransactionByBlockHashAndIndex` is an Ethereum JSON-RPC method that allows you to fetch the transaction details based on the block hash and the index of the transaction within that block. This method can be useful when you want to retrieve transaction details for a specific transaction without knowing its transaction hash. - -## Usecase - -Use cases for this method may include: - -- Inspecting transaction details for debugging purposes -- Gathering data for transaction analysis -- Fetching transaction information for specific blocks in a block explorer application - -## Parameters - -The `eth_getTransactionByBlockHashAndIndex` method accepts two parameters: - -- `blockHash` (required): The hash of the block containing the transaction. - - Example: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e" -- `transactionIndex`: (required): The index of the transaction within the specified block. The index is a hexadecimal value. - - Example: "0x1" - -## Returns - -The method returns a JSON object containing the following fields: - -| Name | Description | -| :--------------- | :------------------------------------------------------------------------------------------- | -| hash | The transaction hash as a 32-byte hex string. | -| nonce | The number of transactions made by the sender prior to this one. | -| blockHash | The hash of the block in which this transaction is included. | -| blockNumber | The block number in which this transaction is included. | -| transactionIndex | The index of the transaction within the block. | -| from | The address of the sender. | -| to | The address of the recipient. `null ` if the transaction is a contract creation transaction. | -| value | The value transferred in wei. | -| gasPrice | The gas price provided by the sender in wei. | -| gas | The gas limit provided by the sender. | -| input | The data sent along with the transaction. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_getTransactionByBlockHashAndIndex", - "params": [ - "0x2907402477167193008a0cbbaa8073278c48e8b97bf9ed1a2101f6ad2130dbaf", - "0x1" - ] - }' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const tx = await tatum.rpc.getTransactionByBlockHashAndIndex('0x2907402477167193008a0cbbaa8073278c48e8b97bf9ed1a2101f6ad2130dbaf', 1) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblocknumberandindex.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblocknumberandindex.md deleted file mode 100644 index 7f5255f3..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyblocknumberandindex.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: "eth_getTransactionByBlockNumberAndIndex" -slug: "rpc-arbitrum-eth_gettransactionbyblocknumberandindex" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:43:21 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:12 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getTransactionByBlockHashAndIndex` is an Ethereum JSON-RPC method that allows you to fetch the transaction details based on the block hash and the index of the transaction within that block. This method can be useful when you want to retrieve transaction details for a specific transaction without knowing its transaction hash. - -## Usecase - -Use cases for this method may include: - -- Inspecting transaction details for debugging purposes -- Gathering data for transaction analysis -- Fetching transaction information for specific blocks in a block explorer application - -## Parameters - -The `eth_getTransactionByBlockHashAndIndex` method accepts two parameters: - -- `blockHash` (required): The hash of the block containing the transaction. - - Example: 10123321 -- `transactionIndex`: (required): The index of the transaction within the specified block. The index is a hexadecimal value. - - Example: 0 - -## Returns - -The method returns a JSON object containing the following fields: - -| Name | Description | -| :--------------- | :------------------------------------------------------------------------------------------- | -| hash | The transaction hash as a 32-byte hex string. | -| nonce | The number of transactions made by the sender prior to this one. | -| blockHash | The hash of the block in which this transaction is included. | -| blockNumber | The block number in which this transaction is included. | -| transactionIndex | The index of the transaction within the block. | -| from | The address of the sender. | -| to | The address of the recipient. `null ` if the transaction is a contract creation transaction. | -| value | The value transferred in wei. | -| gasPrice | The gas price provided by the sender in wei. | -| gas | The gas limit provided by the sender. | -| input | The data sent along with the transaction. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_getTransactionByBlockNumberAndIndex", - "params": [ - 10123321, - 0 - ] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const tx = await tatum.rpc.getTransactionByBlockNumberAndIndex(10123321, 0) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyhash.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyhash.md deleted file mode 100644 index 8db27853..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionbyhash.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: "eth_getTransactionByHash" -slug: "rpc-arbitrum-eth_gettransactionbyhash" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:47:29 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:29 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getTransactionByHash` is an Ethereum JSON-RPC method that allows you to query transaction details based on its hash. This method is useful when you want to retrieve information about a specific transaction, such as its sender, receiver, value, and more. Common use cases include tracking transaction status, monitoring incoming transactions, or analyzing historical transaction data. - -## Parameters - -The `eth_getTransactionByHash` method takes one parameter: - -- `transactionHash`: The hash of the transaction you want to retrieve. This should be a 32-byte hash string with a 0x prefix. - - Example: 0x97696c2014695e851d85a344cbbc6ae8ab9d386de05cb0230fe50b91c044639b - -## Returns - -The method returns a JSON object containing the following fields: - -| Name | Description | -| :--------------- | :------------------------------------------------------------------------------------------- | -| hash | The transaction hash as a 32-byte hex string. | -| nonce | The number of transactions made by the sender prior to this one. | -| blockHash | The hash of the block in which this transaction is included. | -| blockNumber | The block number in which this transaction is included. | -| transactionIndex | The index of the transaction within the block. | -| from | The address of the sender. | -| to | The address of the recipient. `null ` if the transaction is a contract creation transaction. | -| value | The value transferred in wei. | -| gasPrice | The gas price provided by the sender in wei. | -| gas | The gas limit provided by the sender. | -| input | The data sent along with the transaction. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "eth_getTransactionByHash", - "params": ["0x97696c2014695e851d85a344cbbc6ae8ab9d386de05cb0230fe50b91c044639b"], - "id": 1 -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const tx = await tatum.rpc.getTransactionByHash('0x97696c2014695e851d85a344cbbc6ae8ab9d386de05cb0230fe50b91c044639b') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactioncount.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactioncount.md deleted file mode 100644 index d67dacee..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactioncount.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: "eth_getTransactionCount" -slug: "rpc-arbitrum-eth_gettransactioncount" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 08:50:00 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:35 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getTransactionCount` method is an Ethereum JSON-RPC method that retrieves the number of transactions sent from a given address. It is a useful method for developers who need to keep track of an account's nonce value to avoid transaction collisions or incorrect order of execution. The nonce value is essential for ensuring transaction uniqueness and preventing replay attacks. - -## Usecase - -Use cases for this method include: - -- Determining the nonce value for a new transaction to be sent from a specific address -- Monitoring the number of transactions sent by an address to observe its activity -- Troubleshooting transaction issues and verifying if a transaction was submitted successfully - -## Parameters - -The `eth_getTransactionCount` method accepts two parameters: - -- `address`: The address whose transaction count will be retrieved. - - Example: 0x742d35Cc6634C0532925a3b844Bc454e4438f44e -- `blockParameter `: A string indicating the block number or block state to consider when retrieving the transaction count. - - Possible values: `"earliest"`, `"latest"`, `"pending"`, or a specific block number in hexadecimal format - - Example: "latest" - -## Returns - -The method returns a single value: - -| Name | Description | -| :--------------- | :------------------------------------------------------------------------------------------ | -| transactionCount | A hexadecimal representation of the number of transactions sent from the specified address. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_getTransactionCount", - "params": [ - "0x742d35Cc6634C0532925a3b844Bc454e4438f44e", - "latest" - ] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.getTransactionCount('0x742d35Cc6634C0532925a3b844Bc454e4438f44e', 'latest') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionreceipt.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionreceipt.md deleted file mode 100644 index 337d0cbc..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_gettransactionreceipt.md +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: "eth_getTransactionReceipt" -slug: "rpc-arbitrum-eth_gettransactionreceipt" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 10:52:31 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:46 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getTransactionReceipt` is an Ethereum JSON-RPC method that retrieves the transaction receipt of a given transaction hash. This method is particularly useful when you need to obtain detailed information about a transaction's execution, such as its status (success or failure), gas usage, and logs (events). Common use cases include checking the status of a transaction after it has been mined or inspecting the events emitted by a smart contract during a specific transaction. - -## Parameters - -This method requires a single parameter: - -- `transactionHash`: The hash of the transaction for which you want to obtain the receipt. - - Example: "0x2a4811309750a84058d2fd1bd8dd534bf3a34039ff1b34e29f23a92dfb06449d" - -## Returns - -The method returns an object containing the following fields: - -| Name | Description | -| :---------------- | :-------------------------------------------------------------------------------------------------------- | -| transactionHash | The hash of the transaction. | -| transactionIndex | The transaction's index position in the block. | -| blockHash | The hash of the block where this transaction was mined. | -| blockNumber | The block number where this transaction was mined. | -| from | The address of the sender. | -| to | The address of the receiver. `null `when it's a contract creation transaction. | -| cumulativeGasUsed | The total amount of gas used when this transaction was executed in the block. | -| gasUsed | The amount of gas used by this specific transaction alone. | -| contractAddress | The address of the contract created, if the transaction was a contract creation. Otherwise, `null`. | -| logs | An array of log objects, which were emitted during the transaction. | -| logsBloom | A 256-byte bloom filter, which is a compressed representation of the logs emitted during the transaction. | -| status | The status of the transaction's execution. `"0x1"` indicates success, while `"0x0" `indicates failure. | - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "id": 1, - "method": "eth_getTransactionReceipt", - "params": [ - "0x2a4811309750a84058d2fd1bd8dd534bf3a34039ff1b34e29f23a92dfb06449d" - ] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const tx = await tatum.rpc.getTransactionReceipt('0x2a4811309750a84058d2fd1bd8dd534bf3a34039ff1b34e29f23a92dfb06449d') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblockhash.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblockhash.md deleted file mode 100644 index 0964e059..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblockhash.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "eth_getUncleCountByBlockHash" -slug: "rpc-arbitrum-eth_getunclecountbyblockhash" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 10:58:52 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:03:55 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getUncleCountByBlockHash` method is an Ethereum JSON-RPC method that returns the number of uncles in a specified block by its hash. This method can be useful for gathering information about the performance of the Ethereum network and to analyse the security of the blockchain. - -Uncles are blocks that are not included in the main blockchain but are still valid, and they contribute to the overall security and decentralisation of the Ethereum network. The inclusion of uncles helps prevent centralisation and ensures the mining process remains competitive. - -## Parameters - -The `eth_getUncleCountByBlockHash` method takes one parameter: - -- `blockHash`: The hash of the block for which you want to get the uncle count. - - Example: "0x827d30e914a3adeefabb9d53f70da87e6e0ed3d02a72e7d9ae9bfd1bf123c7a3" - -## Returns - -The return object for this method is a hex-encoded integer representing the number of uncles in the specified block. - -- Example value: "0x1" (1 uncle) - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getUncleCountByBlockHash", - "params": [ - "0x827d30e914a3adeefabb9d53f70da87e6e0ed3d02a72e7d9ae9bfd1bf123c7a3" - ] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.getUncleCountByBlockHash('0x827d30e914a3adeefabb9d53f70da87e6e0ed3d02a72e7d9ae9bfd1bf123c7a3') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblocknumber.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblocknumber.md deleted file mode 100644 index 2105b6d7..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_getunclecountbyblocknumber.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "eth_getUncleCountByBlockNumber" -slug: "rpc-arbitrum-eth_getunclecountbyblocknumber" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 11:01:27 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:04:05 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The `eth_getUncleCountByBlockHash` method is an Ethereum JSON-RPC method that returns the number of uncles in a specified block by its hash. This method can be useful for gathering information about the performance of the Ethereum network and to analyse the security of the blockchain. - -Uncles are blocks that are not included in the main blockchain but are still valid, and they contribute to the overall security and decentralisation of the Ethereum network. The inclusion of uncles helps prevent centralisation and ensures the mining process remains competitive. - -## Parameters - -The ` eth_getUncleCountByBlockHash` method takes one parameter: - -- `blockNumber`: The number of the block for which you want to get the uncle count. - - Example value: 15537345 - -## Returns - -The return object for this method is a hex-encoded integer representing the number of uncles in the specified block. - -- Example value: "0x1" (1 uncle) - -## Request - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_getUncleCountByBlockNumber", - "params": [ - "0xED14C1" - ] -}' - -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const result = await tatum.rpc.getUncleCountByBlockNumber(15537345) - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_maxpriorityfeepergas.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_maxpriorityfeepergas.md deleted file mode 100644 index bdb7de7a..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_maxpriorityfeepergas.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: "eth_maxPriorityFeePerGas" -slug: "rpc-arbitrum-eth_maxpriorityfeepergas" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 07:57:40 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:04:30 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The`eth_maxPriorityFeePerGas` RPC method is specifically designed to return the maximum priority fee per gas that is needed to be included in a block. This method is crucial for developers and users interacting with the Ethereum network, as it provides insights into the current gas fees required for transactions to be processed efficiently. - -## Parameters: - -This method does not accept any parameters. This simplicity allows for a straightforward query to obtain the current maximum priority fee per gas. - -## Returns - -The response from the `eth_maxPriorityFeePerGas` method is a string representing the maximum priority fee per gas in wei. Wei is the smallest denomination of ether, where 1 ether = 1e18 wei. - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/API_KEY/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key:{API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "eth_maxPriorityFeePerGas", - "params": [], - "id": 1 -}' - -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const gasPrice = await tatum.rpc.maxPriorityFeePerGas() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_sendrawtransaction.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_sendrawtransaction.md deleted file mode 100644 index 4f6e24c9..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-eth_sendrawtransaction.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: "eth_sendRawTransaction" -slug: "rpc-arbitrum-eth_sendrawtransaction" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 08:12:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:04:39 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The`eth_sendRawTransaction` RPC method is used to facilitate the transmission of a signed and serialized Ethereum transaction onto the network. This approach proves invaluable when seeking complete oversight of the signing procedure, especially when employing hardware wallets, cold storage solutions, or custom signing libraries. Its versatility shines through in multiple scenarios, including Ether transfers, smart contract interactions, and contract deployments. - -## Parameters - -`Transaction data`: This is a required parameter. It is a hex string that represents the signed transaction data. This data must be prepared and signed offline or through a wallet before being sent to the network. - -## Returns - -The response from the `eth_sendRawTransaction` method is a JSON object containing the following fields: - -| Name | Description | -| :------ | :----------------------------------------------------------------------------------------------------------------- | -| jsonrpc | A string indicating the version of the JSON-RPC protocol. It should be "2.0". | -| id | A number that identifies the request. This should match the id value in the request. | -| result | The transaction hash of the sent transaction. If the transaction is not yet available, this will be the zero hash. | - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "id": 1, - "jsonrpc": "2.0", - "method": "eth_sendRawTransaction", - "params": [ - "0xf86d8201...94a7bc" - ] -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const gasPrice = await tatum.rpc.sendRawTransaction('0x0000.......') - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockattestations.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockattestations.md deleted file mode 100644 index ca3428fb..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockattestations.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: "getBlockAttestations" -slug: "rpc-arbitrum-getblockattestations" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 15:39:50 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Tue Apr 02 2024 08:41:39 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getBlockAttestations`** endpoint allows you to retrieve attestations associated with a specific Ethereum 2.0 Beacon Chain block. - -## Example use cases: - -1. **Attestation Analysis:** Researchers and validators can use this endpoint to analyze attestations made for a specific block. -2. **Validator Operations:** Validators may need to retrieve attestations to check if their attestations have been included in a block. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :------------------------------------------------------------------------------------------------------ | -| **`blockId`** | `string` | Yes | The unique block ID of the Ethereum 2.0 Beacon Chain block for which you want to retrieve attestations. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The **`data`** array contains information about attestations. - - **aggregation_bits** (string): The attester aggregation bits - - **data** (object array): The AttestationData object from the CL spec - - **slot**: The corresponding slot - - **index**: The index - - **beacon_block_root**: The LMD GHOST vote - - **source** (object array): The Checkpoint - - **epoch** (string): The corresponding epoch - - **root** (string): The corresponding root - - **target** (object array): The Checkpoint - - **epoch** (string): The corresponding epoch - - **root** (string): The corresponding root - - **signature** (string): The signature - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify the block ID in camel case -const blockId = '0xabcdef1234567890'; - -// Retrieve attestations for the specified block using the tatum.rpc.beacon.v1.getBlockAttestations method -const attestations = await tatum.rpc.beacon.v1.getBlockAttestations(blockId); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheader.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheader.md deleted file mode 100644 index d620e3ab..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheader.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: "getBlockHeader" -slug: "rpc-arbitrum-getblockheader" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 17:25:56 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:57:40 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getBlockHeader`** endpoint allows you to retrieve a specific beacon block header from the Ethereum 2.0 Beacon Chain based on its unique block ID. - -## Example use cases: - -1. **Header Retrieval:** Developers and network administrators can use this endpoint to fetch the header of a specific beacon block for analysis or verification purposes. -2. **Validator Operations:** Validators may need to retrieve specific beacon block headers for proposing and attesting to blocks. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :------------------------------------------------------------------------------------------------------ | -| **`blockId`** | `string` | Yes | The unique block ID of the Ethereum 2.0 Beacon Chain block for which you want to retrieve attestations. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The `data` object with the following fields: - - **root** (string, hex): The root is a hexadecimal string representing the root hash of the beacon block header. It follows the pattern: ^0x[a-fA-F0-9]{64}$. - - **canonical** (boolean): `true` if the block header is considered canonical, indicating it's part of the main chain. - - **header** (object): The header object contains detailed information about the beacon block header. - - **message** (array): The BeaconBlockHeader object - - **slot** (string): The slot to which this block corresponds - - **proposer_index** (string): The index of validator in validator registry - - **parent_root** (string): The signing merkle root of the parent BeaconBlock - - **state_root** (string): The tree hash merkle root of the BeaconState for the BeaconBlock - - **body_root** (string): The tree hash merkle root of the BeaconBlockBody for the BeaconBlock - - **signature** (string): The signature - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify the block ID -const BlockId = '0xabcdef1234567890'; - -// Retrieve the beacon block header using the getBlockHeader method -const beaconHeader = await tatum.rpc.beacon.v1.getBlockHeader({blockId: BlockId}); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheaders.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheaders.md deleted file mode 100644 index b5a50a5b..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockheaders.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "getBlockHeaders" -slug: "rpc-arbitrum-getblockheaders" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 17:00:22 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:57:50 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getBlockHeaders`** endpoint allows you to retrieve beacon block headers from the Ethereum 2.0 Beacon Chain. These headers contain important information about the chain's progress and state. - -## Example use cases: - -1. **Chain Monitoring:** Developers and network administrators can use this endpoint to monitor the progress and health of the Ethereum 2.0 Beacon Chain. -2. **Validator Operations:** Validators can retrieve beacon block headers to perform various operations, such as proposing and attesting to blocks. - -## Parameters - -| Name | Type | Required | Description | -| :---------------- | :------- | :------- | :------------------------------------------------------------------------------------------------------- | -| **`slot`** | `string` | No | The slot number to fetch beacon block headers for. | -| **`parent_root`** | string | No | The root hash of the parent beacon block header. Fetches beacon block headers for the given parent root. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The **`data`** array contains a list of beacon block headers, where each header has the following structure: - - **root** (string, hex): The root is a hexadecimal string representing the root hash of the beacon block header. It follows the pattern: ^0x[a-fA-F0-9]{64}$. - - **canonical** (boolean): `true` if the block header is considered canonical, indicating it's part of the main chain. - - **header** (object): The header object contains detailed information about the beacon block header. - - **message** (array): The BeaconBlockHeader object - - **slot** (string): The slot to which this block corresponds - - **proposer_index** (string): The index of validator in validator registry - - **parent_root** (string): The signing merkle root of the parent BeaconBlock - - **state_root** (string): The tree hash merkle root of the BeaconState for the BeaconBlock - - **body_root** (string): The tree hash merkle root of the BeaconBlockBody for the BeaconBlock - - **signature** (string): The signature - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Retrieve beacon block headers using the getBlockHeaders method -const beaconHeaders = await tatum.rpc.beacon.v1.getBlockHeaders(); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockroot.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockroot.md deleted file mode 100644 index ce3df774..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getblockroot.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "getBlockRoot" -slug: "rpc-arbitrum-getblockroot" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 17:01:44 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:03 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getBlockRoot`** endpoint allows you to retrieve the root of a specific Ethereum Beacon Chain block or block header. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :------------------------------------------------------------------------------------------------------ | -| **`blockId`** | `string` | Yes | The unique block ID of the Ethereum 2.0 Beacon Chain block for which you want to retrieve attestations. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The `data` object with the following fields: - - **root** (string, hex): The root of the Beacon Block or Block Header is a hexadecimal string representing the root hash of the beacon block header. It follows the pattern: ^0x[a-fA-F0-9]{64}$. - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify the block ID -const blockId = {blockId: 'your-block-id'}; // Replace with the desired block ID - -// Retrieve the root of the specified Ethereum Beacon Chain block or block header -const blockRoot = await tatum.rpc.beacon.v1.getBlockRoot(blockId); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getgenesis.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getgenesis.md deleted file mode 100644 index 9fa5139f..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getgenesis.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "getGenesis" -slug: "rpc-arbitrum-getgenesis" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 17:43:29 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:06 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getGenesis`** endpoint allows you to retrieve critical information about the genesis state of the Ethereum Beacon Chain. - -## Example use cases: - -1. **Network Monitoring:** Network administrators and developers use this data to monitor and analyze the Ethereum 2.0 network's health and progress. -2. **Validator Setup:** Validators joining the Ethereum Beacon Chain network need the genesis information to initialize their nodes correctly. - -## Parameters - -The **`getGenesis`** endpoint does not require any additional parameters. You can simply make a GET request to the endpoint to retrieve the genesis information. - -## Returns - -- **data** (object): The object with the following values: - - **genesis_time** (string): The genesis_time configured for the beacon node, which is the unix time in seconds at which the Eth2.0 chain began - - **genesis_validators_root** (string): The genesis validator root - - **genesis_fork_version** (string): A fork version number - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Retrieve the Ethereum Beacon Chain genesis information -const response = await tatum.rpc.beacon.v1.getGenesis() - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatecommittees.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatecommittees.md deleted file mode 100644 index 451ebe6d..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatecommittees.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: "getStateCommittees" -slug: "rpc-arbitrum-getstatecommittees" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Mon Mar 18 2024 17:32:19 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:16 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateCommittees`** endpoint allows you to retrieve information about committees associated with a specific Ethereum 2.0 Beacon Chain state. - -## Example use cases: - -1. **Committee Analysis: **Researchers and validators can use this endpoint to analyze committees for a specific state, including validator indices and shard assignments. -2. **Validator Operations:** Validators may need to retrieve committee information to participate in shard or crosslink proposals. - -## Parameters - -| Name | Type | Required | Description | -| :------------- | :------- | :------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`state_id`** | `string` | Yes | The state identifier. It can be one of: head (canonical head in node's view), genesis, finalized, justified, slot and stateRoot (hex encoded stateRoot with 0x prefix) | -| **`epoch`** | `string` | No | Fetch committees for the given epoch. If not present, the committees for the epoch of the state will be obtained. | -| **`index`** | `string` | No | Restrict returned values to those matching the supplied committee index. | -| **`slot`** | string | No | Restrict returned values to those matching the supplied slot. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The `data` array contains information about committees. Each committee object in the array includes details related to the committee index, slot, and an array of validators assigned to attest at a specific slot with the same committee index. - - **index** (string): The committee index at a slot - - **`slot`** (string): The slot - - **`validators`** (object array): The list of validator indices assigned to this committee - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Define the parameters object -const params = { - stateId: 'your-state-id', // Replace with the actual state ID you want to use - epoch: '1', // Optional: Fetch committees for a specific epoch - index: '1', // Optional: Restrict returned values to a specific committee index - slot: '1', // Optional: Restrict returned values to a specific slot -}; - -// Retrieve committees information using the getStateCommittees method -const committees = await tatum.rpc.beacon.v1.getStateCommittees(params); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefinalitycheckpoints.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefinalitycheckpoints.md deleted file mode 100644 index 6b234737..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefinalitycheckpoints.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: "getStateFinalityCheckpoints" -slug: "rpc-arbitrum-getstatefinalitycheckpoints" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 17:43:19 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:25 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateFinalityCheckpoints`** endpoint allows you to retrieve the finality checkpoints associated with a specific `stateId`. - -## Example use cases: - -1. **Finality Assessment:** Developers can use finality checkpoints to assess the level of finality reached by the Ethereum Beacon Chain. By examining the `previous_justified`, `current_justified`, and `finalized` checkpoints, they can determine the state of consensus and the security of the network. -2. **Validator Monitoring: **Validators in the Ethereum 2.0 network can use finality checkpoints to monitor the progress and stability of the network. They can track changes in the `previous_justified` and `current_justified` checkpoints to ensure they are participating in a secure and finalized chain. -3. **Network Stability Analysis:** Network administrators and developers can monitor the network's finality checkpoints to assess its stability. Sudden changes or deviations in the `previous_justified`, `current_justified`, and `finalized` checkpoints may indicate issues or attacks on the network, prompting immediate action. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :------------------------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The unique identifier for the Ethereum Beacon Chain state for which you want to retrieve finality checkpoints. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object): The `data` object contains the finality checkpoints with the following structure: - - **`previous_justified`** (object): Provides information about the previous justified beacon block. - - **`epoch`** (string): The corresponding epoch - - **`root`** (string): The corresponding root - - **`current_justified`** (object): Provides information about the current justified beacon block. - - **`epoch`** (string): The corresponding epoch - - **`root`** (string): The corresponding root - - **`finalized`** (object): Provides information about the finalized beacon block. - - **`epoch`** (string): The corresponding epoch - - **`root`** (string): The corresponding root - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify the state ID -const StateId = 'your-state-id'; - -// Retrieve the finality checkpoints using the getStateFinalityCheckpoints method -const finalityCheckpoints = await tatum.rpc.beacon.v1.getStateFinalityCheckpoints({stateId: StateId}); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefork.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefork.md deleted file mode 100644 index fa11cf99..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatefork.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: "getStateFork" -slug: "rpc-arbitrum-getstatefork" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 17:59:10 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:34 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateFork`** endpoint allows you to retrieve information about the fork associated with a specific Ethereum Beacon Chain state. - -## Example use cases: - -1. **Fork Analysis:** Developers can analyze and track forks in the Ethereum Beacon Chain to make informed decisions. -2. **Network Monitoring:** Network administrators and developers use this data to monitor the Ethereum 2.0 network and its forks. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :--------------------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The unique identifier for the Ethereum Beacon Chain state for which you want to retrieve fork information. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object ): The `data` object contains the following properties: - - **`previous_version`** (string, hex): Previous fork version number - - **`current_version`** (string, hex): Current fork version number - - **`epoch`** (string): The epoch number - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Specify the state ID -const StateId = 'your-state-id'; - -// Retrieve the state fork using the getStateFork method -const stateFork = await tatum.rpc.beacon.v1.getStateFork({stateId: StateId}); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstateroot.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstateroot.md deleted file mode 100644 index b146417d..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstateroot.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "getStateRoot" -slug: "rpc-arbitrum-getstateroot" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 16:14:11 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:43 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateRoot`** endpoint allows you to retrieve the state root of a specific Ethereum Beacon Chain state. - -## Example use cases: - -1. **State Verification:** Developers can verify the state of the Ethereum Beacon Chain at a specific state ID. -2. **Custom Queries:** Network administrators and developers can use this data for custom queries and analysis of the Ethereum 2.0 network. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The unique identifier for the Ethereum Beacon Chain state you want to retrieve the root for. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object ): The `data` object contains the following properties: - - **root** (string, hex): The `root` is a hexadecimal string representing the HashTreeRoot of the BeaconState object. It follows the pattern:` ^0x[a-fA-F0-9]{64}$`. - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Specify the state ID -const StateId = 'your-state-id'; - -// Retrieve the state root using the getStateRoot method -const stateRoot = await tatum.rpc.beacon.v1.getStateRoot({stateId: StateId}); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatesynccommittees.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatesynccommittees.md deleted file mode 100644 index a4743a09..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatesynccommittees.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "getStateSyncCommittees" -slug: "rpc-arbitrum-getstatesynccommittees" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 16:49:25 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:58:52 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateSyncCommittees`** endpoint allows you to retrieve information about the sync committees of the Ethereum Beacon Chain for a specific state. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------- | :------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The state identifier. It can be one of: head (canonical head in node's view), genesis, finalized, justified, slot and stateRoot (hex encoded stateRoot with 0x prefix) | -| **`epoch`** | `string` | No | To fetch sync committees for a specific epoch. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object ): The `data` object ccontains the following properties: - - **validators** (object array): An object array of validators participating in sync committees. - - **validator_aggregates** (object array): An object array of aggregated data from validators in sync committees. - -## Request Example - -```Text cURL - -``` -```Text JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify request parameters as one object -const params = { - stateId: 'your-state-id', - epoch: 'your-epoch', // Optional: Replace with the desired epoch -}; - -// Retrieve sync committees for the specified state -const syncCommittees = await tatum.rpc.beacon.v1.getStateSyncCommittees(params); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidator.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidator.md deleted file mode 100644 index 46e414c3..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidator.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: "getStateValidator" -slug: "rpc-arbitrum-getstatevalidator" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 17:15:23 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:59:03 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateValidator`** endpoint allows you to retrieve detailed information about a specific validator in the Ethereum Beacon Chain. This information is valuable for anyone interested in understanding the status and details of a particular validator. - -## Parameters - -| Name | Type | Required | Description | -| :---------------- | :------- | :------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The state identifier. It can be one of: head (canonical head in node's view), genesis, finalized, justified, slot and stateRoot (hex encoded stateRoot with 0x prefix) | -| **`validatorId`** | `string` | No | Either a hex-encoded public key (any bytes48 with a 0x prefix) or a validator index. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object ): The `data` object contain the following structure: - - **index** (string): The index of validator in validator registry - - **balance** (string): The current validator balance in gwei - - **status** (string): The Validator status which could have possible values of: - - **pending_initialized**: When the first deposit is processed, but not enough funds are available (or not yet the end of the first epoch) to get validator into the activation queue - - **pending_queued**: When validator is waiting to get activated, and has enough funds, etc. while in the queue, validator activation epoch keeps changing until it gets to the front and makes it through (finalization is a requirement here too) - - **active_ongoing**: When validator must be attesting and has not initiated any exit - - **active_exiting**: When validator is still active, but filed a voluntary request to exit - - **active_slashed**: When validator is still active, but has a slashed status and is scheduled to exit - - **exited_unslashed**: When validator has reached the regular exit epoch, is not being slashed, and doesn't have to attest any more, but cannot withdraw yet - - **exited_slashed**: When validator has reached the regular exit epoch, but was slashed, have to wait for a longer withdrawal period - - **withdrawal_possible**: After validator has exited, a while later is permitted to move funds and is truly out of the system - - **withdrawal_done**: (not possible in phase0, except slashing full balance) having moved funds away - - **validator** (object): Validator details containing the following fields: - - **pubkey** (string): The validator's BLS public key, uniquely identifying them. \_48-bytes, hex encoded with 0x prefix, case insensitive - - **withdrawal_crendetials** (string): The root of withdrawal credentials - - **effective_balance** (string): The balance at stake in Gwei - - **slashed** (string): The validator is slashed (no longer active) or not - - **activation_elgibility_epoch** (string): When criteria for activation were met - - **activation_epoch** (string): Epoch when validator activated. FAR_FUTURE_EPOCH if not activated - - **exit_epoch** (string): Epoch when validator exited - - **withdrawable_epoch** (string): When validator can withdraw or transfer funds. FAR_FUTURE_EPOCH if not defined - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum'; - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }); - -// Specify the state ID and validator ID -const params = { - stateId: 'your-state-id', - validatorId: 'validator-1', -}; - -// Retrieve information about a specific validator using the getStateValidator method -const validator = await tatum.rpc.beacon.v1.getStateValidator(params); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy(); -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidatorbalances.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidatorbalances.md deleted file mode 100644 index 3bfa724c..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidatorbalances.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "getStateValidatorBalances" -slug: "rpc-arbitrum-getstatevalidatorbalances" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 17:56:47 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:59:15 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateValidatorBalances`** endpoint allows you to retrieve the balances of specific validators within the Ethereum Beacon Chain state. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :----------------- | :------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **`stateId`** | `string` | Yes | The state identifier. It can be one of: head (canonical head in node's view), genesis, finalized, justified, slot and stateRoot (hex encoded stateRoot with 0x prefix) | -| **`id`** | `array of strings` | No | specify the IDs of validators for which you want to retrieve balances. You can provide an array of hex-encoded public keys (any bytes48 with a 0x prefix) or validator indices. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array): The `data` object array contains the following properties: - - **index** (string): The index of validator in validator registry - - **balance** (string): The current validator balance in gwei - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Specify the state ID and optional array of validator IDs -const params = { - state_id: 'your-state-id', - id: ['validator-1', 'validator-2'], // Optional -} - -// Retrieve validator balances using the getStateValidatorBalances method -const validatorBalances = await tatum.rpc.beacon.v1.getStateValidatorBalances(params); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidators.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidators.md deleted file mode 100644 index 6968fd46..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-getstatevalidators.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: "getStateValidators" -slug: "rpc-arbitrum-getstatevalidators" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Wed Mar 20 2024 18:09:48 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:59:38 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -The **`getStateValidator`** endpoint allows you to retrieve detailed information about a specific validator in the Ethereum Beacon Chain. This information is valuable for anyone interested in understanding the status and details of a particular validator. - -## Parameters - -| Name | Type | Required | Description | -| :------------ | :------------- | :------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **`stateId`** | `string` | Yes | The state identifier. It can be one of: head (canonical head in node's view), genesis, finalized, justified, slot and stateRoot (hex encoded stateRoot with 0x prefix) | -| **`id`** | `string array` | No | An array of either hex-encoded public keys (any bytes48 with a 0x prefix) or validator indices. | -| **`status`** | `string array` | No | Validator status specification. Available values: pending_initialized, pending_queued, active_ongoing, active_exiting, active_slashed, exited_unslashed, exited_slashed, withdrawal_possible, withdrawal_done, active, pending, exited, withdrawal. | - -## Returns - -- **execution_optimistic** (boolean): `true` if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the `false` value. -- **finalized** (boolean): If the response mentions the chain's final history picked by forks, it's `true`. Without the field, more calls are needed to compare the requested epoch with the final checkpoint. -- **data** (object array ): The `data` object arrays contain the following structure: - - **index** (string): The index of validator in validator registry - - **balance** (string): The current validator balance in gwei - - **status** (string): The Validator status which could have possible values of: - - **pending_initialized**: When the first deposit is processed, but not enough funds are available (or not yet the end of the first epoch) to get validator into the activation queue - - **pending_queued**: When validator is waiting to get activated, and has enough funds, etc. while in the queue, validator activation epoch keeps changing until it gets to the front and makes it through (finalization is a requirement here too) - - **active_ongoing**: When validator must be attesting and has not initiated any exit - - **active_exiting**: When validator is still active, but filed a voluntary request to exit - - **active_slashed**: When validator is still active, but has a slashed status and is scheduled to exit - - **exited_unslashed**: When validator has reached the regular exit epoch, is not being slashed, and doesn't have to attest any more, but cannot withdraw yet - - **exited_slashed**: When validator has reached the regular exit epoch, but was slashed, have to wait for a longer withdrawal period - - **withdrawal_possible**: After validator has exited, a while later is permitted to move funds and is truly out of the system - - **withdrawal_done**: (not possible in phase0, except slashing full balance) having moved funds away - - **validator** (object): Validator details containing the following fields: - - **pubkey** (string): The validator's BLS public key, uniquely identifying them. \_48-bytes, hex encoded with 0x prefix, case insensitive - - **withdrawal_crendetials** (string): The root of withdrawal credentials - - **effective_balance** (string): The balance at stake in Gwei - - **slashed** (string): The validator is slashed (no longer active) or not - - **activation_elgibility_epoch** (string): When criteria for activation were met - - **activation_epoch** (string): Epoch when validator activated. FAR_FUTURE_EPOCH if not activated - - **exit_epoch** (string): Epoch when validator exited - - **withdrawable_epoch** (string): When validator can withdraw or transfer funds. FAR_FUTURE_EPOCH if not defined - -## Request Example - -```Text cURL - -``` -```javascript JS SDK -// Import necessary libraries and modules -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -// Initialize the Tatum SDK with Ethereum-specific parameters -const tatum = await TatumSDK.init({ network: Network.ETHEREUM }) - -// Specify the state ID, optional ID array, and optional status array -const params = { - stateId: 'your-state-id', - id: ['validator-1', 'validator-2']; // Optional, - status: ['active', 'exited']; // Optional, -} -const idArray = -const statusArray = - -// Retrieve information about validators using the getStateValidators method -const validators = await tatum.rpc.beacon.v1.getStateValidators(params); - -// Destroy Tatum SDK - needed for stopping background jobs -await tatum.destroy() -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_content.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_content.md deleted file mode 100644 index bf547065..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_content.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: "txpool_content" -slug: "rpc-arbitrum-txpool_content" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 16:51:12 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:59:48 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`txpool+content` is specifically designed to return all pending and queued transactions currently in the transaction pool. It's important to note that this method is supported only on Geth, which is a popular Ethereum client. - -## Parameters - -`txpool_content `method does not accept any parameters. This means you can call it without needing to provide any additional information to get the current state of the transaction pool. - -## Returns - -The response from the `txpool_content` method is an array of transaction objects. Each transaction object contains several fields that provide detailed information about the `pending` transaction: - -| Name | Description | -| :------------------- | :----------------------------------------------------------------------- | -| address | The address initiating the transaction. | -| nonce | The nonce of the sending address. | -| blockHash | The hash of the block where the transaction was included. | -| blockNumber | The number of the block where the transaction was included. | -| from | The address of the sender. | -| gas | The total amount of gas units used in the transaction. | -| gasPrice | The price of gas for the transaction. | -| maxFeePerGas | The maximum fee per gas unit that the sender is willing to pay. | -| maxPriorityFeePerGas | The maximum priority fee per gas unit that the sender is willing to pay. | -| hash | The hash of the transaction. | -| input | The encoded transaction input data. | -| to | The address of the recipient. | -| transactionIndex | The index of the transaction within the block. | -| value | The amount of Ether sent with the transaction. | -| type | The type of the transaction. | -| accesslist | The access list for the transaction. | -| chainId | The ID of the chain where the transaction is valid. | -| v | The ECDSA recovery id encoded as a hexadecimal format. | -| r | The ECDSA signature r. | -| s | The ECDSA signature s. | -| yParity | Another value used for transaction signing | - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method": "txpool_content", - "params": [], - "id": 1, - "jsonrpc": "2.0" -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const content = await tatum.rpc.txPoolContent() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_inspect.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_inspect.md deleted file mode 100644 index 3e369b84..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_inspect.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: "txpool_inspect" -slug: "rpc-arbitrum-txpool_inspect" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 18:15:33 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 08:59:57 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - - `txpool_inspect `method is part of the txpool namespace in Ethereum's JSON-RPC API, which provides access to several non-standard RPC methods to inspect the contents of the transaction pool. This method is specifically tailored for developers to quickly see the transactions in the pool and identify any potential issues. It is used to list a textual summary of all the transactions currently pending for inclusion in the next block(s), as well as the ones that are being scheduled for future execution only. - -## Parameters - -The `txpool_inspect` method does not require any parameters. - -## Returns - -The response from `txpool_inspect` is an object with two fields: pending and queued. Each of these fields is an associative array, where each entry maps an origin-address to a batch of scheduled transactions. These batches themselves are maps associating nonces with transactions summary strings: - -| Name | Description | -| :------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| pending | This field contains transactions that are currently pending for inclusion in the next block(s). Each entry in this field maps an origin-address to a batch of transactions. Each transaction batch is a map associating nonces with transactions summary strings. | -| queued | This field contains transactions that are being scheduled for future execution. Similar to the pending field, each entry in this field maps an origin-address to a batch of transactions, with each transaction batch being a map associating nonces with transactions summary strings. | - -The transactions summary strings provide details about each transaction, including the recipient address, the amount of ether being sent (in wei), and the gas price and gas limit (in gwei and gas units, respectively). - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "txpool_inspect", - "id": 1 -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const inspect = await tatum.rpc.txPoolInspect() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_status.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_status.md deleted file mode 100644 index d7b5c204..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-txpool_status.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: "txpool_status" -slug: "rpc-arbitrum-txpool_status" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, RPC" - robots: "index" -createdAt: "Tue Mar 19 2024 18:34:31 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:00:07 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - - `txpool_status` method is part of the Ethereum JSON-RPC API, which is used to query the status of the transaction pool (mempool) on an Ethereum node. This method is particularly useful for developers and analysts who need to monitor the current state of pending and queued transactions in the Ethereum network. - -## Parameters - -`txpool_status` method does not require any parameters. - -## Returns - -`txpool_status` method returns an object containing two fields; pending and queued: - -| Name | Description | -| :------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| pending | This field indicates the number of transactions that are currently pending in the transaction pool. Pending transactions are those that have been broadcast to the network but have not yet been included in a block. | -| queued | This field shows the number of transactions that are queued for future execution. These transactions are not yet ready to be included in a block but are waiting for their turn based on their gas price and nonce. | - -The method would return a JSON object with the current status of the transaction pool, including the number of pending and queued transactions. - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "method": "txpool_status", - "params": [], - "id": 1, - "jsonrpc": "2.0" -}' -``` -```javascript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const status = await tatum.rpc.txPoolStatus() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -``` diff --git a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-web3_clientversion.md b/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-web3_clientversion.md deleted file mode 100644 index bbe5f6c5..00000000 --- a/v1.0/RPC Nodes/rpc-evm/rpc-arbitrum/rpc-ethereum-web3_clientversion.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: "web3_clientVersion" -slug: "rpc-arbitrum-web3_clientversion" -excerpt: "Ethereum RPC" -category: 65c5e93c623cad004b45d505 -hidden: false -metadata: - image: [] - keywords: "ethereum, rpc" - robots: "index" -createdAt: "Tue Mar 19 2024 22:33:09 GMT+0000 (Coordinated Universal Time)" -updatedAt: "Wed Apr 03 2024 09:00:25 GMT+0000 (Coordinated Universal Time)" ---- -## Overview - -`web3_clientVersion` method is part of the Ethereum JSON-RPC API, specifically designed to return the current version of the Ethereum client being used. This method is particularly useful for debugging or when you need to ensure compatibility with specific client versions. - -## Parameters - -This method does not accept any parameters. It is a simple request that does not require any input data to function. - -## Returns - -The response from the `web3_clientVersion `method will be a JSON object containing the result field, which holds the current client version in string format. - -## Request Example - -```curl cURL -curl --location 'https://api.tatum.io/v3/blockchain/node/ethereum-mainnet/' \ ---header 'Content-Type: application/json' \ ---header 'x-api-key: {API_KEY}' \ ---data '{ - "jsonrpc": "2.0", - "method": "web3_clientVersion", - "params": [], - "id": 1 -}' -``` -```typescript JS SDK -// yarn add @tatumio/tatum - -import { TatumSDK, Ethereum, Network } from '@tatumio/tatum' - -const tatum = await TatumSDK.init({network: Network.ETHEREUM}) - -const version = await tatum.rpc.clientVersion() - -await tatum.destroy() // Destroy Tatum SDK - needed for stopping background jobs -```