Here is the Raspberry Pi wallet for v0.9.1.0-unk - for both the Qt and headless daemon (command line) - UPNP enabled.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallet was built on a Raspberry Pi2 (ARM7) running Raspbian Wheezy.
3) Installation directory where the binaries are installed is ~/opt/viral or /home/pi/opt/viral
4) All that is needed is to execute the command below on your Pi in a terminal window and afterwards you need to click on the Viral icon on your desktop to launch the Qt wallet or go to the directory with the wallets and run the daemon (virald) with the options you want at the command prompt or in a terminal window
5) An Internet connection is required for the installation
6) A bootstrap.dat is used to fast track the blockchain sync - up to block 7847
7) The bootstrap.dat also works for Windows wallets. For your convenience I have included a direct link below to an untarred bootstrap.dat to make it easy for the Windows users. Windows users just have to copy the bootstrap.dat file into their c\users\yourusername\AppData\Roaming\viral folder and run the Win client again
8.) You need at least an 8GB memory card
9) The installation itself takes about 30-45min on an out-of-the-box Pi
10) You cannot just download the binaries, 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 port 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.
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/viral folder and execute sha256sum <filename> and md5sum <filename> and compare the values with the values in the checksums.txt file

Users will be familiar with the Qt wallet as it works like the Windows one. Instructions to use the headless command line daemon wallet:

1) Since you the installation script created a viral.conf file with the startup settings in it, go to the folder with the binaries ~/opt/viral and enter ./virald 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 ./virald
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 ./virald encryptwallet <yourpassword>
5) To stake with your wallet run the command ./virald walletpassphrase <yourpassword> 99999999 true

Let me know about any issues that you may encounter.

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

Direct links:
Link to installation script
Link to viral-qt
Link to virald
Link to bootstrap.dat up to block 7847
Link to bootstrap.dat up to block 7847, untarred for the Win users
Link to checksums.txt

If you like this, you are welcome to donate Viral to VThqxinccshK3piywdmP6TQXLc2t1VQ69X

It does work fine. Iv been running solo mining on a Raspberry Pi. 

You want to get rid of your coins?

Balls and the experimental 10K holds the record with billions in netweight.

You have to create it.

How does the giveaway work?

Have you seen TimC's pic above of his wallet? (lucky bastid) This is ACISCs we are talking about at <10 difficulty and not CPU miners. ASICS let 100 blocks fly by in 10 seconds.

If you dont have the pools in at launch it is not a fair launch as not everyone can solo mine. Some people have to remote to their miners or have rented miners. The honourable and correct thing to do is to do go test your code and do a re-launch at a later date. If you continue you will lose support of the pools and the coin will be tainted with fud from day one.

Even if the code works now it is 10min down the line and blocks have been solo mined. This is a test of management's integrity.

Dev, how about wallet update with masternodes and the rest. 

PUA is not virus but a Possible Unwanted Application.  A packer can be used in malicious activity and there is a slight change that it is malicious, but probably not.

There seems to be halving


And it looks like halving every 100,000 blocks, with a minimum of 1 coin in the end.

Nevermind, it is 30s. That means 2,880 blocks per day = 144,000 coins per day = 52,46m per year. Without halving it will take 20 years to get to the max supply so that seems an irrelevant number.

What was the block time again?

So it was his dependencies then.

But you started it.

What is the story behind this coin?

So what is the status here?

Have a look here. It probably works the same.

https://bitcointalk.org/index.php?topic=895425.msg11373421#msg11373421

It might have been a masternode that tipped.

What % of the blocks will masternodes get and will the nodes be up before POW?