<p>Looking at the Makefile</p>

<p>start:
    $(BITCOIND) $(B1) -daemon
    $(BITCOIND) $(B2) -daemon</p>

<p>start-gui:
    $(BITCOINGUI) $(B1) &amp;
    $(BITCOINGUI) $(B2) &amp;</p>

<p>so probably <strong><em>make start-gui</em></strong> will work for you</p>

CC BY-SA 3.0
2016-07-01T19:01:43.747Z
2016-07-01T19:01:43.747Z
carvmarc
<p>Use the <code>-testnet</code> option. This will run the daemon in testnet.</p>

CC BY-SA 3.0
2016-07-01T08:56:46.597Z
I think that will run it for the global testnet- isn't that right? I want to just run it on my own *local* testnet- I think it's different
smatthewenglish
CC BY-SA 3.0
2016-07-01T18:59:54.643Z
They're the same thing. The way testnet-in-a-box prevents connecting to the global testnet is by connecting only to each other. Essentially, your daemon thinks you have the longest chain because it doesn't see the global testnet.
Jimmy Song
CC BY-SA 3.0
2016-06-30T18:59:21.713Z
2016-06-30T18:59:21.713Z
Jimmy Song
<p>I'm running a small testnet locally with this project: </p>

<p><a href="http://github.com/freewil/bitcoin-testnet-box" rel="nofollow">http://github.com/freewil/bitcoin-testnet-box</a></p>

<p>but I'm having trouble pointing bitcoin-qt to the blockchain that I created locally myself, so I have some data like this: </p>

<pre><code>bitcoin-cli -datadir=1  getinfo
{    
    "version" : 90300,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000000,
    "testnet" : false,
    "keypoololdest" : 1413617762,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
bitcoin-cli -datadir=2  getinfo
{
    "version" : 90300,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000000,
    "testnet" : false,
    "keypoololdest" : 1413617762,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
</code></pre>

<p>and I want that to be the data, and the addresses that is picked up and incorporated by bitcoin-qt. I guess there should be some flags to facilitate this but everything I've tried so far always in unsuccessful- maybe someone on here knows or has some idea? </p>

<bitcoin-core><testnet><bitcoin-qt-setup><local>
is there a way to run bitcoin-qt and point it to a local testnet?
smatthewenglish
# is there a way to run bitcoin-qt and point it to a local testnet?

(Asked by: username_0 on 2016-06-30)

I'm running a small testnet locally with this project: 
http://github.com/freewil/bitcoin-testnet-box
but I'm having trouble pointing bitcoin-qt to the blockchain that I created locally myself, so I have some data like this: 
bitcoin-cli -datadir=1  getinfo
{    
    "version" : 90300,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000000,
    "testnet" : false,
    "keypoololdest" : 1413617762,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
bitcoin-cli -datadir=2  getinfo
{
    "version" : 90300,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000000,
    "testnet" : false,
    "keypoololdest" : 1413617762,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}

and I want that to be the data, and the addresses that is picked up and incorporated by bitcoin-qt. I guess there should be some flags to facilitate this but everything I've tried so far always in unsuccessful- maybe someone on here knows or has some idea?

**Tags:** bitcoin-core, testnet, bitcoin-qt-setup, local


---

## 2 answers

### Answer by username_1 on 2016-07-01. Score: 1 | Accepted answer

Looking at the Makefile

start:
$(BITCOIND) $(B1) -daemon
$(BITCOIND) $(B2) -daemon

start-gui:
$(BITCOINGUI) $(B1) &
$(BITCOINGUI) $(B2) &

so probably ***make start-gui*** will work for you


---

### Answer by username_2 on 2016-06-30. Score: 1

Use the `-testnet` option. This will run the daemon in testnet.

> **Comments:**
> **username_0**: I think that will run it for the global testnet- isn't that right? I want to just run it on my own *local* testnet- I think it's different  
> **username_2**: They're the same thing. The way testnet-in-a-box prevents connecting to the global testnet is by connecting only to each other. Essentially, your daemon thinks you have the longest chain because it doesn't see the global testnet.  

---

