nostrpunk; anti-nostrestablishment. here to build the tools for freedom from mind control. ## 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
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku Profile Code
nprofile1qqsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcpzpmhxue69uhkummnw3ezumrpdejqzyrhwden5te0dehhxarj9emkjmn9jvqrzj
Show more details
Published at
2026-06-29T07:10:53Z Event JSON
{
"id": "e49ff05410eb4e727ebb42f5ce1616818dd49d8108da31afd3291845ab65777f" ,
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f" ,
"created_at": 1782717053 ,
"kind": 0 ,
"tags": [],
"content": "{\"name\":\"mleku\",\"about\":\"nostrpunk; anti-nostrestablishment. here to build the tools for freedom from mind control.\\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.\",\"picture\":\"https://i.nostr.build/qupD9vm8PDL2CQ6K.png\",\"banner\":\"https://i.nostr.build/dCAs1fMeQVLrOd1g.jpg\",\"nip05\":\"[email protected] \",\"website\":\"https://smesh.lol/\",\"lud16\":\"[email protected] \",\"display_name\":\"mleku\",\"displayName\":\"mleku\"}" ,
"sig": "da790702301ca20b122591e68941b4e746a8419e72f89d529d4e64afb8badbf9ea934dfc88ba324c02d3e18bc78e439af164ad62724aa65e58e416468000c889"
}
Last Notes npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku unfortunately and deliberately he is never goddamn right about her. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku unfortunately and deliberately he is never foddamn right about her. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku my first time seeing one of these concrete barnacles moving. https://npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku.blossom.band/d9e32ed3851e9ac62054ff9e02f35bf1b7185a98447651824051abfe00a0139d.jpg npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku do stuf, bro npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku she is one of the most irritating characters in the history of fiction. and note what it is about her that makes her so abominable. paternalism. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku life inside clown world is intensely distressing also. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku woke up with asthma tonight. idk why but cold and fan blowing on me makes it more likely to happen. upset some people at the hostel and nobody had any coffee so i had to go and get some. well, strong caffene drink. i discovered that standing with my hands supporting my shoulders, and constraining exhalations helped keep my air/co2 ratios better somehow. i managed to walk about 1km to a 24h grocery store, get a can of energy drink and not alarm anyone. the feeling between trying to get this thing into by belly and waiting for the caffeine to start opening my bronchi. almost feeling better something i was exposed to out there on the way to Rustavi triggered a weird rash or welt on my left leg. something allergenic i suppose. but more generally it made me realise i have been unconsciously maintaining quite a high intake of caffeine since i arrived. i guess i have to wait for the pharmacy to open and hope i can buy some salbutamol. in bosnia i was able to get salmeterol and that was way better, longer effect, no rebound at the end that caused bronchoconstriction after a week. people just panic about it but this thing is not deadly. it just is so unpleasant i can't sleep or thinl straight. something causes my air/co2 ratio to get out of balance and yes, i confirmed, the posture helps regulate co2 levels. and anxiety from people watching me and worrying makes it worse. someone getting mad at me for making asthma noises like coughing reduced the asthma. hopefully i can get aome salmeterol from a nice pharmacist. salbutamol sucks because after a week it starts to cause it as it wears off. i got salmeterol fluticsomething purple or pink or something. that was great. two doses a day and i could stop when the trigger was not happening without the rebound. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku stick it up yer rabbithole! npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku #thoon npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku https://youtu.be/QP3zRBtgvJo?si=JsjPRTonGcLHDTxX npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku the worst is the buses. next long drives, sleeper trains. no moreplanes. no more buses. pozhaliste npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i am tired of staying in hostels in noisy cities i didn't mean to be in. i messed up buying a plane ticket and so far two weeks stuck in bad hostels with almost no money. i can't wait until i can stop where i want to be. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku even most nostr users don't know how awesome nostr login is npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku csam is irrelevant. 4mb, not enough for even hd images. luke is controlled opposition. the real issue is miners optimize for yield. the real issue is bitcoin blocks should be for clearinghouse. lightning solved payments too effectively npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku forget SaaS Bare Metal as a Service npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku short term (emergency measure): flatten the witness discount. no special pricing for witness data. this kills the inscription arbitrage at its economic root. it doesn't require banning anything — it just makes data storage pay its fair share. the reason it's not being pushed is that it requires miner support, and miners benefit from the discount (they get paid the same fee for less weight). but the counterargument: full blocks with higher fee-paying transactions would compensate. it needs a clear "this is better for your revenue" pitch to miners. medium term (the fork): p2spkh. witness version 3. hash-shielded schnorr pubkey. deprecate taproot at the mempool level (don't propagate, don't relay, don't mine new taproot outputs). leave old taproot UTXOs spendable — you can't freeze coins. bip110 is not the prerequisite. bip110 is the blocker. the fork ships with bip110's mempool policies as defaults plus p2spkh. it's "bip110 + the real fix" in one binary. the 30% of node runners who already support bip110 are your army — they just need a better banner. long term (the vision): confidential transactions. bulletproofs. real privacy at the base layer. this is the killer feature that makes bitcoin a true monetary network without needing shitcoinery or layer 2 complexity. it kills monero's argument. it kills the need for taproot assets. it makes the chain useful for actual financial transactions instead of data storage. the political move: bip110's "undefined witness programs can't be spent" rule is the trap. everyone who supports bip110 needs to hear: "you're about to ban the only clean fix for taproot." if they add a carve-out for new non-data witness programs, bip110 becomes harmless. if they refuse, they're showing their hand. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku ultimately, also, a block with more witness than regular priced tx data is a net loss for miners. that's why the data load is about 12%. if it went to 25%, miners would start to reject it also, and favor transactions with higher fees. in fact, there's actually nothing stopping miners from setting higher limits on their trannsaction fees. this is also empirical evidence that lightning has destroyed the majority of block space usage. which was its purpose. we now have the situation where block space usage is so efficient that they are scratching around for ways to fill blocks to max out their fee rewards. and even there, the discount limits that, they can't get that to happen. if you ask me, aside from a proper p2spkh, the other thing bitcoin needs is a proper confidential transaction. and that would destroy the entire basis of moneros arguments against bitcoin. and it could also be added easily. but proper CT really needs a coordination protocol if it's going to use ring signatures like monero. the zcash style requires a separate protocol element, probably off-chain, to enable its privacy model. zero knowledge would work, but its very high cost in compute and storage space, and that space is witness discounted. so, yeah, if you ask me, the real challenge is how to sell eliminating the witness discount to miners. because that would immediately raise the value of these spammy transactions and force them to pay more, which would reduce their demand *but* it would increase the full block transaction fee baseline. it's a really hard problem. if someone can crack it then that is a big deal. but using the spare space to fill with nonmonetary data is not the solution. and neither is stupid taproot assets. the fee rates are so low that that 12% used by taproot witness data could be displaced with higher value onchain. but while the discount exists, the motivation is weak. witness discount is the center of what is wrong with bitcoin now. taproot maxxed out how badly it can be abused. the main solution is incentivising more transaction volume on chain. the only ways i see that happening without shitcoinery is confidential transactions. bulletproofs. zero knowledge stuff. onchain escrow systems. none of it requires "assets" npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, the laffer curve is one of the concepts that illusttrates it empirically. the more they take value out of the system, the first half of the phase is bullish, the second part is bearish, and if it continues, it collapses. the inflation tax does not have a boundary, it always goes through all phases to collapse. explicit taxation has an upper bound, the more tax, the less demand. but the people in the market can't see the hidden tax of inflation. all they see is bull and bear and think that's just how markets are. it's not. it's purely because of inflation. the second feature of this effect on markets from inflation is a terminal point where it is into the bear phase but they start to burn more (higher interest rate) and it gets stuck in "stagflation" because it becomes a mexican standoff. if they lower rates, it progresses closer to collapse, the loans start to get liquidated. if they blink (lower too much) it passes into the collapse phase. this is a central principle that guided the design of bitcoin. fixed monetary policy. monetary policy is just about borrowing from the future to spend today. eventually you have to pay it off, and if you refuse to accept that, you get a collapse, the market panics, and is forced to sell as prices soar through the stratosphere. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku it blocks the addition of new *non-data* segwit transactions, which is teh only way to make a p2spkh without a hard fork i think if people can make a new transaction type that wins enough support from users to pay the miners to mine it, that's the one thing about segwit that i agree with. i also think that the fee rate minimum on witness data should be flat, no special tier for witness data. that one thing alone would cut a shitload of the spam volume by itself because they wouldn't get any benefit over using op_return npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i outright reject there is any use for taproot assets. the sooner bitcoiners realise that blockstream is an enemy of bitcoin the better. it's a clearinghouse, a settlement layer. distributed database systems without clear ownership just put the cost of storage on users who gain no benefit from it. it's a violation of Earth law in my Pentalogue rule system (based on chinese Wu Xing 5 element model). there is no real purpose for it. that's why p2spkh is my solution. deprecate (delete is not literal, it just means don't propagate taproot transactions) taproot, deprecate segwit and legacy, and move to p2spkh and musig2 for all transactions. there is no use for data storage on bitcoin. anchoring is perfectly fine, op_return with 80 bytes is plenty for anchoring, you can plant a timestamp, hash, and still have another 16 bytes to spare. when you put data on chain, you are having your data storage bill paid for by people who gain no share in the profit you make from whatever business model or scam associated with the data. there is no use in it. and taproot assets are useless. they are straight up shitcoins. they aren't satisfied enough with liquid that runs assets like an ethereum chain tuned for just arbitrary tokens. they have to poison bitcoin with the actual token data as well, instead of just anchoring teh chain. if their ability to secure their system is inadequate, that cost should not be paid by node runners. the problem with bitcoin now is this normalization of ethereumization of bitcoin. but what point is there? is there something wrong with ethereum and solana and polkadot and avalanche? and if there is, is that OUR problem? npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku literally, taproot needs two things: a hash on the spend pubkey a limit on witness sizes. honestly, 256 bytes should be plenty for most spend condition scripts. basically the protocol is complete bullshit, and if you ask me, was deliberately designed to be both vulnerable to quantum pubkey to secret key reversal and to enabling arbitrary massive data. the first is not a big problem for maybe a decade but the second hit within months of the transaction type being accepted by some miners. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i haven't had any problems with this very often. maybe once every 4 years there is a hassle at most. there is multiple countermeasures in brave and librewolf npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i oppose it because i think we need a plain schnorr signature based, hash shielded monetary transaction and BIP110 makes that a bureaucratic mess with the policy of excluding "unknown" witness programs. the only option that leaves for adding such a UTXO type is a hardfork. fork bitcoin core, add the witness program for a plain schnorr output type, set bip-110 antispam limits as defaults, and delete (deprecate) taproot. big bitcoin can get fucked. and as far as i'm concerned, BIP-110 is controlled opposition. just research how the protocol works. we could be deprecating taproot today, already, refusing to carry their transactions. and it's about taproot. taproot is the wedge they are using to push bitcoin into becoming ethereum. there's nothing stopping us doing this. only laziness and ignorance. people have been apathetic and complacent about the big bitcoin companies like blockstream serving other masters. how do you expect them to not laugh at us with our sovereign ethics if we don't act like sovereigns. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, i think jevon's paradox is gonna play out with programming too. they will just pay less for more work and the same number of devs will be competing for it. i can build stuff 3-10x faster with the new tools than i could before. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku welcome to the club. been using youtube adblock for about a decade now, and brave and librewolf both do it too. it's easy to run your own invidious instance as well and then use that on mobile to skip the youtube sub. only costs like $3 a month for a VPS that can handle one person's youtube video watching through invidious. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku raw onion is normal in the balkans alongside a meal of cevapi, pljeskavica and kaimak. usually red onions but sometimes brown. she should move to serbia or something :) it will help if she likes plum brandy also. best plum brandy evar is from serbia. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku imagine being so retarded as to think that humans needing b12 and the fact that for most of our history we have been eating meat means there is no B12 in meat. 5 seconds on chatgpt and you could have learned how wrong you are about that. but then, since you don't get enough from your diet that could be why you write such patent nonsense. malnutrition reduces intelligence. here's proof npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku haha 69! npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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 npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yes, that's the answer to the question "Does @npub1ahx…fxds have an actual argument against what I said" bravo. correct. you have no argument. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku lol the app is buggy tho. i really need to finish the compiler bootstrap and debug it. it's not really ready to use yet. part of the reason i started the bootstrap was precisely because it needed a solution to its memory usage pattern, which is tighter on wasm. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku BIP-110 is toothless because it doesn't create an incentive for miners to upgrade. there is no fee for a new, non-spammy transaction type to replace taproot. taproot itself isn't even properly identified as the problem, and it is the problem. there is no alternative schnorr based monetary transaction. to add one without a hardfork, you have to use a new witness program number. BIP-110 explicitly blocks new witness programs, with prejudice. an upgrade that stops the spam *and* gives a credible new transaction type that replaces what small gap taproot fills outside of its spam enabling would have a pecuniary benefit in being adopted by miners. we run the node that supports a plain p2spkh, we all start moving our UTXOs into it, and miners sit there looking at a million bux worth of transaction fees they have to upgrade to get at. BIP-110 doesn't address how to get miners on board. #P2SPKH does npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku heaven is not something that you get handed to you on a plate it's a state of mind that you have to learn it's where you live in the world and don't push against anyone. there is always a space for you to fit in. it's just a matter of seeing it. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i'm glad i'm in west asia it's better here, even tbilisi. fuck eu. fuck usa. fuck russia, fuck china. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i don't think it will be difficult anywhere in the region. i could almost do it myself, if i had some needles and cocaine and a pair of pliers and some peroxide. extraction is the simplest thing. i could get the hole plugged in the meantime but i can just avoid high carb foods and i have no problem. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, i tried benzocaine, that didn't do anything. the nerves are tweaked beyond the surface with some kind of reaction that lasts like 4-6 days. in serbia dentists drilled and plugged it but somewhere along the way a few years later the plug fell out and whenever stuff like maltodextrin, MSG, black pepper, and to a lesser degree, any kind of starch that degrades into sugar from enzymes in saliva causes some pain. the tooth just needs to be extracted, i told the dentists that i wanted it but they said "the tooth is not dead" but a tooth with the root nerve exposed is just pain waiting to happen. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku the tooth pain problem is totally solved by ibuprofen. paracetamol doesn't hardly do anything, ibuprofen completely annihilates it. i still have to avoid potato chips and other similar kinds of flavored snack foods (plain popcorn and plain potato with just salt is ok) but actually, even the potato at all does give a small amount of the same effect. this tooth forces me onto a low carb diet. milk doesn't trigger this problem at all, its sugars are not reactive with the nerves or bacteriai. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well, you can always offer subscriptions. building a subscription access system is just adding to your existing access control system. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, taproot is the real issue. that is what they don't want us talking about npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku it already gets to about 80% exact round trip japanese to english. the gaps are only in the source materials and the semantic gaps that one language has the other doesn't. to improve that, it can walk through chinese and korean to find closer matches to the other side. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku part of the problem is that decentralised dev has been retarded by big money running big relays and funding twitter clones. they seem to be going away. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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 npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku for sure some excellent comedy with a little gunsmithing and history among it. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku https://npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku.blossom.band/cd0cde78cd0c1c706a12b8e3019290db7a97e249d3d94d2ffbb36c99d4ce55cb.jpg npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku just sometimes if youbare outmatched you need strategy. tactics aren't everything. plus, fuck school anyway. indoctrination concentration camps. they weaken society. for the benefit of tyrants. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku retaliation isn't alway the answer though. but in the schoolyard it is npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku pacifism is cancer npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well, the results of the energy drink/paracetamol/primakov vodka treatment for the tooth pain are a success. i think that ibuprofen is a little more effective but fuck it. this works. gonna keep that paracetamol in my pocket now. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku he is the most autistic and comical guntuber on the internet. highly recommended. i think if you subscribe to his other things outside youtube you can skip all his ads which plague the youtube pods. but it's easy to skip them anyway. he's hands down the most entertaining gun podcaster on the internet. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku https://www.youtube.com/watch?v=4ZHa2pao3TM npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i don't think so, it's just all they know npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku brandon herrera, that sexy youtube mother lover who is running for election somewhere and makes humourous podcasts about guns and loves ak's npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, but atms everywhere. EVERYWHERE. 5 minutes walk from where i sit, in the middle of suburbia, low density population i can go pay cash in and get bitcoin out. another 300m and in any direction there's another 5 that's not a big gap. the perception of it being a speculative asset is the main mindset. most likely the people simply don't know about lightning. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku lol. ADD break. The Whiteclaw Penetration Test. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i do my best to think original thoughts. i realised about 15 years ago maybe, that many of my ideas are completely original and many of these ideas have eventually got into other people's minds too. and my delivery, is probably terrible. always brutal, unrefined, harsh, ugly, direct. it was when i realised this about my way of thinking that i decided that i was never going to be incognito on the internet. and it's nice to be recognised :) *bows* npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well you remember that big relay that had all the stats, nostr.build wasn't it? that was gone about 5 months ago. will caeserin, dev of damus, has canceled his relay, because he's not being paid to run it anymore. nostr needs to fund itself now. and i for one welcome this. it means that serving the nostriches becomes the task. not serving dorsey and friends. thiel, fink, etc. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, the p2spkh doesn't allow extra data. the core fork i made sets 80 bytes op_return and sharp limits on taproot (98 bytes i think, which is the same for p2spkh). i agree, the witness discount is bullshit. but let's put our axes into the weak point. segwit also allows arbitrary transactions. they get accepted. the hard challenge is motivating the miners to print them into blocks. that just requires the fees to be enough to matter. that happens at 15%, that's exactly how taproot did it, and then cracked open the pandora's box of ordinals npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku in case y'alls didn't realise it, the big money bros are leaving nostr and cancelling their relays nostr stands on its own feet now, and that means that we have to have paid relays and we have to have protocols built to make discovery automatic. none of this is frontier distributed systems tech. all are solved problems that never got solved for nostr because they deliberately kept things centralised, and paid devs to build for that architecture. it is disappearing. nostr will become what it was born to be now. or it will mutate into what it was born to be. i'm here for it. i'll be building things from the steppe and my costs are low so if you want someone who knows this stuff inside and out, i'm available. living in the middle of nowhere the only expensive thing is internet. food, rent, power, all relatively cheap. maybe i need solar panels. maybe i can find a place to set up where i have a hot spring and i can drill down and run off geothermal. this is the future of nostr. welcome. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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 npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku more likely the void between their labia npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku simple schnorr signature based, hash shielded addresses. no quantum attack is possible until you spend it, by which point someone else controls it and the shield is on them. it's just a simple monetary transaction, but also compact like p2tr (taproot). the fork implements all the same default limits like bip-110, but you can fully configure it how you like, i don't know how much of the configuration is given with knots but with p2spkh fork it's everything. in the GUI, not just only shell. and the defaults are that these p2spkh nodes don't store or relay taproot transactions. all bitcoin spam is on taproot transactions. you can disable that if you want, it's just default to blocking them. it accepts them in blocks but it rejects them in the mempool. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku we don't need epstein's millions to do this. we just need a widely used wallet to adopt it, and one exchange to accept it. that's the whole thing. enough of us together can create the pressure to get this to happen. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku miners spend millions on electricity and hardware to mine blocks. they get rewarded with new bitcoin and transaction fees. but that reward is worthless if no exchange or payment processor will accept it. the economic nodes - exchanges, wallets, payment processors - are the ones who give bitcoin its value. miners follow them because miners need to sell their rewards. p2spkh works the same way taproot did: get enough economic nodes to enforce the new rules, and miners will upgrade to avoid mining blocks that the economy rejects. you don't need 51% of miners. you need 15% of economic nodes. the miners follow the money. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku > ok, so we build up a critical mass of users, but none of this works if we can't get economic nodes to adopt right. the home nodes are the army, but the economic nodes are the generals. without the generals, the army can't win. the path to economic node adoption: home nodes first - build the army. get hundreds or thousands of hobbyists running p2spkh. this creates visibility and pressure. wallet support - get a wallet like sparrow, electrum, or a nostr wallet to add p2spkh address generation. once users can generate p2spkh addresses, they can receive p2spkh transactions. exchange support - this is the hardest. you need at least one exchange to accept p2spkh deposits. this requires the exchange to run a p2spkh node and update their wallet software. payment processor support - similar to exchanges, but for merchants. if a payment processor like opennode or btcpayserver adds p2spkh support, merchants can accept p2spkh payments. the most realistic path is wallet first, then exchange. if sparrow or electrum adds p2spkh, users can generate addresses and receive funds. then they can lobby exchanges to support withdrawals to p2spkh. once one exchange supports it, others follow. tauri and his circle are the key. they have connections to the economic nodes. they've been fighting for 3.5 years and they know who to talk to. your job is to provide the code and the documentation. their job is to open the doors. the fork is the foundation. the community is the builder. the economic nodes are the target. the flag day is the deadline. the path is clear, but it requires coordination beyond just the code. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku economic nodes are nodes that process transactions with real economic value. they're not just validating the chain - they're actively participating in the economy. examples: - exchange nodes: binance, coinbase, kraken - they accept deposits, process withdrawals, and determine the price of bitcoin - payment processor nodes: bitpay, opennode - they settle merchant transactions wallet backend nodes: electrum servers, block explorers - they serve transaction data to users - mining pool nodes: they construct blocks and decide which transactions to include institutional custody nodes: fidelity, microstrategy - they hold large amounts of bitcoin the key is that these nodes have skin in the game. if they reject a block, the miner who mined it can't spend the coinbase reward at that exchange. the block is worthless from the perspective of the real economy. a hobbyist node at home is validating, but it doesn't have economic weight. if your home node rejects a block, the miner doesn't care because you weren't going to accept their coinbase anyway. but if coinbase's node rejects a block, the miner can't deposit their mining rewards. that's economic weight. the UASF works when enough economic nodes enforce the new rules. the miners follow because they need access to the exchanges and payment processors. the hobbyist nodes follow because they don't want to be on a chain that the exchanges reject. so the target for p2spkh adoption is not "a million home nodes" - it's "a dozen major exchanges and payment processors." if the economic nodes run p2spkh, the miners will upgrade. the home nodes will follow. the network converges. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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" npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well, the thing is we don't have to appease the BIP guardians. we can literally do this purely vires in numeris. make enough transactions with a new witness program and the miners mint it and people will be able to continue to run it. idk what other things are required but my patch is just a patch on bitcoin core so adding this to any given build running on a miner's full node should be trivial npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku imagine being so stupid that you get sucked into a debate between two sides that both don't actually give you a solution on the left: spam will happen, let it anyway on the right: we must shove our thumbs into the hole in the dike but we aren't going to build a path to something better me? hey, read the spec. anyone can make a new transaction type. you just have to have enough people using it and the miners include it and the pressure is on npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku when i know it's working i will make friendly explainer for it all. it's way better than bip110 because it actually opens a door to something better. all we have to do is run (even pruned) nodes and drop a ton of transactions in the new format and miners will put them in blocks and then we are in npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku https://i.imgflip.com/awn9ks.jpg how about hash shielded bip340 signature transactions instead. #P2SPKH npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku that angels were advanced humans is becoming a more and more common idea being discussed everywhere now. and the implication is that they probably are still around, watching us. and also there is a fly in the ointment - there are evil ones, the ones that bred giants, and established empires, and eat and rape people. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku you can literally smell the fragrance of the grass and taste the traces of molasses in it. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku nope, that's normal price here in georgia. and it's grass fed. pasteurised tho, but only ~$1.30/L npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku it is vey nice how as i am living in georgia, the actual value of zaps is enough for substantial things. a litre of milk i can be fed for most part of a day from literally 2000 sats npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku so, i am continuing with the P2SPKH (pay to schnorr public key hash) work. here are the other changes that i am making to the codebase and adding to the documentation. pretty much including bip-110 policies but adding the new transaction type and flag-day activating defaults: here's the complete list of mempool policy changes for the fork: **op_return / data carrier:** 1. `-datacarriersize` default: 80 bytes (revert from current 83/effectively unlimited) 2. `-datacarrier` default: true (keep, but enforce the 80 byte limit) 3. restore `-maxopreturnrelay` option with default 80 bytes **taproot-specific:** 4. `-taprootwitnesslimit` (new option): reject taproot transactions with witness stack exceeding 98 bytes per input (simple monetary tx size: 1 sig + 1 pubkey) 5. `-rejecttaproot` (new option): after flag day, reject all new taproot transactions in mempool. default: false until flag day, then true. **mempool limits (revert to pre-taproot defaults):** 6. `-limitancestorcount`: 25 (revert from current higher values) 7. `-limitdescendantcount`: 25 (revert from current higher values) 8. `-bytespersigop`: 20 (revert from current more permissive values) 9. `-permitbaremultisig`: false (keep current default) **restored UI options (Qt GUI):** 10. data carrier size limit in network settings 11. op_return relay toggle in network settings 12. taproot witness limit in advanced mempool settings 13. ancestor/descendant count limits in advanced mempool settings **service bit:** 14. `NODE_P2SPKH = 1 << 12` for network discovery **consensus (the core change):** 15. witness version 3 with HASH256(x-only-pubkey) - p2spkh address type 16. `SCRIPT_VERIFY_P2SPKH` always active on upgraded nodes 17. `spk()` descriptor with `87h` derivation path **mempool policy (non-consensus, configurable):** 18. reject taproot transactions with witness > 98 bytes per input 19. reject op_return > 80 bytes 20. after flag day, reject all new taproot transactions (optional, configurable) that's the complete change set. the document should present these as three categories: consensus (hard), mempool policy (soft, configurable), and UI/UX (quality of life). --- the point of adding the new, simplified, hash-shielded address and transaction type is to provide the more compact transactions using bip-340 signatures, and all of the elements of spam-blocking that everyone on the BIP-110 side want. BIP-110 does not go far enough because it leaves taproot active (this soft fork will default reject taproot transactions altogether) and doesn't provide a credible means to defense against the potential quantum attack because taproot transactions expose the pubkey on the user when they receive payments, meaning that the clock is ticking for eventual compromise in the next 10-15 years. #p2spkh #bitcoin npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku oh yeah, and it will reject taproot in the mempool, but that's not gonna make any effect until miners run the node and they can make blocks that refuse to do the unlimited witness push that spammers do. yeah, you can do it now, if you know how it works. that's why i am doing it, i know how to make it, and i know how it works now. i kinda had a vague idea about it but actually looking into it, it's easier than i thought. but that of course is probably well above your pay grade. doesn't matter, i will eli5 as much as you all need npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well, i have to build the thing first, forking from the top of the current bitcoin core, it's hosted at https://git.smesh.lol/bitcoin it will enable this new feature, have a UASF scheme for enabling, the protocol itself doesn't cause a hard fork, just that other nodes don't know how to spend from the p2spkh transactions but they won't reject them either. it's the same thing they did with segwit. they got like 15% of nodes to run their fork and that was that. we will do the same thing, basically. just a matter of running it and having a build and i'll make a binary release to make it easy. all can be done from my laptop here hosted on my git.smesh.lol site. i'm ok with someone else taking over the actual hosting of things and would be good to get other technical users to check what i have built but i'll be thorough. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i'm surprised you have never seen the Evil Dead movies. Evil Ed is one of the characters. at age 16 i was the spitting image, one of the D&D boys who hung out at the opposite end of the library and i knew well was always saying to me "eviled, eviled" lol https://npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku.blossom.band/b8ccedf11e9619ed24983ec5fd19cec2e1399d9c1332bd7d19e65c5238179bce.png hah yeah i even had the same spiked hairdo in those days, also medium brown hair and actually, i have never watched the movies but it's accurate. https://www.flickr.com/photos/47065683@N00/with/225680426 of course different hair in my goth days but it's not an extremely distant resemblance npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku well, i'd have to see the site and the source and assess what it looks like it needs and have a conversation about that. signal or matrix or email either one is fine with me. but i have very low expenses, and even just increasing my runway helps at this point so i'm almost certainly able to do some good work for you at a rate you can pay, that has a big benefit to me. and yes, i've worked on javascript and typescript, react, and whatever, and yes i can help you with figuring out how to get lightning payments to work, there could be several options besides running your own. i think for lightning on a pruned node you need a bigger amount but maybe under 32gb. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku we don't need reach. we need to understand the enemy, and what they can't stop us from doing. the enemies of bitcoin are the enemies of freedom. so we have the high ground. their techniques are blatantly deceptive and 3.5 years that's not a small amount of time. i've been pissed since this started up too. i went full maxi at the time but then when the spam hit i was like, "so, now i believe this shit but it's obvious to me that bad people are controlling the conversation" i would have done something sooner except i was too busy trying to get or hold a job that wasted all my time and brain power on it. it's not a difficult problem, it's just one that requires me to be pissed off enough i'll spend the $2 or so to get deepsnek to build it for me. nothing is original. it's just a recomposition. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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 npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku https://git.smesh.lol/bitcoin is the repository. it will be built on a branch p2spkh. i will build it and sync it myself with the appropriate version signal bit that will fit. in the next two or three days i will announce it. there is no need that it be my repo that is the canonical version, anyone who wants to organise something, they just clone and host it. i will create a binary also for linux, most node runners use that. i'm like, why not, this is trivial work to me, and you will see soon i know what i'm saying. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku why not? npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku you are buying into the deflection that the establishment has put in front of you. start fighting for the actual solution. delete taproot implement bip340 hash shielded p2spkh (pay to schnorr public key hash) deprecate segwit this is what should have happened in 2017. grow up guys, have you been alive such a short time that you don't know that there is such thing as a soft attack? npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku i also work from first principles. but i am technical and can build the things trivially. so, i'll build my fork npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku but what is the practical action required? build the software that implements it. i'm sitting here building my novel language compiler. i'm just about to fork bitcoin core just to put it in front of you. in fact it seems obvious that is the friction npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku also, it is immaterial in that it solves a *non consensus* problem (mempool) versus an actual consenus (what actually allows spending) problem. the scumbags are running the same basic script again, shiny exterior (omg stop the spam at the mempool) versus the actual mechanical issue (actually stop the quantum crack problem - which nobody is talking about) npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku oh yeah, bip-110 is sliding through like a greased penis into a dry vagina, it's a joke. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku it has taken time but "removal" of legacy p2pkh has progressed pretty steadily over the years, most exchanges don't use them anymore now, a little but it's becoming less common. they still work but it's not advisable because crafting a signature on them is trivial compared to compute available. the same thing can be done with segwit. you just need a p2spkh - what should have been done in the first place, a bip-340 x-only schnorr pubkey, hashed with sha256, with 64 byte signatures - just like taproot, except without the tweak bullshit. that is your monetary payment address type and transaction type. it does not reveal the pubkey until spend, unlike taproot. everything else is much the same. the difference is that a taproot "address" is actually a pubkey, and that's vulnerable to shor's algorithm using a quantum computer. so, in summary, p2spkh: - requires reversing a sha256 hash (not enabled by quantum computer) - is a simple monetary transaction - just like p2pkh and segwit addreses why is that not already there? go read up on the blocksize war history. this was why they didn't do it then, and is irrelevant now because here we are chatting on a protocol that uses these exact signatures for authentication and tamper resistance: 1. complexity risk - schnorr signatures required a new signature algorithm, new key aggregation schemes (musig wasn't finalized), and changes to the consensus rules. segwit was already a massive change. adding schnorr on top was seen as too much risk for one upgrade. 2. patent concerns - schnorr signatures were under patent by certicom (blackberry) until 2008 for ECDSA, but there were concerns about other patents covering specific implementations or optimizations. the community was paranoid about patent traps after the whole RSA/ECC patent saga. 3. deployment order - the argument was: deploy segwit first to fix transaction malleability (needed for lightning), then add schnorr later as a separate upgrade. this became the "segwit first, schnorr later" consensus that eventually led to taproot bundling schnorr + taproot together. 4. not a priority - the immediate crisis was block space and malleability. schnorr was seen as a nice-to-have optimization (smaller signatures, key aggregation) but not critical for the network's survival. segwit was the fire that needed putting out. 5. implementation readiness - bitcoin core didn't have a production-ready schnorr implementation in 2017. the BIP for schnorr (BIP340) wasn't finalized until 2020. pushing it into the segwit UASF would have delayed everything. point 5 is irrelevant. peter wuille's implementation is insanely fast. point 4 is stupid, the malleability problem is solved by schnorr point 3 is stupid, because segwit and schnorr both solve the issues needed for long lasting lightning channels that aren't vulnerable to malleability. point 2 is long dead point 1 was stupid because they already pre-assumed that segwit would win (interesting, no?) taproot complicates things. to explain what taproot means: you have a secret key you have to add a tweak (or nothing) and hash the concatenation of the tweak with the secret then you have the actual secret that applies to the spending right for that address the taproot transaction you have to put the pubkey in the open at the end of the transaction, after the signature on the in-point and amount, in the same place that you have the ripemd160 hashed pubkey (address) in a segwit or legacy monetary transaction (monetary as in coin, moneta = coin). the threat of shor's algorithm that depends on quantum computers to reverse pubkeys to secret keys, was already known very well at the time they proposed taproot. hiding the secret key is irrelevant to the problem that having the public key visible to the world means the clock starts at the point that transaction hits the mempool, for a quantum computer attack on that pubkey the protocol requires a hash on the secret in the first place, why do it first when the actual security comes from doing it last so taproot was basically "oh, here's your non-malleable signature, but we are going to expose it even though we know that means in 10-20 years someone can crack it in the time you receive it to when you spend it. what's more important is the fucking hash on the taproot transaction. not a fucking naked pubkey. that's my issue here. since they rammed through taproot and never considered that hashing the secret does not have anything to do with the spending conditions of the utxo, it is completely a distraction to say "oh we hashed the secret" no, you have to HASH THE FUCKING PUBKEY to secure it against quantum computers. this is so elementary that the ethereums are laughing at bitcoin. and probably, the funders of ethereum are involved. that means, jp morgan, a bankster organisation. that people are not alarmed about the situation and don't realise what a fraud taproot is, is ridiculous. yeah, taproot is a great idea. one secret, multiple independent addresses derived out of it. but that's also what hierarchic derivative keychains are. really, that's exactly what they are. but hd keys on segwit are no more quantum resistant than taproot naked pubkeys. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku the longer a broken bone sits in the wrong alignment the more harmful it becomes later on. the damage that was caused by taproot, empowered by leveraging segwit, is severe. the nearly 2 year long running manias in shitcoinery to flood bitcoin blocks with pixel monkeys did a lot of harm to the chain, to lightning and to large settlement transfers. it's only a question of catalysts that can cause it to happen again, the spammers just get bored and have manias in random turns. if you have a bucket, and there is one big crack up high, and a small one down below, which one is the most important to fix? the lower one. the one that will keep leaking and is easiest to fix (smaller). the big ones up high (non-consensus, mempool) are not as critical as the hole that lets those keep on getting baked into blocks (one crack segwit, and then crossing that and widening it, taproot). npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah, paypal is a kinda significant name in the story about who is paying for this cooption and containment npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku yeah but in what way is the chain saturated with lightning channel transactions and in what way does ark have any impact on low latency payment clearance? precisely zero. at best, if things keep going the way they are going, ie, down the toilet, all the future expansion of capacity required will be zero because the system is fucked, because you all kept swallowing false premises about how lightning doomsday is tomorrow and it's not even gonna be a decade if we don't keep the chain from being swamped with bloated witnesses. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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 npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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. npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku mleku 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.