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

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: Cyboria on September 07, 2017, 11:12:35 AM

Quote from: malafaya on September 07, 2017, 10:30:55 AM

Hmmm, who is this guy?

"addr" : "109.195.147.134:63553",
"services" : "00000001",
"lastsend" : 1504797968,
"lastrecv" : 1504797954,
"conntime" : 1504797954,
"version" : 71051,
"subver" : "/m-core:1.3.1/",

All I can see is that the signal is coming from somewhere in Russia/Bashkortostan
Why are you wondering?

Edward0181 above said he used connect=, but he got this old wallet connecting to him.
Also I thought older protocol versions could not connect to newer ones.

Cyboria

newbie

Activity: 21

Merit: 0

Quote from: malafaya on September 07, 2017, 10:30:55 AM

Hmmm, who is this guy?

"addr" : "109.195.147.134:63553",
"services" : "00000001",
"lastsend" : 1504797968,
"lastrecv" : 1504797954,
"conntime" : 1504797954,
"version" : 71051,
"subver" : "/m-core:1.3.1/",

All I can see is that the signal is coming from somewhere in Russia/Bashkortostan
Why are you wondering?

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: jcreyesb on September 07, 2017, 10:57:42 AM

we must upgrade to 1.4.3.1 ??

NO! It's not an upgrade. It's a test version. All transactions there are not valid on the main chain.

jcreyesb

full member

Activity: 224

Merit: 100

we must upgrade to 1.4.3.1 ??

malafaya

sr. member

Activity: 490

Merit: 256

Quote from: BassT on September 07, 2017, 10:47:35 AM

Strange, all day it worked without any problem with addnode=, 15 minutes ago got same problems like edward0181. Peers from mainnet appeared.

Changed to connect=, now all fine

Peers may be obtained from other peers. For example, you may have gotten them from edward0181's peer.
Another way is from the peer IRC channel, unless you set irc=0 in the .conf file. All wallet versions share the same IRC channel AFAIK.

Of course, a peer may always connect to yours on its own initiative, unless you block it (by using connect=, or by blocking incoming peers with listen=0).

BassT

newbie

Activity: 4

Merit: 0

Strange, all day it worked without any problem with addnode=, 15 minutes ago got same problems like edward0181. Peers from mainnet appeared.

Changed to connect=, now all fine

malafaya

sr. member

Activity: 490

Merit: 256

Hmmm, who is this guy?

"addr" : "109.195.147.134:63553",
"services" : "00000001",
"lastsend" : 1504797968,
"lastrecv" : 1504797954,
"conntime" : 1504797954,
"version" : 71051,
"subver" : "/m-core:1.3.1/",

edward0181

full member

Activity: 276

Merit: 100

Better now :-D

Code:

./magid getinfo
{
    "version" : "v1.4.3.1",
    "protocolversion" : 71061,
    "walletversion" : 60000,
    "balance" : 256.31924000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 1451302,
    "timeoffset" : 0,
    "moneysupply" : 7269146.69022204,
    "connections" : 3,
    "proxy" : "",
    "ip" : "85.214.23.202",
    "ipv4" : "85.214.23.202",
    "ipv6" : "0.0.0.0",
    "difficulty" : {
        "proof-of-work" : 0.35032528,
        "proof-of-stake" : 0.00072166
    },
    "testnet" : false,
    "keypoololdest" : 1503507967,
    "keypoolsize" : 102,
    "mininput" : 0.00000000,
    "paytxfee" : 0.00010000,
    "errors" : "This build is for test only; do NOT use for minging and any other transactions; report bugs to the Magi team."
}

Code:

./magid getpeerinfo
[
    {
        "addr" : "109.195.147.134:63553",
        "services" : "00000001",
        "lastsend" : 1504797968,
        "lastrecv" : 1504797954,
        "conntime" : 1504797954,
        "version" : 71051,
        "subver" : "/m-core:1.3.1/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1445929,
        "banscore" : 0
    },
    {
        "addr" : "185.7.87.86:52153",
        "services" : "00000001",
        "lastsend" : 1504797968,
        "lastrecv" : 1504797968,
        "conntime" : 1504797967,
        "version" : 71061,
        "subver" : "/m-core:1.4.3.1/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1451302,
        "banscore" : 0
    },
    {
        "addr" : "87.171.74.199:62620",
        "services" : "00000001",
        "lastsend" : 1504798012,
        "lastrecv" : 1504798011,
        "conntime" : 1504798011,
        "version" : 71061,
        "subver" : "/m-core:1.4.3.1/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1451355,
        "banscore" : 0
    }
]

edward0181

full member

Activity: 276

Merit: 100

I'll remove blocks / database and use connect= instead of addnode... lets see

malafaya

sr. member

Activity: 490

Merit: 256

I think you're connecting also to peers on the main chain (main wallet v1.4.3). Test wallet is v1.4.3.1, right? Test chain is probably around block 1451000 whereas main chain is around 1469000.
You should probably use connect= to connect to test peers only.

edward0181

full member

Activity: 276

Merit: 100

I'm lost

getinfo:

Code:

/m-wallet-1.4.3.1-test-linux/bin/64# ./magid getinfo
{
    "version" : "v1.4.3.1",
    "protocolversion" : 71061,
    "walletversion" : 60000,
    "balance" : 256.73307218,
    "newmint" : 41.17470470,
    "stake" : 0.00000000,
    "blocks" : 1454101,
    "timeoffset" : 0,
    "moneysupply" : 7276388.55658416,
    "connections" : 5,
    "proxy" : "",
    "ip" : "85.214.23.202",
    "ipv4" : "85.214.23.202",
    "ipv6" : "0.0.0.0",
    "difficulty" : {
        "proof-of-work" : 0.89867533,
        "proof-of-stake" : 0.00267158
    },
    "testnet" : false,
    "keypoololdest" : 1503507967,
    "keypoolsize" : 102,
    "mininput" : 0.00000000,
    "paytxfee" : 0.00010000,
    "errors" : "This build is for test only; do NOT use for minging and any other transactions; report bugs to the Magi team."

getpeerinfo:

Code:

 ./magid getpeerinfo
[
    {
        "addr" : "115.79.39.188:57363",
        "services" : "00000001",
        "lastsend" : 1504796813,
        "lastrecv" : 1504796802,
        "conntime" : 1504796801,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1453011,
        "banscore" : 0
    },
    {
        "addr" : "185.7.87.86:51555",
        "services" : "00000001",
        "lastsend" : 1504796813,
        "lastrecv" : 1504796813,
        "conntime" : 1504796812,
        "version" : 71061,
        "subver" : "/m-core:1.4.3.1/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1451302,
        "banscore" : 0
    },
    {
        "addr" : "180.173.16.119:8885",
        "services" : "00000001",
        "lastsend" : 1504797019,
        "lastrecv" : 1504797018,
        "conntime" : 1504796825,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1469576,
        "banscore" : 0
    },
    {
        "addr" : "87.245.7.194:10069",
        "services" : "00000001",
        "lastsend" : 1504797019,
        "lastrecv" : 1504797019,
        "conntime" : 1504796879,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1469579,
        "banscore" : 0
    },
    {
        "addr" : "104.128.225.240:8233",
        "services" : "00000001",
        "lastsend" : 1504797018,
        "lastrecv" : 1504797018,
        "conntime" : 1504796891,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1469579,
        "banscore" : 0
    },
    {
        "addr" : "190.207.135.160:61710",
        "services" : "00000001",
        "lastsend" : 1504797020,
        "lastrecv" : 1504797021,
        "conntime" : 1504796974,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 1469579,
        "banscore" : 0
    },
    {
        "addr" : "46.36.36.96:8233",
        "services" : "00000001",
        "lastsend" : 1504797024,
        "lastrecv" : 1504797025,
        "conntime" : 1504796997,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1469579,
        "banscore" : 0
    },
    {
        "addr" : "93.182.160.133:8233",
        "services" : "00000001",
        "lastsend" : 1504797020,
        "lastrecv" : 1504797021,
        "conntime" : 1504796998,
        "version" : 71061,
        "subver" : "/m-core:1.4.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1469579,
        "banscore" : 0
    }
]

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: edward0181 on September 07, 2017, 09:48:04 AM

All other wallets / nodes are on correct version ;-)

Just want to help and test, but I see other peers on much higher startheight, and my wallet just doesn't go higher.

Great to see people helping out Joe with testing. Good work Edward0181

edward0181

full member

Activity: 276

Merit: 100

All other wallets / nodes are on correct version ;-)

Just want to help and test, but I see other peers on much higher startheight, and my wallet just doesn't go higher.

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: edward0181 on September 07, 2017, 09:41:59 AM

My Wallet is stuck on 1454101 in test wallet / net.

Thanks Edward0181. Good thing you added TEST wallet in your post. 😉

edward0181

full member

Activity: 276

Merit: 100

My Wallet is stuck on 1454101 in test wallet / net.

poer

full member

Activity: 541

Merit: 100

Quote from: starmman on September 07, 2017, 09:21:05 AM

Quote from: poer on September 07, 2017, 09:15:21 AM

why bittrex cannot deposit magi

Hi Poer,

(simple version of explanation) There were problems with the chain constantly becoming forked due to some miners having too much hashing power. The current live version of the chain is not a permanent solution, so hasn't been loaded onto the exchanges - the permanent solution is currently under a test network and will be rolled out if successful. Joe will likely post when this is ready then the exchanges will be notified and deposits/withdrawals back online again.

ok thanks for information ....happy universary 3 years for magicoin

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: poer on September 07, 2017, 09:15:21 AM

why bittrex cannot deposit magi

Hi Poer,

(simple version of explanation) There were problems with the chain constantly becoming forked due to some miners having too much hashing power. The current live version of the chain is not a permanent solution, so hasn't been loaded onto the exchanges - the permanent solution is currently under a test network and will be rolled out if successful. Joe will likely post when this is ready then the exchanges will be notified and deposits/withdrawals back online again.

poer

full member

Activity: 541

Merit: 100

why bittrex cannot deposit magi

oVPN

member

Activity: 116

Merit: 10

Quote from: TommyYo on September 06, 2017, 09:59:42 PM

and another question guys, i am mining in minerclaim, i see the rewards are usually 10~ down to 0.5, now i see that some payouts outside of the pool with 1,000 coins, whit proof-of-stake.

Block Height Age Transactions Value Out Difficulty Extracted by
1468880 1 minute 20.4 kB 1,125.58529186 XMG 0.0058 Proof of Stake

while each value out from minerclain is 10~, can some one please explain this to me? can i also do PoS and extract 1,000 each time?
please advise
thank you

our explorer here shows output of stake blocks (Mint), not value used to stake + output: http://178.17.174.27:8280/m-chain/

BassT

newbie

Activity: 4

Merit: 0

Quote from: joelao95 on September 06, 2017, 03:10:37 PM

Pls help the test (PoW & PoS mining). We'd see if this test comes out without forks.

Looking good so far. I'm staking and could also mine some blocks.

One interesting thing is the miners output, which I've not seen in the regular chain and solo mining.

Using m-minerd-64 (cpuminer 2.4) I'm sometimes getting:

[2017-09-07 13:52:41] accepted: 0/31 (0.00%), 48.48 khash/s (booooo)

Using cpuminer-opt-3.6.8 sometimes produces RPC-Errors. As soon as one error kicks in, miner can't submit any further blocks until restartet

[2017-09-07 14:06:33] JSON-RPC call failed: Invalid parameter
[2017-09-07 14:06:33] submit_upstream_work json_rpc_call failed
[2017-09-07 14:06:33] ...retry after 10 seconds
[2017-09-07 14:06:45] JSON-RPC call failed: Invalid parameter
[2017-09-07 14:06:45] submit_upstream_work json_rpc_call failed
[2017-09-07 14:06:45] ...retry after 10 seconds
[...]

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