Losing security is what it gets if it gets drivechains.
Federated BFT protocols are a dime a dozen and don't require any changes to bitcoin for anchoring. None of them have been in any way practical for anything other than pumping bags. Have you not done any research into this subject? The history goes back to at least 2013 with the fork party that broke out on bitcointalk.
Which of those PoW forks still have any importance now, that aren't changing over to Piece of Sh*t scam "decentralization"??
Monero, and only because of the dark web.
People respect you for making Nostr but your expressed opinions about DCs are being abused by scammers to pump their racket. It's no more going to get into mainline than GreenPeace's Change The Code campaign, and for the same reasons. They are scams.
The cat is already out of the bag as far as damaging your credibility though.
Well, good luck with it. The problems you speak of have been solved, but the system that implements it isn't finished yet. I should spend more time working on it than reading and posting with nostr.
It's base58check I presume. 6 bits per character so, close to 448 (with 5 or so for the checksum) bytes in total, 64 if it's schnorr, 63-67 bytes if it's ECDSA, so 384 bytes of payload, probably. This is about equivalent to a pair of P2PKH transactions.
I see no difference, what am I missing? nostr:npub1jdvvva54m8nchh3t708pav99qk24x6rkx2sh0e7jthh0l8efzt7q9y7jlj nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424


top two and bottom two lines look the same on both, you only start to see differences in the body. They are probably redundant data if they appear in several different tokens.
I personally feel the whole thing is kinda sketch cos the tech is ancient, I mean literally 40 years old, and several attempts have been made to work with it and none of them stuck. Only Bitcoin finally solved the ecash problem.
I mean, signature and data... the signature is 64 bytes which is 103 characters.
928 character seems excessive for a blinded signature. Is it in Base32 or something?
IPFS isn't heavy. Neither is neutrino, and afaik it already runs the back end of at least a couple of wallet apps. Something about bananas? LND and Neutrino together.
If mobile devices weren't encumbered by proprietary firmwares and gated by app stores I'm sure that p2p apps on them would proliferate. Mesh networking standards are everywhere too, they just are hardly in use because someone doesn't want you to get off the grid where they are surveilling you and selling your dossier to the highest bidder.
He's a 10, but he uses hashtags
If it's after 40 time to stop with the sauce cos that's the main thing that angers the intestines. Also, anything made from, or fed on seeds, those not only angry the gut but for me at least give me nasty skin rash and asthma
When I get my little patch of dirt I'm getting a breeding pair of russian blues and should have got myself set up for catching fish from clean atlantic waters.. and I'll also raise rabbits, they are a favourite food, plus even ordinary rabbits make such nice fur trimmings for things, not that one needs such warmth often here but hey, gonna use it anyhow.
Well, kubo, the original Golang version, can easily be set up to run on a mobile device inside an app, as can anything you can compile to the target, arm64 platform.
So also can even a python based one like Electrum, or of course a Go SPV like Neutrino.
I can and have even deployed a pure Go based app that rendered to an EGL display, and it works on iOS also.
Everyone seems to think that Go is somehow in alignment with Google. No, actually, they just maintain this guilt by association because Go is what they build most of their infrastructure with. The GUI frameworks are a bit clunky, and so is the mobile stuff, but it all can be used, and does work.
P2P doesn't require a stable IP address nor does it require inbound routing, if the protocol has a rendezvous in it, and IPFS's back end, libp2p, has a rendezvous for exactly this.
It's more likely that nobody who has the inclination and the resources has actually looked into doing it. It's entirely possible.
I have even run a full node of a bitcoin fork inside LXC containers on Android, 5 years ago, so there is actually none of the limitations you believe exist.
Just use IPFS, then it's a separate network and good luck to them blocking it.
and Scissors beats Paper
This is an english/australian gesture that originates with the legend of Robin Hood. These are the two fingers you need to fire an arrow, and the significance of the gesture is that at one time there was a very draconian tax regime and the people who were caught fighting back had these fingers removed so they couldn't fire arrows.

I meant, if you are using an LNURL it's tied to a domain name and they know who to go to to find records. You are trusting them to not keep records, and they won't be able to tell you if they are if they have a national security letter telling them not to. You wouldn't believe how many crypto exchanges and related businesses get these things. They will be here on Nostr soon enough.
https://nostrcheck.me/media/public/nostrcheck.me_7480448978066498191694257007.webp
Don't forget your freedom gag.
You rat on yourself when you use an LNURL.
It's not for nothing the latin root of evil is the same as small.
Clients don't have to publish that they made the zap...
also, yes, cats need high protein, low fat. But a quality fat, that has plenty of cholesterol, saturated fats and stearates. Omega 3s like in egg yolk make their fur super pretty, so I figure probably fish is a really suitable food for them. Preferably whole, just gut the fish and slap it down and let nature take its course. Rodents also, same thing, just gut them and off they go. All the collagen in the skin is good for them too.

