Sure. Ill make the image.

It is possible to do this. One can make a generically prepared card with everything installed except the wallet.dat. An image is then made of the card which is uploaded or shared via bittorrent. The file will be 8GB though as its only drawback.

That is what Cooper thought in Interstellar when the went down to the planet to look for the beacon. When he got back to the ship 23 years had past. Crypto time is very much like that 1 earth day is like one year in Crypto-time

Yes it takes about 3 days for a straight sync on Pi. Bootstrap slightly less and bootstrap on PC about 12 hours. It is what happens when chains get longer. BTC itself can take weeks. BTC "solved" that with headers only sync. It is something you could consider as the chain grows.

Activate coin control, go into send and select inputs. Expand the tree and see if things look normal there.

No. Easy come easy go. Giveaways = bad.


Correct.


there is no relationship between number of deposits and staking. The relationship is between number of coins in the wallet (input block size also matter) and the time they have been at the address without moving, as well as if the wallet is unlocked for staking.


Sounds like an error on your side. Do a normal sync from scratch. (Clean your directory except your wallet.dat and warp.conf. put the right things in the .conf and resync your chain)

No, it is why he got a permission error with the compile.

Pleasure. Source code has the incorrect permission on the file.

cd ~/warp/src/leveldb
sudo chmod 755 build_detect_platform
run your make again

You have to ask yourself first what is the purpose of an HTML wallet and how such a wallet will achieve the coins goals and objectives. A new type of wallet could for example improve user experience by being able to transact faster, be more secure, transact quicker on the move, use less space by being thin or whatever you are trying to achieve. You will then have to ask yourself if having an HTML wallet on a Pi will realise those same advantages for the user. If not then it might be best to remain with the current wallet on the Pi as the advantage of Pi is to have a wallet at low energy usage mostly for staking at long intervals.

It is an option.

Importing the block chain from the bootstrap.dat took about 12 hours on a Core i7 notebook during a test. So yes it takes a long time to import 730k blocks. It is still shorter though than a native sync.

The problem with fantom is that there is a problematic block at 19xxxx somewhere that gets stuck with a download from scratch. There are copies of the longest chains out there eg. Block explorer and exchange that could make a bootstrap that could solve the problem to get more up to date nodes out there.

See posts 2635, 2636 and 2639 above

In what sense? What are your concerns?

Here are the Raspberry Pi wallets (headless and Qt) for SaluS on Raspbian Jessie (v8)

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2 (ARM7) running Raspbian Jessie (v8) and the instructions and scripts assume you are running as user "pi". It is a pre-requisite to have 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 of the OS.
3) Installation directory where the binaries are installed is ~/opt/salus or /home/pi/opt/salus
4) To run the wallets go to the directory with the wallets and run the wallet file - salusd for the headless wallet at the command line or click on the SaluS icon on the desktop or run the salus-qt wallet.
5) An Internet connection is required for the installation
6) A bootstrap.dat is available to fast track the blockchain sync and goes in the ~/.salus folder
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\salus 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.
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 enables the ufw firewall by default, but does not force any special rules. 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/salus 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 salus.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/salus and enter ./salusd in a terminal window or at the command line 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 ./salusd eg. ./salusd 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 ./salusd 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 ./salusd 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.


Let me know if there are any issues.

Direct links:
Link to SaluS wallet installation script
Link to Qt wallet
Link to headless wallet
Link to virustotal scan for salusd
Link to virustotal scan for salus-qt
Link to bootstrap.dat (zipped)
Link to checksums.txt

SaluS address : SjbGrwb7wLYkr9SShpvAScCwxoDw1ib1Cb

If I remember correctly, the diamond dev made some commits to have an option to disable sse2 (so as to not re-invent the wheel)

Just execute "sudo ufw enable" at the command prompt. By default it disables all incoming connections, but will allow outgoing connections.

I looked into the the Raspberry Pi wallet - The source code contains sse2 which is Intel functionality that ARM does not understand. It is possible to make a Pi wallet but then the dev has to modify the code to be able to exclude the use of sse2. It might be possible to add a --disable-sse2 option in configure. If the devs can do this then the Pi wallet will be possible.