[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]

[hamamana99]

On Cryptopia p&d goes usually as high as 150% but they choose coins which have released some kind of news ajd they try to attrack outsiders by tweeting in mass that info.Also they target coins which have a decent volume already, meaning there are potential buyers, something around 3-5 BTC. At the moment Magi does not qualify for any of these so I hardly see any p&d group to target Magi.

[starmman]

Starmman,

   A noob question, sorry.  Is the any advantage of me transfer my magi from my wallet to me Bittrex account? 

Hi,

to be honest I'm not sure - personally, I only keep as much XMG in Trex as I want to trade and the rest staking in my wallet as its more secure there.

if there are problems with the network, or you are on a forked chain its best not to transfer magi - I'm out of the country and away from my wallet so can't do any test transfers right now or see what the status is for me. I'm sure some others on here will know a bit more about whats going on

[starmman]

On Cryptopia p&d goes usually as high as 150% but they choose coins which have released some kind of news ajd they try to attrack outsiders by tweeting in mass that info.Also they target coins which have a decent volume already, meaning there are potential buyers, something around 3-5 BTC. At the moment Magi does not qualify for any of these so I hardly see any p&d group to target Magi.

Magi has been targeted many times in the past - but its never guaranteed

[ocminer]

Someone is currenty trying / doing an attack on magi and is orphaning most blocks..


Block 1739508 BlockTime=1523350623 CurrTime=1523350475 AdjustedTime=1523350469 vtx[0].nTime=1523350623
REORGANIZE
REORGANIZE: Disconnect 29 blocks; b0cc38999e9d3757aef0..00000000852978be6e6b
REORGANIZE: Connect 2 blocks; b0cc38999e9d3757aef0..a26929a0055867b4c06b

Attackers adresses are:

9LvDoEhev9aVgskEQNrqgnXTQVb6rnaP1m
9JfhHYNXt6fmAd3j46DNfMXvbCreBWf8DF

IPs:
37.48.118.9
2001:1af8:4700:a049:2::

amongst others.. from what I see


It's the same scheme like from the XVG attack, manipulated block times:

Block 1739558 BlockTime=1523351350 CurrTime=1523351385 AdjustedTime=1523351381 vtx[0].nTime=1523351350
SetBestChain: new best=000000000f64a1ff6b14d0616db2033638cf562fc21a282f2c58ec852bb38e21  height=1739558  money supply=8514885  trust=71525804620351  date=04/10/18 09:09:10
Stake checkpoint: 922fb2cf
ProcessBlock: ACCEPTED
received block 848061254478a01574c2
Block 1739557 BlockTime=1523351343 CurrTime=1523351386 AdjustedTime=1523351382 vtx[0].nTime=1523351343
REORGANIZE
REORGANIZE: Disconnect 2 blocks; 34fe3afe4d397df8cdbf..000000000f64a1ff6b14
REORGANIZE: Connect 1 blocks; 34fe3afe4d397df8cdbf..848061254478a01574c2
REORGANIZE: done
SetBestChain: new best=848061254478a01574c2424333d72d5b2c0bb80ae97148a0ca10e4a7366f9522  height=1739557  money supply=8514804  trust=71525824597721  date=04/10/18 09:09:03
Stake checkpoint: 6711efb7



More info:


received MALICIOUS block 000000001c7041bdb201
Block 1739603 BlockTime=1523354643 CurrTime=1523354654 AdjustedTime=1523354653 vtx[0].nTime=1523354643
SetBestChain: new best=000000001c7041bdb2010e43e36eeeddb7d3e8e4e3d1867a8c27c37fc1de8d79  height=1739603  money supply=8515121  trust=71526313044852  date=04/10/18 10:04:03
Stake checkpoint: 9d13fb8a
ProcessBlock: ACCEPTED
ocminer: block received from IP [2001:1af8:4700:a049:2::]:8233
ThreadRPCServer method=submitblock
Block 1739603 BlockTime=1523354644 CurrTime=1523354656 AdjustedTime=1523354655 vtx[0].nTime=1523354644
ProcessBlock: ACCEPTED
ThreadRPCServer method=getblock
received getdata for: block 000000001c7041bdb201


--
received VALID block 000000002a747490ce06
Block 1739604 BlockTime=1523354658 CurrTime=1523354692 AdjustedTime=1523354691 vtx[0].nTime=1523354658
SetBestChain: new best=000000002a747490ce069b9d0be21d9706dd2035a3bbfb4098b550d08055f7a8  height=1739604  money supply=8515133  trust=71526313068656  date=04/10/18 10:04:18
Stake checkpoint: a34da038
ProcessBlock: ACCEPTED
ocminer: block received from IP 213.5.36.33:52183
Flushed 15024 addresses to peers.dat  67ms
received getdata for: block 000000002a747490ce06
Flushing wallet.dat
Flushed wallet.dat 58ms
received getdata for: block 000000002a747490ce06



--
received MALICIOUS block 000000001a92c5bff0c8
Block 1739605 BlockTime=1523354620 CurrTime=1523354753 AdjustedTime=1523354752 vtx[0].nTime=1523354620
SetBestChain: new best=000000001a92c5bff0c8642fbfe0f8a5f4ab1e4dd9a35d9e804f66b055af5066  height=1739605  money supply=8515138  trust=71526313093414  date=04/10/18 10:03:40
Stake checkpoint: 7804d868
ProcessBlock: ACCEPTED
ocminer: block received from IP [2001:1af8:4700:a049:2::]:8233
received getdata for: block 000000001a92c5bff0c8
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 705ms




It looks like the attacker has several manipulated nodes which simpy exclude legit blocks and he overwrites them with his manipulated blocks. As long as he has the majority and enough hash, there's not much that I can do about it without getting the coin itself fixed... He is also sucessfull in lowering the difficulty on his chain, so the rewards on his blocks are > 40 XMG instead of the normal 8-11 XMG...

A pity..

Since this is still happening and the attackers is orphaning all pool blocks, I've stopped the pool until someone fixes it

[drgauravxmg]

Need help.

What does this mean :

EXCEPTION: St13runtime_error       
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

[edward0181]

Need help.

What does this mean :

EXCEPTION: St13runtime_error       
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

[edward0181]

Still looks like time hack indeed, same as we have had on PoW blocks in past.
Take it, once Joe is back, he'll adress same way as PoW was fixed.

Thnx!

[ocminer]

Still looks like time hack indeed, same as we have had on PoW blocks in past.
Take it, once Joe is back, he'll adress same way as PoW was fixed.

Thnx!

yep, it's exactly the same scheme like on XVG

[drgauravxmg]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

[earl3000]

....


It looks like the attacker has several manipulated nodes which simpy exclude legit blocks and he overwrites them with his manipulated blocks. As long as he has the majority and enough hash, there's not much that I can do about it without getting the coin itself fixed... He is also sucessfull in lowering the difficulty on his chain, so the rewards on his blocks are > 40 XMG instead of the normal 8-11 XMG...

A pity..

Since this is still happening and the attackers is orphaning all pool blocks, I've stopped the pool until someone fixes it

I completely understand, that you are backing out, but I think these attack happen, because people are backing out of mining, so attacks will get easier, since the NetworkHashrate is dropping.  
They are probably using rented hardware, so the first few attack might not be too profitable, but may be when the hashrate drops it might.

[111magic]

so is this the end for the coin?

Neuh...
Dev will find sollution, as he does always

this aint the first time? im just into the coin about 2 months now

Issues pop up from time to time and at least for Magi, they get fixed in a timely manner.

There was last an issue around the start of Janurary - fingers crossed that this one will not be so bad

Will be ok. More people should start staking. No panic Magi has experience with issues! It only makes the coin stronger!

[drgauravxmg]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

Any updates on this? The other Senior Members have probably overlooked my query. Could you please help?

Thank You!

[edward0181]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

Any updates on this? The other Senior Members have probably overlooked my query. Could you please help?

Thank You!

If you've deleted and restarted magi, then debug logs willl fill again.
Please show contents of debug.log here, so we can see.

Thanks

[drgauravxmg]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

Any updates on this? The other Senior Members have probably overlooked my query. Could you please help?

Thank You!

If you've deleted and restarted magi, then debug logs willl fill again.
Please show contents of debug.log here, so we can see.

Thanks

Thank You So Much for the prompt reponse.
Now since that it has stuck, it doesn't come up with the error that I marked in RED in my earlier post.
It is simply stuck at 88 days ago.

I have exited MAGI Client and have uploaded the db.log and debug.log to google drive. Please check if I have managed to grant proper permissions for you to have a look at it. I think it to be better to share the link rather than copy-paste the full debug.log.

Thank You.

Here is the link :
db.log : https://drive.google.com/open?id=1MBT4VYD7rKEaorAuvqLw_ppR5n_EBjUt
debug.log : https://drive.google.com/open?id=1yMZyJOGgM5vQ-lfQM5pbMWKHZaeCHrG6

[lilaj4de]

Does it exist or does any company use MAGI as a payment processor? Could you tell which companies  accept?

[magiboi]

all my workers are on minerclaim.net now

since supr stopped

something fishy is happening with the network hashrate

https://poolinfo.systms.org/

[starmman]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

Any updates on this? The other Senior Members have probably overlooked my query. Could you please help?

Thank You!

Hi, sorry - didn't notice your message - did you try checkwallet and repairwallet in the console?

[drgauravxmg]

Need help.

What does this mean :

EXCEPTION: St13runtime_error      
CDB() : can't open database file wallet.dat, error -30974

I have been trying to re sync the chain from the uploaded file at m-core.org. I have my wallet backed up. I pasted it on my newly downloaded blockchain folder right where it has to be. But still I get this error.

Would really appreciate the help.

Thank You!

does wallet.dat has read-write rights?
What is in your debug.log and db.log (first clear them and restart magi core) then copy past log files here.

wallet.dat has no such locked READ and WRITE Attributes.
I have deleted the debug.log and db.log restarted the Magi Core. It is stuck at 88days ago. There are active connections.

No help, it has been more than an hour now.

Any updates on this? The other Senior Members have probably overlooked my query. Could you please help?

Thank You!

Hi, sorry - didn't notice your message - did you try checkwallet and repairwallet in the console?

Yes. No errors there either.

Please also check the debug.log and db.log posted a few posts earlier.

Thank You!

[tazzz013]

So I guess my question is, are we still o.k. to be mining right now?

[flippintwit]

So I guess my question is, are we still o.k. to be mining right now?

I am, all 78 KH/s that I have and staking all 15 coin that I have.  ( I've only been working Magi a month or so.)