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.

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

Configurable max transaction size #17099

Open
bilyana-gospodinova opened this issue Dec 18, 2024 · 0 comments · May be fixed by #17142
Open

Configurable max transaction size #17099

bilyana-gospodinova opened this issue Dec 18, 2024 · 0 comments · May be fixed by #17142
Assignees
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible.

Comments

@bilyana-gospodinova
Copy link
Contributor

Problem

As part of the integration of the hedera.app dependency in the mirror node, we noticed that the
maxSignedTxnSize is currently not configurable so the max value is 6 KB. On contract create, if the size of the contract is greater than this value, we need to make 2 transactions - one for file upload and one for the contract create using the file ID. Making 2 transactions would slow the performance down on our side.

Solution

If the maxSignedTxnSize becomes configurable, we can increase the value of the property on our side and make only 1 transaction for contract create without the need for file upload.

Alternatives

No response

@steven-sheehy steven-sheehy added the Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. label Dec 18, 2024
@tinker-michaelj tinker-michaelj self-assigned this Dec 19, 2024
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Services Team Dec 19, 2024
@tinker-michaelj tinker-michaelj moved this from 📋 Backlog to 👷🏼‍♀️ In Progress in Services Team Dec 19, 2024
@tinker-michaelj tinker-michaelj moved this from 👷🏼‍♀️ In Progress to 👀 In Review in Services Team Dec 19, 2024
steven-sheehy pushed a commit to hashgraph/hedera-mirror-node that referenced this issue Dec 20, 2024
This PR fixes BytecodeUtilsTest which were failing when ran against modularized flag.

Made BytecodeUtilsTest extend AbstractContractCallServiceTest and now gets initial setup which makes most of the test except for one pass.

The one test that did not pass was -> testExtractRuntimeBytecodeEthCall. The reason was that the EthCall.binary was bigger than services max transaction size with a little bit.
This issue will be fixed in hashgraph/hedera-services#17099

Workaround solution for the test is:
Deleted EthCall methods - getTokenName and getTokenSymbol.
We have the exacts same tests in ContractCallServiceERCTokenReadOnlyFunctionsTest so these 2 can be deleted.
Deleting those decreased the binary and now it passes services max txn size check.

Changes in this PR also fix a couple of tests using the EthCall contract in ContracCallServiceTest.

This PR modifies ... in order to support ...
BytecodeUtilsTest - extends AbstractContractCallServiceTest
EthCall.sol - delete getTokenName and getTokenSymbol to decrease contract binary

Signed-off-by: Kristiyan Selveliev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible.
Projects
Status: 👀 In Review
Development

Successfully merging a pull request may close this issue.

3 participants