question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LSAT paid w/ no notice or confirmation

See original GitHub issue

I just downloaded the latest LiT release and started running it using an existing “remote” lnd (running on the same machine). It started up fine and I was able to pull up the terminal in my browser. The terminal page looks fine, but when I go to the “Lightning Pool” page (my main motivation for trying this out) I get a blank page that only says “Lightning Pool” at the top. I don’t see any errors in the litd logs, I’ve included the relevant snippet from the first time I visited the pool page.

I also realized after the fact that my node paid a 1000 sat invoice for an LSAT token upon visiting the pool page - which I assume is to retrieve information about the pool bid/ask orders. It’s a small but non-trivial amount and it seems like poor UX that it was paid automatically without any confirmation or even notice on my behalf. It’s also unfortunate that I don’t know exactly what the LSAT token is for, or how long it’s good for.

Logs:

2020-11-03 00:44:28.386 [INF] LITD: Handling static file request: /static/js/6.84ee280e.chunk.js
2020-11-03 00:44:28.472 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListAccounts
2020-11-03 00:44:28.477 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListOrders
2020-11-03 00:44:28.590 [ERR] AUCT: [/poolrpc.ChannelAuctioneer/Terms]: rpc error: code = Internal desc = payment required
2020-11-03 00:44:28.590 [INF] LSAT: Payment of LSAT token is required, paying invoice
2020-11-03 00:44:32.059 [INF] LNDC: Payment 8e141a947e35459d3e2406b8d24da42c95ab0752d9d48753ecaa217f053ea922 completed
2020-11-03 00:45:48.430 [INF] LITD: Handling static file request: /pool
2020-11-03 00:45:48.539 [INF] LITD: Handling static file request: /static/js/3.679bad4f.chunk.js
2020-11-03 00:45:48.540 [INF] LITD: Handling static file request: /static/js/main.8c764815.chunk.js
2020-11-03 00:45:48.879 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2020-11-03 00:45:48.928 [INF] LITD: Handling static file request: /static/js/6.84ee280e.chunk.js
2020-11-03 00:45:48.999 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListAccounts
2020-11-03 00:45:49.000 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListOrders
2020-11-03 00:45:49.054 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetInfo
2020-11-03 00:45:49.156 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ListChannels
2020-11-03 00:45:49.189 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/SubscribeTransactions
2020-11-03 00:45:49.237 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/SubscribeChannelEvents
2020-11-03 00:45:49.286 [INF] LITD: Handling gRPC web request: /looprpc.SwapClient/Monitor
2020-11-03 00:45:49.305 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/GetChanInfo
2020-11-03 00:45:49.311 [INF] LITD: Handling gRPC web request: /looprpc.SwapClient/ListSwaps
2020-11-03 00:45:49.313 [INF] LOOPD: Monitor request received
2020-11-03 00:45:49.367 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/ChannelBalance
2020-11-03 00:45:49.479 [INF] LITD: Handling gRPC web request: /lnrpc.Lightning/WalletBalance
2020-11-03 00:47:49.414 [INF] LITD: Handling static file request: /static/js/7.b59c0e8a.chunk.js
2020-11-03 00:48:05.057 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListAccounts
2020-11-03 00:48:05.058 [INF] LITD: Handling gRPC web request: /poolrpc.Trader/ListOrders

I can provide system details if that would be helpful.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
jamaljsrcommented, Feb 23, 2021

Agreed, I’ve already begun working on adding this confirmation prompt to the UI. I’ll have a PR up by the end of this week. Thanks for additional info.

1reaction
jamaljsrcommented, Mar 2, 2021

Instead of adding the confirmation prompt to the UI, we’ve decided to remove the requirement for an LSAT on the server for the RPC calls made on page load. You can now view the Pool page without incurring the 1000sat payment. This should resolve this issue going forward for all new users. Thanks for the feedback everyone.

Read more comments on GitHub >

github_iconTop Results From Across the Web

LSAC Candidate Agreement: Terms and Conditions for the ...
In the event that LSAC rescinds or cancels the registration of any Candidate who registers to take the Test but does not schedule...
Read more >
Frequently Asked Questions about LSAT Writing - LSAC
In most cases, a canceled writing sample is not reported to any law schools. When your LSAT Writing is canceled for certain rules...
Read more >
Fee Waivers for the LSAT & Credential Assembly Service (CAS)
Fees previously paid cannot be waived retroactively, and no refunds will be issued. Please note: Some law schools will waive their application fees...
Read more >
LSAT Score Audit | The Law School Admission Council
No. The Score Audit itself is a verification of your full set of test responses, a comparison of those responses with the correct...
Read more >
Getting Ready for Your LSAT Exam - LSAC
Please note: Other proctoring software applications may interfere or conflict with ... (If you do not already have an account with ProctorU, this...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found