Code RED: priority support for red teaming
opensats-code-red
https://opensats.org/blog/code-red-supporting-first-responders
- Organisation
- OpenSats
- Evidence role
- Organisation statement
- Published
- 2026-08-06
- Source changes
- 0
- Detected differences
- 1
- Unreviewed
- 0
- Copies held
- 2
OpenSats' own 6 August announcement, by Gigi and the organisation, that red team applications will be prioritised for the foreseeable future, with a dedicated path at opensats.org/red and reimbursement of past LLM token costs. Held as a funder changing what it pays for in response to the incident, which is a distinct kind of response from a statement about it: the same nonprofit is named in the held Red Team posts as covering their compute bill. OpenSats is a bitcoin funding nonprofit and NVK stepped down from its board on 2 August (opensats-nvk-board-departure); the post itself draws no connection. What is disbursed under the policy is not observable from this archive.
Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
MissionFundsAboutBlogFAQDonate Mission Funds About Blog FAQ Donate Published onThursday, August 6, 2026 Code RED: Priority support for red teaming Authors NameGigiTwitter@dergigi NameOpenSatsTwitter The COLDCARD vulnerability that is currently being exploited shows that security flaws can go undetected for years, even catastrophic ones. We want to do what we can to help the first responders that have been fire fighting, triaging, and red teaming as the industry digests what this exploit revealed. A lot of people have been working 24/7 in the last few days, doing everything in their power to reduce the damage that is being done. We see it as our duty to allocate sats where they're needed most. And right now, support for the red team is duly needed. If you are red teaming critical Bitcoin software today, opensats.org/red is a priority path to funding, including reimbursement of past LLM token costs. Click here to >_ applyfor red team fundingApplyfor red team funding✉️✉️✉️ We will prioritize any red team applications for the foreseeable future. Thank you for your work and support. Discuss on nostr • View on GitHub Tags grantsbitcoinsecurity Previous Post Meet Barry Deen, the Webmaster Behind Wisp ← Back to the blog Send emailView on GitHubView on XView on Nostr Terms · Transparency · Privacy · Contact Open Sats Initiative, Inc. (EIN 85-2722249) is a 501(c)(3) non-profit organization. All gifts and donations are tax-deductible to the full extent of the law. © 2026 OpenSatsExcerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
1 presentation-noise difference. Sidebar, ticker and other page chrome churn that our review classified as not being a change to what the source says.
- +2 -0 Only the 'Next Post' navigation link and adjacent post title appeared below the announcement; the announcement text was unchanged.
The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
Compare the screenshot or a quotation against the original while it is available.