@Picolo and Beachguy!
Duly Noted. Pass on to the engineers
How about fixing the inability to connect to a regular BTC node for mining.... |
|
|
|
Thanks notlist3d and dogie,
I will wait for new firmware that Bitmain will have to post due to some broken miners that may have gotten shipped.
Also, because I have no energy and time left budgeted for this miner over this weekend.
My only frustration is is that despite known problems in shipped miners, Bitmain has not reacted promptly to provide easy solutions to problems like firmware.
My C1 is operational for now though I have to run it at lower speed and manage it with stupid alternatives e.g. saving miner configuration still does not make all pools operational, (it is random but limited to first pool dead in most cases).
I have to run cgminer from command shell using ssh to make it work.
Thanks for your advise Tupsu, will keep that in mind and that precious link.
regards
The problem you described appears to be a bad SD card which isn't going to be fixed with new firmware. I just read this entire thread. I have a solo setup and previously had an S1 on it with no issues and I cannot get the C1 to work. It works with other pools no problem but no matter what I have tried it always comes up "dead" on the C1 . The S1 for the URL I just had x.x.x.x:port and then it would add the http:// on front and work fine (mostly/bit flaky still).. the C1 adds the "stratum+tcp://" and even when I set it to http://*.*.*.*:port it still shows up as dead. Is there something different that needs to be done in the C1s? This quoted post is the only thing I found semi similar but even in different pool slots other than #1 it still is always dead. Everything else is taken care of ie node is fine and other miners including S1 connect fine and ip is in the rpcallow in the conf. Any ideas.. it is 11/26 firmware My own server has worked exactly 1 time in the last few days of messing with it.. then I changed another unrelated setting and reapplied and poof... hasn't worked again since. S1's work absolutely no problem. I even switch IPs between S1/C1 no matter what the C1 just shows up dead pool for no reason I can see. Pretty sure whatever the problem is it is the C1... This is absolutely pissing me off. It appears as it is C1 does not work with the standard BTC node solo mining. I tried CG 4.61 by itself and it asks for “--btc-address” and would not connect to a server until supplied. I think this is the reason it is not functional. I must have been seeing things when I thought it worked once. This is the last response from bitmain after multiple low comprehension emails. "Sorry to hear that. there may be some incompatibles with solo mining for C1." They keep telling me to use their pool and even told me I could user their "solo" setup which sounds like a complete joke... "suggest you consider to mine with antpool directly. We're using solo mining and will distribute the payment once blocks are found. stratum.antpool.com:3333, or solo.antpool.com:3333, solo.antpool.com:25 " Is there a way to supply arguments to firmware containing CG to actually fix my issue? I really expect to be able to connect to the standard client as a server.. seems pretty fundamental for btc mining equipment to be able to do. I understand everyone is very eager to say how stupid solo is.. I don't care, I am mostly using it to be involved / gambling and for heat... |
|
|
|
Thanks notlist3d and dogie,
I will wait for new firmware that Bitmain will have to post due to some broken miners that may have gotten shipped.
Also, because I have no energy and time left budgeted for this miner over this weekend.
My only frustration is is that despite known problems in shipped miners, Bitmain has not reacted promptly to provide easy solutions to problems like firmware.
My C1 is operational for now though I have to run it at lower speed and manage it with stupid alternatives e.g. saving miner configuration still does not make all pools operational, (it is random but limited to first pool dead in most cases).
I have to run cgminer from command shell using ssh to make it work.
Thanks for your advise Tupsu, will keep that in mind and that precious link.
regards
The problem you described appears to be a bad SD card which isn't going to be fixed with new firmware. I just read this entire thread. I have a solo setup and previously had an S1 on it with no issues and I cannot get the C1 to work. It works with other pools no problem but no matter what I have tried it always comes up "dead" on the C1 . The S1 for the URL I just had x.x.x.x:port and then it would add the http:// on front and work fine (mostly/bit flaky still).. the C1 adds the "stratum+tcp://" and even when I set it to http://*.*.*.*:port it still shows up as dead. Is there something different that needs to be done in the C1s? This quoted post is the only thing I found semi similar but even in different pool slots other than #1 it still is always dead. Everything else is taken care of ie node is fine and other miners including S1 connect fine and ip is in the rpcallow in the conf. Any ideas.. it is 11/26 firmware My own server has worked exactly 1 time in the last few days of messing with it.. then I changed another unrelated setting and reapplied and poof... hasn't worked again since. S1's work absolutely no problem. I even switch IPs between S1/C1 no matter what the C1 just shows up dead pool for no reason I can see. Pretty sure whatever the problem is it is the C1... This is absolutely pissing me off. |
|
|
|
Thanks notlist3d and dogie,
I will wait for new firmware that Bitmain will have to post due to some broken miners that may have gotten shipped.
Also, because I have no energy and time left budgeted for this miner over this weekend.
My only frustration is is that despite known problems in shipped miners, Bitmain has not reacted promptly to provide easy solutions to problems like firmware.
My C1 is operational for now though I have to run it at lower speed and manage it with stupid alternatives e.g. saving miner configuration still does not make all pools operational, (it is random but limited to first pool dead in most cases).
I have to run cgminer from command shell using ssh to make it work.
Thanks for your advise Tupsu, will keep that in mind and that precious link.
regards
The problem you described appears to be a bad SD card which isn't going to be fixed with new firmware. I just read this entire thread. I have a solo setup and previously had an S1 on it with no issues and I cannot get the C1 to work. It works with other pools no problem but no matter what I have tried it always comes up "dead" on the C1 . The S1 for the URL I just had x.x.x.x:port and then it would add the http:// on front and work fine (mostly/bit flaky still).. the C1 adds the "stratum+tcp://" and even when I set it to http://*.*.*.*:port it still shows up as dead. Is there something different that needs to be done in the C1s? This quoted post is the only thing I found semi similar but even in different pool slots other than #1 it still is always dead. Everything else is taken care of ie node is fine and other miners including S1 connect fine and ip is in the rpcallow in the conf. Any ideas.. it is 11/26 firmware |
|
|
|
Thanks for contacting my store! You can now get over 4000 wanking accessories to make sure you (and her) get the perfect wank every single time! www.cryptosextoys.com A 2,000$ ass dildo.. that's perfectly acceptable. |
|
|
|
|
whats next peso.. sheckle.. ruble... what a tool
|
|
|
|
The irony is everyone was too busy bitching and moaning about all the NUD they lost after the blockchain reset to realize that CPU mining was piss easy. I solo mined more NUD with 3 desktop CPUs and 1 laptop in the week after the reset than I did BEFORE the blockchain reset with scrypt mining.
Testify... I thought I was an idiot mining what the network hash was saying was a dead coin. |
|
|
|
i can get coin listed on bittrex for around 2BTC - i mean, thats their price not mine
Bill will add coins when they think the coin is good enough to get listed. No need to pay 2BTC. I already spoke with him about adding NUD before we even had the blockexplorer. Give it some time, i expect NUD willbe added in less then a week. guys,bill will not add any coin without give him 3 btc. it is a market price.2 btc is no enough now. If the choice is pay BTC or don't get added to bittrex for months, I choose don't get added to bittrex for months. Has the dev team even received a total of 2 BTC worth of donations yet? I haven't checked the thread in a few days but my guess is no. 2-3 BTC is much better spent on development rather than paying an exchange to add NUD. If development continues and more and more planned features are added, exchanges will be clamoring to add NUD. Patience! IDK about the exchange angle seems like alot of shady bullshit and shitcoins. NUD for me is like the so so chick you liked in school... then over summer she developed a fantastic rack... Let it develop. |
|
|
|
Edison was nothing compared to Tesla.
This ^ Did Tesla propose a monetary system? don't see how he is relevant here. Dev I sent you a little surprise. |
|
|
|
was all excited till i saw the picture of edison.....failed coin right there.....if you dont know simple history about the person you have on youre coin you are a complete fn moron.....this coin will fail no doubt about it.
... who else gets electricity form ComEd IE... Commonwealth EDISON. Maybe they are on the verge of bankruptcy for a poorly chosen name lol Anyone that is going to take time to bitch about the name of a coin or marketing (especially in a D bag manor) goes right on my ignore list. |
|
|
|
to the Poon  |
|
|
|
OK, assuming this isn't a bug in their pool, if they downloaded the source code from trunk and compiled their own daemon, that could cause problems. The new version wasn't ready for release yet and the nodes haven't even been updated. If they did that, they to go back to using 0.8.6 like the rest of the network.
Shhhh |
|
|
|
•Per-block difficulty adjustments, was suppose to start in July, but, dif just skyrocketed to 12,563,358.13519800
What's going on?
The per-block difficulty adjustments will be part of the version released the first week of July. That's what I thought, but it is happening now. The dif has gone up on the last 7 blocks, currently at dif 14,303,674.4882 So explain this? { "version" : 80600, "protocolversion" : 70001, "walletversion" : 60000, "blocks" : 45009, "difficulty" : 5994149.47859651, } |
|
|
|
|
I am usually near the top of CPU coins with pretty good setup. I was near the top in dark x11 pools for weeks before GPU miners came out with a few people with a few MP Xeon setups above me. Hash rate of the highest user for this coin hours after launch with an new algo is 400X my multi cpu setup. Doesn't smell right.
|
|
|
|
yeah but this fixed WKC price is brilliant... Why would you sell for a third of the price... better buy three months membership then....
I agree. It's worth 10 cents there, why people are selling it for less is beyond me. You can use that same logic for why it should never go over 10c , not a fan of trying to fix the price. |
|
|
|
Props for following through with what you said you intended to create you just should have tested it a bit more before launch.
To people complaining about conversion rates I assume you could read and did read the first post before scrypt mining. No sympathy here.
What's the problem? The network is running perfectly fine, isn't it? It is for me. Not sure what your referring to, I have no problem. If your referring to the "tested a bit more before launch" I am talking about the bcrpt/scrypt on launch. |
|
|
|
|
Props for following through with what you said you intended to create you just should have tested it a bit more before launch.
To people complaining about conversion rates I assume you could read and did read the first post before scrypt mining. No sympathy here.
|
|
|
|
was "bcrypt" ever addressed? or was this just an "mistake" to throw scrypt people of the scent while it was raped?
Well, it would be raped if scrypt people knew about it, so I'm not exactly sure the point there? Anyway.. we need to keep pushing this thread guys. This coin has innovation. Unlike most of the last few pages of clones. The point is who gets to do the raping... the coin is currently raped in comparison to a cpu algo launch. Seems like it was launched as a scrypt intentionally but tried to hide that fact..(so just raped by in the know) "Since NUD is a CPU coin and is very likely to remain so in the foreseeable future your rewards would be large and the potential to earn for your effort maximized. No other mining methods except the official client are available." I had been looking for a good cpu algo coin, to launch it as such and then have it minable by scrypt is a complete joke. I'm guessing it was a mistake. You might want to check out slimcoin for a nice cpu coin. Nah doesn't interest me, accessible hash algo alone is no reason to use a coin. I have plenty of good mining equipment, my concern is in regards to integrity and launch shenanigans. |
|
|
|
was "bcrypt" ever addressed? or was this just an "mistake" to throw scrypt people of the scent while it was raped?
Well, it would be raped if scrypt people knew about it, so I'm not exactly sure the point there? Anyway.. we need to keep pushing this thread guys. This coin has innovation. Unlike most of the last few pages of clones. The point is who gets to do the raping... the coin is currently raped in comparison to a cpu algo launch. Seems like it was launched as a scrypt intentionally but tried to hide that fact..(so just raped by in the know) "Since NUD is a CPU coin and is very likely to remain so in the foreseeable future your rewards would be large and the potential to earn for your effort maximized. No other mining methods except the official client are available." I had been looking for a good cpu algo coin, to launch it as such and then have it minable by scrypt is a complete joke. |
|
|
|
|
was "bcrypt" ever addressed? or was this just an "mistake" to throw scrypt people of the scent while it was raped?
|
|
|
|
|
Show Posts
