You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remix shows the following error message for my contract
Contract creation initialization returns data with length of more than 24576 bytes. The deployment will likely fail if the current network has activated the eip 170. More info: [eip-170](https://eips.ethereum.org/EIPS/eip-170)
However, the contract can be succesfully deployed with force send. We should add in our documentation what is the expected behavior for large smart contracts and eip 170 (ignore such errors and eip 170? different limit?)
Remix shows the following error message for my contract
Contract creation initialization returns data with length of more than 24576 bytes. The deployment will likely fail if the current network has activated the eip 170. More info: [eip-170](https://eips.ethereum.org/EIPS/eip-170)
However, the contract can be succesfully deployed with force send. We should add in our documentation what is the expected behavior for large smart contracts and eip 170 (ignore such errors and eip 170? different limit?)
ref: https://github.com/paritytech/bcn-retreat-dx-feedback/issues/2
The text was updated successfully, but these errors were encountered: