hey, this was a long time ago, but looks like I wasn't sending with enough
fee
Reject: tx efc9b24967eadf77661ef2376f7e7f278a76c4ce2ce4a24b1348e3bf15af452a
for reason 'insufficient priority' (66)
INSUFFICIENTFEE
I have manually increased the fee value of the SendRequest to a very high
value, and now is working.
On Mon, Apr 23, 2018 at 2:07 AM, <aman.v...@mobiloittegroup.com> wrote:
> Hi Rodrigo
>
> Can you please help by answering how was your problem resolved.As I am
> stuck in same problem
>
>
> On Friday, November 6, 2015 at 3:29:27 AM UTC+5:30, Rodrigo Acosta wrote:
>>
>> Yes, I have upgraded to 13.3 and also review the debug log of the core
>> clients. But there is nothing there related to the transaction,
>>
>> While examining in more detail the Broadcast object used to publish the
>> transaction to the core client, I'm seeing this response:
>>
>> Reject: tx efc9b24967eadf77661ef2376f7e7f278a76c4ce2ce4a24b1348e3bf15af452a
>> for reason 'insufficient priority' (66)
>> INSUFFICIENTFEE
>>
>> I have manually increased the fee value of the SendRequest to a very high
>> value, and now is working.
>>
>> I also set at the core clients the config value txconfirmtarget=1000 and
>> make sure I'm forcing a fee higher that 1000 satoshis.
>>
>> I need to investigate more but this is a great step towards the solution
>> for me.
>>
>>
>>
>> El miércoles, 28 de octubre de 2015, 7:09:48 (UTC-3), Andreas Schildbach
>> escribió:
>>>
>>> No I don't see anything wrong. Did you try using 0.13.3? I've got no
>>> experience with RegTest, I always use Testnet.
>>>
>>> Did you also look at the log of the Bitcoin Core peer(s) that receive
>>> the transaction? It might contain further hints.
>>>
>>>
>>> On 10/27/2015 10:01 PM, Rodrigo Acosta wrote:
>>> > So you don't see anything wrong in my code Andreas?
>>> > I'm focusing in the clients configuration and tried many different
>>> > things, so I just want to remove the change of having a mistake in the
>>> > code that send the bitcoins.
>>> >
>>> > Thanks!
>>> >
>>> > El domingo, 25 de octubre de 2015, 10:46:10 (UTC-3), Andreas
>>> Schildbach
>>> > escribió:
>>> >
>>> > The special case of connecting to just one peer is perhaps not
>>> well
>>> > tested. First of all, an you update to bitcoinj 0.13.3 and try
>>> again?
>>> >
>>> >
>>> > On 10/24/2015 10:43 PM, Rodrigo Acosta wrote:
>>> > > Hi everybody, I think I have been with this issue for more than
>>> a
>>> > week
>>> > > now, so I'm kind of desperate already.
>>> > >
>>> > > I'm working in RegTest with bitcoinj 13.1
>>> > >
>>> > > I have written a simple console program, that connects to
>>> localhost
>>> > > publish a receive address and when I have positive balance, I
>>> start
>>> > > sending and broadcasting the transaction.
>>> > > The event listeners tells me that bitcoins are being sent, but
>>> for
>>> > some
>>> > > reason I can't understand, then are not being received by the
>>> bitcoin
>>> > > core client.
>>> > >
>>> > > This is simplified code:
>>> > >
>>> > > public class NewMain {
>>> > >
>>> > > /**
>>> > > * @param args the command line arguments
>>> > > */
>>> > > public static void main(String[] args) throws
>>> > BlockStoreException,
>>> > > UnreadableWalletException, InterruptedException, IOException,
>>> > > AddressFormatException, InsufficientMoneyException,
>>> > ExecutionException,
>>> > > TimeoutException {
>>> > > NetworkParameters networkParameters =
>>> RegTestParams.get();
>>> > > Wallet wallet = null;
>>> > >
>>> > > File walletFile = new File("wallet1");
>>> > > if (walletFile.exists()){
>>> > > wallet = Wallet.loadFromFile(walletFile);
>>> > > } else
>>> > > {
>>> > > wallet = new Wallet(networkParameters);
>>> > > }
>>> > >
>>> > > BlockStore blockStore = new
>>> > MemoryBlockStore(networkParameters);
>>> > > BlockChain blockChain = new
>>> BlockChain(networkParameters,
>>> > > wallet, blockStore);
>>> > > PeerGroup peers = new PeerGroup(networkParameters,
>>> > blockChain);
>>> > > peers.addWallet(wallet);
>>> > >
>>> > > InetSocketAddress inetSocketAddress = new
>>> > > InetSocketAddress("192.168.1.140", 18444); //my local client ip
>>> > address
>>> > > and port
>>> > > PeerAddress peerAddress = new
>>> > PeerAddress(inetSocketAddress);
>>> > > peers.addAddress(peerAddress);
>>> > > peers.start();
>>> > > peers.downloadBlockChain();
>>> > > System.out.println(wallet.fre
>>> shReceiveAddress().toString());
>>> > >
>>> > > while (true){
>>> > >
>>> > System.out.println(wallet.getBalance().toFriendlyString());
>>> > >
>>> > > Thread.sleep(5000);
>>> > > if (wallet.getBalance().isPositive()){
>>> > > Address address = new Address(networkParameters,
>>> > > "mpxZhWE8saKxnpdihMPm3oSJ5EZqp3xLWU"); //this is by bitcoin
>>> core
>>> > client
>>> > > address
>>> > >
>>> > > Wallet.SendRequest sendRequest =
>>> > > Wallet.SendRequest.to <http://Wallet.SendRequest.to>(address,
>>> > Coin.valueOf(1000));
>>> > > wallet.completeTx(sendRequest);
>>> > >
>>> > > wallet.commitTx(sendRequest.tx);
>>> > >
>>> > > TransactionBroadcast future =
>>> > > peers.broadcastTransaction(sendRequest.tx);
>>> > > future.future().get();
>>> > > }
>>> > > wallet.saveToFile(walletFile);
>>> > > }
>>> > > }
>>> > >
>>> > > }
>>> > >
>>> > >
>>> > > The sl4f output is
>>> > >
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet completeTx
>>> > > INFO: Completing send tx with 1 outputs totalling 0.00001 BTC
>>> (not
>>> > > including fees)
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet completeTx
>>> > > INFO: with 9.99756 BTC change
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet completeTx
>>> > > INFO: with a fee of 0.00001 BTC
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet completeTx
>>> > > INFO: completed:
>>> > > bee4efde20bfd8ed202a1c7f788219a8c625a2c00fa64ac13403b62f4826a150:
>>>
>>> > > Unknown confidence level.
>>> > > in
>>> > >
>>> > PUSHDATA(71)[304402201199daf1e9464af2376726f9c043a6ea9e3132e
>>> 8c5625be639b16d035462d1ec02200999eca7a6cc09d189d94c5fb59581c
>>> 3c674396844e35d02e1633540729fb2af01]
>>> >
>>> > >
>>> >
>>> > PUSHDATA(33)[0276592c2a0226817bd4e4f03842137cbbaffb13a4c5d6ee8d4e99a7c1530e212b]
>>>
>>> >
>>> > > 9.99758 BTC
>>> > >
>>> > >
>>> >
>>> > outpoint:bd0194f8f8fb39f6ee44a9efc2b17eab6b4dabb806ae9d4fbb6cdb12a40f0f78:0
>>>
>>> >
>>> > > hash160:c14667686855952e563629157eaef59b1437afc8
>>> > > out DUP HASH160
>>> > > PUSHDATA(20)[679115cba74e7e5cef11af7df135320ad1baf44d]
>>> EQUALVERIFY
>>> > > CHECKSIG 0.00001 BTC
>>> > > out DUP HASH160
>>> > > PUSHDATA(20)[04e795508549e05810270e8fed102bb6820291d6]
>>> EQUALVERIFY
>>> > > CHECKSIG 9.99756 BTC
>>> > > fee 0.00001 BTC
>>> > >
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet maybeCommitTx
>>> > > INFO: commitTx of
>>> > > bee4efde20bfd8ed202a1c7f788219a8c625a2c00fa64ac13403b62f4826a150
>>>
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet updateForSpends
>>> > > INFO: marked
>>> > > bd0194f8f8fb39f6ee44a9efc2b17eab6b4dabb806ae9d4fbb6cdb12a40f0f78:0
>>>
>>> > as spent
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.Wallet maybeCommitTx
>>> > > INFO: ->pending:
>>> > > bee4efde20bfd8ed202a1c7f788219a8c625a2c00fa64ac13403b62f4826a150
>>>
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.wallet.KeyChainGroup
>>> > > maybeMarkCurrentKeyAsUsed
>>> > > INFO: Marking key as used:
>>> > >
>>> >
>>> > DeterministicKey{pub=0336a1ee288841350c215346632ecc8090c8a5c75bec917f63639f88017b02d2ab,
>>>
>>> >
>>> > >
>>> >
>>> > chainCode=f6e9e57523f3c831b10dbf2dc9dea2dd6f068d35efb4141487a987bcd2504652,
>>>
>>> >
>>> > > path=M/0H/1/121, isEncrypted=false, isPubKeyOnly=false}
>>> > > Oct 24, 2015 5:33:10 PM org.bitcoinj.core.TransactionBroadcast
>>> > broadcast
>>> > > INFO: Waiting for 1 peers required for broadcast, we have 1 ...
>>> > > Oct 24, 2015 5:33:10 PM
>>> > > org.bitcoinj.core.TransactionBroadcast$EnoughAvailablePeers run
>>> > > INFO: broadcastTransaction: We have 1 peers, adding
>>> > > bee4efde20bfd8ed202a1c7f788219a8c625a2c00fa64ac13403b62f4826a150
>>>
>>> > to the
>>> > > memory pool
>>> > > Oct 24, 2015 5:33:10 PM
>>> > > org.bitcoinj.core.TransactionBroadcast$EnoughAvailablePeers run
>>> > > INFO: Sending to 1 peers, will wait for 0, sending to:
>>> > [192.168.1.140]:18444
>>> > >
>>> > > Which is everything normal, and bitcoins appears to be getting
>>> > send to
>>> > > my peer. I create blocks (with bitcoin-cli generate 1) but the
>>> > incoming
>>> > > transactions never reach the peer.
>>> > >
>>> > > What am I doing wrong!!!!
>>> > > pleaseeeee...
>>> > >
>>> > > I hope this is a very silly mistake like my last stupid question
>>> > >
>>> > > --
>>> > > 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+u...@googlegroups.com
>>> > <mailto:bitcoinj+u...@googlegroups.com>.
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "bitcoinj" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/bitcoinj/6GRHN8X--bE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> 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.
