|
| 1 | +# Release Notes |
| 2 | +- [Bug Fixes](#bug-fixes) |
| 3 | +- [New Features](#new-features) |
| 4 | + - [Functional Enhancements](#functional-enhancements) |
| 5 | + - [RPC Additions](#rpc-additions) |
| 6 | + - [tapcli Additions](#tapcli-additions) |
| 7 | +- [Improvements](#improvements) |
| 8 | + - [Functional Updates](#functional-updates) |
| 9 | + - [RPC Updates](#rpc-updates) |
| 10 | + - [tapcli Updates](#tapcli-updates) |
| 11 | + - [Breaking Changes](#breaking-changes) |
| 12 | + - [Performance Improvements](#performance-improvements) |
| 13 | + - [Deprecations](#deprecations) |
| 14 | +- [Technical and Architectural Updates](#technical-and-architectural-updates) |
| 15 | + - [BIP/bLIP Spec Updates](#bipblip-spec-updates) |
| 16 | + - [Testing](#testing) |
| 17 | + - [Database](#database) |
| 18 | + - [Code Health](#code-health) |
| 19 | + - [Tooling and Documentation](#tooling-and-documentation) |
| 20 | + |
| 21 | +# Bug Fixes |
| 22 | + |
| 23 | +# New Features |
| 24 | + |
| 25 | +## Functional Enhancements |
| 26 | + |
| 27 | +- A new [address version 2 was introduced that supports grouped assets and |
| 28 | + custom (sender-defined) |
| 29 | + amounts](https://github.com/lightninglabs/taproot-assets/pull/1587). When |
| 30 | + creating an address, the user can now specify `--address_version v2`. The |
| 31 | + amount is optional for V2 addresses, and if it is not specified by the |
| 32 | + receiver, the sender can choose any amount to send. V2 addresses with custom |
| 33 | + amounts work for both simple assets (non-grouped/asset ID only) and grouped |
| 34 | + assets. In addition, V2 addresses also increase on-chain privacy and therefore |
| 35 | + are ideal as re-usable, long-term static addresses (with on-chain privacy |
| 36 | + guarantees similar to BIP-0352 Silent Payments). |
| 37 | + V2 addresses require the use of a proof courier that supports the |
| 38 | + new `authmailbox+universerpc://` protocol. Any `tapd` that runs with version |
| 39 | + `v0.7.0` or later and uses `universe.public-access=rw` automatically supports |
| 40 | + that new protocol. Users running with the default configuration (and therefore |
| 41 | + the default/standard universe servers) will not need to change anything, as |
| 42 | + the default universe servers will be updated after the release of |
| 43 | + `tapd v0.7.0`. |
| 44 | + |
| 45 | +## RPC Additions |
| 46 | + |
| 47 | +- The `SendAsset` RPC has a new field `addresses_with_amounts` that allows the |
| 48 | + user to specify a custom amount to send to a V2 address that doesn't have an |
| 49 | + amount specified. |
| 50 | + |
| 51 | +## tapcli Additions |
| 52 | + |
| 53 | +- The `tapcli assets send` command now has a new flag `--addr_with_amount` that |
| 54 | + allows users to specify the amount to send to a V2 address that allows custom |
| 55 | + amounts (which is the case when a V2 address is created with an amount of 0). |
| 56 | + |
| 57 | +# Improvements |
| 58 | + |
| 59 | +## Functional Updates |
| 60 | + |
| 61 | +## RPC Updates |
| 62 | + |
| 63 | +## tapcli Updates |
| 64 | + |
| 65 | +## Code Health |
| 66 | + |
| 67 | +## Breaking Changes |
| 68 | + |
| 69 | +## Performance Improvements |
| 70 | + |
| 71 | +## Deprecations |
| 72 | + |
| 73 | +# Technical and Architectural Updates |
| 74 | + |
| 75 | +## BIP/bLIP Spec Updates |
| 76 | + |
| 77 | +## Testing |
| 78 | + |
| 79 | +## Database |
| 80 | + |
| 81 | +## Code Health |
| 82 | + |
| 83 | +## Tooling and Documentation |
| 84 | + |
| 85 | +# Contributors (Alphabetical Order) |
| 86 | + |
| 87 | +- ffranr |
| 88 | +- George Tsagkarelis |
| 89 | +- Olaoluwa Osuntokun |
| 90 | +- Oliver Gugger |
0 commit comments