API Updates

LNURL-Pay

• Add support for LUD-06 and LUD-16 payRequests, enabling reusable deposit destinations via Lightning. 

• LNURL destinations can be displayed as strings, human readable Lightning addresses or QR codes. 

• Lighting destinations can be created via the API, allowing clients to specify the associated username for a lightning address. 

• All clients are given a random LNURL domain by default for use with lightning addresses. For example, a user could receive Bitcoin at satoshi@orange-pill.riverlightning.com.

• Custom subdomains and custom domains are available for paying tiers. For example, satoshi@your-company.com.

• Lightning destinations are treated as deposit intents, which can be fetched via the API.

Vouchers (LNURL-Withdraw)

• Add support for vouchers (LUD-03 LNURL withdrawRequests) to streamline withdrawals. 

• The API response returns the voucher details, allowing River Lightning clients to transform these into QR codes which end users can scan to pull funds into an LNURL-enabled Lightning wallet. 

• Vouchers can be created via the API with parameters for amount, fee_limit, expiry, and LNURL domain. 

• Vouchers can be locked to prevent use.

• Clients can fetch voucher details and statuses via the API.

Fixes & Improvements

• TOTP security improvements.

• Update data structure for web platform users and API keys in anticipation of increased functionality.

• Updates to rate limit policy for public endpoints.

• Data architecture changes to support future product lines.

Web Platform Updates

• Completed support for all on-chain workflows. This feature now supports the ability to initiate on-chain withdrawals through the platform for permissioned users, and to view or generate new on-chain deposit addresses.

• Surfaced initiator field in transaction details.

• Removed unwanted autocomplete flows from the platform.

• Cleaned up transactions table UI.

• Improved the password reset flow.

• Enabled autofocus on user inputs.

• Added on-chain volume to the transaction volume chart.

• Added LNURL details to transaction details for LNURL-pay withdrawals.

New Feature Work

• Added the ability to embed custom description hashes in invoices.

• Backend work to prep for a new feature supporting deposits to lightning addresses via LNURL-Pay. 

• Backend work to prep for a new feature supporting withdrawals with LNURL vouchers via LNURL-Withdrawal.

Fixes & Improvements

• Improved error handling for WITHDRAWAL_AMOUNT mismatch.

• Improved error handling for DESCRIPTION_HASH mismatch.

• Added tracking for the initiator of an event. 

• Transitioned API docs to a new vendor for improved usability and readability.

Web Updates

• Transactions details panel now automatically closes when a user paginates through transaction history. 

• Verbiage was standardized across web platform pages.

• Minor UI cleanup and fixes.

• The login form added navigation to contact sales & support.

API Updates

• On-chain withdrawals can now be initiated via the API. This functionality supports specifying fee tiers so clients can decide between speed and cost savings, while River assesses the necessary fee for each urgency level. Additionally, the withdrawals can set nominal fee limits to avoid excessively expensive withdrawals during mempool congestion. This endpoint is also supported by the estimate_fee endpoint. 

• Added preimage as a response field for relevant withdrawal objects.

• Removed the requirement for users to indicate the network of their withdrawals. Instead, it is now auto-detected based on the destination format, simplifying API calls.

• Destination_type is now returned in withdrawal responses.

• Added a Content-Type: application/json; charset=UTF-8 header to webhook requests.

Web Redesign

We’ve created a completely new feel for the River Lightning Web experience. River introduced a new blue-centric color scheme, and refreshed the UI to feel more lively. This update makes it easier to find key information, by displaying key statistics on the overview page, and adding new search capabilities to transactions. 

The update introduces new navigation options and moves to a left-hand navigation. Common workflows, such as functionality for user management and logging out became more accessible. The update also adds payment preimage data to withdrawals in the dashboard to help operational team members quickly diagnose payment status and give updates. 

Updates & Fixes

• The API added a response field for destination_type to withdrawals. 

• River Lightning clients can now generate new onchain deposit addresses using the deposit intent endpoint. 

• The API documentation was updated to be more intuitive and correct minor inconsistencies with actual API behavior.