Move the LiT/LND compatibility matrix into docs/compatibility.md for
archival so future releases no longer require README updates to adjust
the table.
Update README to direct users to release notes for minimum lnd versions
and fall back to the archived table when not specified.
This information is now available in the GitHub release notes for each
release. Removing it from the README simplifies the project release
procedure (no need to update) and avoids unnecessary duplication,
reducing the risk of inconsistencies.
With a upgrade to a never version of newer golang.org/x/tools/govet,
a lint check to check for legacy buildtag lines starting with
`// +build` has been added, as they're no longer needed.
In order for the `make lint` check to pass with the newer version, we
remove such buildtag lines.
If there are no RPCParamsJson set for an action, the value is
represented differently in KVDB vs SQL.
In the SQL DB, empty RPCParamsJson are represented as nil, while they
are represented as an empty array in the KVDB version. Therefore, we
need to override the RPCParamsJson in that scenario, so that they are
set to the same representation when a KVDB and an SQL action is
compared.
Bump `lnd` to v0.20.0-beta.rc2, `loop` to `v0.31.5-beta`, `tapd` to
`v0.7.0-rc2` and `lndclient` to `v0.20.0-3`.
Also bump `looprpc`, `swapserverrpc` and `taprpc` to the versions used
in the respective releases.
This commit also includes an update to the protos and sample data to
reflect the changes in the bumped dependencies.
In the bbolt store, an empty config for a feature is represented as an
empty array, while in for the SQL store, the same config is represented
as nil. Therefore, in the scenario where a specific feature has an empty
config, we override the SQL FeatureConfig for that feature to also be
set to an empty array. This is needed to ensure that the deep equals
check in the migration validation does not fail in this scenario.
With the introduction of multi-rfq send in taproot assets (see related
PR https://github.com/lightninglabs/taproot-assets/pull/1613) we
extended the behavior of the SendPayment RPC slightly.
Now we may not specify an RFQ peer in order for a list of peers to be
created & used automatically. When that happens, we will return multiple
quotes over the RPC.
The content of this commit changes our client wrapper around the
handling of the payment result. Previously we'd expect for exactly a
single quote to be returned over the stream (for the single defined
peer). Now we read all of the quotes that are returned in the new quotes
array field of the RPC. To maintain backwards compatibility we also kept
the previous single-quote RPC field, which we make sure to only read
once now that we read both fields (avoid a duplicate quote from
appearing in the logs).
With the latest version of tapd we no longer require the rfq field to be
set. If left unset then AddInvoice/SendPayment will automatically
acquire quotes in order for the operation to be carried out.
