Author

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

newbie
Activity: 5
Merit: 0
either  0.2 XMG  , long enough in Crypto im out there Wink

What pool is working ?? I tried many, but today they all stopped!   Sad Sad

Here is my pool:

http://crypto.ngrok.majed.pro:9999/site/gomining?algo=m7m

username:root
password:toor

min Payout is now 1.5 XMG

hey dude, is there a tutorial how to set up an own yiimp magicoin pool for private use?
yiimp is here https://github.com/tpruvot/yiimp
, but still need to somehow implement the magi wallet/pool into it??
legendary
Activity: 1750
Merit: 1005
My wallet (running over a rpi3) is getting connection timeout issues during this morning, I don't know why because the internet connection is running fine. May it be related with the issue? I'm using the 1.4.5.1 version.

If I want to update it to 1.4.5.2 (or another release) the procedure will be (just asking for confirmation).

Stop current wallet
Backup the wallet.dat file.
Compile new wallet
Run new wallet with the same wallet.dat file.

Is this correct? should I remove the blockchain folder and sync it again? or could I use the same data? It takes hours to full sync.

Minning on Minerclaim is activated? It's not clear based on the messages shown on their site but I'm still getting connection refused messages both using xmg.minerclaim.net or eu1.minerclaim.net urls (don't know exactly which is the right one).


Best thing is hold your actions & wait for new info
full member
Activity: 378
Merit: 101
W10x64

Magi version v1.4.5.2 ()
Using OpenSSL version OpenSSL 1.0.2j  26 Sep 2016
Startup time: 01/06/18 09:59:03


************************
EXCEPTION: 12bignum_error      
CBigNum::operator/ : BN_div failed      
C:\Wallets\Magi-qt\m-wallet.exe in ThreadStakeMiner()      


What to do ?
It worked on the old version.

UPD:

Delele ALL dir (blocks,database) all works.
newbie
Activity: 13
Merit: 0
My wallet (running over a rpi3) is getting connection timeout issues during this morning, I don't know why because the internet connection is running fine. May it be related with the issue? I'm using the 1.4.5.1 version.

If I want to update it to 1.4.5.2 (or another release) the procedure will be (just asking for confirmation).

Stop current wallet
Backup the wallet.dat file.
Compile new wallet
Run new wallet with the same wallet.dat file.

Is this correct? should I remove the blockchain folder and sync it again? or could I use the same data? It takes hours to full sync.

Minning on Minerclaim is activated? It's not clear based on the messages shown on their site but I'm still getting connection refused messages both using xmg.minerclaim.net or eu1.minerclaim.net urls (don't know exactly which is the right one).

newbie
Activity: 93
Merit: 0
Update: Magi find the issue & is working on fix!
More info asap!

my wallet crashed than i open it again locked withought staking and i got one stake 7 hours in future 0.000687....xmgs  

should we close our wallets and wait for the fix or leave it running ?
jr. member
Activity: 44
Merit: 1
My wallet in Ubuntu is working without any issue.

PS: I realized why. Even if posii=1 is not stacking because not enough weight.
legendary
Activity: 1750
Merit: 1005
Update: Magi find the issue & is working on fix!
More info asap!
hero member
Activity: 712
Merit: 500
YoBit still has not updated their wallet... I'm losing my time with them and no replies from support. Not gonna use that exchange in the future.
member
Activity: 137
Merit: 10
Hi,
since today morning i get this with my wallet:
https://imgur.com/a/yNnIU


Read back the last couple pages, crashing when staking, don't stake right now and it will run.

Thanks.
now it runs.
newbie
Activity: 18
Merit: 0
Hi,
since today morning i get this with my wallet:
https://imgur.com/a/yNnIU


Read back the last couple pages, crashing when staking, don't stake right now and it will run.
member
Activity: 137
Merit: 10
Hi,
since today morning i get this with my wallet:
https://imgur.com/a/yNnIU
member
Activity: 150
Merit: 11
Little update: Magi passed Hardfork blocknumber succesful. But there is still work in progress. Magi will keep you informed here!
So will we still keep getting a lot of orphaned blocks? checked my pool this morning and it's hitting blocks often just 50% of them are being orphaned even after hardfork, will the orphan rate of blocks slow down soon or is more work needed?
legendary
Activity: 1750
Merit: 1005
Little update: Magi passed Hardfork blocknumber succesful. But there is still work in progress. Magi will keep you informed here!
legendary
Activity: 2688
Merit: 1240
I already have:

error: {"code":-1,"message":"CBigNum::operator/ : BN_div failed"}
newbie
Activity: 16
Merit: 0
The pool was private! just fixed minimum payout for XMG .. 1.5 XMG is more reasonable!

Cheers!

and make the payout hourly too Smiley

Payouts are made automatically every 2 hours for all balances above 1.5, or 0.15 on Sunday.
newbie
Activity: 3
Merit: 0
Same here with Mac OS X and Wallet 1.4.5.1.
It worked well until this morning when syncing to the post-hardfork-ed new blocks

Best.


My Wallet crashes when activating Pos in Windows , with such a failure (application closed due to MSV...dll failure.

Client version 1.4.5.1
synced succesfully

but wont work
newbie
Activity: 109
Merit: 0
The pool was private! just fixed minimum payout for XMG .. 1.5 XMG is more reasonable!

Cheers!

and make the payout hourly too Smiley
newbie
Activity: 15
Merit: 0
this is the message block 1606987 is giving
Block 1606987 BlockTime=1515220020 CurrTime=1515220024 AdjustedTime=1515220023 vtx[0].nTime=1515219952

**
EXCEPTION: 12bignum_error
CBigNum::operator/ : BN_div failed
Magi in ProcessMessages()

ProcessMessage(block, 265 bytes) FAILED

hope it helps
Exactly the same problem. I tried Debian 8/9, Win x86, all go to crash. No matter the binary I take, or compile by myself (compile only on Debian 8 ). Win x64 seems not crash, but also not sync.
Wallet 1.4.5.2
can you try build from source after apply this commit https://github.com/filoozom/magi/commit/2ffa778bf7be59a4da76bd1d56b77a133ce795ef ?
Code:
just cd to magi folder
wget https://github.com/filoozom/magi/commit/2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch
git apply 2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch
Thanks for commit, but nothing changed, The same result
Code:
************************
EXCEPTION: 12bignum_error       
CBigNum::operator/ : BN_div failed       
Magi in ThreadStakeMiner() 
Update:
've disabled stacking, magi seems get run, but something still wrong with block 1606987 , wallet not syncing
newbie
Activity: 3
Merit: 0
this is the message block 1606987 is giving
Block 1606987 BlockTime=1515220020 CurrTime=1515220024 AdjustedTime=1515220023 vtx[0].nTime=1515219952

**
EXCEPTION: 12bignum_error
CBigNum::operator/ : BN_div failed
Magi in ProcessMessages()

ProcessMessage(block, 265 bytes) FAILED

hope it helps
Exactly the same problem. I tried Debian 8/9, Win x86, all go to crash. No matter the binary I take, or compile by myself (compile only on Debian 8 ). Win x64 seems not crash, but also not sync.
Wallet 1.4.5.2
can you try build from source after apply this commit https://github.com/filoozom/magi/commit/2ffa778bf7be59a4da76bd1d56b77a133ce795ef ?
Code:
just cd to magi folder
wget https://github.com/filoozom/magi/commit/2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch
git apply 2ffa778bf7be59a4da76bd1d56b77a133ce795ef.patch
newbie
Activity: 15
Merit: 0
this is the message block 1606987 is giving
Block 1606987 BlockTime=1515220020 CurrTime=1515220024 AdjustedTime=1515220023 vtx[0].nTime=1515219952

**
EXCEPTION: 12bignum_error
CBigNum::operator/ : BN_div failed
Magi in ProcessMessages()

ProcessMessage(block, 265 bytes) FAILED

hope it helps
Exactly the same problem. I tried Debian 8/9, Win x86, all go to crash. No matter the binary I take, or compile by myself (compile only on Debian 8 ). Win x64 seems not crash, but also not sync.
Wallet 1.4.5.2
Jump to: