Yes. You must put the bootstrap.dat file in the ~/.iocoin folder (/home/pi/.iocoin), there where your iocoin.conf and wallet.dat files are.

PS: Also remember to enable your firewall (sudo ufw enable)

Great.

What problem do you have with downloading the bootstrap file?

The Pi password has nothing to do with anti-virus. The Pi like any Linux/Unix machine has many things that can be configured for security and security practices that can be followed. Part of the domain covers good password management and another malware management if you want to go to that level of depth.


When the Pi boots up from the card it ends at a command prompt after you authenticated your user account. It is not something that has to be "opened". The GUI on the other hand has to be started, either manually or automatically during boot.


If you execute the script I posted on a raw Jessie loaded Pi it does exactly that - the wallet is there as an icon on the desktop to run. However it requires some preparation of the card as well as downloading the blockchain. It is possible to make an 8GB image of a prepared card that if burned to another card will boot up to a fully prepared Pi with the new card. The image is 8GB and could be burned to a card for someone or the person can download it and burn it to his card on his own.


I dont think anything should be sold as a principle. if there is a server that can take 8GB files with lots of bandwidth, people can rather download the image and burn to their cards. Or if someone can start a bittorent with the image it can also work p2p. it is possible to burn the 8GB image to  larger card and just resize the partition to the max of the new card.

I have tested the script on an 8GB card and it works perfectly. The installation takes about 500MB of space excluding the blockchain.  You might have made a mistake with preparation of the SD card.

You have to do the following things:
1. Download the Raspbian Jessie image https://downloads.raspberrypi.org/raspbian_latest
2. Unzip and burn the image to your card, 8GB or higher. You get different tools for this and if you use a Mac you can use Apple Pi Baker v1.81
3. Boot up from the card and do the setup.
4. At the command prompt run sudo raspi-config
5. In raspi-config click on expand file system so that your whole card becomes one big partition. This will leave about 3.5GB free of the 8GB card and you will have ample space for the script.
6. You can also setup other things in raspi-config like your localized settings, hostname, password etc.
7. This is most probably a superfluous comment, but at the command prompt type startx to bring up the graphical interface where you can then launch the Qt wallet.

Regarding your question on the 512MB memory - I do not have an older ARM6 processor Pi with 512MB memory so I cannot tell you if it will work. Chances are good though that it will work on your version.

Thanks for the incentives!

I spent some more time and looked into the Qt5 issue. I managed to solve it so that Qt5 wallets can be widely distributed but only when using Raspbian Jessie. I have updated the Pi instructions post to have 2 installation scripts, one for Wheezy (only headless wallet) and one for Jessie (headless and Qt5 wallets)

It is a pleasure

IOC address appended to Pi wallet post above.

Here are the Raspberry Pi wallets for IOCoin. If you are using Raspbian Wheezy (v7) you have to use the headless command line wallet. If you are using Raspboan Jessie (v8) you can choose between the headless commandl line wallet or the Qt wallet.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2 (ARM7) running Raspbian Wheezy (v7) as well as Jessie (v8) and the instructions and scripts assume you are running as user "pi". It is a pre-requisite to have either Raspbian Wheezy or Jessie installed on your Pi micro-SD card. You can find instructions of how to do this on https://www.raspberrypi.org/downloads/ by either installing n00bs and selecting your OS or by downloading the image for one of the 2 versions of the OS.
3) Installation directory where the binaries are installed is ~/opt/iocoin or /home/pi/opt/iocoin
4) To run the wallets go to the directory with the wallets and run the wallet file (iocoind_jessie or iocoin_wheezy for the respective headless wallets at the command line or if you have Jessie you can click on the IOC icon on the desktop or run the iocoin-qt wallet.
5) An Internet connection is required for the installation
6) A bootstrap.dat is available to fast track the blockchain sync - up to block 734407. The installation script does not force the install of the bootstrap.dat as it is very large. You need to manually download it, unzip it and place the bootstrap.dat in the ~/.iocoin folder and then run the wallet.
7) The bootstrap.dat also works for Windows wallets. Windows users just have to copy the bootstrap.dat file into their c\users\yourusername\AppData\Roaming\IOCoin folder and run the Win client again
8.) You need at least an 8GB memory card for the wallet.
9) The installation itself takes about 30-45min on an out-of-the-box Pi, but due to the large chain it will take several hours to import the blockchain.
10) You cannot just download the dynamic wallets, you have to run the script to get the dependencies as well else it will not run.
11) The installation script does not enable the UFW firewall by default. If you want to enable it, uncomment the UFW lines in the script and add the ports you want open and run it again or enable it manually by running the UFW commands as in the script with the correct port numbers from the command line.
12) Always verify the checksums when you download files to make sure it was downloaded ok. To verify the checksums on your Pi, go to the ~/opt/iocoin folder and execute sha256sum <filename> and md5sum <filename> and compare the values with the values in the checksums.txt file. Do the same for the bootstrap.dat

Instructions to use the headless command line daemon wallet:

1) The installation script creates an iocoin.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/iocoin and enter ./iocoind_jessie or ./iocoind_wheezy (depending on which version of the OS you installed) in a terminal window to start the server
2) After the blockchain has been imported you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./iocoind_jessie or ./iocoind_wheezy eg. ./iocoin_jessy getinfo. During the first time blockchain import process the wallet will be non-responsive in the sense that it will say it cannot connect to the wallet. Just wait for the import to finish and the wallet will become responsive again.
3) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
4) To encrypt your wallet run the command ./iocoind_jessie encryptwallet <yourpassword> or ./iocoind_wheezy encryptwallet <yourpassword>
5) Once you have the wallet running, blockchain imported and your wallet with coins on the Pi, then you can kickstart staking by executing ./iocoind_jessie walletpasshprase <yourwalletpassword> 99999999 true or ./iocoind_wheezy walletpasshprase <yourwalletpassword> 99999999 true

Instructions to use the Qt wallet:

1) The wallet works exactly the same as the one in Windows.

To kickstart the installation execute the following commands at the command prompt or in a terminal window on your Pi.

For Raspbian Wheezy (headless wallet)

For Raspbian Jessy (headless & Qt wallet)

Direct links:
Link to Wheezy wallet installation script
Link to Jessie wallet installation script
Link to Qt wallet for Jessie
Link to headless wallet for Jessie
Link to headless wallet for Wheezy
Link to virustotal scan for iocoin-qt
Link to virustotal scan for iocoind_jessie
Link to virustotal scan for iocoind_wheezy
Link to bootstrap.dat up to block 734407 (228MB zipped)
Link to checksums.txt

Ill look into making one.

I was one of those that didnt understand properly that the dev will be valuing his alt bags and making the bag's value in BTC (like market cap calc) part of the distribution as a contribution. or maybe I still dont understand exactly how it worked. Only after the distribution did I realize the big impact it would have. In essence the dev "sold" his alt bags through a calculation similar to calculating market cap it seems not taking into account real buy orders in the market. Needless to say I was upset about it that the dev got 600k of the 1m coins.

After a while though I realized that it could actually be a positive thing. Lets assume for a moment that the dev has good intentions and will not dump the 600k. Lets further assume that the dev does own the alts listed on the front page and will not dump those either. Then it effectively means that there are 400k SLS in circulation. Add to this the future cash inflows from the alt bags staking earnings and the coin has the potential of trading 100-300k. The block explorer is quite nice and it is easy to watch the top account and the public can quickly blow the whistle if the top account moves significantly.

Unless of course that there is something else that I don't understand yet of the inner workings that is not clear on the OP.

I think the diff went up too high for anyone else to stake. He probably closed the premine accounts for staking so that rate of blocks go slower than 16min so that the diff can go lower. During those periods of diff lowering the blocks will be extremely slow, potentially not finding a block for a whole day. Diff has already reduced from 2000+ to 875.

Are you distributing the full 1,000,000? How confident are you that your calculations for distribution are accurate?

There is no problem with the wallet. Everyone is just waiting for the next block. With the next block everything will be current and you will also see how much the diff will drop. Coinage is also not dependent on block movement so you are accumulating coinage while waiting for the next block. Also, coins can only move when blocks are solved so until the next block your coins will be in limbo if you moved them.

What is your block height where you are stuck? The chain is currently on 51466 and should be moving again later today. As long as you are on this block as well all is 100% in order. Until the next blocks are solved movements will appear "stuck" but nothing is wrong or broken. Just be patient.

Patience is a virtue but a rare attribute in crypto.

Download the 2 block files and place them in your \roaming\CIONZ folder together with your wallet.dat and CIONZ.conf. Run the wallet and you will be up to date.

The chain is slow atm because Spots seems to want the difficulty to go lower. Lower difficulty increases the chances of getting a block for holders with smaller balances.

I got another stake. You just have to be patient and wait until you get the stake. It is also very important to understand the purpose of the premine for CIONZ. From observation it seems that in this case the premine can be seen as Premine-as-a-Tool (PaaT). Its purpose is to 1) move the chain if it gets stuck and 2) make difficulty go up or down as required. It is irrelevant really what the size of the premine is. Using PaaT in this way eliminates the issues that were prevalent with balls and 10k as it is possible to make staking very difficult and therefore influence users to rather hold instead of sell as well as to keep coins static instead of moving them and losing coinage.

All of this makes the coin more rare and creates opportunities for profit for those normal holders that are patient and build their holdings.

and another...

and another...

Looks like chain is stuck @ 51406

It looks like the Yobit chain is up and running again.