Event-driven channels

Starknet

Starknet is a permissionless Ethereum Layer 2 validity rollup developed by StarkWare, powered by STARK proofs and the Cairo smart contract language. Developers interact with Starknet via a versioned Starknet JSON-RPC (served by Pathfinder, Juno, and Papyrus full nodes as well as Infura / Alchemy / B

6 channels across 1 AsyncAPI spec · Provider profile

Channels

starknet_subscribeEvents

Creates a WebSocket stream that fires notifications for new Starknet events matching optional `from_address`, `keys`, `block_id`, and `finality_status` filters. Notifications are delivered via `starkn

Starknet WebSocket RPC API
starknet_subscribeNewHeads

Creates a WebSocket stream that fires notifications for new block headers. The client publishes a `starknet_subscribeNewHeads` request and receives a `subscription_id`; subsequent block header notific

Starknet WebSocket RPC API
starknet_subscribeNewTransactionReceipts

Creates a WebSocket stream that fires notifications for new transaction receipts. The client may filter by `finality_status` (vector, default `[ACCEPTED_ON_L2]`; `ACCEPTED_ON_L1` is excluded) and `sen

Starknet WebSocket RPC API
starknet_subscribeNewTransactions

Creates a WebSocket stream that fires notifications for new transactions. The client may filter by `finality_status` vector (default `[ACCEPTED_ON_L2]`; `ACCEPTED_ON_L1` is excluded), `sender_address`

Starknet WebSocket RPC API
starknet_subscribeTransactionStatus

Creates a WebSocket stream that first emits the current known status of the supplied `transaction_hash` and then emits an event for every subsequent status change, until the transaction is final (ACCE

Starknet WebSocket RPC API
starknet_unsubscribe

Closes a previously opened WebSocket subscription identified by `subscription_id`. The server responds with a boolean indicating whether the unsubscription succeeded, or an `INVALID_SUBSCRIPTION_ID` (

Starknet WebSocket RPC API