I am sure you have heard it previously - size does not matter  

The correct question to ask is to post the output of a one-way hash function of the binary. On linux that would be the output of eg. sha256sum Loco-qt.
This can be compared the one-way hash output of the official binary. In addition, when a file is uploaded to www.virustotal.com it automatically calculates a one-way hash of the file and this hash also needs to correspond to the binary on your system and completes the triad. You can get the sha256 hash on virustotal at the top part of the screen where the results are displayed or in the URL to the scan result.

The reason for this is that if one-way hash outputs are the same, it means that the binary has maintained its integrity and no unauthorized changes were made to the file. The addition of code, malicious or not (even if it is just one bit) will give a completely different one-way hash output. Comparing size of a file gives a false sense of assurance.

A quick hack on your Ubuntu is to execute sudo cp /usr/local/lib/libsecp* /usr/lib then run ./locod again. Maybe it will work on the Mint as well.

Your binary is dynamically compiled and it cannot find the libsecp256k1 dependencies. You have one of 3 options:

1. Do the quick hack above and copy the dependencies from where it was installed to a generic default library
2. Create a path to where the libraries can be found
3. Compile the binary statically. You can do this with sudo make STATIC=1 -f makefile.unix. The required libraries will then be coded into the binary and it will not look for them during run-time. The file becomes roughly double in size.

Is your Ubuntu 14.04 64 bit or 32 bit?

PS: Have you changed the permissions on the build_detect_platform file? You have to go to yoursourcelocation/Loco/src/leveldb and execute sudo chmod +x build_detect_platform. After this try to build again.

What version of Linux do you use?

Wallet works fine on the Pi. Stakes mature after 200 as per design. No wallet issues so far.

PS: Guys cut Nightz some slack. From my interactions with him so far he is not the type of person that screws people over. Everyone should just take a chill pill, sit back, relax and wait for him to get his personal issues sorted. That is not too much to ask.

Philakone, carry on with your feedback you are doing great. Put on your thick skin. This project is all about delivering a polished product. You can agree with the dev what is the best channel is for providing feedback whether here of offline. Agree that with the dev but do keep on testing and highlighting issues.

Guys, unless the points made are not valid, instead of taking on Phil, rather thank him for raising the issues. Posting it here is good for transparency and accountability. Imagine the issues being picked up only later when the site is loaded. Let the devs fix the issues and let Phil identify more bugs to be fixed.

Think big picture and dont get blinded by looking at the short term.

Phil has a valid point like all the other points he made. The site has to cater for its customer and it is a reasonable request to have all the available info on a match at the user's fingertips satisfying the assertions of accuracy, validity, completeness and timeliness as this is what makes one site stand out from the rest. It is possible for a user to view info elsewhere and then come back to take a position. However, that wastes valuable minutes and seconds. These seconds do not matter to casual users, but they make all the difference to professional users. Wasted seconds means inconvenience to users and seconds lost means revenue lost and added up becomes a sizable amount of lost revenue. A site owner must maximize the time a user actively uses a site in order to maximize revenue. I am sure that over time the teething issues will be sorted out by the dev and people like Phil are in effect doing 100% testing and represents a professional user. Phil's requirements are therefore representative of the requirements of a professional user. Make Phil happy and you will make the majority of professional users that the dev is aiming to pull in happy.

Give him a few more days, maybe a week or so.

You must read the transcripts of the Discord dev update discussion of yesterday.

Not sure how formal or in what format the principle will be applied here but

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

Another country coin. Why would that country want a virtual coin?

In Africa terms, you a playing with the lions balls to have a staking coin with only 1500 coins. If 50% is on an exchange, 25% dont care and 25% does stake, it will take ages for fractions of coins to mature and you will have endless problems getting the chain to move. All you need to create the perfect cluster**** is to add 200 block reward maturity. You should increase the coin total significantly.

Unless your reference to ISH (Imaginary Stake Holding) means that the whole thing lives in people's imagination and the coins are chased by big flying elephants with wings while you take the next puff...  

All windows builds are flawed. The only builds that work are ones that was built on Linux from source. In turn, only certain Linux builds gets past block 192131. It takes about 2-3 days to get to block 192131 even if imported from a bootstrap.dat. What-if analysis therefor takes a long time and days at a time. The only combination I have found to work is Ubuntu 14.04 32 bit. There might be others but the effort to find more is not worth it. A flawed build will stop at block 192131 even if you feed it a bootstrap of block >700k.

It is just not feasible to save this coin. It is better to start a new coin and chain with this coins features. Unless of course you get a developer to review the code and fix the problem.

Unless C-CEX gets ther chain up to date the coins there are useless. Furthermore, I doubt that the effort and resources required by C-CEX to get the chain up to date is worth the effort. I think what will happen is a delisting based in a broken chain and all coins in exchange wallets will be gone.

I got a Pi wallet as well.

All wallets get stuck on block 192131 even with a bootstrap.dat that is further in the chain and dev is gone.

The only combination that gets past this block is Ubuntu 14.04 32 bit with a compile from the github (not the zip file in other links) and following instructions to the letter.

Unfortunately, with the issues on the chain the coin is dead as a doornail. Move on.

It is a pity because the time for dev involvement is in the next few weeks. Loco started with a high distribution compared to the coming hipos % so final money supply will be high. In one month on autopilot over hipos period might kill the coin.

All the best sorting your issues.

Facts are facts and can be delivered sugar coated or not. Nothing wrong with delivering without the sugar coating. The devs must just fix it asap to customers demands.

Business management 101

Ok that makes sense. secp256k1 can be a difficult candidate.