The ANN updated, Windows and Linux binaries ready, MacOS X binaries coming tomorrow. Would be good to update our web site as well. We need to notify all pools and exchanges of the hard fork.
does this update/fork address the orphan issues when mining? I've been running v1.5.0.0-orb-3-g78dc34f-dirty because of it.... Orphans shouldn't be an issue with the coming block target of 2 minutes on average. Thanks. I've updated the wallet and so far so good: www.zpool.ca/site/block?id=579Cheers |
|
|
|
The ANN updated, Windows and Linux binaries ready, MacOS X binaries coming tomorrow. Would be good to update our web site as well. We need to notify all pools and exchanges of the hard fork.
does this update/fork address the orphan issues when mining? I've been running v1.5.0.0-orb-3-g78dc34f-dirty because of it.... |
|
|
|
is MMR and NH blocked from using zpool? Still unable to connect to sha256.mine.zpool.ca:3333
I've been using NH, but not on SHA... can't see any reason they wouldn't connect... Whats your mining address start with? just the first 5-6 is fine. 14R8wj try now |
|
|
|
is MMR and NH blocked from using zpool? Still unable to connect to sha256.mine.zpool.ca:3333
I've been using NH, but not on SHA... can't see any reason they wouldn't connect... Whats your mining address start with? just the first 5-6 is fine. looks like they were banned on that machine. I'll check into this a bit further but plz let me know your address, first 6 char |
|
|
|
is MMR and NH blocked from using zpool? Still unable to connect to sha256.mine.zpool.ca:3333
I've been using NH, but not on SHA... can't see any reason they wouldn't connect... Whats your mining address start with? just the first 5-6 is fine. |
|
|
|
{
"version" : "v2.5.4.2: Beta",
"protocolversion" : 62016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 0,
"timestamping" : {
"systemclock" : 1474399707,
"adjustedtime" : 1474399707,
"ntpoffset" : 0,
"p2poffset" : null
},
"moneysupply" : 0.00000000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00024414,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1468947863,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
}
connected 107.170.67.22:51325
send version message: version 62016, blocks=0, us=192.95.29.72:51325, them=107.170.67.22:51325, peer=107.170.67.22:51325
connected 193.219.117.63:51325
send version message: version 62016, blocks=0, us=192.95.29.72:51325, them=193.219.117.63:51325, peer=193.219.117.63:51325
socket closed
disconnecting node 107.170.67.22:51325
socket closed
disconnecting node 193.219.117.63:51325
current version is -> "v2.5.4.2: Beta 2.5.4.2"please redownload,rebuild source https://github.com/martexcoin/martexcoinuggg, I just did... "version" : "v2.5.4.2: Beta", that's different than v2.5.4.2: Beta 2.5.4.2??? # cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/martexcoin/martexcoin.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master # git pull Already up-to-date. |
|
|
|
|
{
"version" : "v2.5.4.2: Beta",
"protocolversion" : 62016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 0,
"timestamping" : {
"systemclock" : 1474399707,
"adjustedtime" : 1474399707,
"ntpoffset" : 0,
"p2poffset" : null
},
"moneysupply" : 0.00000000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00024414,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1468947863,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
}
connected 107.170.67.22:51325
send version message: version 62016, blocks=0, us=192.95.29.72:51325, them=107.170.67.22:51325, peer=107.170.67.22:51325
connected 193.219.117.63:51325
send version message: version 62016, blocks=0, us=192.95.29.72:51325, them=193.219.117.63:51325, peer=193.219.117.63:51325
socket closed
disconnecting node 107.170.67.22:51325
socket closed
disconnecting node 193.219.117.63:51325
|
|
|
|
Please update wallet urgently Bug detected in the master branch, please re-download the version of branch 2.5.4.2version -> "v2.5.4.2: Beta 2.5.4.2"https://github.com/martexcoin/martexcoinSorry for the inconvenience not able to connect to peers..... addnode=seed.martexcoin.org addnode=seed1.martexcoin.org addnode=seed2.martexcoin.org addnode=seed3.martexcoin.org addnode=seed4.martexcoin.org trying connection 52.32.234.211:51325 lastseen=156.7hrs connect() failed after select(): Connection refused |
|
|
|
THE PHANTOM OF THE ZPOOL
as promised. after all it's plain and simple 30% fee,
the only excuse could be compensating hype of mined shares' stats
is the same seen on BTC addresses?? I haven't been able to tell, but perhaps there is a different code path for non btc exchanging?? |
|
|
|
mmm.. i'm getting "connecting to remote pool" on nicehash
which stratum address? sha256.mine.zpool.ca:3333 strange... pool verification works... Pool verification process is complete. Tested pool is compatible! |
|
|
|
mmm.. i'm getting "connecting to remote pool" on nicehash
which stratum address? |
|
|
|
is sha256 mining working?
It is, but I just saw again it segfaulted. I'll be look into this some more today. I think some of my tuning didn't hold after a reboot so will reapply. Might see some more bumps as this is done. thanks! what was the difficulty misuse about anyway? using a diff not appropriate for their miner. generally it's best to let auto diff handle it, unless you're knowledgeable about and know the exact diff your miner performs best at. |
|
|
|
is sha256 mining working?
It is, but I just saw again it segfaulted. I'll be look into this some more today. I think some of my tuning didn't hold after a reboot so will reapply. Might see some more bumps as this is done. |
|
|
|
is sha256 mining working?
It is, but I just saw again it segfaulted. I'll be look into this some more today. |
|
|
|
The x11 24 estimate has broke. It is 2000 times what it should be: PS C:\Users\aaron> (Invoke-WebRequest -Uri " http://www.zpool.ca/api/status" | ConvertFrom-Json).x11 name : x11 port : 3533 coins : 22 fees : 2 hashrate : 37216621421 workers : 181 estimate_current : 0.00002672 estimate_last24h : 0.07634612 actual_last24h : 0.02446 rental_current : 0.02956473 lastbloc : 706987 timesincelast : 35 PS C:\Users\aaron> (Invoke-WebRequest -Uri " http://www.zpool.ca/api/status" | ConvertFrom-Json).scrypt name : scrypt port : 3433 coins : 43 fees : 2 hashrate : 2055694805 workers : 83 estimate_current : 0.00008249 estimate_last24h : 0.00008002 actual_last24h : 0.07668 rental_current : 0.08586065 lastbloc : 1885661 timesincelast : 247 looks like it's bitpoke again. I'll toast it. |
|
|
|
got disconnected several times in the last hour or so, everything ok with the sha256 pool?
Last stop causeConnection failed: Connection refused
should be ok now. looks like it was someone misusing the diff settings. still something going on with this port so running debug now. Hopefully will turn something up. The servers are due for a reboot/patch so I may do that later tonight. |
|
|
|
|
will be waiting for the BTCD swap.
|
|
|
|
Crackfoo, are you going to drop payment support of BTCD next month when the Komodo ICO starts?
why would I do that? On a similar note, I've been tossing around the idea of dropping the PoS coins altogether. I haven't been able to find someone willing to help me automate it. I would hope not; I like being paid in the POS coins. Although I can kind of understand your position; especially since whenever you tell us you are going on vacation the POS coins spend most of those periods short of funds. yup :\ |
|
|
|
|
Show Posts
