-
Notifications
You must be signed in to change notification settings - Fork 220
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.
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
feat: limit transaction size #6154
feat: limit transaction size #6154
Conversation
Test Results (CI) 3 files 117 suites 36m 52s ⏱️ Results for commit 0b9197e. ♻️ This comment has been updated with latest results. |
Test Results (Integration tests) 2 files + 2 11 suites +11 26m 40s ⏱️ + 26m 40s For more details on these failures, see this check. Results for commit 0b9197e. ± Comparison against base commit 97fc7b3. ♻️ This comment has been updated with latest results. |
287f722
to
460c677
Compare
7112d23
to
227cdcf
Compare
base_layer/wallet/src/transaction_service/protocols/transaction_send_protocol.rs
Outdated
Show resolved
Hide resolved
Added checks to ensure that transactions to self or that are negotiated between parties do not exceed the RPC frame size limit.
8b2403b
to
0b9197e
Compare
Description
Added checks to ensure that transactions negotiated between parties, transactions to self and imported transactions do not exceed the RPC frame size limit when the transaction is broadcast to the base node. This can easily happen when lots of dust inputs are collected to be spent. If a too-large transaction is detected in any of the transaction service protocols it will be cancelled so that the user can try to create a new transaction with different parameters, for example, to reduce the recipient amount.
Edit:
spend_dust
tests to speed it up even more as suggested by @SWvheerdenMotivation and Context
See #6108
How Has This Been Tested?
Added unit tests:
test_spend_dust_to_self_in_oversized_transaction
test_spend_dust_to_other_in_oversized_transaction
test_spend_dust_happy_path
What process can a PR reviewer use to test or verify this change?
Code walk-through
Review unit tests
Breaking Changes