If the price of 1.78 BTC is accurate, there's no hope of ROI.
The bitcoinwisdom calculator came up with over 1188 days with no end in sight (that's as far ahead as the calculator will show) with a 3% difficulty increase, 2% pool fee, 20 day delivery (who knows when they'll ship), and free electricity.
I guess anyone buying these have to be optimistic about the difficulty flattening some months down the road after the spike once the L3 is released. Also they'd have to be willing to trust that the L3 will be more reliable than the S9.
As much as I'm intrigued by the idea of the L3, I'll probably sit this one out.
hoping they are able to handle multipools and you're chances of ROI will be much better. |
|
|
|
Well Sadly, I may have spoke too soon.
My A4 ran without a hiccup for over 5 days.
Today I shut it down, packed it up and took it to my remote site with better cooling for its full time placement.
I was gonna get a screen cap showing it running for over 5 days but forgot before I shut it down.
Transported the A4 and set it up at new location and it literally runs for 5 minutes and then reboots itself.
The only thing that has changed in this transition is the PSU but the same (2880) was previously running 2 s7's and now is running 1 S7 plus this A4, the S7 is doing fine.
Cards aren't dropping and this whole experience may be coincidence or maybe the PSU is having an issue as its the only thing that changed but either way.... more issues for me to deal with.
While I was typing this I just witnessed it reboot itself again.
That's the 6th reboot in about 30 minutes.
I'm pretty upset right now as this angers me more than words can describe so right now this is just the facts. I will share my thoughts about this later.
Same A4, Same Pool, Same Settings, different PSU and its rebooting every 5 minutes.
My guess its the PSU so I'm going to approach it from that standpoint.
In the interim this thing is probably going to hash upwards of a few days like this with 5 minute reboots... maybe it will magically start working? Who knows.
Network would be different as well. Might be useful to do some analyzing of connection latency as well. I'm not sure how the A4 work but perhaps if it thinks there is network issues it reboots as well? |
|
|
|
Was a fork ever chosen? I thought people where getting on the c-cex chain to send coins? is other exchange still on another chain?
actually those checkpoints secure the blockchain (see https://bitcointalk.org/index.php?topic=194078.0) to prevent additional chains with really fast asics now the chain used by ccex and dutch-mining is off of the "official" one, but thats another matter if one wants to sync to the official chain i suggest using the addnodes provided by nova the other way round use those by ccex well aware of the reasons for having checkpoint blocks, just as well as their potential for abuse. trying connection 208.163.158.201 lastseen=0.0hrs
received block 00000f8923e2585d5cbd
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49
ProcessBlock: ACCEPTED
received block 00000047b8d42ab011bc
SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15
ProcessBlock: ACCEPTED
received block 0000004b8b45189977df
* hyuck, we're gonna need minimum PoW 1e0fffff
SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17
ProcessBlock: ACCEPTED
received block 000000299fe41f7a5aa0
* hyuck, we're gonna need minimum PoW 1e09a06c
ERROR: AcceptBlock() : incorrect proof-of-work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 92.63.57.24:5556 (0 -> 100) DISCONNECTING
disconnecting node 92.63.57.24
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
for the sake of being a team player, rather than a dick; check the 'hyucks' above. some debug code i've thrown in whilst attempting to sync against the 'official' nodes. block 4 needs to be 1e09a06c, but in xenixblockchain.com; it is listed as 1e0340dac-cex has been on the correct chain from the start; not sure what happened with nova. one page back. novaexchange runs a chain that doesnt currently sync with any source. just tried (2 minutes ago, with official dev source https://github.com/xenixcoin/xenixcoin.git):  i've forked the existing repo, fixed it and it syncs to c-cex's chain in minutes ( https://github.com/barrystyle/xenixcoin.git). even dev's own repo will sync to c-cex's chain if sufficient nodes are available. I was still going to tell you. Anyway I remove the coin of my pool at the end of the month
You must comment on lines 2149 and 2150 in main.cpp
And recompile.
Once syncro decomment the lines and recompile again
And even to watch that its does not happen again
// Check proof-of-work or proof-of-stake
if (nBits != GetNextTargetRequired(pindexPrev, IsProofOfStake()))
return DoS(100, error("AcceptBlock() : incorrect %s", IsProofOfWork() ? "proof-of-work" : "proof-of-stake")); you're kidding right? you mean 'oh, just uncomment the code that verifies each block as it comes through'. im gonna throw a bit of hashrate at this shortly via rental if anyone else would like to join in how to join? i don't find where is to download the wallet i see on the explorer, new coin only generated 0.08 xenix each block When I tried mining this, I was getting 19 XEN per block but then the chain would eventually re-organize and my blocks would orphan... the spec of the coin say it's 19 per block.... |
|
|
|
When I try and mine with keccak, I get rejects:
ThreadRPCServer method=submitblock
ERROR: CheckBlock() : hashMerkleRoot mismatch
ERROR: ProcessBlock() : CheckBlock FAILED
Merkleroot hash is always sha256d but it's set to keccak... MAXcoin works just fine on keccak... Am I missing something? maxcoin use single sha256 for coinbasetx (and all tx hash): https://github.com/tpruvot/cpuminer-multi#L1676-L1679while joincoin use double sha256 for all tx. ohhh. so I guess it's not compatible with yiimp's/cpuminer keccak... |
|
|
|
When I try and mine with keccak, I get rejects:
ThreadRPCServer method=submitblock
ERROR: CheckBlock() : hashMerkleRoot mismatch
ERROR: ProcessBlock() : CheckBlock FAILED
Merkleroot hash is always sha256d but it's set to keccak... MAXcoin works just fine on keccak... Am I missing something? |
|
|
|
|
When I try and mine with keccak, I get rejects:
ThreadRPCServer method=submitblock
ERROR: CheckBlock() : hashMerkleRoot mismatch
ERROR: ProcessBlock() : CheckBlock FAILED
Any ideas?
./bin/joincoind-keccak getinfo
J keccak
{
"version" : 1030200,
"protocolversion" : 1006,
"walletversion" : 100,
"balance" : 0.00000000,
"blocks" : 655001,
"timeoffset" : 0,
"connections" : 7,
"proxy" : "",
"pow_algo_id" : 10,
"pow_algo" : "keccak",
"difficulty" : 460.18487533,
"difficulty_sha" : 50712.61125739,
"difficulty_x11" : 21.58866274,
"difficulty_x13" : 1.09693024,
"difficulty_x15" : 1.30805772,
"difficulty_scrypt" : 4.33803726,
"difficulty_nist5" : 15.56491970,
"difficulty_groestle" : 20.69913573,
"difficulty_pentablake" : 61.49371023,
"difficulty_whirlpool" : 162.36920039,
"difficulty_luffa" : 194.23847730,
"difficulty_keccak" : 460.18487533,
"difficulty_quark" : 1.87725580,
"difficulty_bastion" : 0.12582486,
"testnet" : false,
"keypoololdest" : 1483533924,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
}
|
|
|
|
I know Crackfoo mentioned they had to upgrade their stratum to get better has rates. I wonder if that is what Prohashing did. It will be great news for A4 and Titan owners if that is the case.
yeah that was for the www.zpool.ca stratums, I'm not really sure what ph is running behind the scenes. |
|
|
|
Hi, I've re-enabled join on www.zpool.ca with algos: nist5, quark, scrypt, sha256, x11, x13, x15 Cheers! We've added keccak algo now. Cheers |
|
|
|
good luck. Had bad exprience with them when using MRR with them.
I often rent from MRR on www.zpool.ca and don't ever see issues. Only with the rig themselves. Usually the hash rate is above the stated rig rate. One time i tried payout was about halfwhat it should have been. Might be because i rented Titan (bad at switching), but i don't remeber. Perhaps. We've only recently implemented changes to the stratum server to help with high speed ASICs... |
|
|
|
good luck. Had bad exprience with them when using MRR with them.
I often rent from MRR on www.zpool.ca and don't ever see issues. Only with the rig themselves. Usually the hash rate is above the stated rig rate. |
|
|
|
|
ohh interesting. will be keeping an eye on this
|
|
|
|
Hi,
We have added RADS as an official payout coin on our multipool: www.zpool.ca
I hope you can bring good support from miners. We offer 10+ algos to mine and over 100 altcoins.
Cheers! We'll be turning off the RADS wallet Jan 1st 2017 so if you're mining with a RADS address please take that into consideration and move to a BTC address. Cheers! |
|
|
|
Which is the wdc pool with most hashrate?
we have ~40% of WDC last 100 blocks... www.zpool.caCheers |
|
|
|
I tried the A4s on several multi-algo pools, and for the first time I see the A4s hitting and above the intended hashrate and staying there long enough. I am mining at a multi-algo pool; zpool.ca
The op asked me to try 65536 x 2 = 131072 as the diff level. I was not able to set diff level more than 65536 in other pools.
My A4s are B3 with v2.02 firmware - I was lucky to get B3 and only had to upgrade the firmware.
My cubes are setup a bit differently ~ 417MHs per A4.
Anyways, just sharing my findings.
Go and try and see if it works for your A4s. Pays direct to BTC too
Pool: stratum+tcp://scrypt.mine.zpool.ca:3433
Userid: BTC or coin address.
Password: c=BTC d=131072
Password: c=BTC,d=131072
No registration
Thanks for testing your A4 out citronick, just a note though, for the password, make sure you separate password options with commas... |
|
|
|
|
perhaps the seed nodes are down too?
|
|
|
|
already did that.The same happened to both my laptop and my pc
can't connect to the network
tried deleting all files but wallet
reinstalled the wallet
still the same
block source is not available and 0 connection to bitcoin network is all i get
i also have same problem. hrmm, I've just had to reboot my servers and low and behold... none of my wallets connect either.... something a bit odd has happened.... any ideas devs? ----edit I suspect its perhaps some issues over the tor network.... I went to the length of install the standalone tor daemon... join wallet: trying connection ozkzcn3gp34dx5mp.onion:17941 lastseen=384153.9hrs Dec 28 14:34:50.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for circuit) Dec 28 14:34:51.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. Dec 28 14:36:51.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:36:51.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:38:52.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:38:52.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:38:59.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Dec 28 14:39:02.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Dec 28 14:39:03.000 [warn] Fetching v2 rendezvous descriptor failed. Retrying at another directory. Dec 28 14:39:05.000 [notice] Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later). Dec 28 14:40:53.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:41:08.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for circuit) Dec 28 14:42:54.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for rendezvous desc) Dec 28 14:43:11.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:17941. Giving up. (waiting for circuit) when I rebooted, I had 15-20 peers on my wallets... |
|
|
|
|
Show Posts
