@fare I am not aware how to check that in the logs, how would I do it?. The EVM is based of https://github.com/lightstreams-network/lightchain
If I resend the same smart contract creation tx, it just says nonce too low because I assign a nonce of 0 to all raw txs since each tx is sent from a unique account
I tried with a private net of 4 nodes. If I send to the second node it is the same issue.
Well if there was a gas issue, web3 would return an error like insufficient gas price, or gas too low when txs are sent using sendSignedTransaction, would it not?
The bombardment, did not fail entirely. There were smart contracts created because I got tx receipts with the contractAddress field. Actually, when I sent 6000tx, I got 4500tx with a receipt that had contractAddress field. So I am assuming 1500tx failed probably
Is there a common pattern to the failing functions? For instance, I once had a problem that only showed when the first byte of an address was 0 or some such.
@fare What do you mean? You had a problem when the first byte of the sender account address was 0, for smart contract creation tx?
Hi all, if I can abruptly ask a question here:
geth --syncmode "light" getting stuck at:
INFO [09-11|19:11:43.053] Mapped network port proto=udp extport=30303 intport=30303 interface="UPNP IGDv1-IP1"
Have tried resyncing clock, deleting chain data, double and triple checking 30303 is open. No luck. Any ideas?