It is necessary to enable tx relay, but since you have done that (and restarted) there should be nothing else to do as long as you are synced past your last checkpoint and haven't set a too-small mempool size. It is possible that your mempool is too small and is therefore losing txs due to overflow. Please review the debug log for more insight.
e
> On Dec 24, 2015, at 12:16 PM, Kobi Gurkan <kobigurk@???> wrote:
>
> Missed an important part - bx with the default endpoint shows the unconfirmed transactions.
>
>> On 24/12/15 19:15, Kobi Gurkan wrote:
>> Hi,
>>
>> I'm working with the latest 2.2.0 release, and having a hard time getting unconfirmed transactions with fetch-history.
>> I'm accessing the query port by both nodejs and bx and I don't get unconfirmed transactions back in the result, only confirmed ones.
>> I thought that some configuration was missing, so I tried changing relay_transactions to true, but there isn't any change.
>>
>> Am I missing something obvious?
>>
>> Kobi
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
::
Re: [Libbitcoin] fetch-history with…
