I just submitted a maintenance request for Magi on Yobit and pointed to the new wallet source - hopefully this will resolve issues with deposits/withdrawls in 1-2 weeks, but we'll see.

From looking at the commits:

• Added lightsplasher's total balance display
• Fixed automatic wallet update notifications
• Migrated to LevelDB for transaction storage
• Updated checks for PoS blocks
• Updated checkpoint syncing, hopefully eliminating the "checkpoint too old" bug
• Added automatic coin stack merging/splitting (as far as I can tell)

Feel free to shoot me a PM if you need help setting up the automatic update checking with the official site. I'm also not opposed to hosting the update text file in the interim for you guys if that will help.

Also, I was planning on adding the following as a pull request some time ago, but life shifted a bit for me and I haven't found the time to do work on it. Here's a link to PayCoin's (sort of hack-y) solution to the "Checkpoint is too old" problem: https://github.com/PaycoinFoundation/paycoin/pull/33. It basically just took out the check for checkpoint age, which is sort of a grey area... but it would definitely calm down the panic about the error popping up in the wallet.

Thanks for bringing this up to me via PM, utahjohn.

I originally said that whatever returned after using uname -a was fine because we were talking about Raspberry Pis (1 and 2) and the makefile supports both armv6l and armv7l (which are actually identical). It's just not working with any of the previous architecture commands because of the 64-bit OS (see below).


It looks like you guys in the thread have already figured it out: someone will need to write a scrypt-aarch64.S file for everything to work smoothly.

Alternatively, I could probably have the wallet fall back to a C++ implementation on unsupported architectures. It would just need to be transparent to the users that their architecture does not perform as well as it might with its own assembly implementation. (That is to say that the performance would be really bad compared to a native solution.)

Speaking of performance hits, though, I'm pretty sure one could the ARM version of QEMU to run a 32-bit binary if you just want to run the wallet on an arm64 board. At least until a more robust solution is found. A guide for setting QEMU up on a Raspberry Pi can be found here, but I'm not sure how well that translates to ODROID's boards. You might have to set up ODROID's boards for virtualization (if they support it) and compile QEMU yourself to get things working.

It is still worth using, without a doubt. I assume it hasn't been updated since September because it's stable and there haven't been too many features requested.

The reward function is explained in the "Magi-Reward-V2" and "Necessary to adjust miner efficiency?" sections of this post. If you want a graph of any block's possible rewards based on average hashrate (and block difficulty), you can use the following site to play with the parameters: http://starflakenights.net/crypto/blockreward/xmg.html.

1. See first post
2. See first post and my initial reply

Hints: mature coins can be spent; reward means reward; interest rate also means reward

Ah, yeah, I should have made sure that make all built the libraries and the tests, rather than just the tests.

That being said, is Qt Creator linking the leveldb and boost libraries properly? I've never used Qt Creator because command line compilation is just: qmake && make . But, from your pastebin, it looks like it can't find leveldb or boost... so perhaps making sure Qt Creator knows where the libraries are is the answer.

First post:

Block rewards depend on network hashrate as well as the current block number. You can look at a graph here to get an idea of the reward scheme: http://starflakenights.net/crypto/blockreward/xmg.html.

Because leveldb is part of the sources.

To answer the original question, it looks like QT Creator isn't compiling leveldb for you, so it's probably easiest to pop open your terminal, navigate to vertcoin/src/leveldb, and run a make all.

You do realize that all those links, except the post about recent withdrawl issues, are about events from 1-2 years ago, right? Just file a support ticket if you haven't already and they will probably get back to you in a day or so.

Are you asking why such a large hashrate is producing so few coins?

The block reward adjusts according to the network hashrate, rising to a certain point, then quickly dropping if the hashrate gets too high. You can check out a plot of the block reward function on this site. Just keep in mind that the reward calculation is based on the hashrate over time, not the instantaneous hashrate.

Basically, Bootstrap.dat allows you to import a portion of the blockchain incredibly quickly by bypassing the peer downloading requirement. It's essentially identical to someone posting their copy of the blockchain for you to download. When all the blocks are "bootstrapped" in, your client continues downloading blocks (newer than those in the bootstrap file) from peers as it normally would.

For a slightly more in-depth explanation, here's the Litecoin wiki page for Bootstrap.dat.

Joe,

There's actually an issue with retrieving the version.txt file that's up on coinmagi.org - it's inaccessible via the Qt curl method because of the mod_security permissions for the server. Instead of sending the version information, the site spits back an HTML-based error message. The error is detailed in the latter half of a new pull request.

The other half of the pull request makes version checking a little more robust. Since it wasn't immediately obvious to me why the client wasn't reporting that a new version was available, I figured I might as well tidy up some loose ends in the code. Previously, significantly lower program versions could trigger the Update warning.

--

If you want to test the success of the version.txt retrieval, I also added a console printout in src/qt/updatecheck.cpp (line 40) for debugging. If the mod_security problem ends up giving you trouble, uncommenting that line as well as the iostream include on line 6 enables the printouts.

It appears that the issue can probably be resolved by adding a few lines to ./.htaccess on the server, but that might not be ideal. I'm not entirely sure what the mod_security filtering does, but it might be important.

Edit: You can also use http://starflakenights.net/crypto/magiversion/version.txt for an example of what should be going on. Not sure why my web space is more permissive than the official site. Changing the retrieval URL in the code makes everything work as intended.

According to their thread:

I feel like this would appeal to a fairly small market. In my mind, dolls and clothing and whatnot work out for established brands because they are based on an already popular franchise (as you see with TV/movie -> toy/game/clothing line transitions). Coming into it with just the idea that it exists is probably not going to bring in any significant income.

So... If you want to make something out of your idea, I would suggest creating enjoyable content and publicizing that before monetizing it.

There are source links on the download page. As I recall, the project was originally closed-source, but the author open-sourced it to give back to the community.

The Sweet Spot Miner (Official Magi site mirror, out of date) is a program (written in Delphi, I think?) that manages your hashing power (so you don't waste energy mining when the rewards are low). From the link above:

And here's a screenshot of the interface, if you're curious:

Since no one has given more helpful advice, have you tried the "Run as Administrator" option from the context (right-click) menu?

Actually, the site is reporting version 1.2.3.0. Maybe the issue with checkpoints isn't actually fixed?

Edit: here's a blurb from the HoboNickels Troubleshooting Guide