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

[malafaya]

why shutting down wallet?

Because I don't know if my older wallet version will eventually fork in the next hours. And I don't need it open anyway: I can skip staking for a day or so .

ok, thanks, i will

I wasn't exactly suggesting or advising anything here

[1714918258]

1714918258

[jcreyesb]

why shutting down wallet?

Because I don't know if my older wallet version will eventually fork in the next hours. And I don't need it open anyway: I can skip staking for a day or so .

ok, thanks, i will

I wasn't exactly suggesting or advising anything here

[ex33s]

This is really strange. Supposedly minerclaim already has the new wallet with the new rules, but it just mined 3 PoW blocks in a row in the same minute...
Is there something I misunderstood?

This release fixes these changes

1) fix sync issue
2) protocol ver 71062

So the new rules for PoS and PoW is NOT included in this release.

[malafaya]

This is really strange. Supposedly minerclaim already has the new wallet with the new rules, but it just mined 3 PoW blocks in a row in the same minute...
Is there something I misunderstood?

This release fixes these changes

1) fix sync issue
2) protocol ver 71062

So the new rules for PoS and PoW is NOT included in this release.

Hmmmm... so we will need to change protocol version again when we included them, right?...

[ex33s]

This is really strange. Supposedly minerclaim already has the new wallet with the new rules, but it just mined 3 PoW blocks in a row in the same minute...
Is there something I misunderstood?

This release fixes these changes

1) fix sync issue
2) protocol ver 71062

So the new rules for PoS and PoW is NOT included in this release.

Hmmmm... so we will need to change protocol version again when we included them, right?...

I think so yes. Joe can correct me if i'm wrong here.

[jcreyesb]

i have about 8 "POS" transactions  not valid.. why this ?


[img https://ibb.co/msFirv ]https://ibb.co/msFirv[/img]

[abbeytim]

ok so those coming on now the reason we closed our wallets and arent staking or solo mining is joe released 1.4.3.1 but thats source and linux we are still waiting for windows version

so we shut our wallets and solo mining down because the new 1.4.3.1 wallet nodes probably will not accept our pos and pow blocks.

the pools run linux therfore have updated to 1.4.3.1 so there fine. if u solo mine or pos on 1.4.3 ur blocks probably wont be accepted by the new 1.4.3.1 so

we shut our pos and pow solo down not to waste energy or mess up the chain i personaly pool mine so im fine as long as the pool has the update which it does

[abbeytim]

i have about 8 "POS" transactions  not valid.. why this ?


[img https://ibb.co/msFirv ]https://ibb.co/msFirv[/img]

i had that happen too some are just orphans and didnt get accepted some of it happened when the fork happened and werent valid either

[abbeytim]

  thinking of that i know on bitcoin qt we can run -zapwallettxes to get rid of unconfirmed or orphans but that command doesnt work with magicoin qt  so if joe or someone could tell me what the command is so i can get rid of them

[abbeytim]

Hi,
Does Bitcoin wallet commant "zapwallettxes" works also with Magi?
Thanks.

Unfortunately such function is not in the present code of Magi. I guess this is one of the reasons we should work out the latest code.

Probably you can try dumpprivkey and then import into a fresh wallet to see if make the transactions right. 

should of searched first lol

[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,
....
"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?

passed 22 hours, but nothing on my wallet.
each computer (14 pcs) shows about this

[2017-09-11 19:13:54] CPU #3: 35.24 kH, 7238.50 H/s
[2017-09-11 19:13:54] CPU #1: 31.11 kH, 6278.00 H/s
[2017-09-11 19:13:54] CPU #0: 33.66 kH, 6530.36 H/s
[2017-09-11 19:13:55] CPU #2: 42.58 kH, 7514.24 H/s
[2017-09-11 19:13:56] m7m block 1475146, diff 3.41, net 76.80 MH/s
[2017-09-11 19:14:01] CPU #1: 31.39 kH, 6524.55 H/s
[2017-09-11 19:14:01] CPU #3: 36.19 kH, 6971.89 H/s
[2017-09-11 19:14:01] CPU #0: 32.65 kH, 6237.93 H/s
[2017-09-11 19:14:01] CPU #2: 37.57 kH, 6921.67 H/s
[2017-09-11 19:14:08] CPU #1: 32.62 kH, 6720.57 H/s
[2017-09-11 19:14:08] CPU #3: 34.86 kH, 7040.89 H/s

how can I see that they work and my wallet setuped correctly?

[joelao95]

passed 22 hours, but nothing on my wallet.
each computer (14 pcs) shows about this

[2017-09-11 19:13:54] CPU #3: 35.24 kH, 7238.50 H/s
[2017-09-11 19:13:54] CPU #1: 31.11 kH, 6278.00 H/s
[2017-09-11 19:13:54] CPU #0: 33.66 kH, 6530.36 H/s
[2017-09-11 19:13:55] CPU #2: 42.58 kH, 7514.24 H/s
[2017-09-11 19:13:56] m7m block 1475146, diff 3.41, net 76.80 MH/s
[2017-09-11 19:14:01] CPU #1: 31.39 kH, 6524.55 H/s
[2017-09-11 19:14:01] CPU #3: 36.19 kH, 6971.89 H/s
[2017-09-11 19:14:01] CPU #0: 32.65 kH, 6237.93 H/s
[2017-09-11 19:14:01] CPU #2: 37.57 kH, 6921.67 H/s
[2017-09-11 19:14:08] CPU #1: 32.62 kH, 6720.57 H/s
[2017-09-11 19:14:08] CPU #3: 34.86 kH, 7040.89 H/s

how can I see that they work and my wallet setuped correctly?

At this moment pool mining will work better, or you'll need much more time to succeed in solo mining. There are formula to estimate mining time by taking into account individual vs network hashrates.

[joelao95]

ok so those coming on now the reason we closed our wallets and arent staking or solo mining is joe released 1.4.3.1 but thats source and linux we are still waiting for windows version

so we shut our wallets and solo mining down because the new 1.4.3.1 wallet nodes probably will not accept our pos and pow blocks.

the pools run linux therfore have updated to 1.4.3.1 so there fine. if u solo mine or pos on 1.4.3 ur blocks probably wont be accepted by the new 1.4.3.1 so

we shut our pos and pow solo down not to waste energy or mess up the chain i personaly pool mine so im fine as long as the pool has the update which it does

I'm not sure of what's happening right now.
The main peer if v1.4.3 and many people (namely pools) are already upgrading to v1.4.3.1, which if I understood correctly disconnects older peers (also the main peer running v1.4.3!).
So what will happen in the next hours? Are we following the main peer or the upgraded wallets? I'm not sure what to do at this point. Not even sure if mining at the pools is doing any good.

Mining with pools having wallet 1.4.3.1 is ok. But, what if your wallet using old version is stacking?
Since Joe made the announcement I shut down my wallet.

This version is with protocol version greater than the prior; it connects both new and old versions. The idea is to elevate protocol version, so once we have the new wallet (with fixes), we are able to cut off all of the old version prior to 71062.

This wallet is not yet having fixes.

It's totally unnecessary to close / turn off staking / mining / wallet. Even with the new wallet with fixes, one should be able to keep staking / mining 24/7.

[jcreyesb]

ok so those coming on now the reason we closed our wallets and arent staking or solo mining is joe released 1.4.3.1 but thats source and linux we are still waiting for windows version

so we shut our wallets and solo mining down because the new 1.4.3.1 wallet nodes probably will not accept our pos and pow blocks.

the pools run linux therfore have updated to 1.4.3.1 so there fine. if u solo mine or pos on 1.4.3 ur blocks probably wont be accepted by the new 1.4.3.1 so

we shut our pos and pow solo down not to waste energy or mess up the chain i personaly pool mine so im fine as long as the pool has the update which it does

I'm not sure of what's happening right now.
The main peer if v1.4.3 and many people (namely pools) are already upgrading to v1.4.3.1, which if I understood correctly disconnects older peers (also the main peer running v1.4.3!).
So what will happen in the next hours? Are we following the main peer or the upgraded wallets? I'm not sure what to do at this point. Not even sure if mining at the pools is doing any good.

Mining with pools having wallet 1.4.3.1 is ok. But, what if your wallet using old version is stacking?
Since Joe made the announcement I shut down my wallet.

This version is with protocol version greater than the prior; it connects both new and old versions. The idea is to elevate protocol version, so once we have the new wallet (with fixes), we are able to cut off all of the old version prior to 71062.

This wallet is not yet having fixes.

It's totally unnecessary to close / turn off staking / mining / wallet. Even with the new wallet with fixes, one should be able to keep staking / mining 24/7.

... And the new Wallet when Will release?

[abbeytim]

Main net update:

Updated the main source code (v1.4.3.1):

1) fix sync issue
2) protocol ver 71062

https://github.com/magi-project/magi

Protocol ver 71062 will get us to where once we get on the latest revisions, we'll disconnect all prior versions. Pls update to this version. I'm compiling binaries and will post links once available.  

and i assumed 1) fix sync issue


 was the fix

[joelao95]

Main net update:

Updated the main source code (v1.4.3.1):

1) fix sync issue
2) protocol ver 71062

https://github.com/magi-project/magi

Protocol ver 71062 will get us to where once we get on the latest revisions, we'll disconnect all prior versions. Pls update to this version. I'm compiling binaries and will post links once available. 

Here are binaries for v1.4.3.1:

http://coinmagi.org/bin/m-wallet-1.4.3.1/

The plan of merging fixes, that is v1.4.4:

1) Get another test wallet tomorrow

2) On Wednesday, 9/13, v1.4.4 source code finalizing; depending on how much time to compile the complete set of binaries as well as documentation, we might be able to make post until 9/14

The difficulty adjustment gets little tricky since we're disturbing the way blocks are accepted by enforcing block checking. The thing is that what happens to PoW difficulty that is adjusted based on block time will make corresponding influence on the block value, that's the center of the question.

[lhedwin]

Main net update:

Updated the main source code (v1.4.3.1):

1) fix sync issue
2) protocol ver 71062

https://github.com/magi-project/magi

Protocol ver 71062 will get us to where once we get on the latest revisions, we'll disconnect all prior versions. Pls update to this version. I'm compiling binaries and will post links once available. 

Here are binaries for v1.4.3.1:

http://coinmagi.org/bin/m-wallet-1.4.3.1/

The plan of merging fixes, that is v1.4.4:

1) Get another test wallet tomorrow

2) On Wednesday, 9/13, v1.4.4 source code finalizing; depending on how much time to compile the complete set of binaries as well as documentation, we might be able to make post until 9/14

The difficulty adjustment gets little tricky since we're disturbing the way blocks are accepted by enforcing block checking. The thing is that what happens to PoW difficulty that is adjusted based on block time will make corresponding influence on the block value, that's the center of the question.

Sorry, my english is not good. This new wallet is for test only?

[111magic]

Main net update:

Updated the main source code (v1.4.3.1):

1) fix sync issue
2) protocol ver 71062

https://github.com/magi-project/magi

Protocol ver 71062 will get us to where once we get on the latest revisions, we'll disconnect all prior versions. Pls update to this version. I'm compiling binaries and will post links once available. 

Here are binaries for v1.4.3.1:

http://coinmagi.org/bin/m-wallet-1.4.3.1/

The plan of merging fixes, that is v1.4.4:

1) Get another test wallet tomorrow

2) On Wednesday, 9/13, v1.4.4 source code finalizing; depending on how much time to compile the complete set of binaries as well as documentation, we might be able to make post until 9/14

The difficulty adjustment gets little tricky since we're disturbing the way blocks are accepted by enforcing block checking. The thing is that what happens to PoW difficulty that is adjusted based on block time will make corresponding influence on the block value, that's the center of the question.

Sorry, my english is not good. This new wallet is for test only?

Looks like it. If i read correct the new releases will be posted on 14 september 2017. Thats 1 day before Magi's third birthday! 😁

[malafaya]

Main net update:

Updated the main source code (v1.4.3.1):

1) fix sync issue
2) protocol ver 71062

https://github.com/magi-project/magi

Protocol ver 71062 will get us to where once we get on the latest revisions, we'll disconnect all prior versions. Pls update to this version. I'm compiling binaries and will post links once available. 

Here are binaries for v1.4.3.1:

http://coinmagi.org/bin/m-wallet-1.4.3.1/

The plan of merging fixes, that is v1.4.4:

1) Get another test wallet tomorrow

2) On Wednesday, 9/13, v1.4.4 source code finalizing; depending on how much time to compile the complete set of binaries as well as documentation, we might be able to make post until 9/14

The difficulty adjustment gets little tricky since we're disturbing the way blocks are accepted by enforcing block checking. The thing is that what happens to PoW difficulty that is adjusted based on block time will make corresponding influence on the block value, that's the center of the question.

Sorry, my english is not good. This new wallet is for test only?

Looks like it. If i read correct the new releases will be posted on 14 september 2017. Thats 1 day before Magi's third birthday! 😁

From what I understood, this v1.4.3.1 is not a test wallet but a normal one. Joe intends to get another test wallet "tomorrow"/today.

[edward0181]

And with that the exchanges will have a working wallet again? Would indeed be nice if all is fixed just before coins 3th birthday.