011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 011 Should fail when calling msgValue with more value than available balance
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 011 Should fail when calling msgValue with more value than available balance
from/to Addresses in transaction to a contract (deployed through HAPI tx) are in evm and long-zero format ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests Formats of addresses in Transaction and Receipt results from/to Addresses in transaction to a contract (deployed through HAPI tx) are in evm and long-zero format
should not return contract bytecode after sefldestruct ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should not return contract bytecode after sefldestruct

"before all" hook for "Function calling HederaTokenService.isToken(token)" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles "before all" hook for "Function calling HederaTokenService.isToken(token)"
"before all" hook for "should execute "eth_getCode" for hts token" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode "before all" hook for "should execute "eth_getCode" for hts token"
"before all" hook in "@api-batch-2 RPC Server Acceptance Tests" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests "before all" hook in "@api-batch-2 RPC Server Acceptance Tests"
"before all" hook in "RPC Server Acceptance Tests" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests "before all" hook in "RPC Server Acceptance Tests"
"eth_call" for non-existing contract address returns 0x ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call "eth_call" for non-existing contract address returns 0x
001 Should call pureMultiply ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 001 Should call pureMultiply
001 Should call pureMultiply ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 001 Should call pureMultiply
002 Should call msgSender ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 002 Should call msgSender
002 Should call msgSender ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 002 Should call msgSender
003 Should call txOrigin ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 003 Should call txOrigin
003 Should call txOrigin ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 003 Should call txOrigin
004 Should call msgSig ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 004 Should call msgSig
004 Should call msgSig ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 004 Should call msgSig
005 Should call addressBalance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 005 Should call addressBalance
005 Should call addressBalance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 005 Should call addressBalance
006 'data' from request body with wrong method signature ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 006 'data' from request body with wrong method signature
006 'data' from request body with wrong method signature ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 006 'data' from request body with wrong method signature
007 'data' from request body with wrong encoded parameter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 007 'data' from request body with wrong encoded parameter
007 'data' from request body with wrong encoded parameter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 007 'data' from request body with wrong encoded parameter
008 should work for missing 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 008 should work for missing 'from' field
008 should work for missing 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 008 should work for missing 'from' field
009 should work for missing 'to' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 009 should work for missing 'to' field
009 should work for missing 'to' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 009 should work for missing 'to' field
010 Should call msgValue ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 010 Should call msgValue
010 Should call msgValue ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 010 Should call msgValue
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 011 Should fail when calling msgValue with more value than available balance
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 011 Should fail when calling msgValue with more value than available balance
012 should work for wrong 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 012 should work for wrong 'from' field
012 should work for wrong 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 012 should work for wrong 'from' field
@release Expect Unsupported Method Error message when subscribing for "other" method ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection @release Expect Unsupported Method Error message when subscribing for "other" method
@release Should execute eth_call on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider @release Should execute eth_call on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_call on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket @release Should execute eth_call on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getBalance on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider @release Should execute eth_getBalance on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getBalance on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket @release Should execute eth_getBalance on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getBlockByHash on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider @release Should execute eth_getBlockByHash on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getBlockByHash on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket @release Should execute eth_getBlockByHash on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getBlockByNumber on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider @release Should execute eth_getBlockByNumber on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getBlockByNumber on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket @release Should execute eth_getBlockByNumber on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getLogs on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Ethers Web Socket Provider @release Should execute eth_getLogs on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getLogs on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Standard Web Socket @release Should execute eth_getLogs on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getStorageAt on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider @release Should execute eth_getStorageAt on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getStorageAt on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket @release Should execute eth_getStorageAt on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getTransactionByHash on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider @release Should execute eth_getTransactionByHash on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getTransactionByHash on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket @release Should execute eth_getTransactionByHash on Standard Web Socket and handle valid requests correctly
@release Should execute eth_getTransactionReceipt on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider @release Should execute eth_getTransactionReceipt on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_getTransactionReceipt on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket @release Should execute eth_getTransactionReceipt on Standard Web Socket and handle valid requests correctly
@release Should execute eth_newFilter on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Ethers Web Socket Provider @release Should execute eth_newFilter on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_newFilter on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Standard Web Socket @release Should execute eth_newFilter on Standard Web Socket and handle valid requests correctly
@release Should execute eth_sendRawTransaction on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider @release Should execute eth_sendRawTransaction on Ethers Web Socket Provider and handle valid requests correctly
@release Should execute eth_sendRawTransaction on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket @release Should execute eth_sendRawTransaction on Standard Web Socket and handle valid requests correctly
@release Should execute web3_clientVersion on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 web3_clientVersion @release Should execute web3_clientVersion on Standard Web Socket and handle valid requests correctly
@release Socket server responds to the eth_chainId event ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection @release Socket server responds to the eth_chainId event
@release Subscribes for contract logs for a specific contract address (using evmAddress) ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events @release Subscribes for contract logs for a specific contract address (using evmAddress)
@release Subscribes for contract logs for a specific contract address (using long zero address) ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events @release Subscribes for contract logs for a specific contract address (using long zero address)
@release captures approve and transferFrom events ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to hts tokens and listens for synthetic log events @release captures approve and transferFrom events
@release captures transfer events ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to hts tokens and listens for synthetic log events @release captures transfer events
@release contract owner transfers tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens @release contract owner transfers tokens
@release contract owner transfers tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens @release contract owner transfers tokens
@release fail "eth_getTransactionReceipt" on precheck with wrong nonce error when sending a tx with a higher nonce ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks @release fail "eth_getTransactionReceipt" on precheck with wrong nonce error when sending a tx with a higher nonce
@release fail "eth_getTransactionReceipt" on precheck with wrong nonce error when sending a tx with the same nonce twice ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks @release fail "eth_getTransactionReceipt" on precheck with wrong nonce error when sending a tx with the same nonce twice
@release fail "eth_getTransactionReceipt" on submitting with wrong nonce error when sending a tx with the same nonce twice ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks @release fail "eth_getTransactionReceipt" on submitting with wrong nonce error when sending a tx with the same nonce twice
@release returns the total amount of tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 balanceOf when the requested account has some tokens @release returns the total amount of tokens
@release returns the total amount of tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 total supply @release returns the total amount of tokens
@release returns the total amount of tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 balanceOf when the requested account has some tokens @release returns the total amount of tokens
@release returns the total amount of tokens ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 total supply @release returns the total amount of tokens
@release should be able to call eth_getFilterChanges for NEW_BLOCK filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to call eth_getFilterChanges for NEW_BLOCK filter
@release should be able to create a log filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to create a log filter
@release should be able to create a newBlock filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to create a newBlock filter
@release should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall false
@release should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall false
@release should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall true
@release should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall true
@release should call eth_gasPrice ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_gasPrice @release should call eth_gasPrice
@release should correctly execute "eth_getBalance" with block number in the last 15 minutes with several txs around that time ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should correctly execute "eth_getBalance" with block number in the last 15 minutes with several txs around that time
@release should deploy a contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs @release should deploy a contract
@release should execute "eth_call" request to Basic contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to Basic contract
@release should execute "eth_call" request to simulate deploying a contract with `to` field being empty/undefined ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to simulate deploying a contract with `to` field being empty/undefined
@release should execute "eth_call" request to simulate deploying a contract with `to` field being null ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to simulate deploying a contract with `to` field being null
@release should execute "eth_estimateGas" for contract call ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas @release should execute "eth_estimateGas" for contract call
@release should execute "eth_estimateGas" for contract call, using a standard websocket ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_estimateGas @release should execute "eth_estimateGas" for contract call, using a standard websocket
@release should execute "eth_estimateGas" for contract call, using a websocket provider ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_estimateGas @release should execute "eth_estimateGas" for contract call, using a websocket provider
@release should execute "eth_estimateGas" for existing account ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas @release should execute "eth_estimateGas" for existing account
@release should execute "eth_estimateGas" hollow account creation ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas @release should execute "eth_estimateGas" hollow account creation
@release should execute "eth_getBalance" for contract with id converted to evm_address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" for contract with id converted to evm_address
@release should execute "eth_getBalance" for newly created account with 1 HBAR ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" for newly created account with 1 HBAR
@release should execute "eth_getBalance" with block number in the last 15 minutes for account that has performed contract deploys/calls ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with block number in the last 15 minutes for account that has performed contract deploys/calls
@release should execute "eth_getBalance" with block number in the last 15 minutes ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with block number in the last 15 minutes
@release should execute "eth_getBalance" with latest block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with latest block hash
@release should execute "eth_getBalance" with latest block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with latest block number
@release should execute "eth_getBalance" with one block behind latest block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with one block behind latest block number
@release should execute "eth_getBalance" with pending ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release should execute "eth_getBalance" with pending
@release should execute "eth_getBlockByHash", hydrated transactions = true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls @release should execute "eth_getBlockByHash", hydrated transactions = true
@release should execute "eth_getBlockByNumber", hydrated transactions = true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls @release should execute "eth_getBlockByNumber", hydrated transactions = true
@release should execute "eth_getBlockTransactionCountByHash" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls @release should execute "eth_getBlockTransactionCountByHash"
@release should execute "eth_getBlockTransactionCountByNumber" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls @release should execute "eth_getBlockTransactionCountByNumber"
@release should execute "eth_getCode" for contract evm_address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode @release should execute "eth_getCode" for contract evm_address
@release should execute "eth_getCode" for contract with id converted to evm_address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode @release should execute "eth_getCode" for contract with id converted to evm_address
@release should execute "eth_getTransactionByBlockHashAndIndex" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should execute "eth_getTransactionByBlockHashAndIndex"
@release should execute "eth_getTransactionByBlockNumberAndIndex" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should execute "eth_getTransactionByBlockNumberAndIndex"
@release should execute "eth_getTransactionByHash" for existing transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should execute "eth_getTransactionByHash" for existing transaction
@release should execute "eth_getTransactionCount" contract latest ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract latest
@release should execute "eth_getTransactionCount" contract with id converted to evm_address historic ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract with id converted to evm_address historic
@release should execute "eth_getTransactionCount" contract with id converted to evm_address latest ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract with id converted to evm_address latest
@release should execute "eth_getTransactionCount" for account with id converted to evm_address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" for account with id converted to evm_address
@release should execute "eth_getTransactionCount" historic ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" historic
@release should execute "eth_getTransactionCount" primary ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" primary
@release should execute "eth_getTransactionCount" with block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" with block hash
@release should fail to execute "eth_getTransactionReceipt" for hash of London transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should fail to execute "eth_getTransactionReceipt" for hash of London transaction
@release should return the code ethers WebSocketProvider ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getCode @release should return the code ethers WebSocketProvider
@release should return the code through a websocket ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getCode @release should return the code through a websocket
@release should return the right "effectiveGasPrice" for SYNTHETIC Contract Call transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should return the right "effectiveGasPrice" for SYNTHETIC Contract Call transaction
@release should return the right "effectiveGasPrice" for SYNTHETIC HTS transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release should return the right "effectiveGasPrice" for SYNTHETIC HTS transaction
@release should subscribe to newHeads and receive a valid JSON RPC response ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Configuration given WS_NEW_HEADS_ENABLED=undefined are set @release should subscribe to newHeads and receive a valid JSON RPC response
@release-light, @release should execute "eth_estimateGas" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas @release-light, @release should execute "eth_estimateGas"
@release-light, @release should execute "eth_getBalance" for contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance @release-light, @release should execute "eth_getBalance" for contract
@release-light, @release should execute "eth_getTransactionReceipt" for hash of 2930 transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release-light, @release should execute "eth_getTransactionReceipt" for hash of 2930 transaction
@release-light, @release should execute "eth_getTransactionReceipt" for hash of London transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release-light, @release should execute "eth_getTransactionReceipt" for hash of London transaction
@release-light, @release should execute "eth_getTransactionReceipt" for hash of legacy transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release-light, @release should execute "eth_getTransactionReceipt" for hash of legacy transaction
@release-light, @release should execute "eth_sendRawTransaction" for legacy EIP 155 transactions ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls @release-light, @release should execute "eth_sendRawTransaction" for legacy EIP 155 transactions
Cache set by one instance can be accessed by another ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache Cache set by one instance can be accessed by another
Call to HTS token from non-existing account returns error ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Negative tests Call to HTS token from non-existing account returns error
Call to allowance method of an HTS token with non-existing owner account in call data returns error ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Negative tests Call to allowance method of an HTS token with non-existing owner account in call data returns error
Call to allowance method of an HTS token with non-existing spender account in call data returns error ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Negative tests Call to allowance method of an HTS token with non-existing spender account in call data returns error
Call to non-existing HTS token returns 0x ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Negative tests Call to non-existing HTS token returns 0x
Calling eth_subscribe Logs with a non existent address should fail ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe ethSubscribe Logs Params Validations Calling eth_subscribe Logs with a non existent address should fail
Calling eth_subscribe Logs with an empty address should fail ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe ethSubscribe Logs Params Validations Calling eth_subscribe Logs with an empty address should fail
Calling eth_subscribe Logs with an invalid topics should fail ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe ethSubscribe Logs Params Validations Calling eth_subscribe Logs with an invalid topics should fail
Calling eth_unsubscribe decrements the internal counters ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection subscription limits Calling eth_unsubscribe decrements the internal counters
Closes connections to the server on webSocket close ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Closes connections to the server on webSocket close
Connection TTL is enforced, should close all connections ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection TTL Connection TTL is enforced, should close all connections
Correctly performs set, get and delete operations ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache Correctly performs set, get and delete operations
Correctly sets TTL time ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache Correctly sets TTL time
Does not allow more connections from the same IP than the specified limit ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe IP connection limits Does not allow more connections from the same IP than the specified limit
Does not allow more connections than the connection limit ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection limit Does not allow more connections than the connection limit
Does not allow more subscriptions per connection than the specified limit with newHeads ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Configuration given WS_SUBSCRIPTION_LIMIT=2, WS_NEW_HEADS_ENABLED=true are set Does not allow more subscriptions per connection than the specified limit with newHeads
Does not allow more subscriptions per connection than the specified limit ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection subscription limits Does not allow more subscriptions per connection than the specified limit
Establishes multiple connections ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Establishes multiple connections
Expect Unsupported Method Error message when subscribing for newPendingTransactions method ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Expect Unsupported Method Error message when subscribing for newPendingTransactions method
Falls back to local cache for REDIS_ENABLED !== true ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache given REDIS_ENABLED=false are set Falls back to local cache for REDIS_ENABLED !== true
Function calling HederaTokenService.isToken(token) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles Function calling HederaTokenService.isToken(token)
Function with HederaTokenService.isFrozen(token, account) - using long zero address ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.isFrozen(token, account) - using long zero address
Function with HederaTokenService.isKyc(token, account) - using long zero account address ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.isKyc(token, account) - using long zero account address
Function with IERC20(token).allowance(owner, spender) - using both evm addresses ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC20 Function with IERC20(token).allowance(owner, spender) - using both evm addresses
Function with IERC20(token).balanceOf(account) - using evm address ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC20 Function with IERC20(token).balanceOf(account) - using evm address
Function with IERC20(token).balanceOf(account) - using long zero address ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC20 Function with IERC20(token).balanceOf(account) - using long zero address
Function with IERC20(token).totalSupply() ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC20 Function with IERC20(token).totalSupply()
Function with IERC721Enumerable(token).totalSupply() ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC721Enumerable Function with IERC721Enumerable(token).totalSupply()
Function with IERC721Metadata(token).name() ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC721Metadata Function with IERC721Metadata(token).name()
Function with IERC721Metadata(token).symbol() ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC721Metadata Function with IERC721Metadata(token).symbol()
Function with IERC721Metadata(token).tokenURI(tokenId) ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through IERC721Metadata Function with IERC721Metadata(token).tokenURI(tokenId)
HBAR limiter is updated within acceptable tolerance range in relation to actual spent amount by the relay operator ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit HBAR limiter is updated within acceptable tolerance range in relation to actual spent amount by the relay operator
Multiple ws connections and multiple subscriptions per connection ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Multiple ws connections and multiple subscriptions per connection
Pure method revertWithCustomErrorPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithCustomErrorPure returns tx receipt
Pure method revertWithNothingPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithNothingPure returns tx receipt
Pure method revertWithPanicPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithPanicPure returns tx receipt
Pure method revertWithStringPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithStringPure returns tx receipt
Relay can execute "eth_getCode" for ERC20 contract with evmAddress ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract Relay can execute "eth_getCode" for ERC20 contract with evmAddress
Relay can execute "eth_getCode" for ERC20 contract with evmAddress ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token Relay can execute "eth_getCode" for ERC20 contract with evmAddress
Returns revert message for pure methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert message for pure methods
Returns revert message for view methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert message for view methods
Returns revert reason in receipt for payable methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert reason in receipt for payable methods
Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget
Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should allow different accounts associated in the same HbarSpendingPlan to contribute to the same budget
Should eventually exhaust the hbar limit for EXTENDED user and still allow another EXTENDED user to make calls ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should eventually exhaust the hbar limit for EXTENDED user and still allow another EXTENDED user to make calls
Should eventually exhaust the hbar limit for PRIVILEGED user and still allow another PRIVILEGED user to make calls ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should eventually exhaust the hbar limit for PRIVILEGED user and still allow another PRIVILEGED user to make calls
Should eventually exhaust the total HBAR limits after many large contract deployments by different tiered users ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Multiple users with different tiers Should eventually exhaust the total HBAR limits after many large contract deployments by different tiered users
Should execute eth_blockNumber on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 eth_blockNumber Ethers Web Socket Provider Should execute eth_blockNumber on Ethers Web Socket Provider and handle valid requests correctly
Should execute eth_blockNumber on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 eth_blockNumber Standard Web Socket Should execute eth_blockNumber on Standard Web Socket and handle valid requests correctly
Should execute eth_blockNumber requests with undefined params and receive expected result ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 JSON-RPC requests validation Request with undefined params Should execute eth_blockNumber requests with undefined params and receive expected result
Should execute eth_chainId requests with undefined params and receive expected result ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 JSON-RPC requests validation Request with undefined params Should execute eth_chainId requests with undefined params and receive expected result
Should execute eth_gasPrice on Ethers Web Socket Provider and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 eth_gasPrice Ethers Web Socket Provider Should execute eth_gasPrice on Ethers Web Socket Provider and handle valid requests correctly
Should execute eth_gasPrice on Standard Web Socket and handle valid requests correctly ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 eth_gasPrice Standard Web Socket Should execute eth_gasPrice on Standard Web Socket and handle valid requests correctly
Should execute eth_sendRawTransaction on Ethers Web Socket Provider for the deterministic deployment transaction ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should execute eth_sendRawTransaction on Ethers Web Socket Provider for the deterministic deployment transaction
Should execute eth_sendRawTransaction on Standard Web Socket for the deterministic deployment transaction ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should execute eth_sendRawTransaction on Standard Web Socket for the deterministic deployment transaction
Should execute eth_sendRawTransaction requests with undefined params and receive MISSING_REQUIRED_PARAMETER error ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 JSON-RPC requests validation Request with undefined params Should execute eth_sendRawTransaction requests with undefined params and receive MISSING_REQUIRED_PARAMETER error
Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":"0x","data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":"0x","data":"0x18160ddd"},"latest"]]
Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":"0xabcdef","data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":"0xabcdef","data":"0x18160ddd"},"latest"]]
Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":123,"data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider Should fail eth_call on Ethers Web Socket Provider and handle invalid TX_INFO. params=[[{"to":123,"data":"0x18160ddd"},"latest"]]
Should fail eth_call on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{ to: '0xabcdef', data: '0x1a2b3c4d' },36,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider Should fail eth_call on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{ to: '0xabcdef', data: '0x1a2b3c4d' },36,]
Should fail eth_call on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{},false,0x0] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Ethers Web Socket Provider Should fail eth_call on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{},false,0x0]
Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":"0x","data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":"0x","data":"0x18160ddd"},"latest"]]
Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":"0xabcdef","data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":"0xabcdef","data":"0x18160ddd"},"latest"]]
Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":123,"data":"0x18160ddd"},"latest"]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket Should fail eth_call on Standard Web Socket and handle invalid TX_INFO. params=[[{"to":123,"data":"0x18160ddd"},"latest"]]
Should fail eth_call on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{ to: '0xabcdef', data: '0x1a2b3c4d' },36,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket Should fail eth_call on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{ to: '0xabcdef', data: '0x1a2b3c4d' },36,]
Should fail eth_call on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{},false,0x0] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_call Standard Web Socket Should fail eth_call on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[{},false,0x0]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,36] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,36]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhedera]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,latest]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,latest]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Ethers Web Socket Provider Should fail eth_getBalance on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,36] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,36]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhedera]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,latest]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,latest]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBalance Standard Web Socket Should fail eth_getBalance on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,54] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,54]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,false,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,false,39]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true]
Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Ethers Web Socket Provider Should fail eth_getBlockByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,54] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,54]

Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,false,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,false,39]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,true,39]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true]
Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByHash Standard Web Socket Should fail eth_getBlockByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,0xhbar]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,54] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,54]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,true,39]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xnetwork,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xnetwork,false]
Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Ethers Web Socket Provider Should fail eth_getBlockByNumber on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,0xhbar]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,54] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,54]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,true,39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36,true,39]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x36]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar,false]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhedera,true]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xnetwork,false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xnetwork,false]
Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-1 eth_getBlockByNumber Standard Web Socket Should fail eth_getBlockByNumber on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Ethers Web Socket Provider Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]]
Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Ethers Web Socket Provider Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]]
Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Ethers Web Socket Provider Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]]
Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0xhedera","fromBlock":"latest","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Ethers Web Socket Provider Should fail eth_getLogs on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0xhedera","fromBlock":"latest","toBlock":"latest"}]]
Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Standard Web Socket Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]]
Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Standard Web Socket Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]]
Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Standard Web Socket Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]]
Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0xhedera","fromBlock":"latest","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getLogs Standard Web Socket Should fail eth_getLogs on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0xhedera","fromBlock":"latest","toBlock":"latest"}]]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,0x0] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,0x0]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,latest]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,36,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,36,latest]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Ethers Web Socket Provider Should fail eth_getStorageAt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,0x0] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,0x0]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[,]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,0xhbar,latest]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,36,latest] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,36,latest]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000]
Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getStorageAt Standard Web Socket Should fail eth_getStorageAt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[txHash] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Ethers Web Socket Provider Should fail eth_getTransactionByHash on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[txHash]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[txHash] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionByHash Standard Web Socket Should fail eth_getTransactionByHash on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[txHash]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[63] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[63]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Ethers Web Socket Provider Should fail eth_getTransactionReceipt on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[63] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[63]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_getTransactionReceipt Standard Web Socket Should fail eth_getTransactionReceipt on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Ethers Web Socket Provider Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]]
Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Ethers Web Socket Provider Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]]
Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Ethers Web Socket Provider Should fail eth_newFilter on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]]
Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Standard Web Socket Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[]]
Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Standard Web Socket Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"0xhedera","toBlock":"latest"}]]
Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_newFilter Standard Web Socket Should fail eth_newFilter on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[[{"address":"0x0000000000000000000000000000000000000000","fromBlock":"latest","toBlock":"0xhedera"}]]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Ethers Web Socket Provider Should fail eth_sendRawTransaction on Ethers Web Socket Provider and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,hbar]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0x0000000000000000000000000000000000000000,rpc,invalid]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xHedera]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[0xhbar]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[39]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[66]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[abc]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[false]
Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true] ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-2 eth_sendRawTransaction Standard Web Socket Should fail eth_sendRawTransaction on Standard Web Socket and throw predefined.INVALID_PARAMETERS if the request's params variable is invalid. params=[true]
Should ignore invalid params in filter object and still successfully call eth_subscribe Logs  ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe ethSubscribe Logs Params Validations Should ignore invalid params in filter object and still successfully call eth_subscribe Logs 
Should increase the amount spent of the spending plan by the transaction cost ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers EXTENDED Tier Should increase the amount spent of the spending plan by the transaction cost
Should increase the amount spent of the spending plan by the transaction cost ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Preconfigured Tiers PRIVILEGED Tier Should increase the amount spent of the spending plan by the transaction cost
Should reject the requests because of the invalid JSON-RPC methods ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 JSON-RPC requests validation Request  & Method Validations Should reject the requests because of the invalid JSON-RPC methods
Should reject the requests because of the invalid JSON-RPC requests ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-1 JSON-RPC requests validation Request  & Method Validations Should reject the requests because of the invalid JSON-RPC requests
Should reset limit for requests ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should reset limit for requests
Should return a batch of requests ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Batch Request Test Suite BATCH_REQUESTS_ENABLED = true Should return a batch of requests
Should return unsupported method when WS_NEW_HEADS_ENABLED is set to false ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Configuration given WS_NEW_HEADS_ENABLED=false are set Should return unsupported method when WS_NEW_HEADS_ENABLED is set to false
Should submit batch requests to WS server and receive IPRateLimitExceeded error until rate limit is reached ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should submit batch requests to WS server and receive IPRateLimitExceeded error until rate limit is reached
Should submit single requests to WS server and receive IPRateLimitExceeded error until rate limit is reached ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should submit single requests to WS server and receive IPRateLimitExceeded error until rate limit is reached
Subscribe and Unsubscribe ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Subscribe and Unsubscribe
Subscribe and receive log event and unsubscribe ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection Subscribe and receive log event and unsubscribe
Subscribe to multiple contracts on same subscription Should fail with INVALID_PARAMETER due to feature flag disabled ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection given WS_MULTIPLE_ADDRESSES_ENABLED=false are set Subscribe to multiple contracts on same subscription Should fail with INVALID_PARAMETER due to feature flag disabled
Subscribe to multiple contracts on same subscription ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection given WS_MULTIPLE_ADDRESSES_ENABLED=true are set Subscribe to multiple contracts on same subscription
Subscribes for contract logs for a single topic ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events Subscribes for contract logs for a single topic
Subscribes for contract logs for address and multiple topics ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events Subscribes for contract logs for address and multiple topics
Subscribes for contract logs for multiple topics ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events Subscribes for contract logs for multiple topics
Subscribes for debug ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events Subscribes for debug
Subscribing for contract logs for a specific contract address and a wrong topic. ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Subscribes to log events Subscribing for contract logs for a specific contract address and a wrong topic.
Type 3 transactions are not supported for eth_sendRawTransaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Shard Blob Transactions Type 3 transactions are not supported for eth_sendRawTransaction
When JSON is invalid, expect INVALID_REQUEST Error message ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection When JSON is invalid, expect INVALID_REQUEST Error message
decreases the spender allowance ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance decreases the spender allowance
decreases the spender allowance ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance decreases the spender allowance
emits a transfer event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance emits a transfer event
emits a transfer event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens emits a transfer event
emits a transfer event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance emits a transfer event
emits a transfer event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens emits a transfer event
emits an approval event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance emits an approval event
emits an approval event ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance emits an approval event
establishes connection ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection establishes connection
eth_call contract revert returns 200 http status ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call eth_call contract revert returns 200 http status
from/to Addresses in transaction between accounts are in evm format ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests Formats of addresses in Transaction and Receipt results from/to Addresses in transaction between accounts are in evm format
from/to Addresses in transaction to a contract (deployed through HAPI tx) are in evm and long-zero format ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests Formats of addresses in Transaction and Receipt results from/to Addresses in transaction to a contract (deployed through HAPI tx) are in evm and long-zero format
from/to Addresses in transaction to a contract (deployed through the relay) are in evm and long-zero format ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests Formats of addresses in Transaction and Receipt results from/to Addresses in transaction to a contract (deployed through the relay) are in evm and long-zero format
from/to Addresses when transferring HTS tokens to the tokenAddress are in evm and long-zero format ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests Formats of addresses in Transaction and Receipt results from/to Addresses when transferring HTS tokens to the tokenAddress are in evm and long-zero format
has 18 decimals ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract has 18 decimals
has 18 decimals ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token has 18 decimals
has a name ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract has a name
has a name ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token has a name
has a symbol ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract has a symbol
has a symbol ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token has a symbol
keyType = ADMIN ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = ADMIN
keyType = FEE ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = FEE
keyType = FREEZE ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = FREEZE
keyType = KYC ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = KYC
keyType = PAUSE ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = PAUSE
keyType = SUPPLY ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenKey(token, keyType) keyType = SUPPLY
nft with no custom fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) nft with no custom fees
nft with royalty fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) nft with royalty fees
nonce for contract correctly increments ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount nonce for contract correctly increments

other account transfers tokens back to owner ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens other account transfers tokens back to owner
other account transfers tokens back to owner ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough tokens other account transfers tokens back to owner
returns zero ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 balanceOf when the requested account has no tokens returns zero
returns zero ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 balanceOf when the requested account has no tokens returns zero
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender does not have enough allowance when the token owner does not have enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender does not have enough allowance when the token owner has enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner does not have enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is the zero address reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender does not have enough allowance when the token owner does not have enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender does not have enough allowance when the token owner has enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner does not have enough balance reverts
reverts ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is the zero address reverts
should NOT allow eth_call to process IHRC719.isAssociated() method ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles eth_call with force-to-consensus-by-selector logic should NOT allow eth_call to process IHRC719.isAssociated() method
should allow eth_call to successfully process IHRC719.isAssociated() method ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles eth_call with force-to-consensus-by-selector logic should allow eth_call to successfully process IHRC719.isAssociated() method
should associate to a nft ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests should associate to a nft
should associate to a token with custom fees ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests should associate to a token with custom fees
should associate to a token ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests should associate to a token
should be able to approve anyone to spend tokens ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Approval Tests should be able to approve anyone to spend tokens
should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall true
should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a failing CALL transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CALL transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a failing CALL transaction with revert reason of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CALL transaction with revert reason of type Legacy with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall true
should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall true
should be able to delete a token ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Delete Token Tests should be able to delete a token
should be able to deploy a contract without creating file ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit should be able to deploy a contract without creating file
should be able to deploy a medium size contract with fileCreate ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit should be able to deploy a medium size contract with fileCreate
should be able to execute getApproved on nft ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Approval Tests should be able to execute getApproved on nft
should be able to execute getTokenKey ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Key management Tests should be able to execute getTokenKey
should be able to execute setApprovalForAllPublic ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Approval Tests should be able to execute setApprovalForAllPublic
should be able to execute updateTokenKeys ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Key management Tests should be able to execute updateTokenKeys
should be able to execute wipeTokenAccount ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Wipe Tests should be able to execute wipeTokenAccount
should be able to execute wipeTokenAccountNFT ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Wipe Tests should be able to execute wipeTokenAccountNFT
should be able to freeze and unfreeze fungible token transfers ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Freeze/Unfreeze Tests should be able to freeze and unfreeze fungible token transfers
should be able to freeze and unfreeze non-fungible token transfers ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Freeze/Unfreeze Tests should be able to freeze and unfreeze non-fungible token transfers
should be able to get a custom token fees ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Custom Fees Tests should be able to get a custom token fees
should be able to get and update fungible token expiry info ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Token Expiry Info Tests should be able to get and update fungible token expiry info
should be able to get and update non fungible token expiry info ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Token Expiry Info Tests should be able to get and update non fungible token expiry info
should be able to get default KYC status for fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile KYC Tests should be able to get default KYC status for fungible token
should be able to get default KYC status for non fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile KYC Tests should be able to get default KYC status for non fungible token
should be able to get fungible token info ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Get Token Info Tests should be able to get fungible token info
should be able to get non-fungible token info ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Get Token Info Tests should be able to get non-fungible token info
should be able to get token info ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Get Token Info Tests should be able to get token info
should be able to grant KYC, tranfer hts tokens and revoke KYC ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile KYC Tests should be able to grant KYC, tranfer hts tokens and revoke KYC
should be able to mint a nft ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests should be able to mint a nft
should be able to pause fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Pause/Unpause Tests should be able to pause fungible token
should be able to pause non fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Pause/Unpause Tests should be able to pause non fungible token
should be able to return more than 2 logs with limit of 2 logs per request ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to return more than 2 logs with limit of 2 logs per request
should be able to transfer both fungible and non-fungible tokens in single cryptoTransfer ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should be able to transfer both fungible and non-fungible tokens in single cryptoTransfer
should be able to transfer fungible tokens ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should be able to transfer fungible tokens
should be able to transfer nft with transferFrom ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests HTS Precompile Approval Tests should be able to transfer nft with transferFrom
should be able to transfer non-fungible tokens ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should be able to transfer non-fungible tokens
should be able to uninstall existing log filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive should be able to uninstall existing log filter
should be able to uninstall existing newBlock filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive should be able to uninstall existing newBlock filter
should be able to unpause fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Pause/Unpause Tests should be able to unpause fungible token
should be able to unpause non fungible token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Pause/Unpause Tests should be able to unpause non fungible token
should be able to use `address` param with a large block range ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `address` param with a large block range
should be able to use `address` param with multiple addresses ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `address` param with multiple addresses
should be able to use `address` param ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `address` param
should be able to use `blockHash` param ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `blockHash` param
should be able to use `fromBlock` param ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `fromBlock` param
should be able to use `topics` param ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use `topics` param
should be able to use range of `fromBlock` and `toBlock` params ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should be able to use range of `fromBlock` and `toBlock` params
should call eth_feeHistory ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_feeHistory should call eth_feeHistory
should check initial balances ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests should check initial balances
should create a BASIC spending plan for a new user and use the same plan on second transaction and different plan on third transaction from another user ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch1 BASIC Tier should create a BASIC spending plan for a new user and use the same plan on second transaction and different plan on third transaction from another user
should create and associate to a fungible token with custom fees ‑ RPC Server Acceptance Tests Acceptance tests @htsprecompilev1 HTS Precompile V1 Acceptance Tests should create and associate to a fungible token with custom fees
should create and associate to an nft ‑ RPC Server Acceptance Tests Acceptance tests @htsprecompilev1 HTS Precompile V1 Acceptance Tests should create and associate to an nft
should create associate to a fungible token ‑ RPC Server Acceptance Tests Acceptance tests @htsprecompilev1 HTS Precompile V1 Acceptance Tests should create associate to a fungible token
should create fungible token with default freeze status true ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Freeze/Unfreeze Tests should create fungible token with default freeze status true
should create non fungible token with default freeze status true ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Freeze/Unfreeze Tests should create non fungible token with default freeze status true
should delete the file created while execute "eth_sendRawTransaction" to deploy a large contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should delete the file created while execute "eth_sendRawTransaction" to deploy a large contract
should deploy a large contract and decrease remaining HBAR in limiter when transaction data is large ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit should deploy a large contract and decrease remaining HBAR in limiter when transaction data is large
should eventually exhaust the hbar limit for a BASIC user after multiple deployments of large contracts ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch1 BASIC Tier should eventually exhaust the hbar limit for a BASIC user after multiple deployments of large contracts
should execute "eth_call" with both data and input fields ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with both data and input fields
should execute "eth_call" with correct block hash object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block hash object
should execute "eth_call" with correct block number object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block number object
should execute "eth_call" with correct block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block number
should execute "eth_call" with incorrect block hash object, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block hash object, SC should not exist yet
should execute "eth_call" with incorrect block number as an object, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block number as an object, SC should not exist yet
should execute "eth_call" with incorrect block number, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block number, SC should not exist yet
should execute "eth_call" without from field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" without from field
should execute "eth_call" without gas field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" without gas field
should execute "eth_chainId" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_chainId"
should execute "eth_estimateGas" with `to` filed set to null (deployment transaction) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with `to` filed set to null (deployment transaction)
should execute "eth_estimateGas" with both input and data fields present in the txObject ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with both input and data fields present in the txObject
should execute "eth_estimateGas" with data as 0x instead of null ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with data as 0x instead of null
should execute "eth_estimateGas" with input as 0x instead of data ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with input as 0x instead of data
should execute "eth_estimateGas" with to, from, value and gas filed ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with to, from, value and gas filed
should execute "eth_estimateGas" with to, from, value,accessList gas filed ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should execute "eth_estimateGas" with to, from, value,accessList gas filed
should execute "eth_getBalance" for non-existing address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getBalance should execute "eth_getBalance" for non-existing address
should execute "eth_getBlockByHash" for non-existing block hash and hydrated transactions = false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByHash" for non-existing block hash and hydrated transactions = false
should execute "eth_getBlockByHash" for non-existing block hash and hydrated transactions = true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByHash" for non-existing block hash and hydrated transactions = true
should execute "eth_getBlockByHash", hydrated transactions = false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByHash", hydrated transactions = false
should execute "eth_getBlockByNumber" for non existing block number and hydrated transactions = false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByNumber" for non existing block number and hydrated transactions = false
should execute "eth_getBlockByNumber" for non existing block number and hydrated transactions = true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByNumber" for non existing block number and hydrated transactions = true
should execute "eth_getBlockByNumber", hydrated transactions = false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockByNumber", hydrated transactions = false
should execute "eth_getBlockTransactionCountByHash" for non-existing block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockTransactionCountByHash" for non-existing block hash
should execute "eth_getBlockTransactionCountByNumber" for non-existing block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockTransactionCountByNumber" for non-existing block number
should execute "eth_getBlockTransactionCountByNumber" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should execute "eth_getBlockTransactionCountByNumber"
should execute "eth_getCode" for hts token ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should execute "eth_getCode" for hts token
should execute "eth_getStorageAt" request against an inactive address (contains no data) and receive a 32-byte-zero-hex string  ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request against an inactive address (contains no data) and receive a 32-byte-zero-hex string 
should execute "eth_getStorageAt" request to get current state changes with passing specific block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request to get current state changes with passing specific block hash
should execute "eth_getStorageAt" request to get current state changes with passing specific block ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request to get current state changes with passing specific block
should execute "eth_getStorageAt" request to get current state changes without passing block ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request to get current state changes without passing block
should execute "eth_getStorageAt" request to get current state changes ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request to get current state changes
should execute "eth_getStorageAt" request to get old state with passing specific block ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getStorageAt should execute "eth_getStorageAt" request to get old state with passing specific block
should execute "eth_getTransactionByBlockHashAndIndex" for invalid block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionByBlockHashAndIndex" for invalid block hash
should execute "eth_getTransactionByBlockHashAndIndex" for invalid index ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionByBlockHashAndIndex" for invalid index
should execute "eth_getTransactionByBlockNumberAndIndex" for invalid index ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionByBlockNumberAndIndex" for invalid index
should execute "eth_getTransactionByBlockNumberAndIndex" for non-exising block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionByBlockNumberAndIndex" for non-exising block number
should execute "eth_getTransactionByHash" for non-existing transaction and return null ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionByHash" for non-existing transaction and return null
should execute "eth_getTransactionCount" for account with non-zero nonce ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" for account with non-zero nonce
should execute "eth_getTransactionCount" for non-existing address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" for non-existing address
should execute "eth_getTransactionCount" from hollow account ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" from hollow account
should execute "eth_getTransactionCount" secondary ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" secondary
should execute "eth_getTransactionReceipt" for non-existing hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_getTransactionReceipt" for non-existing hash
should execute "eth_getUncleByBlockHashAndIndex" for non-existing block hash and index=0 ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleByBlockHashAndIndex" for non-existing block hash and index=0
should execute "eth_getUncleByBlockHashAndIndex" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleByBlockHashAndIndex"
should execute "eth_getUncleByBlockNumberAndIndex" for non-existing block number and index=0 ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleByBlockNumberAndIndex" for non-existing block number and index=0
should execute "eth_getUncleByBlockNumberAndIndex" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleByBlockNumberAndIndex"
should execute "eth_getUncleCountByBlockHash" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleCountByBlockHash"
should execute "eth_getUncleCountByBlockNumber" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_getUncleCountByBlockNumber"
should execute "eth_hashrate" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_hashrate"
should execute "eth_maxPriorityFeePerGas" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_maxPriorityFeePerGas"
should execute "eth_mining" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_mining"
should execute "eth_sendRawTransaction" and deploy a contract with any arbitrary calldata size ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" and deploy a contract with any arbitrary calldata size
should execute "eth_sendRawTransaction" and deploy a contract with more than 2 HBAR transaction fee and less than max transaction fee ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" and deploy a contract with more than 2 HBAR transaction fee and less than max transaction fee
should execute "eth_sendRawTransaction" and deploy a contract with more than max transaction fee ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" and deploy a contract with more than max transaction fee
should execute "eth_sendRawTransaction" and deploy a large contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" and deploy a large contract
should execute "eth_sendRawTransaction" and fail when deploying too large contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" and fail when deploying too large contract
should execute "eth_sendRawTransaction" for London transactions ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" for London transactions
should execute "eth_sendRawTransaction" for deterministic deployment transaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" for deterministic deployment transaction
should execute "eth_sendRawTransaction" for legacy transactions (with no chainId i.e. chainId=0x0) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" for legacy transactions (with no chainId i.e. chainId=0x0)
should execute "eth_sendRawTransaction" of type 1 and deploy a real contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" of type 1 and deploy a real contract
should execute "eth_sendRawTransaction" of type 2 and deploy a real contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should execute "eth_sendRawTransaction" of type 2 and deploy a real contract
should execute "eth_sendRawTransaction" without triggering HBAR rate limit exceeded ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit should execute "eth_sendRawTransaction" without triggering HBAR rate limit exceeded
should execute "eth_submitWork" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_submitWork"
should execute "eth_syncing" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "eth_syncing"
should execute "net_listening" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "net_listening"
should execute "net_version" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "net_version"
should execute "web3_client_version" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should execute "web3_client_version"
should fail "eth_call" request without data field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail "eth_call" request without data field
should fail "eth_sendRawTransaction" for EIP155 transaction with a too high gasLimit ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for EIP155 transaction with a too high gasLimit
should fail "eth_sendRawTransaction" for EIP155 transaction with not enough gas ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for EIP155 transaction with not enough gas
should fail "eth_sendRawTransaction" for Legacy 2930 transactions (with gas price too low) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for Legacy 2930 transactions (with gas price too low)
should fail "eth_sendRawTransaction" for Legacy 2930 transactions (with insufficient balance) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for Legacy 2930 transactions (with insufficient balance)
should fail "eth_sendRawTransaction" for Legacy transactions (with gas price too low) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for Legacy transactions (with gas price too low)
should fail "eth_sendRawTransaction" for London transaction with a too high gasLimit ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for London transaction with a too high gasLimit
should fail "eth_sendRawTransaction" for London transaction with not enough gas ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for London transaction with not enough gas
should fail "eth_sendRawTransaction" for London transactions (with gas price too low) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for London transactions (with gas price too low)
should fail "eth_sendRawTransaction" for London transactions (with insufficient balance) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for London transactions (with insufficient balance)
should fail "eth_sendRawTransaction" for legacy EIP 155 transactions (with gas price too low) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for legacy EIP 155 transactions (with gas price too low)
should fail "eth_sendRawTransaction" for legacy EIP 155 transactions (with insufficient balance) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for legacy EIP 155 transactions (with insufficient balance)
should fail "eth_sendRawTransaction" for transaction with incorrect chain_id ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls Prechecks should fail "eth_sendRawTransaction" for transaction with incorrect chain_id
should fail "eth_sendRawTransaction" for transaction with incorrect chain_id ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should fail "eth_sendRawTransaction" for transaction with incorrect chain_id
should fail to debug a transaction with invalid onlyTopCall value type ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should fail to debug a transaction with invalid onlyTopCall value type
should fail to debug a transaction with invalid tracer type ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should fail to debug a transaction with invalid tracer type
should fail to execute "eth_call" with wrong block hash object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block hash object
should fail to execute "eth_call" with wrong block number object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block number object
should fail to execute "eth_call" with wrong block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block number
should fail to execute "eth_call" with wrong block tag ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block tag
should fail to swap approved fungible tokens ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should fail to swap approved fungible tokens
should fail to swap approved non-fungible tokens ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should fail to swap approved non-fungible tokens
should fail to transfer fungible and non-fungible tokens in a single tokenTransferList ‑ RPC Server Acceptance Tests Acceptance tests @tokencreate HTS Precompile Token Create Acceptance Tests CryptoTransfer Tests should fail to transfer fungible and non-fungible tokens in a single tokenTransferList
should individually update amountSpents of different spending plans ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests HBAR Rate Limit For Different Spending Plan Tiers @hbarlimiter-batch2 Multiple users with different tiers should individually update amountSpents of different spending plans
should not be able to call eth_getFilterChanges for not existing filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not be able to call eth_getFilterChanges for not existing filter
should not be able to execute "eth_estimateGas" with no transaction object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should not be able to execute "eth_estimateGas" with no transaction object
should not be able to execute "eth_estimateGas" with wrong from field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should not be able to execute "eth_estimateGas" with wrong from field
should not be able to execute "eth_estimateGas" with wrong gas field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should not be able to execute "eth_estimateGas" with wrong gas field
should not be able to execute "eth_estimateGas" with wrong to field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should not be able to execute "eth_estimateGas" with wrong to field
should not be able to execute "eth_estimateGas" with wrong value field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_estimateGas should not be able to execute "eth_estimateGas" with wrong value field
should not be able to uninstall not existing filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not be able to uninstall not existing filter
should not be able to use `toBlock` without `fromBlock` param if `toBlock` is not latest ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should not be able to use `toBlock` without `fromBlock` param if `toBlock` is not latest
should not cache "finalized" block in "eth_getBlockByNumber"  ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should not cache "finalized" block in "eth_getBlockByNumber" 
should not cache "latest" block in "eth_getBlockByNumber"  ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should not cache "latest" block in "eth_getBlockByNumber" 
should not cache "pending" block in "eth_getBlockByNumber"  ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should not cache "pending" block in "eth_getBlockByNumber" 
should not cache "safe" block in "eth_getBlockByNumber"  ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Block related RPC calls should not cache "safe" block in "eth_getBlockByNumber" 
should not fail "eth_sendRawTransactxion" for Legacy 2930 transactions ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should not fail "eth_sendRawTransactxion" for Legacy 2930 transactions
should not return contract bytecode after sefldestruct ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should not return contract bytecode after sefldestruct
should not support "eth_coinbase" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_coinbase"
should not support "eth_getWork" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_getWork"
should not support "eth_newPendingTransactionFilter" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not support "eth_newPendingTransactionFilter"
should not support "eth_protocolVersion" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_protocolVersion"
should not support "eth_sendTransaction" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_sendTransaction"
should not support "eth_sign" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_sign"
should not support "eth_signTransaction" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_signTransaction"
should not support "eth_submitHashrate" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Unsupported RPC Endpoints should not support "eth_submitHashrate"
should not throw rate limit exceeded error for eth_chainId ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Rate Limiters Acceptance Tests RPC Rate Limiter Acceptance Tests Given requests within the Tier 2 rate limit should not throw rate limit exceeded error for eth_chainId
should return 0 for getTokenType with passed FUNGIBLE_COMMON token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile for token check methods should return 0 for getTokenType with passed FUNGIBLE_COMMON token
should return 0x0 for account alias on eth_getCode ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should return 0x0 for account alias on eth_getCode
should return 0x0 for account evm_address on eth_getCode ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should return 0x0 for account evm_address on eth_getCode
should return 0x0 for non-existing contract on eth_getCode ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests eth_getCode should return 0x0 for non-existing contract on eth_getCode
should return 1 for getTokenType with passed HTS NON_FUNGIBLE_UNIQUE token ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile for token check methods should return 1 for getTokenType with passed HTS NON_FUNGIBLE_UNIQUE token
should return 400 error for non-existing transaction hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should return 400 error for non-existing transaction hash
should return empty logs if address = ZeroAddress ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should return empty logs if address = ZeroAddress
should return empty on "eth_accounts" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-2 RPC Server Acceptance Tests @release Hardcoded RPC Endpoints should return empty on "eth_accounts"
should return empty result for  non-existing `blockHash` ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should return empty result for  non-existing `blockHash`
should return false for isToken with passed contract address ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile for token check methods should return false for isToken with passed contract address
should return only logs of non-zero addresses ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests eth_getLogs should return only logs of non-zero addresses
should return the transaction count through a websocket ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-2 eth_getTransactionCount should return the transaction count through a websocket
should return the transaction count through an ethers WebSocketProvider ‑ RPC Server Acceptance Tests Acceptance tests @release @web-socket-batch-2 eth_getTransactionCount should return the transaction count through an ethers WebSocketProvider
should return transaction result with no chainId field for legacy EIP155 transactions  (with no chainId i.e. chainId=0x0) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-1 RPC Server Acceptance Tests RPC Server Acceptance Tests Transaction related RPC Calls should return transaction result with no chainId field for legacy EIP155 transactions  (with no chainId i.e. chainId=0x0)
should return true for isToken with passed token address ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile for token check methods should return true for isToken with passed token address
should revert if attempting to wipe more tokens than the owned amount ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile Wipe Tests should revert if attempting to wipe more tokens than the owned amount
should subscribe to newHeads, include transactions true, and receive a valid JSON RPC response ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Subscriptions for newHeads should subscribe to newHeads, include transactions true, and receive a valid JSON RPC response
should subscribe to newHeads, with "include transactions false", and receive a valid JSON RPC response ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Subscriptions for newHeads should subscribe to newHeads, with "include transactions false", and receive a valid JSON RPC response
should subscribe to newHeads, without the "include transactions", and receive a valid JSON RPC response ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe newHeads Subscriptions for newHeads should subscribe to newHeads, without the "include transactions", and receive a valid JSON RPC response
should throw an exception for getTokenType with passed contract address ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS Precompile for token check methods should throw an exception for getTokenType with passed contract address
should throw rate limit exceeded error for eth_chainId ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Rate Limiters Acceptance Tests RPC Rate Limiter Acceptance Tests Given requests exceeding the Tier 2 rate limit should throw rate limit exceeded error for eth_chainId
should timeout a request after the specified time ‑ RPC Server Acceptance Tests Acceptance tests @server-config Server Configuration Options Coverage Koa Server Timeout should timeout a request after the specified time
should update fungible token properties ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS update token info test should update fungible token properties
should update non-fungible token properties ‑ RPC Server Acceptance Tests Acceptance tests @tokenmanagement HTS Precompile Token Management Acceptance Tests HTS update token info test should update non-fungible token properties
should verify the estimated and actual transaction fees for file transactions are approximately equal ‑ RPC Server Acceptance Tests Acceptance tests @hbarlimiter HBAR Limiter Acceptance Tests HBAR Rate Limit Tests @hbarlimiter-batch1 Total HBAR Limit should verify the estimated and actual transaction fees for file transactions are approximately equal
test delete operation ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache fallback to local cache in case of Redis error test delete operation
test getAsync operation ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache fallback to local cache in case of Redis error test getAsync operation
test multiSet operation ‑ RPC Server Acceptance Tests Acceptance tests @cache-service Acceptance Tests for shared cache fallback to local cache in case of Redis error test multiSet operation
token with all custom fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) token with all custom fees
token with fixed hbar fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) token with fixed hbar fees
token with fixed token fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) token with fixed token fees
token with fractional fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) token with fractional fees
token with no custom fees ‑ RPC Server Acceptance Tests Acceptance tests @precompile-calls Tests for eth_call with HTS Calling HTS token through HederaTokenService Function with HederaTokenService.getTokenCustomFees(token) token with no custom fees
transfers the requested amount ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests ERC20 Contract should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance transfers the requested amount

transfers the requested amount ‑ RPC Server Acceptance Tests Acceptance tests @erc20 Acceptance Tests HTS token should behave like erc20 transfer from when the token owner is not the zero address when the recipient is not the zero address when the spender has enough allowance when the token owner has enough balance transfers the requested amount
when the client sends a message ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection TTL Connection TTL is reset when the client sends a message
when the server sends a message ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-batch-3 eth_subscribe Connection TTL Connection TTL is reset when the server sends a message