d57heinz
Legendary
Offline
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
|
|
August 01, 2017, 12:37:36 PM |
|
If anyone wants me to hold their payouts - they can request it (but send an email from your pool account email address to the address you get pool messages from) However, the held payouts will sit in your dust fund until I do the dust processing code, some time in the future, in a galaxy far far away.
Also, tell me ASAP, coz once I've created the payout for any block, which is before it matures, I'd have to redo the payout from scratch to change anything, and of course once it's matured, the transaction is out on the bitcoin network, so I certainly wont be trying to double spend it, to change it.
It's not an on, off, on, off, on, off thing I will be doing, just a once off thing now you can request over the next few days, then later request it back on again.
Edit: OK added a link to here, on the web site also.
Why don't you save yourself from all this hassle and just setup a payout like most all pools do. I know it's not from lack of coding ability. Set a small withdrawal fee and that's that. You've been talking about this for cpl years. I'd say either get it done or just say that's going to be donation to the pool. When someone tells me it's gonna get done some time in future in a galaxy far far away basically says to me it's never getting done. You need to take a stand get it done and stop leading on the little miners that could actually be receiving a payout from other pools. Granted it may be less but if you never pay the other pools look much better. How about a roadmap of some sort please and thank you. Ps. Hell of ya have to use code from mpos. That'll save loads of time Best Regards Doug
|
As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 01, 2017, 12:45:58 PM |
|
Nope. Simple 'roadmap' for that already exists ... and posted a few times.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 01, 2017, 02:05:14 PM |
|
Well the 12:20pm 'median time' passed a while ago - still no sign of a fork yet. I guess they might have a 'very small turnout' and take some time to make a fork block ... I'm not 100% certain if they just stop at block 478557 until they find a fork block, or they keep going until they find a fork block on the 'current BTC block' But the blockchair site seems to have stopped at 478557 so I guess that was the Bitcoin block that met the median 12:20am UTC requirement
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 01, 2017, 02:08:17 PM |
|
The white listed 'vip' node in LA failed over the users on it at 14:02 - it was a failover with a failback a minute later. All ok again.
|
|
|
|
NomadGroup
|
|
August 01, 2017, 03:09:10 PM |
|
Payout Information So the payout handling for B-Day (yeah I think that name is an appropriate play on D-Day) will be as follows: I'm queueing up 478254 and 478261 right now to go out as soon as they Mature - as per normal. The 'expected' Maturity times at the moment are: ~3:50am (478254) and ~5:00am UTC (478261) That gives a bit over 19 hours to confirm them before 1-Aug 0:20 UTC Currently we expect to average ~13hrs per block so there's a reasonably high probability they will both be confirmed before B-Day If not, well I don't REALLY think it matters, but we'll see anyway 478295, on the other hand is expected to Mature at ~10:40am UTC, and with the ~13hrs before it's average 'expected to be confirmed', that lands it close to B-Day arrival time. So, I'll hold back sending out the payment for 478295 (and any blocks found after 478295) until tomorrow. -- Again, I don't see why there should be any problems at all with Bitcoin on B-Day, but considering the melodrama going around, it's not really that big a deal to add a short delay to just a few payouts. ... and anyone who is really concerned can also have me hold their 'unqueued' payouts until they are no longer concerned as per the web site says. -- Edit: I also set 42,000 sat in each one as a txn fee - about $1 - to see if that makes others confirm them also. The Bitcoin transaction rate really has dropped recently - often block aren't full - so there's probably a higher chance of it getting into another pool's block if there's some tiny fee in it. Anyway - we'll see if that makes any difference for those 2 payouts. Thanks Kano! Indeed all payouts came in before the D day. I transferred both to cold storage but didn't have the time to transfer the last one but it's ok, let's see what happens to it lol.
|
|
|
|
NomadGroup
|
|
August 01, 2017, 03:25:04 PM |
|
Kano I have a question.... do miners have to pick on which of the 2 networks they need to mine the BTC or BCC? Or do we just mine regularly and if we do then we just receive the BTC or the BCC as well? Might be a dumb question but I pretty new to this stuff.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 01, 2017, 03:47:47 PM |
|
Kano I have a question.... do miners have to pick on which of the 2 networks they need to mine the BTC or BCC? Or do we just mine regularly and if we do then we just receive the BTC or the BCC as well? Might be a dumb question but I pretty new to this stuff. We mine BTC only. From the fork onwards, new block rewards and new transactions are only one side or the other. If you have a wallet you control, you can clone it and make it into a BCH wallet using the BCH version of bitcoin. However, it muxt have been done before the fork, to 'just work' After the fork (now) you have to roll back the blocks and transaction since the fork, so what bitcoin does is effectively wipe it all and start again, but using your keys from your wallet, it of course doesn't wipe the wallet, and then rebuilds everything back up to the fork, then continues on again on the other fork. WARNING, if you do clone your wallet, I've heard from someone who did it, that the fork bitcoin client uses the same folders by default, so will overwrite you bitcoin data. Thus you'd have to use the datadir option to point it to another folder, or better, run the clone on another computer.
|
|
|
|
NomadGroup
|
|
August 01, 2017, 04:21:03 PM |
|
Kano I have a question.... do miners have to pick on which of the 2 networks they need to mine the BTC or BCC? Or do we just mine regularly and if we do then we just receive the BTC or the BCC as well? Might be a dumb question but I pretty new to this stuff. We mine BTC only. From the fork onwards, new block rewards and new transactions are only one side or the other. If you have a wallet you control, you can clone it and make it into a BCH wallet using the BCH version of bitcoin. However, it muxt have been done before the fork, to 'just work' After the fork (now) you have to roll back the blocks and transaction since the fork, so what bitcoin does is effectively wipe it all and start again, but using your keys from your wallet, it of course doesn't wipe the wallet, and then rebuilds everything back up to the fork, then continues on again on the other fork. WARNING, if you do clone your wallet, I've heard from someone who did it, that the fork bitcoin client uses the same folders by default, so will overwrite you bitcoin data. Thus you'd have to use the datadir option to point it to another folder, or better, run the clone on another computer. I see, so there will be created some pools to mine BCC only? It has to be mined by someone right? And yes I have all of the BTC in my Ledger Nano, although they told me yesterday that it will take them a while and they don't know how to resolve the split issue in the older version of the Ledger wallet. But they said that the holders of the new versions of their wallets such as Ledger Nano S should be able to see both balances right away in BTC and BCC. So I was told to buy a new Nano S wallet and do a recovery from my old one. . Thanks Kano!
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 01, 2017, 04:55:54 PM |
|
Well what that means is the 'Ledger' is watching 2 blockchains - not just BTC, but BCH also. Will be interesting to see if the 'brand new' BCH chain code is reliable ...
Anyway, from now on, the two are unrelated, except that the addresses in each use the same keys.
|
|
|
|
NomadGroup
|
|
August 01, 2017, 05:06:34 PM |
|
Well what that means is the 'Ledger' is watching 2 blockchains - not just BTC, but BCH also. Will be interesting to see if the 'brand new' BCH chain code is reliable ...
Anyway, from now on, the two are unrelated, except that the addresses in each use the same keys.
I see, ok thanks!
|
|
|
|
|
dzimmerm56
Member
Offline
Activity: 118
Merit: 14
|
|
August 01, 2017, 07:27:32 PM |
|
Has anyone else noticed the Banned peers list getting really large in their bitcoin core wallet/full node?
dzimmerm
|
1 S9, 2 A741s, 1 A821, 3 A841s, and full bitcoin node About 80THash/sec
|
|
|
wmabern
|
|
August 01, 2017, 09:01:59 PM Last edit: August 01, 2017, 09:38:50 PM by wmabern |
|
Has anyone else noticed the Banned peers list getting really large in their bitcoin core wallet/full node?
dzimmerm
Just took a look at my node. (I just restarted it this morning.) Currently I have 18 connections and two in my banned list. Of course that number may grow the longer it is online. EDIT: I have five in the banned list now.
|
BITMIXER.IO Gone Baby, Gone.. ;-) Not any good sig campaigns out there that I want!
|
|
|
firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
August 01, 2017, 09:50:25 PM |
|
Has anyone else noticed the Banned peers list getting really large in their bitcoin core wallet/full node?
dzimmerm
Just took a look at my node. (I just restarted it this morning.) Currently I have 18 connections and two in my banned list. Of course that number may grow the longer it is online. EDIT: I have five in the banned list now. Interesting. Mine's been up for about three days straight now...119 connections, 85 on the banned list (all from today).
|
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
Cozy
Newbie
Offline
Activity: 32
Merit: 0
|
|
August 01, 2017, 11:11:54 PM |
|
Yep i have like 60 banned peers
|
|
|
|
VRobb
|
|
August 01, 2017, 11:26:48 PM |
|
I look forward to kano-san's sage wisdom regarding this. I suspect, though have no data, that it's possibly related to the forked up shitcoincrash that's being tossed about like a dirty diaper, which both smells and is as unwanted 'round these parts!
|
I don't believe in superstition because it's bad luck: 13thF1oor6CAwyzyxXPNnRvu3nhhYeqZdc These aren't the Droids you're looking for: S5 & S7 (Sold), R4B2, R4B4 (RIP), 2x S9 obsolete, 2xS15-28, S17-56, S17-70 Pushing a whopping 1/5 PH! Oh The SPEED!!!
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 02, 2017, 12:56:28 AM Last edit: August 04, 2017, 05:02:17 AM by kano |
|
Regarding the Bitcoin 'fork': The fork occurred at 478559 The Bitcoin block hash was ...000019f112ec... The Cashcow hash was ...0000651ef99c... As at now: Since then there have been (478635) 76 more (77 total) Bitcoin blocks and 6 more (7 total) Cashcow blocks - 3 mined by ViaBTC and 4 mined that say "Genesis Block 269-273 Hennessy Road Wan Chai Hong Kong" - whoever that is So that makes for 84 blocks and 7 of those 84 (8.3%) are on the fork. Rough numbers, but gives us a vague idea of how much hash rate has left Bitcoin but would indeed suggest a possible nice diff drop coming up next
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4172
Merit: 8086
'The right to privacy matters'
|
|
August 02, 2017, 01:02:44 AM |
|
big runup on bcc near 450 btc is solid at 2700
I am hodling all my core coins for now . I have a new avalon pointed here my hash is over 35th
|
|
|
|
tf315
Member
Offline
Activity: 71
Merit: 10
|
|
August 02, 2017, 01:59:10 AM |
|
Looking to bump up my hashrate here with some new miners. Anyone know of any hosting providers that have any available space? The one I'm currently using is out of power for more miners.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4536
Merit: 1847
Linux since 1997 RedHat 4
|
|
August 02, 2017, 02:06:35 AM |
|
Has anyone else noticed the Banned peers list getting really large in their bitcoin core wallet/full node?
dzimmerm
Just took a look at my node. (I just restarted it this morning.) Currently I have 18 connections and two in my banned list. Of course that number may grow the longer it is online. EDIT: I have five in the banned list now. Interesting. Mine's been up for about three days straight now...119 connections, 85 on the banned list (all from today). My bitcoinds are a little more aggressive at banning connections I blacklist IP addresses automatically in ipsets ... lots So I'd only be guessing, but yep it does sound like core banning nodes sending out invalid blocks, which is, of course, reasonable.
|
|
|
|
|