Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate newaddress p2sh #5751

Merged
merged 4 commits into from
Jan 14, 2023

Conversation

rustyrussell
Copy link
Contributor

@rustyrussell rustyrussell commented Nov 30, 2022

This means we no longer hand out p2sh addresses (after two more releases). Hopefully we'll be handing out taproot by then!

Based on #5747.

@rustyrussell rustyrussell added this to the v23.02 milestone Nov 30, 2022
Copy link
Collaborator

@niftynei niftynei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going to clash with a very similar commit in #5670 but otherwise lgtm

@rustyrussell rustyrussell force-pushed the deprecate-p2sh branch 2 times, most recently from 39ff9e8 to f106b9d Compare January 4, 2023 03:32
@rustyrussell rustyrussell force-pushed the deprecate-p2sh branch 3 times, most recently from cd41fcb to 88d7af5 Compare January 12, 2023 06:03
…, use bech32.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
We used to create some p2sh-segwit addresses just to mix things up.  This
streamlines back to just bech32.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Deprecated: JSON-RPC: `newaddr`: `addresstype` `p2sh-segwit` (use default, or `bech32`).
@rustyrussell
Copy link
Contributor Author

Last DF test fixup due to number change (not using p2sh any more, so we have more sats!) and rebased to fix up rust gen files.

Copy link
Collaborator

@vincenzopalazzo vincenzopalazzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK c530b3d

Rerun the CI because looks like a little bit flacky in the last 2 days (from github side)

tests/test_invoices.py Show resolved Hide resolved
…stination

The close call can fail, since we already unilaterally closed since we mined blocks
too fast:

```
2023-01-14T01:00:10.2502199Z E           pyln.client.lightning.RpcError: RPC call failed: method: close, payload: ['107x1x1', None, 'bcrt1qeyyk6sl5pr49ycpqyckvmttus5ttj25pd0zpvg'], error: {'code': -32602, 'message': "Short channel ID not active: '107x1x1'"}
...
2023-01-14T01:00:10.5288050Z lightningd-4 2023-01-14T00:59:59.650Z UNUSUAL 0266e4598d1d3c415f572a8488830b60f7e744ed9235eb0b1ba93283b315c03518-chan#1: Peer permanent failure in CHANNELD_NORMAL: Fulfilled HTLC 0 SENT_REMOVE_COMMIT cltv 113 hit deadline
```

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
@rustyrussell
Copy link
Contributor Author

Ack 48661a3

Simple fix...

@rustyrussell rustyrussell merged commit 9d5841a into ElementsProject:master Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants