Bitcoin Forum
June 19, 2021, 10:41:15 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin transaction larger than 1 MB?  (Read 284 times)
0xfff
Full Member
***
Offline Offline

Activity: 224
Merit: 100


View Profile
February 10, 2017, 03:19:09 PM
 #1

What would happen if you tried to send a tx larger than 1 MB? It couldn't fit in a block so would it even be included in mem pool? How many inputs/outputs would you need for a 1 MB transaction?
1624099275
Hero Member
*
Offline Offline

Posts: 1624099275

View Profile Personal Message (Offline)

Ignore
1624099275
Reply with quote  #2

1624099275
Report to moderator
1624099275
Hero Member
*
Offline Offline

Posts: 1624099275

View Profile Personal Message (Offline)

Ignore
1624099275
Reply with quote  #2

1624099275
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1624099275
Hero Member
*
Offline Offline

Posts: 1624099275

View Profile Personal Message (Offline)

Ignore
1624099275
Reply with quote  #2

1624099275
Report to moderator
bg002h
Donator
Legendary
*
Offline Offline

Activity: 1445
Merit: 1016


I outlived my lifetime membership:)


View Profile WWW
February 10, 2017, 03:55:42 PM
 #2

Block size limit is one of many limits in the consensus rules. There are limits to the number of signature / hash operations as well as input and outputs. I'm not sure you could make a >1MB transaction that conformed to these ancillary rules, but if you did no one would add it to a block. It might make for a decent attack vector though…to clog up the relay function of the network.

Hardforks aren't that hard. It’s getting others to use them that's hard.
1GCDzqmX2Cf513E8NeThNHxiYEivU1Chhe
iGotSpots
Legendary
*
Offline Offline

Activity: 2310
Merit: 1054



View Profile WWW
February 10, 2017, 04:04:22 PM
 #3

What would happen if you tried to send a tx larger than 1 MB? It couldn't fit in a block so would it even be included in mem pool? How many inputs/outputs would you need for a 1 MB transaction?

It would just get rejected. Combining about 876 inputs should put you above

greenlion
Hero Member
*****
Offline Offline

Activity: 668
Merit: 500


View Profile
February 10, 2017, 06:36:32 PM
 #4

There are two separate aspects of the system that would stop such a thing --

1) Transactions > 100 kb are considered non-standard by nodes. This isn't a consensus rule, but it's local policy where nodes will refuse to relay the transaction. In general you would have to manually submit your raw tx to a miner to get anything nonstandard mined, because the network will not propagate it for you. This is why it wouldn't end up in the mempool.

2) The 1MB blocksize cap will stop a miner from including it in a block, because it would be impossible for a miner to construct a candidate block that would be valid and includes your >1MB transaction.

There isn't really a way to answer how many inputs and outputs you would need, because for normal p2pkh tx's outputs are smaller than inputs (because you have to include signature data in the tx), but ballpark based on how many typical transactions fit in a block, it would be somewhere in the neighborhood of a few thousand, depending on the exact inputs and outputs.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!