Quote from: BitMaxz on Today at 11:38:27 PM

Quote from: Jodmapht on Today at 11:24:16 PM

Yes it is fully synced. Before I rebooted it a couple of hours ago it had been running for months. And the blockheight matches mempool.space/testnet

Are you running a prune node? I suggest disable it if it is set to prune.

Are you able to send tBTC on-chain? I mean normally send testnet coins, not by opening channels. Test it first and let's see if this is only by opening the channel or even on-chain doesn't work.

What is your current node system specs? Are you in Ubuntu?

Can you try to edit the bitcoin.conf and add this "maxmempool=500" without qoutes or change it to 1000 then test make sure to restart bitcoind.
If you still having issue try adding this on the Bitcoin.conf file "mempoolexpiry=72" then restart it again and test.

No it is not a pruned node:

./bin/bitcoin-cli -testnet getblockchaininfo
{
"chain": "test",
"blocks": 4075162,
"headers": 4075162,
"bestblockhash": "000000000ff380e4ddabeaef62b63a23a29b57fe0c93257a2aaf5a6420c66ffd",
"difficulty": 1,
"time": 1742866878,
"mediantime": 1742865677,
"verificationprogress": 1,
"initialblockdownload": false,
"chainwork": "0000000000000000000000000000000000000000000016426f159b1301805f97",
"size_on_disk": 189685877847,
"pruned": false,
"warnings": "Unknown new rules activated (versionbit 28)"
}

I am using FreeBSD on arm64. I am bitcoind running in another jail with mainnet and I don't have any issue. I had maxmempool set to 300, I just increased it to 1000 and set mempoolexpiry to 72:

2025-03-24T23:56:36Z * Using 37.2 MiB for transaction index database
2025-03-24T23:56:36Z * Using 32.6 MiB for basic block filter index database
2025-03-24T23:56:36Z * Using 8.0 MiB for chain state database
2025-03-24T23:56:36Z * Using 220.2 MiB for in-memory UTXO set (plus up to 953.7 MiB of unused mempool space)

./bin/bitcoin-cli -testnet estimatesmartfee 1 economical
{
"errors": [
"Insufficient data or no feerate found"
],
"blocks": 2
}