lightninglabs / lightninglabs/taproot-assets
[feature]: Extend reporting of transitory/limbo transaction states (CLI/RPC)
@GeorgeTsagk is already working on this.
Since Nov 7, 2023.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
When assets move into a transitory state (e.g. burning an asset), the daemon stops listing assets because it intends to remove them from the wallet's ownership. There's then an apparent UX disparity between 1) what's being reported by tapd 2) the state that's included in blocks 3) The state that could confirm by a broadcasted transaction. The daemon would benefit in terms of UX, and future functionality, by reporting these classes of transitory / limbo state. The CLI should be intuitive to users in the scenario where the burn etc is in limbo while the daemon waits for the transaction to be included in a block.
- User feedback has been given that transitory state not being available makes it confusing what's has or is about to happen
- **Important to payment-channel functionality, the daemon's architecture will benefit from being able to keep track of and report pending transaction**
## Deliverable
`tapd` should be enhanced to report transitory / in-flight / limbo transactions
lnd's `lncli pendingchannels` command could be a parallel:
https://github.com/lightningnetwork/lnd/blob/e6fbaafda4a9cfe08ccee5106aa6dc1da62bcebc/rpcserver.go#L3823-L3858
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.