He has a point and his concerns are valid. If there are issues it needs to be fixed. You cannot expect a site to be adopted and grow if the systems are not accurate. I am sure there will be teething problems, but these must be fixed if they want people to start spending big amounts on the site.

If there are issues, then put a disclaimer not to spend large amounts until the devs give the go ahead and mark it as alpha or beta or something.

On the other hand, it is not possible to do 100% testing and the only way the real issues will be detected are in the field some of which have been detected through "live testing" by people like philakone.

It is not an issue to compile. You just need to chmod +x the build_detect_platform in src/leveldb before you compile.

Is the mechanism for this ICO a normal exchange based ICO?

Re-tweet please

Fixed 

Staking is very slow due to network weight which is a good thing as it indicates strong security of the chain. The block rate is in line with design which is good.

With 100k you will relatively quickly within a few hours get 1 stake of 2.8 coins. Then the 100,002.8 will split into 2 input blocks of ~50,001 coins each which will take slightly longer and will give you two stakes, 2.8 coins each. Then the 50,001 will each split into ~2 blocks each of 25,000. It will take slightly longer again and then you will get 4 stakes of 2.8 coins each. This will carry on until your input blocks are very small. When they get too small combine them, but all your blocks over time will all hit a stake, it might just take a long time if they become too small. Whether you stake with 100k in one block or 100 coins in a block both will give you 2.8 coins when they hit a stake.

PM me if you want to sell. My price is low though but maybe we can work something out.

Here are the Loco Raspberry Pi wallets (headless and Qt) for Go2 v1.4.5.0-Alpha on Raspbian Jessie (v8) as well as a bootstrap.dat file. The wallet has been tested on both a Pi2 and Pi3.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2/3 (ARM) 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. NB! It is important that if you do a fresh install from a Jessie image, that you first expand your file system with raspi-config. It is the first option in the menu. The default image they provide installs a partition of about 3.5GB and it needs to be expanded to 8GB or you will not have enough space for the installation. It is furthermore always a good idea to select the boot options in raspi-config to boot to a command prompt with authentication. You can then start the graphical desktop with "startx" manually. This helps with issues during upgrades.
3) The installation script installs the required dependencies automatically.
4) Installation directory where the binaries are installed is ~/opt/loco or /home/pi/opt/loco
5) To run the wallets after installation go to the directory with the wallets and run the wallet file - ./locod for the headless wallet at the command line or click on the loco icon on the desktop or run the loco-qt wallet file.
6) An Internet connection is required for the installation
7) You need at least an 8GB memory card for the wallet.
8.) The installation itself takes about 30-45min on an out-of-the-box Pi.
9) You cannot just download the dynamic wallets, you have to run the script to get the dependencies as well else it will not run.
10) The installation script enables the ufw firewall by default, but does not force any special rules. The wallet still works this way with the port blocked. If however you want to enable it to become a fully functional node, uncomment the ufw lines in the script and add the ports you want open (default 34575 for Loco) 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.
11) 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/loco folder and execute sha256sum <filename> and md5sum <filename> and compare the values with the values in the checksums.txt file.
12) The installation script also installs a bootstrap.dat file up to block 63545.

Instructions to use the headless command line daemon wallet:

1) The installation script creates an loco.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/loco and enter ./locod in a terminal window or at the command line to start the server
2) After the blockchain has been downloaded you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./locod eg. ./locod 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 ./locod encryptwallet <yourpassword>
5) Once you have the wallet running, blockchain downloaded and your wallet with coins on the Pi, then you can kickstart staking by executing ./locod walletpassphrase <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 Loco wallet installation script
Link to Qt wallet
Link to headless wallet
Link to virustotal scan for loco-qt
Link to virustotal scan for locod
Link to bootstrap.zip
Link to bootstrap.tar.gz
Link to checksums.txt

Loco address : 5vJRoKPpANz5oaiJJGrMQhnoNEwztDnKrh

2 nodes generated stakes close to each other and both claimed the stake. Looks like this happened to you twice. The network will accept one of each as the correct transaction. If it is yours it will turn into accepted and start to mature and the stake reward will be added to your balance. If the network rejects your transaction and accept the other node's transaction yours will turn into an orphan and you will get nothing. This means though that your coins will not lose its coin age and will generate another transaction very shortly in the next few blocks of approximately the same reward.

Ok good news about the explorer and bad news about the dev. That means lets wait for the dev to respond and take it from there.

I think lulworm is making one for the bounty that the dev has for this purpose.

It needs a block explorer first.

You have to know when to exit and when to enter. Feed the market when it is hungry and buy when it is full. The money making part of the coin's lifecycle is over. It now enters the phase where the dev/community actions including development etc. determines the future. Those with short term views made money during the scramble for coins in the hpos phases and now one has to take a longer term view and look at things like road maps etc.

If you did not make your money by now, you will have to wait it out longer term on the back of dev/ community actions and plans.

Read this

https://bitcointalk.org/index.php?topic=1410287.msg14509118#msg14509118

Steps:

1) You ideally wnat all your coins in one address - this is more of a housekeeping issue.
2) Enable coin control
3) Select all your coins and send to your own main receiving address ie. send them to yourself

All your coins will now be in one block and in one address and staking after they mature. Only do this combination once. When you get stakes, the coins that stake will be added to the reward and the result split in 2. Then you have 2 input blocks staking. Leave them like that to keep on splitting and stake independently for the reasons explained in my quote above. Only when the input blocks become small (maybe 20 or so) can you go back to step one and combine them in a number of sizable blocks. With 250 blocks for confirmation of newly minted coins, it is in the interest of the network if everyone has many smaller sized input blocks.

You can also run it on your Pi2.

Here are the Raspberry Pi wallets (headless and Qt) for GameBet v1.0.0.0 on Raspbian Jessie (v8) as well as a bootstrap.dat file. The wallet has been tested on both a Pi2 and Pi3.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2/3 (ARM) 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. NB! It is important that if you do a fresh install from a Jessie image, that you first expand your file system with raspi-config. It is the first option in the menu. The default image they provide installs a partition of about 3.5GB and it needs to be expanded to 8GB or you will not have enough space for the installation. It is furthermore always a good idea to select the boot options in raspi-config to boot to a command prompt with authentication. you can start the graphical desktop with "startx" manually. This helps with issues during upgrades.
3) The installation script installs the required dependencies automatically.
4) Installation directory where the binaries are installed is ~/opt/GameBet or /home/pi/opt/GameBet
5) To run the wallets after installation go to the directory with the wallets and run the wallet file - ./GameBetd for the headless wallet at the command line or click on the GameBet icon on the desktop or run the GameBet-qt wallet file.
6) An Internet connection is required for the installation
7) You need at least an 8GB memory card for the wallet.
8.) The installation itself takes about 30-45min on an out-of-the-box Pi.
9) You cannot just download the dynamic wallets, you have to run the script to get the dependencies as well else it will not run.
10) The installation script enables the ufw firewall by default, but does not force any special rules. The wallet still works this way with the port blocked. If however you want to enable it to become a fully functional node, uncomment the ufw lines in the script and add the ports you want open (default 7777 for GameBet) 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.
11) 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/GameBet folder and execute sha256sum <filename> and md5sum <filename> and compare the values with the values in the checksums.txt file.
12) The installation script also installs a bootstrap.dat file up to block 1665.

Instructions to use the headless command line daemon wallet:

1) The installation script creates an GameBet.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/GameBet and enter ./GameBetd in a terminal window or at the command line to start the server
2) After the blockchain has been downloaded you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./GameBetd eg. ./GameBetd 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 ./GameBetd encryptwallet <yourpassword>
5) Once you have the wallet running, blockchain downloaded and your wallet with coins on the Pi, then you can kickstart staking by executing ./GameBetd walletpassphrase <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 GameBet wallet installation script
Link to Qt wallet
Link to headless wallet
Link to virustotal scan for GameBetd
Link to virustotal scan for GameBet-qt
Link to bootstrap.zip
Link to bootstrap.tar.gz
Link to checksums.txt

GameBet address : GLGopwjmXEm4xNAo7XAQbsVBqp2VPk9roo

There is a big market for this type of thing and if the devs can get the business model and UI smooth and slick there is lots of potential.

It is surprisingly low at 6% on the Pi3.

The same principle applies in real life where shares trade cum-dividend closer to the dividend payout date. There is normally a last day of registration. The price increase as registration date gets closer to discount the dividend. It would be possible for example to sign a message on registration date and do a proof of ownership to a certain address. The price will then drop after the date to compensate for the exclusion of the payout.