Download cgminer 3.7.2 with GPU support for Windows ...


Aeon (AEON) is a private, secure, untraceable currency. You are your bank, you control your funds, and nobody can trace your transfers.

DigiByte Mining Pool - Official Launch - 50,000 DGB Giveaway!

DigiByte Mining Pool - Official Launch - 50,000 DGB Giveaway!
I have been working hard on the front-end of my pool for the past couple of months. Anyone who saw v1.0 will be shocked to see the progress it's made. It now has a fantastic front-end with detailed charts, graphs, and user stats, all in a sleek Bootstrap 4.0 layout.
Miners....come join us at
I wanted to offer support for all Algo's, and initially, I did. But after talking with DigiByte developers, and taking their advice this was changed to support only Scrypt and SHA256D. Until ProgPOW is implemented GPU mining is pointless, so this ultimately is why I chose Scrypt and SHA256D.
Another feature of the pool is BTC and LTC Solo Mining for any of you guys out there that have some gear that's not profitable to mine with anymore and just want to play the blockchain lottery. Wouldn't it be nice to wake up with 6.25 Bitcoin in your wallet one morning?
General Pool Features are:
  • Asic-Boost Supported
  • Ultra-efficient handcrafted code
  • Transaction fees paid to miners
  • VarDiff & Static Diff Supported
  • Anonymous mining to your wallet
  • Solo Mining
  • No withdraw fees
  • No registration
  • No pool wallets
Ready to join up? Head over to to get started.
PS - Did I mention we're going to give one lucky miner 50,000 DigiByte?
Want to know more about the Giveaway?
submitted by WeDontServeYourKind to Digibyte [link] [comments]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs:
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2
How to CPU Mine NewEnglandcoin (NENG) in macOS
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at:
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up:
NENG v1.4.0 Android Mining, randomSpike Evaluation
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal
NENG Security, Decentralization & Valuation
Whitepaper v1.0
Step by step guide on how to setup an explorer:
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf):
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE):
MacOS Wallet (10.11 El Capitan or higher):
Android with GNUroot on 32 bits old Phones (alpha release) wallet:
Windows wallet:
addnode ip address for the wallet to sync faster, frequently updated conf file:
How to Sync Full Node Desktop Wallet
Cheetah CPU Miner Software
Solo Mining with GPU or ASIC
How to Run Two Full Node in Same Desktop PC
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
Cminors' Pool
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows
Dec 31, 2018 - Technical Whitepaper is Released
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC
Nov 29, 2018 - A Warning to ASIC Miners
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

Transcript of discussion between an ASIC designer and several proof-of-work designers from #monero-pow channel on Freenode this morning

[08:07:01] lukminer contains precompiled cn/r math sequences for some blocks:
[08:07:11] try that with RandomX :P
[08:09:00] tevador: are you ready for some RandomX feedback? it looks like the CNv4 is slowly stabilizing, hashrate comes down...
[08:09:07] how does it even make sense to precompile it?
[08:09:14] mine 1% faster for 2 minutes?
[08:09:35] naturally we think the entire asic-resistance strategy is doomed to fail :) but that's a high-level thing, who knows. people may think it's great.
[08:09:49] about RandomX: looks like the cache size was chosen to make it GPU-hard
[08:09:56] looking forward to more docs
[08:11:38] after initial skimming, I would think it's possible to make a 10x asic for RandomX. But at least for us, we will only make an ASIC if there is not a total ASIC hostility there in the first place. That's better for the secret miners then.
[08:13:12] What I propose is this: we are working on an Ethash ASIC right now, and once we have that working, we would invite tevador or whoever wants to come to HK/Shenzhen and we walk you guys through how we would make a RandomX ASIC. You can then process this input in any way you like. Something like that.
[08:13:49] unless asics (or other accelerators) re-emerge on XMR faster than expected, it looks like there is a little bit of time before RandomX rollout
[08:14:22] 10x in what measure? $/hash or watt/hash?
[08:14:46] watt/hash
[08:15:19] so you can make 10 times more efficient double precisio FPU?
[08:16:02] like I said let's try to be productive. You are having me here, let's work together!
[08:16:15] continue with RandomX, publish more docs. that's always helpful.
[08:16:37] I'm trying to understand how it's possible at all. Why AMD/Intel are so inefficient at running FP calculations?
[08:18:05] midipoet ([email protected]/web/ has joined #monero-pow
[08:18:17] hardware development works the other way round. We start with 1) math then 2) optimization priority 3) hw/sw boundary 4) IP selection 5) physical implementation
[08:22:32] This still doesn't explain at which point you get 10x
[08:23:07] Weren't you the ones claiming "We can accelerate ProgPoW by a factor of 3x to 8x." ? I find it hard to believe too.
[08:30:20] sure
[08:30:26] so my idea: first we finish our current chip
[08:30:35] from simulation to silicon :)
[08:30:40] we love this stuff... we do it anyway
[08:30:59] now we have a communication channel, and we don't call each other names immediately anymore: big progress!
[08:31:06] you know, we russians have a saying "it was smooth on paper, but they forgot about ravines"
[08:31:12] So I need a bit more details
[08:31:16] ha ha. good!
[08:31:31] that's why I want to avoid to just make claims
[08:31:34] let's work
[08:31:40] RandomX comes in Sep/Oct, right?
[08:31:45] Maybe
[08:32:20] We need to audit it first
[08:32:31] ok
[08:32:59] we don't make chips to prove sw devs that their assumptions about hardware are wrong. especially not if these guys then promptly hardfork and move to the next wrong assumption :)
[08:33:10] from the outside, this only means that hw & sw are devaluing each other
[08:33:24] neither of us should do this
[08:33:47] we are making chips that can hopefully accelerate more crypto ops in the future
[08:33:52] signing, verifying, proving, etc.
[08:34:02] PoW is just a feature like others
[08:34:18] sech1: is it easy for you to come to Hong Kong? (visa-wise)
[08:34:20] or difficult?
[08:34:33] or are you there sometimes?
[08:34:41] It's kind of far away
[08:35:13] we are looking forward to more RandomX docs. that's the first step.
[08:35:31] I want to avoid that we have some meme "Linzhi says they can accelerate XYZ by factor x" .... "ha ha ha"
[08:35:37] right? we don't want that :)
[08:35:39] doc is almost finished
[08:35:40] What docs do you need? It's described pretty good
[08:35:41] so I better say nothing now
[08:35:50] we focus on our Ethash chip
[08:36:05] then based on that, we are happy to walk interested people through the design and what else it can do
[08:36:22] that's a better approach from my view than making claims that are laughed away (rightfully so, because no silicon...)
[08:36:37] ethash ASIC is basically a glorified memory controller
[08:36:39] sech1: tevador said something more is coming (he just did it again)
[08:37:03] yes, some parts of RandomX are not described well
[08:37:10] like dataset access logic
[08:37:37] RandomX looks like progpow for CPU
[08:37:54] yes
[08:38:03] it is designed to reflect CPU
[08:38:34] so any ASIC for it = CPU in essence
[08:39:04] of course there are still some things in regular CPU that can be thrown away for RandomX
[08:40:20] uncore parts are not used, but those will use very little power
[08:40:37] except for memory controller
[08:41:09] I'm just surprised sometimes, ok? let me ask: have you designed or taped out an asic before? isn't it risky to make assumptions about things that are largely unknown?
[08:41:23] I would worry
[08:41:31] that I get something wrong...
[08:41:44] but I also worry like crazy that CNv4 will blow up, where you guys seem to be relaxed
[08:42:06] I didn't want to bring up anything RandomX because CNv4 is such a nailbiter... :)
[08:42:15] how do you guys know you don't have asics in a week or two?
[08:42:38] we don't have experience with ASIC design, but RandomX is simply designed to exactly fit CPU capabilities, which is the best you can do anyways
[08:43:09] similar as ProgPoW did with GPUs
[08:43:14] some people say they want to do asic-resistance only until the vast majority of coins has been issued
[08:43:21] that's at least reasonable
[08:43:43] yeah but progpow totally will not work as advertised :)
[08:44:08] yeah, I've seen that comment about progpow a few times already
[08:44:11] which is no surprise if you know it's just a random sales story to sell a few more GPUs
[08:44:13] RandomX is not permanent, we are expecting to switch to ASIC friendly in a few years if possible
[08:44:18] yes
[08:44:21] that makes sense
[08:44:40] linzhi-sonia: how so? will it break or will it be asic-able with decent performance gains?
[08:44:41] are you happy with CNv4 so far?
[08:45:10] ah, long story. progpow is a masterpiece of deception, let's not get into it here.
[08:45:21] if you know chip marketing it makes more sense
[08:45:24] linzhi-sonia: So far? lol! a bit early to tell, don't you think?
[08:45:35] the diff is coming down
[08:45:41] first few hours looked scary
[08:45:43] I remain skeptical: I only see ASICs being reasonable if they are already as ubiquitous as smartphones
[08:45:46] yes, so far so good
[08:46:01] we kbew the diff would not come down ubtil affter block 75
[08:46:10] yes
[08:46:22] but first few hours it looks like only 5% hashrate left
[08:46:27] looked
[08:46:29] now it's better
[08:46:51] the next worry is: when will "unexplainable" hashrate come back?
[08:47:00] you hope 2-3 months? more?
[08:47:05] so give it another couple of days. will probably overshoot to the downside, and then rise a bit as miners get updated and return
[08:47:22] 3 months minimum turnaround, yes
[08:47:28] nah
[08:47:36] don't underestimate asicmakers :)
[08:47:54] you guys don't get #1 priority on chip fabs
[08:47:56] 3 months = 90 days. do you know what is happening in those 90 days exactly? I'm pretty sure you don't. same thing as before.
[08:48:13] we don't do any secret chips btw
[08:48:21] 3 months assumes they had a complete design ready to go, and added the last minute change in 1 day
[08:48:24] do you know who is behind the hashrate that is now bricked?
[08:48:27] innosilicon?
[08:48:34] hyc: no no, and no. :)
[08:48:44] hyc: have you designed or taped out a chip before?
[08:48:51] yes, many years ago
[08:49:10] then you should know that 90 days is not a fixed number
[08:49:35] sure, but like I said, other makers have greater demand
[08:49:35] especially not if you can prepare, if you just have to modify something, or you have more programmability in the chip than some people assume
[08:50:07] we are chipmakers, we would never dare to do what you guys are doing with CNv4 :) but maybe that just means you are cooler!
[08:50:07] and yes, programmability makes some aspect of turnaround easier
[08:50:10] all fine
[08:50:10] I hope it works!
[08:50:28] do you know who is behind the hashrate that is now bricked?
[08:50:29] inno?
[08:50:41] we suspect so, but have no evidence
[08:50:44] maybe we can try to find them, but we cannot spend too much time on this
[08:50:53] it's probably not so much of a secret
[08:51:01] why should it be, right?
[08:51:10] devs want this cat-and-mouse game? devs get it...
[08:51:35] there was one leak saying it's innosilicon
[08:51:36] so you think 3 months, ok
[08:51:43] inno is cool
[08:51:46] good team
[08:51:49] IP design house
[08:51:54] in Wuhan
[08:52:06] they send their people to conferences with fake biz cards :)
[08:52:19] pretending to be other companies?
[08:52:26] sure
[08:52:28] ha ha
[08:52:39] so when we see them, we look at whatever card they carry and laugh :)
[08:52:52] they are perfectly suited for secret mining games
[08:52:59] they made at most $6 million in 2 months of mining, so I wonder if it was worth it
[08:53:10] yeah. no way to know
[08:53:15] but it's good that you calculate!
[08:53:24] this is all about cost/benefit
[08:53:25] then you also understand - imagine the value of XMR goes up 5x, 10x
[08:53:34] that whole "asic resistance" thing will come down like a house of cards
[08:53:41] I would imagine they sell immediately
[08:53:53] the investor may fully understand the risk
[08:53:57] the buyer
[08:54:13] it's not healthy, but that's another discussion
[08:54:23] so mid-June
[08:54:27] let's see
[08:54:49] I would be susprised if CNv4 ASICs show up at all
[08:54:56] surprised*
[08:54:56] why?
[08:55:05] is only an economic question
[08:55:12] yeah should be interesting. FPGAs will be near their limits as well
[08:55:16] unless XMR goes up a lot
[08:55:19] no, not *only*. it's also a technology question
[08:55:44] you believe CNv4 is "asic resistant"? which feature?
[08:55:53] it's not
[08:55:59] cnv4 = Rabdomx ?
[08:56:03] no
[08:56:07] cnv4=cryptinight/r
[08:56:11] ah
[08:56:18] CNv4 is the one we have now, I think
[08:56:21] since yesterday
[08:56:30] it's plenty enough resistant for current XMR price
[08:56:45] that may be, yes!
[08:56:55] I look at daily payouts. XMR = ca. 100k USD / day
[08:57:03] it can hold until October, but it's not asic resistant
[08:57:23] well, last 24h only 22,442 USD :)
[08:57:32] I think 80 h/s per watt ASICs are possible for CNv4
[08:57:38] linzhi-sonia where do you produce your chips? TSMC?
[08:57:44] I'm cruious how you would expect to build a randomX ASIC that outperforms ARM cores for efficiency, or Intel cores for raw speed
[08:57:48] curious
[08:58:01] yes, tsmc
[08:58:21] Our team did the world's first bitcoin asic, Avalon
[08:58:25] and upcoming 2nd gen Ryzens (64-core EPYC) will be a blast at RandomX
[08:58:28] designed and manufactured
[08:58:53] still being marketed?
[08:59:03] linzhi-sonia: do you understand what xmr wants to achieve, community-wise?
[08:59:14] Avalon? as part of Canaan Creative, yes I think so.
[08:59:25] there's not much interesting oing on in SHA256
[08:59:29] Inge-: I would think so, but please speak
[08:59:32] hyc: yes
[09:00:28] linzhi-sonia: i am curious to hear your thoughts. I am fairly new to this space myself...
[09:00:51] oh
[09:00:56] we are grandpas, and grandmas
[09:01:36] yet I have no problem understanding why ASICS are currently reviled.
[09:01:48] xmr's main differentiators to, let's say btc, are anonymity and fungibility
[09:01:58] I find the client terribly slow btw
[09:02:21] and I think the asic-forking since last may is wrong, doesn't create value and doesn't help with the project objectives
[09:02:25] which "the client" ?
[09:02:52] Monero GUI client maybe
[09:03:12] MacOS, yes
[09:03:28] What exactly is slow?
[09:03:30] linzhi-sonia: I run my own node, and use the CLI and Monerujo. Have not had issues.
[09:03:49] staying in sync
[09:03:49] linzhi-sonia: decentralization is also a key principle
[09:03:56] one that Bitcoin has failed to maintain
[09:04:39] hmm
[09:05:00] looks fairly decentralized to me. decentralization is the result of 3 goals imo: resilient, trustless, permissionless
[09:05:28] don't ask a hardware maker about physical decentralization. that's too ideological. we focus on logical decentralization.
[09:06:11] physical decentralization is important. with bulk of bitnoin mining centered on Chinese hydroelectric dams
[09:06:19] have you thought about including block data in the PoW?
[09:06:41] yes, of course.
[09:07:39] is that already in an algo?
[09:08:10] hyc: about "centered on chinese hydro" - what is your source? the best paper I know is this:
[09:09:01] linzhi-sonia: do you mine on your ASICs before you sell them?
[09:09:13] besides testing of course
[09:09:45] that paper puts Chinese btc miners at 60% max
[09:10:05] tevador: I think everybody learned that that is not healthy long-term!
[09:10:16] because it gives the chipmaker a cost advantage over its own customers
[09:10:33] and cost advantage leads to centralization (physical and logical)
[09:10:51] you guys should know who finances progpow and why :)
[09:11:05] but let's not get into this, ha ha. want to keep the channel civilized. right OhGodAGirl ? :)
[09:11:34] tevador: so the answer is no! 100% and definitely no
[09:11:54] that "self-mining" disease was one of the problems we have now with asics, and their bad reputation (rightfully so)
[09:13:08] I plan to write a nice short 2-page paper or so on our chip design process. maybe it's interesting to some people here.
[09:13:15] basically the 5 steps I mentioned before, from math to physical
[09:13:32] linzhi-sonia: the paper you linked puts 48% of bitcoin mining in Sichuan. the total in China is much more than 60%
[09:13:38] need to run it by a few people to fix bugs, will post it here when published
[09:14:06] hyc: ok! I am just sharing the "best" document I know today. it definitely may be wrong and there may be a better one now.
[09:14:18] hyc: if you see some reports, please share
[09:14:51] hey I am really curious about this: where is a PoW algo that puts block data into the PoW?
[09:15:02] the previous paper I read is from here
[09:15:38] hyc: you said that already exists? (block data in PoW)
[09:15:45] it would make verification harder
[09:15:49] linzhi-sonia:
[09:15:51] but for chips it would be interesting
[09:15:52] we discussed the possibility about a year ago
[09:16:05] oh good links! thanks! need to read...
[09:16:06] I think that paper by dryja was original
[09:17:53] since we have a nice flow - second question I'm very curious about: has anyone thought about in-protocol rewards for other functions?
[09:18:55] we've discussed micropayments for wallets to use remote nodes
[09:18:55] you know there is a lot of work in other coins about STARK provers, zero-knowledge, etc. many of those things very compute intense, or need to be outsourced to a service (zether). For chipmakers, in-protocol rewards create an economic incentive to accelerate those things.
[09:19:50] whenever there is an in-protocol reward, you may get the power of ASICs doing something you actually want to happen
[09:19:52] it would be nice if there was some economic reward for running a fullnode, but no one has come up with much more than that afaik
[09:19:54] instead of fighting them off
[09:20:29] you need to use asics, not fight them. that's an obvious thing to say for an asicmaker...
[09:20:41] in-protocol rewards can be very powerful
[09:20:50] like I said before - unless the ASICs are so useful they're embedded in every smartphone, I dont see them being a positive for decentralization
[09:21:17] if they're a separate product, the average consumer is not going to buy them
[09:21:20] now I was talking about speedup of verifying, signing, proving, etc.
[09:21:23] they won't even know what they are
[09:22:07] if anybody wants to talk about or design in-protocol rewards, please come talk to us
[09:22:08] the average consumer also doesn't use general purpose hardware to secure blockchains either
[09:22:14] not just for PoW, in fact *NOT* for PoW
[09:22:32] it requires sw/hw co-design
[09:23:10] we are in long-term discussions/collaboration over this with Ethereum, Bitcoin Cash. just talk right now.
[09:23:16] this was recently published though suggesting more uptake though I guess
[09:23:29] I find it pretty hard to believe their numbers
[09:24:03] well
[09:24:09] sorry, original article:
[09:24:11] just talk, no? rumors
[09:24:18] college students are already more educated than the average consumer
[09:24:29] we are not seeing many such customers anymore
[09:24:30] it's data from cisco monitoring network traffic
[09:24:33] and they're always looking for free money
[09:24:48] of course anyone with "free" electricity is inclined to do it
[09:24:57] but look at the rates, cannot make much money
[09:26:06] Ethereum is a bloated collection of bugs wrapped in a UI. I suppose they need all the help they can get
[09:26:29] Bitcoin Cash ... just another get rich quick scheme
[09:26:38] hmm :)
[09:26:51] I'll give it back to you, ok? ha ha. arrogance comes before the fall...
[09:27:17] maye we should have a little fun with CNv4 mining :)
[09:27:25] ;)
[09:27:38] come on. anyone who has watched their track record... $75M lost in ETH at DAO hack
[09:27:50] every smart contract that comes along is just waiting for another hack
[09:27:58] I just wanted to throw out the "in-protocol reward" thing, maybe someone sees the idea and wants to cowork. maybe not. maybe it's a stupid idea.
[09:29:18] linzhi-sonia: any thoughts on CN-GPU?
[09:29:55] CN-GPU has one positive aspect - it wastes chip area to implement all 18 hash algorithms
[09:30:19] you will always hear roughly the same feedback from me:
[09:30:52] "This algorithm very different, it heavy use floating point operations to hurt FPGAs and general purpose CPUs"
[09:30:56] the problem is, if it's profitable for people to buy ASIC miners and mine, it's always more profitable for the manufacturer to not sell and mine themselves
[09:31:02] "hurt"
[09:31:07] what is the point of this?
[09:31:15] it totally doesn't work
[09:31:24] you are hurting noone, just demonstrating lack of ability to think
[09:31:41] what is better: algo designed for chip, or chip designed for algo?
[09:31:43] fireice does it on daily basis, CN-GPU is a joke
[09:31:53] tevador: that's not really true, especially in a market with such large price fluctuations as cryptocurrency
[09:32:12] it's far less risky to sell miners than mine with them and pray that price doesn't crash for next six months
[09:32:14] I think it's great that crypto has a nice group of asicmakers now, hw & sw will cowork well
[09:32:36] jwinterm yes, that's why they premine them and sell after
[09:32:41] PoW is about being thermodynamically and cryptographically provable
[09:32:45] premining with them is taking on that risk
[09:32:49] not "fork when we think there are asics"
[09:32:51] business is about risk minimization
[09:32:54] that's just fear-driven
[09:33:05] Inge-: that's roughly the feedback
[09:33:24] I'm not saying it hasn't happened, but I think it's not so simple as saying "it always happens"
[09:34:00] jwinterm: it has certainly happened on BTC. and also on XMR.
[09:34:19] ironically, please think about it: these kinds of algos indeed prove the limits of the chips they were designed for. but they don't prove that you cannot implement the same algo differently! cannot!
[09:34:26] Risk minimization is not starting a business at all.
[09:34:34] proof-of-gpu-limit. proof-of-cpu-limit.
[09:34:37] imagine you have a money printing machine, would you sell it?
[09:34:39] proves nothing for an ASIC :)
[09:35:05] linzhi-sonia: thanks. I dont think anyone believes you can't make a more efficient cn-gpu asic than a gpu - but that it would not be orders of magnitude faster...
[09:35:24] ok
[09:35:44] like I say. these algos are, that's really ironic, designed to prove the limitatios of a particular chip in mind of the designer
[09:35:50] exactly the wrong way round :)
[09:36:16] like the cache size in RandomX :)
[09:36:18] beautiful
[09:36:29] someone looked at GPU designs
[09:37:31] linzhi-sonia can you elaborate? Cache size in RandomX was selected to fit CPU cache
[09:37:52] yes
[09:38:03] too large for GPU
[09:38:11] as I said, we are designing the algorithm to exactly fit CPU capabilities, I do not claim an ASIC cannot be more efficient
[09:38:16] ok!
[09:38:29] when will you do the audit?
[09:38:35] will the results be published in a document or so?
[09:38:37] I claim that single-chip ASIC is not viable, though
[09:39:06] you guys are brave, noone disputes that. 3 anti-asic hardforks now!
[09:39:18] 4th one coming
[09:39:31] 3 forks were done not only for this
[09:39:38] they had scheduled updates in the first place
[09:48:10] Monero is the #1 anti-asic fighter
[09:48:25] Monero is #1 for a lot of reasons ;)
[09:48:40] It's the coin with the most hycs.
[09:48:55] mooooo
[09:59:06] sneaky integer overflow, bug squished
[10:38:00] p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has joined #monero-pow
[11:10:53] The convo here is wild
[11:12:29] it's like geo-politics at the intersection of software and hardware manufacturing for thermoeconomic value.
[11:13:05] ..and on a Sunday.
[11:15:43] midipoet: hw and sw should work together and stop silly games to devalue each other. to outsiders this is totally not attractive.
[11:16:07] I appreciate the positive energy here to try to listen, learn, understand.
[11:16:10] that's a start
[11:16:48] <-- p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has quit (Quit: Leaving)
[11:16:54] we won't do silly mining against xmr "community" wishes, but not because we couldn'd do it, but because it's the wrong direction in the long run, for both sides
[11:18:57] linzhi-sonia: I agree to some extent. Though, in reality, there will always be divergence between social worlds. Not every body has the same vision of the future. Reaching societal consensus on reality tomorrow is not always easy
[11:20:25] absolutely. especially at a time when there is so much profit to be made from divisiveness.
[11:20:37] someone will want to make that profit, for sure
[11:24:32] Yes. Money distorts.
[11:24:47] Or of the two
[11:26:35] Too much physical money will distort rays of light passing close to it indeed.
submitted by jwinterm to Monero [link] [comments]

I literally have tens of thousands of dollars in top-shelf hardware, looking to repurpose some before selling on eBay to build a NAS system, possibly a dedicated firewall device as well. o_O

Q1) What will you be doing with this PC? Be as specific as possible, and include specific games or programs you will be using.**

A1) This will be a dedicated NAS system for my home network. As such, I'm looking to have it:

- Host ##TB's of 720, 1080 & up resolution Movies and TV Shows I'm about to begin ripping from a MASSIVE DVD & Blueray collection I have.

- My kids are big on Minecraft. I understand it's possible to host your own "worlds" (or whatever they call the maps you can build) on your own "server". I think it would be pretty neat to offer them (& their friends - if can be done 'safely/securely') their own partition on one of my NAS HDD's.

- I also have accounts with a couple diff VPN companies... I understand it's possible (?) to sync said VPN's with a NAS, this might be a more relative topic on the next point/purpose...

- I'd like to be able to remotely link to this NAS for when I travel overseas and want to stream at my temp location from my house/this NAS.
Q2) What is your maximum budget before rebates/shipping/taxes?**

* A2) Here's where I make matters more complicated than most others would... I've been an advocate for Bitcoin and crypto-currencies in general since 2013. I invested in a small mining outfit back in 2014 (strictly Bitcoin/ASIC's). One of my buddies is the President of a large-scale mining operation (foreign and domestic) and he convinced me to dabble in the GPU mining-space. I made my first hardware purchase in Q4, 2017 and launched a small-scale GPU-Farm in my house since then. I had the rigs mining up until Q3 of 2018 (not cost-efficient to keep on, especially living in SoFlo) and since then, the hardware's been collecting dust (& pissing off my family members since they lost access to 3X rooms in the house - I won't let anyone go near my gear). One of my New Years Resolutions for 2019 was to clear out the house of all my mining equipment so that's all about to go up on eBay. So "budget" is relative to whatever I "MUST" spend if I can't repurpose any of the parts I already have on hand for this build... (Anyone having something I "need" and is looking to barter for one of the items I'll list later on in here, LMK).
Q3) When do you plan on building/buying the PC? Note: beyond a week or two from today means any build you receive will be out of date when you want to buy.**

Q4) What, exactly, do you need included in the budget? (ToweOS/monitokeyboard/mouse/etc\)**

A4) Well I had a half-assed idea approximately 1 year ago that it might be wise to build a bunch of 'gaming rigs' to sell on eBay with my intended repurposed mining hardware so I went on a shopping spree for like 6 months. That said; I've got a plethora of various other components that aren't even unboxed yet. 90% of the items I've purchased for this additional project were items that were marked down via MIR (mail-in-rebates) & what-not...
AFAIK, there are only 3X items I absolutely do not have which I 'MUST' find. Those would be - 1) Motherboard which accepts "ECC RAM". 2) CPU for said MOBO. 3) Said "ECC RAM".\* 
Q5) Which country (and state/province) will you be purchasing the parts in? If you're in US, do you have access to a Microcenter location?**

A5) I'm located in Southwest Florida. No Microcenter's here. Best Buy is pretty much my only option although I am a member of Newegg, Amazon & Costco if that makes any difference?
Q6) If reusing any parts (including monitor(s)/keyboard/mouse/etc), what parts will you be reusing? Brands and models are appreciated.**

A6) In an attempt to better clean up this Q&A, I'm going to list the items I have on-hand at the end of this questionnaire in-case passers-by feel like this might be a TLDR.* (Scroll to the bottom & you'll see what I mean).
Q7) Will you be overclocking? If yes, are you interested in overclocking right away, or down the line? CPU and/or GPU?**

A7) I don't think that's necessary for my intended purpose although - I'm not against it if that helps & FWIW, I'm pretty skilled @ this task already (it's not rocket science).
Q8) Are there any specific features or items you want/need in the build? (ex: SSD, large amount of storage or a RAID setup, CUDA or OpenCL support, etc)**

A8) As stated in A4; ECC RAM is non-negotiable... RAID seems like a logical application here as well.

- This will predominantly be receiving commands from MacOS computers. I don't think that matters really but figured it couldn't hurt to let you guys know.\*

- I'd also be quite fond of implementing "PFSENSE" (or something of that caliber) applied to this system so I could give my Netgear Nighthawks less stress in that arena, plus my limited understanding of PFSENSE is that it's ability to act as a firewall runs circles around anything that comes with consumer-grade Wi-Fi routers (like my Nighthawks). Just the same, I'm open to building a second rig just for the firewall.\*

- Another desirable feature would be that it draws as little electricity from the wall as possible. (I'm EXTREMELY skilled in this arena. I have "Kill-A-Watts" to test/gauge on, as well as an intimate understanding of the differences between Silver, Gold, Platinum and Titanium rated PSU's. As well as having already measured each of the PSU's I have on-hand and taken note of the 'target TDP draw' ("Peak Power Efficiency Draw") each one offers when primed with X amount of GPU's when I used them for their original purpose.\*

- Last, but not least, sound (as in noise created from the rig). I'd like to prop this device up on my entertainment center in the living room. I've (almost) all of the top-shelf consumer grade products one could dream of regarding fans and other thermal-related artifacts.

- Almost forgot; this will be hosting to devices on the KODI platform (unless you guys have better alternative suggestions?)
Q9) Do you have any specific case preferences (Size like ITX/microATX/mid-towefull-tower, styles, colors, window or not, LED lighting, etc), or a particular color theme preference for the components?**

A9) Definitely! Desired theme would be WHITE. If that doesn't work for whatever reason, black or gray would suffice. Regarding "Case Size". Nah, that's not too important although I don't foresee a mini-ITX build making sense if I'm going to be cramming double digit amounts of TB in the system, Internal HDD's sounds better than a bunch of externals plugged in all the USB ports.
Q10) Do you need a copy of Windows included in the budget? If you do need one included, do you have a preference?**

A10) I don't know. If I do need a copy of Windows, I don't have one so that's something I'll have to consider I guess. I doubt that's a necessity though.
**Extra info or particulars:*\*

AND NOW TO THE FUN-STUFF... Here's a list of everything (PARTS PARTS PARTS) I have on-hand and ready to deploy into the wild &/or negotiate a trade/barter with:

Corsair Carbide Series Air 540 Arctic White (Model# Crypto-Currency-9011048-WW) - (Probably my top pick for this build).
Cooler Master HAF XB EVO (This is probably my top 1st or 2nd pick for this build, the thing is a monster!).
Cooler Master Elite 130 - Mini ITX - Black
Cooler Master MasterBox 5 MID-Tower - Black & White
Raidmax Sigma-TWS - ATX - White
MasterBox Lite 5 - ATX - Black w/ diff. Colored accent attachments (included with purchase)
NZXT S340 Elite Matte White Steel/Tempered Glass Edition
EVGA DG-76 Alpine White - Mid Tower w/ window
EVGA DG-73 Black - Mid Tower w/ window (I have like 3 of these)

CPU's -
***7TH GEN OR BELOW INTEL's ("Code Name Class mentioned next to each one)**\*
Pentium G4400 (Skylake @54W TDP) - Intel ARK states is "ECC CAPABLE"
Celeron G3930 (Kaby Lake @ 51W TDP) - Intel ARK states is "ECC CAPABLE" :)
i5 6402P (Skylake @65W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i5 6600k (Skylake @ 91W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i7 6700 (Skylake @ 65W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(
i7 7700k (Kaby Lake @ 95W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(

***8TH GEN INTEL's **\*
i3-8350K (Coffee Lake @91W TDP) - Intel ARK states is "ECC FRIENDLY" :)
I5-8600K (Coffee Lake @95W TDP) - Intel ARK states is "NOT ECC CAPABLE" :(

***AMD RYZEN's **\*
Ryzen 3 2200G
Ryzen 5 1600
Ryzen 7 1700X


EVGA Z270 Stinger

GIGABYTE Z370XP SLI (Rev. 1.0)



Way too many to list, nothing but 4 & 8GB DDR4 sticks and unfortunately, none are ECC so it's not even worth mentioning/listing these unless someone reading this is willing to barter. At which time I'd be obliged to send an itemized list or see if I have what they're/you're specifically looking for.\*
BeQuiet -
Pure Wings 2 (80mm)
Pure Wings 2 (120mm)
Pure Wings 2 (140mm)
Silent Wings 3 PWM (120mm)

PoopBrown - NF-A20 PWM (200mm) Specifically for the BIG "CoolerMaster HAF XB EVO" Case
GREY - NF-P12 Redux - 1700RPM (120mm) PWM
Corsair -
Air Series AF120LED (120mm)

NT-HH 1.4ml Thermal Compound
NH-D15 6 Heatpipe system (this thing is the tits)

EVGA (Extremely crappy coding in the software here, I'm like 99.99% these will be problematic if I were to try and use in any OS outside of Windows, because they barely ever work in the intended Windows as it is).
CLC 240 (240mm Water-cooled system
Cryorig C7 Cu (Low-Profile Copper Edition*)

A few other oversized CPU cooling systems I forget off the top of my head but a CPU cooler is a CPU cooler after comparing to the previous 3 models I mentioned.
I almost exclusively am using these amazing "Innovation Cooling Graphite Thermal Pads" as an alternative to thermal paste for my CPU's. They're not cheap but they literally last forever.

NZXT - Sentry Mesh Fan Controller
BeQuiet 550W Straight Power 11 (GOLD)

750P2 (750W, Platinum)
850P2 (850W, Platinum)
750T2 (750W, TITANIUM - yeah baby, yeah)

Quark 750W Platinum
Quark 650W Platinum

Focus 750W Platinum
HGST Ultrastar 3TB - 64mb Cache - 7200RPM Sata III (3.5)
4X Samsung 860 EVO 500GB SSD's
2X Team Group L5 LITE 3D 2.5" SSD's 480GB
2X WD 10TB Essential EXT (I'm cool with shucking)
+ 6X various other external HDD's (from 4-8TB) - (Seagate, WD & G-Drives)

Other accessories worth mentioning -
PCI-E to 4X USB hub-adapter (I have a dozen or so of these - might not be sufficient enough &/or needed but again, 'worth mentioning' in case I somehow ever run out of SATA & USB ports and have extra external USB HDD's. Although, I'm sure there would be better suited components if I get to that point that probably won't cost all that much).
Needless to say, I have at least 1X of everything mentioned above. In most all cases, I have multiples of these items but obviously won't be needing 2X CPU's, Cases, etc...

Naturally, I have GPU's. Specifically;

At least 1X of every. Single. NVIDIA GTX 1070 TI (Yes, I have every variation of the 1070 ti made by MSI, EVGA and Zotac. The only brand I don't have is the Gigabyte line. My partners have terrible experience with those so I didn't even bother. I'm clearly not going to be needing a GPU for this build but again, I'm cool with discussing the idea of a barter if anyone reading this is in the market for one.

I also have some GTX 1080 TI's but those are already spoken for, sorry.

It's my understanding that select CPU's I have on this list are ECC Friendly and AFAIK, only 1 of my MOBO's claims to be ECC Friendly (The ASROCK AB350M PRO4), but for the life of me, I can't find any corresponding forums that confirm this and/or direct me to a listing where I can buy compatible RAM. Just the same, if I go w/ the ASROCK MOBO, that means I'd be using one of the Ryzens. Those are DEF. power hungry little buggers. Not a deal-breaker, just hoping to find something a little more conservative in terms of TDP.

In closing, I don't really need someone to hold my hand with the build part as much as figuring out which motherboard, CPU and RAM to get. Then I'm DEFINITELY going to need some guidance on what OS is best for my desired purpose. If building 2X Rigs makes sense, I'm totally open to that as well...

Oh, I almost forgot... The current routers I'm using are...
1X Netgear Nighthawk 6900P (Modem + Router)
1X Netgear Nighthawk X6S (AC 4000 I believe - Router dedicated towards my personal devices - no IoT &/or Guests allowed on this one)
1X TP-Link Archer C5 (Router). Total overkill after implementing the Nighthawks but this old beast somehow has the best range, plus it has 2X USB ports so for now, it's dedicated towards my IoT devices.
---- I also have a few other Wi-Fi routers (Apple Airport Extreme & some inferior Netgear's but I can only allocate so many WiFi Routers to so many WiFi channels w/out pissing off my neighbors) On that note, I have managed to convince my neighbors to let me in their house/WiFi configuration so we all have our hardware locked on specific, non-competing frequencies/channels so everyone's happy. :)

Please spare me the insults as I insulted myself throughout this entire venture. Part of why I did this was because when I was a kid, I used to fantasize about building a 'DREAM PC' but could never afford such. To compensate for this deficiency, I would actually print out the latest and greatest hardware components on a word document, print the lists up & tape to wall (for motivation). I was C++ certified at the age of 14 and built my first PC when I was 7. At the age of 15 I abandoned all hope in the sector and moved on to other aspirations. This entire ordeal was largely based off me finally fulfilling a childhood fantasy. On that note = mission accomplished. Now if I'm actually able to fulfill my desires on this post, I'm definitely going to feel less shitty about blowing so much money on all this stuff over the last couple years.

TIA for assisting in any way possible. Gotta love the internets!


EDIT/UPDATE (5 hours after OP) - My inbox is being inundated with various people asking for prices and other reasonable questions about my hardware being up for sale. Not to be redundant but rather to expound on my previous remarks about 'being interested in a bartetrade' with any of you here...

I did say I was going to sell my gear on eBay in the near future, I also said I wanted to trade/barter for anything relative to helping me accomplish my OP's mission(s). I'm not desperate for the $$$ but I'm also not one of those people that likes to rip other people off. That said; I value my time and money invested in this hardware and I'm only willing to unload it all once I've established I have ZERO need for any of it here in my home first. Hence my writing this lengthy thread in an attempt to repurpose at least a grand or two I've already spent.

One of the most commonly asked questions I anticipate receiving from interested bodies is going to be "How hard were you on your hardware?" Contrary to what anyone else would have probably done in my scenario which is say they were light on it whether they were or weren't, I documented my handling of the hardware, and have no problem sharing such documentation with verified, interested buyers (WHEN THE TIME COMES) to offer you guys peace of mind.

I have photo's and video's of the venture from A-Z. I am also obliged to provide (redacted) electricity bill statements where you can correlate my photo's (power draw on each rig), and also accurately deduct the excess power my house consumed with our other household appliances. Even taking into consideration how much (more) I spent in electricity from keeping my house at a constant, cool 70-72F year-round (via my Nest thermostat). Even without the rigs, I keep my AC @ 70 when I'm home and for the last 1.5-2 years, I just so happened to spend 85% of my time here at my house. When I would travel, I'd keep it at 72 for my wife & kids.
Additionally; I had each GPU 'custom' oveunderclocke'd (MSI Afterburner for all GPU's but the EVGA's).*
I doubt everyone reading this is aware so this is for those that don't.... EVGA had the brilliant idea of implementing what they call "ICX technology" in their latest NVIDIA GTX GPU's. The short(est) explanation of this "feature" goes as follows:

EVGA GPU's w/ "ICX 9 & above" have EXTRA HEAT/THERMAL SENSORS. Unlike every other GTX 1070 ti on the market, the one's with this feature actually have each of 2/2 on-board fans connected to individual thermal sensors. Which means - if you were to use the MSI Afterburner program on one of these EVGA's and create a custom fan curve for it, you'd only be able to get 1/2 of the fans to function the way intended. The other fan simply would not engage as the MSI Afterburner software wasn't designed/coded to recognize/ communicate with an added sensor (let alone sensor'S). This, in-turn, would likely result in whoever's using it the unintended way having a GPU defect on them within the first few months I'd imagine... Perhaps if they had the TDP power settings dumbed down as much as I did (60-63%), they might get a year or two out of it since it wouldn't run as near as hot, but I doubt any longer than that since cutting off 50% of the cooling system on one of these can't be ignored too long, surely capacitors would start to blow and who knows what else...
(Warning = RANT) Another interesting side-note about the EVGA's and their "Precision-X" OveUnderclocking software is that it's designed to only recognize 4X GPU's on a single system. For miners, that's just not cool. My favorite builds had 8X and for the motherboards that weren't capable of maintaining stable sessions on 8, I set up with 6X. Only my EVGA Rigs had 3 or 4X GPU's dedicated to a single motherboard. Furthermore, and as stated in an earlier paragraph, (& this is just my opinion) = EVGA SOFTWARE SUCKS! Precision X wasn't friendly with every motherboard/CPU I threw at it and their extension software for the CLC Close-Loop-Cooling/ CPU water-coolers simply didn't work on anything, even integrating into their own Precision-X software. The amount of time it took me to finally find compatible matches with that stuff was beyond maddening. (END RANT).
Which leads me to my other comments on the matter. That's what I had every single 1070 ti set at for TDP = 60-63%. Dropping the power load that much allowed me to bring down (on average) each 1070 ti to a constant 110-115W (mind you, this is only possible w/ "Titanium" rated PSU's, Platinum comes pretty damn close to the Titanium though) while mining Ethereum and was still able to maintain a bottom of 30 MH/s and a ceiling of 32 MH/s. Increasing the TDP to 80, 90, 100% or more only increased my hashrates (yields) negligibly, like 35-36 MH/s TOPS, which also meant each one was not only pulling 160-180W+ (Vs. the aforementioned 115'ish range), it also meant my rigs were creating a significantly greater amount of heat! Fortunately for the GPU's and my own personal habits, I live in South Florida where it's hot as balls typically, last winter was nothing like this one. Increasing my yields by 10-15% didn't justify increasing the heat production in my house by >30%, nor the added electricity costs from subjecting my AC handlers to that much of an extra work-load. For anyone reading this that doesn't know/understand what I'm talking about - after spending no less than 2-3 hours with each. and. every. one. I didn't play with the settings on just one and universally apply the settings to the rest. I found the 'prime' settings and documented them with a label-maker and notepad. Here's the math in a more transparent manner:

*** I NEVER LET MY GPU's BREACH 61C, EVER. Only my 8X GPU rigs saw 60-61 & it was the ones I had in the center of the build (naturally). I have REALLY high power fans (used on BTC ASIC MINERS) that were sucking air from those GPU's which was the only way I was able to obtain such stellar results while mining with them. **\*
Mining at "acceptable" heat temps (not acceptable to me, but most of the internet would disagree = 70C) and overclocking accordingly brings in X amount of yields per unit. =
'Tweaking' (underclocking) the GPU's to my parameters reduced my yield per unit from -10-15%, but it SAVED me well over 30-35% in direct electricity consumption, and an unknown amount of passive electricity consumption via creating approximately 20%+ less heat for my AC handler to combat.

I say all this extra stuff not just for anyone interested in mining with their GPU's, but really to answer (in-depth) the apparent questions you people are asking me in PM's. Something else that should help justify my claims of being so conservative should be the fact I only have/used "Platinum and Titanium" rated PSU's. Heat production, power efficiency and longevity of the hardware were ALWAYS my top priority.* . I truly thought Crypto would continue to gain and/or recover and bounce back faster than it did. If this project had maintained positive income for 12 months+, I'd have expanded one of our sites to also cater to GPU mining on a gnarly scale.

Once I have my NAS (& possibly 2nd rig for the firewall) successfully built, I'll be willing/able to entertain selling you guys some/all of the remaining hardware prior to launching on eBay. If there's something you're specifically looking for that I listed having, feel free to PM me with that/those specific item(s). Don't count on an immediate response but what you can count on is me honoring my word in offering whoever asks first right of refusal when the time comes for me to sell this stuff. Fortunately for me, PM's are time-stamped so that's how I'll gauge everyone's place in line. I hope this extra edit answers most of the questions you guys wanted to have answered and if not, sorry I guess. I'll do my best to bring light to anything I've missed out on after I realize whatever that error was/is. The only way anyone is getting first dibs on my hardware otherwise is if they either offer compelling insight into my original questions, or have something I need to trade w/.

THE END (Round#2)

submitted by Im-Ne-wHere to buildapcforme [link] [comments]

Bitcoin Rhodium Mining Guide

Bitcoin Rhodium Mining Guide
Happy Mining!

All available XRC pools can be found on MiningPoolStats

Bitcoin Rhodium Mining Hardware

Baikal Giant+: 1.6 GH/s
Baikal Quad Cube: 1.2 GH/s
Baikal Giant: 900 MH/s
Baikal Quadruple Mini Miner: 600 MH/s
Baikal Miner Cube: 300 MH/s
Baikal Mini Miner: 150 MH/s

Mining Setup

To mine Bitcoin Rhodium you need to set up an XRC wallet and configure your miner of choice. You can choose between Web wallet, Electrum-XRC or Magnum wallet. To set up a web wallet please visit Or download and install Electrum-XRC wallet (recommended) for Windows, Linux and MacOS.
Web wallet:
Electrum-XRC wallet:
Magnum wallet:

Sign up for XRC web wallet if not yet done so

  1. Create an account, with your username, password and secure question.
  2. Sign in and click “Create Wallet”.
  3. Set up a strong transaction password. Make sure you store it securely in a secure password manager of choice.
  4. Copy the seed somewhere safe. It’d be a good idea to write seed on a hardcopy and keep it safe.
  5. Paste it to confirm you got it right.
  6. Grab an address for the mining step. Your wallet is now ready to mine XRC.

Instructions for mining XRC on the official pool

Pool link:
  1. Any miner that supports X13 will be able to mine XRC. We have a few examples below of miners that are well tested with Bitcoin Rhodium network.
  2. For any miner, configure the miner to point to:
(0–0.8 GH/s) stratum+tcp://
(0.8–2 GH/s) stratum+tcp://
(3–4 GH/s) stratum+tcp://
(5+ GH/s) stratum+tcp://
with your XRC address as username and x as password. You don’t need to open an account on pool. You will be mining to XRC address and mined coins will be transferred to your wallet
after blocks reach 10 block maturity
after you mined up minimal amount of coins (currently 0.1 XRC)
sometimes mined blocks could get rejected by network (orphaned) after they were counted as valid blocks. This is normal network behavior to follow longest chain
  1. is used to follow your miner and network statistics.

CPU Miner-Multi

Sample configuration with CPU Miner tested on UBUNTU.
“url” : “stratum+tcp://”, “user” : “YOUR XRC ADDRESS”,
“pass” : “x”,
“algo” : “x13”, “threads” : 1,
“cpu-priority” : 5,
“cpu-affinity” : 1, “benchmark” : false, “debug” : true, “protocol”: true, “show-diff”: true, “quiet” : false
Command to run your CPUMiner: cpuminer -c cpuminer.json


SGMiner is a GPU-based mine:
The configuration below was tested on Windows:
cd C:\Software\sgminer-5.6.1-nicehash-51-windowsamd64 sgminer.exe
— gpu-platform 1 — algorithm x13mod -url stratum+tcp://poolcore.bitcoinrh. org:3062 — pool-user — userpass :x — auto-fan — temp-target 70 — temp-over- heat 82 — temp-cutoff 85 — gpu-fan 65–85 — log-file log.txt — no-adl — no-extra- nonce -P –T


CCMiner is a GPU-based miner (NVIDIA)
Command to run your CCMINER:
ccminer-x64.exe -a x13 -o stratum+tcp:// -O :without -D — show-diff

Baikal miner

Settings: Url:
(0–2 GH/s) stratum+tcp://
(3–4 GH/s) stratum+tcp://
(5+ GH/s) stratum+tcp://
Algo: x13User: your XRC receiving address (make sure you set 2 distinct addresses for each hashing board)
Pass: x
Extranonce: leave off Priority set to 0 and 1
Once pool stratum address and your wallet as user are set up you should see your miner mining against XRC pool. When miner is working the status column is green. The pool and miner are incorrectly configured now as status says “Dead” highlighted in red.

Instructions for mining XRC on BSOD pool

Pool link:
Use this code for your miner: -a x13 -o stratum+tcp:// -u WALLET.rig
BSOD pool allows both solo and party mining.
For solo mining use code: -a x13 -o stratum+tcp:// -u WALLET.rig -p m=solo And for party mining use: -a x13 -o stratum+tcp:// -u WALLET.rig -p m=party.yourpassword
NOTICE: You can use us for North America and asia for Asia instead of euin your .bat file or config.
You can also use BSOD pool’s monitor app for Android and iOS.

Instructions for mining XRC on ZERGPOOL

Zergpool offers low fees (just 0.5%) and also SOLO and PARTY mining with no extra fees.
To mine XRC on Zergpool use this command lines for your miner:
Regular: -a x13 -o stratum+tcp:// -u -p c=XRC,mc=XRC Solo: -a x13 -o stratum+tcp:// -u -p c=XRC,mc=XRC,m=solo Party: -a x13 -o stratum+tcp:// -u -p c=XRC,mc=XRC,m=party
Use your coin wallet address as username in mining software. Specify c=SYMBOL as password to identify payout wallet coin, and the same coin in mc=SYMBOL to specify mining coin.
For more information and support please visit
Notice that when there are more pools mining XRC in different geographic/availability locations choose the nearest to you as lowest priority and then add desirable fall back pool options in different geographic locations or pools. This is useful when one pool experiences issues, to fall back to different pool in Bitcoin Rhodium network.

Calculate your Bitcoin Rhodium mining profitability


Feel free to ask questions in Discord community. There are lots of helpful people around the world watching XRC 24x7.

Bitcoin Rhodium Dev Team
submitted by BitcoinRh to BitcoinRhodium [link] [comments]

Continuous Pool Disconnection & 0 Mh/s Speeds

What's up internet/fellow miners. About a week ago I've made the decision to turn my gaming PC to a mining rig. I've had some success solo mining with nicehashminer (Bitcoin miner) but decided that it would be better to mine Ethereum. I've followed the guide and kept coming across these issues. . . I don't know if it's because my config files are whack or another underlying issue.
(EDIT) Connected to now i'm getting different issues. Here are my most recent logs.
11:11:21:867 c20 args: -epool -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x 11:11:21:869 c20 11:11:21:878 c20 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 11:11:21:883 c20 º Claymore's Dual GPU Miner - v14.7 º 11:11:21:894 c20 º ETH + DCSIA/LBC/PASC/BLAKE2S/KECCAK º 11:11:21:896 c20 º Supercharged Edition º 11:11:21:899 c20 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 11:11:21:912 c20 11:11:21:914 c20 b745 11:11:22:117 c20 ETH: 2 pools are specified 11:11:22:125 c20 Main Ethereum pool is 11:11:22:128 c20 DCR: 0 pool is specified 11:11:22:200 c20 OpenCL platform: NVIDIA CUDA 11:11:22:201 c20 AMD OpenCL platform not found 11:11:22:441 c20 CUDA initializing...
11:11:22:442 c20 NVIDIA Cards available: 1 11:11:22:443 c20 CUDA Driver Version/Runtime Version: 10.2/8.0 11:11:22:444 c20 GPU #0: GeForce GTX 960, 4096 MB available, 8 compute units, capability: 5.2 (pci bus 1:0:0) 11:11:22:445 c20 Total cards: 1 11:11:26:468 c20 NVML version: 10.430.86 11:11:27:273 c20 SSL: Imported 60 certificates from local storage 11:11:27:308 33f8 ETH: Stratum - connecting to '' <> port 4444 (unsecure) 11:11:27:331 33f8 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer", "x"], "id": 2, "method": "eth_submitLogin"}
11:11:27:332 33f8 ETH: Stratum - Connected ( (unsecure) 11:11:27:375 c20 No pool specified for Decred! Ethereum-only mining mode is enabled
11:11:27:383 c20 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
11:11:27:385 c20 ETH: eth-proxy stratum mode 11:11:27:386 c20 Watchdog enabled 11:11:27:388 c20 Remote management (READ-ONLY MODE) is enabled on port 3333 11:11:27:397 c20
11:11:27:404 33f8 buf: {"id":2,"jsonrpc":"2.0","result":true}
11:11:27:405 33f8 ETH: Authorized 11:11:27:412 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:27:468 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa4dc2ea0667952442926fb027314fd0cd783cb300063809c3ce279d84884953f","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:27:505 1cf8 Setting DAG epoch #275... 11:11:29:851 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xb34311e461aeedbc6e19ff26eb477bb24241f67c6fcca04ae0ce5c9ea9416c9b","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:29:852 33f8 ETH: 07/30/19-11:11:29 - New job from 11:11:29:853 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:29:855 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:29:856 33f8 ETH: GPU0 0.000 Mh/s 11:11:30:189 1cf8 Setting DAG epoch #275 for GPU0 11:11:30:192 1cf8 Create GPU buffer for GPU0 11:11:33:056 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x246dfc2d4c7299214c5bff6890eaec46e95326f10a0f7778a2c3711893fc20eb","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:058 33f8 ETH: 07/30/19-11:11:33 - New job from 11:11:33:060 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:067 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:070 33f8 ETH: GPU0 0.000 Mh/s 11:11:33:114 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xffd191ec99473ea193905f976655434dc56a0818a92e0bc3f49759df4ce6a428","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:116 33f8 ETH: 07/30/19-11:11:33 - New job from 11:11:33:118 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:125 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:128 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:182 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:37:184 33f8 ETH: 07/30/19-11:11:37 - New job from 11:11:37:186 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:37:193 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:37:259 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:472 33f8 ETH: checking pool connection... 11:11:37:474 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:37:515 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:214 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x08148d13c03fc8be24926cf555957aa73eebaa6fb9a0f7bc802f2e4a59b27508","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:216 33f8 ETH: 07/30/19-11:11:41 - New job from 11:11:41:218 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:41:225 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:41:247 33f8 ETH: GPU0 0.000 Mh/s 11:11:45:196 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:45:198 33f8 ETH: 07/30/19-11:11:45 - New job from 11:11:45:200 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:45:208 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:45:211 33f8 ETH: GPU0 0.000 Mh/s 11:11:47:486 33f8 ETH: checking pool connection... 11:11:47:488 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:47:529 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:322 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x126f150e00540173459de4712848eeb5993cf40f015de6bef8e1b921b0ab1014","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:324 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:326 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:334 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:337 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:676 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x998033b4ddf28107f5b4d5e55b2d4cdf1ca5206ad5d1b0eacbf4a4a33e04c796","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:677 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:678 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:682 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:684 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:794 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xc29af38a326413d6ccee7806a33d6af54eb6118d2035c9f5e1e042cf355d61fa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:796 33f8 ETH: 07/30/19-11:11:49 - New job from 11:11:49:798 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:805 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:983 33f8 ETH: GPU0 0.000 Mh/s 11:11:51:336 1cf8 GPU0 DAG creation time - 20882 ms 11:11:51:339 1cf8 Setting DAG epoch #275 for GPU0 done 11:11:52:152 2664 GPU0 t=48C fan=45% P=45W 11:11:52:162 2664 Total GPUs power consumption: 45 Watts 11:11:52:404 3344 em hbt: 0, fm hbt: 78, 11:11:52:406 3344 watchdog - thread 0 (gpu0), hb time 1063 11:11:52:407 3344 watchdog - thread 1 (gpu0), hb time 1063 11:11:53:742 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:53:744 33f8 ETH: 07/30/19-11:11:53 - New job from 11:11:53:746 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:53:753 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:55:069 33f8 ETH: GPU0 0.000 Mh/s 11:11:55:350 1cf8 GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:353 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:55:361 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:11:55:363 1cf8 GPU 0, GpuMiner kx failed 1 11:11:55:369 1cf8 Set global fail flag, failed GPU0 11:11:55:410 1cf8 GPU 0 failed 11:11:55:424 37fc GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:432 37fc GPU 0, GpuMiner kx failed 1 11:11:55:436 37fc Set global fail flag, failed GPU0 11:11:55:440 37fc GPU 0 failed 11:11:57:502 33f8 ETH: checking pool connection... 11:11:57:504 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:57:542 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:660 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x787a852f5ac545481815d71276fd0a24414e57d78626b67cb3cb9ba02cf4d0aa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:662 33f8 ETH: 07/30/19-11:11:57 - New job from 11:11:57:664 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:57:672 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:57:675 33f8 ETH: GPU0 0.000 Mh/s 11:11:58:418 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:58:429 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:00:381 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xd9a845fe323638bbfc0901441a5959e6f2e73b625dda369cc55a51d855896e03","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:382 33f8 ETH: 07/30/19-11:12:00 - New job from 11:12:00:383 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:388 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:391 33f8 ETH: GPU0 0.000 Mh/s 11:12:00:490 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x4302100500931a1c914b488a598d8737ff3edbf3f3633468314d6c4e28dab922","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:491 33f8 ETH: 07/30/19-11:12:00 - New job from 11:12:00:492 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:497 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:498 33f8 ETH: GPU0 0.000 Mh/s 11:12:01:488 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:01:500 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:04:502 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:04:504 33f8 ETH: 07/30/19-11:12:04 - New job from 11:12:04:506 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:04:514 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:04:518 33f8 ETH: GPU0 0.000 Mh/s 11:12:04:557 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:04:569 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:07:486 33f8 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000b5f052d5"]}
11:12:07:518 33f8 ETH: checking pool connection... 11:12:07:519 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:07:525 33f8 buf: {"id":6,"jsonrpc":"2.0","result":true}
11:12:07:558 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:07:626 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:07:638 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:08:620 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x25869655f7de1b4af101faf41f51e59fa600e7fea8b139c90dbcfaa55b6c9fb6","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:08:622 33f8 ETH: 07/30/19-11:12:08 - New job from 11:12:08:624 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:08:634 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:08:637 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:592 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x31c0d6df2259de2b9db8cecd3ae97eadb63342697df59490297136aa71c2ac8d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:594 33f8 ETH: 07/30/19-11:12:10 - New job from 11:12:10:596 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:604 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:607 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:696 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:10:706 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:10:768 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x428bacd8f4c294dccc3870b0402b8ea1ba9a5b578ef42309a312ea78e37e7ae4","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:769 33f8 ETH: 07/30/19-11:12:10 - New job from 11:12:10:770 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:775 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:777 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:654 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xf9a5e3322470de0aca5def6fbfa5c559e350f580687ec91f6c452e693b64084e","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:656 33f8 ETH: 07/30/19-11:12:11 - New job from 11:12:11:658 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:676 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:679 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:754 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x77acbeb5ef7ac259f42365da8bc180d934d14d7e61514475e431a74bb33092e8","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:755 33f8 ETH: 07/30/19-11:12:11 - New job from 11:12:11:756 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:761 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:763 33f8 ETH: GPU0 0.000 Mh/s 11:12:13:764 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:13:767 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:15:902 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:15:904 33f8 ETH: 07/30/19-11:12:15 - New job from 11:12:15:906 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:15:914 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:15:917 33f8 ETH: GPU0 0.000 Mh/s 11:12:16:823 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:16:835 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:17:534 33f8 ETH: checking pool connection... 11:12:17:536 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:17:575 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:862 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xac10bfccd03a5ada731630cbccba3733cfbccfecc5b9f531c6373ccd47cf9e71","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:864 33f8 ETH: 07/30/19-11:12:19 - New job from 11:12:19:866 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:19:873 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:19:876 33f8 ETH: GPU0 0.000 Mh/s 11:12:19:893 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:19:903 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:22:679 3344 em hbt: 0, fm hbt: 63, 11:12:22:680 3344 watchdog - thread 0 (gpu0), hb time 31344 11:12:22:682 3344 watchdog - thread 1 (gpu0), hb time 27281 11:12:22:684 3344 WATCHDOG: GPU error, you need to restart miner :( 11:12:22:759 11f8 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:22:770 11f8 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:24:035 3344 Restarting OK, exit...
Config File.txt -

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x

-dpool stratum+tcp://

-dwal DsUt9QagrYLvSkJHXCvhfiZHKafVtzd7Sq4

-dpsw x

-esm 1 -mode 0 -tt 70 -asm 0
epool file.txt-

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

POOL:, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorker, PSW: x, ESM: 0, ALLPOOLS: 0

POOL:, WALLET: 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer, PSW: x, ESM: 1, ALLPOOLS: 0

POOL:, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1, ESTALE: 1

POOL:, WALLET: YourLogin.YourWorkerName, PSW: YourWorkerPass, WORKER: YourLogin.YourWorkerName, ESM: 2

submitted by FlawlessPig to EtherMining [link] [comments]


Coin Specification Segwit with Core PoW Algo Wallets
- BitCore BTX- Core 21 Million Coin- 2,5 min- DefaultPort = 8555 - RPC Port 40332- Segwit and Bloom- 20 MB Blocksize (10 MB + 10 MB Segwit)_- Algo Timetravel10- Diff Retarget: Bitcore 64_15 The Segwit opens up new possibilities like the Lightning Network,Tumblebit, Schnorr Signatures,_Confidential Transactions, Cross-chain atomic swaps, and so on.We are alreadyexploring all these new functions, and testing the water.We expect the first implementations as fast as possible. “TimeTravel10”, that actually bases on 40320 different combinations of hashing algorithms and that easily can be extended_to 362880, 3628800 or even more,lets miners travel through time throughthem or through them through time. Source: Github Release Download: Releases Mobile Wallet: Coinomi / Android / iOS Electrum Wallet Electrem Third party wallets Zeltrez / Jaxx Liberty < NEW
Discover our roadmap here
Ocatex BTX/BTC Bitexlive BTX/ USD EUR BTC Bitibu BTX/BTC Trade Satoshi BTX/BTC
PayCml BTX/LYRA Crex24 BTX/BTC Excoincial SOON > BTX/BTC ...
Go to Livingroom of Satoshi Go to Kamoney Go to Cryptonaut Go to EasyRabBit Go to LucckyGames
Go to CryptoID Go to InsightAPI Go to Livenet
Go to CryptoCompare Go to WorldCoinIndex Go to CoinMarketCap
Bitcorepool Omegapool Suprnova Chainworks
Antminepool Coin-miners BSOD Umine
Poolgpu Yiimp BTXpool Minersport
Cointelegraph Bitcore a lightning fast solution to the scaling debate Read
CCN Bitcore winning scaling race earth shattering speed Read
BTC Echo Muss es immer ein Hardfork sein? Nein! – Bitcore (BTX) legt seit April vor Read
Steemit Bitcore BTX Guide: the 2nd snapshot for BTC HODLers - free BTX | how it works Read
Steemit Making blockchain history: Bitcore (BTX) is currently writing blocks with over 3000 kB of data! Read Why is the Cryptocurrency Community Ignoring Bitcore? Read
Bitcore Bitcoin Core Developer Jimmy Song about Bitcore “the most clever fork” Read
Cryptonaut Bitcore is one of the first known cryptocurrencies to use the hybrid fork method to distribute BTX Read
Soft2share Cryptocurrency was what made an entry into the financial sector to address the concerns raised by the centralized infrastructure. Read
Bitcore BTX - Twitter Official Bitcore BTX - Telegram Official Telegram German Telegram Spanish Telegram Italian Telegram Italian Telegram Russian Telegram Ukraine Telegram Bahasa Telegram Philipine Telegram Romania
Bitcore on Youtube Bitcore on Discord Facebook Fanpage / Group

QQ Groupno. 680492670 Go to Chat on Crypto Go to Line @Bitcore.btx / @Bitcore_official
How to sign a message? How to type your sign message from wallet in the registration form? Read BTX Mining Manual A manual for those who struggles setting up mining BTX. Read
Bitcore Snapshot The premine address is 13hwgY4YUvrgnhjLP5ugFafL1cmbRRtr5ePRE ANN was 23.04.2017Download (140 MB)Mediafiles and CI Download files here Press kit Basic | Press kit Full
Chris Jon Steve David
System, Service Administrator & All-Round Talent Core Developer Brand Ambassador & Social Media Publications & Graphic Design
Chris is Bitcore’s main developer. He has worked on several other coins like BitSend, Bitcloud and more.Founder from Limxtec Jon is the API, Electrum and infrastructure developer for Bitcore. He supervises the contact to exchanges, listing sites and more. David is the artistic mind behind Bitcore. He is also working on media publications and supports the core team’s workflow.
Ivo Thomas Greg (GM) DgCarlosLeon
Web Development & Project Consultant Exchange Manager Mining Expert Support and Graphic Design
Ivo is working on the website as well as helping Bitcore grow both legally and technically. Thomas is our email and exchange manager responsible for most of our official communication with services and exchange platforms. Mining pool admin and mining support via telegram channel. Carlos is Bitcore Reddit communicator and graphic supporter.
Fahim Altinordu Brad Eric Hampus
Supporter Supporter Telegram and Facebook Support Supporter
Turkish and international exchange management. Brad is Bitcore’s Facebook manager. Hampuz is organizing signature campaigns and manages our threads on a lot of altcoin forums.
Klaas Ibrahim Acir Ugur Jose Martin
Supporter Developer Team (Turkey) Supporter Spanish Community Manager
Telegram and altcoin forum support. Ugur is managing Bitcore’s Turkish community and helps with telegram support work.
DISCLAIMER | The Bitcore BTX (ANN REDDIT) cannot take responsibility for third party providers, such as the listed exchanges, wallets, sites and pools. All links hosted on our domain are by community members and third parties and by clicking on any of the listed links you are accepting the risks of using the third party domain and taking responsibility for any losses, damage or other issues using said domain. Crypto-currencies are inherently risky and investors and users must remain vigilant.
Web: Official | News | Coin Specs | Roadmap | White Paper | Ecosystem | Network Update | Community | FAQ | Blog | Team Wallets: Windows | Win Wallet & Blockchain | Linux | Mac | iOS | Android | Eletrum | Zeltrez | Jaxx Liberty Exchanges: Bit Z | Cryptopia | hitBTC | VE Bitcoin | Exrates | Crypto Bridge | QBTC | Coinexchange | Octaex | Bitexlive | Bitibu | Trade Satoshi | PayCML Services: Livingroom of Satoshi | Kamoney | Cryptonaut | | Block Explorers: InsightAPI | Crypto ID | Liivenet Mining Pools: Bitcorepool | Yiimp | Suprnova | Chainworks | Umine | Ant Mine Pool | Coin Miners | BSOD | BTXpool | Minersport | Omegapool | PoolGPU Market Info: CoinMarketCap | World Coin Index | Cryptocompare Source: Github | Kryptowerk | DgCarlosLeon _____________________________________________________________________________
ANN Designed by DgCarlosLeon | Bitcore BTX - 2018
submitted by dgcarlosleon to bitcore_btx [link] [comments]

Something is rotten in the state of DOGE mining

Shibes, something stinks in doge land. A problem in the design of dogecoin means that dishonest (or perhaps we should call them "creative") miners can take a disproportionate share of rewards, leaving everyone else to earn less than they deserve. Many of you have probably noticed that calculators estimate payouts larger than what you earn in practice (for example, dustcoin estimates ~1500DOGE/day @ 200KH/s while Non Stop Mine pays about a quarter of that rate), and most have written it off as bad luck: the blocks your pool found happened to be small, or your pool happened to be unlucky, and such is life. At least another friendly Shibe is having a better day, and it'll come around in tips anyway! Unfortunately, the truth is much darker.
The "random" DOGE rewards per block are not random. In fact, the value of each block is predetermined by a simple equation applied to the hash of the previous block. A creative miner can take advantage of this fact to mine dogecoin when the potential reward is high, and switch to litecoin when the potential reward is low. During some rounds, the reward is so small it isn't worth the electricity spent finding it; during more rounds, the reward is less than can be earned mining LTC; in a few rounds, the reward is spectacular. Honest miners mine with the expectation of earning an average of 500,000 DOGE per block, but when people are selectively mining the high-profit DOGE rounds, the average reward falls for honest miners.
So the question is: is this problem theoretical, or are honest miners really losing value to cheaters? I spent some time digging, and it appears that cheating is rampant! There are a few ways cheating can be detected.
If there is outside competition for high-value blocks, then pools should on average be finding blocks worth less than 500,000 DOGE (because some of the valuable blocks, but none of the low-value blocks, will be found by cheaters). The largest pool, Dogehouse, reports some useful averages: over all time, the pool has found 11,241 valid blocks worth 5365077071.0746 DOGE, for an average of 477,277 DOGE (including fees, which should actually raise the average above 500,000!). That's 4.5% below the expected average block value. Is it simply bad luck? No. With so many blocks found, there's about a 7% chance that the average will be above 505,000 or below 495,000; there's a <<1% chance their average will be above 510,000 or below 490,000, and effectively NO chance of seeing an average below 485,000. 477,000 is simply preposterous. Dogepool is either mind-bogglingly unlucky, or something is fishy.
Maybe Dogehouse is doing something fishy...but we can look at other pools. Dogechain's pool's all-time average block value is similar: 478847 DOGE. They're a smaller pool so the odds of this being bad luck aren't astronomical, but it's not very likely. Fast-pool's average is 477892. They're big enough that the odds are again astronomical.
And this only accounts for people cheating outside of the pools. Cheaters can operate inside our pools (more on this later)!
Maybe there's something wrong with the pools. They mostly run similar software. All their owners could be lying to us. We can check for signs of cheating independent of the pools: if more people are mining high-value blocks than low-value blocks, the hash-rate will be higher when the next block is high-value, so high-value blocks will be found faster than low-value blocks. Here's what you find if you look at 5000 recent blocks (blocks 80,001 to 85,000) and measure the average time to find a block, broken out by the block value:
I had to drop about 50 blocks which were missing good timestamps, but they're evenly distributed and shouldn't skew the averages.
The pattern is clear: the network is finding high-value blocks significantly faster than low-value blocks. Low-value rounds take as much as 10% longer than intended, and high-value rounds take around 5% less time than intended. Significant hashrate belongs to miners that cheat.
I mentioned cheaters can operate inside our pools. The payment algorithms used by most pools were carefully designed for bitcoin's (effectively) fixed block reward. They reliably protect against cheaters trying to hop in and out of pools based on short-term profitability, by making payouts solely dependent on the unknowable future (the straightforward pool payment schemes allow cheaters to look at a pool's recent history and use that to take an unfair share of its earnings; read this awesome paper for details). Since the future reward for a bitcoin pool is completely unknowable, PPLNS does not protect against a hopper who knows the future. In the case of Dogecoin, the future reward IS knowable, and PPLNS offers no protection.
Dogehouse is so big we can reasonably assume they'll find any particular block. Dogehouse is using a PPLNS target similar to an ordinary round's length. Someone who mines only during high-value rounds will, with high confidence, earn significantly more DOGE per share submitted than someone who mines Dogecoin 24/7. They also experience much lower variance in earnings.
The random block reward size needs to be removed. It's fun, but it rewards cheaters. Developing a more secure random block value selection technique is possible, but based on observations of GitHub, I do not trust the Dogecoin creator to get it right. Even subtle errors re-open the opportunity for cheating.
While I believe cheating is already unacceptably common, many will disagree until it worsens. To force the issue, I've included everything you need to join the cheaters.
Patch dogecoin/src/main.cpp:
diff --git a/src/main.cpp b/src/main.cpp index 2af23af..8c32dad 100644 --- a/src/main.cpp +++ b/src/main.cpp @@ -1794,6 +1794,8 @@ bool CBlock::ConnectBlock(CValidationState &state, CBlockIndex* pindex, CCoinsVi prevHash = pindex->pprev->GetBlockHash(); } +fprintf(stdout, "Next block value: %lld\n", GetBlockValue(pindex->nHeight, 0, GetHash())); +fflush(stdout); if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)) return state.DoS(100, error("ConnectBlock() : coinbase pays too much (actual=%"PRI64d" vs limit=%"PRI64d")", vtx[0].GetValueOut(), GetBlockValue(pindex->nHeight, nFees, prevHash))); 
Perl script to control cgminer:
#!/usbin/perl use strict; use warnings; my $ltcMiner = " 4029"; my $dogeMiner = " 4028"; open (INSTREAM, "dogecoind|") or die; my $lastPool = 0; # LTC while (my $line = ) { if ($line =~ /Next block value: ([\d].*)/) { my $val = $1; if ($val >= 70000000000000) { # High-value DOGE round if ($lastPool == 0) { # Switch from LTC to DOGE $lastPool = 1; &onoff($dogeMiner, "en"); &onoff($ltcMiner, "dis"); } else { # Already mining DOGE } } elsif ($lastPool == 1) { # Low-value DOGE round and currently mining DOGE $lastPool = 0; print " Switching to LTC\n"; &onoff($ltcMiner, "en"); &onoff($dogeMiner, "dis"); } else { # Low-value DOGE round; already mining LTC anyway } } } close (INSTREAM); exit; sub onoff { my $miner = shift; my $enDis = shift; open (OUT1, "|nc $miner") or die $!; print OUT1 "gpu${enDis}able|0"; close (OUT1); } 
Then, simply run two instances of cgminer with separate API ports, one configured for LTC and the other configured for DOGE.
submitted by DisappointedShibe to dogemining [link] [comments]

The BCN pump and ZEC

A couple weeks back I decided to look into investment opportunities on coins still using the original cryptonight algo. The thought being, all those X3s are mining something other than monero - so what?
My criteria were, cryptonight algo and traded on polo. The list was short, exactly one coin - Bytecoin. The diff had risen 8x over the past month and the price had not risen proportionally, this made the decision easy. Bought a not- insignificant quantity of them around 60 sats and expected to hold for a while until the expected price increase to move more inline with the diff.
Today, you probably heard what happened on binance with a 32x rise in price. This was "made possible" by no blocks being mined for at least two hours. This jogged my memory on something that happened a couple years back that I'd forgotten all about. This also caused me to reasses my stance on the Z3 and whether it is good or bad for ZCash.
Leading up to the latest bitcoin halving , I was researching SHA256 coins to speculate on. At the time, I figured a lot of the SHA ASICs would move off of bitcoin and into alts after the halving took place. At the time I was trading on both polo and trex, so I wanted coins on both platforms. There were about three coins I settled on as I remember - DGB, Myriad, and CURE. Bought some of each on both exchanges.
A similar scenario unfolded with CURE as happened with BCN today There was a massive, MASSIVE, pump of CURE on Polo but price was mostly unchanged on trex. Sold my CURE on polo and initiated a transfer from trex to polo to sell the remainder. After some time, there were zero confirmations showing on trex. WTF? Searched out a block explorer for CURE and low and behold the chain was not moving. After some time, the pump was over and the chain began moving again.
There was certainly a nefarious actor on the mining side that had stalled the chain. I'm no expert on the technicals of how, but winning shares were being withheld by someone with a significant portion of that network's hashrate. Maybe someone else can chime in with the details on how this type of attack is perpetrated. Incidentally, CURE was delisted from polo a very short time later. Whether this was due to polo calling BS, or being complicit and tipping off somebody prior to the delisting announcement to get one last hoorah, the world will never know.
I also remember some talk around that time of excessive orphans happening on slushpool. It apparently ended up being an unintentional issue wherein one of the larger farms pointed at slush was withholding winning shares. This sounded very similar to what happened with CURE, but with so much more hashrate on the BTC network, others were finding winning shares to keep the chain moving.
So, how is this relevant to ZEC?
I believe the BCN attack was made possible by, and initiated with, Antminer X3s. Somebody has a lot of them and pulled this off.
I believe the CURE attack was perpetrated by a major holder of SHA256 ASICs. The CURE nethash was a drop in the bucket compared to bitcoin so it was probably a simple matter of pulling off BTC for a couple hours, attacking CURE, then returning to BTC (or whatever else they were moving at the time).
Not going to speculate on who waged these attacks, it's irrelevant. The important, common, factor is ASIC miners. I fear that the ZEC network will be vulnerable to this type of attack should action not be taken to resist ASICs. All it would take is two hours to completely trash it's reputation and the effort invested in getting it to where it is today.
Before you call me a GPU shill or ASIC fudder, consider that these things have actually happened and do your own research to refute the points being made. In either case, thank you for taking the time to read what I've written and I look forward to your feedback.
submitted by dunnmines to zec [link] [comments]

GINcoin algorithm change

Development update regarding the changes in mining algorithm.
No action is required on your end unless you use the Gincoin Testnet for development purposes.
The Testnet changes for the algo switch to x16rt are implemented and released as alpha (binaries only) on our Github repo:
The algo change on the Testnet is scheduled for tomorrow, Jan 22, 2019 at exactly 13:00:00 GMT. All blocks mined after that date will use the new algorithm.
The difficulty retargeting algorithm is reset at the same date and will use the minimal difficulty for the whole 30 blocks DGW window, making those 30 blocks and a few after mineable at a very fast rate.
How can I help?
It would help increasing the hash rate on the Testnet as much as possible tomorrow before the switch time. To help with this, BSOD will set up a port for mining on the Gincoin testnet, so anyone who can throw a bit of hash power to it tomorrow morning is greatly appreciated.
If all goes well with the transition on the Testnet we will announce the Mainnet switch date by Wednesday afternoon.

Also, we remind you the initial announcement:
"[We] would like to provide a quick update about the Gincoin blockchain changes we are working on and reasons behind them.
As seen over the past weeks, having the highest Lyra2Z hashrate after Zcoin switched to MTP attracted most of their previous hash power and FPGA miners which have a big advantage over the GPU miners.
While we enjoy having a high network security through high HP we do not agree with abandoning the traditional miners who provide the best decentralization to our network, so we felt an intervention is in order to realign our blockchain with one of its founding principles of being mineable by anyone. Since an intervention was in order we thought we could tackle another risk as well while minimizing the changes operators and miners need to do, so we decided to also introduce a protection for 51% attacks along with the algorithm change.
ALGO CHANGEAfter carefully considering a few options for a new algo, we decided to go ahead with x16rt, the evolution of x16r, pioneered by the Veil blockchain. Although MTP (Zcoin) was our primary choice at first, I felt like it goes against a few important principles, which I can elaborate in a separate discussion.
dPoW 51% ATTACK PROTECTION BY KOMODOGoing through an algo change is a vulnerable moment, so we think implementing the dPoW at the same time is important to ensure partners and exchanges that they don't risk anything during the transition.
The Komodo solution provides notarization of the Gincoin blockchain every 10 minutes to the Bitcoin blockchain effectively securing Gincoin with the hash power of Bitcoin, making a 51% attack impossible.
More details about this implementation will be discussed in a separate conversation.
ROADMAP21-22 Jan (Mon-Tue) we will publish the new algo code and deploy the consensus changes on the Testnet to test the transition and proper difficulty retargetting.
Depending on the results of the Testnet deployment we will set a date for the Mainnet change and release new wallets including the DPoW implementation.
The wallet transition period will be generous so that everyone can update in time, but not too long as we need to react quickly. Might be 10 days.
In the meantime, everyone can help by mining on the Testnet to increase testnet diff. Support can help with instructions on DM."
submitted by GINcoin to GINcoin [link] [comments]

To arms Bitcoin community! Help us to complete this mining installation for the Zürich MoneyMuseum. We are not asking for funds. Only your expertise needed! 20$ tip if you give us the relevant clue to solve or mitigate our main problem. Nice pictures of the exhibition inside as well…

A big thank you to all people who helped us we can now mine true pps with diff1! The people in this thread which have helped most have been awarded. I want to mention also the operator of denis2342 and Luke-Jr.
Actually looking at the miner screen in the Linux terminal helped a lot ;-). The pool constantly resigned to stratum with variable difficulty. We can now mine true pps with diff1. Getwork with long polling seems to be default after disabling stratum...
We will probably post again, when there is a video of the installation in action...
Again many thanks. Learned a lot.
Edit: Thank you for all the answeres so far! We will try different things now and report back. Tip bounty will be distrubuted as soon as we found out what finally does the trick. Ths could take a few days. The offerd tip will be distributed and very likeley a few others as well.
First of all, let me tell you that the Bitcoin Exhibition at the Zürich MoneyMuseum is most likely the biggest and most diverse of it’s kind. Please read more about the museum and the exhibition below.
Help us solve the following problem we experience with our “Muscle Powered Proof of Work” installation:
Me and a friend have invested a lot of time to build an installation for the Museum. It is basically a 10GHash/s miner and RapberryPi which is powered by a hand generator (Maxon DC motor with planetary gear). Here are some pictures of the installation, although not entirely put together yet. There are still some changes planned.
Now let’s get to the core of our problem:
We are mining at the getwork diff1 pool as it is a true pps pool with getwork diff1. The visitors in the museum can power the generator for 2-3min and see directly how many Satoshis the "network" (actually pool but we don't want to confuse the visitors to much at that point) has given the museum for their work. This all works well so far but one problem remains. Sometimes the pool does not get a share from us for more than 40 seconds or even more than 60 in some cases. I have calculated that with 8.4 GHash/s we should find a share about every 0.5 seconds in average (diff1). I think when the pool gets a share it gets all the hashes as it then accounts for several Satoshis. Statistically we get per minute what we should get in theory. We would very much like to lower the time between the accepted shares by the pool, however. This would help to make the overall experience much smoother for the visitors.
Please look at this screenshot from MinePeon and answer some questions:
We see that we get a lot of diff1 hashes. However, only 11 shares/packages have been accepted. The Is there a possibility to set the miner SW so it submits to the pool as soon as a share is found? It seems to send them in packages which sometimes have 4-5 seconds in between but sometimes a much as 80 seconds. I would like to submit packages of hashes much more often. How can this be influenced?
What exactly are the Getworks (GW)?
What exactly are the Accepted ones (Acc)? This is where the TipBounty is. Help us to get a better Acc/diff1 ratio. Best would be 1:1.
What exactly are the rejected ones (Rej)?
What exactly are the discarded ones (Disc)?
What exactly are the difficulty one hashes (diff1)?
Now some of these questions seem very very basic but it is important for us to understand what these are and how we can influence these. We have a 1:1 correlation between the Acc and the pool side acknowledgement of shares/packages. So whenever the MinePeon shows one more for this value the pool value for last submitted share goes to “moments ago”.
Does the miner SW have a setting where we can set after how many diff1 hashes a package of hashes is sent to the pool? If no, do you have another idea why so few are sent? Ideally we would set it so the diff1 hashes are sent every 5 seconds or so, probably even more often.
Is stratum with fixed diff1 possible? If so, would it be better to use stratum?
Are there critical settings if we should know of? (we have tried --request-diff and --no-submit-stale)
We are using BFGMiner on MinePeon if that matters. We could switch to CGMiner if that would help. Any help is very much appreciated. The museum is doing a great job explaining Bitcoin basics. We had special focus on interactive learning and have several things to underline this.
I hope to hear back from you so we can improve our installation. Please don't hesitate to ask if you have further questions. We are both not mining experts.
Thanks for reading and AMA.
Current features of the Bitcoin exhibition at the Zürich MoneyMuseum:
Current Features:
  • Life screen with various stats/charts/parameters/transactions…
  • Printed infographics.
  • Muscle powered PoW: Hand generator with 5v and 3.5-5A output, Raspberry Pi, MinePeon, 5x Antminer U2+ plus a screen to show the hash-rate at the pool and/or in MinePeon web interface. This screen will not be hand powered. This installation will complement their coining die (go to 1:27 to see what I mean).
  • The Bitcoin mining evolution (CPU, GPU, FPGA, ASIC)
  • A few short (2-3 minutes) interviews.
  • Other wallets, Trezor, PiperWallet
  • ATM Prototype, functional
  • MoneyMuseum Bit-Cards
  • PiperWallet to use.
  • Casascius and other physical Bitcoins, Wallets (also some commemorative coins), Paper wallet like one out of the first Bitcoin (A)TM ever
  • Bitcoin Quiz
  • 12 Picture tours
    • Bitcoin for beginners
    • Bitcoin advanced
    • Debunking 13 Bitcoin myths
    • What you definitely have to know
    • The history of Bitcoin
    • Bitcoin und traditional forms of money
    • Alternatives to Bitcoin
    • Citations about Bitcoin
    • How do I open an account?
    • How do I get Bitcoin?
    • Bitcoin community and economy
    • Bitcoin as a platform
I see this as a good opportunity for Bitcoin, so let’s embrace it. I am especially excited to compare the traditional forms of money which used proof of work to the new money which also uses proof of work. I think in that context it will be much easier for the visitors to value this concept.
A lot of schools and other groups book guided tours at the museum. It is open on every Friday from December 05. On. Entry is free of charge.
Edit:Markdown, typos
submitted by SimonBelmond to Bitcoin [link] [comments]

Crypto Mining Farm at Apartment  January 2020 Update ... 13 GPUs in ONE PC? – Mining Adventure Part 2 - YouTube How Much Can You Make Mining Bitcoin With 6X 1080 Ti ... By Far The BEST Bitcoin Mining Software In 2020 ... Mining 1 Ethereum With Bitcoin ASIC's, What's The Difference?

From Bitcoin Wiki. Jump to: navigation, search. There are many different types of Bitcoin mining software available. These tables should help you find what will work best for your mining. information Info BFG BitMinter BTCMiner cgminer Diablo EasyMiner gMinor GroupFabric MPBM OSFPGABM Phoenix poclbm Ufasoft ScalaMiner language : C : Scala : Java : C : Java : Python : C++ : Python : Tcl ... start "C:\cpu-miner-pooler" minerd.exe--url stratum+tcp: ... let's have a look at using your GPU. Setting up your GPU miner. For those that intend to mine with GPUs, or USB mining devices, cgminer is the program to use and can be downloaded from the developer's website – unless, that is, you're a Mac user, in which case you will find some unofficial binaries here. Versions of cgminer ... Sicherlich hat ein gefundener Bitcoin-Block mit 25 BTC heute einen Wert von ca. 10.000,– €, aber die Wahrscheinlichkeit mit 100 TH/s einen Block zu finden ist sehr gering. Das Bitcoin-Mining-Netzwerk hat enorme Wachstumsraten hinter sich und man konkurriert mit den Bigplayern der Mininghardware-Branche. Jeder der sich Hashleistung für das ... CGMiner (NoDevFee) — The most popular miner for GPU / FPGA / ASIC, in this version of the miner, the commission of the developer is completely disabled. CGminer is an open source GPU miner written in C and available on several platforms such as Windows, Linux, and OS X. One of the things that make it extremely popular is that it is based on the original Cpu code. BFGMiner 5.5.0 is a modular cryptocurrency miner written in C. BFGMiner has the ability to dynamically clock, monitor and remotely interface.. Pros: powerful miner with many features, cross-platform, including Raspberry Pi Cons: GPUs are not supported, suitable for more advanced users Platforms: Windows, Mac, Linux Unlike CGminer, BFGminer is designed specifically for FPGA and ASIC.

[index] [34480] [8013] [24793] [40055] [42326] [15490] [2847] [50758] [21565] [15429]

Crypto Mining Farm at Apartment January 2020 Update ...

In this video I will review for the best Bitcoin mining software for you. Let's observe this guy's!!! Downloaded Please support my cha... SUBSCRIBE FOR MORE HOW MUCH - GekkoScience NewPac USB Miner - GekkoScience 8 Port USB Hub - bitcoin miner cpu, bitcoin miner cheap, bitcoin miner chinese, c bitcoin miner, bitcoin miner d3, bitcoin miner device, bitcoin miner download, bitcoin miner download windows 10, bitcoin miner ... Crypto Mining with GPU + CPU Tutorial - Get the Most Profit From Your Computer - Duration: 21 ... Rare Footage Inside Massive Bitcoin Mining Farm! - Duration: 22:50. Press For Truth 14,246 views ... What if you use Antminer S9's to mine 1 Ethereum worth of Bitcoin? Would it make a big difference between GPU Mining the same 1 Ethereum? Let's find out just now when Bitmain anounced a new miner ...