我已经在Ropsten上面开发了几天了。网络变得令人难以忍受的缓慢,并一直导致网络超时非常频繁。这个问题在下午和晚上特别突出(洛杉矶时间)。我试图增加gasPrice,如下所示:
Crafted TX: {
type: 2,
chainId: 3,
nonce: 91,
maxPriorityFeePerGas: BigNumber { value: "100000000000" },
maxFeePerGas: BigNumber { value: "100000000000" },
gasPrice: null,
gasLimit: BigNumber { value: "1000000" },
to: null,
value: BigNumber { value: "0" },
data: '...',
accessList: [],
hash: '0x7d632277c97447bbdaa5a1501c950c9a834be2fea3dce6af168e2b5f661a5a12',
v: 1,
r: '0x19e5c5f7c59f5bd0f12c4de3c86edf9a7b8f6caab9720096617cf7106a037334',
s: '0x5bc3e9191bc12c46837cfee2bfd0d81b27fb1b758395996926676d6f00deb69c',
from: '0x1782760f47eDd41648C418671a068CD3aC38c4dC',
confirmations: 0,
wait: [Function (anonymous)]
}
Ropsten网络肯定在工作,因为Ether扫描资源管理器显示了一个固定的挖掘块流。
以下是事务的发送方式:
const contractFactory = new ethers.ContractFactory(...);
let contract = await contractFactory.deploy({gasPrice: 100 * 1e9});
console.log("Crafted TX: ", contract.deployTransaction);
await contract.deployTransaction.wait();
console.log("deployed contract: ", contract.address);
发布于 2022-01-22 07:34:49
通过切换到使用不同的私钥,这个问题解决了。我还是不明白为什么会这样。可能是因为一个坏女人吗?
一个有趣的观察是,在EtherScan上突然有大量的tx卡住了。
https://ethereum.stackexchange.com/questions/119630
复制相似问题