-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Error: oversized data #1739
Comments
same here |
Same here. Not sure how to put the maxCodeSize in it |
Which version of web3 are you using? |
Since maxCodeSize parameter in genesis.json does not work, I had to fix this issue by increasing the transaction size to 64KB in tx_pool.go. To be specified, this is for Quorum, a fork from Ethereum for enterprise use. DOS is less applicable for private Ethereum networks such as Quorum. Updated code as follows: // UPDATED to 64KB to support the deployment of bigger contract due to the pressing need for sophisticated/complex contract in financial/capital markets - Nathan Aw
References: https://github.com/nathanawmk/quorum/blob/master/core/tx_pool.go https://ethereum.stackexchange.com/questions/55691/oversized-data-during-truffle-migrate/56354#56354 |
we were using web3 - 0.19.0 version |
@basilji |
@nathanawmk |
This is an issue of 0.20.7 and the last maintenance release happened some months ago. Because of this do I close this issue. |
While deploying contract in ethereum private blockchain using web3
web3.eth.contract(JSON.parse(contractabi.toString('utf8')));
mycontract.new({
from: web3.eth.accounts[0],
data: codebin,
gas: 3141592
}
I am getting below error
Error: oversized data
at Object.InvalidResponse (/home/user1/node02/event_test/node_modules/web3/lib/web3/errors.js:38:16)
at /home/user1/node02/event_test/node_modules/web3/lib/web3/requestmanager.js:86:36
at XMLHttpRequest.request.onreadystatechange (/home/user1/node02/event_test/node_modules/web3/lib/web3/httpprovider.js:128:7)
at XMLHttpRequestEventTarget.dispatchEvent (/home/user1/node02/event_test/node_modules/xhr2/lib/xhr2.js:64:18)
at XMLHttpRequest.setReadyState (/home/user1/node02/event_test/node_modules/xhr2/lib/xhr2.js:354:12)
at XMLHttpRequest._onHttpResponseEnd (/home/user1/node02/event_test/node_modules/xhr2/lib/xhr2.js:509:12)
at IncomingMessage. (/home/user1/node02/eventtest/node_modules/xhr2/lib/xhr2.js:469:24)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
The text was updated successfully, but these errors were encountered: