In First Activation Meeting, Bitcoin Developers Discuss Taproot Ways
Taproot was integrated with Bitcoin Core in October 2020, leaving a lot to be desired for this much-anticipated protocol upgrade, with a focus on adding the flexibility of Bitcoin smart transactions and greater transaction privacy.
Last week, the Bitcoin development community met via Internet Relay Chat (IRC) to discuss the settings for activating the taproot and the two code bridge (PR) applications of the BIP 8 signaling mechanism.
Bitcoin development organizer Michael Folkson announced via Bitcoin D-Mail: “In an effort to get closer to the finish line, we are hosting a meeting at IRC on Tuesday, February 2nd at 7:00 PM UTC on the activation of the Tapper route. "The main objective is to finalize the modified BIP 8 activation method ..."
Finally, the meeting provided a better understanding of how SegWit could move forward with a change to Bitcoin's most important protocol.
Formulate the proposal.
Bitcoin developer Anthony Towns has developed suggestions and possible scenarios for activating Taproot. At the February 2 meeting, the people with the most support are “BIP 8 (false, 1y)” and “BIP 8 (true, 1y)”. However, no votes were taken, only alternatives to activation were discussed.
But what does that mean? BIP8 is a procedure that allows you to upgrade consensus in the bitcoin network via a soft fork, and more specifically with a soft fork or MASF. Over time, the user has the option of adding a dynamic soft fork (UASF). In the latest SegWit update, in addition to the BIP 9 MASF, a User-Driven Soft Fork (UASF) was also used. However, Taproot does not appear controversial to minors, so it seems unlikely that UASF will be needed this time around.
Coming back to the suggestion, the parameters are "local timeout" and "timeout", where local timeout basically means whether it will be forced to activate or not. Another relevant parameter that was not discussed much was the "starting height".
If the locale timeout is incorrect and the update does not receive enough support, it is rolled back and a new suggestion is explained. (Wikipedia developer Luke Dashjar called Lucan Timeout = a lie that gives miners extra power they never wanted.)
"If you start with (timeout = T, but timeout = false), then there are three possibilities to kill T. Try again without = true, like) before asking everyone to change software (timeout = t, but timeout = true) Upgrade to UASF, "Towns wrote to IRC." It's also possible for everyone to switch to software that explains it (timeout = T-6 months, but timeout = true). In 6 months, the blocks will start rejecting, and if the longest chain is activated, by then the software fork will be activated in the old and new software.
However, djjr lakconn timeout = false:
Are we generally happy with "Lock time Out = Wrong"?
"Yes," replied Rusty Russell, an energy developer. "We have the USASF hammer if we need it, but better not to use it."
Dasher wrote: "Lot = truth doesn't mean we use it, booty = liar means letting miners decide." "BIP8 (incorrect) is a regression."
But Russell objected to what he sees as a developer implementation: “I think it's important to avoid the appearance of a developer mandate on the protocol, and I also like the idea. to escape before activation. There are going to be difficulties in doing this. "That way I like to start with mais = false, and if it's not enabled, I want to review in 6 months. "
Dasher replied: "There is no developer term here; it is more accurate to speak of one year for the same year, wrong, then one year, [in the case of two subsequent appointments]", replied Dasher.
But it did not happen that Russell drowned:
“I don't agree,” he wrote. Miners have the power of coordination because, unlike other groups, we can reliably measure them in a decentralized manner. This indicates the ability to coordinate * no *, yes. But we also have a plan for this, as BIP-8 makes it very unlikely that a UASF will cause a split. It's as good as it gets. "
Dasher wrote in response, "Much = the truth is planning it," which does not prevent minors from doing MASF. "
Other people in the chat suggested setting the Lock Timeout = Bad option, but by default:
CoinSpy developer Chris Belcher wrote: "It's much safer than lot = lie = loot, so it's very useful = fake first, so we know the hash power is 90%, which is already in favor of tippet. " Writes Chris Belcher, developer of Scissors.
If users can easily change a lot = a lot of a lie in one place without needing a new version, I would support dropping too much = wrong, ”wrote Keegan McClelland.
Special Thanks:
@steemitblog.
@steemcurato01.
@steemcurator02
Special Mentions:
@booming01
@booming02
@booming03
@booming04