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

jcreyesb

full member

Activity: 224

Merit: 100

Quote from: ?? on ??

Just updated to 1.4.5.2 and started mining!

Here is my pool:

http://crypto.ngrok.majed.pro:9999/site/gomining?algo=m7m

username:root
password:toor

i trying both wallet and fails.. in linux and windows

jcreyesb

full member

Activity: 224

Merit: 100

02:10:35

getinfo

02:10:35

{
"version" : "v1.4.5.2",
"protocolversion" : 71064,
"walletversion" : 60000,
"balance" : 6.16033995,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 1606986,
"timeoffset" : 9,
"moneysupply" : 7744266.88714873,
"connections" : 5,
"proxy" : "",

"ipv6" : "::",
"difficulty" : {
"proof-of-work" : 0.00153754,
"proof-of-stake" : 0.00100981
},
"testnet" : false,
"keypoololdest" : 1503018043,
"keypoolsize" : 101,
"mininput" : 0.00000000,
"paytxfee" : 0.00000000,
"errors" : ""
}

ibgeek

newbie

Activity: 25

Merit: 0

Same her.

fragilefungi

full member

Activity: 143

Merit: 100

My wallet wouldn't update block #1606950 and was stuck at #1606949 but minting was enabled. I closed the wallet, reopened it, and it finished syncing the blockchain. I enabled minting again and it crashed. Downloaded 1.4.5.2 and it opens, but crashes after minting enabled.

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: oVPN on January 06, 2018, 01:47:36 AM

Quote from: MecaTNO on January 06, 2018, 01:44:20 AM

The mining its running?

chain is stuck http://178.17.174.27:8280/m-chain/

Thanks oVPN working on it!

ParaplegicRacehorse

member

Activity: 79

Merit: 36

HODL. Patience.

Quote from: MecaTNO on January 06, 2018, 01:44:20 AM

The mining its running?

LuckyPool, at least, is still accepting shares. Such as it is. Block time for current block is currently more than 35 minutes, and that really shouldn't be. At least it seems consistent across the network, with one notable exception who probably didn't update to wallet 1.4.5.1+, which is as it should be.

oVPN

member

Activity: 116

Merit: 10

Quote from: MecaTNO on January 06, 2018, 01:44:20 AM

The mining its running?

chain is stuck http://178.17.174.27:8280/m-chain/

MecaTNO

newbie

Activity: 7

Merit: 0

The mining its running?

oVPN

member

Activity: 116

Merit: 10

fresh wallet crashes, only working with posii=0

getwork says: CBigNum::operator/: BN_div failed (code -1)

jbkel3496

newbie

Activity: 18

Merit: 0

Quote from: ParaplegicRacehorse on January 06, 2018, 01:37:41 AM

Update GitHub Releases, please. Page still shows 1.4.5.1 latest. Link to m-core.org 1.4.5.2 wallet is good, however.

Both wallets are broke.

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: ParaplegicRacehorse on January 06, 2018, 01:37:41 AM

Update GitHub Releases, please. Page still shows 1.4.5.1 latest. Link to m-core.org 1.4.5.2 wallet is good, however.

Working on different fronts atm. Will be ok.

ParaplegicRacehorse

member

Activity: 79

Merit: 36

HODL. Patience.

Update GitHub Releases, please. Page still shows 1.4.5.1 latest. Link to m-core.org 1.4.5.2 wallet is good, however.

[edit]
I see. The tag didn't get set on 1.4.5.2. The top set of downloads from GitHub are correct, per the commit history, but the tag doesn't conform.

orcan1ce

newbie

Activity: 9

Merit: 0

you mean posii=0

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: SolsticeFV on January 06, 2018, 01:16:20 AM

Im am not staking my wallet on windows and it is working. Did not crash

Good thanks for the info. Wait with staking!
Add posii=1 in Magi Conf.

SolsticeFV

newbie

Activity: 23

Merit: 0

Im am not staking my wallet on windows and it is working. Did not crash

realbagdad

newbie

Activity: 39

Merit: 0

Quote from: jonathin.r on January 06, 2018, 01:06:10 AM

My wallet just showed me passing the hardfork, but it keeps crashing... what's going on?

seems someone fucked up with the new wallet..

jbkel3496

newbie

Activity: 18

Merit: 0

Yeah but it kills solo mining.

s0litaire

member

Activity: 133

Merit: 15

Quote from: jonathin.r on January 06, 2018, 01:06:10 AM

My wallet just showed me passing the hardfork, but it keeps crashing... what's going on?

Don't enable PoS!

It's crashing the wallet for now!

orcan1ce

newbie

Activity: 9

Merit: 0

keeps crashing

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

m-wallet version v1.4.5.2

Not mandatory, but recommended in order to reject version earlier than 1.4.5.1.

Windows x32 binary is available as well.

Quote from: joelao95 on December 30, 2017, 02:28:57 AM

~~m-wallet version v1.4.5.1~~

Hard fork will take place at block #1606950. See below for the details of hard fork.

Qt-Wallet and Daemon:

https://github.com/magi-project/magi/releases
http://m-core.org/download/
~~http://m-core.org/bin/m-wallet-1.4.5.1/~~

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

Windows: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-linux.tar.gz
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.2/m-wallet-1.4.5.2-freebsd.tar.gz

~~Windows: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zip~~
~~Linux: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gz~~
~~Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmg~~
~~FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gz~~

Block chain: http://m-core.org/bin/block-chain/

v1.4.5.2
=============
Minimum protocol version 71063

v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:

- The PoW / PoS block generation rule is disabled.

- Difficulty adjustment algo switches back to MQW at #1606948.

- Block drift time is limited within 5 min.

- Remove IRC and add DNS seeds.

Quick guide:

- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.

Quick startup I (without touching the block-chain):

0) Backup wallet.dat;
1) Launch the new wallet.

Quick startup II (replacing the block-chain):

0) Backup wallet.dat;
1) Download block-chain data from here: http://m-core.org/bin/block-chain;
2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.

Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.

Things explained..

Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.

There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.

As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.

By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.

Let us know any questions / suggestions.

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