adb logcat ?
I started a root shell and run the command "adb logcat" and the answer was: "daemon not running. starting it on port xxxxx daemon started successfully waiting for device"
Topic: Getting Coins out of testnet in a box (Read 2578 times)
I'm not sure why it wouldn't connect, what does adb logcat on your phone say? Perhaps the issue is that Andreas may have checkpointed the testnet version of the wallet app as well. Testnet in a box isn't used much these days, I think.
By the way, there should soon be a new regtest mode which would simplify app development more than testnet-in-a-box does.
By the way, there should soon be a new regtest mode which would simplify app development more than testnet-in-a-box does.
Does anyone have a idea how i can make this work ?
The clients on my computer is bitcoin-qt 0.7.0.
I can ping between my computer to my phone and back again. I am able to get the two bitcoin-qt processes to connect to another with my 192.168.10.67 ip number that my computer have.
What is keypool?
The clients on my computer is bitcoin-qt 0.7.0.
I can ping between my computer to my phone and back again. I am able to get the two bitcoin-qt processes to connect to another with my 192.168.10.67 ip number that my computer have.
What is keypool?
I have but it doesn't connect.
here is the conf files:
1:
2:
And i have set the ip of my computer as the trusted ip with the port number of 19000 and then reset the blockchain so the client would get the blocks from my computer. But over the list of block in the mobile app the is one block that i can not get rid of , is that a problem ?
So what is the problem why is it not working?
Thanks in advance
here is the conf files:
1:
Code:
# Important for testnet-in-a-box functionality:
testnet=1
irc=0
dnsseed=0
upnp=0
# Feel free to change these.
# Be careful if you decide to listen on the default testnet
# port (18333), if somebody on the main testnet
# chain connects to you then your chain will be
# over-written.
rpcuser=test
rpcpassword=123
port=19000
rpcport=19001
keypool=5
testnet=1
irc=0
dnsseed=0
upnp=0
# Feel free to change these.
# Be careful if you decide to listen on the default testnet
# port (18333), if somebody on the main testnet
# chain connects to you then your chain will be
# over-written.
rpcuser=test
rpcpassword=123
port=19000
rpcport=19001
keypool=5
2:
Code:
# Important for testnet-in-a-box functionality:
testnet=1
irc=0
dnsseed=0
upnp=0
listen=0
connect=127.0.0.1:19000
# Feel free to change these:
rpcuser=test
rpcpassword=123
port=19010
rpcport=19011
keypool=5
testnet=1
irc=0
dnsseed=0
upnp=0
listen=0
connect=127.0.0.1:19000
# Feel free to change these:
rpcuser=test
rpcpassword=123
port=19010
rpcport=19011
keypool=5
And i have set the ip of my computer as the trusted ip with the port number of 19000 and then reset the blockchain so the client would get the blocks from my computer. But over the list of block in the mobile app the is one block that i can not get rid of , is that a problem ?
So what is the problem why is it not working?
Thanks in advance
If you're using Andreas Schildbach's wallet, grab the testnet version then in the settings screen set your trusted peer to the IP address of one of your nodes.
Hi i have problem.
I have two bitcoin-qt processes running and mining is working fine but i have a bitcoin testnet client i want to connect so i can transfer testnet coins to my mobile. How can i make this work?
My mobile is connected to the wireless that is the same network.
I have two bitcoin-qt processes running and mining is working fine but i have a bitcoin testnet client i want to connect so i can transfer testnet coins to my mobile. How can i make this work?
My mobile is connected to the wireless that is the same network.
testnet in a box is supposed to come with a huge balance "out of the box", but I didn't make v3 so maybe it's not been done in the same way?
If I recall correctly, the first testnet-in-a-box node should have all the coins. The second starts with a zero balance / empty wallet (send it coins from the first if you need to...).
testnet in a box is supposed to come with a huge balance "out of the box", but I didn't make v3 so maybe it's not been done in the same way?
To be extra conservative the protocol requires 120 blocks before generated coins can be sent. If we have a >120 block re-org we likely have big problems. 
Nitpick: the protocol only requires 100 confirmations before allowing to spend a coinbase output, but the client enforces 120, to be safe in the presence of reorganisations.
In case anyone else is wondering this occurs on main-net also. It is a security feature. In the event of a re-orrg generated coins will cease to exist. Unlike normal tx the unconfirmed tx can't simply be submitted again as that block which generated the coins will never exist in this fork of the chain and thus the tx using those coins as an input (and any tx "downstream") will all be invalid and can never become valid.
It can create double spend losses (even accidental ones) as the re-org affects not just the generating tx but any "downstream" txs too.
To be extra conservative the protocol requires 120 blocks before generated coins can be sent. If we have a >120 block re-org we likely have big problems.
It can create double spend losses (even accidental ones) as the re-org affects not just the generating tx but any "downstream" txs too.
To be extra conservative the protocol requires 120 blocks before generated coins can be sent. If we have a >120 block re-org we likely have big problems.
Fantastic. Thank you very much for the clarification.
Am I missing something fundamental here settings wise? Any help would be appreciated.
Your coins are immature.Mined coins will not be added to the balance for a 120 blocks after they are created.
Hello,
I'm running the testnet-in-a-box 3 configs against Bitcoin daemon 6.03 and I've got both instances of bitcoind talking to each other (one connection each), however whenever the mining instance generates a block - there is no balance increase:
Am I missing something fundamental here settings wise? Any help would be appreciated.
I'm running the testnet-in-a-box 3 configs against Bitcoin daemon 6.03 and I've got both instances of bitcoind talking to each other (one connection each), however whenever the mining instance generates a block - there is no balance increase:
Code:
C:\PROGRA~1\Bitcoin>bitcoind -datadir=1 getinfo
{
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000, <----?
"blocks" : 2,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.12500000,
"testnet" : true,
"keypoololdest" : 1346156689,
"keypoolsize" : 6,
"paytxfee" : 0.00000000,
"errors" : ""
}
{
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000, <----?
"blocks" : 2,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.12500000,
"testnet" : true,
"keypoololdest" : 1346156689,
"keypoolsize" : 6,
"paytxfee" : 0.00000000,
"errors" : ""
}
Am I missing something fundamental here settings wise? Any help would be appreciated.
Jump to: