See Testing webhooks.
See Payload format.
At this point we deliver webhook immediately after we see it on the blockchain but in the near future we'll let you specify the count of confirmations to wait before delivering webhooks.
At ariadne.finance we do.
All EVM-compatible networks with typical EVM RPC endpoint.
All payloads for a single webhook you created in your dashboard are delivered sequentially. All webhooks you have added are delivered in parallel.
Use blockNumber, then transactionIndex then logIndex.
Use transactionHash + logIndex as your primary key. No two events can take the same spot (logIndex) in the same transaction (transactionHash).
We will retry to deliver webhooks with a timeout increasing 2x (but limited to 6h) on every failure. We will give up after 48h.
Note: Only 200-299 HTTP status responses from your endpoint are considered a success. Any other response constitutes a failure.
Events on proxy implementation contracts are still emitted in the context of the original address although Etherscan will show you only the ProxyUpgraded events. What you should do is take the ABI of the actual implementation contract and paste it into Create webhook dialog instead of the one that we have automatically provided.
Not handled yet, this is why "Confirmations count" is coming soon in the webhook edit screen. For now you should query your RPC endpoint for the transaction hash after a while and make sure that it still exists.
Probably yes. Currently downloader.js does download every block to match required events with bloom filters, so you'll have ≈7,200 RPC calls on Ethereum Mainnet and probably tens of thousands on Polygon or BSC.
23gate is made by the team at Ariadne Finance:
- Egor Egorov @egorFiNE <me@egorfine.com>
- Roman Zhbadinskyi @insky <zhbadynskyi@gmail.com>
Apache 2.0. See LICENSE.