Skip to content

v0.1.1

Choose a tag to compare

View all tags
@darioAnongba darioAnongba released this 02 Nov 20:34
v0.1.1
8b1cbe2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The v0.1 line carries the v0.3.0 API on the btcd v1 modules, for modules that also require the released lnd v0.21 and tapd v0.8 packages. It includes the 0.2.0 and 0.3.0 changes, except the move to btcd v2 modules. Modules on the btcd v2 line keep using v0.3.x.

Install

go get github.com/lightninglabs/tap-sdk@v0.1.1
go mod edit -replace=google.golang.org/protobuf=github.com/lightninglabs/protobuf-go-hex-display@v1.34.2-hex-display
go mod edit -replace=github.com/lightningnetwork/lnd/tlv=github.com/lightninglabs/taproot-assets/third_party/lnd/tlv@v0.0.0-20261016193543-734ce74dd1e8
go mod tidy

Added

  • AssetRecord.AnchorOutpoint, filled from tapd's chain anchor by both transports. Pass it to Wallet.ExportProofFile to export the exact output's proof when a script key is reused.

Changed

  • Build with the btcd v1 modules, lnd v0.21.3-beta, tapd v0.8.6, and taprpc v1.3.3, so the SDK can share a build with the released daemons.
  • Check custom-anchor activation evidence in the SDK, because tapd v0.8.6 does not export its check.
  • Require the lnd/tlv replacement from tapd v0.8.6 in consuming modules.

Fixed

  • Backend-signed custom-anchor inputs carry the wallet's key derivation and Taproot tweak, so assets received at V2 addresses can be spent. The input keeps the proof's script key.
  • The REST transport sends script-key and internal-key lookups as base64 path parameters, which the gateway requires.
Assets 2
Loading