-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Description
I am encountering an issue with the eth_getTransactionReceipt method on the endpoint https://services.polkadothub-rpc.com/mainnet.
For a specific transaction hash, the RPC returns null, whereas for other transactions on the same endpoint, it returns the correct receipt data. I have verified that the failing transaction should be valid.
Steps to Reproduce
1. The Failing Case (Returns null)
Executing the following command returns null: (https://blockscout.polkadot.io/tx/0xdb294c21e7f154050dc7a7eb4b81d68aba4cb55a56adbe76fcf8256f767ae873)
curl https://services.polkadothub-rpc.com/mainnet \
-H "Content-Type:application/json;charset=utf-8" \
-d '{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_getTransactionReceipt",
"params": ["0xdb294c21e7f154050dc7a7eb4b81d68aba4cb55a56adbe76fcf8256f767ae873"]
}'
Response:
{"jsonrpc":"2.0","result":null,"id":1}
2. The Working Case (Returns data) (https://blockscout.polkadot.io/tx/0xbeb914a046d77e769d3cea821fe525e4809a4ce38a39793c580076640e50b0ab)
To confirm the endpoint is operational, I tested another transaction hash which works as expected:
curl https://services.polkadothub-rpc.com/mainnet \
-H "Content-Type:application/json;charset=utf-8" \
-d '{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_getTransactionReceipt",
"params": ["0xbeb914a046d77e769d3cea821fe525e4809a4ce38a39793c580076640e50b0ab"]
}'
Expected Behavior
The API should return the transaction receipt object for the hash 0xdb294c21e7f154050dc7a7eb4b81d68aba4cb55a56adbe76fcf8256f767ae873, similar to how it behaves for other valid transactions.
Environment
- RPC Endpoint:
https://services.polkadothub-rpc.com/mainnet - Method:
eth_getTransactionReceipt