diff options
| author | Ryan Ofsky <ryan@ofsky.org> | 2023-07-19 16:28:24 -0400 |
|---|---|---|
| committer | Ryan Ofsky <ryan@ofsky.org> | 2023-07-19 16:43:12 -0400 |
| commit | 5608e1d3b4ba3a23c05937918046e428be890505 (patch) | |
| tree | 77186d3a53f0af0c1349149c3854cb45ff1793cf /src/rpc/client.cpp | |
| parent | 4d828ef427b26a0e36a34779b2567821f898d690 (diff) | |
| parent | f1d807e383942ae20e080174d33ac17afd649351 (diff) | |
Merge bitcoin/bitcoin#27928: test: Add more tests for the BIP21 implementation
f1d807e383942ae20e080174d33ac17afd649351 Add more tests for the BIP21 implementation (Kiminuo)
Pull request description:
This PR is an attempt to make it clear how the current BIP21 implementation behaves in Bitcoin Core. Especially, I'm interested whether one can specify multiple `amount` (`message`, etc.) parameters.
My primary end goal is to answer [this question of mine](https://bitcoin.stackexchange.com/questions/118654/how-to-interpret-bip21-uri-with-amount-specified-twice/) but I figured that maybe it's worth a PR. If not, I'll close the PR.
ACKs for top commit:
MarcoFalke:
lgtm ACK f1d807e383942ae20e080174d33ac17afd649351
kevkevinpal:
ACK [f1d807e](https://github.com/bitcoin/bitcoin/pull/27928/commits/f1d807e383942ae20e080174d33ac17afd649351)
Tree-SHA512: d287809d47c5cfc667f850927bfd969bd345a996d3d53a4c26ef0ffd29eb75ef53358692a15f9a0493ec9e1c101123b6584572e25f87bcb98ff67f6b6c166de4
Diffstat (limited to 'src/rpc/client.cpp')
0 files changed, 0 insertions, 0 deletions