10,073 sat/vB?!?

I’m counting on the ‘market’ to react and bitcoin devs to fix this..

If people want to play around with jpgs on the blockchain, whatever, but once it starts negatively affecting standard Bitcoin transactions, that’s enough..

well, my nsec is compromised, RIP

It pains me to say it after 3 years of building on it but I think lightning is ngmi, at least for non custodial pleb payments.

I think ark and liquid are fundamentally a more sound approach to L2 for end users.

If it REQUIRES the end user to run infrastructure, even if that is just a phone, it's going to be too janky to actually scale.

Not to mention that somehow lightning is already more ossified than L1...

If we continue down the custodian route people will get rugged or KYC d

I am ready for your hate, but this is my current take. Also would be happy to be proven wrong.

Now back to sshing into my node and working on chantools to recover a force closed channel utxo that lnd didn't report.

Totally easy for everyday users to solve if they run into this problem...

Can we build a Nostr-native onion routing for private events using DVMs?

Each onion hop is a GiftWrap using an Ephemeral event kind encrypted to the next onion DVM. The client assembles all hops and sends the private message to the first DVM via the user's main relay. That DVM decrypts the ephemeral event and sends it to the next DVM. The last DVM will send it to the user.

This minimizes the user's IP leakage to the set of trusted relays that user likes while sustaining the relay decentralization properties of NIP-65.

User's would never connect directly to the read relays of other users because they might not be trusted.

Since the relay knows your Nostr filters, it does know which pubkeys you are interested in (including your own key). Decoupling sending an event to a pubkey and filtering events for your pubkey in the same connection/IP is key to reducing the power that the relay has over you.

This would be akin to using several Tor sessions, a new session for every new message you send, while giving the Client the power to choose different "exit" nodes (DVMs) at each new message.

Am I crazy or is this actually better?

We’re launching something big tomorrow

Here is your hint: 🔗

Put your best guesses below 👇

Should also be noted SMS with or without RCS should still be considered a legacy communication method and only used where necessary.

Legacy calls and texts should be avoided as they're not secure and trust the carrier / network along with having weak security against other parties.

Our recommendation is still to get as many of your contacts as possible to use Signal or other non-carrier-based communication apps using the signal protocol/secure E2EE encryption. It is why we don't give the stock AOSP Messeging app much attention to encourage people away from using it.

First time been at the Gordon Ramsey burger restaurant! 🍔 really was delicious! Recommended 🤙

ross ulbricht is still in jail.

if he had used monero, he would be in freedom living a happy life

CORRUPT POLITICIANS TRYING TO BAN LIFE BOATS AS THE SHIP THEY BUILT CONTINUES TO SINK.