Is there a solution to paying high fees when opening and closing lightning channels once we hit a fee only market?What are Channel Factories and how do they work?Transaction overriding in lightning networkDo Lightning Channels have to be resolved before a certain time?Is lightning network limited by the 'size' of channels?The cost of restarting a lightning channelLightning network explaination (bidirectional channel funded by one party)What is the size of different types of channel funding/closing transactions for the Lightning Network?Lightning Route Discovery - How to know capacity in each direction?Lightning network avoiding bad channelsLightning: How would I make a monthly payment to a utility company, etcWhy do we need a “routing” process in Lightning Network?
Is there a solution to paying high fees when opening and closing lightning channels once we hit a fee only market?
Why do testers need root cause analysis?
Was murdering a slave illegal in American slavery, and if so, what punishments were given for it?
Three knights or knaves, three different hair colors
Which values for voltage divider
What is the required burn to keep a satellite at a Lagrangian point?
Caught with my phone during an exam
Why is this integration method not valid?
Illustrating that universal optimality is stronger than sphere packing
Is being an extrovert a necessary condition to be a manager?
How would a physicist explain this starship engine?
What is the winged creature on the back of the Mordenkainen's Tome of Foes book?
Wifi light switch needs neutral wire. Why? AND Can that wire be a skinny one?
Why is this python script running in background consuming 100 % CPU?
Real Analysis: Proof of the equivalent definitions of the derivative.
What does it mean for something to be strictly less than epsilon for an arbitrary epsilon?
Are clauses with "который" restrictive or non-restrictive by default?
Does science define life as "beginning at conception"?
What pc resources are used when bruteforcing?
Why did Nick Fury not hesitate in blowing up the plane he thought was carrying a nuke?
why "American-born", not "America-born"?
Is ideal gas incompressible?
Meaning of "half-crown enclosure"
Can diplomats be allowed on the flight deck of a commercial European airline?
Is there a solution to paying high fees when opening and closing lightning channels once we hit a fee only market?
What are Channel Factories and how do they work?Transaction overriding in lightning networkDo Lightning Channels have to be resolved before a certain time?Is lightning network limited by the 'size' of channels?The cost of restarting a lightning channelLightning network explaination (bidirectional channel funded by one party)What is the size of different types of channel funding/closing transactions for the Lightning Network?Lightning Route Discovery - How to know capacity in each direction?Lightning network avoiding bad channelsLightning: How would I make a monthly payment to a utility company, etcWhy do we need a “routing” process in Lightning Network?
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers, I’m yet to read a valid argument against this.
transaction-fees lightning-network fee-market
add a comment |
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers, I’m yet to read a valid argument against this.
transaction-fees lightning-network fee-market
add a comment |
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers, I’m yet to read a valid argument against this.
transaction-fees lightning-network fee-market
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers, I’m yet to read a valid argument against this.
transaction-fees lightning-network fee-market
transaction-fees lightning-network fee-market
asked 3 hours ago
Electric_Sheep01Electric_Sheep01
282
282
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
'Under the hood' of a lightning network channel open/close, a user will be sending a bitcoin transaction. In order to send a bitcoin transaction, a fee is paid to miners.
One advantage of having a lightning channel is that you can amortize the cost of the miners fee across a potentially enormous number of payments. All else equal, having the ability to transact on the lightning network thus lowers a users expected fees/payment, small blocks or not.
Channel factories are a technology that could allow for immense cost saving for lightning users. So this is potentially a 'solution', in the context of your question.
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers
'Uneconimcal' doesn't seem like the right word to use here. If in the future a bitcoin transaction costs hundreds of dollars in fees, that would mean that the ability to send a bitcoin transaction is in high demand. By many measures, being in high demand is a mark of success, though 'big-blockers' will argue that by increasing the block size the network can increase the 'supply', thus lowering transaction fees.
To illustrate this point, consider the absurdity of this sentence:
"That restaurant has become very popular! Nobody goes there anymore"
So you may ask "Why don't we just increase the size of the restaurant then?"
Well, the issue is that by increasing the size of the restaurant, the restaurant will lose the properties that made it popular in the first place!
So lets return to Bitcoin, to explain why increasing the block size ('making the restaurant larger') is a naïve solution that damages the network's desirable properties, while only providing a rather meagre linear scaling relief:
Implementing larger blocks means that running a full node on the network will be more resource intensive (bandwidth, computational cycles, storage, etc), and so naturally we should expect less nodes will exist due to the increased costs. This is damaging to the core properties of bitcoin (eg censorship resistance), which can only exist when the network is sufficiently decentralized. 'How decentralized is good enough?' is a question that is difficult (if not impossible) to answer, but this much is certain: increasing costs is a centralizing force, and the most conservative approach is to be 'better safe than sorry'. A blockchain network is a very expensive and inefficient way to implement a database, but the core properties mentioned above make these expenses 'worth it', at least according to the market.
In any case, there has never been a time where the average Bitcoin transaction fee is 'hundreds of dollars'... in fact transaction fees have been quite low for the majority of the history of the network. This isn't to say that fees can't or won't increase in the future, but making changes that sacrifice the most important properties of Bitcoin seems like an extremely misguided approach to scaling the network.
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
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%2f87843%2fis-there-a-solution-to-paying-high-fees-when-opening-and-closing-lightning-chann%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
'Under the hood' of a lightning network channel open/close, a user will be sending a bitcoin transaction. In order to send a bitcoin transaction, a fee is paid to miners.
One advantage of having a lightning channel is that you can amortize the cost of the miners fee across a potentially enormous number of payments. All else equal, having the ability to transact on the lightning network thus lowers a users expected fees/payment, small blocks or not.
Channel factories are a technology that could allow for immense cost saving for lightning users. So this is potentially a 'solution', in the context of your question.
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers
'Uneconimcal' doesn't seem like the right word to use here. If in the future a bitcoin transaction costs hundreds of dollars in fees, that would mean that the ability to send a bitcoin transaction is in high demand. By many measures, being in high demand is a mark of success, though 'big-blockers' will argue that by increasing the block size the network can increase the 'supply', thus lowering transaction fees.
To illustrate this point, consider the absurdity of this sentence:
"That restaurant has become very popular! Nobody goes there anymore"
So you may ask "Why don't we just increase the size of the restaurant then?"
Well, the issue is that by increasing the size of the restaurant, the restaurant will lose the properties that made it popular in the first place!
So lets return to Bitcoin, to explain why increasing the block size ('making the restaurant larger') is a naïve solution that damages the network's desirable properties, while only providing a rather meagre linear scaling relief:
Implementing larger blocks means that running a full node on the network will be more resource intensive (bandwidth, computational cycles, storage, etc), and so naturally we should expect less nodes will exist due to the increased costs. This is damaging to the core properties of bitcoin (eg censorship resistance), which can only exist when the network is sufficiently decentralized. 'How decentralized is good enough?' is a question that is difficult (if not impossible) to answer, but this much is certain: increasing costs is a centralizing force, and the most conservative approach is to be 'better safe than sorry'. A blockchain network is a very expensive and inefficient way to implement a database, but the core properties mentioned above make these expenses 'worth it', at least according to the market.
In any case, there has never been a time where the average Bitcoin transaction fee is 'hundreds of dollars'... in fact transaction fees have been quite low for the majority of the history of the network. This isn't to say that fees can't or won't increase in the future, but making changes that sacrifice the most important properties of Bitcoin seems like an extremely misguided approach to scaling the network.
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
add a comment |
'Under the hood' of a lightning network channel open/close, a user will be sending a bitcoin transaction. In order to send a bitcoin transaction, a fee is paid to miners.
One advantage of having a lightning channel is that you can amortize the cost of the miners fee across a potentially enormous number of payments. All else equal, having the ability to transact on the lightning network thus lowers a users expected fees/payment, small blocks or not.
Channel factories are a technology that could allow for immense cost saving for lightning users. So this is potentially a 'solution', in the context of your question.
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers
'Uneconimcal' doesn't seem like the right word to use here. If in the future a bitcoin transaction costs hundreds of dollars in fees, that would mean that the ability to send a bitcoin transaction is in high demand. By many measures, being in high demand is a mark of success, though 'big-blockers' will argue that by increasing the block size the network can increase the 'supply', thus lowering transaction fees.
To illustrate this point, consider the absurdity of this sentence:
"That restaurant has become very popular! Nobody goes there anymore"
So you may ask "Why don't we just increase the size of the restaurant then?"
Well, the issue is that by increasing the size of the restaurant, the restaurant will lose the properties that made it popular in the first place!
So lets return to Bitcoin, to explain why increasing the block size ('making the restaurant larger') is a naïve solution that damages the network's desirable properties, while only providing a rather meagre linear scaling relief:
Implementing larger blocks means that running a full node on the network will be more resource intensive (bandwidth, computational cycles, storage, etc), and so naturally we should expect less nodes will exist due to the increased costs. This is damaging to the core properties of bitcoin (eg censorship resistance), which can only exist when the network is sufficiently decentralized. 'How decentralized is good enough?' is a question that is difficult (if not impossible) to answer, but this much is certain: increasing costs is a centralizing force, and the most conservative approach is to be 'better safe than sorry'. A blockchain network is a very expensive and inefficient way to implement a database, but the core properties mentioned above make these expenses 'worth it', at least according to the market.
In any case, there has never been a time where the average Bitcoin transaction fee is 'hundreds of dollars'... in fact transaction fees have been quite low for the majority of the history of the network. This isn't to say that fees can't or won't increase in the future, but making changes that sacrifice the most important properties of Bitcoin seems like an extremely misguided approach to scaling the network.
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
add a comment |
'Under the hood' of a lightning network channel open/close, a user will be sending a bitcoin transaction. In order to send a bitcoin transaction, a fee is paid to miners.
One advantage of having a lightning channel is that you can amortize the cost of the miners fee across a potentially enormous number of payments. All else equal, having the ability to transact on the lightning network thus lowers a users expected fees/payment, small blocks or not.
Channel factories are a technology that could allow for immense cost saving for lightning users. So this is potentially a 'solution', in the context of your question.
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers
'Uneconimcal' doesn't seem like the right word to use here. If in the future a bitcoin transaction costs hundreds of dollars in fees, that would mean that the ability to send a bitcoin transaction is in high demand. By many measures, being in high demand is a mark of success, though 'big-blockers' will argue that by increasing the block size the network can increase the 'supply', thus lowering transaction fees.
To illustrate this point, consider the absurdity of this sentence:
"That restaurant has become very popular! Nobody goes there anymore"
So you may ask "Why don't we just increase the size of the restaurant then?"
Well, the issue is that by increasing the size of the restaurant, the restaurant will lose the properties that made it popular in the first place!
So lets return to Bitcoin, to explain why increasing the block size ('making the restaurant larger') is a naïve solution that damages the network's desirable properties, while only providing a rather meagre linear scaling relief:
Implementing larger blocks means that running a full node on the network will be more resource intensive (bandwidth, computational cycles, storage, etc), and so naturally we should expect less nodes will exist due to the increased costs. This is damaging to the core properties of bitcoin (eg censorship resistance), which can only exist when the network is sufficiently decentralized. 'How decentralized is good enough?' is a question that is difficult (if not impossible) to answer, but this much is certain: increasing costs is a centralizing force, and the most conservative approach is to be 'better safe than sorry'. A blockchain network is a very expensive and inefficient way to implement a database, but the core properties mentioned above make these expenses 'worth it', at least according to the market.
In any case, there has never been a time where the average Bitcoin transaction fee is 'hundreds of dollars'... in fact transaction fees have been quite low for the majority of the history of the network. This isn't to say that fees can't or won't increase in the future, but making changes that sacrifice the most important properties of Bitcoin seems like an extremely misguided approach to scaling the network.
'Under the hood' of a lightning network channel open/close, a user will be sending a bitcoin transaction. In order to send a bitcoin transaction, a fee is paid to miners.
One advantage of having a lightning channel is that you can amortize the cost of the miners fee across a potentially enormous number of payments. All else equal, having the ability to transact on the lightning network thus lowers a users expected fees/payment, small blocks or not.
Channel factories are a technology that could allow for immense cost saving for lightning users. So this is potentially a 'solution', in the context of your question.
Paying several hundred dollars to open and close a lightning channel seems uneconomical. This is a common argument against lightning by big blockers
'Uneconimcal' doesn't seem like the right word to use here. If in the future a bitcoin transaction costs hundreds of dollars in fees, that would mean that the ability to send a bitcoin transaction is in high demand. By many measures, being in high demand is a mark of success, though 'big-blockers' will argue that by increasing the block size the network can increase the 'supply', thus lowering transaction fees.
To illustrate this point, consider the absurdity of this sentence:
"That restaurant has become very popular! Nobody goes there anymore"
So you may ask "Why don't we just increase the size of the restaurant then?"
Well, the issue is that by increasing the size of the restaurant, the restaurant will lose the properties that made it popular in the first place!
So lets return to Bitcoin, to explain why increasing the block size ('making the restaurant larger') is a naïve solution that damages the network's desirable properties, while only providing a rather meagre linear scaling relief:
Implementing larger blocks means that running a full node on the network will be more resource intensive (bandwidth, computational cycles, storage, etc), and so naturally we should expect less nodes will exist due to the increased costs. This is damaging to the core properties of bitcoin (eg censorship resistance), which can only exist when the network is sufficiently decentralized. 'How decentralized is good enough?' is a question that is difficult (if not impossible) to answer, but this much is certain: increasing costs is a centralizing force, and the most conservative approach is to be 'better safe than sorry'. A blockchain network is a very expensive and inefficient way to implement a database, but the core properties mentioned above make these expenses 'worth it', at least according to the market.
In any case, there has never been a time where the average Bitcoin transaction fee is 'hundreds of dollars'... in fact transaction fees have been quite low for the majority of the history of the network. This isn't to say that fees can't or won't increase in the future, but making changes that sacrifice the most important properties of Bitcoin seems like an extremely misguided approach to scaling the network.
answered 1 hour ago
chytrikchytrik
8,0612629
8,0612629
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
add a comment |
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
Chanel factories and eltoo where my first thought as well. What do you think about side chains? For example lightning could be build on top of Liquid and the cross chain Atomic swap should not be a problem. In particular the American call option Problem should not exist as the underlying asset is the same by the end of the day. In that sense we would have a fragmented base layer in which tx costs should not rise to heavily.
– Rene Pickhardt
1 hour ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
@RenePickhardt hmm interesting! I hadn't considered the possibility of sidechain/mainchain LN interoperability as a means of lowering fees. While the trust model of holding liquid coins is different, I think it could quite reasonably be argued that the potential cost savings would be worth the tradeoff for some users. I think you could post that idea as an answer as well, it seems reasonable to me!
– chytrik
52 mins ago
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%2f87843%2fis-there-a-solution-to-paying-high-fees-when-opening-and-closing-lightning-chann%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