Giter Club home page Giter Club logo

segwit2x.github.io's Introduction

SegWit2x Working Group

Charter

The charter of this working group is design, implement, build, test, and deploy the software required to make Bitcoin scale, in accordance with the specific points of the agreement made on May 21, 2017. Participants in the agreement are expected to allocate technical resources to testing and deploying the software within the timeframe below.

Calendar

  • May 23 - Kickoff
  • May 30 - Pre-Alpha
    • More detailed plan sent out to the Agreement Participants for feedback
  • June 16 - Alpha Milestone
    • Alpha software ready
    • New testnet network setup
    • BIP published
  • June 30 - Beta Milestone
    • All comments / issues from Alpha have been addressed
    • Testing complete
  • July 14 - Agreement Participants Install and Test Milestone
  • July 21 - Nodes Running & Signaling begins
  • August 23 - SegWit active on network
  • August status report in English, and in Chinese

Mailing list

A publicly archived, members-only mailing list is available. Info page, Archives

Projects

The initial effort of the working group focuses on producing a segwit2x reference implementation in C++. This is published to the "segwit2x" branch at https://github.com/btc1/bitcoin/tree/segwit2x

Other resources

segwit2x.github.io's People

Contributors

jgarzik avatar jheathco avatar mbelshe avatar philbertw4 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

segwit2x.github.io's Issues

shame on you.

The least u can do is implement replay protection. Ugly people

segwit2x-announce should mention network message length

Hi,

I just did a set of minimum changes to the core codebase according to the specifications on the segwit2x-announce site, to test a "cleanroom implementation" without looking at the btc1 codebase.

But when I ran that client on testnet5, it stalled on block 33923 and disconnected all other clients.

Turns out, 33923 is the first block exceeding MAX_PROTOCOL_MESSAGE_LENGTH in size (which is 4MB by default in core), once I increased it, things were progressing nicely again and I can confirm that core-with-some-numbers-changed indeed follows the chain.

I would suggest adding a note about this to the site, so that it can serve as a minimum specification for building a compatible client.

segwit2x-announce should mention how to safely opt-out of changes

I personally don't care or support 1Mb (or whatever random increase SegWit provides). But people who opt-out should still be advised how to opt-out safely.

There should be clear recommendation on how to use replay protection and/or split your coins. Furthermore recommendations for exchanges should be given how to handle the transition as clear and safe as possible.

~90% of miners upgrading is a strong market signal, but it cannot (without reasonable doubt) be considered the entire market. Therefore recommendations for how to list btc1 and bitcoin core should be given. Even if the market gravitates towards btc1 almost immediately and concisely.

Regardless of the viability of the Core/NO2X chain, exchanges will continue to trade it, and if it is traded it can become viable again. It is irresponsible to not take this possibility into account, and not to advise accordingly.

IMHO advice towards exchanges should be:

  1. Halt withdrawals temporarily,
  2. Either list BTC/Bitcoin as the combined token (Btc1 + Core), or split the token into BTC-2X and BTC-CORE.
  3. Explain how to split coins.

Then the market can decide whether BTC-2X or BTC-CORE gets the BTC/Bitcoin moniker. And then exchanges should list both accordingly.

Advice towards users should be:

  1. Explain how to split coins.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.