Skip to content

Commit 48bcad8

Browse files
committed
Clarify starknet events notification can be received multiple times when PRE_CONFIRMED is used
1 parent d6cdaa8 commit 48bcad8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

api/starknet_ws_api.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@
5858
{
5959
"name": "starknet_subscribeEvents",
6060
"summary": "Events subscription",
61-
"description": "Creates a WebSocket stream which will fire events for new Starknet events with applied filters. Events are emitted for all events from the specified block_id, up to the latest block",
61+
"description": "Creates a WebSocket stream which will fire events for new Starknet events with applied filters. Events are emitted for all events from the specified block_id, up to the latest block. If PRE_CONFIRMED finality status is provided, events might appear multiple times, for each finality status update. If a single event is required, ACCEPTED_ON_L2 must be selected (the default).",
6262
"params": [
6363
{
6464
"name": "from_address",
@@ -87,7 +87,7 @@
8787
},
8888
{
8989
"name": "finality_status",
90-
"summary": "The finality status of the most recent events to include, default is ACCEPTED_ON_L2",
90+
"summary": "The finality status of the most recent events to include, default is ACCEPTED_ON_L2. If PRE_CONFIRMED finality is selected, events might appear multiple times, once for each finality status update.",
9191
"required": false,
9292
"schema": {
9393
"type": "string",

0 commit comments

Comments
 (0)