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

[Vitalik_Pedik]

I've updated a windows version here if one wants to test the testnet: https://m-core.org/bin/m-wallet-1.4.6.3-test/m-wallet-1.4.6.3-test.zip

We'll make out a fix to the issue by a new version soon (about weekend I expect).

I apologize for some extra days needed to do some extended tests.

Stop doing splitting on REAL chain, or say truth that it is your actions.

[1714932852]

1714932852

[icecoin2000]

Hello everyone,

Just got on the bandwagoon for Magi the last week, which seem to have been a bad week to join up on.

Strange behaviours with missing transactions,  faulty transactions,  hard forks,  strange levels of rewards,  several mining pools with different netblocks, talks about attack on the magi network.
So much drama on this thread,  yet litte information on whats going on.

I have some questions,  I'm mining on pom.m-hash with what I assume is the normal chain (not test), I like the idea of limit but it turns out there is actually noone enforceing it given the fact ppl mining at higher levels.

The network seem to go bananas sometimes with rewards up to 40xmg/block and even if they get confirmed,  the payout look like its confirmed,  but the actual transaction is invalid. 
What is the cause of these reward spikes and did they result in a hard fork of the chain?  What causes these invalid transactions when looking at it?

Sample 1) confirmed transaction in pool,  invalid transaction at chainx  (https://chainz.cryptoid.info/xmg/tx.dws?a4a24a491dde695e0fa415bfe3671ec6a40503662e42192348b5d8e266e623aa)
is this the hard fork ppl talk about last night?

Sample 2),   confirmed transaction in the pool,  valid transaction at chainz,  but my address is not there hence no payout.
https://chainz.cryptoid.info/xmg/tx.dws?1ec0e5ecab4a0bad3a72248f6c0d591ad8b9474823b5b322f36f00506bd61cfb


And yes,  I have tried checkwallet,  repairwallet

[Jeremy450]

Whos got the lastest blockchain database having major issues updating wallet from 1822476 and have tried just using devs node only.

[edward0181]

Whos got the lastest blockchain database having major issues updating wallet from 1822476 and have tried just using devs node only.

stuck also on 2 servers.
main laptop running correct, but linux servers all stuck at 2476

[starmman]

I've updated a windows version here if one wants to test the testnet: https://m-core.org/bin/m-wallet-1.4.6.3-test/m-wallet-1.4.6.3-test.zip

We'll make out a fix to the issue by a new version soon (about weekend I expect).

I apologize for some extra days needed to do some extended tests.

Better to be safe - hope the testing goes well!

[tommyrsk]

So which nodes should i had to .conf?

should aready be in the config file

you might have to delete the block chain and download the one a page or so back

edit: try close and reopening your wallet. i did it to mien and my is catching up the 100 or so blocks its behind on.

http://jemisp.com/wallet2.png

I have this ones:

addnode=104.128.225.215
addnode=45.35.251.73

They are correct?

On TrasMaMod we do only keep connection to 104.128.225.215

Code:

connect=104.128.225.215
listen=0

[Vitalik_Pedik]

TrasMaMod clever, do like TrasMaMod)

[xpoolx]

So which nodes should i had to .conf?

should aready be in the config file

you might have to delete the block chain and download the one a page or so back

edit: try close and reopening your wallet. i did it to mien and my is catching up the 100 or so blocks its behind on.

I have this ones:

addnode=104.128.225.215
addnode=45.35.251.73

They are correct?

On TrasMaMod we do only keep connection to 104.128.225.215

Code:

connect=104.128.225.215
listen=0

Im trying with this params since days but i cannot connext to the devs node

[Vitalik_Pedik]

104.128.225.215 node also have random (or not random) blocking ip, so try different ip

[Vitalik_Pedik]

In current mod of 104.128.225.215 node, if someone who succesfuly connected to it will mine POS block, it will be split, so be sure that your POS mining is off
More interesting thing is why Joe not say about it? Is this a part of top secret experiment)?
So, you are all members of his experiment)

https://media.giphy.com/media/qjfeT5XdAirCg/giphy.gif

[tommyrsk]

104.128.225.215 node also have random (or not random) blocking ip, so try different ip

And that could happend if you have some others connect=, addnode= and listen=1 and you are "leaded" into a fork.. Then the 104.128.225.215 will disconnect you. And if Joe hasn't changed the default settings, it means that you (on same IP-address) will be blocked for at 24h (60*60*24 = 86400) that is the default bantime.

Ensure to have only the connect=104.128.225.215 and listen=0 in the config file (remove all other addnode and connect).
To solve it from beeing on a fork/banned, you have to remove the folders "blocks/", "database/" and "peers.dat". Download the blockchain earlier published by Joe and ekstract blocks and database folder from it. Then get a new IP-adress (restart maybee your modem for internet-connection) OR wait for 24h...
Then the block-chain will get in sync with devs node.

[xpoolx]

In current mod of 104.128.225.215 node, if someone who succesfuly connected to it will mine POS block, it will be split, so be sure that your POS mining is off
More interesting thing is why Joe not say about it? Is this a part of top secret experiment)?

[Vitalik_Pedik]

104.128.225.215 node also have random (or not random) blocking ip, so try different ip

And that could happend if you have some others connect=, addnode= and listen=1 and you are "leaded" into a fork.. Then the 104.128.225.215 will disconnect you. And if Joe hasn't changed the default settings, it means that you (on same IP-address) will be blocked for at 24h (60*60*24 = 86400) that is the default bantime.

Ensure to have only the connect=104.128.225.215 and listen=0 in the config file (remove all other addnode and connect).
To solve it from beeing on a fork/banned, you have to remove the folders "blocks/", "database/" and "peers.dat". Download the blockchain earlier published by Joe and ekstract blocks and database folder from it. Then get a new IP-adress (restart maybee your modem for internet-connection) OR wait for 24h...
Then the block-chain will get in sync with devs node.

I investigated that those ip bans not linked with "leading into a fork" reason. They are permanent.

[DisasterFaster]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

[Vitalik_Pedik]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

[tommyrsk]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

The latest official is:

Blockchain snapshot as follows:

https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz

The TrasMaMod is synced up according to this one.

[DisasterFaster]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

[Vitalik_Pedik]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

[DisasterFaster]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

Thanks!

On another note has the dev provided any technical explanation of what caused this latest issue? Is there only 1 dev on this coin now?

[Jeremy450]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

Thanks!

On another note has the dev provided any technical explanation of what caused this latest issue? Is there only 1 dev on this coin now?

page or so back he replied to me and said he knows of the issues and is working on it.

i got a reply from joe. I hope this doesnt get me in trouble.

Hi Jeremy,

I'm very aware of the issue, and trying to make out fixes (hard fork). It was happening on the PoS; unfortunately I've to have extended days; I'll keep posted.

-Joe

Happy to do a screenshot to prove its from joe.