New answers tagged

1

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'...


1

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 ...


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 ...


0

You should be able to recover access to your Coinbase wallet through your Coinbase account. Try contacting them via email!


0

I guess the pending transactions number is relating to all network transactions. It takes a time to propagate new transactions from your local node queue. It may also depend on the Gas fee, so underpaid transactions might be rejected from the limited queues of other nodes


0

This should solve your issue. I added comments on the lines that I changed so you can spot them easily. Let me know if it works for your use case! contract Raffle { mapping(address => bytes32) commitments; mapping(uint256 => address) reserved; mapping(bytes32 => address) commitOwners; // ADD THIS event Reserved(uint256 value, ...


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!


0

It's to be expected that a single node can't retrieve all pending transactions, Blocknative suggests a miss rate of 1%: In our analysis, a single node's mempool in a single geography will miss ~1% of all transactions during normal operating conditions. Under heavy transaction volumes, the percentage of missed transactions can vary greatly.


Top 50 recent answers are included