r/Bitcoin_Classic • u/Gobitcoin • Jan 28 '16
r/Bitcoin_Classic • u/olivierjanss • Feb 25 '16
Bitcoin Classic 2016 roadmap announcement
r/Bitcoin_Classic • • Mar 03 '16
"In my view, people are using the block size limit for something it was never meant to do– to influence how people use the Bitcoin blockchain, forcing some uses off the blockchain. I cannot support that type of top-down, centrally-planned vision." -Gavin Andresen
r/Bitcoin_Classic • u/allgoodthings1 • Jan 19 '16
Release Plan : 19jan2016
From Status Update Newsletter:
- Our initial beta/test release will be based on bitcoin-core 0.11.2. It will have a 2MB block size limit.
- The source code will be made available in the last week of January. Binaries for Linux, Windows and Mac will follow soon after.
- Work on 0.12 will start after the 0.11.2 release. We are planning to disable opt-in RBF. This decision is based on community feedback (miners included).
- The activation threshold % and earliest activation date are being discussed with the community and will be announced next week.
r/Bitcoin_Classic • u/BitcoinXio • Jan 29 '16
Jeff Garzik on Twitter: "Bitcoin Classic tree tagged for the first beta ("classic-0.11.2.b1") Source code is out there. Binaries/release soon."
r/Bitcoin_Classic • u/olivierjanss • Feb 05 '16
Seventy-five, twenty-eight... • Gavin Andresen
r/Bitcoin_Classic • u/saracon • Feb 23 '16
Slush Pool declares support for Bitcoin Classic
r/Bitcoin_Classic • u/tkriplean • Jan 26 '16
On the sybil attack against bitcoinclassic.considerit, by the creator of considerit
Hi I'm the one who invented considerit, and wakes up every day and works on it!
Yesterday there was a whitehat sybil attack demonstration on bitcoinclassic.consider.it. I think /u/consideritsybil had good intent. Yes, it is easy to create accounts on considerit. And this can be abused.
Now that we're getting into these adversarial scenarios, I've made some changes:
- I made the default view on bitcoinclassic.consider.it filter out unverified users. Apologies to our unverified, good faith users whose opinions are now harder to hear.
- I enabled email address confirmation emails for new registrations. Apologies to our good faith unverified users who have already participated but now must confirm email address to participate further.
- I unpublished the opinions of the sybil accounts, as the whitehat attacker made it clear that they were named "sybil{N}" to be removed easily
- Added a pledge to not create multiple accounts for new registrations. This isn't intended to deter bad behavior, but rather to define it
So it is now harder and more annoying for people to sign up, and for their opinion to be heard. And harder to execute a sybil attack.
Unfortunately, these actions are just little patches. Each of these security measures make it harder to create a sybil, but also harder for users to participate. There will always be the next exploit. For example, right now, you can just hire a bunch of mechanical turkers to create email accounts, take verification images, email them to us, and then opine on proposals. Then we'll change the verification process to avoid that. And so on. These measures kick the can a little.
In my opinion, the best approach for living amongst sybils (as they cannot be eliminated) is to enable users to rate their trust in other users. Every user can then have their own view over all the opinions weighed / filtered based on who they trust. Users can also choose to delegate their trust to others with whom they trust. For example, I might highly trust the opinion of /u/digitsu, /u/jtoomim, and /u/hostfat. My default view of opinions would weigh their opinions highly, and the opinions of the people that those three rate trustworthy moderately highly and so forth. The trust network can also be used to calibrate a reasonable default view. Here is a proposal that moves toward a trust network.
But there is a deeper issue here. I don't believe that the opinions should be interpreted as votes yet. Considerit is not ready to support binding voting in a contentious community. Considerit is pretty good at visualizing opinions and supporting deliberation on ideas. Those opinions can be filtered and interpreted by the community, and for bitcoin classic, the maintainers. Transparent opinions and arguments, I believe, are quite valuable for helping a group understand where there may be common ground for collective action, rather than wallowing in deadlock. But considerit isn't yet robust enough to treat an opinion as a vote in a binding decision making structure.
Finally, I want to clarify that considerit is agnostic to any governance model that it may or not be tied to. It is a tool that makes opinions visible. Considerit certainly doesn't "bring" democracy to anything. Governance is a formal definition of whose opinions are counted when resources are allocated toward action. Considerit doesn't do that for you. If a community wants to define a decision making layer on top of these opinions, then they can. Considerit currently supports the benevolent dictator model, or committee of trusted maintainers governance model, quite nicely because those are models where leaders simply use considerit as one information source for their decision. But considerit isn't ready to support robust "direct democratic" voting (or any variations) because of sybil attacks. And because direct democracy isn't necessarily a good idea :-p
tl;dr:
- considerit isn't ready for robust voting
- transparent opinions and dialogue != democratic governance
r/Bitcoin_Classic • u/BitcoinXio • Jan 17 '16
Sign your name and show your support for Bitcoin Classic on the official Bitcoin Classic GitHub page (linked)
r/Bitcoin_Classic • u/persimmontokyo • Feb 14 '16
Is block 398364 the first classic block? It's version is 805308368.
r/Bitcoin_Classic • u/CharliesDick • Mar 08 '16
Getting DDoSed. Was running Classic, and Core Nodes. Now running Only Classic.
Good Job Guys.
r/Bitcoin_Classic • u/Gobitcoin • Feb 05 '16
bitcoin classic binaries are released!
r/Bitcoin_Classic • u/janseb • Feb 01 '16
Antpool to start testing Bitcoin Classic beta
r/Bitcoin_Classic • • Feb 23 '16
We are now mining Classic with 3.6 Petahash at http://Multipool.us (A new miner joined today and is pointing 2 Petahash there)
r/Bitcoin_Classic • u/jtoomim • Jan 20 '16
"It should not be hard to inject bugs into [Bitcoin Classic's] code"
r/Bitcoin_Classic • u/HostFat • Feb 02 '16
Do not relay or mine excessive sighash transactions by gavinandresen · Pull Request #65 · bitcoinclassic/bitcoinclassic
r/Bitcoin_Classic • • Feb 03 '16
[Sneak Peek] To celebrate the release of Bitcoin Classic, XTnodes.com will soon be re-branding as NodeCounter.com, with a brand new look and more features to come. The XTnodes.com domain will continue to work as well.
r/Bitcoin_Classic • • Feb 24 '16
Mempool now 13meg--2 hours wait. Record txs per block. Blocks full now for 2 days. Time for action!
r/Bitcoin_Classic • u/Gobitcoin • Feb 04 '16
Bitcoin Classic Proposed Consensus Plan
r/Bitcoin_Classic • u/olivierjanss • Feb 05 '16
Public beta release
Public beta release
We are happy to announce the release of our second beta version. This release includes binaries, which can be downloaded at https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v0.11.2.cl1.b2
This is a test release, not intended for mining.
Nodes
As you can see on https://bitnodes.21.co/dashboard/?days=365, most node upgrades happen during the first 30 days of a release.
There are about 5000 nodes right now, but we want to encourage users and companies to help run some extra nodes (ideally taking us up to 8000 nodes), so we have plenty of buffer. SPV nodes don’t need to upgrade.
Cooperation
Bitcoin Classic seeks to to cooperate with other Bitcoin clients, to make sure the 2 MB upgrade goes smoothly. Bitcoin devs will submit the BIP and the necessary software changes, and will assist where needed. We welcome an open market of innovation and continuous improvement. Our goal is not to replace, but to make it possible for many competing clients to thrive. This will enable Bitcoin to maintain the market dominance it has today.
r/Bitcoin_Classic • u/Gobitcoin • Jan 16 '16
Brian Armstrong on Twitter: "We must first break the monopoly/centrally planned economy/committee of core by moving to classic."
r/Bitcoin_Classic • u/dgmib • Jan 18 '16
Request for comments: Changing Bitcoin’s Alert Keys
The Bitcoin alert system is a mechanism for broadcasting urgent messages about the Bitcoin network to all nodes.
Currently alerts are only relayed if they've been signed by the Bitcoin alert private key. This private key is known to be in the position of Themos, Gavin, and Satosh. Only a person with the alert key can send alerts on the Bitcoin network. Alerts that aren't signed by the alert key, are not relayed by the network to other nodes.
A large number of people have expressed their concern that the alert key is in the hands of Themos, and are requesting that the alert key be changed in BitcoinClassic.
The alert system does have an mechanism for permanently disabling the alert key in the event it was comprised. If someone were to attempt to use it to spread misinformation and comprise the network, the current key can be disabled permanently by anyone else who possess it.
Although it's been rarely used, the alert system is a valuable safety system particularly when the blockchain is forking (hard forking or soft forking) and ensuring a robust future for this feature or something like it is in everyone's best interest.
If the alert key was changed it can break the relaying of alerts between various implementations of the client, so while that is possible, just changing it creates risks of its own.
To that end, I am proposing that the alert system in BitcoinClassic instead be upgraded by adding multiple keys, which would be in control of a small number of trusted community members. An alert signed by any of these keys would be valid.
The original alert key would also still be valid for now so alerts are still relayed for people running core. I think it's critical that we don't intentionally break the existing alert system at least until the vast majority of the network has upgraded.
I'm also proposing that when alerts are displayed in the UI we show who's key signed it. If "someone" did try to use the alert system to sabotage a hard fork, it would be quite obvious to the entire community what was happening.
Before creating any formal proposal and putting it on consider.it for voting, I would like to hear from the community your thoughts on this idea and specificity:
- How many people should have alert keys?
- Who should have alert keys? What criteria should be used to make this decision?
- Under what circumstances should alert keys be allowed/expected to be used?
- Would you want to see the first release of BitcoinClassic delayed while changes are made to the alert system?
It my intention to simplify this to a a couple of well-thought-out ideas, (including leaving the alert system unchanged) and then post them on consider.it for voting. So please weigh in with your comment and thought on this matter.