Awesome!  Good luck, Phil!

I'll join you if my BTC ever makes it to my NH wallet

d57heinz, Antpool is the worst offender of empty blocks in the entire bitcoin world.  I started a thread months ago about empty blocks and back then called out the big offenders.

Either Antpool doesn't have the talent to fix the problem with their pool, they don't give a shit about it, or both.  People need to stop mining here and point their hash somewhere else.  bravo-mining.com could use the influx of hash.  BCMonster is another pool looking for miners.  DrHaribo's pool is a great recommendation as well.  Don't forget mmpool and of course kano's pool.  So many good choices for people...

Prices on NH/WH are down to "normal" levels if anyone is interested in grabbing a rental.  Hit a block and you'll get the bonus, which is currently at 1BTC.

By the way, if the pool were to hit a block right now, we'd include 2850 transactions and get 0.74 in fees.

It's because of their lousy code, plain and simple.  They maintain an awful fork of cgminer that they insist on including with every piece of hardware they sell.  They claim support for p2pool, and even have a forked repository with some code - that hasn't been touched since 2014 and didn't work when they released it.

If only more people saw the light and pointed their hash away from this (and other big, bad-for-bitcoin pools) and took a chance on the smaller ones like mine.  I manage to include a full set of transactions in every block and am consistently benchmarked either right ahead of, or right behind kano and -ck's pools in terms of block propagation speed across the network - both of whom's pools also always include a full transaction set and are completely verified.

So, take up the call and point your gear away from these greedy, bad-for-bitcoin pools and point it to a smaller pool.  Help the little guys grow.  Help decentralize the network.  Help Bitcoin.

Received with my thanks .

Unfortunately even giving away free BTC bonuses to block finders doesn't guarantee people will mine on your pool.  I'd love it if people stopped mining on the big, bad-for-Bitcoin pools and pointed their hash to our pools instead.  Very hard to get people to switch over, though.

That's not how it works... Expected time to block is based on your hash rate, not some multiplier of a share you found.

1) Opening ports 9332, 8333 and 9333 means you're running a full BTC node and publicly accessible p2pool node.

2) P2Pool supports stratum by default.  You don't need to do anything.  Just set your miner to use stratum+tcp://your.ip.address:9332

3) Putting "/" and/or "+" doesn't increase your odds of finding a share.  Well... the "/" *might* if you're mining on a node that has a ton of hashing power and defaults to a share value higher than p2pool minimum... but not really relevant if you're the only miner on the node.

4) Transaction fees are the fees BTC users pay for their transactions to be included in blocks.  The bit you quoted is from Antpool.  Just ignore that crap.  Standard p2pool (i.e. running your own node) includes paying the transaction fees to miners.

5) I don't own an S7, but reports have shown that, like other Bitmain products, the S7 suffers on p2pool because of the crap fork of cgminer they use.

6) I have no idea about bfgminer or active submission, sorry.

OK, here's a little bit more info for you

Ensure you've got your tor service running.  Also, ensure you've got a control port (typically 9051) and you've properly generated a hashed password for the control port, or you use cookie authentication (which I don't).

In your bitcoin.conf file put:

torpassword=YOUR_PASSWORD_HERE
debug=tor

That'll let you see some potentially useful logging information.

Now, when you start your bitcoin core you should see similar to this:

Do the following:

1) backup your wallet
2) stop core
3) start core as follows:


That will ditch blast any unconfirmed/weird transactions and also do a full rescan.  You will be good to go after that.

Whoever is trying to connect to my pool as "avalon6" you're doing it wrong.  You need to create your account and then create a worker for that account.  For example, if you created an account "BravoPool" and a worker "avalon6" with password "123", then you'd configure your miner as follows:

Pool: stratum+tcp://stratum.bravo-mining.com:3333
Username: BravoPool.avalon6
Password: 123

Hope this helps and you can get it sorted.

Since I saw the public note about it funding Bittrex, I figured he was using blockchain.info as a wallet.  Why they would allow you to create a transaction like that is beyond me.  I don't think their UI should allow for a user to manually enter miner fees.  Especially not when the UI is as poorly designed as theirs is, even though he had to go to the custom transaction type to create the transaction he did.

It only creates an address if you don't specify one on the command line when starting your node.  That's because it needs a default address to account for node fees and also any shares generated by miners trying to use something other than their BTC address as a username.

If you then have two miners on your node and they are using proper BTC addresses (B and C), then if they have any shares on the chain when a block is hit, the coinbase transaction will directly pay to B and C.

No...

This is the transaction:

6e3bf6483bb2f10ed2f5938f2649c570bd0c3ab5d7b5e86ed3bdecce5455ac51

I don't know how he did it, but take a look at the input and outputs.  The input has ~2.35BTC in address 1J... the two outputs are a 1BTC to address 15a... and 0.35BTC back to the same 1J... address.  Oops... that leaves a 1BTC fee for the miners.

You are a generous man, Phil.

From the release documentation:

Automatically use Tor hidden services

Starting with Tor version 0.2.7.1 it is possible, through Tor’s control socket API, to create and destroy ‘ephemeral’ hidden services programmatically. Bitcoin Core has been updated to make use of this.

This means that if Tor is running (and proper authorization is available), Bitcoin Core automatically creates a hidden service to listen on, without manual configuration. Bitcoin Core will also use Tor automatically to connect to other .onion nodes if the control socket can be successfully opened. This will positively affect the number of available .onion nodes and their usage.

This new feature is enabled by default if Bitcoin Core is listening, and a connection to Tor can be made. It can be configured with the -listenonion, -torcontrol and -torpassword settings. To show verbose debugging information, pass -debug=tor.

Link: https://bitcoin.org/en/release/v0.12.0#automatically-use-tor-hidden-services

No luck with that rental, unfortunately.  Best share was only 52,677,068,799.

Don't forget - that block finder bonus is still available!  And since we're still under 110% of expected shares, that's a 1BTC bonus

Gotta love when somebody pays way over the expected rate for rental hash... 8PH/s rental paying .0036.  Someone's got some coins to burn.

Oh well... as soon as that dies my rental will be back online.

Thanks.  Will be happy to have you point your hash here.  The more base hash the pool has the better for everyone

Jonny's about to get going... just waiting on the second confirmation from NH...