Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Torq to v1.0.10 #820

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ohenrik
Copy link

@ohenrik ohenrik commented Jul 29, 2023

This release is only available using docker or binaries since the source code is now closed source.

Torq v1.0

New:

  • Connections status: Provides insight into the internals of Torq. (People often ask if there is a way to see if it's still importing data; well, now you can!)
  • LND: Select an outbound channel for payment
  • Keep historic information about tagging/untagging
  • Manually request a channel from an LSP that is following the LSP channel request specification (i.e. Deezy)
  • HTLC information in Open Channels
  • Quick filter with fuzzy search on listing screens
  • Mempool API integration for fee recommendations

New HTLC Firewall workflows:

  • You can create one or more workflows to firewall/drop HTLCs. (i.e. block any HTLC coming from peer1 going to peer2 below a certain amount. Or block any HTLC if the amount of pending HTLC for a peer is above a certain amount)
  • New HTLC Firewall Related workflow nodes:
    • HTLC Intercepted (Trigger): Every HTLC will trigger the workflow when HTLC interceptor is enabled in the node's settings
    • HTLC Event (Data Source): Starting point for the HTLC Firewall workflow
    • HTLC Filter (Filter): Allows you to filter base on the HTLC's incoming and/or outgoing amount
    • HTLC Channel Split (Filter): This splits the flow and you can chose to continue with either the incoming channel or outgoing channel from the HTLC
    • HTLC Channel Join (Filter): After a split you can chose to join the flow back together
    • HTLC Blocker (Action): This will firewall/drop the HTLC if something passed through it's parent

New workflow nodes:

  • Close channel: be very careful with this one so you don't accidentally close a channel because of a logical error in your workflow!
  • Open channel
  • Request channel: You can now automatically request a channel from an LSP that is following the LSP channel request specification (i.e. Deezy)

Workflow update:

  • Dry-run a workflow
  • Capture workflow logs
  • Visualize workflow logs in a flow diagram, including very detailed information for debugging workflows
  • HTLC filterable data added to Channel Filter (i.e. summary of all pending HTLCs for peer1)

Updates:

  • Improved filtering on the peers page
  • Various optimizations and updates

Torq pay:

  • We've never hidden the fact that some day you will have to pay to use Torq.
  • This release starts a new phase for our startup.
  • You will need a subscription and we chose to use Stripe for the initial launch.
  • We ourselves are a startup looking for a good model to be able to provide the power of Torq to as many node operators as possible, so please don't hesitate to reach out to provide feedback! Let's take lightning to the next level, together!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant