Here is the Raspberry Pi wallet for v0.8.7.6-unk-beta - for both the Qt and headless daemon (command line) - UPNP enabled. It is possible to solo mine with this wallet if you want to.

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/tetcoin or /home/pi/opt/tetcoin
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 Tetcoin icon on your desktop to launch the Qt wallet or go to the directory with the wallets and run the daemon (tetcoind) 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 109643
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\tetcoin 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/tetcoin 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 a Qt wallet in Windows. Instructions to use the headless command line daemon wallet:

1) Since you the installation script created a tetcoin.conf file with the startup settings in it, go to the folder with the binaries ~/opt/tetcoin and enter ./tetcoind 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 ./tetcoind eg. ./tetcoind getinfo
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 ./tetcoind encryptwallet <yourpassword>

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 tetcoin-qt
Link to tetcoind
Link to virustotal scan for tetcoin-qt
Link to virustotal scan for tetcoind
Link to bootstrap.dat up to block 109643 - .tar.gz
Link to bootstrap.dat up to block 109643 - .zip for the Win users
Link to checksums.txt

Here is the Raspberry Pi wallet for v0.8.7.4-19 - for both the Qt and headless daemon (command line) - UPNP enabled. It is possible to solo mine with this wallet if you want to.

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/czarcoin or /home/pi/opt/czarcoin
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 Czarcoin icon on your desktop to launch the Qt wallet or go to the directory with the wallets and run the daemon (czarcoind) 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 106595
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\czarcoin 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/czarcoin 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 a Qt wallet in Windows. Instructions to use the headless command line daemon wallet:

1) Since you the installation script created a czarcoin.conf file with the startup settings in it, go to the folder with the binaries ~/opt/czarcoin and enter ./czarcoind 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 ./czarcoind eg. ./czarcoind getinfo
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 ./czarcoind encryptwallet <yourpassword>

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 czarcoin-qt
Link to czarcoind
Link to virustotal scan for czarcoin-qt
Link to virustotal scan for czarcoind
Link to bootstrap.dat up to block 106595 - .tar.gz
Link to bootstrap.dat up to block 106595 - .zip for the Win users
Link to checksums.txt

I have updated the bootstrap.dat to block 20386

https://bitcointalk.org/index.php?topic=1072230.msg11545746#msg11545746

I have updated the bootstrap.dat to block 18432

https://bitcointalk.org/index.php?topic=1073653.msg11576747#msg11576747

How is the guide coming along? I think there are several people that want to get MN up and running.

He has been reported several times already. It seems that it is not only on this thread that he is causing trouble. A start would be not to quote any of his posts and ignore anything he says.  He said a few posts back that he thought he was out of this thread but then he got quoted and was pulled back in. Lets then not quote him and ignore his posts.

Can you please post a step-by-step guide of exactly how to configure a masternode and what must go in the .conf file of the local wallet (rpcwallet) and what must go int he .conf on the remote wallet that is the actual masternode.

How do you actually create a MN. I have tried everything and cannot get it right. The config that is generated in the wallet witht he MN private key etc is that the config for the wallet with the collateral address or is that the config for the MN itself?

If POS needs fixing you can ask Presstab to fix it (at a fee of course)

It looks like the WOC2 chain has moved. This can only mean good news and that the swop coins have probably been transferred.

Is this coin still alive?

I have updated the bootstrap.dat file up to block 113395 which works on both Linux and Windows versions of the wallet. I have also recompiled the Pi binary with UPNP enabled which improves the number of connections.

https://bitcointalk.org/index.php?topic=954240.msg11261172#msg11261172

You can attach the SSD to the PC an then specify with -datadir that the data directory is on the SSD. This will work. POS seems to be an art and you will get different responses on different methods from different people.

barabbas, it seems that you are carrying on with your attempts to sabotage this project that shows promise, by spreading, fud, baseless accusations which if unproven are lies. This is crypto and there is always risk and by the mere fact of participating in crypto one knows the risk one is taking. The devs for this project have delivered much more so far than most other projects which reduces the risk. Lets look at this based on the facts at hand:

Your argument seems to be around the 400k coins at 120k sats to raise ~500BTC. You keep referring to the stupid (moronic) action from the dev to do this as he will never get it. You also say that the dev is manipulating the price as well as that he is doing this project only to get access to actionable trading information.

I have attached a screenshot right at the bottom which you keep overlooking which is very clearly posted on the OP, indicating that the number of coins and price was a community decision and not that of the dev. Based on the poll, the community voted for 400k @ 120k sats. Personally I voted for 100k @ 75k as that is more realistic imo. However, as shown by the poll outcome the option of 400k @ 120k sats won by far. I accept the outcome and therefore support the community in this regard. As a matter of principle I would be upset if the dev gets a mandate from the community and then do something different. This evidence clearly renders any of your claims, accusations and references to the number of coins and price thereof, the devs involvement in the choice and anything else related to it as baseless and unsubstantiated. Just the mere fact that you base your whole argument on the number of coins and price without reference to the poll and the mandate by the community makes your whole case fall flat. Unless you can prove that the dev acted on his own with the placement with its current specs your argument does not hold water.

The dev mentioned that he bought coins on the market. He did not say that he is manipulating the price. It can also be one of the other 30 voters that are buying selling coins that would like to see the placement succeed or even just a price increase based on normal trading. Unless you can provide confidential trading records from Bittrex that indicates ALL trades at the current levels are from the devs account, your accusations are just speculation.

I expect you to provide evidence that the poll did not happen, the confidential trading records as well as evidence that the dev is doing this only to get access to actionable trading information because without it, your accusations are baseless, lies, fud and typical of that of a troll that is trying to wreck a project that shows promise and the way you state your case just plan rude and inappropriate. You are so confident with your accusations that you keep returning and posting them again and again which seems to indicate that you have the evidence at hand. You have already caused damage in that you probably scared away investors for the current placement. I will be reporting my own post to the moderators and that I have requested this evidence from you. If you can provide the evidence then I will apologise and follow your warnings. If you cannot provide the evidence, I would request the moderators to take action against you as a fudder, lier, troll and saboteur if they agree with me. If you cannot provide evidence to support your claim them stay away from this thread.

I am so far satisfied with the way that the dev team has handled things with MTR and ToshiDesk and it seems much more professional and refreshing than most other offerings in the alt-coin market.

Screenshot from OP for your reference and convenience:

Dev has made one post since launch. Maybe another post with "hi" should be done by him first before looking at other exchanges.

Well, get that block explorer (proper one) up and running and then it will be clear if pos is working or not.

It is on Yobit.

If you look at the wallet it says not staking because you do not have mature coins. It might be that the coin maturing is not working properly as per the design. Coins should mature after 2 hours in the wallet.

If there are people with mature coins and not staking, it is probably because of competition with the POW.

If you decide in the end you want to go the Pi route to save energy, have a look a the link below and let me know if you need any assistance. Which makes me think that the chain has grown a lot and Ill post a new bootstrap.dat file later today.

https://bitcointalk.org/index.php?topic=954240.msg11261172#msg11261172

I run all my wallets on Raspberry Pi. It works great for just about anything including solo mining, staking you name it. The only issue is that Qt5 libraries are not available yet to so ant apt-get install. It is possible to do a standalone compile of Qt5 but that becomes very tricky and the Qt5 compiles on a i looks ugly. In addition, compiling Qt5 on the Pi takes between 1-2 days.

In order to determine the strategy of a coins wallets on a Pi, look if the .Pro file has been setup for Qt5 or Qt4. If Qt4 then no problem it will compile, if Qt5 then skip Qt and just compile the headless daemon. You could always build your own Qt4 project if you really have the time and effort but it generally is not worth the effort. Here ans there are tricks to bypass the Qt5 issues like the qtwaitingspinner solution I mentioned in the one thread. In all cases headless daemon works perfectly fine. Qt wallets have a marginal advantage in that you can see visually what is going on with your coins and managing addresses with copy paste etc. There is nothing though that can be done with Qt wallet that you canot do with the daemon with a little bit more effort.

Iv posted several installation scripts for Pi wallets through the alt-coin section. If you want advice on a certain coin or want a script for it let me know.

EDIT: I would recommend the following 2 things for the headless daemon: 1) Change UPNP to "1" in the makefile.unix and 2) always check the src/leveldb/build_platform_detect to make sure it has read permissions for at least the account your compiling with, but it is ok to change it to "anyone" or world for the build.