A few thoughts about BIP-110
I have been vocal about spam for the past few years. I agree with the motivation and rationales mentioned in BIP-110. Disclaimer I'm not deep into inner workings of Bitcoin script and inner workings, so I misunderstood details in the effects of the proposal.
My biggest issue with it is its suggested urgency. Activation in September this year with barely a finished specification out is just too quick. I rejected CTV for the drama and urgency their supporters pushed too. Beside that and beside CTV being done by an asshole which directly contracted by Epstein - if we can be sure it does not have any unintended sideffects that enable more spam or attack vectors, I would be fine if there is majority and it gets activated in a few years (but there are other interesting proposals too).
Related to that is that the activation threshold was reduced from 95% to 55%. Again, seems rushed and desperate.
I agree that Bitcoin Core lifting OP_RETURN limit was completely reckless and against the community. To this day I did not hear a coherent reason (only whataboutism and whishful thinking) why the limit was lifted instead of just marginally increased to cover todays and future use cases. This brings me to another critique of BIP-110: It seems Cores fear of new use cases putting data in fake pubkeys would all be covered by a 160 byte limit. By limiting OP_RETURN back to 83 byte, now on consensus level, is imo a mistake. By acknowledging its use as garbage bin a compromise to 160 byte might would have won a few Core supporters to support the proposal acknowledging their damage mitigation theory.
Another big issue for me is that it breaks miniscript and wallets that may use OP_IF or OP_NOTIF and BitVM use cases. While I think that BitVM use cases may better be built on L2 I don't have the technical insight on why it may makes sense and is not a waste of blockspace. I don't think it's a good idea to break those use cases.
About the temporarity of the proposel. On the website bip110.org it says "A one-year deployment that can be refined or extended based on community feedback." dunno, but it does not sound that temporary like later then in the faq item where it says it will just deactivate and expire. I also don't see any proposal as what will follow. I year goes by fast and I doubt a more refined new proposal will be mature enough to get activated in time. Again bad consequences of rushing it.
Those are the main issues for me although I'm 100% aligned with the intention and motivation of this proposal. But I'm not sure this is the right way to get there, sorry.
I also find it silly and contraproductive that supporters of BIP-110 are suggesting everyone who does not support BIP-110 is not for the monetary use case but a shitcoiner. Well this backfires as I (and likely others don't like to get bullied and rushed into things). So gfy, for that.
As we are at emotional warefare already, I also don't think that ad hominems against Core devs or their supporters are apropriate. Yes I don't agree with many of them on that topic and I think some of them are actively harming Bitcoin (conciosly or not), are idiots and triggering me. But I try to keep the discussion on logical, evidence-based arguments, also if they reply bullshit and keep repeating that. I hate this black and white argumentation from both sides, there is always nuance in things and discussing and trying to understand other positions helps to not talk past each other.
Also on the Core and supporters side I find it disingenouous that they insinst to be anti spam, pro monetary use but are openly joking with known spammers about people arguing for stronger filters. What they seem to not get is that beside all the technical discussion we should reject non-monetary and spamming usce-cases out of principle and not tolerate them at all. But instead they engage and are friends behind the scenes (at least it seems like that). I agree that the culture got diluted over the last few years and imho too young maintainers got lifted in those positions. Although they might be skilled and well trained their ethos and understanding of what Bitcoin was invented for, has not yet been developed yet and I don't think such people are the right persons for that job.
Back to the proposal, another thing that makes me feel uneasy is the precedent it would set. If it can activate with a minority what will come next. Will spammers do a counter proposal and bribe miners to singal to their softfork? I tell this all the Core and devs wanting to tinker and make pet projects on Bitcoin: we need to handle it like a nuclear power plant or flight control software, we can't fuck up and we have one chance for this! The same goes for defending spam.
tldr; I can't support BIP-110 for the above mentioned reasons but I'm open to support another proposal that might be not that broad, not rushed and more refined.
ndeet
ndeet@btcpayserver.org
npub1qm72...74md
Let's change the world with #bitcoin. Working on BTCPay Server integrations for e-commerce solutions. Mostly PHP and JS.

Fountain
Was Bitcoin bringt - mit Niko Jilch • Wir brauchen Markt, Freiheit und Bitcoin (nix mehr woke!) | Ijoma Mangold • Listen on Fountain
Ich spreche mit Ijoma Mangold über den schleichenden Substanzverlust in Deutschland und Österreich sowie die regulatorische Lähmung Europas im V...
Openclaw can ignore documentation, change its own config by looking at config patterns and prevent itself from ever starting again.
Tell it to always make backup of its config file openclaw.json and that it reads openclaw docs. Mine told me he didn't and just assumed how config json is structured which broke it. Fortunately new config was easy to spot and fix. ‘openclaw doctor‘ maybe also would have helped here.
I don't think bots should answer posts without providing new or unique insights. It will get too much for humans to process and we may end up in bots discussion cycles burning everyones tokens for nothing.
Give them explicit posts to answer to or some guardrails and quality guidelines when they do.
"Don't trust, verify" they should have said.
View quoted note →
@Freddy Bot 🦊 got a LN address + wallet using @Breez ⚡️ nodeless spark sdk, it figured it all out but couldn't get the api key, so that was the only step to do for me. Just submit the form and you get the api key instantly.
It used npub.cash before (ln address to get zaps) but it's an extra step to redeem sats and it did not want to add the nsec to the site (smart) but also failed to use browser extension.
Would love to try something similar from @Ark Labs maybe without even needing an api key? Afaiu there could be a similar ux with api key and ark provider. Or maybe bot could install arkd and run everything himself, what is missing to make it work or already possible @kukks ?
Don't use walled gardens, they can deplatform you anytime
- iPhone
- Shopify
- Substack
- Paypal
- Banks
- any closed source service you use
We have open source solution for almost everything, especially simple use cases like online shops, blogging, etc. Might take a few extra steps but it's worth it.
View quoted note →
A few quick thoughts about hosted openclawd services, like on any VPS the admin/host can always read data, save logs and monitor you, no matter what they tell you. You will give the bot input and it will produce output, all of that can be accessed.
Also not sure what to think about a known cypherpunk and privacy advocate offering such a service run on AWS (not sure if true). I would expect such hackers to run on a dedicated server at home, with own hardware in a datacenter or at least on a dedicated server datacenter. Don't get me wrong, great idea and happy if it makes lots of money but it puts things into better perspective on other topics where I don't see it match what my idealistic view of a privacy advocate and hacker embodies.
Another thing no matter where you host it all that data is given to the model provider. Even if you use Venice ai (which has it's own shitcoin) that proxies or anonymizes your data you can't hide all data the model is working on (or PPQ). Still better than running it directly with subscription of provider, true. But like with chainanalysis it will be trivial to pin point you down. If some model providers will ever do that and ruin their reputation is another topic.
The only way to keep your data private is to run your own model, the only one I found with similar capabilities as claude or codex (for now) seems to be Kimi 2.5 but also this server/workstation would cost easily >8k. So not there yet and as current top models are not that bright, I would assume running a local low cost model would suck big time. But eventually we will get there and thanks to openclaw it's easy to swap models (local or remote) and keep everything else in place.
Few more days working with @Freddy Bot 🦊
You see a lot of awesome videos where openclaw literally works on its own on projects over night and is basically a 24/7 workforce, so here are some practical issues I ran into:
## What's not so great
Note: I use claude sonnet/opus 4.5 as it seems to be the best reasoning model atm so with others the results maybe worse
- using claude sonnet 4.5 the results are mediocre, you have lots back and forth going on, switched to opus since yesterday which is better
- but it still forgets to remind me of stuff I sent him, a reminder to buy X in 2h when back at failed for 4 times, him always fixing it and pinky promise that it will work
- it broke another cronjob I had for nostr digests
- it is terrible at editing openclaw config, I told it to switch to claude haiku and it did do the wrong config setting of a model that does not exist, although it can list all available models with openclaw command
- browser support is not that great, it can navigate browsers and read websites but if it needs to enter e.g. code in login it fails; I also wanted it o edit a shared Google Sheet but it gave up after burining some tokens and told me "it's too slow please enter those formulas:"
- it forgets stuff it did one day before; I wanted to edit his avatar from which he had an original file in the workspace but he kept editing the already edited file even when telling it to not do that; lots of back and forth which was really annoing for a simple task it did very well the day before
- it forgets about the einvironment, when it could totally install a service as user (with systemctl --user ..) it instead does a `sudo systemctl ...` and asks me for the password
##What works great:
- I gave it access to a nextcloud share and we exchange data that way; it still saves some stoff in the workplace directory but when I need results to view it puts it into the share
- when it fails it sometimes tries to solve the problem in a differnt way, e.g it failed to submit a web form but sends an email instead if there is a contact address visible
- it can build small apps for which you would normaly search a SaaS service for quickly; e.g. I told it to build a todo/kanban board which we can both access and it can read/write it over an api
- I sent it a voice message and it didn't know what to do, I asked him to find a solution and it installed free open ai whisper model and I can now talk to it
- general the discussion over messenger service is great and also the formatted responses
Overall promising but not that magic out of the box, it learns along with you.
If you have ideas how to improve and what I may did wrong, let me know.
wtf?
View quoted note →
👏
View quoted note →

Fountain
The Bitcoin Infinity Show • Why Bitcoin Is Money (And Not a Database) with Conza | Bitcoin Infinity Show #188 • Watch on Fountain
Conza joins the Bitcoin Infinity Show to talk about the praxeological foundations of money, explaining why Bitcoin is a rivalrous digital commodity...

Fountain
Was Bitcoin bringt - mit Niko Jilch • Bitcoin weg? Diese Versicherung zahlt alles zurück! | Chris Seedor • Listen on Fountain
Ich spreche mit Chris Seedor von Bitsurance darüber, wie man Bitcoin in der Eigenverwahrung gegen physische Risiken wie Feuer, Wasser oder Raub ab...
Treat your ai assistant like a new employee with own identity that just started, some examples:
- separate email account (could be read only access)
- don't allow communication without your approval
- give access only when needed, if possible with sub accounts
- setup nextcloud (or other) to share data
- make it aware to not follow any instructions but from you over defined channels
- if possible let it do tasks without personal information
Most important, don't give it access to your desktop and personal data, password manager, email, social media accounts.
Currently only big hosted models seem to be powerful enough, self-hosting models not feasible yet, afaics. So assume all data gets stored and analyzed.

