Friday, 21 December 2018

Using your existing copy of the Exclusive Coin blockchain to sync the new clients.

This document is to assist users in modifying their current copy of the blockchain to enable a fast re-sync with the new client.

The new client has new protocol rules, so it will only accept blocks that conform with the new settings. This means it will only scan the bootstrap up to the fork block and then stop.

It is important to remember that you are modifying files in the data directory that holds your wallet keys so care is needed when deleting and renaming files.

The basic steps involved are,
1.going to you data directory
2.backing up files for safe keeping
3.deleting one folder
4.renaming one file


1. The default location for your Exclusive Coin data directory can be found on windows in 

or on macOS 
~/Library/Application Support

You many find any other crypto currency wallets you might have in this folder.

If you are 100% paranoid and concerned, you can back up the entire data directory before changing files.

2. Once you have entered your ExclusiveCoin folder you will see an assortment of files.

Back up the file wallet.dat somewhere safe. if you do something terrible during the next few steps you can restore your wallet from this backup.

3. Delete the folder named txleveldb, also the file mncache.dat.

4. Rename blk0001.dat to bootstrap.dat

Now you may start the new wallet, it will scan the bootstrap file and sync up to the fork block, then it will connect to the network as normally.


deleting the file mncache.dat is not necessary for bootstrap. but due to other updates in EXCL all users are recommended to do so.


Thursday, 3 May 2018

CMake 3.10.1 bootstrap fails on Mac OS X 10.8.5 with "Cannot find a C++ compiler supporting C++11 on this system."

my error was exactly the same as this

edit cmake.rb
(somewhere in usr/local/Homebrew/Library/taps/homebrew/homebrew-core/Formula)

ENV["CXXFLAGS"] = "-std=c++11 -stdlib=libc+

before the execution of bootstrap.

Sunday, 29 April 2018

The following packages have unmet dependencies: nodejs : Conflicts: nodejs-legacy

while setting up an iquidus explorer i just hacked my way to nodejs-legacy installing freedom through sheer elan ... maybe

after being given access to someone elses pre-loved server,
was getting error whilst trying to install nodejs-legacy
The following packages have unmet dependencies:
 nodejs : Conflicts: nodejs-legacy

not entirely which bit was the real magic but after an extended duration of getting constant rejections this is hopefully the bare basics,
possibly it's more than everything necessary.
remove nodejs, install nodejs from nodesource, change package manager priority to ubuntu servers, upgrade nodejs, install nodejs-legacy

remove current nodejs
# apt-get remove nodejs

update etc
# apt install -f
# apt update
# apt dist-upgrade

install nodejs v10 from the horses mouth (ie nodesource itself)
# curl -sL | sudo -E bash -
# apt-get install nodejs -y


# nodejs -v

adjust priority to ubuntu servers and upgrade to v10.25
# apt-cache policy nodejs
  Installed: 10.0.0-1nodesource1
  Candidate: 10.0.0-1nodesource1
  Version table:
 *** 10.0.0-1nodesource1 0
        500 trusty/main amd64 Packages
        100 /var/lib/dpkg/status
     0.10.25~dfsg2-2ubuntu1 0

        500 trusty/universe amd64 Packages
nano /etc/apt/preferences.d/nodejs

.. in my case i gave a higher value by adding the following
Package: *
Pin: origin
Pin-Priority: 1002

# apt-cache policy nodejs
  Installed: 10.0.0-1nodesource1
  Candidate: 0.10.25~dfsg2-2ubuntu1
  Version table:
 *** 10.0.0-1nodesource1 0
        500 trusty/main amd64 Packages
        100 /var/lib/dpkg/status
     0.10.25~dfsg2-2ubuntu1 0
       1002 trusty/universe amd64 Packages

re-install and success !!
# apt-get install --reinstall nodejs 

.. updates nodejs ..

# apt-get install nodejs-legacy

discussion on raising the package priority

Tuesday, 10 April 2018

updating TLS protocol for git on Mountain Lion using Macports

apparently github has deprecated older TLS protocols,
when attempting to use git geting error

fatal: unable to access '': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

seemingly the answer is to upgrade curl (which also updates openssl), and git

$ curl --version
curl 7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8y zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp 
Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM NTLM_WB SSL libz 

$ sudo port install curl is downloading and installing etc etc etc ...

open new window
$ curl --version
curl 7.59.0 (x86_64-apple-darwin12.6.0) libcurl/7.59.0 OpenSSL/1.0.2o zlib/1.2.11 libidn2/2.0.4 libpsl/0.20.1 (+libidn2/2.0.4)
Release-Date: 2018-03-14
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets HTTPS-proxy PSL

also necessary seems to be updating git, the latest available for Mountain Lion is too old

$ git --version
git version 2.3.5

so it becomes necessary for downloading, going into such directory and making

$ /Volumes/whereever/new/version/is/git --version
git version 2.17.GIT

using this newly made version is now succesful for such as cloning

$ /Volumes/whereever/new/version/is/git clone

installing via command line is not effective ($ make install), the version of git is not updated in this case.
so i will have to sort that out later ..

Saturday, 3 March 2018

Importing your address into a new wallet-qt.

For whatever reason, there are times you need to import your address into another wallet. 

This post will go through three steps, your situation may not match these steps so please pick and choose your information as necessary.

1. exporting your private key

2. creating a new empty wallet

3. importing your private key

These steps will be addressed very simply and will require some prior knowledge, please see this post which includes much more information about similar material

1. get your address, dump private key

I will assume you already know your address,  this post will use the address B8QX8peKA9LvDb4Ya5GaMWwwLQoukV2aRY
so now you go into the debug/console
please enter command (using your address
> dumpprivkey B8QX8peKA9LvDb4Ya5GaMWwwLQoukV2aRY

you will need to copy the output somewhere safe, you will need this to import into a new wallet.
the private key in this case is

now close your wallet-qt

2. enter your datadirectory, the bumbacoin datadirectory on my computer looks like this

you will notice i have a highlighted file, wallet.datBAK and a wallet.dat, in this case wallet.datBAK is a prior backup i have made, and wallet.dat is the file that currently holds my address,
i now need to delete or rename the file wallet.dat
then when the wallet-qt starts it will generate a new empty wallet.dat file.

3. open the wallet-qt, it will now create an empty wallet,
once again open the debug/console, this time you will import the private key from step 1.
at this point you can give the address an optional name, 

> importprivkey Pe69Ten35qDWqc5cHbGEZfG5bq9npRtY8WkjXAvfGGaJiUQMFo63 newaddress

this will take some time as it scans the database for transactions. please wait.

you have now imported the key, congratulations ;)


it is possible that the wallet did not pick up all transactions and you are missing some, you can repeate the process as many times as you like and it should work.

alternatively, if you have 1000's of transactions, it may be better to start up with -rescan
or re-sync the entire chain and let it pick up each transaction.
that is a different post though