"blktmpl error: Unrecognized block version, and not allowed to reduce or force it"

when trying to mine to a bitcoin classic node. Will this require an updated version of libblkmaker? looking at bitcoin-cli getblocktemplate I see

I don't support altcoins. When/if Classic actually proposes a hardfork (no such proposal has been made yet) and it achieves consensus to replace Bitcoin (from the entire community, not merely some niche with an agenda), I will add support at that time.

(Also, people who support a reckless hardfork without consensus, ought to seriously consider whether they think the project can actually survive without any competent developers involved...)

"blktmpl error: Unrecognized block version, and not allowed to reduce or force it"

when trying to mine to a bitcoin classic node. Will this require an updated version of libblkmaker? looking at bitcoin-cli getblocktemplate I see

I don't support altcoins. When/if Classic actually proposes a hardfork (no such proposal has been made yet) and it achieves consensus to replace Bitcoin (from the entire community, not merely some niche with an agenda), I will add support at that time.

(Also, people who support a reckless hardfork without consensus, ought to seriously consider whether they think the project can actually survive without any competent developers involved...)

I figured your reply would be something like that. I wont be a jerk and ask why scrypt asics are supported if you dont support altcoins.

"blktmpl error: Unrecognized block version, and not allowed to reduce or force it"

when trying to mine to a bitcoin classic node. Will this require an updated version of libblkmaker? looking at bitcoin-cli getblocktemplate I see

I don't support altcoins. When/if Classic actually proposes a hardfork (no such proposal has been made yet) and it achieves consensus to replace Bitcoin (from the entire community, not merely some niche with an agenda), I will add support at that time.

(Also, people who support a reckless hardfork without consensus, ought to seriously consider whether they think the project can actually survive without any competent developers involved...)

I figured your reply would be something like that. I wont be a jerk and ask why scrypt asics are supported if you dont support altcoins.

I don't maintain the scrypt support, and certainly don't provide [unpaid] support if someone has problems with some scrypt altcoin.

"blktmpl error: Unrecognized block version, and not allowed to reduce or force it"

when trying to mine to a bitcoin classic node. Will this require an updated version of libblkmaker? looking at bitcoin-cli getblocktemplate I see

I don't support altcoins. When/if Classic actually proposes a hardfork (no such proposal has been made yet) and it achieves consensus to replace Bitcoin (from the entire community, not merely some niche with an agenda), I will add support at that time.

(Also, people who support a reckless hardfork without consensus, ought to seriously consider whether they think the project can actually survive without any competent developers involved...)

I figured your reply would be something like that. I wont be a jerk and ask why scrypt asics are supported if you dont support altcoins.

I don't maintain the scrypt support, and certainly don't provide [unpaid] support if someone has problems with some scrypt altcoin.

So if someone else submits a PR that allows bfgminer to work with a bitcoin classic node, you'll merge it? (That is, if someone else "maintains" the bitcoin classic support)?

"blktmpl error: Unrecognized block version, and not allowed to reduce or force it"

when trying to mine to a bitcoin classic node. Will this require an updated version of libblkmaker? looking at bitcoin-cli getblocktemplate I see

I don't support altcoins. When/if Classic actually proposes a hardfork (no such proposal has been made yet) and it achieves consensus to replace Bitcoin (from the entire community, not merely some niche with an agenda), I will add support at that time.

(Also, people who support a reckless hardfork without consensus, ought to seriously consider whether they think the project can actually survive without any competent developers involved...)

I figured your reply would be something like that. I wont be a jerk and ask why scrypt asics are supported if you dont support altcoins.

I don't maintain the scrypt support, and certainly don't provide [unpaid] support if someone has problems with some scrypt altcoin.

So if someone else submits a PR that allows bfgminer to work with a bitcoin classic node, you'll merge it? (That is, if someone else "maintains" the bitcoin classic support)?

If it isn't Classic-specific (ie, generalised), doesn't affect libblkmaker itself, and doesn't degrade Bitcoin support in any way.

But a more practical way would be to have Classic's bitcoind simply set sizelimit to 2 MB and use the version/force mutation in BIP 23.I think that would result in something that actually works with unmodified BFGMiner/libblkmaker.

I am trying to downclock my 700gh monarch that is shutting down my psu at only 65c with the V5X command and it does not seem to get through,the card stills shutdown and does not downclock.I tried with 4.2.0 (bfl version) and 5.4.1 and with 2 different Lepa 1200w psu's

Should I see a confirmation in the bfgminer window when sending this command ?

If you wanted to learn about computers would you study an Amiga from the 1980s? No, of course not.

So if you want to learn about bitcoin mining why on earth would you try to cpu mine? No one supports cpu bitcoin mining anymore because tech has progressed way way way beyond that. Nothing you might learn there would be applicable to the world of asic mining.

Get a Gekko compac stick or buy a used S3, they're easy to use, cheap, and you can actually learn something useful from them.

i did have it on S1 S3 and S5 the only one i could get it to hash on was a S5 . for S1 and S3 it worked but wouldn't hash even posted a few pages back asking what might be wrong no one seemed to care, so i gave up.

even had the right openwrt links set up right in the opkg.conf file . you have to go to the open WRT site and find the old links to attitude_adjustment/12.09/ar71xx/packages/Packages.gz, they have sense been archived sense they kind of are no longer supported .

i wanted to at least get it working on a s1 and s3 but didn't happen for me,and the problem with S5 it works great seems to work better then the cgminer version bitmain hacked in but after a reboot it's gone :. bitmain set it up that way, sigh.