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

[Vitalik_Pedik]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

My suggestions
1. Hardcode main pools (need list) to be guarantors of the chain (not forever).
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system with emulation of attack (several times)
4. Remove hardcoded pools.

[seeksilence]

It seems that my magi.conf file still works. My pool http://104.207.149.217  has the same block number with https://poolinfo.systms.org/. And the Net Hashrate is only 13,520.47 KH/s .

The recently found block:

1447973   119 left   lervito           08/20/2017 00:56:41   0.6509   43.25   42,661   15,464   36.25
1447970   116 left   anonymous   08/20/2017 00:24:22   1.0152   43.25   66,530   69,884   105.04

Rewards at 43.25. Not sure if it is correct or not. Take your own risk to mine.

[frphm]

Folks - this newbie account ~ Vitalik_Pedik~  has only posts on this thread

just sayin, he showed up when the problems showed up

Excuse you, I signed up here when the problem started too, so that I could stay informed as to what the solution was. Doesn't mean I did it. Don't start throwing around baseless accusations.

[orcanice]

Seems like the problem is getting solved... hashrate just jumped alot.

[Myth888]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

Edit: You can use the block date from here to catch up http://coinmagi.org/bin/block-chain/

Place connect=104.128.225.215 in magi.conf, or

magid -connect=104.128.225.215

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

force the next update to only accept solo mining and not accept connections outside and incorporate a miner in the wallet. Or incorporate a control in the node itself to reject too many mining connections.

[Lightsplasher]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

Edit: You can use the block date from here to catch up http://coinmagi.org/bin/block-chain/

Place connect=104.128.225.215 in magi.conf, or

magid -connect=104.128.225.215

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

I think the problem maybe caused by flash mining by big miners.  I've seen this before on another coin.  The solution was to hard fork into a proof of stake only coin.  Unfortunately this happened after after several months of struggle and the community was so fractured by problems with forks that all of the exchanges and support was lost.  The coin did run well with no forks at that point but it is gone now.

My suggestion is to go to a proof of stake only coin with a reasonable coin block cap.  Interest rate should be high enough to supply some liquidity with a coin cap to prevent too high an inflation rate in the long term.  Once things settle down for a while perhaps we can think of adding PoW back in some better form.

[TheKingInYellow]

Just now realized the big issue here. So what's the deal with the wallet? Will this be fixed anytime soon? I deleted my chain and redownloaded the blockchain and now it says I have less coins than I used to have even 6 months ago. What gives?

Kinda sucks to see my magi pop away like that.. I've been in since 1900 sat.

[Myth888]

Im trying to learn how to mine solo while this is going on. I need a little help though. I can mine with this pc where my wallet is but how do i connect to this pc wallet with another pc?

[Redrover]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

Edit: You can use the block date from here to catch up http://coinmagi.org/bin/block-chain/

Place connect=104.128.225.215 in magi.conf, or

magid -connect=104.128.225.215

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

I think the problem maybe caused by flash mining by big miners.  I've seen this before on another coin.  The solution was to hard fork into a proof of stake only coin.  Unfortunately this happened after after several months of struggle and the community was so fractured by problems with forks that all of the exchanges and support was lost.  The coin did run well with no forks at that point but it is gone now.

My suggestion is to go to a proof of stake only coin with a reasonable coin block cap.  Interest rate should be high enough to supply some liquidity with a coin cap to prevent too high an inflation rate in the long term.  Once things settle down for a while perhaps we can think of adding PoW back in some better form.

I tend to agree with what Lightsplasher is saying but is there a way to still have both?
What about significantly reducing PoW and significantly increasing PoS to the point that PoS is securing the network?

This would have the benefit of encouraging saving and staking for interest and still nearly everyone with a computer and wallet could continue to participate in magi.

Another plus side to this would be even less energy use with staking compared to cpu mining.

Or... What about PoS on a mobile wallet, is it feasible?  If it is, this could become a great asset when combined with MagiPay.  Think about it, most everyone has a cell phone now.  Wouldn't it be awesome to have the option to be able to do everything 'Magi' with the cell phone and no longer require a pc?

[Myth888]

Just now realized the big issue here. So what's the deal with the wallet? Will this be fixed anytime soon? I deleted my chain and redownloaded the blockchain and now it says I have less coins than I used to have even 6 months ago. What gives?

Kinda sucks to see my magi pop away like that.. I've been in since 1900 sat.

try to backup your wallet then type in the command repairwallet in console

[joelao95]

Blockchain data is here (block #1447972):

http://coinmagi.org/bin/block-chain/

Wallet version 1.4.1.1 is fine:

http://coinmagi.org/bin/m-wallet-1.4.1.1/
https://github.com/magi-project/magi/releases

The following pools are currently on, pls join mining:

https://www.zpool.ca

http://104.207.149.217/

Will update when more pools up.

[TheKingInYellow]

Blockchain data is here (block #1447972):

http://coinmagi.org/bin/block-chain/

Wallet version 1.4.1.1 is fine:

http://coinmagi.org/bin/m-wallet-1.4.1.1/
https://github.com/magi-project/magi/releases

The following pools are currently on, pls join mining:

https://www.zpool.ca

http://104.207.149.217/

Will update when more pools up.

Thanks, my wallet's working just fine again on what I assume is the correct chain.

[seeksilence]

https://github.com/JayDDee/cpuminer-opt
This cpuminer seems a little faster in Ubuntu.

To install in Ubuntu 16.04
check https://github.com/JayDDee/cpuminer-opt/blob/master/RELEASE_NOTES
sudo apt-get install build-essential libssl-dev libcurl4-openssl-dev libjansson-dev libgmp-dev automake
git clone https://github.com/JayDDee/cpuminer-opt
cd cpuminer-opt
./build.sh

Right now, the block confirmation needs over 120, possible 500? So after receive the coin in the wallet, I will run the payout script.

[amitim]

Right now, the block confirmation needs over 120, possible 500? So after receive the coin in the wallet, I will run the payout script.

on zpool.ca - 520

[Boocha466]

Blockchain data is here (block #1447972):

http://coinmagi.org/bin/block-chain/

Wallet version 1.4.1.1 is fine:

http://coinmagi.org/bin/m-wallet-1.4.1.1/
https://github.com/magi-project/magi/releases

The following pools are currently on, pls join mining:

https://www.zpool.ca

http://104.207.149.217/

Will update when more pools up.

Question! Hanging on stock exchanges - wallets. They will work ?

[joelao95]

Question! Hanging on stock exchanges - wallets. They will work ?

Will work once their wallet is synced.

[joelao95]

For one interested to solo mining:

Setup magi.conf to include:

Code:

daemon=1
server=1
rpcport=8232
rpcallowip=127.0.0.1
rpcuser=randome_username
rpcpassword=randome_rpcpassword

Run:

Code:

minerd --url=http://127.0.0.1:8232 -u randome_username -p randome_rpcpassword -t thread_numbers -e cpu_efficiency

[CoinMin3r]

Blockchain data is here (block #1447972):

http://coinmagi.org/bin/block-chain/

Wallet version 1.4.1.1 is fine:

http://coinmagi.org/bin/m-wallet-1.4.1.1/
https://github.com/magi-project/magi/releases

The following pools are currently on, pls join mining:

https://www.zpool.ca

http://104.207.149.217/

Will update when more pools up.

Thanks. Now I got to the correct chain with that latest version of the wallet.  

[Myth888]

If it is to become a solo only mining then that will actually kill most of the botnets and other malware.

I'm not sure I follow.  Botnets can solo mine, so how would you accomplish that?

Eliminating pools might eliminate a lot of botnets, but if it's to remain accessible to everyone (kinda the whole point) then it must be mineable on consumer hardware.  If it is, miner bots are relevant.  If not, the average person no longer has a chance at solo mining because the average person has a relatively outdated and underpowered system.

It will reduce the frequency of payout but on the average you will still receive the same payout in theory. In practice you might even get more payout since it will eliminate the botnets limiting mining to actual users not those who are just in for quick profit and out when the difficulty rises. The other alternative is to actually remove the unique reward system that is currently in place so that quick profiteers dont jump in when rewards are high. You ask me id rather go with solo mining only but that is me. And i dont have high end systems mining this coin. 50 hashes a sec is pretty low.

[Boocha466]

For one interested to solo mining:

Setup magi.conf to include:

Code:

daemon=1
server=1
rpcport=8232
rpcallowip=127.0.0.1
rpcuser=randome_username
rpcpassword=randome_rpcpassword

Run:

Code:

minerd --url=http://127.0.0.1:8232 -u randome_username -p randome_rpcpassword -t thread_numbers -e cpu_efficiency

Does not produce block changes! Maybe you need to add a line?

Code:

minerd --url=http://127.0.0.1:8232 -u randome_username -p randome_rpcpassword -t thread_numbers -e cpu_efficiency --coinbase-addr=Purse

[/quote]