Search Results

Based on the above rationale, there is no theoretical limit to the number of transactions that can be squished into a block, just needs a bit of time to adjust. … Practically you need to get those transactions to the miners, they have to process it, distribute the results etc, so based on how optimal the implementations are, there's an upper limit. …

No. You cannot send the entire balance because the fees are deducted from your account's balance, not from the value being sent. To sweep an account you need to send balance-gas*price ETH as the valu …

In Go creating a signed transaction would look something like this: transaction := types.NewTransaction(nonce, recipient, value, gasLimit, gasPrice, input) signature, _ := crypto.Sign(transaction.Sig …

However as you mentioned, a contract can itself create multiple transactions as a result of a single invocation. …

All transactions contained within can be considered successfully executed. Security wise of course there can be reorgs, but in general they are executed transactions. … Pending on the other hand is the collection of transactions that can be executed by the network (that your own node knows about), but have not yet been done so. …

My guess is that your script misses a nonce, producing non-executable transactions. …

Neither of the clients need to be in sync to get the transaction through. For a transaction to be valid you only need to have enough funds on the sender balance, use the correct nonce for the sender …

If the contract is under your control, you can simply emit a log whenever you want and then watch for log events. If the contract is not under your control or it's a plain account, you have no offici …

When you push in more transactions than the blocks fit in, the block sizes are gradually increased to cater for them, so in theory it's unlimited. … The record for the main net (i.e. real, paid transactions) was something along 8 TPS, but that didn't even dent the system. …

That being said, AFAIK miner miners/pools run the standard algorithm included in Geth, which is: Discard anything below a threshold Gather all the executable transactions (i.e. one for each account) … Pick the more expensive one Repeat from step 2. until no more transactions fit into the block Few caveats: The algorithm is actually a bit smarter and does a fancy sort so that steps 2-3-4 can be done …

Please paste the command you are trying to send the transaction with. A plain transaction needs 21000 gas per the protocol parameters. A block on the current main net goes up to 3 * PI million / 2, or …

The second is simpler, the gas fees are deducted from your account, not from the transferred value, so you need only to specify 21K gas (transaction cost) * 50 shannon (minimum gas price currently). …

Given that it's zero indexed and you have 7 executed transactions, means that the last used nonce was 6. …

If you look at your account in a block explorer (e.g. etherchain), you'll see two outgoing transactions. … Well, these are the transaction costs associated with your transactions. …

The personal.sendTransaction method expects a second argument, the password to ephemerally unlock the account with and send the transaction in one go. If you don't provide a password, this endpoint de …