Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 372. (Read 2375631 times)

Yes, trying on the diff adjustment that would be ideal as solution in part to the issue.

Yes, it's on a test, no touch of the main chain. Once we confirm no forks, we'll migrate to main chain.

i lost more tan 700, and i cant see my historic transactions, you clean the Database ?
how can i get my coins back ?

Correct,
isn't working yet

PoW blocks are coming in, but that wallet I helped you to compile is only for testing and not stable?

Already 18 minutes no pow blocks found...

Good news about the test build - I'll update cryptopia, they'll wan't know an ETA of live - is there a rough estimate?

No worries, glad to help out

Worked like a charm, many thanks.

Is this still where we are?

Why not a diff adjustment like DigiShield or DGW (Dark Gravity Wave), everything slows down as hashrate rises, a vice versa, and let it be?

Especially if we're talking about a botnet! 

Indeed, the limit would punish everyone just because a few people would be mining with their botnets. A few botnets or farms start mining, the limit is reached, PoW is disabled, the smaller miners are prevented from mining. This idea gives control to the botnets.

Thanks for the test update !

Correct, that is only for testing.

This is just for testing, right? The main chain still operates with the "old" rules (plain v1.4.3)...

Great info. Many thanks

I Get that too but on Manjaro dist. If you really want to compile but get bugnum errors like these.

This is how I fixed it, I compiled a standalone OpenSSL that works besides the systems Openssl libs

This is only for when you compile m-wallet and on a linux system
If you do not feel comfortable doing these steps, don't do it.
I make no guarantee that this will work and / or not break your system, use caution.

This is for Linux only

Goto https://www.openssl.org/source/ and download openssl-1.0.2l.tar.gz
Extract the files from the tar.gz

Configure OpenSSL with the following
I'm using the path /opt/openssl-1.0.2l as the example here (Also the same on how I installed it on my system)

--prefix and --openssldir needs to be the same location, you can change location as you wish but I recommend that you place it where you can find  easy it and where it will not overwrite systems OpenSSL (Caution! Overwrite system OpenSSL might break the system)

After the config is complete you need to compile and test it with the folloing commands

When that's completed we need to install it to the directory that you configured with --prefix

After that is completed you can verify it with this command
And you should see something like this

Now that you have a nice standalone version of Openssl besides you now you need to tell qmake to user this version of OpenSSL instead of system default

Then it's time to compile the wallet, I'm using Qt5 and qmake-qt5 in this example

And after that you should have a nice compiled version of m-wallet with openssl-1.0.2l instead of the system default

Thank you for the update Joe. Happy that the forking problem is solved. If the test is going well can we expect for a release early next week?

For whatever reason, I just can't compile it on Ubuntu 16... downgraded to Openssl1.0.2g but always fails on bignum errors...
Will await build versions and just extract.

Thanks Joe for all work.

Sounds great! Can't wait to test it out. Already compiled the test wallet