How was the dust limit of 546 satoshis was chosen? Why not 550 satoshis? Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is meant by Bitcoin dust?Why is a transaction with outputs of less than ฿0.00005460 rejected?Could Bitcoin dust spam be effectively combatted by actually including it in the block-chain?Should there be a minimum transaction limit to prevent dust spam?Wallet design: What to do with dust amounts in change?Since Bitcoin Core 0.14.0, how does a node with default settings compute the dust limit?What is the dust limit on Bitcoin Cash transactions?In bitcoin core, how to avoid the dust exception?Electrum 3.3.2 the transaction was rejected by network rules dust error… Tried different nodes, Doesnt WorkDoes bitcoin dust fee rule or policy activate in bitcoin testnet?Does Bitcoin dust limit include miner fee as well?
IndentationError when pasting code in Python 3 interpreter mode
Is there a way in Ruby to make just any one out of many keyword arguments required?
If a contract sometimes uses the wrong name, is it still valid?
Does polymorph use a PC’s CR or its level?
How to bypass password on Windows XP account?
List *all* the tuples!
What causes the vertical darker bands in my photo?
Should gear shift center itself while in neutral?
Can a non-EU citizen traveling with me come with me through the EU passport line?
Did Xerox really develop the first LAN?
3 doors, three guards, one stone
How do I keep my slimes from escaping their pens?
How is the internal pullup resistor in a microcontroller wired?
Why there are no cargo aircraft with "flying wing" design?
Can Pao de Queijo, and similar foods, be kosher for Passover?
Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?
Area of a 2D convex hull
What are 'alternative tunings' of a guitar and why would you use them? Doesn't it make it more difficult to play?
If 'B is more likely given A', then 'A is more likely given B'
Does surprise arrest existing movement?
List numbering with letters
How can I fade player when goes inside or outside of the area?
Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?
Is it true that "carbohydrates are of no use for the basal metabolic need"?
How was the dust limit of 546 satoshis was chosen? Why not 550 satoshis?
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?What is meant by Bitcoin dust?Why is a transaction with outputs of less than ฿0.00005460 rejected?Could Bitcoin dust spam be effectively combatted by actually including it in the block-chain?Should there be a minimum transaction limit to prevent dust spam?Wallet design: What to do with dust amounts in change?Since Bitcoin Core 0.14.0, how does a node with default settings compute the dust limit?What is the dust limit on Bitcoin Cash transactions?In bitcoin core, how to avoid the dust exception?Electrum 3.3.2 the transaction was rejected by network rules dust error… Tried different nodes, Doesnt WorkDoes bitcoin dust fee rule or policy activate in bitcoin testnet?Does Bitcoin dust limit include miner fee as well?
Is there a reason why 546 satoshis was chosen as dust limit instead of 547 or even 550 satoshis, historically?
history dust
asked 7 hours ago
MCCCSMCCCS
4,97431444
add a comment |
Is there a reason why 546 satoshis was chosen as dust limit instead of 547 or even 550 satoshis, historically?
history dust
asked 7 hours ago
MCCCSMCCCS
4,97431444
add a comment |
Is there a reason why 546 satoshis was chosen as dust limit instead of 547 or even 550 satoshis, historically?
history dust
asked 7 hours ago
MCCCSMCCCS
4,97431444
Is there a reason why 546 satoshis was chosen as dust limit instead of 547 or even 550 satoshis, historically?
history dust
history dust
asked 7 hours ago
MCCCSMCCCS
4,97431444
asked 7 hours ago
MCCCSMCCCS
4,97431444
asked 7 hours ago
MCCCSMCCCS
4,97431444
asked 7 hours ago
MCCCSMCCCS
4,97431444
asked 7 hours ago
MCCCSMCCCS
4,97431444
4,97431444
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The dust limit is not actually fixed, technically - it varies based on the type of output. 546 satoshis is simply the most commonly known one, for a p2pkh output. Being the longest-lived output type, I suspect some wallets/blog posts/literature might treat it as a hard coded dust limit.
As to how to arrive at 546 satoshis, we must first know what "dust" means. A dust output is an output which costs more to spend, than it is worth. In other worse, an X BTC output that costs >X to spend, is a dust output. This is directly proportional to the amount of data required to spend an output, since fees in bitcoin are commonly denoted "per-byte". The more bytes you must add to your tx to spend an output, the higher its dust threshold.
A very basic tx consisting of 1 p2pkh input (~148 bytes), and 1 p2pkh output (~34 bytes) comes out to 182 bytes. The dust limit is 3 times this number (assuming a relay fee of 1 satoshi), or 182*3 = 546 sats.
For more complex txs, such as p2sh, this number is larger. For less space-intensive ones such as the newer segwit options, this number would be lower.
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why3*relay feewas selected. As for the relay fee bit, I believe it comes from theminrelaytxfeeflag for bitcoind, which lets you control which transactions your node relays based on fee
– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
add a comment |
Bitcoin core sets the dust limit to a value where spending an output would exceed 1/3 of its value. This calculation is based on the node's setting for the minimum relay transaction fee (see option -minrelaytxfee) whose default is 0.00001 BTC/KB. Any transaction with a fee less than that does not get relayed by the node i.e. is dropped from its mempool.
For a node that uses the default -minrelaytxfee of 0.00001 BTC/KB (1000 satoshis/KB) and given that for P2PKH an input is 148 bytes and an output is 34 bytes, it follows that an output less than or equal to 546 satoshis is considered dust according to Bicoin core.
Reference: What is meant by Bitcoin dust?
answered 5 hours ago
Thalis K.Thalis K.
1967
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "308"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f86068%2fhow-was-the-dust-limit-of-546-satoshis-was-chosen-why-not-550-satoshis%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The dust limit is not actually fixed, technically - it varies based on the type of output. 546 satoshis is simply the most commonly known one, for a p2pkh output. Being the longest-lived output type, I suspect some wallets/blog posts/literature might treat it as a hard coded dust limit.
As to how to arrive at 546 satoshis, we must first know what "dust" means. A dust output is an output which costs more to spend, than it is worth. In other worse, an X BTC output that costs >X to spend, is a dust output. This is directly proportional to the amount of data required to spend an output, since fees in bitcoin are commonly denoted "per-byte". The more bytes you must add to your tx to spend an output, the higher its dust threshold.
A very basic tx consisting of 1 p2pkh input (~148 bytes), and 1 p2pkh output (~34 bytes) comes out to 182 bytes. The dust limit is 3 times this number (assuming a relay fee of 1 satoshi), or 182*3 = 546 sats.
For more complex txs, such as p2sh, this number is larger. For less space-intensive ones such as the newer segwit options, this number would be lower.
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why3*relay feewas selected. As for the relay fee bit, I believe it comes from theminrelaytxfeeflag for bitcoind, which lets you control which transactions your node relays based on fee
– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
add a comment |
The dust limit is not actually fixed, technically - it varies based on the type of output. 546 satoshis is simply the most commonly known one, for a p2pkh output. Being the longest-lived output type, I suspect some wallets/blog posts/literature might treat it as a hard coded dust limit.
As to how to arrive at 546 satoshis, we must first know what "dust" means. A dust output is an output which costs more to spend, than it is worth. In other worse, an X BTC output that costs >X to spend, is a dust output. This is directly proportional to the amount of data required to spend an output, since fees in bitcoin are commonly denoted "per-byte". The more bytes you must add to your tx to spend an output, the higher its dust threshold.
A very basic tx consisting of 1 p2pkh input (~148 bytes), and 1 p2pkh output (~34 bytes) comes out to 182 bytes. The dust limit is 3 times this number (assuming a relay fee of 1 satoshi), or 182*3 = 546 sats.
For more complex txs, such as p2sh, this number is larger. For less space-intensive ones such as the newer segwit options, this number would be lower.
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why3*relay feewas selected. As for the relay fee bit, I believe it comes from theminrelaytxfeeflag for bitcoind, which lets you control which transactions your node relays based on fee
– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
add a comment |
The dust limit is not actually fixed, technically - it varies based on the type of output. 546 satoshis is simply the most commonly known one, for a p2pkh output. Being the longest-lived output type, I suspect some wallets/blog posts/literature might treat it as a hard coded dust limit.
As to how to arrive at 546 satoshis, we must first know what "dust" means. A dust output is an output which costs more to spend, than it is worth. In other worse, an X BTC output that costs >X to spend, is a dust output. This is directly proportional to the amount of data required to spend an output, since fees in bitcoin are commonly denoted "per-byte". The more bytes you must add to your tx to spend an output, the higher its dust threshold.
A very basic tx consisting of 1 p2pkh input (~148 bytes), and 1 p2pkh output (~34 bytes) comes out to 182 bytes. The dust limit is 3 times this number (assuming a relay fee of 1 satoshi), or 182*3 = 546 sats.
For more complex txs, such as p2sh, this number is larger. For less space-intensive ones such as the newer segwit options, this number would be lower.
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
The dust limit is not actually fixed, technically - it varies based on the type of output. 546 satoshis is simply the most commonly known one, for a p2pkh output. Being the longest-lived output type, I suspect some wallets/blog posts/literature might treat it as a hard coded dust limit.
As to how to arrive at 546 satoshis, we must first know what "dust" means. A dust output is an output which costs more to spend, than it is worth. In other worse, an X BTC output that costs >X to spend, is a dust output. This is directly proportional to the amount of data required to spend an output, since fees in bitcoin are commonly denoted "per-byte". The more bytes you must add to your tx to spend an output, the higher its dust threshold.
A very basic tx consisting of 1 p2pkh input (~148 bytes), and 1 p2pkh output (~34 bytes) comes out to 182 bytes. The dust limit is 3 times this number (assuming a relay fee of 1 satoshi), or 182*3 = 546 sats.
For more complex txs, such as p2sh, this number is larger. For less space-intensive ones such as the newer segwit options, this number would be lower.
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
answered 7 hours ago
Raghav SoodRaghav Sood
7,77621127
7,77621127
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why3*relay feewas selected. As for the relay fee bit, I believe it comes from theminrelaytxfeeflag for bitcoind, which lets you control which transactions your node relays based on fee
– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
add a comment |
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why3*relay feewas selected. As for the relay fee bit, I believe it comes from theminrelaytxfeeflag for bitcoind, which lets you control which transactions your node relays based on fee
– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
I think this answer could be clarified a bit. It seems to boil down to the statement that "the dust limit is fixed at 3 satoshis per byte", which raises the question as to how this figure was selected. Also, referring to this as a "relay fee" seems misleading because no fees are collected by nodes who merely relay transactions.
– Nate Eldredge
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why
3*relay fee was selected. As for the relay fee bit, I believe it comes from the minrelaytxfee flag for bitcoind, which lets you control which transactions your node relays based on fee– Raghav Sood
7 hours ago
@NateEldredge Absolutely - I'm trying to look up some sources I read ages ago on why
3*relay fee was selected. As for the relay fee bit, I believe it comes from the minrelaytxfee flag for bitcoind, which lets you control which transactions your node relays based on fee– Raghav Sood
7 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
Wasn't it the case that dust limit was introduced to prevent creation of UTXOs whose value is lower than the cost of scriptSig to spend it? For a 148 byte input, scriptSig would be 107 bytes. That is ~34*3.
– Ugam Kamat
6 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
I think Ugam is right according to this.
– MCCCS
5 hours ago
add a comment |
Bitcoin core sets the dust limit to a value where spending an output would exceed 1/3 of its value. This calculation is based on the node's setting for the minimum relay transaction fee (see option -minrelaytxfee) whose default is 0.00001 BTC/KB. Any transaction with a fee less than that does not get relayed by the node i.e. is dropped from its mempool.
For a node that uses the default -minrelaytxfee of 0.00001 BTC/KB (1000 satoshis/KB) and given that for P2PKH an input is 148 bytes and an output is 34 bytes, it follows that an output less than or equal to 546 satoshis is considered dust according to Bicoin core.
Reference: What is meant by Bitcoin dust?
answered 5 hours ago
Thalis K.Thalis K.
1967
add a comment |
Bitcoin core sets the dust limit to a value where spending an output would exceed 1/3 of its value. This calculation is based on the node's setting for the minimum relay transaction fee (see option -minrelaytxfee) whose default is 0.00001 BTC/KB. Any transaction with a fee less than that does not get relayed by the node i.e. is dropped from its mempool.
For a node that uses the default -minrelaytxfee of 0.00001 BTC/KB (1000 satoshis/KB) and given that for P2PKH an input is 148 bytes and an output is 34 bytes, it follows that an output less than or equal to 546 satoshis is considered dust according to Bicoin core.
Reference: What is meant by Bitcoin dust?
answered 5 hours ago
Thalis K.Thalis K.
1967
add a comment |
Bitcoin core sets the dust limit to a value where spending an output would exceed 1/3 of its value. This calculation is based on the node's setting for the minimum relay transaction fee (see option -minrelaytxfee) whose default is 0.00001 BTC/KB. Any transaction with a fee less than that does not get relayed by the node i.e. is dropped from its mempool.
For a node that uses the default -minrelaytxfee of 0.00001 BTC/KB (1000 satoshis/KB) and given that for P2PKH an input is 148 bytes and an output is 34 bytes, it follows that an output less than or equal to 546 satoshis is considered dust according to Bicoin core.
Reference: What is meant by Bitcoin dust?
answered 5 hours ago
Thalis K.Thalis K.
1967
Bitcoin core sets the dust limit to a value where spending an output would exceed 1/3 of its value. This calculation is based on the node's setting for the minimum relay transaction fee (see option -minrelaytxfee) whose default is 0.00001 BTC/KB. Any transaction with a fee less than that does not get relayed by the node i.e. is dropped from its mempool.
For a node that uses the default -minrelaytxfee of 0.00001 BTC/KB (1000 satoshis/KB) and given that for P2PKH an input is 148 bytes and an output is 34 bytes, it follows that an output less than or equal to 546 satoshis is considered dust according to Bicoin core.
Reference: What is meant by Bitcoin dust?
answered 5 hours ago
Thalis K.Thalis K.
1967
answered 5 hours ago
Thalis K.Thalis K.
1967
answered 5 hours ago
Thalis K.Thalis K.
1967
answered 5 hours ago
Thalis K.Thalis K.
1967
1967
add a comment |
add a comment |
Thanks for contributing an answer to Bitcoin Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f86068%2fhow-was-the-dust-limit-of-546-satoshis-was-chosen-why-not-550-satoshis%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
