You might try leaving transaction_pool_consistency disabled in config (though it shouldn't matter). No need to rebuild or re-sync when changing mempool settings, restart is sufficient.

I wouldn’t use master for comparison as It isn’t considered stable.

"No missing transactions from [194.187.96.2:8333] inventory" means that the transaction inventory from the peer contained no transactions that were missing from the local mempool.

Feel free to send me a full log. You could get fully synced, switch your config, clear your log and then start up, post your test transaction to the network, let it run for a few minutes, query using bx, and then send me the log. I could do this myself but I'm traveling and have limited capability.

e

------

From: Kobi Gurkan [mailto:kobigurk@gmail.com]
Sent: Sunday, December 27, 2015 8:04 AM
To: Eric Voskuil <eric@???>
Cc: libbitcoin@???
Subject: Re: [Libbitcoin] fetch-history with unconfirmed transactions

OK, I'm pretty sure I'm doing something wrong.
I tried the same with freshly built master, still no unconfirmed transactions.

Kobi
On 27/12/15 10:35, Kobi Gurkan wrote:
Hi Eric,

Thanks for that, but still having issues.

To avoid any confusions - I tried syncing from scratch with relay_transactions = true and an enlarged transaction pool capacity.
Still can't see unconfirmed transactions while the default node that bx talks to does see them.

I believe the log indicates the transaction inventory is saved, like this line :
08:34:38.891999 DEBUG [inventory] Transaction inventory from [194.187.96.2:8333] dc44299f386f4d76fccef1518dd46724fa299bf0c03cefd03592f46877298112
08:34:38.892067 DEBUG [inventory] No missing transactions from [194.187.96.2:8333] inventory

I attach my complete configuration file, maybe you can spot something here?

[network]
# The number of threads in the network threadpool, defaults to 4.
threads = 4
# The port for incoming connections, defaults to 8333 (18333 for testnet).
inbound_port = 8336
# The maximum number of incoming network connections, defaults to 0.
inbound_connection_limit = 0
# The maximum number of outgoing network connections, defaults to 1.
outbound_connections = 2
# The time limit for connection establishment, defaults to 5.
connect_timeout_seconds = 5
# The time limit to complete the connection handshake, defaults to 15.
channel_handshake_seconds = 15
# The time between blocks that initiates a request, defaults to 1.
channel_poll_seconds = 1
# The time between ping messages, defaults to 5.
channel_heartbeat_minutes = 5
# The inactivity time limit for any connection, defaults to 10.
channel_inactivity_minutes = 10
# The maximum age limit for an outbound connection, defaults to 1440.
channel_expiration_minutes = 1440
# Request that peers relay transactions, defaults to false.
relay_transactions = true
# The maximum number of peer hosts in the pool, defaults to 1000.
host_pool_capacity = 1000
# The peer hosts cache file path, defaults to 'hosts.cache'.
hosts_file = hosts.cache
# The debug log file path, defaults to 'debug.log'.
debug_file = debug.log
# The error log file path, defaults to 'error.log'.
error_file = error.log
# The advertised public address of this node, defaults to none.
self = 0.0.0.0:0
# A seed node for initializing the host pool, multiple entries allowed, defaults shown.
seed = seed.bitnodes.io:8333
seed = seed.bitcoinstats.com:8333
seed = seed.bitcoin.sipa.be:8333
seed = dnsseed.bluematt.me:8333
seed = seed.bitcoin.jonasschnelli.ch:8333
seed = dnsseed.bitcoin.dashjr.org:8333
# Testnet seed nodes.
#seed = testnet-seed.alexykot.me:18333
#seed = testnet-seed.bitcoin.petertodd.org:18333
#seed = testnet-seed.bluematt.me:18333
#seed = testnet-seed.bitcoin.schildbach.de:18333
[blockchain]
checkpoint = 00000000000000000937e53693c22140975adf349ac61aa2c90479fa60aee92e:390149
[node]
# The number of threads in the node threadpool, defaults to 4.
threads = 4
# The minimum block bytes per minute during initial block download, defaults to 1000000.
minimum_bytes_per_minute = 1000000
# The maximum number of transactions in the pool, defaults to 2000.
transaction_pool_capacity = 200000
# Enforce consistency between the pool and the blockchain, defaults to false.
transaction_pool_consistency = true
# Persistent host:port to augment discovered hosts, multiple entries allowed.
# peer = obelisk.airbitz.co:8333
# IP address to disallow as a peer, multiple entries allowed.
# blacklist = 127.0.0.1

[server]
# The query service endpoint, defaults to 'tcp://*:9091'.
query_endpoint = tcp://*:19091
# The heartbeat service endpoint, defaults to 'tcp://*:9092'.
heartbeat_endpoint = tcp://*:19092
# The block publishing service endpoint, defaults to 'tcp://*:9093'.
block_publish_endpoint = tcp://*:19093
# The transaction publishing service endpoint, defaults to 'tcp://*:9094'.
transaction_publish_endpoint = tcp://*:19094
# Enable the block and transaction publishing endpoints, defaults to false.
publisher_enabled = true
# Enable the query and heartbeat endpoints, defaults to false.
queries_enabled = true
# Write service requests to the log, defaults to false.
log_requests = true
# The query polling interval in milliseconds, defaults to 1000.
polling_interval_milliseconds = 1000
# The heartbeat interval in seconds, defaults to 5.
heartbeat_interval_seconds = 5
# The subscription expiration time, defaults to 10 minutes.
subscription_expiration_minutes = 10
# The maximum number of subscriptions, defaults to 100000000.
subscription_limit = 100000000
# The path to the ZPL-encoded server private certificate file.
# certificate_file =
# The directory for ZPL-encoded client public certificate files, allows anonymous clients if not set.
# client_certificates_path =
# Allowed client IP address, all clients allowed if none set, multiple entries allowed.
# whitelist = 127.0.0.1
On 25/12/15 19:21, Eric Voskuil wrote:
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