i created watching wallet from offline wallet then i receive payment on watching wallet now i want to create a payment hash from watching wallet then sign this hash from offline wallet then i broadcast that transaction hash from watching wallet,
does bitcoinj support all these functionalities of working with offline and watching wallet ? On Saturday, May 5, 2018 at 6:57:17 AM UTC-7, Andreas Schildbach wrote: > > A watching wallet cannot spend. You need the private keys to spend, > which a watching wallet doesn't have. > > > On 05/04/2018 05:42 PM, Tyga wrote: > > i created watching wallet using bitcoinj, i am able to receive payments > > on WatchingWallet, but i am unable to send payment from this, when i try > > to send transaction i am getting this error: > > > > org.bitcoinj.core.InsufficientMoneyException: Insufficient money, > > missing 0.01001 BTC > > > > i also redownload the .spv file but still getting this error, i don't > > know what to do further as i am stuck here, kindly help. > > > > My wallet: > > > > _________________________________________ > > Wallet containing 0.333 BTC (spendable: 0.00 BTC) in: > > 0 pending transactions > > 3 unspent transactions > > 0 spent transactions > > 0 dead transactions > > Last seen best block: 1046303 (2016-12-04T15:29:13Z): > > 000000000131917ac459aefb91774dbb42caeca497afc0cfd1766e0338cc7f88 > > Wallet is watching. > > > > Keys: > > Earliest creation time: 2013-05-23T00:00:00Z > > Key birthday: 1369267200 [2013-05-23T00:00:00Z] > > Key to watch: > > > tpubD6NzVbkztN62j2dAvTmVdNL7x5YkRu8P4xkMXBx76dD4igKjzaF8pugmsiD4c6upTe5ro5gfWSF6g8oX5oMEKvn9GUVTfQBb1XE3JHSh2Bo > > > > addr:mpwmv1t2CcQnqqqoex1PH2MLhPDGYmVtGp > > hash160:676addc86a09d68eb19fd41b76df99df2b3f7c87 (M/0H/0/0) > > addr:mg7wLYPQ7hWetsPmB6j4U7RigQXUERSe3k > > hash160:069dc27c7c25761033711acc82318b2f62bcf9e0 (M/0H/0/1) > > addr:n3Xnm8fLruEvwKJmA8D3tsGVLJY5WuRRVz > > hash160:f17b39b0da74c77cc8a83f768878a03a749105f6 (M/0H/0/2) > > > > > >>>> UNSPENT: > > 0.111 BTC total value (sends 0.00 BTC and receives 0.111 BTC) > > confidence: Appeared in best chain at height 1296042, depth 2114532. > > Source: NETWORK > > 35b259b918e3c8e23fefa24bb91b408265709b4acd87de7a5179e38939295c6e > > updated: 2018-05-03T08:32:56Z > > in > > > > PUSHDATA(71)[30440220355660851e5bb4fe2783fd3cd6407189f5ab555b42dfa559857fb620e899398e0220216133bc96c8a0e8398c8730cf81619e26ab53d7b5519dfc11e60c817a6b15f001] > > > > > PUSHDATA(33)[021a3cbe7ba085934976f106817841db33ad5b20fbba5b7c66dedf260d94353c60] > > > > > > > outpoint:8220e10a11df1e5d25846f729235917df62671b30d06a251f27a3dec9f2fcb4f:0 > > out DUP HASH160 > > PUSHDATA(20)[069dc27c7c25761033711acc82318b2f62bcf9e0] EQUALVERIFY > > CHECKSIG 0.111 BTC > > out DUP HASH160 > > PUSHDATA(20)[98d938b26192f1be1d981f53d608d49c75f98003] EQUALVERIFY > > CHECKSIG 1.1699537 BTC > > prps UNKNOWN > > 0.111 BTC total value (sends 0.00 BTC and receives 0.111 BTC) > > confidence: Appeared in best chain at height 1295946, depth 2114628. > > Source: NETWORK > > d4fe818ab42317e3a35ff2710b35fc9c3e09e79bd59bd3c855dfff168d5812d3 > > updated: 2018-05-02T21:04:48Z > > in > > > > PUSHDATA(72)[3045022100e29904cb96f2aa27da9dc84f405051bc749d7f11ef73b1ba5b94c40611eadf5002202497cfe3565620b2a05a06c673534ef59eef1efda34deff870842e8ea59df87f01] > > > > > PUSHDATA(33)[034c2a246e9de8d37f1698bed2ccf35244fc5e42e4791b0ddc915140d05d211a90] > > > > > > > outpoint:6335255ee3da71dc341164dad60e5d312db0f2c0af7d824cba445d4c61e13ddb:0 > > out DUP HASH160 > > PUSHDATA(20)[069dc27c7c25761033711acc82318b2f62bcf9e0] EQUALVERIFY > > CHECKSIG 0.111 BTC > > out DUP HASH160 > > PUSHDATA(20)[54823f928764117fdd179f5704c72b938493a072] EQUALVERIFY > > CHECKSIG 0.49429671 BTC > > prps UNKNOWN > > 0.111 BTC total value (sends 0.00 BTC and receives 0.111 BTC) > > confidence: Appeared in best chain at height 1295933, depth 2114641. > > Source: NETWORK > > d8b7b39a976567b0ff83bf164d701ac0c9ea5fcf92168e29d1349695213a49e1 > > updated: 2018-05-02T20:00:34Z > > in > > > > PUSHDATA(71)[3044022014fdbebb717b8b9a90e905020c17edbee181cfcc7c5298c4c29ec1c7bcea17ef02204a8a21ff058847d1f140f5b834221512a5cd8595205bc7f31dca6d7ab430132801] > > > > > PUSHDATA(33)[03b1592edc4d71dafc5c14c6e5b478197e741f329dd49330ea6ae652bc5b330402] > > > > > > > outpoint:e0b7ee3fd391d769cf8b3ad23a87108485bfa917b615b44dca7cb82e7b0328da:0 > > out DUP HASH160 > > PUSHDATA(20)[676addc86a09d68eb19fd41b76df99df2b3f7c87] EQUALVERIFY > > CHECKSIG 0.111 BTC > > out DUP HASH160 > > PUSHDATA(20)[d6ca19a023ca0f8ec0277edc6fe687bfb4675b33] EQUALVERIFY > > CHECKSIG 0.5389092 BTC > > prps UNKNOWN > > > > -- > > 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 [email protected] <javascript:> > > <mailto:[email protected] <javascript:>>. > > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
