That’s exactly what OHTTP lets you do. Clients can bake in that they only connect to relays over OHTTP and relays can be unreachable without it. And it doesn’t take 30s to start like Tor.
It is a requirement since WebSocket is not really HTTP, but a hack that breaks out of HTTP to keep a TCP socket open. WebTransport lets you do the same kind of streaming split into genuine HTTP packets.
Yes WebTransport is how you stream data inside HTTP
OHTTP uses pre-defined routes and doesn’t have its own separate consensus mechanism so it’s far far simpler than Tor
Everything Nostr is WebSockets now, tunneling is a bit more complex/slow, WebTransport is relatively new and not super widely supported
If nostr used WebTransport instead of WebSockets traffic could tunnel through an Oblivious HTTP relay since it could be wrapped in HTTP/3. Then your IP could be protected. nostr:note1a34x06rtygqzng3atkjcygpxdw3vtf3m0qr3hythe9r06n76qe4s5p0xea
In case people were curious about SNICKER but it wasn't easily discoverable:
https://gist.github.com/AdamISZ/2c13fb5819bd469ca318156e2cf25d79
Was this BIP ever part of a PR in the github.com/bitcoin/bips repo? Probably would be assigned a number in no time if it were today
Interesting perspective. I’d say she, as many do, mistakes merit for elitism.
“El Salvador offers a worked example of what it might look like to roll out Right-wing progressivism in a previously dysfunctional polity.”
https://unherd.com/2024/04/the-future-belongs-to-right-wing-progressives/
The title & cover triggered some lefty friends who couldn’t cool down before reading but I found it insightful.
oh wait *paying a person*, (not “in person”) makes all the sense in the world
Release time!
In our biggest update yet, we've completely redesigned the home screen, added a nostr-based profile setup walkthrough, and have finished our initial fedimint integrations by adding a federation discovery & recommendations!
Most lightning wallets these days are what we call "invoice-oriented." We want to go back to the basics to solve what people are really trying to do: paying a person. We've added a new wallet creation flow to make the wallet about you!
The new version of Mutiny now allows you to create a new nostr profile, or import a nostr private key from an existing profile. From there, you can now DM other mutiny & nostr users to send or request money directly from the app. No more copy / pasting invoices!
To double down on social, we've redesigned our home screen to put people first. We now include a row of recent profiles for quick access. We also now have tabs on the home screen for looking at your payment activity, your friend's zap activity on nostr, and your payment requests.
Next up, better fedimint support!
Mutiny has had beta support for the fedimint protocol for a couple of months now. Instead of opening a lightning channel on your first receive, with a minimum of 100k sats, you can get started on a fedimint with just a few sats.
This new update adds a way to discover available fedimints to join. Naturally, the discovery process is powered by an open protocol built on nostr. You can see who recommends a federation, and add it with one click.
You'll automatically receive funds to that fedimint, as long as the amount is smaller than 200,000 sats, and you'll automatically spend out of that fedimint, with a fallback to your regular lightning balance. You can also swap from fedimint to your lightning balance at any time.
Coming up shortly after this release, we'll be adding federated lightning addresses that lock incoming payments to your key, which you may redeem at any point by coming back online. We'll be rolling this out to Mutiny+ users first, stay tuned!
Let us know what you think! We're excited about this new direction and need feedback to help us continue driving forward.
https://blog.mutinywallet.com/mutiny-new-design-people-oriented/
Congrats on the release
🚅 nothing stops this train
I am surprised most Mutiny users are trying to make payments in person
Still in the idea stage
I just posted Payjoin-in-Potentiam to fund LSPs to open channels on your behalf in one atomic transaction. This is an optimization of Swap-in-Potentiam that posts only half of the bytes to the blockchain to achieve the same outcome.
Check it out on Delving Bitcoin:
Have you ever spoken with small business owners? Most I know complain about CC fees. Especially those whose customers used to pay by check.
A new version could replace WebSocket with WebTransport which is an http protocol and not just a hack
I’m super interested in this topic. But the audio from Alex is borderline unlistenable :/
I’m not sure of any UI that yet enables this fine grained queueing and batching you’re describing but it’s certainly possible. sender would propose their batch, receiver would respond with theirs, combined and signed, and the sender would take a final sign off if all looks good. Should be the same flow you’re used to for any other tx in terms of signing, but both would set up queues or batches in their respective wallets beforehand to consolidate or otherwise batch funds beforehand. nostr:npub1yashrajtj3ddn9u2ypzalp4qew4f9u8wls0tpf5kuvqarenqwckql8adnu might have some design input
Payjoin is coordinated by end to end encrypted messages transmitted over the internet between sender and receiver. The protocol is specified in BIP 78 and BIP 77. Neither sparrow nor Mutiny support receiving payjoin yet (but stay tuned)
Payjoin enables exactly what you’ve described, multiple inputs and outputs from each user may be batched into a single transaction. Input selection depends on the wallet implementation but is not limited by the payjoin protocol itself. What selection do you have in mind?