From 242e09b0f215186dd118f25c5ba7c6f4da4ac85e Mon Sep 17 00:00:00 2001 From: Pierre Krieger Date: Thu, 4 Apr 2024 06:26:52 +0200 Subject: [PATCH] =?UTF-8?q?Revert=20"transactionWatch:=20Limit=20the=20num?= =?UTF-8?q?ber=20of=20active=20subscriptions=20and=20clarif=E2=80=A6"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This reverts commit bef3ab503f57c362917682d9ffd4370ffb3e00b0. --- src/api/transactionWatch_unstable_submitAndWatch.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/api/transactionWatch_unstable_submitAndWatch.md b/src/api/transactionWatch_unstable_submitAndWatch.md index f8dfc8f..6b25be7 100644 --- a/src/api/transactionWatch_unstable_submitAndWatch.md +++ b/src/api/transactionWatch_unstable_submitAndWatch.md @@ -10,9 +10,6 @@ The string returned by this function is opaque and its meaning can't be interpre Once this function has been called, the server will try to propagate this transaction over the peer-to-peer network and/or include it onto the chain even if `transactionWatch_unstable_unwatch` is called or that the JSON-RPC client disconnects. In other words, it is not possible to cancel submitting a transaction. -The JSON-RPC server must accept at least 4 `transactionWatch_unstable_submitAndWatch` subscriptions per JSON-RPC client. -Trying to open more might lead to a JSON-RPC error when calling `transactionWatch_unstable_submitAndWatch`. - ## Notifications format This function will later generate one or more notifications in the following format: @@ -127,7 +124,7 @@ No more event will be generated about this transaction. The `invalid` event indicates that the runtime has marked the transaction as invalid. -This can happen for a variety of reasons specific to the chain, such as a bad signature, bad nonce, not enough balance for fees, invalid decoded transaction bytes etc. +This can happen for a variety of reasons specific to the chain, such as a bad signature, bad nonce, not enough balance for fees, etc. `error` is a human-readable error message indicating why the transaction is invalid. This string isn't meant to be shown to end users, but is for developers to understand the problem. @@ -168,5 +165,4 @@ JSON-RPC servers are allowed to skip sending events as long as it properly keeps ## Possible errors -- A JSON-RPC error with error code `-32800` can be generated if the JSON-RPC client has already opened 4 or more `transactionWatch_unstable_submitAndWatch` subscriptions. -- A JSON-RPC error with error code `-32602` is generated if the `transaction` parameter is not a valid hex string. Note that no error is produced if the bytes of the `transaction`, once decoded, are invalid. Instead, an `invalid` notification will be generated. +A JSON-RPC error is generated if the `transaction` parameter has an invalid format, but no error is produced if the bytes of the `transaction`, once decoded, are invalid. Instead, an `invalid` notification will be generated.