synonymdev / lsp-ui

Blocktank LSP admin dashboard

LSP UI

Recommended resolution for your embedded widget:

• width - 480px
• height - 800px

<iframe
	style="margin: auto; min-width: 480px; min-height: 800px;"
	id="widget"
	src="https://widget.synonym.to/"
	seamless
></iframe>

Set environment variables

The following environment variables are required to run the app:

REACT_APP_MAINNET=true // or false

Set this environment variable if you want to test in regtest:

REACT_APP_API_URL="https://api.stag.blocktank.to/blocktank/api/v2/"

Available Scripts

⚠️ Switch to the Node.js version defined in .node-version. You can visit .node-version File Usage and use one of these methods to change the node version you need.

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner in the interactive watch mode.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

yarn build:mainnet and yarn build:testnet

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
It also sets the REACT_APP_MAINNET environment variable to true or false respectively.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

lsp-ui's Issues

Not able to open a channel to a Tor node?

Getting a "HTTP error 500", when trying to open a channel to a node with Tor address.
Steps followed:

1. Pay invoice
2. Select 'claim manually'
3. Enter the node's complete address and click on 'Open Channel'

Might also have to do with my node's Tor config.

Feature: change Channel failed text

Description

This copy has been updated to cover more edge cases and can be implemented in the frontend as well.

Preview:

Bug: ListItem key is not a prop.

Description

I'm getting this error: component ListItem key is not a prop.

Add min-height to the styling of the widget

Adding min-height to the styling of the widget (maybe the #root element) would make the use of this widget with iframes much more convenient.

Suggestion: 788px as it is the current while on the on-chain payment invoice screen.

Feature: add language picker

Add multilanguage support.

Feature: autocomplete amount/values from error messages.

UX optimization

Allow the user to click an error message to set the value of the input field to the amount mentioned in the error message. Use the amounts/values for the error messages as currently set in the frontend code.

Feature: delete failed/expired orders

Description

Implement this 'delete failed/expired orders' functionality in the Widget frontend.
No confirmation dialog needed, only for failed/expired orders.

---

Preview

Order ID not displayed to the user

Order ID should be displayed to the user

• when the invoice is paid for opening the channel
• on the order status display

User can reference the order ID, in case follow up is required for problems related to channel opening. This should enable easier handling of the support request.

I did notice the order id on the mailto link, on the Contact Support button. But user may not always want to use that button to reach out for support, so having explicit knowledge of the order ID should be helpful.