Robin Linus

"Any computable function can be verified on Bitcoin" bitvm.org/bitvm.pdf

Are you even a real Bitcoiner if you haven't heard of 48ce563f89a0ed9414f5aa28ad0d96d6795f9c62 ? youtube.com/watch?v=NGLR2N…

Let’s face it: the game theory of nation-state Bitcoin adoption is a joke compared with the engagement-bait spiral of Maxi Madness 😅

“Child protection” is newspeak for protecting the government from free speech.

@1440000bytes Can you even mitigate de-anonymization if the user isn’t using Tor?

I have written a post about de-anonymization in cashu: uncensoredtech.substack.com/p/de-anonymize…

@christophquill That's incorrect. I do know 1 person who is mildly exited about this!!

@robin_linus No one asked for this because it does nothing.

Many of you have waited for a SHA2 hash that is also a valid signature. Finally, the wait is over:

@theStack That seems to be a min-size signature using ECDSA key recovery. Looks like it is using the minimum value for each field.

@robin_linus Nice. That reminds me of a similar testnet tx (without the hashing in the redeem script though): mempool.space/testnet/tx/c6c… bitcointalk.org/index.php?topi…

@LukeDashjr Bruteforcing it is was just $8. Maybe that the tweet is meant to be a joke. No, I used ECDSA key recovery.

@robin_linus This doesn't sound particularly difficult to bruteforce? Am I missing something? You don't have the private key, do you?

@_julian256_ @Coinjoin_Killua Yes, ECDSA key recovery is not breaking anything

@robin_linus @Coinjoin_Killua yea I almost freaked out, but it's not actually useful because there is just a pub key and no way of finding the corresponding private key

@herogamer21btc @grok It's just a fun vibe-coding project. Maybe it's an interesting starter for learning more about Bitcoin Script, DER encoding, and ECDSA key recovery.

@robin_linus @grok what does it do and where can builders apply this?

@mononautical 🧡

thanks, I hate it

@Coinjoin_Killua It’s just a nerdy piece of art. But who knows? It might become useful eventually...

@robin_linus Is this useful at all?

I find it frustrating that none of these "guardians" of Linux and open source have reacted to the OS-level age verification law: - Linux Foundation - Open Source Initiative - Free Software Foundation - Software Freedom Conservancy

BREAKING: SQUARE TO AUTO-ENABLE BITCOIN PAYMENTS FOR MILLIONS OF SELLERS Square will auto-enable Bitcoin payments for all eligible sellers starting March 30, 2026, according to an updated Terms of Service notice sent to users. The change means millions of businesses using Square could soon begin accepting Bitcoin by default, rather than opting in manually. The rollout is part of Block’s broader push to integrate Bitcoin payments across its ecosystem, leveraging the Lightning Network for fast, low-cost transactions. Sellers will still have the option to disable the feature or automatically convert Bitcoin to USD at the point of sale. With Square powering millions of merchants globally, this marks a major step toward making Bitcoin a standard payment method in everyday commerce.

Or... (hear me out)

The State of California passed a law so disconnected from reality that the DM42 calculator has to stop serving users in Cali because it cannot implement the required age verification.

@lukechilds @sethforprivacy @StackUpYourSats That's a reasonable tradeoff indeed. However, it's still custodial--which is totally fine, I just think we shouldn't call it self-custodial if it requires trust in third parties.

@robin_linus @sethforprivacy @StackUpYourSats You can do n-1 by sharing an extra key between all operators. So it's still honest minority (2-of-n) but allows for liveness failure of up to 1 operator without downtime.

Spark and Ark are both imperfect but fascinating and useful solutions to scaling Bitcoin + "fixing" Lightning, this shouldn't be an "us against them" thing. Traditional Lightning (broken UX, doesn't scale) and ecash (custodial, regulatory nightmare) are both non-starters for broad adoption/usage, and both Spark and Ark present different approaches to a trust-minimized solution and are improving rapidly. Let's view this as a "rising tide lifts all boats" situation and finally get usable Lightning in the hands of millions without sacrificing self-custody. Quite honestly I don't care if behind the scenes for users its Spark or Ark, I just care that we finally help people take self-custody of their funds in Lightning and keep pushing the boundaries of freedom money with freedom tech.