Unable to submit ask order in pool
Closed this issue · 4 comments
Expected behavior
Order successfully placed
Actual behavior
2022-02-18 07:54:43.590 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/SubmitOrder]: rpc error: code = Unknown desc = cannot submit channel
type preference with old trader client, please update your software
To reproduce
Go to pool UI
Select ask
enter amount
click suggest rate
place order
System information
litd running as standalone
connecting to remote lnd 0.14.2
pool-mode
/usr/local/bin/litd -V
litd version 0.14.2-beta commit=lightning-terminal-v0.6.3-alpha
not relevant
macOS
2022-02-18 08:00:15.176 [INF] SESS: Checking for schema update: latest_version=0, db_version=0
2022-02-18 08:00:15.181 [INF] LITD: Dialing lnd gRPC server at localhost:10009
2022-02-18 08:00:15.220 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
2022-02-18 08:00:15.567 [INF] LNDC: Creating lnd connection to localhost:10009
2022-02-18 08:00:15.567 [INF] LNDC: Connected to lnd
2022-02-18 08:00:15.569 [INF] LNDC: Waiting for lnd to unlock
2022-02-18 08:00:15.570 [INF] LNDC: Wallet state of lnd is now: Lnd main server is ready for requests
2022-02-18 08:00:15.692 [INF] LNDC: lnd version: v0.14.2-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watcht
owerrpc,monitoring,kvdb_postgres,kvdb_etcd'
2022-02-18 08:00:15.692 [INF] LNDC: Using network mainnet
2022-02-18 08:00:15.692 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
2022-02-18 08:00:15.813 [INF] LNDC: lnd is now fully synced to its chain backend
2022-02-18 08:00:15.931 [INF] LOOPD: Swap server address: swap.lightning.today:11010
2022-02-18 08:00:15.998 [INF] STORE: Checking for schema update: latest_version=4, db_version=4
2022-02-18 08:00:16.187 [INF] POOL: Version: 0.5.4-alpha commit=v0.5.4-alpha.0.20220114202858-525fe156d240
2022-02-18 08:00:16.187 [INF] LOOPD: Waiting for updates
2022-02-18 08:00:16.187 [INF] LOOPD: Starting swap client
2022-02-18 08:00:16.187 [INF] LOOPD: Starting liquidity manager
2022-02-18 08:00:16.187 [INF] LOOP: Connected to lnd node xxx with pubkey xxx (version v0.14.2-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,monitoring,kvd
b_postgres,kvdb_etcd')
2022-02-18 08:00:16.188 [INF] LOOP: Wait for first block ntfn
2022-02-18 08:00:16.188 [INF] LOOP: Starting event loop at height 723856
2022-02-18 08:00:16.288 [INF] POOL: Auction server address: pool.lightning.finance:12010
2022-02-18 08:00:16.344 [INF] CLDB: Checking for schema update: latest_version=1, db_version=1
2022-02-18 08:00:16.344 [INF] RPCS: Starting trader server
2022-02-18 08:00:16.465 [INF] RPCS: Connected to lnd node xxx with pubkey xxx
2022-02-18 08:00:16.471 [INF] ACCT: Watching spend of xxx:5 for account
xxx
2022-02-18 08:00:17.766 [INF] AUCT: Successfully connected to auction server
2022-02-18 08:00:18.314 [INF] FNDG: Starting funding manager
2022-02-18 08:00:18.314 [INF] FNDG: Funding manager is now active
2022-02-18 08:00:18.314 [INF] RPCS: Trader server is now active
2022-02-18 08:00:18.572 [INF] SESS: Mailbox RPC server listening on xxx
xxx@mailbox.terminal.lightning.today:443
2022-02-18 08:00:18.572 [INF] SESS: Mailbox RPC server listening on mailbox:xxx
xxx@mailbox.terminal.lightning.today:443
...
2022-02-18 08:15:35.931 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/SubmitOrder]: rpc error: code = Unknown desc = cannot submit channel type preference with old trader client, please update your software
Thank you for submitting the bug report. This is a known issue of the UI and we are currently working on a fix.
In the meantime, it should be possible for you to submit orders through the command line. See this doc so find out how to use the pool command against your LiT installation.
It's now possible to submit orders via UI but the channels are created with ORDER_CHANNEL_TYPE_SCRIPT_ENFORCED type (I use lnd 0.14.99-beta) and they never get fulfilled as per lightninglabs/pool#349. Is it possible to use more compatible channel type or set it in the UI? I'm not sure this channel type issue is a part of the OP one.
We'll address the channel type issue in a separate PR to Pool. This was that we could bump the order version which enables a few other functionalities. I hope to have a solution to the channel type issue before releasing a new version of LiT.
Same issue here. Looking forward for fix. Thank you