Unable to fetch latest batch

lightninglabs / pool

Lightning Pool: a non-custodial batched uniform clearing-price auction for Lightning Channel Leases (LCL). An LCL packages up inbound channel liquidity (ability to receive funds) as a fixed income asset with a maturity date expressed in blocks.

MIT License

255 stars 47 forks source link

Unable to fetch latest batch #274

Open rek79 opened 3 years ago

rek79 commented 3 years ago

I have Lightning Pool up and running with account funded successfully. I was also able to create an ask order. However, the order is never filled even though the premium is within market range. Periodic errors received through web interface are shown below. Are those errors normal? Is it possible that the order is not being filled due to Node Tier=T0 and offered liquidity is only 400,000 sats?

LIT logs:

Order gets filled.

Order does not get filled.

Hardware: Odroid HC2 Software: Raspiblitz v1.7 running on Armbian Buster OS

guggero commented 3 years ago

The "context deadline exceeded" is golang's way of saying "request timed out". It sounds like your network connection is slow at times. Are you running Tor only? This could also explain why your order doesn't get matched, you need to be able to connect out to the matched party within a given time or your match will be canceled.

rek79 commented 3 years ago

Yes, connection is Tor only. Are there any settings I can tweak to allow Tor operation?

rek79 commented 3 years ago

@guggero I wasn't sure from your previous response if it's possible to run Tor only with Lightning Pool. Will I need to configure my node to run over clearnet in order to fill orders?

guggero commented 3 years ago

Are you running all connections through Tor? For example with something like Torify? Because the call that is timing out should normally go through clearnet, even if lnd is using Tor only.

You can use a Tor only node with Lightning Pool. But it'll mean that your node needs to connect out to all takers and if that times out the order won't be filled. Try restarting and updating your Tor proxy to make sure you get fresh circuits if you have general connection issues.

rek79 commented 3 years ago

I restarted about a week ago and that seemed to have gotten rid of the error messages originally reported. However, still no takers. I'm running Raspiblitz with Tor only config. Bitcoind config file has onlynet = onion. Here is the full config file:

bitcoind config:

lnd config:

guggero commented 3 years ago

There aren't a lot of batches going on yet. And if your node is T0 people need to opt-in to receive liquidity from your node. So this might take a good while. Also there currently are way more asks than bids.

rek79 commented 3 years ago

Okay, that makes sense. Thanks. I'll read up on ways to increase the tier of my node.