- p2p non-custodial zaps
- When you don't have enough sats to zap someone that has a receiving wallet attached, you'll now pay directly to their attached wallet. We use lnproxy-like mechanism to do this which hides your node pubkey from the zapper (they see SN's node pubkey).
- I described this mechanism in Atomic Split Lightning Payments, Hold Invoices, and Blinded Paths
- Reminder: we have significant bounties on bugs/vulns for stuff like this
- lnbits receiving
- LNBits is our first attached wallet to support both sending and receiving, you can configure it to do one or both now (via @ek)
- sats filter
- we've replaced greeter mode with a more generic
sats filter
which allows you to filter out posts based on "investment"- that is, posts are only visible when a post's
sats zapped + post cost + boost >= sats filter
- that is, posts are only visible when a post's
- you can achieve the same effect as greeter mode by keeping your
sats filter = 0
- If you didn't previously have greeter mode enabled, we default your
sats filter = 10
- we've replaced greeter mode with a more generic
View all commits here: https://github.com/stackernews/stacker.news/commits/master/
(1) is the final difficult stage of our wallet plans. We have a few weeks worth of work left before those plans are done (mostly UX stuff). We'll pin a post about the schedule for wallets soon. No action is needed on your part to keep the sats in your account. When we transition, any sats in your account will be available for withdrawal forever.
FAQ
- What happens to the sats in my SN account when the wallet plans are done?
- Nothing. They will always be yours to withdrawal.
- I'm hard of reading. What will happen to my sats?
- Nothing. They will always be yours to withdrawal.
- Seriously, what will happen to my sats?
- Nothing. They will always be yours to withdrawal.
We'll have more complete FAQ in the pinned post that I'll write soon as mentioned before.
Since starting the Open Source Contributor Award Rules (OSCARs), we've paid a total of 8.5m sats to 26 contributors for 121 contributions! View an up to date list of contribution awards here: https://github.com/stackernews/stacker.news/blob/master/awards.csv
Previous release: #632357
even though it's not mentioned in the spec:phoenixd
with container namelnbits-phoenixd-phoenixd-1
, and for some reason SN is trying to access the local address when I press Save. It should use the Lnbits Create invoice POST api request... which I can confirm works just find with the Invoice key.curl -X POST https://lnbits.mydomain.tld/api/v1/payments -d '{"out": false, "amount": 1000, "memo":"testtest"}' -H "X-Api-Key: <my_invoice_key>" -H "Content-type: application/json"
lnbits.mydomain.tld
) but LNbits returned this error. Maybe it wasn't able to reach the container when it tried but it would work on retries?The container must have reachable as it is running next to the Lnbits container, and I tried the curl command literally a few secs later, successfully.
msat
is not a validunit
for LNBits, but instead of throwing an error, they just divideamount
by 100.undefined
somewhere we shouldn't have. If you disablewild west mode
, you'll be good until we deploy the fix.