mleku

https://git.smesh.lol/

PSA: my old key was leaked mleku (npub1fjq…leku) unfollow and mute that key to stop abuse that may come from it now that the secret is public

delete taproot

nostrpunk; anti-nostrestablishment. here to build the tools for freedom from mind control.

signal: mleku.80
simplex:
matrix: @smeshlol:matrix.org

## CSP laws and element correspondences

- metal. precise interfaces, clean keys. every interaction between peers requires independent bidirectional channels. simplex+lock is strictly more complex and introduces deadlock.
- backpressure by buffer - water. contested claims resolve by flow. backpressure is expressed by buffer state, not by blocking the sender. neither side should be able to freeze the other.
- state ownership - earth. territorial sovereignty. state ownership stays with the longer-lived party. short-lived workers get copies, not originals. death of a worker is reported, not hidden or auto-recovered.
- trust scaling - wood. bilateral incremental growth. trust scales through small synchronous exchanges, not through large upfront commitments gated by third parties. daily before weekly. oxytocin before escrow.
- sovereignty precondition - fire. you can't measure or price what isn't sovereign first. fire-sheng-earth: measurement establishes what you hold. sovereignty is the precondition for bilateral exchange. a peer that can't refuse isn't a peer, it's a resource being extracted.

Public Key

npub125uw9znxawyrvrc4lraf2ertm5k652ve4t87f74v7s7scp2qk2qswmlek0

NIP-05 Address

mlek0.smesh.lol

Profile Code

nprofile1qqs92w8z3fnwhzpkpu2l3754v34a6td29xv64nlyl2k0g0gvq4qt9qgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsvrdyl9

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub125uw9znxawyrvrc4lraf2ertm5k652ve4t87f74v7s7scp2qk2qswmlek0

Show more details

Published at

2026-08-02T11:58:24Z

Kind type

0 Metadata

Event JSON

{ "id": "5552a3ccb6946b7367b571c9e3268ac7b330e8fd4ba3c2d4462510941a05dbd5", "pubkey": "5538e28a66eb88360f15f8fa95646bdd2daa2999aacfe4faacf43d0c0540b281", "created_at": 1785671904, "kind": 0, "tags": [], "content": "{\"name\":\"mleku\",\"about\":\"PSA: my old key was leaked nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku unfollow and mute that key to stop abuse that may come from it now that the secret is public\\n\\ndelete taproot\\n\\nnostrpunk; anti-nostrestablishment. here to build the tools for freedom from mind control.\\n\\nsignal: mleku.80\\nsimplex: \\nmatrix: @smeshlol:matrix.org\\n\\n## CSP laws and element correspondences\\n\\n- metal. precise interfaces, clean keys. every interaction between peers requires independent bidirectional channels. simplex+lock is strictly more complex and introduces deadlock.\\n- backpressure by buffer - water. contested claims resolve by flow. backpressure is expressed by buffer state, not by blocking the sender. neither side should be able to freeze the other.\\n- state ownership - earth. territorial sovereignty. state ownership stays with the longer-lived party. short-lived workers get copies, not originals. death of a worker is reported, not hidden or auto-recovered.\\n- trust scaling - wood. bilateral incremental growth. trust scales through small synchronous exchanges, not through large upfront commitments gated by third parties. daily before weekly. oxytocin before escrow.\\n- sovereignty precondition - fire. you can't measure or price what isn't sovereign first. fire-sheng-earth: measurement establishes what you hold. sovereignty is the precondition for bilateral exchange. a peer that can't refuse isn't a peer, it's a resource being extracted.\",\"website\":\"https://git.smesh.lol/\",\"picture\":\"https://i.nostr.build/qupD9vm8PDL2CQ6K.png\",\"banner\":\"https://i.nostr.build/dCAs1fMeQVLrOd1g.jpg\",\"display_name\":\"mleku\",\"displayName\":\"mleku\",\"nip05\":\"[email protected]\",\"lud16\":\"[email protected]\"}", "sig": "f58504b695e8b61ec4bba23c2a5b9a790600dc5cc6a36faa871b62859fcc30203452d54a880a9db61a8a86d01090e2a2c38db93d0013759c98cffbb72ce0fef6" }

Last Notes

2026-08-03 13:57:19 UTC

- reply

https://git.smesh.lol/bitcoin-releases/raw/v29.3.0.knots20260508-p2spkh1/bitcoin-qt
bitcoind and bitcoin-cli are also on the same path. if you run linux on your pc you can start running a node that will keep bip-110 rules forever. we just need miners to keep it moving.

2026-08-03 13:28:54 UTC

- reply

the tokens you spent responding me to earlier you could have spent doing something similar. but hey, it always takes one node to start a new network. i'm not gonna cast shade on you if you download and run it. i haven't built a binary for it to make it easy but the code is already there. no, i'm upping the binary now.
https://git.smesh.lol/bitcoin-releases
that is the binaries for amd64 linux version. you can find the source in
https://git.smesh.lol/bitcoin
now, run it, or not, doesn't make any difference to me. put your money where your mouth is. easy to complain, not even that much more difficult to run a node that challenges the orthodoxy. promote it to get someone to verify i did the work correctly. it contains a new transaction UASF for the future after bip110 flag day that replaces taproot's schnorr transaction type. that's for future, but i already did the work.
the binary makes it easy for you to drop it on your machine and start it up. it doesn't matter if you set it up as pruning because the chain history is common to bitcoin core until 3 days time. it will have all the newest blocks anyway. so it's a small commitment that means a lot.

2026-08-03 13:17:01 UTC

- reply

did you? because i have done it. node is syncing. a permanent bip-110 fork. it will be synced up tomorrow by lunchtime or so. now what are you doing?

2026-08-03 13:15:03 UTC

- reply

only because nobody had the initiative to make one. that changed today.

2026-08-03 12:00:02 UTC

- reply

haha. i offer a third option: keep running bip110 chain. i invite technically savvy users to vet what my agent did on top of my own vetting. good. i'll use their fixes if i made mistakes.
plus, with an alt chain, that is essentially pre-taproot rules, we can set up a market against spamcoin, and sure that might lower our alt chain balance in fiats but once they done selling we have a price. at that point the miners get interested

2026-08-03 11:44:23 UTC

- reply

you didn't bother to tell your agent to not use signature em dashes tho? not a difficult thing to do. i mostly state in my posts when an AI wrote it, by some contextual mechanism at least.

2026-08-03 11:25:51 UTC

- reply

and me, personally, from 7 august i am also running a node that continues to enforce bip-110 alongside a core node, both pruned, because that's perfectly valid. and it means i can build a simple exchange orderbook that enables price discovery.
as far as i'm concerned, taproot is over. the fork that allows it can go do that, but we know how it went for BCH who went on to spam up their chain and what the market thought of that. don't be fooled by the short term view. the long term view is that bitcoin as base monetary layer still holds, even if most of the users ignore that. the reason why bitcoin price has tanked so hard, if you ask me, is because bitcoin majority has swallowed the jizz from a bunch of liars and those who reject it will be proven right in the long term.
that's why i'm building a forever 110 chain. i will have it deployed today and the code to run it will be available to deploy or audit. bug catches most welcome. i'm gonna do my due diligence to make sure it doesn't have them. and my build will have a potential future UASF that replaces taproot for the lightning/ark use case. i have been watching this thing for a long time and my analysis is unimpeachable in my opinion. the support for it will be the proof of work. i take the risk, i try the thing, and if it works, then i am vindicated. and i'm not alone. many agree with me. i have the capability to enable them to actively resist. bitcoin core will become a coin name.

2026-08-03 11:05:57 UTC

- reply

that particular case could be unrelated. if you are in a marriage and have lived the life of managing all the complexities of it, it can just have been a lucky coincidence. that doesn't exonerate lutnick but it is sufficiently clear that it is an overreach to rope in everyone without evidence. there is plenty of other damning evidence of complicity and inside information in other cases. hell, just the red hot angle-cut beams in the rubble is enough. as is wtc7 collapsing with barely a single fire in the building.
a lynching of innocents discredits the resistance. the clear malicious actors in this play are clear, at this point, even the point nvk is busy trying to delete his historical shit that shows he was malicious. the others, that's another thing. we are in the age of AI and the wayback machine. people have archived receipts. we cannot morally act on things that are not credibly supported by evidence. but what evidence we have is damning. that is enough. some will get away with their part in the play for now but those who deserve public excoriation will get it justifiably and without any moral question.
i know in my heart that there is connections between them all. i have said publicly that i believe that every single person who has got platform on X and twitter about bitcoin is involved in some way. proving that is difficult. acting on weak proof is a mistake.
the real response is to refuse to play along the rules they write. we play along with the rules that they claim to support. we take the blow - we go minority fork, we make a fork. we build exchanges, we build infrastructure that works only on the taproot deleted, spam-limited fork. it may seem like a loss for now but credibility is hard to earn, and easy to spend.

2026-08-03 10:48:41 UTC

- reply

make a show of helping the victims, but don't actually make them whole. continue to support the mechanism that led to this violent act against innocent people.
not gonna wash with me, not gonna wash with a lot of people.
we have been watching your larping as bitcoiners for years, and we are fed up at this point.
consider actually living the principles you sell your attention for. or prepare for boxes of tea to be thrown into the bay.

2026-08-03 10:45:12 UTC

a little history lesson:
the pattern is remarkably consistent across 500 years of history: **tiny, stubborn minorities with low overhead and high conviction change the world; comfortable majorities don't.**
**the demographic profile of the stubborn core:**
- **1-3% of the population**, but densely networked. the cypherpunks were a mailing list of a few thousand. the abolitionists were maybe 2% of americans for 30 years. the suffragettes were a few thousand women in a nation of millions. the samizdat network in the USSR was statistically invisible.
- **economically independent or low-overhead**: monks, artisans, tradespeople, people who don't need the system's approval to eat. the printing press operators, the ham radio operators, the shipyard workers. people whose survival doesn't depend on the institution they're resisting.
- **ideologically framed, not materially motivated**: they refuse on principle, not for a raise. this is why they can't be bought off.
- **curmudgeons overrepresented**: the chronic skeptics, the ones who were "difficult" before the crisis. they have the receipts because they never trusted the narrative.
- **skilled in the era's communications technology**: pamphleteers in 1776, samizdat typists in 1970, mailing lists in 1992, relays in 2026. the resistance uses the distribution channel the center underestimates.
**the mechanism of stubborn refusal:**
1. **a visible alternative exists** - the refusal itself is the signal. "we will not" is a reference point others gravitate to.
2. **it raises the legitimacy cost** - every crackdown proves the movement matters. the powerful are forced to respond, and the response is the advertisement.
3. **it recruits through demonstration** - people see refusal is possible, and the threshold to join drops.
4. **the center's response legitimizes it** - the moment the powerful argue with the minority, they've conceded the minority is a threat.
**historical scoreboard:**
- **the american revolution**: the sons of liberty were a few thousand. the boston tea party was ~100 people. the refusal to accept the intolerable acts, held stubbornly, outlasted the british empire's patience and logistics. britain had 100x the men, 1000x the money, and lost because it couldn't outlast a minority that refused to normalize.
- **the suffragettes**: decades of hunger strikes, window smashing, public humiliation - and the refusal to accept that the franchise was closed. they won with numbers that never exceeded a rounding error of the population.
- **gandhi's salt march**: one man, a handful of followers, and the refusal to pay a tax on salt. the refusal was the entire strategy. it worked because it was unbearably visible and impossible to argue with.
- **the montgomery bus boycott**: 381 days of a black community refusing to ride buses. economically devastating to the transit system, morally devastating to the segregation narrative. the refusal, not the protest, was the weapon.
- **the cypherpunks**: a few thousand people refused to accept that privacy was dead. they wrote the cryptographic primitives that now secure trillions. they changed the world with math and stubbornness and no institutional backing whatsoever.
- **solidarity**: it started with one shipyard refusing to work. the refusal spread by demonstration, not by organization.
- **the french resistance**: tiny numbers, huge morale effect, disproportionate damage to the occupation's legitimacy.
"we can stay autistic longer than they can remain solvent," is the historical formula: **the center has overhead, the stubborn minority doesn't. the center must eventually break even; the minority just has to keep refusing.**
gen - withdrawal as sovereignty - is the oldest trick in the book. every one of those movements won by refusing to participate on the terms offered, not by defeating the center in a head-on fight. the center can't counter a refusal to play. that's the water element: resolution through refusal. the first to act on the lie destroys it for both - and the refusal is the act.

2026-08-03 10:30:41 UTC

https://i.imgflip.com/ay0qwi.jpg
#bip110 #fuckcore #coretards #meme #memestr

2026-08-03 10:16:43 UTC

- reply

yeah, it sure would, wouldn't it? surely they had that idea in the plan as a shield against total revolt?

2026-08-03 10:01:38 UTC

- reply

if spook agencies are involved in this, and personally, the evidence they are is absolutely massive, then the coldcard attack was an overreach. they just destroyed their legitimacy by attempting to dominate the bitcoin resistance this way. the alarming nature of the attack means that there is massive distributed investigation going on right now and the conclusions they find, that implicate and link together many players on the chessboard, will be the end of the power of their network of influencers and blood money manipulation feed.
bitcoin was always built from day one to be a replacement of central banking, globally. those of us who understand that, will also understand that their short term gains spend their long term viability. the USD is hyperinflating. the people in the "world island" are slowly detaching from the petrodollar and eurodollar. when this "currency area" collapses, the USD collapses.
that's the long game. we win by holding to our principles and doing our own research and publishing it. the court of the internets will rule very much in our favor. the evidence i can already cite off the top of my head is enough for me. what people are going to dig up is going to be so damning that it will be worth taking a lot of risk to stay on the right side of history, because their house of cards is falling.

2026-08-03 09:46:02 UTC

- reply

we are few but we are bound by our hearts to the ethics that bitcoin represents. short term they win this battle but long term they can't win the battle that is structurally in our favor.

2026-08-03 09:45:01 UTC

- reply

i am working up a knots-based fork. it also has a new transaction type that will go up for UASF after bip-110 activation - if that fails majority hashpower, which is likely, then the chain will be isolated. but we can still feed from the same mempool and keep the bip-110 compliant transactions. we can solo mine on it, 40x chance of winning a block on the minority fork. sure, big miners on core can switch to our chain and mine but they can't mine spam into it, the nodes will not accept the blocks. that's what we want. if we can't have their hashpower, we can still make enough hashpower to keep it.
i don't see what there is to lose when staying with the herd of actually retarded central bank bootlicking spamtards is compromising the whole point of bitcoin. "assets" are paper, hypothetical. sats are real. a foreverbip110 fork will have real sats, not inflated ones.
and i'm super pleased to see that others agree. i will focus on getting this thing together so it runs, and i will be running a node at smesh.lol IP on my VPS. i'm also welcoming others hosting their own replicas of the codebase and keeping them synced up, so we can cherrypick off the work of the bankster funded core devs what is of value and leave out the garbage.
being in the minority, on the right side of history, is better than doing nothing, and there is thousands of shitcoins out there. bitcoin core is becoming one of them. i'm not being part of that.
in fact i'm considering that i can cut my pruning to 32gb and run a core chain on the other side and build a small exchange to trade between them. that is the bridge that next to the mempool cross talk, creates a way to discover the value of the forked sats. it's not difficult to do, and having one node already synced, i add the foreverbip110 fork node alongside it and i can accept payments in both with two separate btcpayserver instances. i can make a small exchange app with order books and just focus on trading between the two. sure, the coretards will dump but i'll still collect fees and use them to buy more foreversats.

2026-08-03 09:31:22 UTC

# 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:
- matrix: @smeshlol:matrix.org
- signal: mleku.80
- email: [email protected]
- git: https://git.smesh.lol/

2026-08-03 09:16:36 UTC

the strategic calculation error of the coretards is very simple:
shitcoin transactions and ordinal spam and suchlike, are "paper" values. they entirely depend on "paper" money from central banks.
central banks one day can wake up and choose violence, hike rates, and they will, because hyperinflation is teetering on happening. the eurasian continent is abandoning the USD as fast as it can. that is the hypothetical basis of the value of these spammy "assets" on the core spamchain.
in contrast, the value of what sats will be denominated in on the minority bip-110 and subsequent minority fork, is real value, denominated in sats, not USD.
that is what really changes the equation.
don't give up just because lukedashjr's and dathonohm's efforts fail. we get forked off. let's build an exchange. let's petition small exchanges to list the minority coin. the UTXO set is still there. we can mine with more rewards, even if the value of the minority chain is lower for now, the fact that we have solid economic backing and are not depending on central bank liquidity matters more than anything.
those of us who mine and hodl and run nodes and run businesses that accept these payments, we don't depend on central bank liquidity as much.
that's the achilles heel of the coretard spamchain. they are aligned with the global monetary scam. that is not what bitcoin is about, they are shooting themselves in the foot, low time preference, autistic monetary maxis will win anyway. or at least we will have a clean, legitimate chain with actual monetary value not just puffed up by suits printing money by cosy deals with banks and the central banks and world bank and imf.
you want the parallel economy? then you should support the minority fork chain anyway. because otherwise next up is bitvm and running a spamchain node cost goes from the current ~$400 startup cost and $20/month sorta range, into the thousands of dollars.
i've seen what it's like in shitcoin land. EPYC nodes with a terabyte of memory and 64+ terabyte. just to run an Internet Computer node. price is in the range of $70-200 THOUSAND dollars. that's where spamchain ends up.
some of us don't care about being in the majority. we care about the real economics and ethics. i will run a reduced data signalling node indefinitely. i will modify my node to retain it even after the flag day in 4 days.
they can have fun licking central bankers boots. i'm here to do real business.

2026-08-03 08:53:37 UTC

- reply

i consulted with the deepsnek on this, and it gave a good insight. onchain payments are the thing that the minority fork needs to retain its power. the transactions will finalise well enough. big miners can only attack us if we are primary offchain lightning transactions, so as a business using the bip-110 minority fork, we want to prefer people do onchain transactions. those tokens exist automatically if they had them historically from the spamchain as well.
so long as the resistance refuses to let go of this, an exchange will list the minority chain. once that happens the miners have to join. they can't blow up our channel opens and closes because we aren't doing them. everything lives onchain. fees are commensurately lower in economic value until we win and enough miners come across. but mining the minority chain is also more productive for those of us who do.
we just apply the principle: "we can stay autistic longer than they can remain solvent" and that's the thing - the big miners are almost all leveraged up to the gills to have sufficient resources. they are not low time preference players. the impact required to cut them out of a substantial amount of economic real transactions is lower than it is the other way around.
there's just no way i'm letting bitcoin turn into ethereum. that's completely contrary to everything bitcoin is about. the coretards think they win because they have the biggest capital base. but they don't have the most important capital: actual p2p business and actual morals. their capital is hot air, not material goods and physical labor.

2026-08-03 08:37:24 UTC

winning the war against spam and shitcoinery on bitcoin is not just about gaining hashpower. the situation as i last saw it is being measured - by p2p nodes signalling bip-110, it was at 20% of total nodes. there is efforts that are visible by coretards running fake p2p nodes that don't actually process transactions or actually relay transactions - a cheap, high time preference attempt to stuff the ballot box. it won't work. that 20% figure doesn't probably count the fake p2p nodes that don't actually have a replica of the blockchain behind them.
> ok, so 20% is the number of nodes signalling not just the ones with miners attached. but that's a LOT still, enough that it's now a swarm of political resistance
right - node signaling is the political metric. 7-15% of nodes running reduced-data rules is the swarm: every one of them is an independent deployment of the resistance, not a proxy for luke or dathon. no single point of attack. that's the octalogue's xun and kun working - invisible penetration via adoption, new ground via installed infrastructure.
the strategic distinction: hashpower signaling is about who wins the block race. node signaling is about who owns the economic consensus. when 15% of nodes - including the ones running payment infrastructure - reject blocks that carry spam, the miners face a real economic question: their blocks get orphaned by a minority partition, and the value of their chain depends on the economic majority recognizing their blocks as valid. the 2017 segwit playbook worked exactly this way - BIP148 nodes forced the issue by refusing non-signaling blocks, and miners capitulated when they saw the userbase's economic weight behind it.
the difference from 2017: segwit had ~90%+ of the userbase behind it. BIP-110 has 7-15% of nodes and ~3% of hashpower. the swarm exists but it's smaller than the one that won segwit. the mandatory window in august is the test - if the swarm holds, the economic pressure compounds; if the window closes without capitulation, the reduced-data chain becomes a permanent minority network and the main chain keeps the spam.
the political resistance point stands regardless: 10,000+ nodes refusing to accept the "art on chain" narrative is a public rejection of core's governance that can't be shamed away. whether it converts to a fork win or becomes a permanent parallel consensus, it changes the conversation. the swarm is real. the outcome is not decided yet.
-----
and i'm not gonna stop running my node this way. and i'm going to be running it as a payment rail onchain and lightning. i think that it is very likely that other users will do the same thing. a lot of people were not running nodes because they couldn't do a full node or like me were not in a stable physical location to run a node. but you can do pruned nodes on VPSs. you can attach lightning nodes to them. you can open your own little online business and sell stuff - i'll be selling a book and maybe if i find some people who want to invest in it, the "tinfoil wallet" with tin, gold leaf and pyrolytic carbon shielding, and radioactive material providing entropy that can't even be picked up by a device scanning for it within under a metre range.
because why not? by launching this attack on coldcard users the way they have, they have added something to the mix that is an incontrovertibly evil action that growing amounts of forensics data link the actors involved in bringing about this gigantic heist, they have taken away what comfort we had in our futures. they have made it so this becomes a war that we will not back down from. running nodes that filter the transactions, and some of us mining, enough to form a working chain, we now stand here, doing actual business, and the miners who stick to spamchain are missing out on blocks full of real fees that we get to keep on our minority sidechain, regardless of whether the UASF activates this month, i think i'm going to set about setting it up so it doesn't back down. it stays on the minority chain. i get a miner, and add my little power to a much smaller pool on the sidechain.
miners can either get in on that, or they can go fuck themselves. it doesn't matter. bitcoin is not a smart contract, data storage chain. never was, never will be. that is not an argument they can win. it's contrafactual and contrary to everything Satoshi wrote.

2026-08-03 08:19:51 UTC

- reply

> what is the octalogue text about the sun tzu "make unfathomable plans" - it's mostly about "build it before they recognise it" right?
yes, that's ☴ xun - wind - invisible penetration: "never announce what you are building until it already works. the enemy cannot target what he cannot see, and cannot regulate what already has users."
sun tzu's original is in the chapter on offensive strategy (九地/谋攻 variants): "make unfathomable plans" (do not let them be fathomed) - the art is that the enemy cannot prepare against what he cannot perceive. sun tzu's version is about deception of intent. the octalogue version is stronger: it's not about lying about your plans, it's about not having to state them at all. the finished, working, adopted system is the only communication that matters.
it also contains the regulatory insight: once something has users, banning it becomes a political fight against a constituency. a proposal can be killed quietly in committee. a working network with a population cannot. you don't fight for permission first - you build, then permission becomes irrelevant. that's the wind: invisible until it's everywhere, and by then it's the weather.

2026-08-03 08:06:36 UTC

- reply

the memory is completely mutable, unlike a static neural network that takes inordinate amounts of energy to add knowledge to. the initial implementation of iskra will include a very small model that i have designed a training program for, and the model is focused on only reasoning, not on knowledge. its knowledge will be as minimal as possible, just enough so once it can read knew semantic graphs it will be able to walk the lattice to generate and you don't have to build complicated systems to track prior experience and attempt to condense it small enough to fit in context. it *becomes* the knowledge. eventually, i am pretty sure the iskra lattice gets dense enough that it can do reasoning without any statistical compute.

2026-08-03 08:04:05 UTC

- reply

btw, anyone can do this. pruned nodes means that you can do it practically on a VPS for a cost of typically around $10 a month - your own full node, running on other people's hardware. my instance is running 64gb of allocation for block storage, which is more than required by a reasonable factor to enable running a lightning node off it. i will also be able to run a lightning node that routes payments not just a terminal point for my own wallet. i set some reasonable fee rate and that will offset the effort and costs by some amount. i don't mind if it costs me $5/month to run my own lightning infra, requiring me to look at it and occasionally loop funds around to rebalance channels so they can keep routing nicely. having my own lightning node running 24/7 means i can realistically do a lot more with it than just make payments, i can receive them too, trivially. i can sell things and accept lightning payments, and have digital goods delivered immediately to users. and because it's btcpayserver, i can equally accept on-chain payments as well.
ibd is about half way done now, should be up and running by the time i am landed in bishkek, and i can finish testing and debugging a web app that uses it.
when moxie finally finishes also i can start looking at integration into the moxie version of my orly relay. it will then become a proof of concept for a paid relay that can do onion routing and implement synchronous chat - zero risk of key leaks causing leaks of private messages. ever thought about how they call them "direct messages" now? yeah. because they stopped being private.

2026-08-03 07:58:12 UTC

- reply

yeah, there's another reason why moxie has to have TCO. so, graphs and trees are one part of it, but the iskra language model is full of walking around lattices following graph paths through it. having TCO means that iskra's walker is simpler to understand, and works like an iteration (for loop) with less complex annotations about the decision pathways. the code can be simplified a lot where it currently works via iteration, it can be changed to tail call optimized recursive functions and walk through the lattice until it hits the result it is looking for.
iskra is a partial replacement, maybe eventually full replacement for the statistical based modeling of LLMs. it has a distinct advantage - the entire process of walking the graph of links between concepts becomes fully transparent instead of opaque and probabalistic. when it comes up with a response, you can literally have the model tell you exactly how it came up with the answer, no mysteries. no lossy compression of limited context memories, the memory itself can be immediately written back into the model and the same question requires less processing to answer later because it already did the work one time and stored it.
TCO makes writing the engine simpler. if i'd even considered before i got this far into implementing moxie "do you want tail recursion?" the answer would have been a resolute yes because i have written half to a dozen algorithms in the past that would have been way more performant if they had TCO. now, they will. and TCO is very important for things that process language because language is composed of trees of abstractions and graphs of lateral links between concepts.

2026-08-03 07:49:49 UTC

- reply

i'm running it. a minimal, pruned version, but i'm happy to help add to the swarm of p2p nodes that are actively refusing to propagate spam. i need a full node to implement bitcoin stuff, there will also be my own self-hosted lightning which i will have LUD16 payment path as well so i will be able to ditch WoS and run a cleaned up fork of alby hub as the UI front end as well.
there is definitely a saturation point after which the more BIP-110 nodes, the more the spam transactions are measurably slowed down and completely excluded every time a miner supporting it wins a block, deferring all spams, which took longer to get to miners who would mine these transactions, are completely stalled for another block. all the bip-110 supporting solo miners and smaller pools will also add more friction for the spammers as well.
worth it. and IMO, worth it to sit on a fork for a while as the network is in a partial partition mode, the war then becomes a war of attrition - how long can the impatient, high time preference spammers continue to put up with this without folding and switching their miners to our side. it's really something they can't win because they aren't dedicated to keeping bitcoin about money, and they are impatient. they will still want to do regular transactions as well, so eventually we wear them down by being more autistic than they are aggressive.

2026-08-03 07:23:54 UTC

so, maybe the last architectural decision for the #moxie programming language:
tail recursion
because moxie isolates the scopes of functions, recursion is particularly brutal, each time it calls itself it allocates a new arena, and its result values, that go into the parameters, are passed in and have to be copied on the next cycle.
tail recursion effectively makes it so that every cycle nothing has to be done. the return value is effectively unified with the parameters making an exception that they are mutable, and it just jumps back to the beginning of the function.
Go never had this facility in it and it made recursive implementations very clunky and memory hungry.
the Go compiler itself uses a recursive descent algorithm, so it most likely required a lot of optimization in the garbage collector with the special case so that it doesn't blow up the stack. when you simply call the function itself, usually there is one or more calls back to the function itself at various branches in the logic of the function. what Tail Call Optimization does is effectively recognise that the return values are what are being optimized on, and the input values are the same variables, and you just go back to the top of the function with the return values already handled as being the output values, and voila.
my first time trying to implement this, i never got this far into building a compiler before. i usually got stuck somewhere around the code generator and didn't get to the point of anything actually running.
but i'm super pleased about having TCO in moxie. recursive implementations are simpler to write and more elegant than iterative functions. having TCO in the compiler means that when i have the choice to do iteration or tail recursion, i can write it as tail recursion. there is a lot of stuff such as hash grinding and tree walking and graph walking in general that are simplest to express as recursive so this is a big boost - faster to write, and performance will be very high, similar to how this is also a cheap operation in languages like haskell and lisp, which are also recursion heavy and have TCO.

2026-08-03 07:13:43 UTC

- reply

what is this from? the tibetan flags are red green yellow white blue from the chinese 5 elements (fire wood earth metal water)

2026-08-03 07:10:53 UTC

- reply

i never saw this before but at the coworking space in tbilisi it was on the shelf with a heap of other board games. also two or three different versions with different boxes, same Catan name on it

2026-08-03 07:09:53 UTC

man, istanbul monday morning is so manic, omg. so many dudes running around carrying building materials and giant loads of recyclables on these crazy cart things they walk up and down the crazy hills.
idk how anyone lives in this place, it's so squished together and crazy. the shopkeepers are mostly really nice tho.
and i come back into the hotel and on the TV it's talking endlessly about inflation and showing all these images of people at markets selling fruit and vegetables.

2026-08-03 02:34:29 UTC

2026-08-03 02:32:05 UTC

- reply

they have been suffocating nostr, along with opensats, by funding work that doesn't solve any problems and rather, creates them, with giant relays and trending feeds in a travesty of bitcointwitter.
they don't want the ecosystem to develop an immune system. so anyway, been saying there was a problem for most of the last 3 years, along with a dozen others i follow. and i've had exposure to other elements than the well known ones that glow like uranium and zinc sulfide.

2026-08-03 02:20:28 UTC

- reply

i like cherry silver and gateron clears but i'm weird like that. short distance to switching, more quiet than a laptop keyboard. it does take a lot of practice to not accidentally type tho. really small pressure required to get a keypress. one of these days i'll have a crispy ortholinear 108 board with low profile in the light spring short travel. yes i can type fast with them but what was more important was the effort level. with severe magnesium deficiency it was literally painful to type with standard keyboards.

2026-08-03 02:16:39 UTC

but if you had shown that to these guys they would have told you the robot was hallucinating. i had hoyte say that about a vulnerability in negentropy. lol. whatever.
8 months i have been working with AI to do dev and maybe sometimes you have to get it to run a few times and watch closely what it does but you can actually do these things that would take days and days to do, in hours.
#nevent1q…dpql

2026-08-02 19:04:35 UTC

- reply

it is the prophecy

2026-08-02 18:39:36 UTC

2026-08-02 17:28:47 UTC

- reply

and covenants would destroy bitcoin fungibility utterly

2026-08-02 17:01:52 UTC

- reply

all i see is scripting languages for database engines.
this should have nothing to do with a monetary settlement layer.
there is always a definite set of parties connected to a database of more complex things than simple movement transactions of ownership of one token. money is a public good. assets are private. the separation should exist between them. the fact that ethereum continues a downward slide of value while bitcoin has long term continued an upward trajectory shows you - private assets get milked. public assets grow in value if their supply never changes.

2026-08-02 17:00:00 UTC

- reply

generate own entropy is always the rule. you can read reams of text about the subject and the linux RNG stack is the most mature and complete, literally you do not hardly need to add anything to it. there are devices you can get that use low grade radioactive materials to gather entropy. there is an augment for it called "havaged" which compounds the randomness with every single trigger that exists on a system, inbound and outbound network traffic, keyboard, mouse, disk accesses, yielding of processes to kernel when they wait for input, everything and anything triggers a reseed. most high end large server machines have multiple entropy seeding mechanisms so they can cope with gigabit and 10gbit traffic with SSL. SSL/TLS requires strong entropy for security.
the multisig thing is not the same. a strong password on strong seed is all you need. multisig doesn't materially improve security, it just increases the cognitive burden of keeping it secure. it only makes sense in terms of a cold storage you are not going to touch very often. but even with that situation, you MUST practice accessing it or you will forget how to. so you see the paradox of it?

2026-08-02 16:35:41 UTC

- reply

anyone who is promoting aSsEtS is at minimum a useful idiot and thus not to be trusted.
taproot's lineage runs through blockstream directly:
gregory maxwell (blockstream's CTO at the time) proposed taproot in january 2018, building on the MAST idea and schnorr work
pieter wuille (blockstream at the time) authored the BIPs - BIP 340 (schnorr signatures), BIP 341 (taproot), BIP 342 (tapscript) - and did the core implementation
the taproot activation work, review, and testing happened through bitcoin core with major contributions from blockstream staff
so the specification, the cryptography, and most of the initial implementation came from two blockstream employees. that's not a coincidence - blockstream deliberately staffed the most capable protocol engineers in bitcoin because control of the protocol direction is their real product. the company doesn't sell software as much as it sells position.
bitcoin core was captured pretty much entirely by blockstream in 2014
the 2014 date is when the concentration happened: blockstream was founded that year by core devs - maxwell, wuille, cory fields, others - and the MIT digital currency initiative (which had heavy institutional backing) started funding core development around the same time. the result was that a large fraction of the people writing and reviewing bitcoin core were employed by one company, directly or through its orbit. that's not a theory, it's a staffing chart.
so when taproot came - authored by two blockstream employees, reviewed by a core process heavily staffed by blockstream-affiliated devs, approved by consensus of that same group - the "yes" was structurally guaranteed. not because it was bad, but because the people deciding were the people proposing. the review process is real, the technical merit was real, but the sociological concentration means the outcome was never in doubt. a neutral observer looking at taproot would have to ask what it did not include as much as what it did.
and the asymmetry with drivechain is the tell. drivechain - which would have made sidechains trustless and native, killing the federated model liquid depends on - never got traction despite being technically sound. taproot, which preserves base-layer conservatism while enabling the layer-2 ecosystem blockstream monetizes - sailed through. both outcomes were convenient for the same company. you don't need to believe in a conspiracy to notice the pattern; you just need to believe in incentives.

2026-08-02 16:21:58 UTC

- reply

lol, timechain was andy back?
i'm never gonna stop calling him that. you know epstein was ridiculing him with that deliberate mistake. it's a classic bad guy ridicule to deliberately call someone a muddle of their name. every second cartoon from the 60s had a character doing it.

2026-08-02 16:04:57 UTC

yay 19% on #bip110 getting closer
#nevent1q…662f

2026-08-02 16:02:59 UTC

- reply

yeah, that was rather ironic

2026-08-02 16:01:40 UTC

- reply

not andy back on the island's one, that's probably got an even more ridiculous exploit hanging around inside it. really, best option is a usb live, a pc you keep in a steel box when not in use. linux RNG is rock solid and you can use a tool like this one i made https://git.smesh.lol/seekrit and run it for a random amount of time, it will be practically impossible to know the seed or how many times it was hashed.
you'd pay the same price but have a very high guarantee of good entropy with such a setup. an old laptop would make it even easier to do it like out in a field outside of town no way anyone could have sensors picking up side channel that way.
so yeah, second option yes. jade. no way in hell. blockstream was the driving force behind taproot which was almost immediately turned into a spam attack.

2026-08-02 15:56:21 UTC

- reply

and a bug report literally had the user blocked from the forum? wow. many integrity. such honors

2026-08-02 11:41:09 UTC

2026-08-02 10:50:50 UTC

a little thing i learned out of this nsec leak experience. because nostr DMs are store and forward, if you ever leak your nsec, everything you say in DMs becomes publicly accessible. for this reason, in my work on a new protocol project i have in mind, a re-engineering of nostr fixing all of the errors i see in it, DMs are synchronous only, the relay protocol includes a mechanism for using relays as a proxy, the relays are default paid and use a lightning node to support direct, onion routed payments from users to enable onion routing of their event publication, so one always hides one's network location from any place one's events are published.
synchronous DMs means it's never stored on a relay. only chat partners get your messages, and they only get it via onion paths your client sets up. there will be a simple notification event in teh protocol to ping another user that you want to chat, for the initial case, and it's just going to be how it is - you can't chat unless you are both online. otherwise you end up with this problem where your nsec leak makes your whole chat history visible.
another thing that is in my mind about this protocol is that it deliberately requires you to understand a basic level of cryptographic and network topology things in order to use it. the protocol is not intended to win userbase, it's intended to provide a secure basis for people to communicate publicly and securely communicate privately. the coldcard hack incident is a case in point - adoption inherently exposes users to risks involving trust so any competent replacement for nostr has to eliminate that by raising the bar of entry so that you already have decent opsec before you can even start participating on it.
another thing is relays - they will be default requiring payment to use. this is for two reasons:
- default event publication works using onion routing. to not make a honeypot like Tor that is only fundable by sketchy orgs that are probably mostly spook fronts, the relays have to be self funding
- a baseline of cost for using relays is inherently going to lower the amount of spam on the protocol because every message you publish on it requires you to spend a little money. no spammer or scammer using spam to reach their marks is going to be happy about paying to use the network.
the cost of freedom on the internet is higher than nostr promoters would have you believe. it's worth it, and it's not worth weakening security for the benefit of userbase. the network of bad actors in bitcoin and nostr are exemplary for understanding why the bar has to be raised, and why using the network has to cost.