Managed Blockchain API and the JSON-RPCs supported with AMB Access Polygon - AMB Access Polygon

Amazon Managed Blockchain (AMB) Access Polygon is in preview release and is subject to change.

Managed Blockchain API and the JSON-RPCs supported with AMB Access Polygon

Amazon Managed Blockchain provides API operations for creating and managing token accessors for AMB Access Polygon. For more information, see the Managed Blockchain API Reference Guide .

The following topic provides a list and reference of the Polygon JSON-RPCs that AMB Access Polygon supports. Each supported JSON-RPC has a brief description of its use. You use the Polygon JSON-RPCs to query and get smart contract data, get transaction details, submit transactions, and other utilities such as running traces on transactions, and estimate fees.

AMB Access Polygon supports the following JSON-RPC methods. Each supported JSON-RPC has a category and a brief description of its utility and its default request quotas. Unique considerations for using the JSON-RPC method with Amazon Managed Blockchain are indicated where applicable.

Note
  • Any methods that aren't listed are not supported.

  • When making calls to the Polygon JSON-RPCs on Amazon Managed Blockchain, you can do so over an HTTPS connection authenticated using the Signature Version 4 signing process. This means that only authorized IAM principals in the AWS account can make Polygon JSON-RPC calls. To do this, AWS credentials (an access key ID and a secret access key) must be provided with the call.

  • You can also use token-based access as a convenient alternative to the Signature Version 4 (SigV4) signing process. If you prioritize security and auditability over convenience, use the SigV4 signing process instead. However, if you use both SigV4 and token-based access, your requests will not work.

  • JSON-RPC batch requests aren't supported on Amazon Managed Blockchain (AMB) Access Polygon for this preview.

  • The Quotas column in the following table lists the quota for each JSON-RPC. Quotas are set in requests per second (RPS) per Region per Polygon network (Mainnet) for each JSON-RPC.

    For increasing your quota, you must contact AWS Support. To contact AWS Support, sign into the AWS Support Center Console. Choose Create case. Choose Technical. Choose Managed Blockchain as your service. Choose Access:Polygon as your Category and General guidance as your Severity. Enter RPC Quota as the Subject and in the Description text box list the JSON-RPC and the quota limits applicable to your needs in RPS per Polygon network per Region. Submit your case.

Topics
    Category JSON-RPC Description Quota Considerations
    Ethereum eth_blockNumber Returns the number of the most recent block. 150
    eth_call Immediately runs a new message call without creating a transaction on the blockchain. 100 eth_call consumes 0 gas, but has a gas parameter for messages that require it.
    eth_chainId Returns an integer value for the currently configured Chain Id value that's introduced in EIP-155. Returns None if no Chain Id is available. 300
    eth_estimateGas Estimates and returns the gas that's required for a transaction without adding the transaction to the blockchain. 10
    eth_feeHistory Returns a collection of historical gas information. 10
    eth_gasPrice Returns the current price per gas in Wei. 100
    eth_getBalance Returns the balance of an account for the specified account address and block identifier. 100
    eth_getBlockByHash Returns information about the block specified using the block hash. 100
    eth_getBlockByNumber Returns information about the block specified using the block number. 150
    eth_getBlockReceipts Returns receipts about the block specified using the block number. 10
    eth_getBlockTransactionCountByHash Returns the number of transactions in the block specified using the block hash. 100
    eth_getBlockTransactionCountByNumber Returns the number of transactions in the block specified using the block number. 100
    eth_getCode Returns the code at the specified account address and block identifier. 100
    eth_getLogs Returns an array of all logs for a specified filter object. 10 You can make eth_getloqs requests on any block range with a 1K block range by default when a contract address is provided. Contracts with high activity may be limited to smaller block ranges. If no contract address is provided, the block range will be 8.
    eth_getRawTransactionByHash Returns the raw form of the transaction specified by the transaction_hash. 150
    eth_getStorageAt Returns the value of the specified storage position for the specified account address and block identifier. 150
    eth_getTransactionByBlockHashAndIndex Returns information about a transaction using the specified block hash and transaction index position. 150
    eth_getTransactionByBlockNumberAndIndex Returns information about a transaction using the specified block number and transaction index position. 150
    eth_getTransactionByHash Returns information about the transaction with the specified transaction hash. 150
    eth_getTransactionCount Returns the number of transactions sent from the specified address and block identifier. 100
    eth_getTransactionReceipt Returns the receipt of the transaction using the specified transaction hash. 150
    eth_getUncleByBlockHashAndIndex Returns information about the uncle block specified using the block hash and uncle index position. 150
    eth_getUncleByBlockNumberAndIndex Returns information about the uncle block specified using the block number and uncle index position. 150
    eth_getUncleCountByBlockHash Returns the number of counts in the uncle specified using the uncle hash. 150
    eth_getUncleCountByBlockNumber Returns the number of counts in the uncle specified using the uncle number. 150
    eth_maxPriorityFeePerGas Returns the fee per gas that's an estimate of how much you can pay as a priority fee, or "tip," to get a transaction included in the current block. 300 Generally you use the value that's returned from this method to set the maxFeePerGas in the subsequent transaction that you're submitting.
    eth_protocolVersion Returns the current Ethereum protocol version. 300
    eth_sendRawTransaction Creates a new message call transaction or a contract creation for signed transactions. 10 Managed Blockchain supports raw transactions only. You must create and sign transactions before sending them.
    Debug debug_traceBlockByHash Returns the possible tracing result number by executing all transactions in the block specified by the block hash with a tracer (Trace Mode required). 10
    debug_traceBlockByNumber Returns the tracing result by executing all transactions in the block specified by number with a tracer (Trace Mode required). 10
    debug_traceCall Returns the number of possible tracing results by executing an eth call within the context of the given block execution (Trace Mode required). 10
    debug_traceTransaction Returns all traces of a given transaction (Trace Mode required). 10
    Net net_version Returns the current network id. 300
    Trace trace_block Returns a full stack trace of all invoked opcodes of all transactions that were included in a block. 10
    trace_call Returns the number of possible tracing results by executing an eth call within the context of the given block execution (Trace Mode required). 10
    trace_transaction Returns all traces of a given transaction (Trace Mode required). 100
    Tx Pool txpool_content Returns all pending and queued transactions. 2
    txpool_status Provides a count of all transactions currently pending inclusion in the next blocks, and those that are queued (being scheduled for future execution only). 10
    Web web3_clientVersion Returns the current client version. 150