Bitcoin Forum
May 13, 2024, 05:23:36 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 4 5 6 7 »
21  Bitcoin / Mining support / MOVED: Gezocht fulltime miner / built en onderhoud Alkmaar on: June 06, 2017, 08:49:07 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1954201.0
Non English altcoin mining
22  Bitcoin / Mining / MOVED: Do You Know a Good Chinese Manufacturer? on: June 04, 2017, 11:41:02 AM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1948385.0
Dupe thread in altcoin mining.
23  Bitcoin / Bitcoin Discussion / The Barry Silbert segwit2x agreement with >80% miner support. on: May 22, 2017, 09:24:36 AM
So you've probably heard by now that the large pools have been meeting in secret to discuss a way forward for the bitcoin protocol that would both activate segwit and a future 2MB hard fork. It appears the closed doors meetings did indeed come to an agreement, but not quite what has been assumed by the community.

This is allegedly the draft agreement:
https://pastebin.com/VuCYteJh

Copied below:
Quote
We agree to immediately support the following parallel upgrades to the bitcoin protocol, which will be deployed simultaneously and based on the original Segwit2Mb proposal:
 
 
 
·         Activate Segregated Witness at an 80% threshold, signaling at bit 4
 
·         Activate a 2 MB hard fork on September 21, 2017
 
 
 
The following companies have committed to provide technical and engineering support to test and support the upgrade software, as well as to assist companies with preparing for the upgrades:
 
 
 
·         Bitcoin.com
 
·         BitFury
 
·         BitGo
 
·         Bitmain
 
·         BitPay
 
·         Blockchain
 
·         Bloq
 
·         RSK Labs
 
·         Xapo
 
 
 
We are also committed to the research and development of technical mechanisms to improve signaling in the bitcoin community, as well as to put in place communication tools, in order to more closely coordinate with ecosystem participants in the design, integration and deployment of safe solutions that increase bitcoin capacity
 
 
 
We welcome all companies, miners, developers and users to join us and help prepare bitcoin for the future

In short, what this actually means is a large proportion of the big mining pools have agreed to ignore pretty much all scaling signalling and adopt their own to further their desires. They plan to do a hard fork within 4 months6 months(updated) that both activates segwit and creates a base block size increase of 2MB concurrently. In addition, they are NOT going to be using the existing segwit bits, signalling instead their own bit to activate segwit which is incompatible with the segwit activation from core. They are also planning activation at >80% hashrate.

In essence this means the pools are creating a fork of the current bitcoin code which is planned to be incompatible with any current version should their hard fork go ahead. Which means that every single current code node user, be they core, BU, classic, XT, whatever, is currently going to be on an incompatible fork of bitcoin after their planned deployment in SeptemberDecember. So they are asking the entire community to ignore all existing bitcoin implementations and adopt their software node implementation before that time, or risk being on a very hashrate poor fork, even though there is no published code to support this SeptemberDecember fork yet.

This isn't remotely what many of us were expecting when we heard the pools were agreeing to implement segwit provided a hard fork was also available. In retrospect it makes sense given their aggressive stance in the past, but basically this is without doubt the most aggressive stance yet by the mining consortium. It's even more amazing given bitcoin.com allegedly signed the agreement - BU's reference pool implementation owned by Roger Ver. I wonder if all the groups that allegedly signed the agreement are even aware of what it is they're agreeing to? Bitfury for example are in there, who have been vocal proponents of segwit to date.

This will no doubt make the community even more aggressive in response with its BIP148 stance. I don't like BIP148, but I like this even less.

I'd like to believe this draft agreement was heavily revised and is basically wrong, but at this stage this is all we have to go off.
24  Bitcoin / Bitcoin Discussion / Major crash no. 5 for BU nodes. on: May 09, 2017, 06:50:07 AM


I count 5 major crashes by now, no?

I don't know what this one is yet, but no doubt it's more of their crappy code crashing, and of course they'll blame core somehow...  Roll Eyes
25  Bitcoin / Hardware / MOVED: Gpu problem Code 12 error on: May 03, 2017, 08:44:52 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1899843.0
Dupe
26  Bitcoin / Mining support / MOVED: Decred not mining on: May 02, 2017, 11:57:40 PM
This topic has been moved to CPU/GPU Bitcoin mining hardware.

https://bitcointalk.org/index.php?topic=1898647.0
Irrelevant discussion to modern bitcoin mining.
27  Bitcoin / Pools / MOVED: New public P2Pool node on: April 28, 2017, 03:46:46 AM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1889854.0
Dupe post and not English
28  Bitcoin / Mining support / MOVED: AntBleed backdoor! on: April 27, 2017, 10:56:15 AM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1889102.0
Dupe thread
29  Bitcoin / Pools / MOVED: Hello I'm new and need some help on: April 26, 2017, 09:12:54 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1854695.0
Dupe
30  Bitcoin / Bitcoin Discussion / 4th Major Crash Bug Exploit on BU on: April 24, 2017, 09:45:05 AM
https://twitter.com/alistairmilne/status/856405606630133761



I'm more worried about other sorts of exploits in code of this quality...

I wonder if there will be a closed or open source update for this one?
31  Bitcoin / Pools / ckpool.org CLOSED on: April 19, 2017, 06:40:41 AM
http://ckpool.org


No frills, no fuss ZERO FEE anonymous SPLNS bitcoin mining for everyone

No registration required, coinbase generation, no pool op wallets

Configuration:

Just point your miner to one of:
Code:
pool.ckpool.org:3333
pool.ckpool.org:443
If in Europe use one of:
Code:
depool.ckpool.org:3333
depool.ckpool.org:443
If in mainland China use:
Code:
cn.ckpool.org:443

Set your username to your btcaddress with any or even no worker extension, and any password.
eg:
Code:
cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.0 -p x
If you enter an invalid address you will be rejected

SPLNS

SPLNS stands for Score Per Last N Shares. Score refers to the fact that share value is weighted by the difficulty of the share found.
Last N Shares refers to the fact that the score is a rolling score based on N shares where N means 5 x the current difficulty.
The rolling average is weighted according to when the shares were found - the more recent shares are the more they are worth.

Features of SPLNS:

Hop proof - the system cannot be gamed to earn more by hopping on and off during lucky blocks.
Short "ramp up time" compared to PPLNS - rewards more rapidly rise to stable levels when you first start hashing.
Long "ramp down time" - you are still entitled to rewards for a very long period which is pool hashrate dependant rather than time dependent so you don't quickly "fall off" and earn nothing when you stop mining. Additionally this helps minimise variance for intermittent miners.
Lucky rewards - since shares are weighted by the difficulty of the share found, if you are a small miner that has a handful of lucky high diff shares, you can earn significantly more, capped at current network difficulty.
Block finder rewards - as per lucky rewards, a large share weight is attached to block finds (but is applied to the next block reward since user rewards are included in the existing unsolved block reward.) The sooner the next block is found, the higher the block finder reward is.
Malicious & faulty miner disincentives - since shares are rewarded according to the difficulty of the share found, malicious miners that withhold block solves, or faulty hardware that doesn't produce high diff shares will have substantially less reward than on any other pay scheme or pool.

SPLNS calculation is done on the fly and updated every minute based as a product of HERP DERP.
Herp stands for Hash Extracted Rate Product - where each share is worth sqrt(MIN(share diff, network_diff) / work_diff) * work_diff / 2
Derp stands for Difficulty Extrapolated Reward Payment - where the reward equals the user's herp divided by the pool's herp i.e. it is the expected reward should a block be found now.
The pool's Herp is simply added until it reaches 5 * network difficulty. After that it is biased every minute by scaling existing herp down to add the latest minute's herp and all users' herp is adjusted by the same scale the pool's was.

Additional and/or unique ckpool.org features:

Accurate statistics by the minute - while the statistics displayed at ckpool.org are rudimentary, they are updated by the minute and include accurate estimates of hash rate, herp and derp - which translates into an accurate estimate of payout should a block be solved.
Luck estimates - as the difficulty of each share is calculated into the user's herp, it is compared to an equivalent 'last N share' calculation to determine the miner's overall luck. This is done on a per worker and per user basis and displayed in the stats.The larger the miner and the longer they mine, the closer to 1 their luck will be while small miners may have much more variation.
Coinbase generation - Block solve reward is distributed directly from the block to each user, meaning each user gets a 'mined' transaction directly into their wallet as soon as the block is solved so there is no wait to get paid and no pool wallet storing user's rewards. Rewards will be considered 'immature' by bitcoin rules so will be unspendable until 100 network confirmations have passed.
Interleaved rewards - Each time a block is solved, the top 100 miners will receive a payout while 50 of the remaining smaller miners will receive a payout. Rewards will alternate between the smaller miners according to who has waited the longest for a payout. Rewards accumulate from blocks worked on even if miners are not scheduled for a payout with that block. This is done to minimise the size of the coinbase transaction to minimise latency, maximise mining hardware compatibility, and to make sure miners don't receive many small payouts which would lead to much larger fees when spending their reward.
Micropayments - payments below the dust threshold at block solve time will add to the user's herp for the next block. Once a miner's reward on successive blocks is greater than the dust threshold they will join other users with interleaved payouts.
Blocks are always as full as network congestion demands - ckpool never mines empty or light blocks and yet is still extremely fast at getting new work out to miners on block changes to minimise wasted work and decrease orphan risk.
Rapid propagation of blocks thanks to high speed low latency connections across a network of bitcoin nodes to further decrease orphan risk.
Shares all transaction fees with miners - transaction fees account for a significant portion of mining reward now and as ckpool.org always mines blocks full of transactions the extra rewards can be substantial.
Massively scalable - ckpool can handle extremely large amounts of miners without detriment to performance.

FAQ

Q: Should I use different usernames for each of my miners?
A: You are much better off consolidating all your workers to use the same username and different workernames. The reason is each different user will get a separate reward transaction at block find and each transaction will attract its own fee to spend at a later date, so you'll end up spending less fees if you just use the one username. Additionally if you have multiple small miners (eg. USB sticks), you may never get over the dust threshold if each miners to a separate address.

Q: What is the dust threshold?
A: 5460 satoshi or 0.0000546 BTC. Once enough herp has been amassed to create this much derp, miners will enter the payout queue.

Q: Are there any restrictions on hardware?
A: Only ASIC miners are allowed. Only mining hardware/software that is faulty or malicious and cannot mine high diff shares or has some/all blocks withheld that you are conscious of is not allowed - using such hardware will lead to substantially decreased rewards.

All pool code source freely available here: https://bitbucket.org/ckolivas/ckpool-splns

Support and live discussion on IRC: irc.freenode.net #ckpool

Pool code and pool operated and created by Con Kolivas, creator of cgminer and ckpool.
32  Bitcoin / Pools / MOVED: How come any PPS give more than 100%? on: April 18, 2017, 10:17:42 AM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1875058.0
Asked same question in 3 threads
33  Bitcoin / Mining support / MOVED: bitcoin mining startup on: April 15, 2017, 07:05:38 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1871444.0
Dupe
34  Bitcoin / Mining support / MOVED: msi z77a-g45 Anakart aldık üzerine 3 on: April 04, 2017, 09:56:17 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1854967.0
Non English altcoin mining discussion
35  Bitcoin / Pools / MOVED: add mining pool to our top mining pool directory and get more miner on: April 02, 2017, 04:34:39 AM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1813500.0
Promoting dead service no longer maintained by OP
36  Bitcoin / Bitcoin Technical Support / Zap wallet txns in pruned mode? on: February 11, 2017, 10:20:22 PM
Since -zapwallettxes implies -rescan, it means its use is effectively mutually exclusive of using pruned mode. Does anyone have any suggestions for a workaround without redownloading the whole blockchain again?
37  Bitcoin / Hardware / MOVED: Sheriff Contacted over power consumtion on: October 25, 2016, 07:54:17 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1641495.0
Numerous dup threads.
38  Bitcoin / Hardware / MOVED: Power Getting Shut Off Tomorrow. SOS on: October 25, 2016, 07:53:28 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1660862.0
Numerous dup threads
39  Bitcoin / Pools / MOVED: GBMiners Welcome You All on: October 21, 2016, 12:17:00 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1656841.0

Yet another duplicate thread. Please only use ONE thread for your pool.
40  Bitcoin / Mining support / MOVED: Funds requered to mine bitcoins on: September 12, 2016, 09:34:31 PM
This topic has been moved to Trashcan.

https://bitcointalk.org/index.php?topic=1615189.0
No begging
Pages: « 1 [2] 3 4 5 6 7 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!