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.

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.

# 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/

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.

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.

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.

# 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/

# 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/

# 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/

> 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.

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.

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.

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.

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

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

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.

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.

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.