withdraw

History

Padreug 2877cf6b20 Some checks failed lint.yml / Revert "fix: allow HTTP LNURL for RFC1918/loopback baseurls (#2)" (push) Failing after 0s Details Revert "fix: allow HTTP LNURL for RFC1918/loopback baseurls (#2 )" This reverts commit `66026ab`. Closes #2 as resolved by switching the dev LNbits to TLS (self-signed cert) instead of carving out plain HTTP for RFC1918 hosts. With HTTPS the producer-side python-lnurl validation accepts any host, AND the lnbits-core consumer-side `lnurlscan` accepts it too — the symmetric problem the carve-out couldn't solve on its own. `create_lnurl_from_baseurl` (#1, ``e9d911e``) is kept — it's orthogonal to the transport scheme and still wanted for the nostr-transport `lnurl=null` fix.	2026-06-01 21:44:57 +02:00
..
__init__.py	feat: add linters and ci (#28 )	2024-07-11 10:30:28 +02:00
test_init.py	feat: add linters and ci (#28 )	2024-07-11 10:30:28 +02:00

lint.yml / Revert "fix: allow HTTP LNURL for RFC1918/loopback baseurls (#2)" (push) Failing after 0s

Details

Revert "fix: allow HTTP LNURL for RFC1918/loopback baseurls (#2 )"

This reverts commit 66026ab.

Closes #2 as resolved by switching the dev LNbits to TLS
(self-signed cert) instead of carving out plain HTTP for
RFC1918 hosts. With HTTPS the producer-side python-lnurl
validation accepts any host, AND the lnbits-core consumer-side
`lnurlscan` accepts it too — the symmetric problem the carve-out
couldn't solve on its own.

`create_lnurl_from_baseurl` (#1, `e9d911e`) is kept — it's
orthogonal to the transport scheme and still wanted for the
nostr-transport `lnurl=null` fix.

2026-06-01 21:44:57 +02:00

__init__.py feat: add linters and ci (#28 ) 2024-07-11 10:30:28 +02:00

test_init.py feat: add linters and ci (#28 ) 2024-07-11 10:30:28 +02:00