Dr. Margot Paez

Climate change physicist and admirer of heterodox economics. I have crazy ideas about bitcoin. Tweets are my own, not my employer's.

Climatepunks use bitcoin.

[Dr. Margot Paez @jyn_urso]

Too much of our effort on climate change is spent mourning the death of our future. We can still have a future and we should still dream of what it can be. If we accept doom, then that’s what we’ll get. Yes, we need transformative change to get there, but first we need vision.

[Dr. Margot Paez @jyn_urso]

Throughout my PhD I loathed teaching. Through the @bitcoinpolicy REU program, I have learned that actually I just hate academia but I really get a lot of pleasure and satisfaction out of mentoring students through their research projects. I will miss my interns but next year I get to do it all over again. Looking forward to it.

[Dr. Margot Paez @jyn_urso]

@callebtc 🤭

[Dr. Margot Paez @jyn_urso]

@Rob1Ham Matrix and vector multiplication is very dangerous.

[Dr. Margot Paez @jyn_urso]

@newenglandhodl They doing this still?

[Dr. Margot Paez @jyn_urso]

@callebtc Like the book?

[Dr. Margot Paez @jyn_urso]

How’s BIP110 signaling going? Is there a website that is tracking this?

[Dr. Margot Paez @jyn_urso]

@DecrimNat Not true. Opinions are why so many people recommended coldcard.

[EVAN KALOUDIS @evankaloudis]

🚨PSA for LND + BTCPay Server users🚨

Don’t assume you’re safe after upgrading.

You’re going to want to explicitly destroy your macaroons and macaroons.db and recreate them fresh. This also applies to auth mechanisms for other LN backends.

Also, if you generated a hot on-chain wallet in BTCPay you want to move those funds.

[Dr. Margot Paez @jyn_urso]

In case you missed it, the livestream recording of our student research colloquium is up. Please take some time to watch, our interns produced really valuable research on bitcoin’s social impact, mining and energy development, and the Core v Knots debate.

[Bitcoin Policy Institute @bitcoinpolicy]

2026 BPI REU Final Colloquium https://t.co/gq5WaplhQU

[BTCPay Server @BtcpayServer]

There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.

Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.

If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.

[The Rage @theragetech]

🚨NEW: IS DEBANKING THE NEW IMMIGRATION POLICY?

Financial regulators are the latest agents to be recruited in the Trump administration’s war on immigration.

🔗 By @EconWithNick

https://t.co/sartZw0wHg

[Dr. Margot Paez @jyn_urso]

Saylor needs to get rekt.

[Pledditor @Pledditor]

You know how social engineers and email scammers purposefully write in poor grammar as a filter to ensure everybody who falls for the scam is of extremely low intelligence?

[Michael Tidwell @miketwenty1]

I want to put some serious thoughts out there. I have friends and people I respect who support BIP 110. My concern is the manipulation that could happen if, or more likely WHEN, it fails.

Every hour we get closer, it becomes more likely that this soft fork will result in a hard fork, especially given the attitudes being posted publicly on X. It is concerning that reality does not seem to be sinking in regarding something that should be obvious.

A soft fork intended to stop spam, although I disagreed with many of the details, I was not really opposed to it in principle.

However, I cannot help but call out this delusional behavior. We are less than TWO days away from this becoming extremely contentious and potentially resulting in a rapid hard fork. Over the last 24 hours, only TWO blocks have signaled "readiness or support" for BIP 110.

Chris Guida himself said this on stage at the Toronto BTC++ conference. Exact quote:

"I don't think there's going to be any uncertainty leading up to the fork. A few days before the deadline, they're all just going to turn it on, and everything is going to be fine."

I genuinely want to make sure people do not get rekt here. If you remain a supporter through thick and thin, even in the event of a potential hard fork, I strongly recommend that you do not sell your coins on the chain with the clear majority of SHA-256 hashpower.

If you are also bullheaded about BIP110, please take heed of advice from people like @start9labs on how to protect yourself in this situation. You may need to close your Lightning Network channels to prevent a loss of funds if you remain on the minority fork and refuse to run a Bitcoin Core node.

Do not be misled by definitions. If BIP 110 has minority hashpower, it will not be Bitcoin.

Please do not let your friends be manipulated into losing a lifetime's worth of Bitcoin savings. BIP 110 supporters are Bitcoiners, and they do not deserve to get rekt, in my opinion.

[Dr. Margot Paez @jyn_urso]

@Mandrik How about, “ice core”?

[Dr. Margot Paez @jyn_urso]

@Crypto_Mags Just shows the level of delusion they have that they think somehow everyone will abandon the btc chain and price will collapse and it wont matter.

[Dr. Margot Paez @jyn_urso]

@GreaserRichard I think we need pled ids. If you cant verify your plebeian status with a podconf issued pleb id then you cannot run a node.

[Dr. Margot Paez @jyn_urso]

I am glad toxic maximalism is dead. Maybe we can be a more inclusive community where adoption isn’t just among fascist AfD types.

[Dr. Margot Paez @jyn_urso]

@AaronSepulvedaC What kind of protein? Socialist proteins exist.

[Dr. Margot Paez @jyn_urso]

@ThumpGoFast Who else?

[Rob Hamilton @Rob1Ham]

This reply to @callebtc was one day before the red team initiative began.

Kimi K3 went open weights on July 27th. I had pinged people about how powerful Kimi K3 was. We were red teaming our own infrastructure as it launched to see what it could find.

After the Cold Card hack, it became quickly evident that most people who maintained software were not using frontier AI tools for defensive security.

For a couple dollars in credits, you can look at any open source codebase to see what is found. There are a lot of rough parts around the edges, but there is one thing for certain, the world of cyber security has changed forever.

What we are doing is not particularly special, for $10-30 you can likely scan most small/medium code bases and take a look for yourself. There are great tools like @opencode we've been using to have access to many models at once.

The bag guys will do this (or already have!) and your security posture has to change.

Have a security.md file in your repository, this guarantees the cleanest way to handle responsible disclosure.

We are entering a new world of cybersecurity where anyone for the price of a nice meal can interrogate a code base. I'm not sure any of us understand the long term ramifications.

If you are interested in supporting the effort you can donate to the @OpenSats red team fund.