-
Notifications
You must be signed in to change notification settings - Fork 649
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
Check transaction size #1573
Comments
GRAPHENE_DEFAULT_MAX_TRANSACTION_SIZE is set to 2048, which I believe is way too low. So I agree with Abit. The maximum_transaction_size should be adjusted prior to the hardfork. |
What is the biggest transaction we had in mainnet so far? |
I will be doing a reindex tonight. I will attempt to capture that information. |
Fixed by #1586 Biggest transaction to date: 1,008,285 |
I'll propose to committee to set a max tx size of |
1,048,576 please...let's not mix SI and IEC prefixes :) |
The best thing about standards is there are so many to choose from. I vote for 1,010,101 as it looks more "techie" :-D |
1234567 ? easy to remember |
Bug Description
As reported in #374, transaction size hasn't been checked in consensus code, although we have a global chain parameter
maximum_transaction_size
.bitshares-core/libraries/chain/include/graphene/chain/protocol/chain_parameters.hpp
Line 42 in 58c0c49
Note: before enabling this check with a hard fork, we should set the parameter to a fair value to avoid breaking things.
Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: