################################################################################ Section 0 - Premable ################################################################################ *** USE THE INFORMATION IN THIS DOCUMENT AT YOUR OWN RISK *** This is meant to be a guide for using the bitcoin_fork_claimer tool to move forked coins. It finds and generates parameters for the tool, however it is not guaranteed to be bug-free. You accept full responsiblity for running this code and the bitcoin_fork_claimer tool. *** USE THE INFORMATION IN THIS DOCUMENT AT YOUR OWN RISK *** This generated document also provides pointers to which exchanges allow deposits of these coins and some hint as to their KYC requirements. This is not an endorsement of these exchanges and this information is not guaranteed to be accurate. Also, some of the non-KYC exchanges may decide to require KYC at their convenience. *** USE THE INFORMATION IN THIS DOCUMENT AT YOUR OWN RISK *** We are not the authors of the bitcoin_fork_claimer tool, and are also not responsible for any bugs or malicious effect. Please make sure you understand the code you are running and accept 100% of the risk of anything that happens as a result. *** USE THE INFORMATION IN THIS DOCUMENT AT YOUR OWN RISK *** ################################################################################ Section 1 - Table of Contents ################################################################################ Table of Contents: Section 0 - Premable Section 1 - Table of Contents Section 2 - Warning to Move BTC Section 3 - Obtaining the bitcoin_fork_claimer Tool on TAILS Section 4 - Preparing Proxychains Tool on TAILS Section 5 - Private Key Search-and-replace Instructions Section 6 - BitCore (BTX) Value Summary Section 7 - Support Good Cypherpunk Tools Section 8 - Claming Instructions for BitCore (BTX) ################################################################################ Section 2 - Warning to Move BTC ################################################################################ Bitcoin (BTC) detected on provided addresses: These addresses do not contain BTC. Excellent. ################################################################################ Section 3 - Obtaining the bitcoin_fork_claimer Tool on TAILS ################################################################################ The bitcoin_fork_claimer tool must be obtained off of GitHub. The lines to invoke the claimer.py script are assuming that bitcoin_fork_claimer has been cloned to the same directory as the script which generated this document. Ideally, this is an encrypted USB drive mounted under /media/amnesia/ on TAILS. To 'cd' to that directory: amnesia@amnesia:~$ cd /media/amnesia/mydrive/ To clone the tool off of GitHub: amnesia@amnesia:/media/amnesia/mydrive/$ git clone https://github.com/ymgve/bitcoin_fork_claimer Once the cloning is complete, you can 'cd' into this directory and use the 'git log' command to see what is the top git SHA1 commit id in origin/master: amnesia@amnesia:/media/amnesia/mydrive/$ cd bitcoin_fork_claimer amnesia@amnesia:/media/amnesia/mydrive/bitcoin_fork_claimer$ git log To ensure this code is safe to use, you should check the top SHA1 commit id against the GitHub web interface to make sure 1) you know the exact version you are running, 2) you don't see any evidence of tampering with the software and 3) there are no outstanding issues filed that might affect you. ################################################################################ Section 4 - Preparing Proxychains Tool on TAILS ################################################################################ In order to move coins with the bitcoin_fork_claimer tool on TAILS, you must us the localhost proxy provided by the OS in order to connect to the nodes. This is a required step to make the necessary socket connection for protocol communication via Tor. The easiest way to do this is via the Proxychains tool which wraps the bitcoin_fork_claimer Python process to route traffic through the proxy in a way that is transparent to the script. However, to use this tool you must manually install it on TAILS every time the system is booted. When initially booting up TAILS, in the initial menu that is displayed before you get to the desktop, you must go into the Advanced settings and set an administrator password for the session. To install, from the desktop once you are connected to the network and Tor, you must open a Terminal application session and run the following two commands: amnesia@amnesia:~$ sudo apt-get update amnesia@amnesia:~$ sudo apt-get install proxychains dnsutils This might take a couple minutes to finish. Select 'Y' when prompted. Once installed, using the terminal command 'proxychains' in front of a bitcoin_fork_claimer script invocation will perform the necessary proxy step. This is also covered in detail with screenshots in the article: https://forkdrop.io/installing-and-using-proxychains-utility-on-tails-live-boot ################################################################################ Section 5 - Private Key Search-and-replace Instructions ################################################################################ Command invocation parameters for the bitcoin_fork_claimer tool have been prepared for you in this document. However, strings have been for where your private keys must be provided in order to actually run the script. Once you have retrieved your private keys, it is suggested that you use a text editor's search-and-replace (a.k.a. find-and-replace) functionality to conveniently insert your private keys. To keep your private keys secure, it is recommended that they only be accessed on a secure system and that this document be stored on only an encrypted drive. We have several guides provied to help with these tasks available at forkdrop.io: https://forkdrop.io/secure-live-boot-tails-for-bitcoin-keys https://forkdrop.io/sd-card-for-saving-files-on-tails-live-boot https://forkdrop.io/usb-drive-for-saving-files-on-tails-live-boot https://forkdrop.io/running-bip-39-tool-on-secure-offline-tails-system https://forkdrop.io/running-bitaddress-tool-on-secure-offline-tails-system Once you have obtained your private keys, the following strings in this document are available be replaced throughout with the private key corresponding to the public bitcoin addresses denoted: 1MrpoVBweTnwPTase83S13LSZZ2Ga4Amk7-private-key ################################################################################ Section 6 - BitCore (BTX) Value Summary ################################################################################ According to blockchain.info and what we know about this coin, the credited value of this type on these addresses is below. However, if value has ben subsequently sent, the direct query will find it in addition to what is listed here: 1MrpoVBweTnwPTase83S13LSZZ2Ga4Amk7 has 0.13600000 BTX unclaimed 0.13600000 total credited and not marked as claimed ################################################################################ Section 7 - Support Good Cypherpunk Tools ################################################################################ Lots of hard work went into providing this free stack of software. Support forkdrop.io and the forkdrop_suite tools: BitCore (BTX): 1NrjCLA4oSVRrY6kbCtYZXyvBHDXw4kCHP also: Bitcoin (BTC): 3QLFLTTuV82LzJUMzh2RoDW2t7FeHLYYad Litecoin (LTC): LQQvLzqMrqCCk7jGv8WTcAHNTVcM9KGDrU (and many other fork coins accepted!) ~ Support Ymgve's bitcoin_fork_claimer tool via his donation address in his README.md or seen at: https://github.com/ymgve/bitcoin_fork_claimer Support the TAILS project at: https://tails.boum.org/donate/ Support the Tor project at: https://www.torproject.org/donate/donate-options.html.en Support Tor exit node providers by following suggestions at: https://blog.torproject.org/support-tor-network-donate-exit-node-providers ################################################################################ Section 8 - Claming Instructions for BitCore (BTX) ################################################################################ 1 total balances for BitCore (BTX) 1 unclaimed balances for BitCore (BTX) 0 unclaimed balances with segwit/p2sh/b32 concerns for BitCore (BTX) non-KYC exchanges supporting deposits and trade of BTX: https://forkdrop.io/exrates https://forkdrop.io/crex24 https://forkdrop.io/octaex https://forkdrop.io/cryptopia https://forkdrop.io/hitbtc https://forkdrop.io/cryptobridge https://forkdrop.io/easyrabbit https://forkdrop.io/bitibu https://forkdrop.io/qbtc https://forkdrop.io/exvo KYC exchanges supporting deposits and trade of BTX: https://forkdrop.io/bitexlive https://forkdrop.io/bit-z You may search-and-replace the string: bitcore-destination-address with the address you wish to be the destination for your BTX. bitcoin_fork_claimer script invocations to move this value: -------------------------------------------------------------------------------- id: bitcore-1MrpoVBweTnwPTa-13600000-b3cf4e526c9c9fa proxychains python2.7 bitcoin_fork_claimer/claimer.py BTX b3cf4e526c9c9fa1a1c0070244f6512e29c7f020358d10454775a7d3f88c659c 1MrpoVBweTnwPTase83S13LSZZ2Ga4Amk7-private-key 1MrpoVBweTnwPTase83S13LSZZ2Ga4Amk7 bitcore-destination-address --txindex 2249 --satoshis 13600000 Once this value has been moved, this value can be marked as claimed for subsequent generations of this report by running: $ /home/amnesia/forkdrop_suite/mark-claimed.py /tmp/save_file bitcore-1MrpoVBweTnwPTa-13600000-b3cf4e526c9c9fa -------------------------------------------------------------------------------- ================================================================================