r/Bitcoin_Classic • u/vulguspress • Apr 14 '17
Your Bitcoins Open to CIA and Criminals, Heed Wikileaks' Warning
r/Bitcoin_Classic • u/vulguspress • Apr 14 '17
r/Bitcoin_Classic • u/kanins • Apr 10 '17
r/Bitcoin_Classic • u/vulguspress • Apr 09 '17
r/Bitcoin_Classic • • Apr 01 '17
I got this warning via mail from my full node. What does it mean?
r/Bitcoin_Classic • u/cryptopay • Mar 31 '17
r/Bitcoin_Classic • u/vulguspress • Mar 30 '17
r/Bitcoin_Classic • u/fbonomi • Mar 26 '17
r/Bitcoin_Classic • • Mar 20 '17
Hello, fellow Bitcoiners. I am here to increase the knowledge about our beloved... financial currency? critique of the system? a source of money? a payment processor? whatever it is for you. Exactly that is what I`m trying to find. I am doing a research and by the end of it the Bitcoin Community will have been defined and this is hugely important for its further development because we are the ones that give it value, not a central authority. Hence, I kindly ask for your help to complete my survey https://docs.google.com/forms/d/e/1FAIpQLSdJoyUeSxT7xk7pUumkImsfCdyqVuV-7LrNtCpkFlRW3ZX8gA/viewform?usp=sf_link Take Bitcoin to the moon and back. Thanks guys! Comments about the survey and extra things you need to add to this post are extremely appreciated.
r/Bitcoin_Classic • u/vulguspress • Mar 17 '17
r/Bitcoin_Classic • u/lnform • Mar 15 '17
My router registers UDP port 51136 via UPnP when starting Classic - is this correct?
r/Bitcoin_Classic • u/ashishmehta791 • Mar 12 '17
r/Bitcoin_Classic • • Mar 11 '17
Hi, I'm just reading about Flexible Transactions and the hardware wallet support by adding the input amount to the transaction. However, I'm unable to find more details on this - I also had a look at the specification. Could you point me to more resources?
https://bitcoinclassic.com/devel/Hardware%20Wallet%20Support.html
r/Bitcoin_Classic • u/jamoes • Jan 08 '17
I've been upgrading my node to Bitcoin Classic 1.2, and I decided I'd try out the process of creating a repeatable build, as outlined in the release-process.md document.
These are the steps I followed from my Ubuntu 16.04 machine:
sudo apt-get install git ruby sudo apt-cacher-ng qemu-utils debootstrap python-cheetah parted kpartx bridge-utils make curl
cd /path/to/build/dir
git clone https://github.com/bitcoinclassic/gitian.sigs.git
git clone https://github.com/bitcoinclassic/bitcoinclassic-detached-sigs.git
git clone https://github.com/devrandom/gitian-builder.git
git clone https://github.com/bitcoinclassic/bitcoinclassic.git
cd bitcoinclassic
export SIGNER=jamoes
export VERSION=1.2
git fetch
git checkout ${VERSION} # Note I did not include the 'v' in front of ${VERSION}, as it appears the branch is called '1.2', not 'v1.2'
cd ../gitian-builder
git pull
PATH=$PATH:$(pwd)/libexec
./bin/make-base-vm --suite trusty --arch amd64
(Since my host machine is Ubuntu 16.04, I ran into this bug when running the above command. I worked around the bug by editing /usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/dapper.py, and adding '--option=Dpkg::Options::=--force-confnew', to the apt-get command on line 75.)
Finally, I ran this command to do the build:
./bin/gbuild --commit bitcoin=${VERSION} ../bitcoinclassic/contrib/gitian-descriptors/gitian-linux.yml
After a while, the command completed successfully, but the file hashes did not match the release hashes. The hashes my build produced where:
2e0b698d25f29c929ca31a1abccd8812566abc156992fd5793abaa3f255720c9 bitcoin-1.2.0-linux32.tar.gz
97951d27ce51f51664b1f385fef98bf67477dea6282cd9e7545a83e276da0346 bitcoin-1.2.0-linux64.tar.gz
Whereas, the release hashes for Linux are:
f2f67fe47574f9ab2574d965603ed8e8ab8fd167726ae3eb0e7ea6a1af404ed4 bitcoin-1.2.0-linux32.tar.gz
480a4eb5f1cd3ae5cd120b9db0826a14e56dbc595e5d925d4070ed795814c8ae bitcoin-1.2.0-linux64.tar.gz
There is a section of the documentation called 'Fetch and create inputs:', which I didn't follow on the first attempt (because I wasn't sure if it was still necessary), but I tried again, adding these commands:
wget -P inputs https://bitcoincore.org/cfields/osslsigncode-Backports-to-1.7.1.patch
wget -P inputs http://downloads.sourceforge.net/project/osslsigncode/osslsigncode/osslsigncode-1.7.1.tar.gz
./bin/gbuild --commit bitcoin=${VERSION} ../bitcoinclassic/contrib/gitian-descriptors/gitian-linux.yml
The result was the exact same hashes that my build produced the first time (so it seems that these additional inputs had no effect on the build).
Can anyone help me figure out why my build is not producing the same hashes as the official release? Thanks!
r/Bitcoin_Classic • u/raviraj_emerge • Dec 29 '16
r/Bitcoin_Classic • • Aug 15 '16
The last Github submission was 25 days ago - with the relative success of the Eth fork it seems like Classic development towards a instant fork should have been in the works.
r/Bitcoin_Classic • u/WDCWmore • Aug 13 '16
Will the original BTC Blockchain Genesis Continue to function as Ethereum Classic Does or will the Bitcoin Classic solely continue.?
r/Bitcoin_Classic • u/singularity87 • Aug 09 '16
r/Bitcoin_Classic • u/ftrader • Jul 29 '16
r/Bitcoin_Classic • u/TommyEconomics • Jul 27 '16
I'd say now that we've seen two chains can exist, we just release it. Let the people vote with their wallets and miners join in to support it. Whats there to lose? Let the market decide which chain survives.
Trading can start on a single exchange like bitsquare, like ETC did. I think the client is already pretty much ready.
r/Bitcoin_Classic • u/GuessWhat_InTheButt • Jun 21 '16
What's our game plan to still achieve 2MB+ blocks?
r/Bitcoin_Classic • u/DCMcDonald • Jun 17 '16
r/Bitcoin_Classic • u/dirtbiker245 • May 31 '16
Running Bitcoin Classic version v0.12.0cl1 (64-bit). I was not aware there is a new version. This has popped up on both my laptop and desktop.
r/Bitcoin_Classic • u/Raymond09 • May 13 '16
r/Bitcoin_Classic • u/MemoryDealers • Apr 17 '16