[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 352.

AngryWhiteWolf

full member

Activity: 616

Merit: 100

Quote from: victorgml on September 14, 2017, 05:39:20 PM

Hi everybody I have a problem with my wallet, I downloaded version 1.4.3 it was full sinc and I have some magic coins there, but today I want to open it and it show me an error that says that my pc don't have enough resources and then it erase the file m-wallet.exe

Can anyone help me?

I already lost my magi coin?

I don't know what to do Sad

There will be an update (1.4.4) very soon, that will fix all issues from the last couple of days. Better wait until then. If you have wallet.dat you are ok.

victorgml

newbie

Activity: 5

Merit: 0

Hi everybody I have a problem with my wallet, I downloaded version 1.4.3 it was full sinc and I have some magic coins there, but today I want to open it and it show me an error that says that my pc don't have enough resources and then it erase the file m-wallet.exe

Can anyone help me?

I already lost my magi coin?

I don't know what to do Sad

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: ex33s on September 14, 2017, 05:21:44 PM

Nope,

The commit https://github.com/magi-project/magi/commit/10395ede0b3a68e5aa95f524d0f3550ed918fb52#diff-7ec3c68a81efff79b6ca22ac1f1eabba

Before that the return looked like this

Code:

return ( (pindex_->nHeight > 1451226) );

Which mean when block is higher then 1451226 return true

So even with v1.4.3.1 it's still in maintenance and also that the maintenance has no end in v1.4.3.1

Yep, that's right.
I looked a bit further, to where the reward gets multiplied by 0.3 in maintenance, and it seems that function (GetProofOfWorkReward_OPM) is only used under some "POM V2 whatever" height?
Is this (still) our current height?
Or we can just wait for Joe?

This is tiring.

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: malafaya on September 14, 2017, 05:17:19 PM

My wallet is v1.4.3.1 and it says next reward is 43.245 XMG...
Could it be actually v1.4.3.1 that already crossed the maintenance threshold, and v1.4.4 delayed it?
This is very weird...

Nope,

The commit https://github.com/magi-project/magi/commit/10395ede0b3a68e5aa95f524d0f3550ed918fb52#diff-7ec3c68a81efff79b6ca22ac1f1eabba

Before that the return looked like this

Code:

return ( (pindex_->nHeight > 1451226) );

Which mean when block is higher then 1451226 return true

So even with v1.4.3.1 it's still in maintenance and also that the maintenance has no end in v1.4.3.1

malafaya

sr. member

Activity: 490

Merit: 256

My wallet is v1.4.3.1 and it says next reward is 43.245 XMG...
Could it be actually v1.4.3.1 that already crossed the maintenance threshold, and v1.4.4 delayed it?
This is very weird...

My9bot

full member

Activity: 239

Merit: 100

Quote from: ex33s on September 14, 2017, 04:57:42 PM

Quote from: My9bot on September 14, 2017, 04:50:55 PM

Quote from: malafaya on September 14, 2017, 04:31:15 PM

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

Could you explain it a bit more why you think there's a bug on that return statement?

ohh sry
im worng
i think a have to sleep a while

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: seeksilence on September 14, 2017, 05:01:11 PM

#define HEIGHT_INIT_MAINTENANCE 1451226

#define HEIGHT_END_MAINTENANCE 1481500

bool IsMaintenance(const CBlockIndex* pindex_)

{

return ( (pindex_->nHeight > HEIGHT_INIT_MAINTENANCE) && (pindex_->nHeight < HEIGHT_END_MAINTENANCE) );

}

The maintenance is supposed to end at block 1481500. But current block is only 1479208. Should still in maintenance mode.

That return stametanet will return true or false

So breaking it down a bit

Code:

(pindex_->nHeight > HEIGHT_INIT_MAINTENANCE)

will say true as we are at block ~1479208 which is higher then HEIGHT_INIT_MAINTENANCE

Code:

(pindex_->nHeight < HEIGHT_END_MAINTENANCE)

will say true as we are at block ~1479208 which is lower then HEIGHT_END_MAINTENANCE

With

Code:

&&

between both statements means both needs to be true for it to be in maintenance.

So that function with current block will return true.

If ether of them was false, the return would be false too

So magi is in maintenance

seeksilence

full member

Activity: 239

Merit: 250

#define HEIGHT_INIT_MAINTENANCE 1451226

#define HEIGHT_END_MAINTENANCE 1481500

bool IsMaintenance(const CBlockIndex* pindex_)

{

return ( (pindex_->nHeight > HEIGHT_INIT_MAINTENANCE) && (pindex_->nHeight < HEIGHT_END_MAINTENANCE) );

}

The maintenance is supposed to end at block 1481500. But current block is only 1479208. Should still in maintenance mode.

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: My9bot on September 14, 2017, 04:50:55 PM

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

Not sure about that specific line but this https://github.com/magi-project/magi/commit/10395ede0b3a68e5aa95f524d0f3550ed918fb52#diff-7ec3c68a81efff79b6ca22ac1f1eabba postpones some threshold heights up in v1.4.4, so at block 1478500, both 1.4.3.1 and 1.4.4 started having different params (and probably a fork would be likely).

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: My9bot on September 14, 2017, 04:50:55 PM

Quote from: malafaya on September 14, 2017, 04:31:15 PM

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

Could you explain it a bit more why you think there's a bug on that return statement?

Pool42

newbie

Activity: 28

Merit: 0

As large blocks are falling, Pool42 has disabled its payouts temporarily.
Don't worry it shall be back soon enough when we are sure blocks are effectively valid.

My9bot

full member

Activity: 239

Merit: 100

Quote from: malafaya on September 14, 2017, 04:31:15 PM

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

i think you a right there is a bug in 1.4.4

https://github.com/magi-project/magi/blob/10395ede0b3a68e5aa95f524d0f3550ed918fb52/src/main.cpp#L1074

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: seeksilence on September 14, 2017, 04:44:55 PM

Just temporarily disabled payout. Do not know if xmgpool is on the right track now.
Block values are 43.25 now.

No one use 1.4.4, it is for testnet. It will be released Thursday night.

It's thursday night for me already Wink

.
Binaries will be released tonight. Source code already made available per Joe's post, to those willing to compile.
At least, this is what I understood earliler today.

seeksilence

full member

Activity: 239

Merit: 250

Just temporarily disabled payout. Do not know if xmgpool is on the right track now.
Block values are 43.25 now.

No one use 1.4.4, it is for testnet. It will be released Thursday night.

abbeytim

sr. member

Activity: 438

Merit: 250

i see hopefully joe will give us an update

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: abbeytim on September 14, 2017, 04:33:39 PM

as far as i know 1.4.4 is testnet

Quote from: joelao95 on September 14, 2017, 12:07:05 AM

We have had the updates in place. We are ready to get the fix on the main chain rolling and hence the new wallet.

v1.4.4

Emphasis is mine.
I'm sure most pools already upgraded. Confirmations?

EDIT: Check rewards in https://xmg.minerclaim.net/index.php?page=statistics&action=blocks

abbeytim

sr. member

Activity: 438

Merit: 250

Quote from: malafaya on September 14, 2017, 04:31:15 PM

Quote from: jcreyesb on September 14, 2017, 04:28:50 PM

Quote from: malafaya on September 14, 2017, 04:25:45 PM

Quote from: jcreyesb on September 14, 2017, 03:53:49 PM

Quote from: malafaya on September 14, 2017, 03:46:20 PM

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm 6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm 5 xmg

last block 1479166
one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo

16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

as far as i know 1.4.4 is testnet

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: jcreyesb on September 14, 2017, 04:28:50 PM

Quote from: malafaya on September 14, 2017, 04:25:45 PM

Quote from: jcreyesb on September 14, 2017, 03:53:49 PM

Quote from: malafaya on September 14, 2017, 03:46:20 PM

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm 6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm 5 xmg

last block 1479166
one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo

16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

Not sure what you're trying to show. Your wallet is still v1.4.3.1. Check the reward in this block: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm
The new v1.4.4 is supposed to return to old rewards tomorrow night, but I can already see new blocks with rewards of 30 XMG, probably because pools already upgraded and there's something wrong with the "time trigger"...

jcreyesb

full member

Activity: 224

Merit: 100

Quote from: malafaya on September 14, 2017, 04:25:45 PM

Quote from: jcreyesb on September 14, 2017, 03:53:49 PM

Quote from: malafaya on September 14, 2017, 03:46:20 PM

There's something odd.
People are mining with the old rewards scheme already: https://chainz.cryptoid.info/xmg/block.dws?1479159.htm .
This is ahead of schedule. Possibly a cause for forking?

i'm mining solo..
https://chainz.cryptoid.info/xmg/tx.dws?dceea06d62d0683bca93946a5d6e19e7f6fdb25a0d2c92cfe8f6dd810c59c46b.htm 6 XMG

https://chainz.cryptoid.info/xmg/tx.dws?9c41f47343631f0ffd5af84c4e23bd5d170a8e6faa770adc504edf4cb712fcad.htm 5 xmg

last block 1479166
one node
connect=104.128.225.215

That was a few hours ago. Check the recent blocks.

16:23:46

getinfo

16:23:46

{
"version" : "v1.4.3.1",
"protocolversion" : 71062,
"walletversion" : 60000,
"balance" : 0.00090000,
"newmint" : 12.40329947,
"stake" : 0.00000000,
"blocks" : 1479193,
"timeoffset" : 0,
"moneysupply" : 7340022.00787421,
"connections" : 1,
"proxy" : "",
"ip" : "190.202.x.x",
"ipv4" : "190.202.x.x",
"ipv6" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 1.24027707,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1503492406,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

abbeytim

sr. member

Activity: 438

Merit: 250

cool they just fixed the pool i use

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