|
26 | 26 | - [An integration test flake was |
27 | 27 | fixed](https://github.com/lightninglabs/taproot-assets/pull/1651). |
28 | 28 |
|
29 | | -- Fixed two send related bugs that would lead to either a `invalid transfer |
30 | | - asset witness` or `unable to fund address send: error funding packet: unable |
| 29 | +- Fixed two send related bugs that would lead to either a `invalid transfer |
| 30 | + asset witness` or `unable to fund address send: error funding packet: unable |
31 | 31 | to list eligible coins: unable to query commitments: mismatch of managed utxo |
32 | 32 | and constructed tap commitment root` error when sending assets. |
33 | 33 | The [PR that fixed the two |
|
36 | 36 | tombstone outputs on a full-value send (by using interactive transfers for V2 |
37 | 37 | addresses). |
38 | 38 |
|
39 | | -- [Updated](https://github.com/lightninglabs/taproot-assets/pull/1774) |
| 39 | +- [Updated](https://github.com/lightninglabs/taproot-assets/pull/1774) |
40 | 40 | `BuyOrderRequest` and `SellOrderRequest` proto docs to mark `peer_pub_key` as |
41 | 41 | required. Previously, the field was incorrectly documented as optional. |
42 | 42 | This change corrects the documentation to match the current implementation. |
|
179 | 179 | - [Rename](https://github.com/lightninglabs/taproot-assets/pull/1682) the |
180 | 180 | `MintAsset` RPC message field from `universe_commitments` to |
181 | 181 | `enable_supply_commitments`. |
| 182 | + |
182 | 183 | - [Enhanced RFQ accepted quote messages with asset identification fields](https://github.com/lightninglabs/taproot-assets/pull/1805): |
183 | 184 | The `PeerAcceptedBuyQuote` and `PeerAcceptedSellQuote` proto messages |
184 | 185 | now include asset ID and asset group pub key fields (via the `AssetSpecBytes` |
185 | 186 | message), allowing clients to directly associate quotes with their |
186 | 187 | corresponding assets without manual tracking. |
187 | 188 |
|
188 | | -- The `SubscribeSendEvents` RPC now supports [historical event replay of |
| 189 | +- The `SubscribeSendEvents` RPC now supports [historical event replay of |
189 | 190 | completed sends with efficient database-level |
190 | 191 | filtering](https://github.com/lightninglabs/taproot-assets/pull/1685). |
191 | 192 | - [Add universe RPC endpoint FetchSupplyLeaves](https://github.com/lightninglabs/taproot-assets/pull/1693) |
192 | 193 | that allows users to fetch the supply leaves of a universe supply commitment. |
193 | 194 | This is useful for verification. |
194 | 195 |
|
195 | | -- A [new field `unconfirmed_transfers` was added to the response of the |
| 196 | +- A [new field `unconfirmed_transfers` was added to the response of the |
196 | 197 | `ListBalances` RPC |
197 | 198 | method](https://github.com/lightninglabs/taproot-assets/pull/1691) to indicate |
198 | 199 | that unconfirmed asset-related transactions don't count toward the balance. |
|
204 | 205 | - The `AddrReceives` RPC now supports timestamp filtering with |
205 | 206 | [new `StartTimestamp` and `EndTimestamp` fields](https://github.com/lightninglabs/taproot-assets/pull/1794). |
206 | 207 |
|
207 | | -- The [FetchSupplyLeaves RPC endpoint](https://github.com/lightninglabs/taproot-assets/pull/1829) |
208 | | - is now accessible without authentication when the universe server is |
209 | | - configured with public read access. This matches the behavior of the |
| 208 | +- The [FetchSupplyLeaves RPC endpoint](https://github.com/lightninglabs/taproot-assets/pull/1829) |
| 209 | + is now accessible without authentication when the universe server is |
| 210 | + configured with public read access. This matches the behavior of the |
210 | 211 | existing FetchSupplyCommit RPC endpoint. |
211 | 212 |
|
212 | 213 | - [PR#1839](https://github.com/lightninglabs/taproot-assets/pull/1839) The |
|
239 | 240 | includes unset and zero-valued proto fields (e.g. transaction output indexes). |
240 | 241 | This ensures consistent output shape across all proto messages. |
241 | 242 |
|
242 | | -- The `tapcli addrs receives` command now supports |
| 243 | +- The `tapcli addrs receives` command now supports |
243 | 244 | [new `--start_timestamp` and `--end_timestamp` flags](https://github.com/lightninglabs/taproot-assets/pull/1794). |
244 | 245 |
|
245 | 246 | - The `tapcli addrs receives` command now has new flags `--limit`, `--offset` and |
|
0 commit comments