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
In JSON-RPC API v0.8.0, why does only newHeads subscription have "new" in its name: starknet_subscribeNewHeads, starknet_subscriptionNewHeads? E.g. the events are also new, but there's no "new" in starknet_subscribeEvents and starknet_subscriptionEvents.
In JSON-RPC API v0.8.0, why does only
newHeads
subscription have "new" in its name:starknet_subscribeNewHeads
,starknet_subscriptionNewHeads
? E.g. the events are also new, but there's no "new" instarknet_subscribeEvents
andstarknet_subscriptionEvents
.I've been told that Starknet tries to follow Ethereum's subscription API, but it's quite different from it:
eth_subscribe
) with the subscription type specified in parameters.newHeads
also covers chain reorg (but at least it's also callednewHeads
).pendingTransactions
is callednewPendingTransactions
events
is calledlogs
The text was updated successfully, but these errors were encountered: