Bitcoin Forum
July 16, 2018, 10:40:00 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
   Home   Help Search Donate Login Register  
Pages: [1]
Author Topic: Testnet / mining / limiting impact  (Read 865 times)
Offline Offline

Activity: 76
Merit: 10

View Profile
August 31, 2014, 05:46:13 PM

Hi folks.

For some 3rd party integration testing, we need a fair chunk (one-two hundred for now) of real-testnet btc.

I think I might have made a bit of a mess yesterday, by dumping a KnC Jupiter onto the testnet, while my testnet bitcoind was still playing catchup - I had something like 25000 test btc showing in my wallet, and then none - so I guess I created a local orphan chain or something?  Whatever they were they seem to have gone now.

I think I've split a bit of my Jupiter off now...

  "pools": [
      "quota": "100;stratum+tcp://",
      "user": "jaymax.apollo",
      "pass": "zzzzzzzzzzzzzzzzz"
      "quota": "10;",
      "user": "bitcoinrpc",
      "pass": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  "api-listen": true,
  "api-network": true,
  "api-allow": "W:0/0",
  "load-balance": true

And have apparently mined one block for 25 coin at txid 31e23ded018e48789f6f9e92937db53e02ac92f91754fa7c5a245b1ba6316653
(although I'm not 100% sure if the pool was enabled at that time.)

It seems odd that the output from cgminer is all about Pool 0, never about Pool 1 (that I've caught anyhow) - I'm guessing this has something to do with pool-mining vs solo-mining?  I'm wondering if having cgminer split between testnet and the real net like this might confuse it somehow?

So anyhows, I'd just like to know if I should be doing anything differently to either minimise testnet impact, or to collect the coins we need.

Thanks - and apologies for any noobishness...
Pages: [1]
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!