#softfork

[blogtradingnet]

Soft Fork là gì? Đặc điểm và các sự kiện Soft Fork tiêu biểu

Blogtrading sẽ cung cấp đến các trader thông tin quy trình thực hiện, ưu điểm, hạn chế và các ví dụ thực tế về Soft Fork. Chi tiết tai: https://blogtrading.net/soft-fork-la-gi/ Hastag: #Blogtrading #Blogtradingnet #sangiaodich #sangiaodichtiendientu #SoftFork

[ailtrahq]

Many people these days are finally starting to realize the shortcomings and limitations of off-chain channels limited to two participants, i.e. the Lightning Network, and the necessity to start exploring designs for channels with more than two participants for this direction in scaling to work successfully in the long term. That necessitates accepting new trade-offs, namely that the price for solving some of Lightning's existing problems by packing more than two people into a shared control arrangement for a UTXO is the creation of a whole new class of problems.The biggest problem introduced in making the move from two parties to more than two parties is the interactivity requirement. If you have 10 people in a single channel sharing control of one UTXO, you need all 10 parties online at the same time in order to update the state of that base channel. This presents a much worse coordination problem than the current implementation of Lightning channels where only two people need to be online to make use of the channel. Currently the best thinking regarding this issue is simply to introduce trust into the situation through what is essentially a federation. Lightning (and future multiparty channel systems) work as a self custodial system because the multisig holding funds on chain is n-of-n, requiring 100% of the participants to sign off to change the state of off-chain funds. If you yourself as a member to such an agreement refuse to sign a new update, then it is impossible for your funds to be reassigned in any way. Ignoring the requirement to stay online and watch the blockchain to deal with old states, this security model is equivalent to sole custody on the mainchain. Control of funds cannot be changed from the current state of things without your signature. Reducing the key threshold from n-of-n to m-of-n completely undermines that security equivalence to sole custody on-chain. It is effectively custodial, in that your key is no longer absolutely and non-negotiably required in order to move control of your funds. ZmnSCPxj (not Zman!) has proposed an interesting solution to the interactivity problem. OP_CHECKSEPARATESIGThis proposal would require two softforks, SIGHASH_ANYPREVOUT and OP_CHECKSEPARATESIG. The scope of OP_CHECKSEPARATESIG is so small and tiny of a change I would be amazed if there is any serious contention with it, and APO has a relatively large consensus in the ecosystem as a desirable change. OP_CHECKSIG and OP_CHECKSIGVERIFY are the two main ways signatures are verified in Bitcoin script currently. There are two parts of a signature, the S value and the r value. OP_CHECKSIG(VERIFY) takes the r and S of the signature as one whole argument, and the public key to verify it against as another, for a total of two arguments, and then checks whether the signature is valid or not. OP_CHECKSEPARATESIG takes the public key, the r value, and the S value all as separate arguments (for a total of three), and verifies the signature. Yes, that is literally the entirety of the proposal. A softfork even simpler and less complicated than CHECKTEMPLATEVERIFY (CTV). Why is this needed? Well, you'll see here right now. State Updates Without Everyone Online A multiparty channel. This is what the starting state of a very basic multiparty channel would look like. A pre-signed transaction needing Alice, Bob, and Charlie to sign for a UTXO they share control over with an output for each member. If Alice wants to pay Bob while Charlie is offline, the only option she has is to create a pre-signed transaction from her output in the channel state splitting those funds between herself and the payment to Bob like this: Alice paying Bob. The problem with this arrangement is that Alice can simply sign a conflicting transaction taking back the payment to Bob at any time and use it before Charlie comes online and everyone updates the channel, and because only her key is needed to do that Bob can do nothing to stop her.

We need to have some kind of arbitrator that ensures Alice cannot double-spend Bob when making payments in this way because Charlie is unresponsive. You could just add a condition requiring that a Actuary (M) also be a keyholder for everyone's outputs, meaning they would have to sign to approve any transactions spending Alice, Bob, or Charlie's outputs from the channel state. The problem with that is, now Bob has to trust the Actuary instead of Alice. If the Actuary cooperates with Alice, Bob can still be double spent. This is where OP_CHECKSEPARATESIG comes in. Here's how: the r value in a signature is derived from the nonce used to sign. One of the key risks in nonce handling is the risk of key leakage, reusing the same nonce twice for different transactions will leak enough information for someone with both of those transactions to be able to regenerate the private key used. This can be used to take the Actuary role from above and remove trust in them. Whatever key the Actuary uses for this role, they can load with a bond that can be confiscated. From this point we add their key to everyone's outputs like described above, except specifying in each script exactly what r value has to be used in the signature from M ahead of time. We also have a CSV timelocked path needing only the owner's key; this way users can always spend their funds however they want if the channel is closed on chain after a timelock. Now when Alice goes to pay Bob while Charlie is offline using a pre-signed transaction spending her output in the channel, she goes to the Actuary to sign off on it. After the signatures are completed and Bob has a copy of the transaction, he has an immensely stronger guarantee that these funds will not be double spent. If the Actuary collaborates with Alice to double-spend Bob, his key is leaked and the funds he put in a bond can be confiscated. If the channel is closed out on-chain in this state Bob will be able to confirm the transaction co-signed by the Actuary before Alice can double-spend him, because Alice has to wait for a timelock to expire before she can double-spend, Bob doesn't because the Alice and Actuary spending path has no timelock. This can be added as a clause to every level of the multiparty channel if you nest smaller channels on top as well.This provides a security model for Alice and Bob to update the multiparty channel without Charlie being online, which while not being strictly speaking trustless, is about as close as you can get without meeting that bar. Bob can have a strong guarantee that he won't be double spent, which is virtually 100% as long as the bond value the Actuary uses is greater than the payment value, and Alice can make this payment with a guarantee good enough for Bob even though Charlie is offline. This can be used in that likely very frequent situation where not everyone is available to continue processing updates, and cleanly cut-through whenever everyone is online to update the base level of the channel and remove the extra transactions using this scheme. OP_CHECKSEPARATESIG and the Actuary role it enables in multiparty channels solve a huge problem in actually making the concept of more than two people sharing a channel workable at scale. I'm sure there are plenty of other situations besides multiparty channels where enforcing with a bond that some party only ever signs one version of something. This should be something very seriously considered by Bitcoiners, it provides a big solution to a known problem with no complexity by just slightly changing a tiny aspect of how signatures are verified.  Source

[christophbergmann]

BIP-119: Die Entzauberung der Softfork

BIP-119: Die Entzauberung der Softfork Die Bitcoin-Szene debattiert gerade erhitzt über BIP-119. In der Diskussion sind Politik und Technologie eng verflochten. Wir erklären, worum es geht – und warum es so wichtig ist. #btc #bip119 #ctv

Die Bitcoin-Szene debattiert gerade erhitzt über BIP-119, das eine neue Funktion in das Bitcoin-Protokoll einführen soll. In der Diskussion sind Politik und Technologie eng verflochten. Wir erklären, worum es geht – und warum es so wichtig ist. (more…)

[the-bitcoin-wardrobe]

💯💯 Taproot and Schnorr 🥳 Bitcoin just implemented its latest soft fork. The soft fork was scheduled for block height 709632. This soft fork will include the implementation of two proposals, the Taproot update and Schnorr signature update. 🤔 What is a Bitcoin Taproot update you might ask? Taproot is a name for the next Bitcoin protocol update (soft fork). This will be one of the and most important and anticipated updates since the SegWit upgrade from 2017. The upgrade will add better scripting capabilities and privacy by implementing MAST (Merkelized Abstract Syntax Tree) which will replace currently used P2SH (pay to script hash). P2SH and MAST are ways of locking the transactions with conditions until the conditions are met. P2SH allows other users to see the conditions and allows everyone to see all the different ways they could have met the conditions. While MAST hides all the conditions except the ones that are met when the transactions are processed. One other aspect of this upgrade is that it will also improve Lightning Network privacy by making Lightning Network channels look like regular bitcoin transactions.   🤔 And what is Schnorr update you say? Schnorr update brings multi-sig transactions natively to the Bitcoins signature algorithm. This is important since Bitcoin requires signatures to confirm the transaction. Currently, Bitcoin uses ECDSA, but this signature algorithm does not natively support muti-sig transactions. Schnorr's signature scheme can aggregate multiple signatures and output them as a single signature. This increases privacy and lowers transaction size and fees. Learn everything you need to know about Bitcoin and Crypto in our educational section of our store. 😎 Visit https://btcwardrobe.com #bitcoin #btcwardrobe #bitcoinnews #cryptomarket #taproot #schnorr #bitcoinpricedaily #cryptonews #softfork #fork #bitcoinfork #buybitcoin #blockchaintechnology #bitcoininfo #cryptoclothing #cryptoinfo #cryptomeme #dailycrypto #dailymeme https://www.instagram.com/p/CWQi3wBsQie/?utm_medium=tumblr

[asktorahulsingh]

DAY-61/62 #Bitcoin #SoftFork days away, #Taproot upgrade are closes.. The Taproot upgrade was set for deployment after achieving a 90% consensus among the #Bitcoin Mining nodes. Taproot is Bitcoin’s first major upgrade since August 2017, which saw the introduction of Segregated Witness (#SegWit) and resulted in the launch of Lightning Network. While the previous fork primarily sought to fix transaction malleability and improve Bitcoin’s network scalability, the Taproot upgrade aims to revamp transaction efficiency, privacy and support smart contracts initiatives. Follow here... https://t.co/lrcRLh7TRg Every Indian in the #CryptoSpace Needed #BitcoinAsLegalTender (at India इंडिया भारत) https://www.instagram.com/p/CV_Fv5tBAqo/?utm_medium=tumblr

[gruntcrypto]

What the fork!!! #gruntcrypto #hardfork #softfork #blockchainfork #forkintheroad (at Cape May County, New Jersey) https://www.instagram.com/p/CPS89AOAUma/?utm_medium=tumblr

[digital-hoarder]

The Satoshi Sculpture Garden

[blockcastcc]

Is Bitcoin really on Ethereum ? Will either proponents softfork BTC to ETH?

New Post has been published on https://blockcast.cc/news/is-bitcoin-really-on-ethereum-will-either-proponents-softfork-btc-to-eth/

Is Bitcoin really on Ethereum ? Will either proponents softfork BTC to ETH?

[cryptoknowmics]

Today, the topic which we are going to focus on is not blockchain, but block explorer. Now, what do you understand by this term? Or have you come across this term ever before? If not, then learn it today. read more

[theblockchaincafe]

Types Of Forks In Blockchain Network: Hard Fork And Soft Fork

A fork is defined as a change in a blockchain network. If miners reach a unanimous consensus in the blockchain network, then the result of this mining will be a single blockchain with verified data. Blockchain technology is defined as a single chain of blocks. If the miners don't reach the unanimous consensus, then forks will be created. It means that the single chain of blocks is split into either two valid chains or more valid chains. Mentioned below are the details of Soft Fork, Hard Fork, and Temporary Fork:

Soft Fork

Definition: If the blockchain protocol is changed into a backward-compatible way, then the occurrence of a soft fork will take place. Description: Nodes use the software. A change can occur in the software. New blocks are mined in accordance with new rules in the blockchain protocol. The old version of the software considers this mining as valid. Therefore, the blockchain protocol is changed into a backward-compatible way.

Hard Fork

Definition: If the blockchain protocol is changed into a non-backward-compatible way, then the occurrence of a hard fork will take place. Description: Nodes use the software. A change can occur in the software. New blocks are mined in accordance with new rules in the blockchain protocol. The old version of the software considers this mining as invalid. Therefore, the blockchain protocol is changed into a non-backward-compatible way. A new cryptocurrency will be derived in the situation when the occurrence of a hard fork takes place. It will be a valid original currency. Examples: Original: Ethereum (ETH) New: Ethereum Classic (ETC) Original: Bitcoin (BTC) New: Bitcoin Cash (BCH) The new cryptocurrency will be distributed in a new chain. If a node upgrades the software, then the node will be able to join the new chain. If the node doesn't upgrade the software, then the node will continue to work in an original chain.

Temporary Fork

Definition: If two miners mine a new block simultaneously, then the occurrence of a temporary fork will take place. Description: Many miners can mine a new block simultaneously in a blockchain network. The full nodes in the blockchain network can't agree on the new block. While the new block can be accepted by some nodes in the network. A new chain of blocks will be formed on that point. Other available alternatives of blocks can be agreed upon by other nodes. If a long period of time is taken to propagate the information to the full nodes, then conflicted opinions related to the chronological order of events will exist. Either two blocks or more blocks will have the same block height. If a chain is lost, then a temporary fork will be resolved. This happens since a majority of the network turns towards another chain for adding new blocks

Reasons Behind Forks

Add new functionality, Fix security issues, Reverse transactions are the three reasons behind the occurrence of a fork in a blockchain network. Add new functionality: The code is often updated in a public blockchain. Developments or improvements are carried out by worldwide people. New versions will be released. Fix security issues: The blockchain is a new technology being researched to fix the issues regarding security. Updates will be released. Reverse transactions: If all the transactions of a specific period are breached, then these transactions will be void by them. Read the full article

[blogtradingnet]

Soft Fork là gì? Đặc điểm và các sự kiện Soft Fork tiêu biểu

Blogtrading sẽ cung cấp đến các trader thông tin quy trình thực hiện, ưu điểm, hạn chế và các ví dụ thực tế về Soft Fork. Chi tiết tai: https://blogtrading.net/soft-fork-la-gi/ Hastag: #Blogtrading #Blogtradingnet #sangiaodich #sangiaodichtiendientu #SoftFork

[photono-van-lichten]

Run a full node! Support SegWit!

[christophbergmann]

Schwächt das Taproot-Upgrade die Resistenz von Bitcoin gegen Quantencomputer?

Langsam wird die Aktivierung des seit langem erwarteten Taproot-Upgrades für Bitcoin greiftbar. Doch es mehren sich auch kritische Stimmen. Ein Entwickler warnt, dass Taproot die Resistenz von Bitcoin gegen Quantencomputer schwächt. Continue reading

[the-bitcoin-wardrobe]

🌱 Taproot and Schnorr 🥳   In less than 40 days Bitcoin will implement its latest soft fork. The soft fork is scheduled for block height 709632 which should happen around the 17th of November 2021. This soft fork will include the implementation of two proposals, the Taproot update and Schnorr signature update. 🤔 What is a Bitcoin Taproot update you might ask? Taproot is a name for the next Bitcoin protocol update (soft fork). This will be one of the and most important and anticipated updates since the SegWit upgrade from 2017. The upgrade will add better scripting capabilities and privacy by implementing MAST (Merkelized Abstract Syntax Tree) which will replace currently used P2SH (pay to script hash). P2SH and MAST are ways of locking the transactions with conditions until the conditions are met. P2SH allows other users to see the conditions and allows everyone to see all the different ways they could have met the conditions. While MAST hides all the conditions except the ones that are met when the transactions are processed. One other aspect of this upgrade is that it will also improve Lightning Network privacy by making Lightning Network channels look like regular bitcoin transactions.   🤔 And what is Schnorr update you say? Schnorr update brings multi-sig transactions natively to the Bitcoins signature algorithm. This is important since Bitcoin requires signatures to confirm the transaction. Currently, Bitcoin uses ECDSA, but this signature algorithm does not natively support muti-sig transactions. Schnorr's signature scheme can aggregate multiple signatures and output them as a single signature. This increases privacy and lowers transaction size and fees. Learn everything you need to know about Bitcoin and Crypto in our educational section of our store. 😎 Visit https://btcwardrobe.com #bitcoin #btcwardrobe #bitcoinnews #cryptomarket #taproot #schnorr #bitcoinpricedaily #cryptonews #softfork #fork #bitcoinfork #buybitcoin #blockchaintechnology #bitcoininfo #cryptoclothing #cryptoinfo #cryptomeme #dailycrypto #dailymeme https://www.instagram.com/p/CUwgSPfsGgZ/?utm_medium=tumblr

[asktorahulsingh]

DAY-33 #Taproot is a #SoftFork that improves #Bitcoin’s scripts to increase privacy & could make a Txn. in a #Lightning Network channel, a P2P transaction, or a sophisticated #SmartContract become indistinguishable. Every Indian in the #CryptoSpace Needed #BitcoinAsLegalTender Follow here... https://t.co/vADjI1dygv (at India इंडिया भारत) https://www.instagram.com/p/CU22kk7PCt4/?utm_medium=tumblr