Bitcoin Forum
June 18, 2024, 03:26:02 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 [111] 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 ... 570 »
2201  Bitcoin / Bitcoin Discussion / Re: Segwit support going up = hemorrage stopped on: March 26, 2017, 12:19:39 AM
I'm wondering why we are now experiencing uptrend in BTC's price after all these rumors and it turned out that there's a huge bump in Segwit supporters in the last blocks. After checking CoinDance, I saw that 37.5% of blocks mined today used Segwit while 38.1% used BU.
As much as I would like to see segwit continue to gain traction, the same pools that were mining segwit before are still mining it now, so there doesn't appear to be any increase in support and this is just variance related to pool luck.
2202  Bitcoin / Mining speculation / Re: Dose the KnCMiner Neptune really makes you 1.66 Bitcoins a day? on: March 25, 2017, 11:47:25 PM
Will the miner make me 1 bitcoin a day? if not can you tell me which one that will please!
He already told you no. It won't make 1 bitcoin in 1000 years even. No mining hardware will make you 1 bitcoin in a day unless you buy at least 500 of them.
2203  Bitcoin / Bitcoin Discussion / Re: [POLL] Possible scaling compromise: BIP 141 + BIP 102 (Segwit + 2MB) on: March 25, 2017, 10:12:28 PM
AntPool = BTC-U supporter of bigger blocks HAHAHAHAHA fuck them those china miners cartel
they need BIGGER BLOCKS ? Why ? They can't even mine constant 1MB....
AntPool = BTC-U supporter of bigger blocks miner control of the network
There, fixed it for you
2204  Bitcoin / Bitcoin Discussion / Re: Bitcoin Classic developer admits it: blocksize debate is just a powegrab excuse on: March 25, 2017, 10:01:31 PM
If this is the case then the miners should leave the pools and do solo mining so nobody can dictate them and they can continue mining without having to choose one over the other. Solo mining was also effective before and it will still also be effective and profitable even up to this point.
Solo mining is virtually pointless at current levels of network diff, amounting to no more than lottery mining. The vast majority of miners would end up spending a lot of money on hardware and never once be rewarded for their mining; the whole point of proof of work and the mining system is for there to be incentive to mine, and solo mining leaves them with a virtually guaranteed loss and no meaningful incentive. Note that I run a solo mining service and maintain ALL the free software necessary that would allow them to do it themselves so it's not like I'm even against solo mining, I'm just realistic about it.
2205  Bitcoin / Bitcoin Discussion / Re: BUgcoin strikes back on: March 25, 2017, 09:51:40 PM
Advancements in either p2pool software or something similar would go a long way in starting to alleviate the problems associated with mining centralization. Unfortunately, there hasn't been enough incentive to advance these things. I think instead of removing mining from the reference client, it should have adopted and improved upon the p2pool software.
It's not from lack of incentive. Many of us have spent a lot of man hours with discussion, theories and code in mining that the non-mining world probably is not remotely aware of and quick to dismiss as "greedy miners." The idea behind p2pool was sound, but the reality was that the design is fundamentally flawed in a way that cannot be fixed, making it worse to mine on than a regular pool. P2pool is ultimately simply a merged mined blockchain on top of the bitcoin blockchain - mining on the merged chain means you're simply solo mining on a chain with slightly lower difficulty, yet still far too high a diff. After extensive discussion and investigation it is clear that these flaws cannot be fixed to make it even as attractive as regular pooled mining, let alone better. The design of the current bitcoin proof of work itself means that will always be the case. Without a massive change to the blockchain and proof of work design, pooled mining will always be possible, and the "p2pool" design will never be as good. A distributed peer to peer proof of work design that intrinsically does not lend itself to pooled mining without even changing from sha256d allowing existing hardware to continue mining is indeed a solution but unfortunately p2pool is not it and cannot be made to be it.
2206  Bitcoin / Mining / Re: How does merged mining work? Will we be able to merge mine BTC/BTU post fork? on: March 25, 2017, 09:11:32 PM
No you will not be able to merge mine one chain onto another. For merged mining to work, the merged coin needs to explicitly support being merge mined.
2207  Bitcoin / Mining / Re: Am I the only miner who feels disgusted by the talk of PoW change? on: March 24, 2017, 10:18:53 PM
I think POW will never work for crypto coins.

Now I have gpus for alt coins and s9s for btc.

I have a foot in both camps.

I also think segwit is death for btc

I prefer Bu over over segwit.

And POW is worse then either one
You must be confusing your terminology since POW is Proof of Work which is what current bitcoin is and what segwit and BU would still be if either fork activated.
2208  Bitcoin / Bitcoin Discussion / Re: Bitcoin’s Final Obituary? on: March 24, 2017, 10:22:14 AM
Can't advertise this site enough:
https://99bitcoins.com/bitcoinobituaries/

Bitcoin has in fact died 125 times to date
2209  Bitcoin / Development & Technical Discussion / Re: Question on prune and order of provisioning the download on: March 23, 2017, 09:20:58 PM
The whole lot. Unless you import the blockchain from another pruned node that has done the whole lot once, then it has to download the whole lot to confirm its validity before pruning it as it goes. I've imported a pruned block chain that I pruned once to half a dozen new pruned nodes,  but the first time it came from a full block chain of my own (that way I need not trust anyone else's data.)
2210  Bitcoin / Pools / Re: Bitcoin.com Pool, 110% PPS? on: March 23, 2017, 09:01:49 PM
So far it's been 110% everyday. They asked what improvements could be made on the site. I sent in a few suggestions and every one was added in about an hour. Much to my dismay.
EDIT: And delight.
I'd love to see you ask them to stop signalling BU and signal segwit.  Tongue
2211  Bitcoin / Bitcoin Discussion / Re: Are Mining pools spamming the network with fake transactions? on: March 23, 2017, 10:31:50 AM
As much as most users hate centralisation, it's the hardware not the pools that is the cause. CPU -> GPU -> FPGA -> ASIC as we moved down the line the more centralisation occurred.
And that's not true either. The most centralised it ever was (after becoming more than just a fringe between a handful of people) was when the deepbit pool had about 50% of the network hashrate which was in the GPU (and a lesser extent still CPU) days. Assuming all pools are actually discrete entities at the moment and not just one bigger entity masquerading as multiple entities, it is actually more distributed now than it was in the GPU days. It is not the hardware, nor is it the mining algorithm, it's the fact that pooled mining can (and will) occur. There is talk of ways around it, but I've yet to see a concrete way to make it truly impossible to pool proof of work.
2212  Bitcoin / Bitcoin Discussion / Re: BUgcoin strikes back on: March 23, 2017, 08:26:17 AM
BREAKING: BU developers release closed source patch because they are too incompetent to guarantee functional software.
Facepalm, who can take BU as something serious after such a fail?
The same people who were taking it seriously before are still taking it seriously now, which speaks volumes of their thought processes.
2213  Bitcoin / Bitcoin Discussion / Re: Are Mining pools spamming the network with fake transactions? on: March 23, 2017, 08:24:50 AM
about mining pools backing BU, the list is sure longer: gbminers, btc.top, viabtc, bitcoin.com, canoepool, bitclub and of course AntPool.
Just to elaborate further, antpool is dedicating 75% of its hashrate to BU, and bitclub being in that list is an error; I know doin.dance is listing them but it's wrong. They're definitely advertising segwit only.
2214  Bitcoin / Hardware / Re: GekkoScience 2Pac BM1384 Stickminer Official Support Thread on: March 22, 2017, 10:57:34 PM
As for why it kills cgminer, that I don't know.
Resource exhaustion.

Code:
hotplug thread 362 create failed


Code:
 [2017-03-22 22:17:41.847] Hotplug: GekkoScience added GSD 355
 [2017-03-22 22:17:42.056] Found 0 chip(s) on GSD 355
 [2017-03-22 22:17:42.085] GSD 355 failure, disabling!
 [2017-03-22 22:17:47.280] Hotplug: GekkoScience added GSD 356
 [2017-03-22 22:17:47.486] Found 0 chip(s) on GSD 356
 [2017-03-22 22:17:47.502] GSD 356 failure, disabling!
 [2017-03-22 22:17:52.709] Hotplug: GekkoScience added GSD 357
 [2017-03-22 22:17:52.916] Found 0 chip(s) on GSD 357
 [2017-03-22 22:17:52.950] GSD 357 failure, disabling!
 [2017-03-22 22:17:58.123] hotplug thread 362 create failed

Each driver thread instance remains after the device dies, and after 360 odd devices, each with its own driver thread, the system will not allow the one application to create any more threads. The solution is to not create an actual driver thread until it's clear the device is really working (in code) rather than just detected.
2215  Bitcoin / Development & Technical Discussion / Re: Post your SegWit questions here - open discussion - big week for Bitcoin! on: March 22, 2017, 11:00:25 AM
Its just not good enough, to expect the current set-up of 3, 4, 5 ultra nerdy codey types, to tell us how Bitcoin goes forward. This is simply not sustainable.
But bitcoin is high technology which requires high level engineering. How would the average Jo ever have come up with what bitcoin has become so far, and then where to take it from here? Why dump the high technology now and treat it like a black box that should never have high level engineering applied to keep advancing it, only to have a few dials and buttons adjusted by users?
2216  Bitcoin / Bitcoin Discussion / Re: BUgcoin strikes back on: March 22, 2017, 08:28:58 AM
It's like a religious cult at this stage. They will accept any old crap offered up now, on the premise of "it's just a bug". Imagine trusting the 20 billion dollar btc industry to this crap; crashes are the least of my worries.
And the number of BU nodes is back to the about the same level showing yet again the type of person running this crap (that and all the VPSs owned by the same people inflating the numbers artificially.)

still wondering why antpool is supporting BU after all this, have perhaps some man from their mining farm working on BU, who is working on BU currently, i would like to know who are the dev behind that thing

call this a conspiracy but it could make sense, that someone that is working on the opponent project want to push it at all cost by showing pool support
This is the funny part, antpool don't even need to be running this BU crap to be signalling for it. i doubt they'd trust 100s of PH of mining operations to that crap.
2217  Bitcoin / Bitcoin Discussion / Re: BUgcoin strikes back on: March 22, 2017, 04:59:30 AM
BU is buggy right now.  Growing pains.  They need more mature process.

Guess what -- I still prefer it to Core.  Who cares how robust Core is when they want to change Bitcoin into something that's not even p2p electronic cash anymore.

Dude you can't be honestly still saying this is a good idea, a fucking closed source patch on what is supposed to replace Bitcoin? You have to be kidding me.
It's like a religious cult at this stage. They will accept any old crap offered up now, on the premise of "it's just a bug". Imagine trusting the 20 billion dollar btc industry to this crap; crashes are the least of my worries.
2218  Bitcoin / Pools / Re: Is there any open source SOLO Pool software available? on: March 21, 2017, 08:13:42 PM
Ckpool is open-source software as per the thread linked above if you go read it.


Also to note : the public github is not maintained anymore for CKPool as he does development privately only now. Also with the CKPool code the code does not include a payout coding to handle the payouts so you will need to develop  that. I suggest if you not a great programmer don't bother with that software as it will not be maintained.
Take a look at MPOS code and if you keep your pool private it will work as a solo pool
That is completely wrong. Ckpool is maintained publicly. Ckdb is not maintained publicly.
2219  Bitcoin / Bitcoin Discussion / Re: Proof of work debate? Threatened 51% attack due to fork debate on: March 21, 2017, 10:19:46 AM
You miss the point if you think changing the proof of work will fix the problem. The problem is not what the proof of work algorithm is, the problem is simply that work can be pooled. Anything can be made into an ASIC given enough financial incentive, and any type of work can be pooled. What really is needed is to make it impossible to pool work. Find a solution for that and you have progress.
2220  Bitcoin / Bitcoin Discussion / Re: Jihan and a part of miners afraid that will lost fee market from LN on: March 20, 2017, 10:44:14 PM
Presumably your explanation will be that these successful businessmen are sufficiently idiotic that they are incapable of understanding, despite being successful businessmen
...Yes? This is the group that chose BU as their protest vote.
Pages: « 1 ... 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 [111] 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 ... 570 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!