People who code: we want your input. Take the Survey
3

That is not going to make a difference, bots are looking for pending transactions that execute the addLiquidity method. In order for that to work, the addLiquidity method on the router contract needs to be executed. Whether it is executed directly or via a proxy contract, it does not matter because the method on the router contract is always executed and ...


3

It's just a slow node... When a node receives a transaction, it sends it to other connected nodes, who then send it to other connected nodes (repeat), until all the nodes have the transaction in their mempool. This process takes some time (but not much). It is possible that a transaction that is sent just before a block is mined could be picked up by the ...


3

Note that, in Truffle console, you should try naming() just like: A_instance.naming.sendTransaction() or A_instance.naming() This sends a transaction to network that causes your desired code be run. This process mutates ledger and contracts' states. Using .call() instead .sendTransaction() just makes an interaction between two contracts without mutating ...


2

I think your question is answered in this issue https://github.com/ethereum/go-ethereum/issues/16216 In short, nodes running in "light" mode are only capable of seeing their own transactions.


2

The network is very busy right now, resulting in higher gas prices. If you use a gas price that is too low, your transaction will take a lot longer to confirm. I recommend that you use ETH Gas Station to see what gas price you should use. You can read more about gas in general here: https://support.mycrypto.com/general-knowledge/ethereum-blockchain/what-is-...


2

If you want to speed things up, you can either 'replace' or 'cancel' your original transaction by using the same nonce. Since you have the private key, you can use most common wallets or applications, such as Metamask, MyEtherWallet or MyCrypto who support this. You don't have to do it through the command line. Replace Re-submit your original transaction ...


2

It must've been due to a too low gas price. Gas prices can be highly volatile so by the time your transaction arrives in the mem pool it may already be too low.


2

Miners usually include transactions with a higher gas price but they can include any transactions even with 0 wei gas price. Mine their reward distribution transactions at a nominal 1 gwei gas price. Accept off-chain payments. Flashbot transactions process several transactions as a group. Transactions with gas price away from the last average gas price isn'...


2

Sean from Blocknative here. Thanks for posting the question! Etherscan appears to report a block Timestamp using the block header's timestamp field. This is also reported by Blocknative for confirmed transactions in the blockTimeStamp field. This time is set by the minor when the block is constructed (before actual mining). Note that the miner has some ...


2

No, Ethereum does not have a mechanism for dropping or cancelling transactions automatically. In practice, however, a transaction could be dropped: Every node part of the blockchain has an internal buffer of pending transactions. As new transactions keep coming in, the buffer might get full and older transactions will be dropped. So, after a time long enough,...


2

There's no predefined order for transactions in a block. The only requirement is for transactions from the same address to be sorted by the transaction's nonce but transactions from different addresses can be in any order. In Ethereum mainnet miners will sort by gas price because they will get a larger reward. But it is not always the case, search for "...


1

The transaction failed because due to the higher gas price and being on the same block, it was executed before the liquidity was added. I was confusing the nonce with the block position.


1

You did not post a link to your address so it is difficult to pinpoint the exact cause. However, you most likely sent your first swap with a gas price that was too low. Because of that, it has not yet been picked up by the miners. Any subsequent transaction will also be stalled regardless of their gas price (transactions are always processed in order).


1

If your current account nonce is 9, all the future transactions sent with nonce < 9 will be automatically rejected by the network. Transactions with nonce > 9 will be kept, "set apart" by the miners and exploited once the nonce gap is completed. To solve your problem you have to ensure a transaction with nonce = 9 get mined. You can either ...


1

You can use the nonce and transaction count to validate if the nonce was mined. if (tx.nonce < getTransactionCount(sender)) { drop transaction } I don't think this situation is particular to testnets. I'd say it is worse in mainnet where short chain reorgs are common.


1

You can speed up the transaction and make it go through faster. On MetaMask, click on the transaction that is processing and there will be an option to "Speed up". Click this and it should go through much faster!


1

I also propose a solution based on the block.number, which is safer than using block.timestamp, but with a different approach. Rather than using it to secure a reservation after several blocks, I would use it as an ordering criterion in case that multiple users go for the same number. When a user commits a hash, the current block number is captured in the ...


1

after looking at the transaction on etherscan it appears the gas fee you provided appears to be too low (5GWei). The current state of ethereum is very congested, therefore user's must bid to get their transactions processed. This is done through the setting of the gas price. The higher the gas price the faster your transaction will be included in a new block....


1

The one who mines the block decides the sequence of its transactions. Usually the order is decided by the transactions' gas prices (default logic for most miners). In that case, users may influence it by "speeding up" the transaction, meaning: re-broadcast the transaction with a higher gas price.


1

Binance does not have deposit limits for cryptocurrency. Unverified users have a 2 bitcoin per 24-hours withdrawal limit. So 2 Bitcoins worth of ETH, roughly 53.7 ETH at this time.


1

There is no FIFO. Miners are free to include any transactions they wish as long as the transactions are: Correct in syntax With correct wallet nonce (can't mine transaction with nonce 5 before 4 has been mined) In reality the miners prefer transactions which give them the best rewards: the transactions with the highest gas price. So the higher gas price ...


1

There are some cases maybe you didn't pay attention: You are executing naming() from A by .call() not by .sendTransaction(). Obviously, it never mutates the state. I did guess that because of truffle-contract that there is in the tags list of your question. Maybe, you made a mistake in inserting the real address of C when you call it in both A and B. I mean ...


1

It is a gas price issue. According to EtherScan you are using: 0.00000002 Ether (20 Gwei) According to EthGasStation.info this is below the safe low at the moment: Unless you want to get involved in a difficult game on cancelling old transactions, I suggest you create a new Ethereum account and try to deploy the contracts from there with higher gas price.


Only top voted, non community-wiki answers of a minimum length are eligible