-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Second parameter in solidity contact crashes my ethereum node #4917
Comments
Can you include the JavaScript you are using? It should definitely not be able to crash a node and I’ve used nearly identical code before, so it seems strange, I agree… |
Hi @ricmoo , `pragma solidity 0.8.28; contract SimpleStorage {
}` |
But how are you calling this with Ethers.js? That is Solidity code, not JavaScript. :) I don't think that code will compile in modern Solidity because the |
Code is compiled., no problem. `const nftMarketplaceFactory = new ethers.ContractFactory( const nftMarketplaceContract = await nftMarketplaceFactory.deploy({ console.log("nftMarketplace deployed to address: ", marketplaceAddress);` and as I said, it works with one parameter. |
eth_sendRawTransaction is called with an argument. Nothing is done with two arguments |
maybe this is an nginx problem:
|
Ethers Version
6.13.5
Search Terms
solidity
Describe the Problem
i have a solidity contact that worked with ethers 5. after switching to ethers 6 i have a weird effect: second parameter in the method causes a nternal server error in my ethereum node:
function set(uint x, uint256 itemAct) public { storedData = x; }
The following method works:
function set(uint x) public { storedData = x; }
Code Snippet
Contract ABI
Errors
No response
Environment
No response
Environment (Other)
No response
The text was updated successfully, but these errors were encountered: