Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[RPC-Spec-V2] Limit transaction_unstable_broadcast operations #3081

Closed
Tracked by #1516
lexnv opened this issue Jan 26, 2024 · 0 comments · Fixed by #3772
Closed
Tracked by #1516

[RPC-Spec-V2] Limit transaction_unstable_broadcast operations #3081

lexnv opened this issue Jan 26, 2024 · 0 comments · Fixed by #3772

Comments

@lexnv
Copy link
Contributor

lexnv commented Jan 26, 2024

The JSON-RPC server must allow at least 4 transactions being broadcasted at the same time per JSON-RPC client. Any attempt to broadcast more than 4 transactions simultaneously might result in null being returned.

  • ensure that at least 4 operations per RPC client are accepted by the server (extracted from spec)

cc @paritytech/subxt-team
@lexnv lexnv mentioned this issue Jan 26, 2024
Open
@lexnv lexnv mentioned this issue Feb 2, 2024
Merged
@lexnv lexnv mentioned this issue Apr 2, 2024
Merged
github-merge-queue bot pushed a commit that referenced this issue Apr 19, 2024
@lexnv @jsdw
rpc-v2: Limit transactionBroadcast calls to 16 (#3772)
98a364f 
This PR limits the number of active calls to the transactionBroadcast
APIs to 16.

cc @paritytech/subxt-team 

Closes: #3081

---------

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Co-authored-by: James Wilson <james@jsdw.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

rpc-v2: Limit transactionBroadcast calls to 16 paritytech/polkadot-sdk
1 participant
@lexnv