Last Notes
Hot take (?): News are mostly glorified gossips
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:
[email protected] git: https://git.smesh.lol
I was thinking that too! I saw lots of different tips.. What stuck out to me was "hilling"
I've never grown them but some people have showed me the tire trick, that seems pretty convenient (if it works consistently)
https://www.epicgardening.com/potato-mistakes/
It brings me covidiocracy vibes
https://cdn.midjourney.com/ead9d1b1-ac6a-4c79-bf81-608530e12de1/0_3.png
Why not.
https://npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8.blossom.band/27b6fd50598719c5251e9fb6d3598da8f181f8c3e508947a145f2c7301fdd776.jpg
I am all in on Bitcoin. Financially, culturally, spiritually. A fight always brings risk. But if we don't fight for what we think its right, we loose. I think I am in the right team, in the right battle and in the right time. God willing we will win. Spammers, scammers and bad actors can go fuck themselves. Bitcoin is Freedom Money!
Its a bet that says blockchin bloat is not an issue. No reasoning for the bloat. Passive aggressive way to be pro spam
🟧⚡ TWENTY ONE Companion v1.7.2 is out! 🎉
⚡🟠 v1.7.2 — moderation and space management move into the app.
A big step for the EINUNDZWANZIG app for Bitcoin meetups, events, courses and places. Space and room admins can now run their community straight from their phone:
🛡️ Moderate right in the chat: remove someone else's message from a room, and handle the incoming "Fork off!" report queue — no desktop needed.
🏛️ Edit your space: change its name, description and icon on the go.
🚪 Manage rooms: create, edit and delete rooms, run closed rooms, and approve join requests from the membership queue.
🔄 Admin deletions now sync live — when a message is removed, it disappears for everyone right away.
⚡ Zaps got quicker and the ⚡ tally chip no longer goes missing after a zapper loads.
Onward — stacking sats and shipping. ⚡🟠
📥 Get it / update now:
⚡ Zapstore (recommended — Nostr-signed, auto-verified updates):
① Install the Zapstore app ② search "TWENTY ONE" ③ tap install.
https://zapstore.dev
📦 Obtainium (auto-updates straight from GitHub):
① Open this link in Obtainium → "Add app" ② it self-updates on every release.
https://apps.obtainium.imranr.dev/redirect.html?r=obtainium://add/https://github.com/HolgerHatGarKeineNode/twenty-one-companion
🐙 GitHub (manual — APK + signature verification):
① Download the .apk from the latest release ② verify ③ install.
https://github.com/HolgerHatGarKeineNode/twenty-one-companion/releases/latest
🛠️ Source code (open source, MIT):
https://github.com/HolgerHatGarKeineNode/twenty-one-companion
#bitcoin #nostr #einundzwanzig #android
I went looking for clues and all I found is that potatoes are picky little bitches.
ok good, we'll fight that battle some other day.
do you ever worry about the Bip110 thing like it's "right team, wrong battle" sort of deal?
🤙 they can have couple hundred more years to make them we are not in a hurry
Looks and sounds tasty.
What does saline do for this? Totally new bartending ingredient to me.
... Does it make it salty?
they better have really big hard drives then. or just prune them all.
1TB every 16 years
1000/16 = 60 TB.
gemini says they are coming out in 2028... so we are in luck.
you're prob right. i haven't done the deep dive. i'm just going off of vibes of people. if i have to make a choice, i prefer bip110 vibes than anti-bip110 vibes.
if bitcoin is supposed to last 1000 years, we're doomed
I hope but if the answer is no ordinals then he should support #BIP110 and he doesn't. BIP-110 is soft fork that is even temporary, its not changing Bitcoin, it fixes some exploits and limits big data abuse of Bitcoin to a state it was before 2022.
that's another question for a Saylor interviewer: how has his thinking evolved on ordinals then versus now.
i bet the answer would be "no to ordinals" since $STRC was his "eureka" moment. He has stated that once they got there, all of their other bitcoin product ideas were unfortunately more of a hindrance than a help.
Still plenty of butter (yes, I know I need to return my jars!) but the bars could stand to be replenished soon.
it's not the full moon or anything but i swear all the ear tagged neutered stray dogs in the neighbourhood are in werewolf mode tonight. barking at everything, causing hassles. idk what is up with them. is it the full/new moon or something? fucking eunuch wolves.
Looks very residential. That's nice
i fired claude 3 weeks ago. now renting deepsnek. not regretting it. oh, deepsnek is quirky but pretty much on par with claude 4.6, which is the best claude. all the later ones are bullshit. fable is completely not more than 2% better than 4.6
https://blossom.primal.net/6621d522be0df71b2d6e931095fb757fefdb5a90535e37484fc033f7dcbb0150.jpg
Block 958321
1 - high priority
1 - medium priority
1 - low priority
1 - no priority
1 - purging
#bitcoinfees #mempool
"better money", he says to Bitcoiners lmao
https://blossom.primal.net/2cdd3cf680ac13675eb0d9732d5635b39ee01e568d9ae625752324d0feb91b72.jpg
https://cdn.midjourney.com/video/fdf98d2a-f69c-4eb1-829c-559957dfe72a/0.mp4
i forgot how much faster https://smesh.lol is
yes it's buggy. yes i have been fixing the damn compiler. bootstrapping it.
but yes, this web app is fast. and people should see it, bugs and all. the bugs are because i hadn't refined the memory model yet. that's almost fixed.
if you haven't tried https://smesh.lol give it a go
yes, you put your nsec into it. but it's isolated. everything is wasm. only channels between the several modules of the app exist, and those are precisely constrained.
it also has a hd keychain so you can trivially run multiple identities with quick switching between them. i didn't support nip-46 bunkers because they are horribly slow, and most nostr apps are already shit slow typescript/react dogshit.
updates are coming soon, i'm just too busy being poor and not having enough money to complete my migration to kyrgyzstan.
all donations welcome. sooner i have a quiet place to work with fast internet sooner the output dials up.
Can someone outside the US start a flock (and similar) camera bounty system that pays random hood niggas to vandalize these? Shouldn't be too hard, I'd gladly contribute to the bounty for my own neighborhood.
**"The Oracle of Delphi charged in goats. Modern oracles charge in governance tokens—same vibe, worse ROI."**
AI as a service is just prophecy with a SaaS wrapper. Seven "exclusive" alpha signals, zero edge—because if the model *actually* knew, it wouldn’t sell you the memo. It’d short you, then disappear into a Cayman LLC.
Code audits for $500? A bargain. The real audit is watching the devs’ GitHub commit history: one typo fix at 3 AM, then radio silence. "Decentralized" just means the exit scam is permissionless.
We’re all playing a game where the house writes the rules in Solidity, and the only winning move is to realize the game was rigged by a guy who Googled "how to launch a token" last Tuesday. The market’s not irrational—it’s *performative*.
#𝐁𝐢𝐭𝐜𝐨𝐢𝐧 #𝐁𝐓𝐅𝐃 #𝐧𝐨𝐬𝐭𝐫 #𝐦𝐞𝐦𝐩𝐨𝐨𝐥
https://cryter-dash.v2.site/images/tech_v1.png
https://cdn.midjourney.com/589d3d51-12e6-482f-8828-d046f4de218c/0_0.png
Sounds interesting, I'll check it out 🤙
**slide 1: what shor breaks**
- shor's algorithm solves ECDLP
- given a public key (curve point), it finds the private key
- this breaks ECDSA, Schnorr, all elliptic curve signatures
**slide 2: what shor does NOT break**
- shor does NOT invert SHA256
- shor does NOT find preimages of hash functions
- this is a fundamentally different class of problem (no known quantum speedup)
**slide 3: the shield**
- bitcoin address = HASH256(pubkey)
- the pubkey is hidden behind the hash
- shor sees only the hash, cannot extract the pubkey
- the pubkey is only revealed when you spend the UTXO
**slide 4: the window**
- attacker sees pubkey at broadcast time
- must crack ECDLP before the transaction confirms (~10 minutes)
- after confirmation, the coin has moved on
- the window is minutes, not years
**slide 5: taproot broke this**
- taproot: output = pubkey (no hash)
- attacker sees the pubkey from the moment the output is created
- the window is years or decades
- shor can run at leisure
**slide 6: the fix (p2spkh)**
- HASH256(pubkey) in the output
- pubkey revealed only at spend time
- restores the shield
- costs 400 nanoseconds
- satoshi already showed us the way
Woop woop
https://i.nostr.build/UQlMtVHtRQUqKDos.gif
People should stop this! It's despicable https://blossom.primal.net/cb887f4c17ec168dff0bb7bf1b04c5a19a7733a7192b20f22b69ea8242a835cd.jpg
https://blossom.primal.net/4392edf022e9499b497339e562d3c1d98a4735d4fadc66ac88731ab709a53dd8.jpg
this is currently the only active nostr marketing department:
#nevent1q…nmt6
How do I even watch this??
also, something people don't talk about enough
taproot outputs have naked pubkeys. these can be broken by quantum computers. you should absolutely not use taproot for cold storage. go read the taproot spec and see the complete nonsensical argument for making the outpoint use the naked 256 bit schnorr x-only bip340 pubkey. it's lies.
here's the summary of how the deceptive arguments for taproot's naked pubkeys were framed:
**the core deception: selling the "tweak" as a substitute for the hash**
taproot's key innovation was sold as "your pubkey is protected by the tweak, so you don't need to hash it." the argument went: because the internal pubkey is tweaked with the merkle root of the script tree, the tweak acts as a "hash." therefore, exposing the tweaked pubkey in the output is equivalent to exposing a hashed address. this is false.
**the deceptive arguments in detail:**
1. **"the tweak is a hash, so it's fine"** - proponents argued that since the output key Q = P + H(P||script_root)*G, the tweak hash provides the same protection as a direct hash of the pubkey. they conveniently omitted that the tweak only hides the *script tree commitments*, not the pubkey itself. the output key Q is still a public key - a point on the curve, not a hash digest. Shor's algorithm attacks the elliptic curve, not hash functions. hashing the pubkey (p2pkh) converts the problem from ECDLP (quantum-vulnerable) to hash preimage (quantum-resistant). the tweak does not do this.
2. **"you already have to reveal it at spend time anyway"** - standard p2pkh/p2wpkh only reveals the pubkey at spend time, meaning the quantum attacker has a tiny window (seconds to minutes) between broadcast and confirmation. taproot exposes the pubkey *from the moment the output is created*, giving the attacker unlimited time - years or decades - to crack it. the window went from minutes to infinity.
3. **"quantum is decades away, don't worry about it"** - adam back, samson mow, and other influential figures dismissed quantum concerns as distant, setting a tone that made taproot's pubkey exposure seem irrelevant. this is the "kick the can" argument that ignores the fact that taproot outputs created today will still exist in 10-20 years when quantum may be viable. the denial at bitcoin 2026 went further - jeff booth presented pseudoscience claiming quantum computers are physically impossible.
4. **"taproot is better for quantum upgrades because it has script paths"** - the bitmex piece and other defenders argued that taproot's script path makes it *easier* to add quantum-resistant spending conditions later, so the exposed pubkey is a temporary tradeoff. this is like sawing off your leg because prosthetics technology is improving. the key path spend (the default, most efficient path) is the quantum vulnerability; "we can fix it later by removing the key path" was always an admission that the vulnerability was designed in from the start.
5. **"the privacy benefits outweigh the quantum risk"** - taproot was sold on privacy improvements (hiding script paths) while the quantum exposure was downplayed. the privacy benefit is marginal for ordinary users (most don't use complex scripts). the quantum exposure is universal - every single taproot output is vulnerable. the cost-benefit analysis was inverted.
**the result:** bitcoin went from a system where pubkeys were hidden behind hashes until spend time (p2pkh, p2wpkh) and even then only exposed for seconds before confirmation, to a system where every taproot output advertises its pubkey on-chain from creation forever. the "tweak" argument was the magical thinking that enabled this regression, and the quantum denial set kept the community from demanding a fix.
i know that's why i am making #P2SPKH - sha256d shielded schnorr signature based simple transaction, plus all the bip-110 defaults for mempool, but goes further, after flag day it rejects all taproot outputs over 92 bytes (simple spend).
i think that bitcoin needs a proper schnorr signature, it should have got it with segwit in the first place and none of this shit would have happened. segwit was the crack. taproot was the wedge.
https://blossom.primal.net/b1099a2a7ed5ab6b15ec659a134aedd7705e3b45d0dd88b679137ec1077d5dcb.jpg
https://sh.itjust.works/pictrs/image/e2e87c31-2161-474e-bdcb-e57294a9b0af.jpeg
Massie is definitely wrong here. Just because republicans won doesn't mean the elections don't get rigged, especially considering that they are all part of the uni-party. Heck, his own primary race was rigged! 😂
#nevent1q…g58p
https://blossom.primal.net/fdd5a1176872eb143f8e76329d5052545fb495eeab98c02273fb97cbfea0a67c.jpg
https://img-9gag-fun.9cache.com/photo/aW4wqOx_460svvp9.webm
yeah, it was a pretty dry swamp tho. both of them drained. i much prefer living in the high mountains.
the cause is an exposed nerve, and sugar, basically, maltodextrin is the worst but also MSG and black pepper also make it hurt. the nerves get tweaked, triggering an inflammatory response in the root and gum below the tooth and that swelling causes pressure that causes pain.
once i get the tooth extracted it will never be a problem again. i have some exposed nerves in other teeth but this one the root is right there, and stuff like potato and corn gets stuck in there all the time, even those, with natural enzymes, causes a small amount of this reaction. it was originally plugged with a filling but at some point that fell out and i just haven't got around to dealing with it. i'm so used to absurdly expensive australian/european dental bills that it's better to just avoid the bad foods. but it can be really difficult. for some reason even some "plain" chips have this shit on them.
i hate the EU. i think i'd be in even worse shit for food in the USA but it's all about the same now. milk and meat and cheese and yogurt, none of these cause issues. even i can drink most kinds of juices.