I have updated the bootstrap.dat file up to block 193158 to speed up the blockchain sync for new wallets and put the link in the Raspberry Pi instructions post. The file is also compatible with Windows wallets.

https://bitcointalk.org/index.php?topic=831777.msg11203381#msg11203381

The two main factors to focus on are usability and technology/innovation. The usability is what will introduce more non-crypto people to the scene and distribute the coin more widely. Technology, functionality and innovation is what will keep the citizens of cryptoland interested. The most important objective is setting a strategy to increase general usablility. The second objective is to keep the interest in cryptoland. The first is more long term and the second is short term and must be agile. It is important to keep up with the times and innovation and to adapt to the movements in the scene. Currently the latest "hot topics" are masternodes and instantX and should be a short term focus to implement. Some DMD will be extracted from the markets and put in masternodes and crypto citizens will be drawn in to attempt to get masternodes to earn their slice on block rewards. It will also make the network more robust. It is important to maintain short term momentum and be agile in order to be able to deliver on the longer term strategy.

Its fine. If you don't want to put your money on black here then you are welcome to put it on red somewhere else. 

The linux guide for masternodes needs adjustments. The guide recommends Ubuntu 14.04 which is not ideal, since the pre-compiled binary as well as the source depends on libdb4.8. Libdb4.8 was upgraded to libdb5.1 in 14.04 and onwards and therefore there are no 4.8 dblibs to apt-get and the pre-compiled binary fails. The instructions must be changed to recommend 12.04. If however 14.04 remains recommended, then the instructions must be upgraded to either give workarounds to get 4.8 compiled and installed or to recompile the source on the VPS with 5.1 using the the incompatible db switch or change the source to use 5.1.

How is it possible?

How many masternodes currently?

I tried some solo shortly after launch and got blocks with 0.00 reward and then stopped and moved on.

I am also concerned about the wallet creating its files in the same directory as the executable instead of the roaming directory (Win) and then there is also the standard coin.conf deployed with the binary with the standard node configured. Extra caution is advised when these attributes exist.

LOWGOON?

Rather report bugs/exploits/vulnerabilities in PM.

Even if someone knows who the dev is it is not necessary to dox him. Let him have his privacy. As long as he delivers all is ok.

No, POS difficulty will increase to bring block time back in line with design.

Is it not so that your main coins are primed again for staking after 1 hour, but it is just the stake that takes 3600 blocks to become available and eligible for staking? Once the 3600 blocks are over the stake becomes part of your main coins that mature again 1 hour after hitting a stake.

There is an experimental Snappy Ubuntu available but it is still early days for it and I decided to rather go with the mainstream Raspbian (Debian). Post back on your endeavours after the weekend.

There are no rules that apply to crypto trading and therefore it is Wolf of Wall Street stuff to the power of 10. The first agenda is manipulation for profit by traders and the second agenda is manipulation for profit by scam devs. In-between here and there there are sincere devs and investors that care about the foundation of crypto and enhancing the body of knowledge. Their innovations and skills stick and what they developed gets cloned and enhanced by the next guy that applies his knowledge and skills in turn and so the cycle carries on. Those coins and devs have a tough task because sometimes even if a dev does something great it does not fit into the 2 agendas mentioned above and deos not get noticed or becomes meaningless. However, a sincere dev that focuses on his plan and carries on delivering great stuff in line with new developments on the scene will prevail and price will increase as a result. This must be coupled with usability and creating demand.

I cannot say yet where in the spectrum this coin and dev is and time will tell (although I have not seen evidence of anything bad so far), but what I do know is that the people with the agendas as mentioned above are moving around the scene like locusts devouring everything in their path and sometimes destroying even promising things along the way.

To the dev of this coin I can just say that if you are sincere carry on with your work and that Android wallet looks great. Keep applying your skills and mind and the result will be to disprove the fudders and the rewards will tail your efforts.

Thanks for testing it on the older Pi.  

I am currently busy with Qt5 on Pi as a pet project and once that is sorted it will have to be static builds for the GUI wallet because I could not find any readily available libraries for Qt5 on Pi and I had to compile it natively (almost 2 days). Agreed that if someone just buys a Pi for staking a wallet or two on it, then static builds will be fine.

Here is the Raspberry Pi wallet for v2.0.5.7 - for both the Qt and the headless daemon (command line wallet) versions.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallet was built and tested on a Raspberry Pi2 (ARM7) running Raspbian Wheezy. It might work on an older Pi but I have not tested it
3) Installation directory where the binaries are installed is ~/opt/diamond or /home/pi/opt/diamond
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 Diamond icon on your X desktop or go to the directory with the wallets and run the daemon (diamondd) with the options you want at the command prompt or in a terminal window
5) An Internet connection is required for the installation
6) I have made a bootstrap.dat to fast track the blockchain sync - up to block 918953. I did not force the blockchain download in the installation script due to the size. The file has to be downloaded manually and copied into the same folder where your wallet.dat file is. On the Pi that is ~/.Diamond
7) The bootstrap.dat also works for Windows wallets. Windows users have to unzip/tar the file and copy the bootstrap.dat file into their c\users\yourusername\AppData\Roaming\diamond folder and run the Win client again
8.) You need at least an 8GB memory card
9) The installation itself takes about 45min on an out-of-the-box Pi, but the blockchain import will take a very long time
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) Remember to confirm the checksums of your files to make sure that they downloaded ok. Execute the commands sha256sum <filename> and md5sum <filename> at the command prompt or in a terminal window in the directory where the file is that you want to check.

Users will be familiar with the Qt version of the wallet as per the Windows version. Instructions to use the headless daemon:

1) Since you have an Diamond.conf file with the startup settings in it, go to the folder with the binaries ~/opt/diamond and enter ./diamondd in a terminal window to start the server to create the ~./Diamond folder. Exit the wallet.
2) Download and copy the bootstrap.dat into the ~./Diamond folder and run the wallet again
3) After the blockchain has been imported you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./diamondd
4) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
5) To encrypt your wallet run the command ./diamondd encryptwallet <yourpassword>
6) To stake with your wallet run the command ./diamondd 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 diamondd
Link to diamond-qt
Link to bootstrap.dat up to block 918953
Link to checksums.txt

If you like this, you are welcome to donate DMD to dPzTua6hdEazWfqrCehNYZuRee8zxq9igo

A perfect example of the efforts of the fud group. What constructive purpose and contribution can this post possibly have on the coin, the community and crypto body of knowledge in general? Comments like these do not build a robust digital financial ecosystem to carry humankind forward. If you dont like a coin or a dev, post constructive criticism, with suggestions of how things can be improved.

You started it yesterday so congratulations.  

Your post 583 at which time price was still >10k somewhere and then the rest jumped on the bandwagon and it was one slippery slide downwards.

Has the fudders won on this coin?

It seems like it was a relentless co-ordinated attack that started yesterday with fud after fud without evidence, enticing panic selling until the coin has dropped this low. The best part is that the dev did not even do or say something wrong to deserve all the fud. Yet the attacks came wave after wave with hollow posts liek "This coin is dead" etc. The dev has been very professional so far in his communications. I thought that BCT ha some policies against blatant baseless fud attacks but anyways.

Lets see what happens going forward.

How many coins did you have and what was your network weight?