You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Polling mechanism of eth_getTransactionReceipt(txHash)
But
It is not great for a Dapp/Wallet to use a proprietary API, whereas the open standard RPC interface is more reliable.
L1 and L2s have significantly different throughputs; ideally, a different polling mechanism should be put in place for each network, but that is not a great developer experience to maintain this configuration. In addition, some RPC endpoints, like public endpoints, do not well support fast polling due to a low rate limit.
Instead, the open specification should propose a push mechanism for a mature user and developer experience for transaction inclusion notification
Spec
Parameters:
transactionReceipts
object
2.a. addresses: list of addresses to filter transaction receipts by to or from
2.b. includeRemoved (optional): boolean specifier to include transactions that have been removed from the cannonical chain (or re-orged).
Motivation
As a Dapp/Wallet, the way to be notified of a block inclusion of a transaction are as follows:
But
Instead, the open specification should propose a push mechanism for a mature user and developer experience for transaction inclusion notification
Spec
Parameters:
transactionReceipts
object
2.a.
addresses
: list of addresses to filter transaction receipts byto
orfrom
2.b.
includeRemoved
(optional): boolean specifier to include transactions that have been removed from the cannonical chain (or re-orged).Example:
Response:
Example:
Notifications:
blockHash
blockNumber
transactionIndex
transactionHash
from
to
cumulativeGasUsed
gasUsed
contractAddress
logs
logsBloom
status
effectiveGasPrice
type
The text was updated successfully, but these errors were encountered: