"derp": 1.69e-6,
You know what 10 to the power of -6 means? |
|
|
|
So the derp number is my reward in BTC??? I don't see how that's possible I've been mining for 30 minutes and it's at 1.21
Are you looking at your own BTC address? Everything appears to be in order as far as I can see. Only one address is around that reward and it's "1B5nA9AyLxtRmA16S4YCXR5D1r9Z9j1wBg": 1.26586349 |
|
|
|
@-ck I have an s7 running; Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version Thu Dec 3 16:07:54 CST 2015
Cgminer Version 4.8.0
is this possible to crack a block or do I need to update? Thank you much...
It is still possible. Extremely unlikely but still possible. Updating won't increase your chances of finding a block unless you get more powerful hardware. |
|
|
|
I'm beginner with solo mining and using blackarrow prospere x1 for this.. How i should config my device for "All you need to confirm you are mining to your own address is to examine the coinbase and template sent to you over stratum."  You can't do it with your hardware, you need software that can do it for you. If you build the latest cgminer from git you can use the --decode option (which needs bitcoind running as well as the first pool). Otherwise you have to extract the coinbase from stratum through some other means and feed it into bitcoind to decode the hex. |
|
|
|
Came home saw this on the miners screen FoundBlocks 1 - Got very excited!
Can't seem to see any payout though?
Also this is a old S3 which was even more of a surprise!
Bitmain's cgminer fork is quite broken with respect to block finding detection. |
|
|
|
How many times have I reiterated that what remains a complete mystery is what happens after segwit gets activated when we're staring down the barrel of the 2MB base blocksize (an 8MB overall block weight hence why I add the word base in there)
If that's what you really think, why do you keep feeding the publicity drive for this 2x proposal? You've been doing nothing but talk up it's relevance since it appeared, and yet you're conceding here that there are withheld details that will be imposed (or at least expected) once Segwit 4MB (i.e. BIP141) is activated. You should make your position clearer: do you think mystery clauses in contractual agreements a good idea or not? No, I think this agreement is the most fucked up thing in the history of bitcoin. I'm just glad we're getting segwit, but not remotely pleased about how it's happening, nor what they've planned for the future. Clearer? And if it's not clear, the whole point of this thread is to try and figure out what it means for all of us, I don't want to hype this fucking PoS. I've been trying to be relatively neutral with my reporting and shoot down the occasional trolls who've derailed the discussion. The fact is it's here and it's a tidal wave and we need to learn how to best ride the tidal wave rather than pretend it's not happening and be wiped out in the process ignoring it or trying to swim in another direction. |
|
|
|
Why? I think the guy has a point... For instance, if- when- and after SegWit gets locked in (and thus would make BU incompatible with it), there is no guarantee that the whole thing, to some degree, is 'settled'... We have seen many ideas addressing the scaling issue, yet we have also seen neither sides playing it nice. SegWit, Segwit2x, BU, UASF or whatever other proposal which can be labeled as a (temporary) 'answer', is addressing scaling; yet what they all lack, is addressing the emotions that have came along with them... Logic, basic or not, isn't applicable in that case, as logic simply cannot reason with emotions, the same as emotions cannot reason with logic, as in a way they're complete opposites of each other...
You've misunderstood what I'm flabbergasted by. I never said the whole thing was settled; not even remotely. How many times have I reiterated that what remains a complete mystery is what happens after segwit gets activated when we're staring down the barrel of the 2MB base blocksize (an 8MB overall block weight hence why I add the word base in there). The guy I just put on ignore seems to think this coinbase intention to signal of 85%+ is no guarantee that segwit will get activated and that the BU coinbase signatures used by Jihan and his minions are relevant to that. |
|
|
|
You are trying to mine with ancient software that only mines on CPU or GPU and a computer without mining hardware attached. The ancient software does not speak the current mining protocol and non ASIC hardware cannot meaningfully mine bitcoin. Please read bitcoin mining 101: https://bitcointalk.org/index.php?topic=1944976.0/locked |
|
|
|
If you mean me, I haven't gone too far. I am just currently soloing some alts that are paying me the bitcoin equivalent of ~170-180% PPS, and only the odd hour or 2 in the pool for now. Hopefully this will offset the long-haul overhead of what it takes to be involved in the wait of finding blocks and I can get back to a longer duration in the pool some time soon.
I did mean you, so:  |
|
|
|
|
Well it's no great surprise but it looks like lack of growth has failed to keep the genie in the bottle and scared him off leaving only all the small miners. It's not like it's even bad luck since we haven't even had 100% diff at any stage yet, it's just that it'll take forever on average to find a block. Never fear, the rest of us are all in it for the long haul and there is always the possibility I may be able to convince someone of decent hashrate to join us.
|
|
|
|
OK well then maybe you can explain to me how Segwit2x will be adopted with 40% BU/EC miner support? And 37.5% of the blocks supporting EC? And no outreach to the public whatsoever? With complete silence from Core devs?
Next, what's to prevent Core fanbois from convincing everyone to run the hastily prepared Segwit2x, then after Segwit is adopted, drop another release that doesn't hard fork to 2MB? Do you think the miners will fall for the "bait and switch" tactic used in Hong Kong again? Finally, what makes you think that the miners won't just flag this Segwit 2x support in their headers (it took 10 seconds of work) until the UASF guys lose all of their steam?
I'm starting to think this forum is just an echo chamber for bickering... there must be a better source of information elsewhere.
I tried. You seem incapable or not interested in understanding so I'll just add you to my list of "faith" people incapable of understanding basic logic worth putting on ignore (done). You don't like this forum? Great! Go elsewhere and find the wisdom you seek which will support your faith. I suggest r/btc . |
|
|
|
From my perspective (no need to correct me on this), it seems that the well-funded actors in this drama are sticking to their guns. Core/Blockstream is stuck on "waiting forever for Segwit, which will likely never come", Bitmain is advocating for "increase blocksize or else", and the Lukejr army is opting for "we willz force Segwit through no matter what". Unlimited is quietly chugging along with 40%+ support, with no recent major drama.
There is plenty of need to correct you on this since you're completely wrong. You're really missing the significance of segwit2x. There is no doubt that the main players advertising segwit2x will adopt it. The code already does exist and is complete and they're calling it alpha simply because it hasn't undergone full testing yet. There is at least one pool that has activated its segwit enabling component from the code and is signalling bit4. There is no reason to believe they will back out now barring a major bug showing up. The reason for the rushed schedule for the segwit component is that they're determined to undermine BIP148 from functioning which is why they all start signalling one diff period before BIP148's activation date. Lukejr's army is a mixture of people who actually believe in BIP148 being a workable mechanism and people who just know they must keep pressure on to not let the miners back out of the segwit component of segwit2x. Core is going to get its BIP141 original segwit activation through a fucked up convoluted secondary and tertiary messaging approach invented by the mining consortium so saying "waiting forever for segwit which will likely never come" is completely missing the point of segwit2x since it definitely WILL come and almost certainly hopeful thinking from a BU supporter. The fact you're reproducing my words for what the significance of BU is in light of the current situation and applying them to segwit says it all. Thinking otherwise now is nothing short of faith against all logic and reason. Either way if you keep believing otherwise you can see for yourself come mid-July. As I said before, what core IS facing that goes against its plans that they have no contingency for is the 2MB hard fork after segwit activation months later. I have no idea how that's going to play out. A fixed 2MB hard fork in the segwit2x code however goes against EC as well so if you still think EC is relevant based on the 40% coinbase signatures at present then you're saying they will adopt the emergent approach to block size after 2MB is locked in to allow even larger blocks, or maybe switch back to smaller ones. Not sure why they'd bother with a hard fork to 2MB if they planned to switch to a flexible block size hard fork as well... Furthermore once segwit is locked in, the code is completely incompatible with BU. |
|
|
|
All said and done, if SegWit2x is implemented, how much does it increase the current network capacity? 2x? 4x? How much?
The most pessimistic estimates put segwit alone as averaging 1.7MB and then 2x will double it. The most possible would be 4MB from segwit (with all segwit transactions) and then 2x doubling that. |
|
|
|
|
Locking this thread since it's been asked a billion times before and just attracts offtopic discussion and sigspammers.
|
|
|
|
|
Bitcoin has been around 8 years establishing its worth. How do the others compare considering how long they've been around?
|
|
|
|
Forget about 80% consensus, we are now nearing 90% support, with SegWit2x being supported by 89.6% right now. In just around 24 hours, the support levels have increased from less than 80% to around 90%. Among the major mining pools, as far as I know only Slush Pool and GB Miners are resisting the implementation of SegWit2x.
GBminers is already signalling segwit so even if they don't explicitly support segwit2x, they'll be fine once the segwit component activates, as will all other segwit signalling pools like mine. Slush is a quick mover and is offering segwit signalling anyway as one of his options and is currently talking about considering signalling segwit2x as well on his feeds so there's no way he'll be left with orphaned blocks come the actual activation time. That only leaves a handful of smaller pools that aren't signalling anything yet. No doubt once segwit is being signalled they'll simply see they have no choice but to come on board. |
|
|
|
|
If you guys tell me he's not trolling any more I'll reconsider.
|
|
|
|
...yea yea i expect my post to get deleted even though it contains content about segwit2x
Maybe if you quit posting dumbass comments like that, then you'd stop pissing off the guy that can delete them?  Actually it doesn't really matter what he says any more since I told him he is forbidden from posting on this thread and I have him on ignore so I can't even see what he's posting, just that he's posting and delete his posts on sight. He's done too much trolling for too long on too many threads to be able to redeem himself as far as I'm concerned. He is the no. 1 reason I made this thread self-moderated. |
|
|
|
|
Show Posts
