<p>You add the transaction T to your (the sender's) unconfirmed transactions pool. From there on, it is treated like any other transaction. Then, your client will send a "inv" message to it's peers saying it has a transaction with hash H. (H being the hash of T) If the peers don't have it, they will send a "gettx" message requesting it, and your client will send it to them. They then add it to their list of unconfirmed transactions and they will do the same thing with their peers.</p>

CC BY-SA 3.0
2013-04-27T03:03:02.097Z
What are the maximum and minimum sizes of a set of transactions associated with a block being mined?
Charles Hoskinson
CC BY-SA 3.0
2013-04-27T16:33:39.330Z
Maximum is 1 megabyte. (Transactions are different sizes) Minimum is 1 transaction (You need the coinbase transaction where coins are made out of thin air as reward to the miner)
lurf jurv
CC BY-SA 3.0
2013-04-27T16:34:53.773Z
Also, the miner is constantly mining, no matter how many transactions he currently has.
lurf jurv
CC BY-SA 3.0
2013-04-28T22:19:55.223Z
So has anyone modeled the transaction fill versus solution time? What are the average amount of transactions verified per block? I also assume miners can choose to verify only transactors who give fees?
Charles Hoskinson
CC BY-SA 3.0
2013-05-02T13:40:46.363Z
Most miners will verify every transaction that they receive that pays at least the minimum fee. Some will verify every transaction (It doesn't cost them anything, it's just setting a bad example; transactions that pay no fees shouldn't be verified because of DOS protection reasons). In the future, when there are more transactions, fees are expected to go up because of the scarcity of block space.
lurf jurv
CC BY-SA 3.0
2013-05-02T16:17:39.657Z
Again I repeat my question: What is the average amount of transactions verified per block?
Charles Hoskinson
CC BY-SA 3.0
2013-05-03T00:52:21.537Z
It varies, but the average of the last 10 blocks is 330 transactions per block. That's about 1.8 transactions per second.
lurf jurv
CC BY-SA 3.0
2013-04-27T02:57:06.100Z
2013-04-27T02:57:06.100Z
lurf jurv
<p>Say I am a node (M1) in the bitcoin network who wishes to spend some set of bitcoins (T). M1 selects address (A1) with an associated node (M2) that he wishes to transact with and uses some process (F) involving T's private key to sign over T to A1 to be controlled by M2. </p>

<p>My question is how does T get broadcast to the bitcoin network? What model does the software enforce to announce a transaction has occurred? How is this message relayed and what kind of bandwidth does the relay require? Do all nodes reach participate in the transaction relay or just some? How does a miner decide to verify transaction T during his block solution hunt? How many transactions are considered to be a minimum for a block and how many are considered to be a maximum? And finally how long does a miner wait to fill his transaction queue for a given block solution hunt?</p>

CC BY-SA 3.0
2013-04-27T02:41:26.473Z
Why is M1 a node, but M2 is an address?
Nick ODell
<transactions>
Transaction and Node Proximity Questions
Charles Hoskinson
# Transaction and Node Proximity Questions

(Asked by: username_0 on 2013-04-27)

Say I am a node (M1) in the bitcoin network who wishes to spend some set of bitcoins (T). M1 selects address (A1) with an associated node (M2) that he wishes to transact with and uses some process (F) involving T's private key to sign over T to A1 to be controlled by M2.

My question is how does T get broadcast to the bitcoin network? What model does the software enforce to announce a transaction has occurred? How is this message relayed and what kind of bandwidth does the relay require? Do all nodes reach participate in the transaction relay or just some? How does a miner decide to verify transaction T during his block solution hunt? How many transactions are considered to be a minimum for a block and how many are considered to be a maximum? And finally how long does a miner wait to fill his transaction queue for a given block solution hunt?

**Tags:** transactions

> **Comments:**
> **username_1**: Why is M1 a node, but M2 is an address?  

---

## 1 answers

### Answer by username_2 on 2013-04-27. Score: 1

You add the transaction T to your (the sender's) unconfirmed transactions pool. From there on, it is treated like any other transaction. Then, your client will send a "inv" message to it's peers saying it has a transaction with hash H. (H being the hash of T) If the peers don't have it, they will send a "gettx" message requesting it, and your client will send it to them. They then add it to their list of unconfirmed transactions and they will do the same thing with their peers.

> **Comments:**
> **username_0**: What are the maximum and minimum sizes of a set of transactions associated with a block being mined?  
> **username_2**: Maximum is 1 megabyte. (Transactions are different sizes) Minimum is 1 transaction (You need the coinbase transaction where coins are made out of thin air as reward to the miner)  
> **username_2**: Also, the miner is constantly mining, no matter how many transactions he currently has.  
> **username_0**: So has anyone modeled the transaction fill versus solution time? What are the average amount of transactions verified per block? I also assume miners can choose to verify only transactors who give fees?  
> **username_2**: Most miners will verify every transaction that they receive that pays at least the minimum fee. Some will verify every transaction (It doesn't cost them anything, it's just setting a bad example; transactions that pay no fees shouldn't be verified because of DOS protection reasons). In the future, when there are more transactions, fees are expected to go up because of the scarcity of block space.  
> **username_0**: Again I repeat my question: What is the average amount of transactions verified per block?  
> **username_2**: It varies, but the average of the last 10 blocks is 330 transactions per block. That's about 1.8 transactions per second.  

---

