Yes, for the main net. The test net does not have hash power to be secure and what Lopp does is childish and less developed. Just because he don't gets it his way he try to destroy the sandbox for every one else....

Feels like I am speaking in an empty room. Anyone recommend a Nostr tutorial? Anyone even see this?

I still don't get why people still use email 😂

Oh you know, Just taking the family out for a ceremony at the church of satan. Nice little Sunday. Also: this article makes no mention of the 200 children he sodomised. The FBI article says he took kids out of school to “Mr. Gary’s house”. Imagine your 8 year old coming home from school with ghonohria. That happened because of this guy.

Lt. Col. Michael Aquino was in charge of the US Army’s psyop division, the Phoenix Program, and was implicated in multiple child molestation cases throughout the country. It is estimated that Aquino allegedly was involved in the sexual abuse of over 200 children. Aquino also spent most of his adult life forming a Satanist church called the “Temple of Set”, a version of Satanism that broke away from Anton LaVey’s Church of Satan.

If Elon Musk really unblocks the Brazilian accounts the emperor might ban Twitter in Brazil. Will this be the Nostr moment?

LMFAO FEW UNDERSTOOD THIS

Bare Multisig Outputs

-----------------------

Blocks are getting filled with bare multisig outputs and it's an obvious troll from people that hate Bitcoin. Let me explain.

Multisig currently can be done in many ways, but before p2sh (BIP0013), the only way to do multisig was through putting the many pubkeys on-chain. As ECDSA doesn't really let you aggregate keys, outputs had to specify something like "3-of-5 of these pubkeys." The normal UTXOs have the following number of bytes:

p2pkh:25

p2sh:23

p2wpkh:22

p2wsh:34

p2tr:34

By contrast the n in the k-of-n bare multisig determines the number of bytes and it's 5 + 34 * n (my math might be off, but around there). So for 3-of-5, it's upwards of 170 bytes. But that's using compressed keys. For uncompressed keys, you it's 5 + 66 * n or 335 bytes+, and worse, you can put in illegitimate uncompressed keys (keys that are provably have no private key) to add data to the chain

Why does this matter? Because these bytes stay in the UTXO set, which is what Bitcoin software optimizes for because that's how you validate that a transaction is a not double spend and satisfies the conditions of the smart contract that locked it.

What's worse, if the pubkeys are unspendable (uncompressed keys that are not real points on the secp256k1 curve), then they'll *never* be pruned. So the UTXO set grows larger and requires more resources for your typical node runner.

Interestingly, this was how the whitepaper was embedded into the Bitcoin blockchain by putting pieces of the whitepaper pdf in 64 byte chunks through uncompressed pubkeys. Luke's Eligius pool was one of the first to ban such transactions because they were clearly bloating not just the blockchain, but the UTXO set.

That's what these trolls are doing. They're adding to the UTXO set that's not easily prunable, though now, I'm guessing some people will add pruning for UTXOs with multisig outputs that don't have any legitimate keys.

This is a great question. Nostr isn't generally anonymous. Your IP can be logged whenever you communicate with a relay. So I assume as soon as someone starts putting drugs on nostr market, relays will begin getting subpoenas.

What are the ways around this? Use a throwaway nostr identity and route all of your questionably-legal nostr activity through Tor?

Maybe we will see no-log nostr relays pop up. You would still be trusting them though, and a relay could be run by law enforcement trying to catch you. So I don't really see any way except using Tor.

yeah, that's good but it also requires wot (since zaps are unverifiable) so pure pow is better for discovery (if you want to find people outside your wot)

unless you meant pay for pow, that's awesome and I fully support it

fuck this dystopia

my guess:

pow for discovery and wot for spam filtering

DC is not bigger blocks

It is an additional op code (OP_DRIVECHAIN), the block size stays the same.

Read the BIP