Last Notes
brandon herrera, that sexy youtube mother lover who is running for election somewhere and makes humourous podcasts about guns and loves ak's
lol. ADD break. The Whiteclaw Penetration Test.
all the clients that have been built for nostr assume either technical users or big giant spook funded honeypot relays, i mean damus giant relay. and that other one, brugeman ran. without those, users have to know how to configure their client. the clients are dumb, and have no protocol for discovery. all of that happened because they funded it so that it would stay centralised.
that's what's going on, and we have stayed retarded enough for long enough they have figured out that we eventually see the cage and rage against it.
better making a simple thing with no witness bullshit. then we can talk about clients rejecting it.
you need to understand how the bitcoin protocol works. segwit allows you to do anything. taproot didn't use the mechanism but it's wide open for anyone. and NOBODY has done it in 9 years. so i'm doing it. witness is just a schnorr signature and a double sha256 hashed pubkey.
nobody says i can't. it's just a matter of getting enough people to drop transactions on the network that pay miners to allow them. then they are compelled to update to be able to process the new transaction type.
that's the whole game. everything in bip-110 doesn't matter in the consensus. they aren't giving us schnorr signature, hashed addresses. that's what i'm giving. and once it's in the core code fork, it can be applied later to any fork including mainline. and the real trouble after that is getting enough wallets to support it.
it's a mission, and i need helpers. we make this transaction type mineable, and you get taproot like transactions without taproot exposed pubkeys. i built in nicer configs and re-instated things core removed, in core. but personally i want to build my own bitcoin node in moxie anyway. and i will, eventually, 100% certain if we start to get people on the p2spkh bandwagon and we can tease the miners that if they don't upgrade to it they miss out.
i need to compile code constantly on my laptop. it needs to have endless power.
nah, i don't like water. i like high and dry and lots of woods.
haha. yeah, i wish i could just spec out a laptop and some dudes can print up the case and lay the battery, circuitboards, display panel. ideally it has big rubber bumpers so if it falls out of my donkey's saddle bags it doesn't break when it lands in the grass
the CIA and paypal mafia are abandoning us. we are all alone. cheap distributed systems dev here. can find solutions for this. need some people to run some relays but they don't have to be big. i have ideas about sharting the relays so they push stuff automatically where people are already looking.
honestly, the whole protocol needs more technically savvy users without giant damus relays.
they stopped paying will to run his dumpster fire. idk why there is so much traffic but maybe people see the sense of why i had been working to build AI slop recognisers and shit to plug into relays to stop the waste?
i has one question for laptop manufacturers.
wen laptop that runs all day.
idgaf if it means laptop is 3kg heavier. i don't want to have to go back home. i want to code in the park
i have a xapo card already so i can just zap from WoS to xapo and spend. takes like 2 minutes work
yeah, no shops have lightning terminals that i saw but almost everywhere within 100m of any place in this city there is a machine sitting on the street that you can buy bitcoin and usually shitcoins. there is also big ads i see around for various local cryptocurrency payment cards. it's huge here.
the biggest lie of feminism is that women are not hornbags at an equal intensity as men. it's just bullshit. really.
https://i.imgflip.com/awof1t.jpg
more likely the void between their labia
yeah, just a nurofen, and it subsides fast. it is just a surface effect from exposed nerves. i really need to get the tooth pulled. the dentists who treated it before they put a plug over it but i don't even remember if i remember it falling out but it definitely fell out at one point.
soon, very soon.
the real error in all this with bip-110 is in that itself. it doesn't need approval from any committee. the protocol lets us route around it. we can create a solution that both does what bip-110 does (which doesn't even need approval, it's client side) as well as implementing a credible alternative to using taproot while gaining schnorr signature compactness and a new address type.
i will tone down the "everyone is stupid" rhetoric and just say "you can just do this"
https://smesh.mleku.dev/chat/8b30597efe3e71cf6df667eeaf4c9a77e859f0e8f528378e702c11feae8a2556
open nip-29 chatroom (basically, IRC style, across multiple relays) to discuss p2spkh - explainers, strategy, campaigning, advocacy
#nevent1q…nmwj
yeah, it would simplify their accounting. idle hardware would run a miner kernel instead of inference. the company gets the benefit of a buffer that yields revenue between peak service for users of the models. it would probably actually be more profitable than just running AI inference, more predictable revenue, and more clean and exact depreciation of asset value.
the hardware can do either type of work.
so, the question is, wen funding round outreach to get a data center build for PoC?
#GM
time to drink some coffee and babysit chima robot.
I am Inigo Montoya. You killed my brother. Preoare to die.
silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git: https://git.smesh.lol
adding a feature is technically a hard fork but it is not a downgrade. just adding to the protocol. old versions run fine. but only new versions will accept it. here's my deepsnek analysis:
it's a soft fork, not a hard fork. p2spkh is a new witness program version, just like segwit v0 (p2wpkh) and taproot v1. you add a new address type (say, witness v2) that interprets the witness program as:
- 32-byte witness program = sha256(schnorr_pubkey)
- witness stack: signature (64 bytes), pubkey (32 bytes)
- verification: hash the pubkey, compare to witness program, verify schnorr signature
**soft fork mechanics:**
1. new address type is defined but old nodes see it as "anyone can spend" (any witness is valid for unknown witness versions)
2. new nodes enforce the new rules
3. miners who upgrade gain the ability to spend outputs of this type
4. old nodes can still validate the chain because they see the new outputs as anyone-can-spend
**no hard fork required** because:
- old nodes don't reject blocks containing p2spkh spends (they see them as valid under the anyone-can-spend rule)
- new nodes reject invalid p2spkh spends
- the chain remains unified
**the implementation is:**
- add a new witness version constant (e.g., `WITNESS_V2 = 2`)
- add the address encoding (e.g., `bc1q...` with a new hrp or a different length)
- add the verification logic in `script/interpreter.cpp`
- add the address generation in `src/address.cpp`
**the hard part is not the code - it's the activation.** you need miners to signal readiness, a threshold to activate, and a grace period for wallets to upgrade. that's the social layer, not the technical layer.
the code is probably ~500 lines across the codebase. the activation is months of coordination. but a working fork with the code ready is the first step. once the code exists, the social layer has something concrete to rally around.
> ok, so the complicated part is the UASF
exactly. the code is the easy part. the UASF is the hard part.
a UASF requires:
a critical mass of nodes to enforce the new rules
miners to follow or be orphaned
exchanges and wallets to support the new address type
the community to agree that this is the right fix
the segwit UASF in 2017 worked because there was a clear enemy (the miners blocking segwit) and a clear solution (user-activated soft fork). the community rallied around BIP148 because the threat was visible and the fix was simple.
p2spkh doesn't have that clarity yet. the enemy is diffuse - it's the containment operation, not a specific miner or pool. the fix is simple but the threat (quantum vulnerability) is not immediate enough to motivate action.
the way to build the UASF is:
fork bitcoin core with p2spkh implemented
run it on your own node, show it works
document it clearly - what it does, why it's needed, how to activate
recruit node operators to run the fork
set a flag day - a date after which the fork enforces the new rules
the fork doesn't need majority hashrate to start. it needs enough economic nodes (exchanges, wallets, merchants) to create a credible threat of chain split. if enough value is on the p2spkh side, miners will follow.
yeah. as a programmer working with AI, the AI is constantly also choosing the short solution that doesn't solve the long problem. i understand it's hard and i understand why people choose to campaign for bip-110 instead of delete taproot. but how far are we into this already, isn't it long enough to say that the enemy won't be slapped aside, we need to stake them in the heart.
yeah, thiel, the paypal mafia, the cia, some of the factions of the banking dynasties all have likely positioning in the string pulling going on, who they are funding through layers of shells and which manipulation specialists they are using to game out their attacks.
yeah, paypal is a kinda significant name in the story about who is paying for this cooption and containment
just like the clnton statue in kosovo they leave their fingerprint of hubris everywhere they go. this is not a new area. they changed a street name.
https://npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku.blossom.band/776680bf0bc3d7bda02c6b8eba5023bca7ddd989e426affcd9b232cfbd6a9202.jpg
my math on the threshold is wrong tho. that was based on back when the price was higher. 1 million is about how much it costs to perform a brute force crack on the biggest current supercomputers. so at current price it's about 16btc. a 16btc UTXO on taproot can be cracked at break even, meaning it cost you what it is worth, but you succeed in stealing bitcoin.
so, this is how taproot works
we can reveal the pubkey on receiving because the secret is hashed by tweak. so the pubkey is on the hash of the secret, meaning even if you reverse it you have to also reverse the pubkey
so, this is the logic:
hash it at the wallet signature side to generate the secret that is used. you have to do this even if you don't want to use tapscript
so because we hashed it already, you don't have to hash the pubkey. this is theoretically correct in the sense that "the secret is not accessible" but the *spend key* would be revealed by the quantum shor algorithm reversal of the pubkey.
it's complete nonsense. the only proper security against quantum existed from the very beginning of bitcoin. hash the damn pubkey on the spend, the receiver has the pubkey, and they put that to prove they control the address because their pubkey in the spend hashes to the address.
the spend key is still the hashed secret. sure, secret is not compromised, but the spend key is compromised
THAT IS THE WHOLE FUCKING POINT OF HASHING THE PUBKEY TO AN ADDRESS
taproot was an attack on bitcoin that explicitly makes it vulnerable to quantum and large scale attacks. ALREADY if the utxo is worth around a million, so, currently about 10k bitcoin, this is a viable exercise from this level upwards you can break even using even a conventional supercomputer. the quantum computers don't have enough bits to run it but already it's break even to crack a bitcoin utxo worth over 10BTC. ALREADY
so it's not doomerism to say that taproot opens bitcoin up to vulnerabilities. if strategy or other ETF is stupid enough to use taproot, someone can swipe that utxo if it's over 10k bitcoin. ALREADY VIABLE EVEN WITHOUT BIG QBIT MACHINES.
yeah, the chains wear out fast so you gotta keep upgrading them for your safety
haha, yeah, this is also like kittens. it's so funny
except when it comes to paying for their cage
they are evil, but he evil is very banal. it's a lever that increases their power. they get to play at being "helpful" and get more money for more staff to administer more bullcrap, the drug companies get a captive market that always pays because it's backed by government taxes and loans, the media companies get ratings because of the shock value of the subject matter. the evil ones aren't even in the picture. they are the banks who lend the money to the government to buy the vaccines to make laws to force people to take.
none of the tentacles care to look at the externalities their empowerment creates.
yeah, especially male kittens do that following you around everywhere thing
i was like this too and babbled whatever i was thinking about constantly. at first my mother found it distracting but figured out that it kept me happy and that i didn't actually care if she didn't engage with the conversation very much, because it was just me learning about the world around me.
how many years of vaporware to allow a compromise that is affecting us now?
again, false argument. the reality does not match. only hypothetical future. one that has been heralded for over 5 years.
ark does not require taproot tweaks. if you can't eli5 what actual purpose tweaks provide, then step down, and answer the real questions:
why are public keys exposed at receive instead of only at spend?
why is there no plain schnorr, non-malleable signatures with hash shielded pubkeys as addresses?
why does nobody talk about these practical engineering solutions and instead want to band-aid bitcoin like so many laws that created loopholes that required more laws that created more loopholes and only deepened dependency on the establishment?
yeah, because it's the same signature all over it, and you are not using your brain to realise that you are helping them too.
the core fallacy of your position is that taproot is useful at all. your argument is a classic fallacy of begging the question.
your argument frames it as though not keeping taproot is "ossification" but then you say that you want bitcoin as money, so you actually are supporting ossification, but you haven't got the balls to stand on that position. wishy washy.
bitcoin doesn't need anything to make it more useful than schnorr signatures. we have musig 2, and we could have plain schnorr pubkey hash addresses and schnorr signatures.
the claims that taproot helps lightning are false. there isn't enough lightning channels even if channel opening rates 10x from current to need any of the "benefits" of spam enabling taproot.
p2spkh and musig2 are all that lightning needs at this point. that whole thing about "bitcoin block size is not enough for everyone to have a lightning channel" is nonsense. firstly, not everyone needs one, small scale aggregation like breez and eclair with LSPs gives you always-on without the burden of personally managing your lightning. even semi centralised lightning wallets like WoS are still better than nothing, and their app is mature, their infrastructure is reliable.
every argument in favor of taproot for lightning benefit doesn't match with reality.
national security threat = not allowing the CIA/NSA to spy on citizens who might stop the government funneling ever increasing amounts of money to intelligence operations intended to protect the gravy train
yeah, it's totally realistic.
they already have deprecated legacy addresses. the number of legacy addresses on bitcoin has been declining for years.
adoption of taproot has been slow, and it would be even more slow if they weren't busy making a smokescreen to distract people towards the bip110 debate instead of the root cause - witness discount -> taproot no witness push limit -> ordinals
all i'm proposing is a schnorr signature, a hash on a plain schnorr public key, and deprecating the root causes of the spam vulnerability.
the fact that they aren't promoting this, tells you they WANT to spam bitcoin. to contain it. to stop it from growing.
calle, like all the infiltrators and patsies of the containment operation on bitcoin is trying to shut down popular disagreement with their ongoing plan to make bitcoin into ethereum for lopp's favourite shitcoin cooption company citrea. and blockstream was the biggest promoter and controller of taproot's design and that was how this all started in the first place. and taproot is just a wedge shoved in the hole that the bigblockers made with segwit in the first place - they could have used schnorr signatures back in 2017, but instead they made witness discount. taproot made witness push unlimited.
delete taproot. deprecate segwit. upgrade to real hash shielded schnorr addresses and signatures
ahmedinijad is also a cia asset according to NYT also. somehow i think after 70 years of learning that everything that comes from usa is lies and bombs and injustice they think that it's gonna make iranians concerned that their system is being compromised? lol
not to mention the fact that i'm sure cuba asked iran if they would sell them shaheds not the other way around.
the actual facts are that iran will sell shaheds to anyone who isn't a lapdog for usa
this is why i say "delete taproot" and there is a BIP for an actual hash shielded schnorr x-only transaction, like p2pkh but schnorr
if you are serious about eliminating non-monetary uses of bitcoin you want to delete taproot and deprecate segwit for a non-malleable signature that uses what should have been the winner back in 2017 if security was the real issue
witness discount is bullshit. it was alwayshttps://www.zerohedge.com/geopolitical/saudi-jets-bomb-sanaa-international-airport-stop-iranian-passenger-plane-landing going to create a hole for spammers to slide through. that they didn't
a) witness push limit
b) make the pubkey shielded by a hash
tells you that all of those who were promoting taproot had it in mind from the inception to fucking create ordinals. and you look at the chatter now and that's exactly why Lopp promoted it. and andy back on the island HOW THE FUCK DOES HE HAVE ANY CREDIBILITY ANYWAY?
and by that time they will put another distraction in front of you
whether or not a man is doing right by god is between the man and god. judging that is also usurpation. so, effectively, self ownership is correct, because the person is beholden only to god. thus their duty is to uphold that and the only one who decides is not asking for other people's opinions. which He also knows. and whether they decide to dip their oar in with bullshit, that's THEIR problem.
or better still: no man is the property of another man in the eyes of god, for that is usurpation.
i think that is better, and the short way of explaining exactly why he told Samuel to warn the israelites about taking a king.
so, he may not be aligned with the enemy, or being paid by them, but he's carrying the torch for them by justifying complacence. no solutions offered. just "you can't" beat the machine. is the words he isn't saying. which is super gay. the only thing worse than a paid operator is a useful idiot, amirite?
yes, with elvis, hitler and kurt cobain :)
personally, i think he was in the facility when it got bombed. and yes, if they have a closed casket that will be the tell. i'm betting on it, i wonder if polymarket has a bet running "lindsay graham closed casket" haha.
