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

[edward0181]

Looks like the tests are almost finished.
If i read the posts correct wallet is working good.
Pls give Joe feedback about what worked good & what did not or worked after adding some things. Thanks guys!

Nothing to complain. Pow did work and have read post is doing okay as well. Perhaps an idea to put number of confirmation back to 120? Believe that was done to avoid forking and still it did fork on last time.

[111magic]

Looks like the tests are almost finished.
If i read the posts correct wallet is working good.
Pls give Joe feedback about what worked good & what did not or worked after adding some things. Thanks guys!

Nothing to complain. Pow did work and have read post is doing okay as well. Perhaps an idea to put number of confirmation back to 120? Believe that was done to avoid forking and still it did fork on last time.

Thank you Edward0181 appriciate your respons!

[starmman]

Looks like the tests are almost finished.
If i read the posts correct wallet is working good.
Pls give Joe feedback about what worked good & what did not or worked after adding some things. Thanks guys!

Nothing to complain. Pow did work and have read post is doing okay as well. Perhaps an idea to put number of confirmation back to 120? Believe that was done to avoid forking and still it did fork on last time.

Thank you Edward0181 appriciate your respons!

I didn't manage to get time to setup a test env - great to hear that its working well =)

I wonder if the guy with all the hash could help to try to break it

[malafaya]

Hi.

What is the meaning of this:

CTxMemPool::accept() : accepted b129e2eaf8 (poolsz 1)

It means you got a pending transaction from a peer. These transactions are kept in the mempool. That transaction should be "recorded" in a block by someone soon, when a block is mined/staked.

[penambang]

someone mining with bitcoin addr on magi.altexplorer.xyz, that's not gonna work.

Code:

Unauthorized  1L6bKP4uJz683vNPzt6FhQ7BavwsrG94TJ:x [183.249.191.28]

You must use Magi address, not BTC.

[lhedwin]

Hi.

What is the meaning of this:

CTxMemPool::accept() : accepted b129e2eaf8 (poolsz 1)

It means you got a pending transaction from a peer. These transactions are kept in the mempool. That transaction should be "recorded" in a block by someone soon, when a block is mined/staked.

Ty!

It only shows up when i setgenerate true.

[drgauravxmg]

That is one good news!

Waiting for Dev's announcement about the same. Will then start mining. Didn't know much of the technical aspects, so couldn't participate in tests.

[Lord Cryptocurrency]

I would like information, the Magi are being excluded from Cryptopia and on Bittrex the wallet is under maintenance. What is the future of the currency?

[joelao95]

I would like information, the Magi are being excluded from Cryptopia and on Bittrex the wallet is under maintenance. What is the future of the currency?

We're recovering the wallet.

[joelao95]

Looks like the tests are almost finished.
If i read the posts correct wallet is working good.
Pls give Joe feedback about what worked good & what did not or worked after adding some things. Thanks guys!

Nothing to complain. Pow did work and have read post is doing okay as well. Perhaps an idea to put number of confirmation back to 120? Believe that was done to avoid forking and still it did fork on last time.

It might be better that we remain the current setup. We'll make updates to the main source code soon.

[joelao95]

The test wallet checks blocks to make sure PoW and PoS following a pattern: 1) at least two PoS between PoW blocks, and 2) for any continuous five blocks contains at least one PoW block. When the above conditions are not satisfied, blocks come out at about every 15min. Blocks found before 15min is up will then be rejected, along with error "block violations".

The waiting time "15min" rule might be a concern when PoS blocks not coming out as expected; it would be necessary to rely on the PoS thing which is the main force in the future. By the time when the whole network is staking and PoS becomes a major force pushing forward the chain, we won't see the 15min rule. The 15min is somehow a random number I come up with, that was made to differ from the regular PoW block time (3min). Reducing the waiting time would recover things back to normal faster. 

Thanks all for the test in both PoW and PoS. I believe the chain moves as expected, and I don't see particular concerns, except for the block time, which is 3.17min by averaging the past 100 blocks at #1451764. The longer block time is mainly due to limited PoS blocks; the situation shall get changed once on the mainnet that has more in PoS staking.

I'll update the way that difficulty adjustment works by taking into account the "15min" rule. Once we're done that, we will make changes to the main source code. I hope we get it done in next week.

Pls let me know if you see a fork in test.

[lhedwin]

Looks like the tests are almost finished.
If i read the posts correct wallet is working good.
Pls give Joe feedback about what worked good & what did not or worked after adding some things. Thanks guys!

Nothing to complain. Pow did work and have read post is doing okay as well. Perhaps an idea to put number of confirmation back to 120? Believe that was done to avoid forking and still it did fork on last time.

It might be better that we remain the current setup. We'll make updates to the main source code soon.

Hi.

Is there a way to see the m-wallet log in "live mode"?
sorry about my english.

[peggleg]

Morning all,

Do you know when the exchanges will be accepting XMG again?

Thanks

[amitim]

Hi!
I am try to mining solo.
Ubuntu 16.04, cpuminer-opt 3.6.7/3.6.8
Wallet

Code:

{
"version" : "v1.4.3.0",
"protocolversion" : 71061,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1473251,
"timeoffset" : 0,
"moneysupply" : 7325425.38506251,
"connections" : 2,
"proxy" : "",
....
....
"difficulty" : {
"proof-of-work" : 1.64375831,
"proof-of-stake" : 0.00422338
},
"testnet" : false,
"keypoololdest" : 1504957397,
"keypoolsize" : 102,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Wallet on computer with ip 192.168.0.100

magi.conf

Code:

rpcuser=myuser
rpcpassword=mypassword
rpcport=8232
server=1
listen=1
rpcallowip=192.168.0.*
connect=104.128.225.215
addnode=104.128.225.215
stakesplitthreshold=500
stakecombinethreshold=250

started some computers in local network 192.168.0.* (summary hashrate is ~300Kh). process of mining started. But after 7 hourse i havn't any changes in my wallet.
Command line for mining

Code:

./cpuminer -r 0 -a m7m -o http://192.168.0.100:8232 -u myuser -p mypassword

debug.log hasn't errors, only good strings, for examples

Code:

ProcessBlock: ACCEPTED

Has not much time passed or am I doing something wrong?

[edward0181]

Chance is, that with 300Kh/s you'll have to be lucky to find a block. Current net hashrate is 66MH/s and diff of 2.8.
Can take more then a day to just find a single block solo.

[My9bot]

Hi!
I am try to mining solo.
Ubuntu 16.04, cpuminer-opt 3.6.7/3.6.8
Wallet

Code:

{
"version" : "v1.4.3.0",
"protocolversion" : 71061,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1473251,
"timeoffset" : 0,
"moneysupply" : 7325425.38506251,
"connections" : 2,
"proxy" : "",
....
....
"difficulty" : {
"proof-of-work" : 1.64375831,
"proof-of-stake" : 0.00422338
},
"testnet" : false,
"keypoololdest" : 1504957397,
"keypoolsize" : 102,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Wallet on computer with ip 192.168.0.100

magi.conf

Code:

rpcuser=myuser
rpcpassword=mypassword
rpcport=8232
server=1
listen=1
rpcallowip=192.168.0.*
connect=104.128.225.215
addnode=104.128.225.215
stakesplitthreshold=500
stakecombinethreshold=250

started some computers in local network 192.168.0.* (summary hashrate is ~300Kh). process of mining started. But after 7 hourse i havn't any changes in my wallet.
Command line for mining

Code:

./cpuminer -r 0 -a m7m -o http://192.168.0.100:8232 -u myuser -p mypassword

debug.log hasn't errors, only good strings, for examples

Code:

ProcessBlock: ACCEPTED

Has not much time passed or am I doing something wrong?

$hps=300000
$diff=2.76038541
$time_to_find_inSec = ($diff * pow(2,32) / $hps ) ;

$time_to_find_inSe = (2.76038541 * bcpow(2,32) / 300000) ;

39519.216867685 sec / 60 = 658.65361446142 min

658.65361446142 min / 60 = 10.977560241 hours

[amitim]

@edward0181, @My9bot
Thank you! Now I understood.

[The Frisian]

Staking is fun!

[bfons]

The test wallet checks blocks to make sure PoW and PoS following a pattern: 1) at least two PoS between PoW blocks, and 2) for any continuous five blocks contains at least one PoW block. When the above conditions are not satisfied, blocks come out at about every 15min. Blocks found before 15min is up will then be rejected, along with error "block violations".

The waiting time "15min" rule might be a concern when PoS blocks not coming out as expected; it would be necessary to rely on the PoS thing which is the main force in the future. By the time when the whole network is staking and PoS becomes a major force pushing forward the chain, we won't see the 15min rule. The 15min is somehow a random number I come up with, that was made to differ from the regular PoW block time (3min). Reducing the waiting time would recover things back to normal faster. 

Thanks all for the test in both PoW and PoS. I believe the chain moves as expected, and I don't see particular concerns, except for the block time, which is 3.17min by averaging the past 100 blocks at #1451764. The longer block time is mainly due to limited PoS blocks; the situation shall get changed once on the mainnet that has more in PoS staking.

I'll update the way that difficulty adjustment works by taking into account the "15min" rule. Once we're done that, we will make changes to the main source code. I hope we get it done in next week.

Pls let me know if you see a fork in test.

Thank you for the timely update

[ex33s]

Staking is fun!

Agree!