Show Posts
|
Pages: [1]
|
Hi folks I'm offering a bounty of 500 DOGE for the finder of the first block the recently launched Dogecoin Mining Pool. Hope to see some of you at the pool and happy mining! Cheers and good luck! 
|
|
|
Hi Our Monero Solo-Pool is now open for business: https://coinfoundry.org/pool/xmr-solo. To get things rolling, the finder of the first block will receive a 0.5 XMR bonus. This also applies to the next block found at our regular Monero Pool (PPLNS 0.8%): https://coinfoundry.org/pool/xmr. Would love to welcome some of you at our pools. Good luck and happy mining! 
|
|
|
The orphaned blocks crisis recently experienced by DASH miners and pools, emphasized once again why the current concentration of approximately 70% of network hashpower (DASH in this case) on just two pools (Antpool and ViaBTC) is not just bad for crypto projects, but outright dangerous. Some smaller pools perished during that crisis because miners - understandibly - blamed the pools and the operators for the long streaks of orphaned blocks caused by some large pools (cough) not accepting blocks from other nodes anymore - effectively splitting the network into two chains. If it weren't for the trust of our loyal miners, we might have been on the chopping block as well and I'm pretty sure many other smaller pools felt the heat as well. Therefore I urge you miners to give the smaller pools a second thought instead of allowing the chinese exercise control over mining and giving them confidence that they can get away with stunts like this.
|
|
|
Due to the rising popularity of the Monacoin and the relative scarcity of international pools, we've just added a Monacoin Pool to our family of pools. Summary- Runs on dedicated hardware (Dual Hex-Core Xeons, 128 GB Ram)
- Managed by dedicated staff focused on uptime, performance, fairness and timely payouts
- Pool Fee: 0% (introductory offer)
- Payout System: PPLNS
- Payouts: Hourly
- Minimum Payout: 0.5 MONA
- Newbie friendly support on UserEcho and Twitter
If you have questions or suggestions, feel free to drop me a line here or on Twitter or join the pool's Support-Channel. 
|
|
|
The post is targetted at developers with a strong enough mathematical background to review and assess the technical correctness of the implementation (C#) of a payout scheme developed for a mining pool. I you believe you are qualified for this read on please. I'm the primary developer of MiningCore, a cross-platform multi-currency stratum engine. The software supports pluggable payout schemes to pay miners for their submitted shares based on the block rewards awarded to the pool after finding a block. So far only PPLNS has been implemented. This payout scheme has been invented by forum user Meni Rosenfeld who announced it here on the forums. What I'm looking for is someone who is capable of using the code plus a production data dump provided by me and validate wether the miner balances generated by the code comply with the description of said payout scheme. If you are interested to help please send me a PM. Serious contributions will be rewarded of course.
|
|
|
I'm out of ideas with one miner connecting to our Litecoin Pool. I'm not sure if this is an issue with an incorrectly configured ASIC miner or an issue with the pool-software. Anyone has an idea what to make of this (that's all he does): [2017-09-28 06:51:28.7625] [T] [ltc1] [Pool] Accepting connection [0HL85MLULNTGH] from xx.xx.xx.xx:27009 [2017-09-28 06:51:28.7670] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.subscribe [449] [2017-09-28 06:51:28.9550] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.authorize [auth] [2017-09-28 06:51:29.1443] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1266] [2017-09-28 06:51:29.3359] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1266] [2017-09-28 06:51:58.7996] [D] [ltc1] [Pool] Persisting pool stats [2017-09-28 06:52:22.7059] [D] [ltc1] [Bitcoin Job Manager] No new blocks for 55 seconds - updating transactions & rebroadcasting work [2017-09-28 06:52:22.9011] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1267] [2017-09-28 06:52:58.7992] [D] [ltc1] [Pool] Persisting pool stats [2017-09-28 06:53:13.7704] [D] [ltc1] [Pool] [0HL85MLULNTGH] VarDiff update to 1024 [2017-09-28 06:53:13.9782] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1267] [2017-09-28 06:53:17.7107] [D] [ltc1] [Bitcoin Job Manager] No new blocks for 55 seconds - updating transactions & rebroadcasting work [2017-09-28 06:53:17.9313] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1268] [2017-09-28 06:53:58.8016] [D] [ltc1] [Pool] Persisting pool stats [2017-09-28 06:54:12.7218] [D] [ltc1] [Bitcoin Job Manager] No new blocks for 55 seconds - updating transactions & rebroadcasting work [2017-09-28 06:54:12.9210] [D] [ltc1] [Pool] [0HL85MLULNTGH] Received request mining.get_transactions [txlist1269] The pool even respond to mining.get_transactions with the transaction data returned by the getblocktemplate RPC, yet the miner keeps asking for them.
|
|
|
I'm running a pretty young BCC Mining Pool and I'm seeing some anomalies in the logs associated with a miner pulling 35 GH/s. Since I do not have access to an ASIC miner myself, I need some help. Could someone equipped with an ASIC Miner (Antminer etc.), aim it at the pool for a short while and report back if mining's going smooth or if there are problems? URL: https://poolmining.org/pool/bcc
|
|
|
Hi I'd like to introduce our Mining-Pool at https://coinfoundry.orgWhat differentiates us from most other pools, is our quickly responding an friendly support, our active community and perhaps a fresh and less generic approach to UX. We hope that our near flawless reliability track record combined with lower than average fees might convice you to give us a try. We'd be glad to welcome you aboard! Summary- Running on dedicated servers with multi-Gigabit peerings
- Run by experienced staff with years of experience managing complex systems
- In-house developers maintaining and improving pool code
- Coins: Monero, Bitcoin Gold, Ethereum, Ethereum Classic, Bitcoin Private, Litecon, DASH, ZCash, Verge - Blake, Monacoin, Vertcoin, Bitcoin Cash
- Pool Fee: 0.1% (introductory offer)
- Payout System: PPLNS
- Payouts: Hourly
- Newbie friendly support on UserEcho and Twitter
If you have questions or suggestions, feel free to drop me a line here or on Twitter or join the pool's Support-Channel. 
|
|
|
Hi Ich möchte kurz unseren Monero-Pool vorstellen: https://poolmining.orgFeatures- Läuft auf dedizierter Hardware (Dual Hex-Core Xeons, 128 GB Ram)
- Gehostet in deutschem Datacenter (Failover-Kapazität steht auf Amazon AWS auf Abruf)
- Konsequenter Fokus auf Uptime, Leistung and pünktliche, korrekte Bezahlung
- Coins: Monero, Ethereum, Ethereum Classic, Litecon, DASH, Expanse
- Pool Fee: 0% (Einführungsangebot)
- Auszahlsystem: PPLNS
- Auszahlungen: Stündlich
- Minimale Auszahlung: 0.25 XMR
- Hardfork ready
- Newbie freundlicher Support auf UserEcho und Twitter
Der Pool ist noch sehr jung und wurde in den vergangenen Wochen hauptsächlich von Freunden & Familie getestet ohne aktiv promoted zu werden. Heutzutage ist es für junge Pools ziemlich schwer geworden Miner dazu zu bewegen einem Pool ihr Vertrauen zu schenken der eine deutlich geringere Hashrate als die etablierten Pools bietet und eben generell noch ein unbeschriebenes Blatt ist. Daher sei eines klar gestellt: Die Motivation für den Pool ist nicht etwas Geld abzugreifen und dann beim ersten Zeichen von Problemen den Laden dicht zu machen, wie es in der Vergangenheit nicht selten passiert ist. Der Pool ist ein Langzeitprojekt. Wer unserem Pool eine Chance gibt, unterstützt nicht nur den Pool selbst, sondern auch das Monero-Projekt als Ganzes in dem er seinen ganz persönlichen Beitrag zur Dezentralisierung der Hash-Power leistet. Auf das sich die selbige nicht auf einige wenige grosse Mega-Pools konzentriert. Dezentralisierung ist wichtig! Bei Fragen oder Vorschlägen einfach eine PM an mich. Entweder hier, auf Twitter oder im Support Bereich des Pools. 
|
|
|
Jemand scheint massenhaft RX 570s auf Twitter zu verkaufen. Ich habe mit dem Angebot nichts zutun, es ist mir nur aufgefallen. Na, zumindest wissen wir jetzt warum es seid geraumer Zeit Lieferschwierigkeiten bei GPUs gibt.
|
|
|
Someone's offering a truckload of RX 570s on Twitter. Please not that I'm not affiliated with the offer, I only spotted it. At least now we know why there's a shortage of AMD GPUs.
|
|
|
|