Huh? Bcash? Never heard of of it. Did you mistake that for Bitcoin Cash (BCC)?
Proponent spotted. |
|
|
|
By the way, if anyone is looking for my recommendation for what to do about the August 1 fork that just happened, I recommend that anyone who had bitcoin holdings at the time of the fork safely get hold of their bitcoin cash and sell it all ASAP for bonus bitcoin though it's tricky at the moment due to slow blocks and exchanges. hitbtc.com is one of the easiest ways to move it directly to btc. Here's a bit of a guide about how to proceed: https://bitcointalk.org/index.php?topic=2059111.0Most importantly, make sure to move your real bitcoin to new addresses before selling your bitcoin cash to prevent replay protection from trashing your bitcoin and don't let the bcash software anywhere near your secure bitcoin data. how do I know if I have BCH ? If you had bitcoin at ~12:20 UTC on August 1st you have bch. |
|
|
|
By the way, if anyone is looking for my recommendation for what to do about the August 1 fork that just happened, I recommend that anyone who had bitcoin holdings at the time of the fork safely get hold of their bitcoin cash and sell it all ASAP for bonus bitcoin though it's tricky at the moment due to slow blocks and exchanges. hitbtc.com is one of the easiest ways to move it directly to btc. Here's a bit of a guide about how to proceed: https://bitcointalk.org/index.php?topic=2059111.0Most importantly, make sure to move your real bitcoin to new addresses before selling your bitcoin cash to prevent replay protection from trashing your bitcoin and don't let the bcash software anywhere near your secure bitcoin data. |
|
|
|
What I find weird about the BCash chain is that the blocks seem to come in bursts... one block takes hours to mine, then one or two blocks follow in 10-30 minutes time.
Big entities are intermittently mining it in order to sell off their free bcash crap. None of them are committed to the chain. |
|
|
|
|
My guess is some big entities are mining blocks just to get rid of their free bcc crap because lack of block movement makes it hard to trade that shit otherwise.
|
|
|
|
Hi everyone, noob member here introducing myself for the first time! Been enjoying mining solo on here for sometime so I figured I'd speak up and say hello. Also, thank you CK for all that you do and the services you provide this community, very appreciative. Cheers everyone, have a great day!  Cheers. Welcome, enjoy and good luck! |
|
|
|
|
There is a place for it. It joins the rest of the altcoins. This is the bitcointalk forum.
|
|
|
|
|
Don't worry, they'll start being moved shortly.
|
|
|
|
|
Nope. The real drama hasn't even begun yet. The biggest hurdle has always been the 2x deployment part of segwit2x that's due in 3 month's time.
|
|
|
|
And miners wouldn't like increasing the block size either because that will lower the fees they gather in the short term. It would also mean that their nodes (which I'm told that many use fairly low end hardware) could be very negatively effected by various exhaustion attacks that come with larger blocks. So really miners want smaller blocks, not larger blocks.
That's not entirely true. Lots of mining entities want bigger blocks because $ignorance and $stupidity. They got it into their head that it was the best way to earn more fees long term and have been unable to believe anything else since. |
|
|
|
I am not ck but the answer to that question is:
you can use older cgminer Versions, but not an old core version.
So you need as minimum core version 14.0.0 (Segwit support)
AND
you have to add a patch to it so you are not building up on wrong blocks!
Can -ck confirm this please? You need minimum bitcoin core 0.14.0, correct. Older versions of cgminer that don't explicitly have segwit support but have solo mining support will still be able to mine valid blocks but they will only mine classic transactions without the segwit commitment or any segwit transactions so realistically you should be using the latest cgminer as well. |
|
|
|
Just registered to chime in as I happened to be running into this myself and had thought it might be a quirk from compiling/running with MacOSX. I haven't done much digging into it, and when I get a chance I'll try the debug backtrace mentioned already. I can also confirm that on my system the problem arises between 4.9.2 and 4.10.0 releases.
In case it might be useful to those more familiar with the code, a few crude tests by way of re-building seem to isolate the problem to setting '--enable-icarus' during configuration. That is, including all of the non-standalone drivers minus icarus seems to have a functioning write_config on my system. So do not think this is something to do with all parsing/writing for settings, but may be specific to one or more introduced with icarus support.
Sounds feasible. It's likely to be missing save for the options added to icarus post 4.9.2 |
|
|
|
Every little bit counts. Thanks for joining us. Just dropped in to say thanks to everyone who's still hashing here. Keep on hashing, we'll crack one sooner or later  |
|
|
|
Is it only me or others also constantly getting messages about testing pool on solo mining?
One more issue to mention, 4.10.0 does not write config file and does not load working in v.4.9.2 (and pretty trivial one) config file.
Don't know if related, but the parameter --fix-protocol seems to prevent switching from gbt to stratum if the http server offers both. Regarding the other issues: don't know, haven't tried yet; I'm passing all parameters via commandline (actually in a batch script file). Thanks for the reply. Do I need to upgrade the miner to 4.10.0 at all to mine a segwit blocks? The backend is bitcoin core 0.14.2. No. Current cgminer is segwit compatible. |
|
|
|
CK, do you plan to setup a second pool for solo mining on Bitcoin Cash (BCH)? The fork is happening.
No. It will be yet another insignificant fork. There's far too much fuss about it just because of its timing being associated with the real changes to bitcoin. It's irrelevant. |
|
|
|
|
The higher a pool's hashrate the less your variance is (unless the pool is PPS in which case the pool size makes no difference.) A small pool variance over the short to medium term means you could end up with far less reward, but conversely you could also end up with far more reward. Pool hashrate does not affect your expected earnings. The only difference between pools in expected reward over a long period is the pool fee and whether the pool pays out transaction fees to miners or not.
|
|
|
|
Hi, i wanna try Solo Mining with rented hashrate, How much do i have to Rent and what diff should the rented rig have?
The diff doesn't matter and the hashrate is as much as you are willing to gamble on it. A lot of hashrate for a short period is exactly the same as a little bit of hashrate for a long period. The only difference is whether you get your hashes in before the next diff change, so if network diff is set to rise, you should do more hashrate for less time. |
|
|
|
|
Show Posts
