Your next step is to see if the chain is fully synched. In your wallet dump, there is the line
> Last seen best block: 46367 (2013-01-02T05:58:10Z) which implies it doesn't synch. Or maybe it synches, but is just very slow. Read the logs. On 07/12/2017 01:23 PM, santiago del valle wrote: > I dont really what to do, seems that this is probably simple to solve > but Im really stuck in this. > Watching the Log I see in each Tx Hash this: > [ STARTING] INFO org.bitcoinj.wallet.Wallet - New broadcaster so > uploading waiting tx > 6009856d8aea2b0161730783e6ab0c0ce6a6ab24e35375835050d2bb031fa65b > [ STARTING] INFO org.bitcoinj.core.TransactionBroadcast - Waiting for 10 > peers required for broadcast, we have 0 ... > > El miércoles, 12 de julio de 2017, 21:02:59 (UTC+10), Andreas Schildbach > escribió: > > According to https://testnet.blockexplorer.com > <https://testnet.blockexplorer.com>, your transactions are > confirmed. But in your wallet dump, they're still pending. Try synching > the chain again. If the problem persists, the synch doesn't work. In > this case carefully study the logfile. > > > On 07/12/2017 12:38 PM, santiago del valle wrote: > > I have a DownloadListener attached to the WalletAppKit, it gets fired > > everytime a block is downloaded > > > > > > Wallet containing 0.006 BTC (spendable: 0.00 BTC) in: > > > > > 6 pending transactions > > > > > 0 unspent transactions > > > > > 0 spent transactions > > > > > 0 dead transactions > > > > > Last seen best block: 46367 (2013-01-02T05:58:10Z): > > 00000000037835a92404acb2f18768a49d4f93685ead30aad6bb3b073f411e02 > > > > > > > > Keys: > > > > > Earliest creation time: 2017-07-10T14:10:29Z > > > > > addr:mrXUTn2Ppe7iWszweQKCSnBPVocM75WorV > > hash160:78c290f8f0faf24e7cbd2bc96ba7cecd210e1273 > > creationTimeSeconds:1499695830 > > > > > Seed birthday: 1499695829 [2017-07-10T14:10:29Z] > > > > > Key to watch: > > > > tpubD8TWDx4Wgnoq6fCKBL8qfwmpNUPjDo8peuV4i7p2djLshkmUkALxDSuti8yJiF5dACwQQgpMySiqCj463LLte5FgMiYyS1G5jus7bSku7nX > > > > > > addr:mvw9ExaSTDhHwW9dQ5CHgkcLaVrQC5BBJM > > hash160:a91d01f43b8c10ba9cb05fa07fe0b17d0a6d680e (M/0H/0/0) > > > > > addr:mscDf4bmhE1DUfKjXtdCyfivJaduQJfaov > > hash160:84a069b72a0ba737d1d46020845726a40db171dd (M/0H/0/1) > > > > > > > > > > > >>> PENDING: > > > > > 0.001 BTC total value (sends 0.00 BTC and receives 0.001 BTC) > > > > > confidence: Seen by 4 peers (most recently: 2017-07-10T19:42:32Z). > > Pending/unconfirmed. Source: NETWORK > > > > > a6225bb48c7bb1ff8bc2ac2a2f45f5f65d085b3f640551f54130be8ae857ac91 > > > > > updated: 2017-07-10T19:42:33Z > > > > > in > > > > PUSHDATA(71)[30440220758c401c31f6153acbfb3ba824f6ab197e9734549c0df1708b521cb185a4f2ad02201f50ef3bdc0437c58098d81ac7263974caa2c447948c5ebc89538911b99e23de01] > > > > > PUSHDATA(33)[03f4fca867f44b01f86f3ab2fd2cf5fe677d8599f53d211b405d9ac224fab0404c] > > > > > > > > > > outpoint:02477bcba479ccd3a7336b1a5bbd06afe5a3e6b95db2fe0f5282be7646c6a6af:0 > > > > > > out DUP HASH160 > > PUSHDATA(20)[df14854b7b86c650b84666710be64dc1a847f637] EQUALVERIFY > > CHECKSIG 0.6897 BTC > > > > > out DUP HASH160 > > PUSHDATA(20)[a91d01f43b8c10ba9cb05fa07fe0b17d0a6d680e] EQUALVERIFY > > CHECKSIG 0.001 BTC > > > > > prps UNKNOWN > > > > > 0.001 BTC total value (sends 0.00 BTC and receives 0.001 BTC) > > > > > confidence: Seen by 7 peers (most recently: 2017-07-10T19:42:32Z). > > Pending/unconfirmed. Source: NETWORK > > > > > 6009856d8aea2b0161730783e6ab0c0ce6a6ab24e35375835050d2bb031fa65b > > > > > updated: 2017-07-10T19:42:27Z > > > > > in > > > > PUSHDATA(72)[3045022100a120ddd564dccb2cc9fb8034c41a6271219ec7c549d5035b7fc45e88413b037402205338c01e5b055eef2981851dbf40b9a28317eced14a569e6f8da55de8c34d56a01] > > > > > PUSHDATA(33)[033ea8a2d9446382eab9360ce478542070e4ca0ad945a3e5e68382e9753c49064f] > > > > > > > > > > outpoint:f246d9f04e0faac6e23c44c5dc38bd225534d7e703adfffd933a93091df4e79d:0 > > > > > > out DUP HASH160 > > PUSHDATA(20)[22939ef4e1cd162a7d42657cc85de8a786b0e13f] EQUALVERIFY > > CHECKSIG 0.4288 BTC > > > > > out DUP HASH160 > > PUSHDATA(20)[a91d01f43b8c10ba9cb05fa07fe0b17d0a6d680e] EQUALVERIFY > > CHECKSIG 0.001 BTC > > > > > prps UNKNOWN > > > > > 0.001 BTC total value (sends 0.00 BTC and receives 0.001 BTC) > > > > > confidence: Seen by 10 peers (most recently: > 2017-07-10T19:42:32Z). > > Pending/unconfirmed. Source: NETWORK > > > > > 67d12bca5b8a9cd6ec14332473f5a5e15a46f973d712a5ec77b4713eeda5b0dd > > > > > updated: 2017-07-10T19:42:23Z > > > > > in > > > > PUSHDATA(72)[3045022100cc7b03b0b1d6ceb1553b42e844cad8b9282c158cb00a1fd884c48f65a261e30502207adc987d4d63ba40eaf7b0be5872d4a2e2767292b330b16ca216508f1c425a2a01] > > > > > PUSHDATA(33)[028925bf095a7bdd92857a44c9703b69ede304c97efc1618fd95f1a059f96d9f05] > > > > > > > > > > outpoint:25191ba5f82b0bc5d5b86d00879d810c7e177b9587a24fa24e13bd3b1c82f3c1:0 > > > > > > out DUP HASH160 > > PUSHDATA(20)[df1f5614c3ea5ddda399e933080a60179cb54737] EQUALVERIFY > > CHECKSIG 0.3877875 BTC > > > > > out DUP HASH160 > > PUSHDATA(20)[a91d01f43b8c10ba9cb05fa07fe0b17d0a6d680e] EQUALVERIFY > > CHECKSIG 0.001 BTC > > > > > prps UNKNOWN > > > > > 0.001 BTC total value (sends 0.00 BTC and receives 0.001 BTC) > > > > > confidence: Seen by 11 peers (most recently: > 2017-07-10T19:42:28Z). > > Pending/unconfirmed. Source: NETWORK > > > > > 3fe0d3e33af3790f270bcb0d95bda5dd527e024df7ec7e9e269b1baee34207a1 > > > > > updated: 2017-07-10T19:42:19Z > > > > > in > > > > PUSHDATA(72)[304502210083a61b340a46dca4d7a69cb2e5ce76e7adfc1072929948de92c4c8f6fa12cc3102206ed602b46e73efde17204dc0f4b5eb8739e7b15a51248e07f4eeba1127aee38401] > > > > > PUSHDATA(33)[03ec24876204546cf020586ac1e6b67d24bbba44fca2d7748d71501f9bf83cab30] > > > > > > > > > > outpoint:17e40592e1814291db85e6a7e540260731b0123b0d8bb559805d048534dbd1f3:0 > > > > > > out DUP HASH160 > > PUSHDATA(20)[4023d529d617918a52923163d1088af0a2004059] EQUALVERIFY > > > > El miércoles, 12 de julio de 2017, 20:22:23 (UTC+10), Andreas > Schildbach > > escribió: > > > > 1. Make sure the app synchs the blockchain. WalletAppKit does > this. > > > > The wallet dump is the output of Wallet.toString(). Just copy > and paste > > it to here, assuming that it's still quite small. > > > > > > On 07/12/2017 12:09 PM, santiago del valle wrote: > > > Thanks for the fast answer. > > > 1. How to tell BitcoinJ to confirm those Tx? > > > 2. Im not using the "emptyWallet" feature. But if I do, how > would > > be the > > > convenient way to do it? > > > > > > How to post my Wallet Dump, sorry! > > > > > > Thanks > > > > > > El miércoles, 12 de julio de 2017, 19:09:20 (UTC+10), Andreas > > Schildbach > > > escribió: > > > > > > Two common reasons for this: > > > > > > 1. The incoming payments are not confirmed yet, or bitcoinj > > doesn't > > > know > > > about the confirmations yet. > > > > > > 2. You're not covering the network fee. This commonly > happens > > if you > > > try > > > to send all you have without using the "emptyWallet" > feature. > > > > > > Maybe you'd like to post your wallet dump? > > > > > > > > > On 07/12/2017 10:25 AM, santiago del valle wrote: > > > > Hi, Im creating an Android App, Im being able to receive > > coins but > > > when > > > > I try to send them says that Im missing Bitcoins to > send, I > > have > > > 0.006 > > > > BTC in a Testnet Wallet, I dont really know what Im > missing to > > > achieve > > > > sending BTC. The BTC I received now have more that 3 > block > > depth. > > > > > > > > walletAppKit = new WalletAppKit(testNet, walletDir, > > > "bitcoin_wallet"){ > > > > > > > > @Override > > > > protected void onSetupCompleted() { > > > > super.onSetupCompleted(); > > > > > > > > > > > > if (wallet().getImportedKeys().size() < 1) { > > > > wallet().importKey(new ECKey()); > > > > } > > > > > > > > Coin value1 = > > > > walletAppKit.wallet().getBalance(Wallet.BalanceType.AVAILABLE); > > > //0.00BTC > > > > > > > > Coin value2 = > > > > > > walletAppKit.wallet().getBalance(Wallet.BalanceType.AVAILABLE_SPENDABLE); > > > > > > //0.00BTC > > > > Coin value3 = > > > > walletAppKit.wallet().getBalance(Wallet.BalanceType.ESTIMATED); > > > //0.006 BTC > > > > Coin value4 = > > > > > > walletAppKit.wallet().getBalance(Wallet.BalanceType.ESTIMATED_SPENDABLE); > > > > > > //0.006 > > > > > > > > .... > > > > > > > > -- > > > > You received this message because you are subscribed > to the > > Google > > > > Groups "bitcoinj" group. > > > > To unsubscribe from this group and stop receiving emails > > from it, > > > send > > > > an email to bitcoinj+u...@googlegroups.com > > > > <mailto:bitcoinj+u...@googlegroups.com>. > > > > For more options, visit > https://groups.google.com/d/optout <https://groups.google.com/d/optout> > > <https://groups.google.com/d/optout > <https://groups.google.com/d/optout>> > > > <https://groups.google.com/d/optout > <https://groups.google.com/d/optout> > > <https://groups.google.com/d/optout > <https://groups.google.com/d/optout>>>. > > > > > > > > > -- > > > You received this message because you are subscribed to the > Google > > > Groups "bitcoinj" group. > > > To unsubscribe from this group and stop receiving emails > from it, > > send > > > an email to bitcoinj+u...@googlegroups.com > > > <mailto:bitcoinj+u...@googlegroups.com>. > > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout> > > <https://groups.google.com/d/optout > <https://groups.google.com/d/optout>>. > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "bitcoinj" group. > > To unsubscribe from this group and stop receiving emails from it, > send > > an email to bitcoinj+u...@googlegroups.com > > <mailto:bitcoinj+u...@googlegroups.com>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to bitcoinj+unsubscr...@googlegroups.com > <mailto:bitcoinj+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
