Pages:
Author

Topic: SEGWIT & LN KILLING OFF the OnChain Miners (Better start looking for new Jobs) (Read 2307 times)

legendary
Activity: 1092
Merit: 1000
How do the signatures work?  They are separated into two separate blocks so there would be two blockchains running? One would store a block of transactions and a block of signatures?

blockstream put in the FIBRE network to change the topology of the network (as gatekeepers) so that if segwit activates the segwit nodes control what gets filtered down to old native nodes.

in simple terms segwit nodes receive a cluster of data which is one lump of data called the blockweight where the signatures have their own txid to link back to the txid of the baseblock. if they have whitelisted old native nodes they have to send the smaller 'base' block' to old native nodes

its bait and switched to pretend its one network but because the old nodes are not receiving the same data as the segwit nodes. a fresh segwit node wont sync from a native node.

a native node wont receive segwit unconfirmed transactions. so its a 'pretend' single network. but with differing data held and/or relayed.
same goes with segwits pruned nodes. a segwit node wanting a full sync wont sync from a pruned node. so again all these core features are causing issues for the REAL full node count.because not all the nodes hold all the same data.

core have swept under the carpet how they have made anything not segwit as being second class. but pretended its all good because its "compatible"

as you can see below.
on the left is what people for 6-7 years thought the node network looked like. with pools sending out data and EVERYONE sharing the same data.
on the right is how how segwit/fibre has changed the network topology. to centralise segwit as the gate keepers of what data non segwit nodes get


and yes, segwit nodes could simply not whitelist old native nodes and make it reliant on the pools to send data to old nodes, which looking at this image below is the one on the right.(very worse case scenario, but plausible)

EDIT:gmaxwell buzzwords
downstream(old) <-> upstream(segwit) <-> pool
upstream(segwit) <-> pool<-> downstream(old)


its all explained here including the bit about signature/tx data
https://bitcointalksearch.org/topic/m.17607565

legendary
Activity: 1092
Merit: 1000
Latest on Dangers posed by Segwit,
Words of a Former Segwit Supporter Who has Realized the Truth!

Quote
Initially, I liked SegWit. But then I learned SegWit-as-a-SOFT-fork is dangerous (making transactions "anyone-can-spend"??) & centrally planned (1.7MB blocksize??). Instead, Bitcoin Unlimited is simple & safe, with MARKET-BASED BLOCKSIZE. This is why more & more people have decided to REJECT SEGWIT


https://www.reddit.com/r/btc/comments/5vbofp/initially_i_liked_segwit_but_then_i_learned/

Quote
You wanted people like me to support you and install your code, Core / Blockstream?

Then you shouldn't have a released messy, dangerous, centrally planned hack like SegWit-as-a-soft-fork - with its random, arbitrary, centrally planned,
ridiculously tiny 1.7MB blocksize - and its dangerous "anyone-can-spend" soft-fork semantics.

Now it's too late. The market will reject SegWit - and it's all Core / Blockstream's fault.

The market prefers simpler, safer, future-proof, market-based solutions such as Bitcoin Unlimited.

Quote
The damage which would be caused by SegWit (at the financial, software, and governance level) would be massive:

    Millions of lines of other Bitcoin code would have to be rewritten (in wallets, on exchanges, at businesses) in order to become compatible with all the messy non-standard kludges and workarounds which Blockstream was forced into adding to the code (the famous "technical debt") in order to get SegWit to work as a soft fork.

    SegWit was originally sold to us as a "code clean-up". Heck, even I intially fell for it when I saw an early presentation by Pieter Wuille on YouTube from one of Blockstream's many, censored Bitcoin scaling stalling conferences)

    But as we all later all discovered, SegWit is just a messy hack.

    Probably the most dangerous aspect of SegWit is that it changes all transactions into "ANYONE-CAN-SPEND" without SegWit - all because of the messy workarounds necessary to do SegWit as a soft-fork. The kludges and workarounds involving SegWit's "ANYONE-CAN-SPEND" semantics would only work as long as SegWit is still installed.

    This means that it would be impossible to roll-back SegWit - because all SegWit transactions that get recorded on the blockchain would now be interpreted as "ANYONE-CAN-SPEND" - so, SegWit's dangerous and messy "kludges and workarounds and hacks" would have to be made permanent - otherwise, anyone could spend those "ANYONE-CAN-SPEND" SegWit coins!

    Segwit cannot be rolled back because to non-upgraded clients, ANYONE can spend Segwit txn outputs. If Segwit is rolled back, all funds locked in Segwit outputs can be taken by anyone. As more funds gets locked up in segwit outputs, incentive for miners to collude to claim them grows.



 Cool

FYI:
Segwit => Trojan Virus for a Blockchain  Tongue
legendary
Activity: 1092
Merit: 1000
Im saying adding pow on the stack modifier computation not on the block themselves Wink to avoid the staking on multiple chains.

PoS clients are not designed to stake on multiple chains at the same time.


Discussions I had with some people regarding the nonsense call nothing at stake

Quote
Some authors[15][16] argue that proof-of-stake is not an ideal option for a distributed consensus protocol. One problem is usually called the "nothing at stake" problem, where (in the case of a consensus failure) block-generators have nothing to lose by voting for multiple blockchain-histories, which prevents the consensus from ever resolving. Because there is little cost in working on several chains (unlike in proof-of-work systems), anyone can abuse this problem to attempt to double-spend (in case of blockchain reorganization) "for free".[17]

Ok , above is the quote from the wiki.

Here is what is wrong with it.

BadGuy has 50 coins ,   GoodGuy1 has 10 Coin  , GoodGuy2 also staking 10 coins

GoodGuy1 is staking
[10] on the block 500 on Fork1

At the same moment another block is created by GoodGuy2
[10] on the block 500 on Fork2


Now the BadGuy
Since he has nothing to Lose , Stakes his 50 Coins on both Forks

So Now
Fork1 [60]  & Fork2 [60]

Which means by trying to stake on both blocks at the Same Time, all he did was Negate his Staking Power by adding to Both.  Cheesy

Which Fork is chosen will be decided by someone else , not trying to play both sides.
He makes his staking power irrelevant.

The other flaw with the Nothing at Stake Lie, which must be beyond the concept of PoW miners.
When Proof of Stake stakes a Block , Coin Age is used up, meaning those coins will now be offline and unable to stake until their minimum stake age is reached again.
It would be the same as when a PoW miner mined a coin and then immediately turned off his ASICS for a prescribed amount of time.
Which would mean he could mine no other block until , he was allowed to turn his ASICS back on.
Which is why PoS is superior to PoW , as random Chaos is entered into it.
PoW miners can maintain the ~ same HashRate thruout mining while a PoS Staker Amounts & Coin Age are in constant Flux every time they stake.
So what is burned when you stake, Coin Age & Staking Weight is burned, and it takes a minimum stake age before it can be recovered.

 Cool

FYI:
As far as the DoubleSpend , PoW or PoS is susceptible to doublespend with Zero Confirmations .
Solutions for both PoW & PoS is to wait the prescribed amount of Confirmations, and never accept Zero Confirmations.

In nothing at stake attack, as I understand, attackers doesn't stake on both forks. They argue that stable strategy for all honest miners is to mine on all the fork. Then attacker assumes that everyone is doing this and stakes on the double spend fork (or whatever he wants to use instead of main-chain). That is why it doesn't matter how much attacker has. I do find this valid objection, just something not fundamental and trivial to prevent, hence I started this thread.


OK , so you think

Attacker has 1 coin ,   GoodGuy1 has 10 coins GoodGuy2 also staking 10 coins

Fork1
GoodGuy1 is staking
GoodGuy2 is staking
[20]  

At the same moment on Fork2
GoodGuy1 is staking
GoodGuy2 is staking
[20]

Now the Attacker
Places a transaction on Fork1
Stakes his 1 coin on Fork 2

So Now
Fork1 [20] only 2 blocks & Fork2 [21] 3 blocks

Fork2 now has more coins in 3 Blocks, and becomes the longest chain with the most difficulty.

All of this in an attempt at a double spend.
1st off
Standard PoS wallets don't Multi-stake, you would have to code one your self.


Let's say you do and it works exactly as you described and you spend coins on Fork1 and overwrote it when Fork2 became the longest Chain.
Basically a History rewrite.

This is why it will Fail.  Once the fork2 becomes the longest chain, all of the wallets will reorg to fork2 and it will be the correct chain.
This means the coins you sent in the transaction on fork1 will not confirm, and the wallet you sent it too will not reach even 1 confirmation.

Longest chain with the most difficulty wins , just wait the recommend # of confirmations and all zero confirmation attacks fail.


 Cool

FYI:
Double spending if someone accepts zero confirmations is easy on Proof of Work.
I don't even need to be a miner, just paid a higher transaction fee to pull it off.
I had 2 devices with the same BTC wallet , send the coins from the 1st device to the vendor with no fee,
then send all of my BTC from the same wallet on 2nd device to another BTC address I control, including a high fee for faster transactions.
If the Vendor accepts Zero confirmations, he will see the BTC sent from the 1st device, and I exit the store with his product for free.
5 to 10 minutes later after the 1 confirmation, all of my BTC will have arrived at my other BTC address and the Vendor just saw his payment never Confirmed.
Moral is PoW or PoS wait the recommend confirmations.  Wink
legendary
Activity: 1092
Merit: 1000
Im saying adding pow on the stack modifier computation not on the block themselves Wink to avoid the staking on multiple chains.

The way i understand it, the problem with POS chain is that for example in blackcoin there is granulosity of 16 sec on the time nonce used to compute the proof of stake, meaning for each output you are staking on, you have 16 sec to compute the hash for it, so it leave lot of free time, and it would be very possible for an attacker to keep in permanence different valid version of the chain, and push one or the other on the network at any time. It's what make pos coin more vulnerable to transaction maleability. Even if it's not that useable in practice i think, it can still be potentially a pb. Adding some pow on the stake modifier could avoid this to be exploited too much.

Ok,
as of the moment no one has fixed transaction malleability in BTC,

http://www.coindesk.com/bitcoin-bug-guide-transaction-malleability/
Quote
Malicious individual attacks

Let's say that Alice runs an exchange, and Eve has bitcoins sitting in that exchange. Eve decides to withdraw her coins, and asks Alice to send the bitcoins to her address. When Alice sends them, this automatically creates a transaction, which is transmitted for mining so that it can be included in the bitcoin block chain.

But Eve pretends that Alice never sent them. She uses the transaction malleability flaw to reproduce Alice's original transaction, tweaking the signature slightly to produce a different hash. She then retransmits that transaction, with the different ID.

There is a chance that Eve's transaction will be confirmed on the block chain first. If that happens, the network will assume that transaction is valid, and won't record Alice's. Eve can then complain to Alice that she didn't receive the coins. When Alice checks for her transaction ID in the block chain, she won't find it, and she might try to send more bitcoins, meaning that she'll be out of pocket.


BTC allows transactions to SIT in the Mempool while they wait to be chosen (Pick the ones with higher fees) by the Miners,
which means someone could process a transaction with the mallability issue for BTC.

However Proof of Stake ,
Processes the Mempools transactions in the Order in which they Arrive, Meaning by the time Eve tries to retransmit the transaction,
the original transaction was already included in a block, as her transaction can not leap frog over the earlier transaction.  Wink
in Other words Eve's transaction can not jump in front of Alice's transmission on a PoS Coin network,
because the transactions in the mempool are processed in the order they are received and not selected on a fee basis like BTC.


 Cool

FYI:
The Exchange Operator can always just pull up a decent Block Explorer and look at the Sending and Receive Addresses and see if the coins were Sent & Received.
I guess that is why BTC has not hard forked to fix it , not a major issue if you check the addresses instead of the TX id.
Either way, PoS coins prove superior by not being greedy and not letting people jump their transactions in front of others.  Wink
full member
Activity: 322
Merit: 151
They're tactical
Im saying adding pow on the stack modifier computation not on the block themselves Wink to avoid the staking on multiple chains.

The way i understand it, the problem with POS chain is that for example in blackcoin there is granulosity of 16 sec on the time nonce used to compute the proof of stake, meaning for each output you are staking on, you have 16 sec to compute the hash for it, so it leave lot of free time, and it would be very possible for an attacker to keep in permanence different valid version of the chain, and push one or the other on the network at any time. It's what make pos coin more vulnerable to transaction maleability. Even if it's not that useable in practice i think, it can still be potentially a pb. Adding some pow on the stake modifier could avoid this to be exploited too much.
legendary
Activity: 1092
Merit: 1000
Maybe some small proof of work should be added to the stake modifier computation to incite people keeping on a single chain to make it a bit more secure.

Actually adding PoW to a PoS coin has the exact Opposite effect, it adds attack vectors that do not exist without PoW included.
(Reason ZEIT & Mintcoin both dropped PoW from our coins.)

Security analysis of PoW/PoS hybrids with low PoW reward
https://bitcointalksearch.org/topic/security-analysis-of-powpos-hybrids-with-low-pow-reward-551861

Attacks were Proved to Work by Rat4
Quote
Security analysis of PoW/PoS hybrids with low PoW reward

Low PoW reward doesn't attract miners. This leads to ridiculously low PoW difficulty.

A pair of examples:
Mintcoin scrypt diff 0.1 (vs Litecoin 5677)
SHACoin sha256 diff 1427 (vs Bitcoin 5006860589)

At such difficulty PoW blocks can be mined with speed of light.

Attack I

It is possible to build sequential chain of PoW blocks to confirm a transaction. Only 4 blocks for Mintcoin and 10 for SHACoin.

Is it hard to orphan the chain of PoW blocks?
One PoS block is enough. In both Mintcoin and SHACoin one PoS block may orphan a few millions of PoW blocks.
If at the same time the main chain will get a competing stake, attacker's chain can be enlarged with PoW.
This dramatically increases chance to success in comparison to pure PoW attack.

Ability to confirm a transaction and then orphan confirmations is ability to double spend.

Summary: double spend attack requires 1 PoS block and low hashing power.

Visualization: https://i.imgur.com/Pyrw75q.png

Attack II

Current implementation of stake miner gives up if median time of last blocks is in future.
This temporarily makes the whole network PoW-only and opens well known 51% PoW attack.

Attacker needs only 6 of 11 last blocks.

Successfully tested on Mintcoin: no PoS blocks from 203231 up to 203441, more than 1 hour of real time.

 Cool

FYI:
Funny thing is people see this giant # for PoW has and think it is more secure.
When the fact is ,
I can have a      PoS coin with a  difficulty   of 1
and compare to  BTC with it's     difficulty      440,779,902,287 .

The PoS coin with the difficulty # of 1 is just as secure if not more so than the PoW coin with 440,779,902,287.

Because even with that ultra high difficulty, the Chinese Miners could overwrite the last 12 hours or more whenever they felt like it. ( PoW offers False Security)
On the other Hand,
No one has been able to overwrite even 1 hour on a PoS only chain with a decent staking difficulty ,
plus when someone stakes their coins become inactive for a period of time , blocking a continuous control of the network ,
unlike a PoW ASICS which can dominate a chain indefinitely.
full member
Activity: 322
Merit: 151
They're tactical
For me the issue of security with coins is not necessarily mostly about technical issues first.

It's what make bitcoin very successful is because it make in sort everyone participate get some reward somewhere. It's secure because 51% of users keep it so because they have an interest to do it.

With pos ok some people could buy all the coins and screw the chain, but what does he win ? nothing, he just lose all his money dry. No point in doing this.

And i think for small chain, pos can be more secure because with pow there can always be the risk someone outside the network come with some asics and over power it, with pos it need someone who has coin and is on the network. For small chain i tend to think the risk is still smaller with pos than pow.

And there is something i find really nice with pos, is the authority on the chain can be distributed very easily, maybe it's not very useful in the perspective of coins, but if something like a "proof of authority" could be useful in some scenario, with pow it would need the node to compute a big thing to prove it has the pow, and it would need to do this each time it need to give a "proof of authority", and it would be a big waste, and harder to be sure it's distributed evenly between a certain number of entities, with staking just need to check the network weight. And it make it much easier to distribute the authority on the chain, in certain case it can be interesting.

Maybe some small proof of work should be added to the stake modifier computation to incite people keeping on a single chain to make it a bit more secure.
legendary
Activity: 1092
Merit: 1000
And this is one of the many reasons pow sucks. You need a system similar to POS to make it long term. But bitcoin and others will never change because centralized miners in china don't wanna kill the golden goose.

pos suck even more, who buy more coins on the market win, because he can stake more quickly and dump faster, pow is more fair, you can't just go out and buy tons of gpu, as they require space maintenance, electricity ,cooling etc...and last but not last pos is more prone to be double spended, remember mintcoin and its exchange?



Spoken like a PoW miner, Completely Wrong, but hey your a PoW miner, thinking is not your strong suit.  Wink

PoW is only fair to the Rich, that can afford a warehouse full of ASICS.

PoS is the only real game in town for the rest of the world.
PoS that incorporates Coin Age is better protected than PoW from Double spends.
Mintcoin never had any double spends because of Proof of stake to my knowledge, post a link if you have one.
(Are you talking about the security problems that was caused because they were at one time PoW & PoS, which is why they dropped the PoW.)

Mintpal & mintcoin had no affiliations.

 Cool

PoS is flawed. It has been proven to be insecure endless times due the nothing at stake problem which has never been solved.

No PoS coin will ever, ever, ever deliver the security of a network like bitcoin's. You aren't solving anything with PoS. PoS has more problems than PoW and is not as secure.

No one is going to hold value long term in PoS coins, sorry.

You are one of those idiots that believ G.Maxwell Nothing at stake bullshit,
Read this forum , I destroy his lies:
https://bitcointalksearch.org/topic/nothing-at-stake-in-proof-of-stake-1709776

PoW is a dead end, only the rich will mine.

PoS will defeat PoW, don't worry I don't care if you don't profit from it.  Wink

 Cool

FYI:
Your so called secured BTC, has been vulnerable to a 51% attack from the China for over a year.
It has no security!

Also BTC Core Dev refusal to fix the transactions issue , is hurting it.
Egad. 81,000 + Transactions Unconfirmed. Again. Ugh!   :  https://bitcointalksearch.org/topic/egad-81000-transactions-unconfirmed-again-ugh-1799541
Transaction Fees are SPIKING !                : https://bitcointalksearch.org/topic/transaction-fees-are-spiking-1801057
legendary
Activity: 1204
Merit: 1028
And this is one of the many reasons pow sucks. You need a system similar to POS to make it long term. But bitcoin and others will never change because centralized miners in china don't wanna kill the golden goose.

pos suck even more, who buy more coins on the market win, because he can stake more quickly and dump faster, pow is more fair, you can't just go out and buy tons of gpu, as they require space maintenance, electricity ,cooling etc...and last but not last pos is more prone to be double spended, remember mintcoin and its exchange?



Spoken like a PoW miner, Completely Wrong, but hey your a PoW miner, thinking is not your strong suit.  Wink

PoW is only fair to the Rich, that can afford a warehouse full of ASICS.

PoS is the only real game in town for the rest of the world.
PoS that incorporates Coin Age is better protected than PoW from Double spends.
Mintcoin never had any double spends because of Proof of stake to my knowledge, post a link if you have one.
(Are you talking about the security problems that was caused because they were at one time PoW & PoS, which is why they dropped the PoW.)

Mintpal & mintcoin had no affiliations.

 Cool

PoS is flawed. It has been proven to be insecure endless times due the nothing at stake problem which has never been solved.

No PoS coin will ever, ever, ever deliver the security of a network like bitcoin's. You aren't solving anything with PoS. PoS has more problems than PoW and is not as secure.

No one is going to hold value long term in PoS coins, sorry.
legendary
Activity: 1092
Merit: 1000
And this is one of the many reasons pow sucks. You need a system similar to POS to make it long term. But bitcoin and others will never change because centralized miners in china don't wanna kill the golden goose.

pos suck even more, who buy more coins on the market win, because he can stake more quickly and dump faster, pow is more fair, you can't just go out and buy tons of gpu, as they require space maintenance, electricity ,cooling etc...and last but not last pos is more prone to be double spended, remember mintcoin and its exchange?



Spoken like a PoW miner, Completely Wrong, but hey your a PoW miner, thinking is not your strong suit.  Wink

PoW is only fair to the Rich, that can afford a warehouse full of ASICS.

PoS is the only real game in town for the rest of the world.
PoS that incorporates Coin Age is better protected than PoW from Double spends.
Mintcoin never had any double spends because of Proof of stake to my knowledge, post a link if you have one.
(Are you talking about the security problems that was caused because they were at one time PoW & PoS, which is why they dropped the PoW.)

Mintpal & mintcoin had no affiliations.

 Cool
legendary
Activity: 2590
Merit: 1022
Leading Crypto Sports Betting & Casino Platform
And this is one of the many reasons pow sucks. You need a system similar to POS to make it long term. But bitcoin and others will never change because centralized miners in china don't wanna kill the golden goose.

pos suck even more, who buy more coins on the market win, because he can stake more quickly and dump faster, pow is more fair, you can't just go out and buy tons of gpu, as they require space maintenance, electricity ,cooling etc...and last but not last pos is more prone to be double spended, remember mintcoin and its exchange?
hero member
Activity: 1098
Merit: 500
Now they will have to support segwit or suffer from falling prices lol On the flipside Segwit support will make their coins worth more. Smiley


Exactly who has put that into writing, that LTC will be worth more?
Groestlcoin activated segwit, and they are being dumped at the moment.


 Cool





Groestlwho? Never heard of it
legendary
Activity: 1092
Merit: 1000
Now they will have to support segwit or suffer from falling prices lol On the flipside Segwit support will make their coins worth more. Smiley


Exactly who has put that into writing, that LTC will be worth more?
Groestlcoin activated segwit, and they are being dumped at the moment.


 Cool



hero member
Activity: 1098
Merit: 500
Now they will have to support segwit or suffer from falling prices lol On the flipside Segwit support will make their coins worth more. Smiley
legendary
Activity: 1092
Merit: 1000
Kiklo the biggest shill that you've seen thus far.


Dwgscale11 the biggest Crybaby in the forums.  Cheesy



 Cool
sr. member
Activity: 335
Merit: 250
Kiklo the biggest shill that you've seen thus far.

 Cool

full member
Activity: 322
Merit: 151
They're tactical
Yes I didn't look in depth yet into it, so I might have a wrong idea Smiley I know im missing many things about it Smiley

I can understand the part with merging transactions to spare some from being mined, the case you present is case where its useful,but as the tps ratio of LN is still much higher, do you have a rough idea of how many tx can really be saved this way, and it can garantee the tx from a locked tx will be updated to the blockchain before the lock expire ? Like there will never be a flow of merged tx who would take more time than the lock to expire ?


Cause LN as no way to notify the other node or force them to extend the lock if that happen right ?

For me it's still the pb that the volume of merged tx to be synchronized back on the chain must be kept under control, otherwise it's bit like fractional reserve on the tx processing power. With the same potential issue if everyone want to get their tx back on the main chain all at once.


It's why to me it would be somehow cleaner to mark those tx with a special marker to say they are indefinitely locked  on LN, until another tx from LN make them available again.

That would mean probably slight upgrade  of the protocol because such tx would have no point in an "intra chain" view, as it would make the bitcoin just virtually disapear entierely from the chain, but that would be somehow more clear, and would solve the expire issue.

Because the only thing that I see a bit weird is that it still make the btc state in a sort of Split, they are marked as locked on the chain, meaning there is no way anyone on the network can move those coins before the lock expire, whereas they are effectively moved on the LN, without there is anyway to know it can even possibly happen from the chain.

And it seem dangerous to put a non reiterable timeout on the lock when you cant have a very good predictibility of if the state can be fully synchronized back with the blockchain in this time.


But that's mostly the concern id have with it, otherwise it seem a good idea in the principle, clearly something to be tried.

 
hero member
Activity: 770
Merit: 629
Presented like this it remind me of the pb with buffered io when the io is too slow downstream, and adding a buffer will just end up with the same blocked io latter with a bigger buffer. Buffered can just help smoothing the ups & down,  and it would be a bit like putting a time out on the write io, without really checking the all the data actually been sent at the end of the time out ;p knowing that most likely the throughput of LN is much higher than blockchain, it still lead to the question if the tx can be really processed on the chain before the lock expire,  and if the goal is to write them on chain at the end, if it's really going to do this faster.

Idk to me LN doesn't seem too bad in itself, but I just find there is something a bit askew with the mechanism of locking & parallel processing.

I think you've misunderstood the principle of the LN.  The idea of the LN is NOT to have a "buffered" list of transactions that have to go on-chain.  If that were the case, it wouldn't have any purpose.  The danger with the LN is that "by panic" it becomes such a system at a certain point.  But normally, the LN has more or less the following principle.

Consider first a toy LN with 2 nodes, Alice and Bob.  I even think that this embryonic proposal was already in Satoshi's paper.

Alice and bob want to pay one-another several times.  They could simply do that each time on-chain.  But they could also put each of them, say, 100 coins in an escrow-type of wallet (on chain).  Now, suppose that Alice wants to pay 20 coins to Bob.  She could send a *transaction signature* to Bob that would allow Bob to obtain 20 coins from Alice's wallet ; only, the idea is that Bob doesn't broadcast that transaction, but simply keeps the signature on his disk.  If later, Bob wants to pay 20 coins to Alice, he sends HER a transaction signature, which would override the signature HE obtained from Alice IF EVER he broadcasted it.  And if Alice now pays 20 coins to Bob again, she can send HIM a transaction signature that would override Bob's signature that would have overridden Alice's first signature if ever it was broadcasted.

The whole idea is that people send one-another transaction signatures that override previously obtained transaction signatures.

In other words, if at the end of the day, those 20 coins went 50 times to Bob, and 51 times to Alice, Alice and Bob have simply exchanged signatures amongst themselves, and NOTHING HAPPENED ON THE BLOCK CHAIN.   When they both want to quit, they can opt to:
1) send eachother the final signatures to release the coins to one another in the right amounts of the final balance, if they cooperate
2) DUMP THEIR WHOLE LIST OF TRANSACTIONS on the chain, which will then result in 50 transactions from Alice to Bob, and 51 transactions from Bob to Alice, ending up doing the same.

If the LN link "finishes cleanly" with mutual cooperation, then both of them could have exchanged even 1000 signatures, at the end of the day, only one or two transactions make the final balance on chain.  The idea is that there's no way to cheat, if you try to cheat, the partner dumps the whole list of transactions and obtains in any case what was the final balance.  And you're motivated NOT to do that, because you'd have to pay 1000 transaction fees, while now, you can do with only one.

The LN blows this scale up: instead of having 2 nodes exchanging coins back and forth, a node can open such 1-1 links to several partners, making up a mesh.  Suppose that Alice is connected to Bob and Claire, and Bob is connected to Joe and Jack.  If Alice wants to pay Jack, she can send the money to Bob who can send it to Jack (with a safeguard that Bob cannot keep it).  A lot of payments can hence travel across a lot of 1-1 links without a single on-chain transaction.  A node has to go "on chain" if his balance drops to 0 of course.  Each time the partners cooperate, they can just do one or two transactions to get to the final balance ; if not, they dump ALL their transactions on chain and obtain the same result but with much more transaction fees.

Note: I simplified.  The LN is somewhat more involved.  But you get the idea.
hero member
Activity: 532
Merit: 500
And this is one of the many reasons pow sucks. You need a system similar to POS to make it long term. But bitcoin and others will never change because centralized miners in china don't wanna kill the golden goose.
Pages:
Jump to: