Jump to content
Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Unlock history: who found what, and when

From CMP Wiki

A dated record of how the CMP 170HX unlock came about, from the card's launch in 2021 to the state at the end of October 2026, with credit for each finding. Dates are the dates of the Discord messages (UTC) unless a post gives another. Where accounts disagree, every side is shown with its source and no verdict. This page records who found what and when; it does not describe how the exploit works inside. How to run the unlock today is on Driver unlock, and what each feature gives is on Unlocks.

Before 2026

2021 to 2025: a GA100 mining card, the Merge, and cards at about 200 USD

The CMP 170HX appeared on the Chinese market on 2021-09-01 with no NVIDIA announcement: a GA100 die (the A100's), passively cooled, one 8-pin connector, no display output, at about 4,700 USD. The 170th Street GitBook gives 164 MH/s at 250 W and a 4,299 USD MSRP. Linus Tech Tips covered it on 2021-11-25. Members recall mining farms paying about 4,300 to 5,000 USD a card (Studebaker: 4,300 USD with minimum orders over 1,000 pieces), and Miséricorde said the cards were profitable for Ethereum mining for only about 2 months before proof of stake. The Ethereum Merge on 2022-09-15 collapsed prices to 300 to 500 USD; by 2025 eBay listings ran 200 to 400 USD, and miners dumped cards at around 200 USD before the unlock. The cards last mined Pearl: on 2026-07-28 giaki3003 called Pearl mining "on life support" and CUTE expected prices to drop once it stopped paying.

Reported
Source: @giaki3003, 2026-07-28
Source: @cute_sc2, 2026-07-28
Source: @darkmaniac7, 2026-07-30 (lab notes)
Source: @smit1237, 2026-08-30
Source: @_studebaker_, 2026-08-30
Source: @wakeupmbrc1, 2026-09-16
Source: @smit1237, 2026-09-16
Source: repo github.com/amoghmunikote/170th-Street by amoghmunikote on GitHub, posted by @markshowa, 2026-10-18

The FMA workaround (2023) and the first peer-reviewed study (2025)

niconiconi's review of 2023-10-25 ("All GB/s without FLOPS") documented the FP32 throttle on fused multiply-add, the two-layer PCIe lockdown (a firmware Gen1 lock plus 12 lanes without AC coupling capacitors) and a water block. In December 2023 GitHub issue #73 on dartraiden/NVIDIA-patcher confirmed that compiling OpenCL kernels with #pragma OPENCL FP_CONTRACT OFF raises FP32 from 0.395 to 6.285 TFLOPS. Hackaday featured the card on 2024-09-11. arXiv 2505.03782 (Xing Kangwei, Jiangsu University, 2025-04-30) is the first peer-reviewed study: it validated the workaround and reports more than 15x FP32 uplift. In August 2026 Petri Krohn called issue #73 the thread that started cmpunlocker development (next section). A second paper by Xing Kangwei, "Microbenchmarking Instruction-Level Tensor Core Throttling in NVIDIA CMP 170HX" (Zenodo record 19002983, 2026-03-13), is on @petrikrohn_26497's reference list of 2026-07-31 on the clean room server; the full list is on Reference library.

Reported 8 GB and 10 GB
Source: @mrmannyatx, 2026-08-02
Source: @petrikrohn_26497, 2026-08-14
Source: @petrikrohn_26497, 2026-07-31 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/amoghmunikote/170th-Street by amoghmunikote on GitHub
Source: niconiconi
Source: Xing Kangwei (arXiv)

The FMA workaround in FluidX3D issue #8 (2023-10-24 to 10-27), and issue #73 (2023-12-06)

The workaround was worked out in FluidX3D's benchmark thread (issue #8) around the time of the review above. On 2023-10-24 biergaizi posted FluidX3D results for a locked CMP 170HX. On 2023-10-26 he measured plain (non-FMA) FP32 at about 6,200 GFLOPS with a SYCL benchmark built with contraction off, about 16 times the 395 GFLOPS measured with FMA. On 2023-10-27 replacing FluidX3D's explicit FMA calls raised FP32/FP32 only to 2919 MLUPs/s, because NVIDIA's OpenCL compiler still fused operations, while the same build on a PoCL runtime modified to disable contraction reached full FP32/FP32 speed. The same day FluidX3D's author (ProjectPhysX) suggested #pragma OPENCL FP_CONTRACT OFF, which on NVIDIA's own compiler raised FP32/FP32 from 2276 to about 7585 MLUPs/s, close to an A100. NVIDIA-patcher issue #73 was opened on 2023-12-06 by jetcat8848 with the higher FP32 figure for CMP HX cards, about six weeks later.

Reported 8 GB
Source: repo github.com/ProjectPhysX/FluidX3D by ProjectPhysX on GitHub
Source: biergaizi, biergaizi, ProjectPhysX and biergaizi in FluidX3D issue #8
Source: jetcat8848, NVIDIA-patcher issue #73

Why the card exists: origin theories (debated in September 2026)

Members disagree on why NVIDIA made a crippled A100 for mining. In the order posted, all on 2026-09-18:

  • Takka: a lower-binned A100 meant as an export-legal option for China, never exported, then crippled into a crypto card. He estimated at most 100k to 200k cards were made against millions of A100s, if serial numbers are exhaustive. Source: @spectakkular, 2026-09-18
  • xtj7: the card launched in 2021 and the China AI export restrictions came in 2022; NVIDIA crippled A100 silicon where it would not hurt mining, so as not to cannibalise A100 sales during the mining boom, before ChatGPT changed demand. Source: @xtj7, 2026-09-18
  • Miséricorde thought the A100 market was saturated. Source: @wakeupmbrc1, 2026-09-18
  • cibernox: the cards became e-waste once Ethereum moved to proof of stake, which fits the low days-of-use counters owners read from their cards. Source: @cibernox, 2026-09-18

Earlier theories on the CMP 170hx Clean Room Discussion server, in the order posted:

  • @m3gagluk (2026-06-27): there may be chips with working VRAM but failing NVLink blocks; "those chips wouldn't qualify for other cards either". Source: @m3gagluk, 2026-06-27 (CMP 170hx Clean Room Discussion server)
  • @xanthefin (2026-07-01): the dies could be an A100 batch with early ECC errors. Source: @xanthefin, 2026-07-01 (CMP 170hx Clean Room Discussion server)
  • @leikowo (2026-07-06): 64 GB versions of the PCIe A100 were deployed in a few European supercomputers. Source: @leikowo, 2026-07-06 (CMP 170hx Clean Room Discussion server)
  • @bigptoughneigh (2026-07-07): the stacks are there but binned down, with memory that did not make the cut; packaging loss or not enough power are the only reasons, and he recalled someone saying NVIDIA put perfectly fine A100 cards into CMP cards towards the end of the lifecycle. Source: @bigptoughneigh, 2026-07-07 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-07 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-07 (CMP 170hx Clean Room Discussion server)
  • @gluckmaker (2026-07-07) pointed to a screenshot of an "A100 80GB" with 96 GB and all six memory channels active. Source: @gluckmaker, 2026-07-07 (CMP 170hx Clean Room Discussion server)

None of these posts cites a source.

Contested

About four years of attempts, and cards bought in advance

Asked by Toffles on 2026-08-10 whether the first unlock took less than a month, Petri Krohn answered almost four years: from the Ethereum Merge (2022-09-15), which made CMP cards worthless for mining, to the first clean-room unlocker shared on GitHub (2026-07-14), with people trying throughout. On 2026-07-28 meatsus said the unlock had been "cooking" for 3 years with the real progress in the last 3 months, and Matty Ice said he had worked on it for 3 years. On 2026-08-06 Matty Ice said he stocked up on many 170HX cards years earlier because he always believed an unlock was possible, mined with them in the meantime, and now supplies members (he sent Pasteyy 8 GB cards). The stockpiling account has not been cross-checked.

Reported
Source: @meatsus, 2026-07-28
Source: @icematty, 2026-08-06
Source: @toffles3179, 2026-08-10
Source: @petrikrohn_26497, 2026-08-10

Hardware attacks tried before the software unlock (undated)

Humvee55 said on 2026-07-28 that before the software unlock some cards served as test beds for hardware attacks, because the group expected to need voltage glitching in the style of the Nintendo Switch hack. They tried an SOIC emulator and a bus sniffer, Studebaker mentioned a Raspberry Pi Pico, and the hot-glued wiring did not hold; Humvee55 saw plenty of I2C traffic and accidentally locked a VRM. No date is given for these attempts. The idea came back in October 2026: mrpandagod linked a Tegra voltage-glitching paper (arXiv 2108.06131) on 2026-10-10, and Shirogeek looked for a defective 8 GB card as a glitching test subject on 2026-10-17. Nothing has been built. On the clean room server the idea came up earlier and kept going. @m3gagluk linked the same Tegra paper there on 2026-06-27, the server's first day, and on 2026-07-05 @bigptoughneigh said an AI assistant had told him he would have to start hardware glitching (AI-generated advice, not measured). On 2026-10-02 @dalzyyy said he had not given up on voltage glitching. On 2026-10-24 he gave the card's voltage controller as an MP2888B (marking mp2888bgu; @shirogeek: there is no datasheet for it), and over PMBus he saw the GA100 request about 0.7 V until the OS loads ("90% sure"). He had not written the controller's EEPROM, so nothing stuck, and kept a card whose HBM seemed to be dying (an instant Xid in memtest_vulkan) for voltage-glitching experiments; on 2026-10-31 he found HBMVDD fixed at 1.25 V as far as he could tell. On 2026-10-28 @petrikrohn_26497 recalled that very early in the research a member put an RP2040 or similar on the bus to sniff addresses; the results were inconclusive and were lost with the old Discord server. The glitch route went public on 2026-11-10: Voltage-glitch unlock (GA100VFI).

Reported 8 GB and 10 GB
Source: @m3gagluk, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-05 (CMP 170hx Clean Room Discussion server)
Source: @scallion_9883, 2026-07-28
Source: @_studebaker_, 2026-07-28
Source: @meatsus, 2026-07-28
Source: @djpandaman, 2026-10-10
Source: @dalzyyy, 2026-10-02 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-13 (CMP 170hx Clean Room Discussion server)
Source: @endsjeremy, 2026-10-17
Source: @shirogeek, 2026-10-18
Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @shirogeek, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-24 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-25 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-10-28 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-10-31 (CMP 170hx Clean Room Discussion server)

March to June 2026: the private group and the exploit

The early work happened in an earlier Discord server and a small private group. Most of what is known about it comes from later accounts by members, so the dates below are the dates those accounts were posted.

Pointer: Petri Krohn's account of the private group (posted 2026-07-22)

On 2026-07-22 Petri Krohn, one of a seven-person private group, posted a dated account of the unlock from its start on GitHub in March 2026 to the clean room. A longer write-up by @petrikrohn_26497 exists; see Discord. Pointer: the full account waits for its author's agreement (ask the author first); points from it that others also posted are dated separately on this page.

Reported 8 GB and 10 GB
Source: @petrikrohn_26497, 2026-07-22

From GitHub in March 2026 to a Discord server in April

Petri Krohn's account of 2026-07-22 dates the start of the unlocker work to GitHub in March 2026 and the move to a Discord server to April 2026. On 2026-08-15 he said the first thing he proposed in the GitHub thread in March was to run the card in a virtual machine and spoof both its device ID and its VBIOS; he did not know whether anyone had tried it.

Reported
Source: @petrikrohn_26497, 2026-07-22
Source: @petrikrohn_26497, 2026-08-15

dartraiden/NVIDIA-patcher issue #73: where many members came from

At 00:01 UTC on 2026-06-26 GMZombie007 reminded the server that many members came from issue #73 on dartraiden/NVIDIA-patcher, the thread about higher FP32 throughput on CMP HX cards: he came from there, as did Petri and, he thought, BlackSun, and Far called it his entry point ("the gateway drug"). On 2026-07-23 CUTE linked a comment in the same issue whose author was upset that the unlock was a hack with an uncertain payoff; Far called that ungrateful. On 2026-08-14 Petri Krohn posted, "for the historical record", that issue #73 is the thread that started cmpunlocker development, and Far said it was how he had found the previous Discord server.

Reported
Source: @gmzombie, 2026-06-26
Source: @farawaythrower, 2026-06-26
Source: @mrpec, 2026-06-26
Source: @cute_sc2, 2026-07-23
Source: @petrikrohn_26497, 2026-08-14

Humvee55: the first target was the compute throttle

Humvee55 said on 2026-08-11 that the VRAM unlock gets the headlines, but the original target was the compute throttle, which turned out to be a single register: writing it unlocks compute with no BIOS or driver modification, and cmpunlocker is one way of writing it. Asked by Josephur, he said the unlock ended up being an overflow, after months of trying device-ID and strap approaches. By then the CMP 90HX, 70HX and 170HX had all been cracked.

Reported
Source: @scallion_9883, 2026-08-11
Source: @josephur, 2026-08-11

Humvee55's recollection: early buyers, PG199 and BC-250 work, a proof of concept around mid-June (posted 2026-11-11)

Asked by andrew how people who got cards for about 200 USD heard about the unlock, Miséricorde said almost nobody bought them for the unlock, only the original members maybe; the cards were bought for mining ("qubiq or something"). Humvee55: the original Discord, and mostly chatter on the original GitHub issue, which was driving small price fluctuations. He does not remember the date the group first demonstrated the proof of concept: "I want to say mid june?". US supply seemed very low at the time, so few cards were listed on eBay, and most people thought the cards were "basically trash". What got him into it was Leiko's PG199 work; he started on the BC-250 and moved back and forth between the two. His mid-June estimate sits beside the dated accounts under July 2026 (When did the first unlocker work?).

Reported 8 GB and 10 GB
Source: @cooker.androo, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @wakeupmbrc1, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @scallion_9883, 2026-11-11
Source: @scallion_9883, 2026-11-11

May 2026: a CMP and A100 comparison of 120 registers (research wiki)

According to the Consensus-Protocol research wiki, which its author calls unverified, the earliest dated comparison of the CMP 170HX with A100-class silicon read the same 120 registers on two 10 GB cards (2026-05-05 and 05-07) and on two DRIVE A100 32 GB boards (PG199) on 2026-05-31. Only five groups of settings separated the CMP from the A100: SM speed select, the PCIe generation at boot, NVLink disable, ECC enable and memory geometry. The research wiki does not say who ran it, and it took place before this server existed, so the export cannot confirm it. What each feature gives an owner today: Unlocks.

Reported
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

Amogh bought his card in April 2026

Amogh, the server owner and cmpunlocker's maintainer, said on 2026-07-19 that he bought his CMP 170HX in April 2026. Black Jesus: "Damn. It was known back then already?"

Reported
Source: @_j3ns, 2026-07-19
Source: @ashtray9843, 2026-07-19

The earliest capacity report in the server (2026-06-22, second-hand)

On 2026-06-22, in the earliest messages of this server's history, atsasin passed on second-hand information: the 10 GB card works at 40 GB, 80 GB had been reached on it but was very unstable and had to run at half speed, and the 8 GB card ran stable at 64 GB. He put the 10 GB card's instability down to its Samsung HBM against SK Hynix on the 8 GB card, said he had not seen it himself, and asked others to replicate it. Pointer: marked ask the author first; only these short claims are given here.

Reported 8 GB and 10 GB
Source: @atsasin2126, 2026-06-22
Source: @serplay228, 2026-06-22

The server was invite-only in June 2026

In June 2026 the cmpunlocker Discord was private. On 2026-06-23 Amogh said he had hand-picked members who agreed not to share any cmpunlocker knowledge, including the server itself, and that server access came with access to the cmpunlocker repository. After the original unlocking server went down on 2026-06-25 he stopped accepting new invites ("We already have a sufficient group of talented people, I think with some persistence and sweat we can get it to work."), but agreed to invite Petri Krohn, whose old findings had been deleted with the other server; Petri was posting in #general by 2026-06-27. The owner later cleared this history for public import with credit.

Reported
Source: @jiacheng_liu, 2026-06-23
Source: @meatsus, 2026-06-25
Source: @_j3ns, 2026-06-25
Source: @petrikrohn_26497, 2026-06-27

Compute unlock first works (2026-06-23)

On 2026-06-23, while improving the VBIOS flash method the project used at the time, Amogh found he had used a wrong offset in his calculation for both cards. At 21:52 UTC the same day he announced to everyone: "Compute Unlock finally works!", for either the 8 GB or the 10 GB card; he could not measure the gain himself because he could not fit a fan to his card. At 04:09 UTC on 2026-06-24 he fixed the multi-GPU issue and the offsets, and atsasin moved on to mixbench. On 2026-06-26 he announced a "huge" redesign of the logic, and remarked that GSP patching was useless, the view at the time. The public unlock that followed in July is driver-side and flashes nothing.

Reported 8 GB and 10 GB
Source: @meatsus, 2026-06-22
Source: @meatsus, 2026-06-22
Source: @_j3ns, 2026-06-23
Source: @_j3ns, 2026-06-23
Source: @_j3ns, 2026-06-23
Source: @jiacheng_liu, 2026-06-23
Source: @_j3ns, 2026-06-23
Source: @_j3ns, 2026-06-23
Source: @_j3ns, 2026-06-24
Source: @_j3ns, 2026-06-24
Source: @atsasin2126, 2026-06-24
Source: @_j3ns, 2026-06-26
Source: @_j3ns, 2026-06-26
Source: @serplay228, 2026-06-26
Source: @serplay228, 2026-06-26
Source: @_j3ns, 2026-06-26
Source: @gmzombie, 2026-06-26

The original unlocking server is deleted (2026-06-25)

The original 170HX unlocking Discord was deleted without notice on 2026-06-25 (meatsus: "I woke up to the other discord getting deleted lol"). Amogh announced that the original server was gone and called the effort a free-for-all with competing groups. He had already exported its chats and files for development, "especially jonpry and cab's work which were really helpful in development", and shared them on request through a restricted folder. On 2026-06-27 Thanos posted the logs of the deleted server with a 30-page AI summary of its findings. On 2026-06-26 Amogh asked for help with the SEC2-ROP work as the priority; on 2026-07-02 the motherboard of his development PC failed, pausing his work until a replacement arrived on 2026-07-15.

Reported
Source: @_j3ns, 2026-06-25
Source: @_j3ns, 2026-06-25
Source: @meatsus, 2026-06-25
Source: @thanos8912, 2026-06-27

Who deleted the first server, and why

Only the existence of the earlier server and its deletion are uncontested. The accounts, in the order posted:

  • 2026-06-25: asked who deleted it, lorfidel answered "Humvee" ("They claim they are worried about legal issues"); MrLoki89 relayed that BlackSun put it down to too many problems; adih thought the whole thing had been a scam; Far said the "not legit" talk was an inside joke to make Telegram and eBay scalpers dump their cards. Source: @lorfidel, 2026-06-25
    Source: @serplay228, 2026-06-25
    Source: @adih1266, 2026-06-25
    Source: @farawaythrower, 2026-06-25
    Source: @meatsus, 2026-06-25
  • 2026-07-18: lorfidel again attributed the deletion to Humvee55, who denied it ("I was just a normal user like the rest"). Thanos and decoy also took part. Source: @thanos8912, 2026-07-18
    Source: @lorfidel, 2026-07-18
    Source: @decoy.works, 2026-07-19
    Source: @scallion_9883, 2026-07-19
  • 2026-07-22: Petri Krohn's account says the old Discord was nuked because it may have held information leaked from NVIDIA, and that a new "clean room" Discord opened with the rule: no NVIDIA secrets unless the same information can be shown to come from public sources. Source: @petrikrohn_26497, 2026-07-22
  • 2026-07-28: Humvee55 said the "aha" moment quickly became an "oh shit" moment: attention grew too fast, material appeared on Telegram, crypto people arrived and everyone's names were posted everywhere. He said it was better that the unlock was seen as coming from "Chinese developers". ju5t5omedude said the unannounced shutdown felt like a rug pull. Source: @meatsus, 2026-07-28
    Source: @scallion_9883, 2026-07-28
    Source: @ju5t5omedude, 2026-07-28
  • 2026-09-22: mrpandagod, who says he was not in the original server, gave a second-hand account: the first ("dirty") unlock used leaked NVIDIA documentation, its authors deleted that server and its evidence to avoid being sued, and the unlock was rebuilt without proprietary information in a "clean" server. He called the clean server "this one", while other members refer to "the clean room" as a separate server. Source: @djpandaman, 2026-09-22

Contested

The clean-room rules become written policy (2026-06-27, research wiki)

According to the Consensus-Protocol research wiki, which its author calls unverified, the clean-room rules became written channel policy in the clean-room server on 2026-06-27: no NVIDIA secrets; knowledge that is not public only if it can be shown to follow from public sources; a ban for posting leaked material, including files from the deleted server. The exploit paper was named the one clean input document, because it was published openly and had been disclosed to NVIDIA. Separate dirty-room and clean-room teams were proposed and dropped; in practice the same people worked in different channels. That server is not in this wiki's export; Petri Krohn's account of 2026-07-22 (above) gives the same core rule. The clean room server's own posts from its first days carry these points. On 2026-06-27 @bigptoughneigh, who built its first channel and role that day, concluded that no dirty room was needed, "only a clean room to implement the paper (which we consider clean)"; @petrikrohn_26497 said cleanness means not basing published work directly on what NVIDIA considers illegally obtained secrets, and posted the paper's Zenodo record. @ozaty proposed moving off Discord to protect researchers' privacy, and @meatsus proposed accepting nobody new after about a week. On 2026-07-01 @petrikrohn_26497 told @dart_raiden, who asked to translate the paper into Russian, that the information is in the public domain; the same day @scallion_9883 asked a member not to redistribute an archive of the old server ("don't want to have another chat get nuked") and @arabel1la said it would ruin the clean-room idea. On 2026-07-05 @bigptoughneigh said a script from the old Discord would mean a ban.

Reported
Source: @ozaty, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @meatsus, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-06-27 (CMP 170hx Clean Room Discussion server)
Source: @dart_raiden, 2026-07-01 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-01 (CMP 170hx Clean Room Discussion server)
Source: @scallion_9883, 2026-07-01 (CMP 170hx Clean Room Discussion server)
Source: @arabel1la, 2026-07-01 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-05 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

The exploit write-ups: the paper and the MRMCD2026 talk

On 2026-06-26 Amogh posted the paper on the exploit, "A Canary in the Crypto Mine: Defeating Stack Protection in a GPU Secure Coprocessor" (Zenodo record 20916112); the same day Far joked about "Jon Pry writing that report". By 2026-06-28 a Zenodo link and a PDF had reached the M-Technics Telegram chat (the posts do not name the document; probably the same paper), and Petri Krohn told lorfidel: "It is public. It is supposed to be shared!" NFA linked the paper on ResearchGate on 2026-07-26, and meatsus pointed a newcomer to it on 2026-08-24, naming the author as Jon Pry. On 2026-09-13 Amogh recommended the MRMCD2026 talk "FACEB13D exploit: Liberating the A100 beast inside Nvid..." (title truncated in the export; video) as a history of the unlock. These are the primary public write-ups of the exploit that cmpunlocker and its forks build on; this wiki does not reproduce it. More: Reference library. On the clean room server @liuwake posted the ResearchGate page with a PDF of the paper attached on 2026-07-16, ten days before the post above. On 2026-09-09 @petrikrohn_26497 posted the slides of his talk at "the Chaos Computer Club conference in Germany on Sunday" (PDF posted by @petrikrohn_26497, CMP_170HX_unlock_September_2026_2.pdf) and posted them again on 2026-09-23; @cute_sc2 asked when the talk could be watched. The post names no conference beyond that.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-06-26
Source: @_j3ns, 2026-06-26, link
Source: @farawaythrower, 2026-06-26
Source: @mrpec, 2026-06-26
Source: @lorfidel, 2026-06-29
Source: @petrikrohn_26497, 2026-06-29
Source: @liuwake, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @never_fly_away, 2026-07-26, link
Source: @meatsus, 2026-08-24
Source: @petrikrohn_26497, 2026-09-09 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-09-13
Source: @_j3ns, 2026-09-13, link
Source: @cute_sc2, 2026-09-13 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-09-23 (CMP 170hx Clean Room Discussion server)
Source: @lycorascence, 2026-09-30

Telegram skeptics, and the memory-unlock post rushed to GitHub (late June)

On 2026-06-26 MrLoki89 said members of the Russian M-Technics Telegram channel, a Taobao, 1688 and Pinduoduo resale channel, were joking that the unlock news was a provocation by Russian special services; he and "blacksun" had been spreading it there. Petri Krohn linked an M-Technics post telling buyers "they haven't unblocked anything yet". On 2026-06-27 Petri said one reason he had rushed a post about the memory unlock onto GitHub was that a poster in that channel annoyed him by doubting it; he did not yet have his own system running but had seen screenshots of 200 TFLOPS and 64 GB of VRAM. lorfidel argued that proving the skeptics wrong would only confirm the exploit to bulk resellers and keep prices high. Coverage list: Press and coverage.

Reported
Source: @serplay228, 2026-06-26
Source: @petrikrohn_26497, 2026-06-27
Source: @lorfidel, 2026-06-27

July 2026: going public

When did the first unlocker work? Dates that disagree

Several dates are given for the first unlocker. "Working", "released in the clean room", "shared on GitHub" and "public on Reddit" may be different events. In the order they were posted:

  • 2026-06-23: Amogh announced "Compute Unlock finally works!" in this server (above). Source: @_j3ns, 2026-06-23
  • 2026-07-12: on the CMP 170hx Clean Room Discussion server, @counterstrikeaimgod posted "SM Unlock Successful" at 08:46 UTC and then SGEMM 12.28 TFLOPS FP32 and DGEMM 11.48 TFLOPS FP64 (compute capability 8.0), against about 0.38 TFLOPS FP32 on a stock card. At 08:48 UTC @rubbra_f posted gpu-burn output of 12,223 to 12,254 Gflop/s with 0 errors while the card heated from 62 to 73 C; the output's own timestamps read 14:24 WIB (07:24 UTC). The same day @port00 confirmed it on 8 GB cards but said it crashed within a minute under his load (driver 580.159.04, open modules), @bigptoughneigh said it works on both variants and ran gaming and LLM loads for hours without trouble, and @mrpec and @serplay228 confirmed it with the posted script. Source: @counterstrikeaimgod, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @counterstrikeaimgod, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @rubbra_f, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @port00, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @port00, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @port00, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @mrpec, 2026-07-12 (CMP 170hx Clean Room Discussion server)
    Source: @serplay228, 2026-07-12 (CMP 170hx Clean Room Discussion server)
  • 2026-07-13: Petri Krohn wrote that "Rubbra_F was the first to put the pieces together and produce a reproducible version of the compute unlock", and Amogh agreed. The posts do not reconcile this with the 2026-06-23 announcement. Source: @petrikrohn_26497, 2026-07-13
    Source: @_j3ns, 2026-07-13
  • 2026-07-13: Amogh wrote that "In the 170HX cleanroom server, a compute unlock was released and it's basically available to the public at this point in time". Source: @_j3ns, 2026-07-13
  • 2026-07-20: SkirtChaser dated the public Reddit post of the memory unlock to 2026-07-16. Source: @skirtchaser, 2026-07-20
  • 2026-07-22: Petri Krohn's account says the clean room built the first compute-only unlocker about 10 days earlier, that is about 2026-07-12, and released it on GitHub. Source: @petrikrohn_26497, 2026-07-22
  • 2026-07-27: Petri Krohn tied the first working compute-only unlocker, which he identifies as the first version of cmpunlocker in Amogh's repository, to around 2026-07-03, when clean-room members started buying up every card on eBay and the price went from about 200 to about 400 USD; Jeremy (Ends) read the same jump from eBay sold-listing data. Source: @endsjeremy, 2026-07-27
    Source: @petrikrohn_26497, 2026-07-27
  • 2026-08-10: Petri Krohn dated the first clean-room unlocker shared on GitHub to 2026-07-14. Source: @toffles3179, 2026-08-10
    Source: @petrikrohn_26497, 2026-08-10
  • 2026-08-11: Petri Krohn said the Clean Room unlocker was the first published, on the server owner's GitHub, on 2026-07-15. Source: @petrikrohn_26497, 2026-08-11
  • According to the Consensus-Protocol research wiki, which its author calls unverified, the throttle first came off on real hardware on 2026-07-12, through a manual five-step procedure run from a text console before any driver patch existed, with SGEMM measured at 12.28 TFLOPS; the person who did it put the cost at over 1,100 runs, about 50 of them genuinely different attempts. The research wiki does not name the person, and no message in this server's export carries it. The posts are on the clean room server (2026-07-12, above). Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

Contested

The first clean room scripts: requirements and first-run problems (2026-07-13 to 07-29)

The first compute-unlock scripts shared on the CMP 170hx Clean Room Discussion server were a shell guide script with a Python GSP patcher (attached as Guide_SM_1.sh and patch_gsp.py on 2026-07-13). @petrikrohn_26497 listed the requirements as he understood them: Linux on x86-64, Python 3.8 or newer, a CMP 170HX with device ID 10de:20c2 or 10de:2082, the nvidia-open 580.x driver with its GSP firmware present, and root; run the scripts, then use the normal open driver. Problems members hit, in the order posted:

  • @adih1266 (2026-07-15): install driver 580.159.04, because its GSP firmware path is hard-coded in the script; he also needed open kernel modules compiled from the same branch. Source: @adih1266, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @adih1266, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @adih1266, 2026-07-15 (CMP 170hx Clean Room Discussion server)
  • @ju5t5omedude (2026-07-15): on a CMP 50HX the script stops with a "no ga100" GPU found error; @petrikrohn_26497 said to edit the script to include the 50HX and perhaps rename the patched GSP firmware file so the driver loads it. Source: @ju5t5omedude, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-16 (CMP 170hx Clean Room Discussion server)
  • @ju5t5omedude (2026-07-16): the Python file has to be in the home directory. Source: @ju5t5omedude, 2026-07-16 (CMP 170hx Clean Room Discussion server)
  • @ju5t5omedude (2026-07-17): the 10 GB card's ID 2082 was missing from the script; with it added his 10 GB card worked, "almost identical but slightly higher performance than 8gb". On another machine with an AVX1 CPU, kill.sh hung. Source: @ju5t5omedude, 2026-07-17 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-07-17 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-07-17 (CMP 170hx Clean Room Discussion server)
  • @ju5t5omedude (2026-07-29) posted pcielink.sh to verify a Gen2 link. Source: @ju5t5omedude, 2026-07-29 (CMP 170hx Clean Room Discussion server)

These scripts are history; the current route is on Driver unlock.

Reported 8 GB and 10 GB
Source: @vokrus_gaming, 2026-07-13 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-13 (CMP 170hx Clean Room Discussion server)

cmpunlocker goes public (2026-07-14)

On 2026-07-13 Amogh polled everyone on whether to release cmpunlocker publicly. On 2026-07-14 he first said he would release only a fully working unlock; Petri Krohn argued that releasing the repository would speed up the memory unlock, with more people running tests themselves instead of relying on bots, and that at least a copy should go to the clean room. Mr Pec and Matty Ice agreed, and Amogh wrote: "I'm going to release it today." The poll closed in favour, GitHub organisation memberships were removed except for the developer role, and he posted "Making the repo public now!" at 23:08 UTC and "Done!" at 23:23 UTC (already 2026-07-15 in Europe and Asia). On 2026-07-15 lorfidel argued that Russian members, unlikely to face legal action, could carry the risk; Amogh replied that he lives in the US, "a prime spot for NVIDIA being able to pursue legal action", Thanos offered to publish code under his own GitHub account, and Humvee55 suggested moving to another server. At 17:15 UTC that day Amogh decided to keep this server "as a trusted discussion space no longer associated with cmpunlocker"; the separation ended when he reopened the Dev role on 2026-07-19. None of this is legal advice.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-13
Source: @_j3ns, 2026-07-14
Source: @_j3ns, 2026-07-14
Source: @petrikrohn_26497, 2026-07-14
Source: @mrpec, 2026-07-14
Source: @icematty, 2026-07-14
Source: @lorfidel, 2026-07-15
Source: @scallion_9883, 2026-07-15
Source: @_j3ns, 2026-07-15
Source: @thanos8912, 2026-07-15
Source: @_j3ns, 2026-07-15
Source: @jiacheng_liu, 2026-07-15

The repository's history starts at 04:47 UTC on 2026-07-15

The first commit in cmpunlocker's public history on GitHub ("Initial commit", 9b9fb2f) is dated 04:47 UTC on 2026-07-15, about five and a half hours after the "Making the repo public now" post above. Neither the posts nor the repository say whether the history was re-created after the first public push.

Reported
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub

A compute-only shell script on GitHub, deleted soon after (2026-07-14, research wiki)

According to the Consensus-Protocol research wiki, which its author calls unverified, a compute-only shell script, CMP170HX_Compute_Unlock_v8_3.sh, was pushed to a public GitHub repository on 2026-07-14 and deleted soon after. Its author described it as the compute logic the developers already shared, adapted for several cards; it did nothing for memory. The research wiki names neither the repository nor the author, and no message in this server's export mentions the file.

Reported
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

Memory unlock not yet working; "compute survives FLR, memory does not" (2026-07-13 to 07-15)

On 2026-07-13 Amogh said "I haven't seen anybody get a fully working memory unlock yet", and on 2026-07-15, about an hour after the repository went public, he confirmed to a user that the memory unlock was not functional yet. On 2026-07-14, asked by Amogh what still stood between the working compute unlock and more VRAM plus PCIe Gen2, Petri Krohn answered "Compute survives FLR, memory does not." The same day Petri said "Only 40GB is guaranteed to work on the 10GB card with Samsung stacks", the earliest statement in the server of 40 GB as the 10 GB card's safe ceiling. By 2026-07-19 owners were running 8 GB cards at 64 GB and 10 GB cards at 40 GB (below). First posted on the clean room server on 2026-07-12 by @bigptoughneigh: compute unlocks are "super sticky", but he had not got the memory setting to survive a driver reload, and the memory unlock worked "only at the hardware level so far". On 2026-07-14 he called the unlock completely reversible, and @serplay228 wrote that changes persist only through an FLR or a driver reload and that a power off undoes the unlock.

Reported 8 GB and 10 GB
Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-12 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-13
Source: @_j3ns, 2026-07-13
Source: @serplay228, 2026-07-13
Source: @_j3ns, 2026-07-14
Source: @petrikrohn_26497, 2026-07-14
Source: @farawaythrower, 2026-07-14
Source: @petrikrohn_26497, 2026-07-14
Source: @bigptoughneigh, 2026-07-14 (CMP 170hx Clean Room Discussion server)
Source: @serplay228, 2026-07-14 (CMP 170hx Clean Room Discussion server)
Source: @airj2544, 2026-07-15
Source: @_j3ns, 2026-07-15

First reboot-persistent compute unlock (2026-07-16)

Amogh on 2026-07-16: "In other good news, I got a compute unlock fully working that persists properly." Rubbra_F checked that this meant across reboots, and Mr Pec asked whether a daemon reapplied it; Amogh said it works across reboots and is meant for servers, because a desktop GUI can act oddly. Nothing is written to the card: the unlock is driver-side and volatile, and it reapplies at every driver load.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-16
Source: @rubbra_f, 2026-07-16
Source: @mrpec, 2026-07-16
Source: @_j3ns, 2026-07-16

A fork taken down on 2026-07-17 (research wiki)

According to the Consensus-Protocol research wiki, which its author calls unverified, at least one public cmpunlocker fork was taken offline on 2026-07-17 by a DMCA takedown notice that its owner said came from NVIDIA, and he stopped working on it in public. Others thought it could be automated enforcement, noted that many forks already existed, and advised renaming and rewriting forks. Nobody has published the notice, the research wiki names neither the fork nor its owner, and no post in this server's export mentions a takedown on that date. None of this is legal advice. First posted on the clean room server on 2026-07-17 by @_j3ns (Amogh), about his own repository. At 00:10 UTC he wrote that he had "a bad feeling that all the cmpunlocker forks might be DMCA'd", that this was why his repository was down, that he got his notice "from NVIDIA themselves" and could no longer do public work on it, and that forks should be renamed and rewritten in Rust. @scallion_9883 noted there were already many forks, @icematty thought it was probably automated, and @bigptoughneigh said he had reached out to Louis' nonprofit (FUTO, as he recalled the name). On 2026-07-18 Amogh made his repository public, and asked by @ju5t5omedude whether the story was real he answered: "Maybe, maybe not. It was a guess, but definitely not an educated guess." The posts do not make clear whether the guess was the notice or the prediction about forks; no notice was posted.

Reported
Source: @_j3ns, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @scallion_9883, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @icematty, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-17 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @ju5t5omedude, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

Two lineages: Jon Pry's proof of concept and the driverless Clean Room unlocker

Petri Krohn's summary of 2026-08-11 describes two largely independent unlockers. Jon Pry's proof of concept was intentionally never published and relies heavily on modifying the Linux driver. The Clean Room unlocker is a Python script run before loading the unmodified driver; it was published first and could not unlock memory at the start. On 2026-07-24 Petri announced that the clean room had a memory unlocker that works with stock drivers, which matters where patched drivers cannot load (Secure Boot, code-integrity policies); Rubbra_F still could not get it working on 2026-08-04. Per Petri, after the leak Amogh replaced his hosted version with the Chinese one, and the driverless unlocker was largely abandoned as work moved to PCIe Gen2 and Gen4; Humvee55 called the "chinese unlock" "literally just our POC". The driverless unlocker's public repository is d3dx9/cmpunlocker (last commit 2026-07-18); Amogh posted it on 2026-07-19 to debunk a PCIe Gen4 claim made for it, and it did nothing on his eGPU. Earlier posts on the clean room server, in the order posted:

  • 2026-07-15: @liuwake linked a second clean-room repository, arabel1a/cmpunlocker, and @petrikrohn_26497 welcomed that it had no version history. @ju5t5omedude got stuck at step 6 of 7 and @airj2544 had the same problem with the public release the day before; @beefbonecapone said it left his PC unable to boot and thought the offsets were wrong for the 10 GB card. The posts do not say which release he ran, and no fix was posted. Source: @liuwake, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @airj2544, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @beefbonecapone, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @beefbonecapone, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-07-15 (CMP 170hx Clean Room Discussion server)
    Source: @airj2544, 2026-07-15 (CMP 170hx Clean Room Discussion server)
  • 2026-07-18: @.d3dx9 found kinako404/cmpunlocker, then 4 days old, and @petrikrohn_26497 answered: "The cmpunlocker shared on Github is the one developed here in the clean room. It unlocks compute, but does not unlock memory." Source: @.d3dx9, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-18 (CMP 170hx Clean Room Discussion server)
  • 2026-07-22: @bigptoughneigh said version 2 of his script gave 40 GB with the driver and CUDA working and no driver modifications, the change being in the script and not the driver, and that "the monolithic code here seems to work for 40GB on a completely stock driver"; he asked others to test it on stock open modules. This is two days before the 2026-07-24 announcement above. Source: @bigptoughneigh, 2026-07-22 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-22 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-22 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-22 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-22 (CMP 170hx Clean Room Discussion server)
  • 2026-07-23: @bigptoughneigh: "The script is the whole thing. There's no driver mods so no installer." As he remembered it, the memory script does not unlock compute and needs no FLR; @petrikrohn_26497 gave the run order: the original compute-only scripts with their FLR reset first, then the memory script. Source: @bigptoughneigh, 2026-07-23 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-23 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-23 (CMP 170hx Clean Room Discussion server)
  • 2026-07-26: @petrikrohn_26497 said the unlocker is completely independent of drivers: run a Python script, then use any driver, "Open-source, closed-source, Nouveau, Nova, even Windows". No Windows run was shown. Source: @hamuki, 2026-07-26 (CMP 170hx Clean Room Discussion server)
    Source: @petrikrohn_26497, 2026-07-26 (CMP 170hx Clean Room Discussion server)

Reported 8 GB and 10 GB
Source: @petrikrohn_26497, 2026-07-24
Source: @rubbra_f, 2026-08-04
Source: @petrikrohn_26497, 2026-08-11
Source: @scallion_9883, 2026-08-11
Source: @_studebaker_, 2026-08-11
Source: repo github.com/d3dx9/cmpunlocker by d3dx9 on GitHub

The driverless line continues: refire_chain_v6.py (2026-07-24, research wiki)

According to the Consensus-Protocol research wiki, which its author calls unverified, the driverless line continued as refire_chain_v6.py, released on 2026-07-24 out of band (as a gist and channel attachments, not a repository), with switches for compute, memory (40 or 80 GB), PCIe Gen2, link retraining, or all of them, run with the driver unloaded and the card reset. It was built from data captured on a 10 GB card, so it cannot be used unchanged on an 8 GB card, and nobody had made an 8 GB version; the research wiki calls it experimental and not for production use. In this server clee asked on 2026-08-06 where to learn about the "driverless refire chain", and Thanos answered that it came from another Discord server. First posted on the clean room server on 2026-07-24 by @bigptoughneigh, as a channel attachment ("the version with pcie"): he had added the PCIe registers from Amogh's GitHub to the refire chain and moved the compute, PCIe and memory steps a few times to get everything to land at once, and said "This script only has the WPRmeta for 10GB cards, not 8GB though".

Reported 10 GB
Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub
Source: @c133, 2026-08-06
Source: @thanos8912, 2026-08-06

Public on Reddit (2026-07-16), a Bilibili video and a livestream

SkirtChaser dates the public Reddit post of the memory unlock to 2026-07-16; ant said commenters on r/LocalLLaMA were skeptical, and Arcanum that LocalLLaMA first thought it was bogus. meatsus bought a card the day before "someone released the unlock", after which prices tripled. On 2026-07-16 Petri Krohn shared a Chinese Bilibili video (BV1PGNq6tEhr) showing an OpenCL test with the compute unlock; meatsus judged it an overview with no memory unlock shown. A "170hx AI Server Build LIVESTREAM" went up on YouTube around 2026-07-18 (gym). SkirtChaser and quark2world said crypto miners had found the unlock before the AI scene did. Coverage list: Press and coverage. First posted on the clean room server on 2026-07-16 by @serplay228, who linked the r/LocalLLaMA post "PSA: Nvidia's CMP 170HX Full Compute and Memory(80GB) may be unlock..." (title cut off in the post) at 07:18 UTC. @petrikrohn_26497 wrote a long comment under it, said others might not be able to see it, and copied it to NVIDIA-patcher issue #73. That evening @dalzyyy wrote "I made the post... I only did it because the China sellers found out and all the prices already rose lol": more awareness meant more people working on it and a better chance of it being verified, and he expected the memory unlock to take about a week to a month.

Reported
Source: @serplay228, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @dalzyyy, 2026-07-16 (CMP 170hx Clean Room Discussion server)
Source: @petrikrohn_26497, 2026-07-16
Source: @meatsus, 2026-07-17
Source: @cute_sc2, 2026-07-19
Source: @jimtjames, 2026-07-19
Source: @an_1248, 2026-07-19
Source: @meatsus, 2026-07-19
Source: @_arcanum_, 2026-07-20
Source: @quark2world, 2026-07-20
Source: @skirtchaser, 2026-07-20

HPC's Telegram claims and the modified 610-driver release (2026-07-16 to 07-18)

A Russian Telegram announcement group run around a person called "HPC" (about 4k observers, per Amogh) claimed and then posted an unlock. In the order posted:

  • 2026-07-16: HPC's author claimed contact with "the developers", promised open source within days or weeks and posted a redacted screenshot; meatsus read its 64 GB as a system-RAM readout, and MrLoki89 thought it more likely fake. Source: @lorfidel, 2026-07-16
    Source: @meatsus, 2026-07-16
    Source: @serplay228, 2026-07-16
  • 2026-07-17: the group claimed the full unlock had been ready for two weeks, sold cards in lots of 10 at 38.5k rubles (about 500 USD) each, and said the unlock would come out the next day; meatsus was openly skeptical. Source: @lorfidel, 2026-07-17
    Source: @meatsus, 2026-07-17
  • 2026-07-18: HPC posted an unlock based on a modified NVIDIA 610-series driver, from developers known only to be in China. Thanos was unsure whether it was "clean"; lorfidel argued personal use carries no risk; meatsus urged everyone to stay away ("its proven that it can be unlocked without anything illegally leaked") and Amogh preferred to stay away, saying he was close to an actually clean unlock. Thanos: "We got beaten though". Source: @lorfidel, 2026-07-18
    Source: @thanos8912, 2026-07-18
    Source: @meatsus, 2026-07-18
    Source: @_j3ns, 2026-07-18

Contested

The "Chinese unlock": the original group's leaked proof of concept, or a fake

In the order posted:

  • 2026-07-22: Jack reported that the circulating Chinese unlocker works on 8 GB cards but does not recognise the 10 GB card. lxwx checked it and found it writes the PLM table exactly as Amogh's cmpunlocker does, so it unlocks no extra features and no Gen2. Source: @ludashi666, 2026-07-22
    Source: @lxtend, 2026-07-22
    Source: @lxtend, 2026-07-22
  • 2026-07-22: Petri Krohn identified it as the leaked proof of concept: patched 610 open drivers plus a compiled kernel module. His account says it appeared on Russian Telegram channels about three days after the clean room's release, first as a 520 MB zip, and that its 30 kB diff against the stock sources matched the group's driver modification guides word for word. Source: @petrikrohn_26497, 2026-07-22
  • 2026-07-22: aidoc called the "chinese leaked unlock" a fake: a few Goofish sellers faking success on hacking the chip, with no progress on PCIe speed, only pushing prices up. This may refer to the sellers' further claims rather than the leaked driver itself. giaki3003 added that sellers marketed the card as an AI revolution hoping for A100 pricing. Source: @sekkit_75019, 2026-07-22
    Source: @giaki3003, 2026-07-22
  • 2026-07-22: asked by Eksitus, Humvee55 stated that the "chinese" unlock was word for word the original group's proof of concept and that the stolen POC was all the leakers ever had. Source: @eksitus, 2026-07-22
    Source: @scallion_9883, 2026-07-22
  • 2026-07-27: ju5t5omedude remarked that the team "could not even" keep the "dirty unlock" from leaking. Source: @ju5t5omedude, 2026-07-27

Contested

Supplier prices explode on 2026-07-19; who started the hype

quark2world ordered on 2026-07-17, "at the start of the craziness". CUTE paid for 16 cards at 480 USD each just before supplier prices exploded early on Sunday 2026-07-19 (GMT+2), and Sojun said everyone who ordered that weekend got the run-around. Arcanum noted that cards had vanished from Taobao by 2026-07-17, so Chinese sellers already knew. CUTE said on 2026-07-22 that the unlock "was clear before that too, but not widely known" and that Red Panda Mining made it popular; quark2world credited Amogh with finding the unlock and called it "the 56gb hbm that was lost for 3years". Hackaday published "Industrial GPU Adapted For The Desktop" on 2026-07-22, asking prices moved toward 1,300 to 1,500 USD, and Studebaker asked members to keep things low-key. Dated prices: Price history, July to October 2026.

Reported
Source: @quark2world, 2026-07-20
Source: @cute_sc2, 2026-07-21
Source: @sojun80, 2026-07-21
Source: @_arcanum_, 2026-07-22
Source: @roger_dammit, 2026-07-23
Source: @cute_sc2, 2026-07-23
Source: @_studebaker_, 2026-07-23

The in-driver memory unlock lands on master (2026-07-18)

cmpunlocker's commit history dates the memory unlock to the evening of 2026-07-18 (UTC): "WORKING MEMORY UNLOCK" on the memory branch at 19:11, "FULL WORKING THING" at 20:51, and the merge to master at 21:46. The merge replaced the earlier Python tooling with patches built into the driver, and the same evening the repository's lint and test workflows were deleted. The result is the July baseline of the next entry: 8 GB cards to 64 GB and 10 GB cards to 40 GB. First posted on the clean room server on 2026-07-18 by @_j3ns (Amogh), who linked the repository there at 21:46 UTC, the minute of the merge; asked by @vrownie.diamond whether it worked, he answered "Yup. Even I'm surprised too." Asked by @hamuki that evening how much of the work used AI, @scallion_9883 answered "All of it" and Amogh confirmed it: he used Claude through Anthropic's Cybersecurity Verification Program, in rotation, with "Haiku for random refactors", Sonnet for the coding and "Opus for the actual design".

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @vrownie.diamond, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @hamuki, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @scallion_9883, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub

The July stability baseline: 8 GB to 64 GB, 10 GB to 40 GB (2026-07-19 and 20)

On 2026-07-19 Amogh told testers to use master first ("Multi-GPU was something experimental I wanted to try out"); the 80 branch held the 10 GB to 80 GB path, and the recovery workflow was sudo ./remove.sh --yes, reboot, then repatch. Asked by CUTE whether the 64 GB cards show HBM errors, Amogh answered "Nope, none at all." Far's cuda_memtest on a 10 GB card with the 80 GB profile ran when allocating 39 GB and failed at 40 GB or more, while "40GB has worked perfectly stable". Luna summed it up on 2026-07-20: 80 and 96 GB "cause errors and/or no POST at the moment", and "Right now it's safe to say 8 -> 64 and 10 -> 40." Finishtilt14 confirmed master on six cards on 2026-07-22. The 10 GB card after this: The 10 GB card: provenance and the 80 GB question.

Reported 8 GB and 10 GB
Source: @cute_sc2, 2026-07-19
Source: @_j3ns, 2026-07-19
Source: @farawaythrower, 2026-07-19
Source: @coolgod_72592, 2026-07-19
Source: @_j3ns, 2026-07-19
Source: @finishtilt14, 2026-07-19
Source: @_j3ns, 2026-07-19
Source: @farawaythrower, 2026-07-20
Source: @lunaroseoc, 2026-07-20
Source: @eksitus, 2026-07-20
Source: @finishtilt14, 2026-07-22

The Dev role reopened and forks invited (2026-07-19)

On the evening of 2026-07-19 Amogh invited everyone to fork the repository and change it, and reopened the Dev role ("You know what, I'll re-open up the Dev role again."). From here the project took outside developers such as Humvee55 and AKuchen, who were doing independent register work.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-19

Feature polls: PCIe wins (2026-07-19 and 20)

Amogh polled members on which features to unlock next. When the polls closed on 2026-07-20 he said: "Well, I guess PCIe takes the strong win." The Gen2 unlock followed four days later.

Reported
Source: @_j3ns, 2026-07-19

A driver-port branch for 595, 590 and 580 (2026-07-21)

On 2026-07-21 Amogh created the branch clanker/driver-port for "(hopefully working) driver support of 595, 590 and 580", after a poll on porting cmpunlocker to 580. On 2026-08-07 he said "The exploit only works for 580 and newer", so drivers such as 515 cannot be unlocked with it.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-21
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @_j3ns, 2026-07-21
Source: @_j3ns, 2026-08-07

MIG enabled with one register (2026-07-22)

jonathan.quai enabled Multi-Instance GPU (MIG) on an unlocked 8 GB card by setting one register; nvidia-smi then reported MIG mode Enabled. Only one profile existed (1g.64gb, 63 GB, 70 SM), so it was not yet useful, and Amogh offered to merge a reasonable PR. The MIG patch was validated in September (below).

Reported 8 GB
Source: @jonathan.quai, 2026-07-22
Source: @_j3ns, 2026-07-22
Source: @samuel_hayden., 2026-07-23

Gen2 before the release: from "nobody has it" to a branch that would not retrain (2026-07-18 to 07-23)

On 2026-07-18 the memory unlock worked but cards still ran PCIe 1.0 x4; Amogh confirmed nobody had reached Gen2 and made it his next target. On 2026-07-21 Humvee55 hinted at "a merge request in the near future with pcie2 and some mem and compute OC work", and on 2026-07-22 he said Gen2 can be reached "with the correct register writes", while Gen3 and Gen4 sit behind a hardware mask; the same day he said the original proof of concept had reached Gen2 and would "probably" be merged eventually. At 05:32 UTC on 2026-07-23 Amogh pushed a Gen2 branch that made the card advertise Gen2 but failed to retrain the link; ProfDD and Newman reproduced the failure, and Samuel Hayden suspected fuses gating link training. The first attempts came earlier, on the clean room server: on 2026-07-12 @beefbonecapone reported that under QEMU with VFIO, register values that exposed Gen2 behaviour eventually wedged the passed-through function, while the stable value left the link at Gen1 x4.

Reported 8 GB and 10 GB
Source: @beefbonecapone, 2026-07-12 (CMP 170hx Clean Room Discussion server)
Source: @farawaythrower, 2026-07-18
Source: @_j3ns, 2026-07-18
Source: @_j3ns, 2026-07-19
Source: @impactic, 2026-07-20
Source: @eksitus, 2026-07-22
Source: @scallion_9883, 2026-07-21
Source: @scallion_9883, 2026-07-22
Source: @akuchen_66498, 2026-07-22
Source: @_j3ns, 2026-07-22
Source: @_j3ns, 2026-07-22
Source: @profdd, 2026-07-23
Source: @samuel_hayden., 2026-07-23
Source: @newman_08462, 2026-07-23

Is selling unlocked compute legal? A debate (2026-07-24)

On 2026-07-24, on the CMP 170hx Clean Room Discussion server, a question about a fair price turned into a debate on whether selling compute from unlocked cards is legal. In the order posted:

  • @skirtchaser: a fully unlocked card (PCIe 4.0 and NVLink working) would price near an AMD MI210. Even a provably clean unlock should still be against the law in the EU and US (he quoted 17 U.S.C. 1201(a)(1)(A)), so selling the compute at scale could bring legal action, with statutory damages per card. He pointed to Nintendo of America v. Team-Xecuter and the WoW Glider bot, where a clean-room implementation did not help, and added "I don't think NVIDIA would go after people using this in their own home". Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @skirtchaser, 2026-07-24 (CMP 170hx Clean Room Discussion server)
  • @ju5t5omedude: the HDCP analogy does not fit, because that protection exists for digital content; he pointed to the John Deere case: "It's about standing". Source: @ju5t5omedude, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @ju5t5omedude, 2026-07-24 (CMP 170hx Clean Room Discussion server)
  • @bigptoughneigh: the unlock is software, not sold with the cards or stored on them, and it needs NVIDIA's own open-source drivers on "GPUs we own"; selling cloud access to a jailbroken console would not be legal either. Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)
    Source: @bigptoughneigh, 2026-07-24 (CMP 170hx Clean Room Discussion server)

Nothing was settled. None of this is legal advice.

Contested

PCIe Gen2 works (2026-07-24)

At 00:59 UTC on 2026-07-24 Amogh announced the PCIe Gen2 unlock ("PCIe Gen 2 baby!"; "Phase 1 is out of the way") and pushed cleaned code to the Gen2 branch at 01:23 UTC. He had soldered all 24 lane capacitors, but his eGPU dock limited him to x4. Asked how he found it, he said "I did a lot of tracking on the behavior of the registers that needed to change and just tried permutations of applying them", automating the experiments with an AI coding agent that drove his test machine and rebooted it as needed. Early results were mixed ("Day Zero issues"), so he opened a support ticket channel. cmpunlocker raises the link speed; the capacitor mod raises the lane count (PCIe x16 capacitor mod).

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-07-24
Source: @_j3ns, 2026-07-24
Source: @samuel_hayden., 2026-07-24
Source: @thanos8912, 2026-07-24
Source: @diabeetee, 2026-07-24
Source: @icematty, 2026-07-24
Source: @_j3ns, 2026-07-25

No single person made Gen2 work for everyone. The next four entries give each contribution with its date; the branch history is on Gen2 link retrain.

Newman's multi-card retrain in the driver (patch 0008), merged 2026-07-24 and 25

Newman found that the first retrain script, run at OS startup, retrained only the first card and, by retraining while the driver was using the card, caused random crashes. He moved the retrain into the driver loading phase (new patch 0008) in his fork, bendy2/cmpunlocker. GMZombie007 (two cards) and Eksitus (three 10 GB cards) confirmed it, and it worked on Amogh's machine. Amogh merged it into the Gen2 branch and said on 2026-07-25 that the Gen2 patch is "Newman's fork that properly trains for PCIe Gen 2".

Reported 8 GB and 10 GB
Source: @newman_08462, 2026-07-24
Source: @newman_08462, 2026-07-24
Source: @gmzombie, 2026-07-24
Source: @eksitus, 2026-07-24
Source: repo github.com/bendy2/cmpunlocker by bendy2 on GitHub, posted by @newman_08462, 2026-07-24
Source: @_j3ns, 2026-07-25

The retrain inside the driver upstream: PR #18 (bendy2)

bendy2 worked out the retrain and moved it into the driver by mapping BAR0 there, which fixed the mmap failure that had blocked userspace attempts; it was merged upstream as cmpunlocker PR #18. A reproduction posted by aaasss on 2026-07-29 showed that the link trains to Gen2 only when the GPU's own root port starts the retrain.

Reported 8 GB
Source: @aaasss1456, 2026-07-29
Source: @dino_38975, 2026-08-25
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub

Huzifei's early-boot retry, PR #24 (2026-07-28)

Huzifei found that patch 0007 exposes the Gen2 capability only briefly during GSP initialisation and that the existing retrain ran too late. His early-boot service retries link training every 50 ms until it catches that window (PR #24; fork SuperHuzifei/cmpunlocker-amogh). On his 10 GB card the link went from Gen1 x4 to Gen2 x4 and host-to-device bandwidth from about 0.82 to 1.63 GB/s, with the 40 GB unlock intact. On 2026-07-29 SealClubber called the 50 ms script the latest approach that "works" for most people.

Reported 10 GB
Source: @huzifei, 2026-07-28
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @huzifei, 2026-07-28
Source: repo github.com/SuperHuzifei/cmpunlocker-amogh by SuperHuzifei on GitHub, posted by @huzifei, 2026-07-28
Source: @_studebaker_, 2026-07-29
Source: @sealclubber, 2026-07-29
Source: @huzifei, 2026-07-29

v0.2 ships Studebaker's Gen2 fix (2026-07-29)

Amogh announced cmpunlocker v0.2 at 17:40 UTC on 2026-07-29 (release) and confirmed to Studebaker that he had folded in Studebaker's Gen2 fix: "I added your fix inside, it works wonders!" ju5t5omedude, who had stayed at Gen1 on every branch, got Gen2 with v0.2 ("Yesterday's v0.2 is the only thing that worked for my gen2 unlock"). DeeJay got 65,536 MiB and Gen2 x4 on two cards with v0.2, although both were held in HW Power Brake Slowdown on his host.

Reported 8 GB and 10 GB
Source: @ju5t5omedude, 2026-07-29
Source: @_studebaker_, 2026-07-29
Source: @_j3ns, 2026-07-29
Source: @_j3ns, 2026-07-29
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @_j3ns, 2026-07-29
Source: @deejay9983, 2026-07-30

Forks and PRs in late July; a curated forks room

Around 2026-07-24 the active code lines were amoghmunikote/cmpunlocker (master, Gen2, debug-gen2), Newman's bendy2/cmpunlocker, asm64-hooligan/cmpunlocker with a memory overclock, and ee's PR with changes to make it work on his system; Amogh preferred Newman's approach to ee's overlapping PR. CUTE asked for a curated room listing the important forks, and Amogh agreed. bigfoot pointed out that the repository is open source and can be read before running it. Today's list: cmpunlocker forks.

Reported
Source: @ju5t5omedude, 2026-07-24
Source: @bigfoot1144, 2026-07-24
Source: @e_e_j, 2026-07-24
Source: @_j3ns, 2026-07-24
Source: @cute_sc2, 2026-07-25

P2P between 170HX cards (2026-07-29 and 30)

At 23:51 UTC on 2026-07-29 LimitlessTales announced P2P working on the CMP 170HX under Linux. On 2026-07-30 DeeJay had two fresh cards booting straight into Gen2, 64 GB and P2P (P2P True in both directions) with cmpunlocker v0.2 plus aikitoria's P2P patch, and Amogh announced a P2P branch of cmpunlocker; Samuel Hayden clarified that it is PCIe P2P, not the fused-off NVLink, so the Gen2 link limits it. The first fork with real data moving between four cards came on 2026-08-08 (below). Current state: P2P.

Reported
Source: @_j3ns, 2026-07-28
Source: @ju5t5omedude, 2026-07-28
Source: @limitlesstales, 2026-07-29
Source: @deejay9983, 2026-07-30
Source: @_j3ns, 2026-07-30
Source: @poningru, 2026-07-30
Source: @samuel_hayden., 2026-07-30
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @_j3ns, 2026-07-30

August 2026

Software JTAG published (2026-08-04)

At 20:26 UTC on 2026-08-04 Amogh announced that software JTAG works and published it on the JTAG branch of cmpunlocker. Whether it was useful was unknown; members hoped it could lead to custom VBIOS work or more memory. In September mrpandagod claimed the branch held leak-derived code and said Amogh had removed it (see the dispute in September).

Reported
Source: @_j3ns, 2026-08-04
Source: @djpandaman, 2026-09-29

Amogh: "I'm not the original author" (2026-08-05)

Asked by Bart whether "the original paper author" had stocked up on cards before publishing, Amogh said: "I'm not the original author, I have no clue as to whether that happened or not." He described himself as the developer trying to accommodate everyone, with PCIe Gen3 first and the 80 GB unlock after. quark2world had credited Amogh with finding the unlock on 2026-07-22; this answer and Petri Krohn's account point to Jon Pry and the private group for the original exploit.

Reported
Source: @quark2world, 2026-07-22
Source: @_j3ns, 2026-08-05
Source: @justbendev, 2026-08-05

BAR1 unlock: asm64's fork, merged upstream with credit (2026-08-06 to 08-13)

asm64 published a cmpunlocker fork (asm64-hooligan/cmpunlocker) adding a BAR1 unlock around 2026-08-06; Amogh asked to use it upstream and asm64 agreed on condition of credit. After testers showed "BAR 1: current size: 64GB" (fallengod9962, Studebaker), Amogh confirmed that BAR1 works, merged the 64 GB BAR1 branch to master on 2026-08-13 and credited asm64. intervitens measured little change for single-stream decode and about 10 to 20% better prefill and batched parallel work on two cards; turbine called it fairly low risk on an enterprise motherboard. Details: Resizable BAR and BAR1 64 GB.

Reported
Source: @leesle., 2026-08-06
Source: @_j3ns, 2026-08-07
Source: @turbine, 2026-08-12
Source: @intervitens, 2026-08-12
Source: @_j3ns, 2026-08-13
Source: @fallengod9962, 2026-08-13
Source: @_studebaker_, 2026-08-13

First working P2P: bayley's fork (2026-08-08), then P2P without kernel patches (2026-08-13)

Capone said on 2026-08-06 that he had P2P working, but on 2026-08-07 bayley_w wrote that no public repository had tested-working P2P yet. On 2026-08-08 he published bayley/cmpunlocker, assembled from upstream branches after "several broken sets of p2p patches", with real bytes moving P2P across four GPUs on a Supermicro SYS-4028GR-TRT2; it needed kernel patches for reliable 64 GB BAR1s on that platform. On 2026-08-13 turbine got P2P on four GPUs without kernel patches by combining bayley_w's "force bar1 p2p" driver patches with upstream's BAR1 resize: GPU-to-GPU latency fell from 13.88 to 23.28 us to 1.79 to 1.87 us, which he called a 10x reduction, and bidirectional bandwidth rose from about 8.5 to about 13 GB/s.

Reported
Source: @beefbonecapone, 2026-08-06
Source: @bayley_w, 2026-08-07
Source: @bayley_w, 2026-08-07
Source: @bayley_w, 2026-08-08
Source: repo github.com/bayley/cmpunlocker by bayley on GitHub, posted by @bayley_w, 2026-08-08
Source: @turbine, 2026-08-13

The reserved-region bug and the late-PMA fix (2026-08-06 to 08-30)

On 2026-08-06 bayley_w and Fats found that the unlock exposed a region of about 141 MB at the top of VRAM that should stay reserved; bayley traced it to the "late PMA extension", present in both Amogh's and asm64's code. Writes into that region raise Xid 31, which explained 64 GB cards crashing when cuda_memtest ran over all memory more than once, and vLLM failing during weight loads (Far, 2026-08-10). On 2026-08-11 bayley_w told members to apply the late-PMA fix (cmpunlocker PR #32, late-pma branch) or expect guaranteed Xid 31 errors; bassRAWR and Phoenix17 confirmed it was needed (2026-08-26), and romangitz's patched 10 GB card ran rock solid (2026-09-02). Amogh shipped the fix in v0.3 on 2026-08-30 (release): "I know a lot of you guys had issues with the memory, so I implemented the Late PMA fix per popular request". Miséricorde's analysis of 2026-09-18 places the region over memory the firmware protects. Full story: Xid 31 and the reserved top of VRAM.

Reported 8 GB and 10 GB
Source: @bayley_w, 2026-08-06
Source: @c.03937, 2026-08-06
Source: @farawaythrower, 2026-08-10
Source: @bayley_w, 2026-08-11
Source: @bassrawr, 2026-08-26
Source: @_j3ns, 2026-08-30
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @_j3ns, 2026-08-30
Source: @romangitz, 2026-09-02
Source: @cmdrwaka324, 2026-09-02
Source: @wakeupmbrc1, 2026-09-18

Custom VBIOS: announced (2026-08-07), kept private, dropped (2026-08-23)

On 2026-08-07 Amogh announced he was building a custom VBIOS ("Don't get your hopes up"), which might give 80 GB, ECC or NVLink but not Gen3. On 2026-08-10 he said he could in theory port everything from cmpunlocker into a VBIOS, mainly to reach 80 GB, and that he would release the modded VBIOS but not how he re-signs it, because of the legal risk; Humvee55 answered "nah" when Mello Jello asked whether the signing ability came from leaked material. On 2026-08-20 Amogh pinned the warning: releasing the re-signing steps "poses an absolutely huge legal threat", and anyone else who works them out should weigh that risk. On 2026-08-23 he dropped the VBIOS route because "the ES doesn't provide anything for me to re-sign the VBIOS" and turned to fuse burning for Gen3, which nobody had yet tried on a card. No VBIOS was released. Background: VBIOS and firmware.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-08-07
Source: @ju5t5omedude, 2026-08-07
Source: @sealclubber, 2026-08-07
Source: @_j3ns, 2026-08-10
Source: @cuddylac997, 2026-08-10
Source: @cmdrwaka324, 2026-08-10
Source: @xeax, 2026-08-10
Source: @isah1221, 2026-08-10
Source: @mellojello_, 2026-08-10
Source: @scallion_9883, 2026-08-10
Source: @makesier, 2026-08-10
Source: @_j3ns, 2026-08-20
Source: @_j3ns, 2026-08-23
Source: @programmerboi, 2026-08-23

80 GB on the 10 GB card: clean-room reports and the GSP crash (August and September)

On 2026-08-09 Rubbra_F said someone had got 80 GB on the 10 GB card in the clean-room server, a separate Discord; ju5t5omedude said similar work had been done there about a month earlier, and DaLZy named the clean-room server and Pidan Xiong as two independent confirmations. Those posts cannot be checked from this server's history. On 2026-09-19 MaitOPS said Jon Pry was the first to find the 80 GB of HBM on the 10 GB card; Cudylac's gist ties the crash to the GSP firmware, and it hits the same point on several cards. Where 80 GB stands: The 10 GB card: provenance and the 80 GB question and Memory unlock on the 10 GB card.

Reported 10 GB
Source: @rubbra_f, 2026-08-09
Source: @dalzyyy, 2026-08-09
Source: @ju5t5omedude, 2026-08-09
Source: @_maitops, 2026-09-19

Amogh's break for tinygrad (2026-08-15 to 08-19)

On 2026-08-15 Amogh paused cmpunlocker for a few days to get NVIDIA support into tinygrad for openpilot's eGPU system. He came back on 2026-08-19 "after getting nothing merged into tinygrad" (his PRs were judged too big) and continued on the 170HX. He owns a single 170HX on an eGPU dock and invited Dimon to open a PR for Proxmox support.

Reported
Source: @_j3ns, 2026-08-15
Source: @_j3ns, 2026-08-19

Tom's Hardware's first article and the August price surge (2026-08-18)

Tom's Hardware published the article on 2026-08-18, when members first discussed its 250 USD figure (see Price history and market); on 2026-08-19 artistosu shared Tom's Hardware's article on the software unlock giving 64 GB of VRAM on a "$250" CMP 170HX. DaLZy said it was about a month late, since cards already cost about 500 USD when he had posted about it on r/LocalLLaMA; dalzyyy mocked the comment threads. bayley_w blamed the price surge of 2026-08-20 and 21 on the article, and Schaka described the usual pattern: tech media pick up support for old hardware and prices explode. A second Tom's Hardware article followed in October (below). Prices: Price history, July to October 2026.

Reported 8 GB
Source: @.philow, 2026-08-18
Source: @artistosu, 2026-08-19
Source: @dalzyyy, 2026-08-19
Source: @dalzyyy, 2026-08-19
Source: @bayley_w, 2026-08-21
Source: @schakaqt, 2026-08-21

Hardware ECC done (2026-08-24), then the ECC branch

Humvee55 posted "done for HW ECC" on 2026-08-24, with the code to be shared by another developer. On 2026-09-14 CUTE said ECC already worked for him and needed to be made "pleb friendly" before release: software-only and reversible, costing bandwidth but not capacity. 68x linked cmpunlocker's ECC branch on 2026-09-24, and ECC shipped in v0.5 on 2026-10-04 (below). Whether the shipped ECC corrects errors is a separate question: ECC.

Reported
Source: @scallion_9883, 2026-08-24
Source: @_j3ns, 2026-08-26
Source: @cute_sc2, 2026-09-14
Source: @68x0, 2026-09-24
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @68x0, 2026-09-24

September 2026

PCIe Gen3 announced, then delayed the same day (2026-09-06)

On 2026-09-06 Amogh announced to everyone "We have PCIe Gen 3!" (347 reactions), with caveats ("DON'T GET YOUR HOPES UP!"). He said he found the path through "a lot of Clauding and experimentation" and tested the fuse step on one card of a quad-GPU rig he has access to but does not own. About three hours later he delayed the release because the fuse step could brick cards, gave no date and refunded everyone who had sponsored him that day. In #hardware segmond, reala and cibernox began planning riser, cap-mod and switch upgrades for Gen3.

Reported
Source: @_j3ns, 2026-09-06
Source: @_j3ns, 2026-09-06
Source: @segmond, 2026-09-06
Source: @reala7096, 2026-09-06
Source: @_j3ns, 2026-09-06
Source: @cibernox, 2026-09-06

Hype against reality after the Gen3 announcement

In the order posted, all on 2026-09-06:

  • insomniac and Josh argued that announcements without the risks attached let sellers raise prices, which slows development, and asked for clear statements of what each unlock gives compared with an A100. Josh asked Amogh to put the Gen3 warnings in the announcement, and Amogh did. Josh's "80% chance you brick your card" going to 3.0 x16 is his own estimate, not data from the thread. Source: @ins_mniac, 2026-09-06
    Source: @_____josh_____, 2026-09-06
    Source: @_j3ns, 2026-09-06
  • ST mentioned a Reddit post claiming all cards failed after the mod and called it effective FUD; quark2world said this is why he stopped posting benchmarks. Source: @quark2world, 2026-09-06
    Source: @stcord, 2026-09-06

Contested

VFIO passthrough merged (2026-09-07)

At 04:09 UTC on 2026-09-07 Amogh announced VFIO support (passthrough branch), so the unlock works for Proxmox, KVM and QEMU guests: install on the host, then use the unlocked card in the VM. It was merged to master at 23:03 UTC the same day, and he named vGPU and MIG as next. Setup: Virtual machines and passthrough.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-09-07

Two CMP 100-210 software unlocks on one day (2026-09-08)

Humvee55 (persistent, through nvflash and the InfoROM) and Brazzo97 (a runtime Falcon exploit) announced independent software unlocks for the CMP 100-210 on 2026-09-08. Brazzo said the idea came from cmpunlocker for the 170HX. scallion_9883: "Two completely different routes on the same card on the same day". Other cards: Other CMP cards and other NVIDIA GPUs.

Reported
Source: @brazzo97, 2026-09-08
Source: @roger_dammit, 2026-09-08
Source: @scallion_9883, 2026-09-08

kmike's Gen2 fix, PR #35 (2026-09-11)

kmike had Gen2 failures on his board under Ubuntu 26 and, after hours of debugging, made it work with cmpunlocker PR #35, for rigs where the Gen2 window opens before systemd userspace starts. He believes the Gen2 approach in main misses some cases. The PR was closed as too large, but he suggested others with failing boards try it.

Reported
Source: @kmike84, 2026-09-11

Driver 615 support and v0.4 (2026-09-12 and 13)

On 2026-09-10 the installer still refused driver 615.71.09 and required nvidia-open 610.57.04, 610.43.03 or 610.43.02. Amogh announced v0.4 at 01:50 UTC on 2026-09-13 (release) and said on 2026-09-14: "I added support for 615 a couple of days ago". Supported drivers today: Driver unlock.

Reported 8 GB and 10 GB
Source: @arabus_74064, 2026-09-10
Source: @_j3ns, 2026-09-13
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub, posted by @_j3ns, 2026-09-13
Source: @_j3ns, 2026-09-14

Linus Tech Tips' video (2026-09-12)

Linus Tech Tips published its CMP 170HX video (pvSdeU13hKc) around 17:05 UTC on 2026-09-12: the card unlocked to 64 GB, llama.cpp, the cap mod, a card with memory errors, the PCIe limits and a mention of the Discord. insomniac called it fair and not overhyped. mrpandagod expected 100 to 200 new members that night and asked Amogh to move the Discord link back to the top of the README. On 2026-09-17 Petri Krohn wrote: "The CMP 170HX 64GB has gone mainstream!"

Reported 8 GB
Source: @dalzyyy, 2026-09-12
Source: @ins_mniac, 2026-09-12
Source: @djpandaman, 2026-09-13
Source: @djpandaman, 2026-09-13
Source: @petrikrohn_26497, 2026-09-17

The cmpunlocker author's history file (posted 2026-09-13)

On 2026-09-13 @_j3ns (Amogh) linked docs/HISTORY.md in his cmpunlocker repository on the CMP 170hx Clean Room Discussion server, hoping it would give the history more attention, and said he had made an announcement for people to check it out. It is the author's own account of the project and a primary source for this page.

Reported
Source: @_j3ns, 2026-09-13 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-09-13 (CMP 170hx Clean Room Discussion server)
Source: @_j3ns, 2026-09-13 (CMP 170hx Clean Room Discussion server)
Source: repo github.com/amoghmunikote/cmpunlocker by amoghmunikote on GitHub

MIG patch validated (2026-09-15)

ropuls validated Amogh's mig-unlock.patch on a second card with driver 610.43.03: FP32 SGEMM on the 1g.64gb MIG instance went from 1.85 to 10.2 TFLOP/s (about 5.5x). Only the whole-GPU profile is available, and the patch is a runtime driver patch with no persistent writes to the card. His full report is Consensus-Protocol/cmp170hx PR 3.

Reported 8 GB
Source: @ropuls, 2026-09-15
Source: @humandrone8721_60165, 2026-09-15
Source: repo github.com/Consensus-Protocol/cmp170hx by Consensus-Protocol on GitHub

The 74-SM unlock (2026-09-24)

On 2026-09-24 cmpunlocker gained an SMs branch that re-enables 4 more SMs, taking the card from 70 to 74 SMs (about 6% more compute; Amogh: "equivalent to 2/3 of the NVIDIA T400"). One GPC had an extra 4 SMs disabled, "no clue why" (the lab's read on 2026-11-17: the 4 SMs are TPC 0 of two different GPCs, which GPCs varying by card; see Full SM unlock). JMA1976 confirmed 74 SMs on two GPUs the same day, and others followed within the week. CUTE warned to uninstall the previous unlock before installing a different variant. It shipped in v0.5. Details: Full SM unlock.

Reported 8 GB and 10 GB
Source: @jma1753, 2026-09-24
Source: @_j3ns, 2026-09-24
Source: @cute_sc2, 2026-09-24
Source: @sojun80, 2026-09-25
Source: @c133, 2026-10-02
Source: @darkmaniac7, 2026-11-17 (lab notes)

v0.5 announced, and a turn to hardware (2026-09-26)

On 2026-09-26 Amogh said v0.5 was on the way and would "definitely include some more SMs, and maybe ECC (if I can get that to fully work)", and that cmpunlocker would likely get no new features after it, because "the desirable features like PCIe Gen 3 and NVLink are just not unlockable via software". Asked by n3bs what diverting his attention meant, he replied: "I'm looking at potential ways to burn fuses using hardware." Morrowmake and ST read it as easing off cmpunlocker work. The release itself came on 2026-10-04 (October below).

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-09-26
Source: @n3bs, 2026-09-26
Source: @stcord, 2026-09-26
Source: @voidgiraffe, 2026-09-26

Warning: Gen3 fuse burning cancelled; a card bricked by software alone (2026-09-26)

Warning 8 GB On 2026-09-26 Amogh cancelled the Gen3 release (fusedacmp) because he could not find a reliable way to unlock PCIe Gen3 safely for everyone: card variance he cannot control made some cards unsuitable, a wrong step risks permanent damage, and he bricked one of his own cards with software alone ("you'd be surprised to know what is possible"). Do not try fuse-burning Gen3 methods on the 8 GB card. The 10 GB card's Gen3 route came later: PCIe Gen3 on the 10 GB card.

Source: @_j3ns, 2026-09-26
Source: @_j3ns, 2026-09-26
Source: @_j3ns, 2026-09-26

The RIR finding goes public after an embargo (2026-09-29 to 10-01)

On 2026-09-29 CUTE wrote of having "bragged at Twitter about rir", which set off the 10 GB discussion in #general, and Amogh corroborated it: "I can corroborate that I had full knowledge of RIRs all of this time. This is a very real thing." CUTE said the 48 GB result had been tested in "the dev discord" about a month earlier. mrpandagod said the main unlocking group had split into smaller private chats. On 2026-10-01 Petri Krohn said the RIR information had been under a 30-day embargo: the original work could be announced on 2026-09-30, preferably by its discoverers (he is not one of them), and a follow-up discovery by another member was due on 2026-10-01. What RIR records are: RIR fuse burn and Fuses and floorsweep maps.

Reported 8 GB and 10 GB
Source: @cute_sc2, 2026-09-29
Source: @_j3ns, 2026-09-30
Source: @djpandaman, 2026-10-01
Source: @petrikrohn_26497, 2026-10-01

Dispute over leak-derived material in cmpunlocker's history (2026-09-29)

In the order posted, all on 2026-09-29. None of the commits named in the thread has been checked for this page.

  • mrpandagod argued that cmpunlocker's commit history contains material derived from the LAPSUS$ leak (he named a kernel JTAG bit-banging implementation, commits using internal header and status-code names, and parts of a design document), that Amogh removed the JTAG branch after being told, and that the repository should be rebuilt from before those commits. Source: @djpandaman, 2026-09-29
  • Amogh said using leaked code carries a much bigger risk than not ("There is a way bigger risk than making something that does use leaked code compared to something that doesn't."), asked where such commits were, and later said he had had no legal issues. Source: @_j3ns, 2026-09-29
  • Humvee55 said Amogh took already-public information from the Chinese unlock and improved on it; clee and Humvee55 said mrpandagod had earlier walked back a broader claim, which he denied. Source: @c133, 2026-09-29
    Source: @scallion_9883, 2026-10-01

An earlier instance on the clean room server, 2026-07-18, in the order posted:

  • @beefbonecapone, minutes after Amogh posted his public repository: "this is dirty btw". Source: @beefbonecapone, 2026-07-18 (CMP 170hx Clean Room Discussion server)
  • @_j3ns (Amogh): "Nope, I rebuilt the patch by myself." @beefbonecapone replied that he had removed them (what was removed is not said). Nothing else was posted on it there. Source: @_j3ns, 2026-07-18 (CMP 170hx Clean Room Discussion server)
    Source: @beefbonecapone, 2026-07-18 (CMP 170hx Clean Room Discussion server)

Contested

October 2026

v0.5 released (2026-10-04)

Amogh posted "Software-based ECC works!" on 2026-10-04 and released v0.5 that evening (release). On the 8 GB card it gives 65536 MiB, 74 SM, PCIe Gen2, ECC reporting and a 64 GB BAR1; on the 10 GB card 40960 MiB and the same 4 extra SMs. 68x confirmed the ECC change live on master the same evening (Driver unlock/Confirmation 1). Upgrading needs no uninstall: rerun the installer over the old install (Phoenix17). Amogh said little more is to be had via software, so v0.5 is likely the final feature release (lia_oc and reala, 2026-10-22).

Proven 8 GB and 10 GB
Source: @_j3ns, 2026-10-04
Source: @68x0, 2026-10-04
Source: @_j3ns, 2026-10-04
Source: @phoenixone7, 2026-10-06
Source: @lia_oc, 2026-10-07
Source: @reala7096, 2026-10-22
Source: @lia_oc, 2026-10-22

Driver 615.78.08: support added (2026-10-08), failures reported

In the order posted:

  • 2026-10-08: Amogh announced that support for nvidia-open 615.78.08 was added to master. Source: @_j3ns, 2026-10-08
  • 2026-10-10 to 10-20: drew-3, Zagitta, Kaatchi and HenryKrinkle reported the unlock failing on 615.78.08 and working after going back to 615.71.09; Zagitta said the boot loader image changed in that release, and Humvee55 advised using the old booter. Which commit they ran is not stated. Source: @drew_2, 2026-10-10
    Source: @zagitta, 2026-10-17
    Source: @zagitta, 2026-10-17
    Source: @scallion_9883, 2026-10-17
    Source: @catchyuser, 2026-10-20
    Source: @.henrykrinkle, 2026-10-20

Proven Several owners hit the failure independently; details on Driver and unlock failures.

Keystone RIR burn confirmed on the 10 GB card (2026-10-09 to 10-11)

orrorin posted an AI-drafted RIR burn plan on 2026-10-09. Petri Krohn corrected and completed it ("Only two RIR burns are needed. After that you can do everything in software."), and mrpandagod validated orrorin's record encoding. On 2026-10-11 lxwx burned the two keystone records on a second 10 GB card and confirmed them: they clear the fuse that blocks software overrides, survive a cold boot and take effect after a reboot. A RIR burn is permanent: read RIR fuse burn before using 170hx-rir-tool or Cmp-170hx-rir-burn-util.

Reported 10 GB
Source: @_orrorin, 2026-10-09
Source: @petrikrohn_26497, 2026-10-09
Source: @_orrorin, 2026-10-10
Source: @djpandaman, 2026-10-10
Source: @lxtend, 2026-10-11

10 GB card: from 74 to 128 SMs (2026-10-09 to 10-20)

On 2026-10-09 mrpandagod unlocked a single 10 GB card in steps from 74 to 122 SMs after a day of resets, deliberately outside cmpunlocker; stability was untested. lxwx added 6 SMs on 2026-10-12 and on 2026-10-17 reported all 128 SMs at full clock, his contribution being how to run all 128 at full clock speed; stability problems under real workloads followed. Waypoint (80 SMs, then all SMs not marked defective) and Feralzi (126 SMs, after reading Humvee55's notes) reported the same week, GhostInTheDatacenter reached 128 SMs through the RIR burn on 2026-10-19, and orrorin posted "we did it" on 2026-10-20. Humvee55 said on 2026-10-16 that he runs 20 10 GB cards at 128 SMs and Gen3 x16 with one RIR burn, everything else being volatile software overrides, and on 2026-10-17 he called this the endgame for the 10 GB card; the 8 GB card stays at 74 SMs and 64 GB. Details: Full SM unlock.

Reported 10 GB
Source: @djpandaman, 2026-10-09
Source: @lxtend, 2026-10-12
Source: @djpandaman, 2026-10-12
Source: @scallion_9883, 2026-10-16
Source: @scallion_9883, 2026-10-16
Source: @feralzi, 2026-10-17
Source: @lxtend, 2026-10-17
Source: @lxtend, 2026-10-17
Source: @waypoint3642, 2026-10-17
Source: @scallion_9883, 2026-10-17
Source: @feralzi, 2026-10-17
Source: @ghostinthedatacenter_87281, 2026-10-19
Source: @_orrorin, 2026-10-20

10 GB card: PCIe Gen3 (2026-10-12), process published 2026-10-19

On 2026-10-09 mrpandagod said Gen3 cannot be done with a purely volatile software unlock: a RIR burn is required. After burning the keystone records lxwx could override the Gen3 fuse, and by 2026-10-12 he had Gen3 on his 10 GB card (in an x4 slot). On 2026-10-19 he published the process for the 10 GB card only (Gen3_unlock_en.md in lixiangwuxian/170hx_tips), and other owners confirmed it on their cards. The 8 GB card has no Gen3 route (September, above). Steps and warnings: PCIe Gen3 on the 10 GB card.

Reported 10 GB
Source: @djpandaman, 2026-10-09
Source: @lxtend, 2026-10-11
Source: @lxtend, 2026-10-11
Source: @lxtend, 2026-10-19
Source: @alanoo, 2026-10-19
Source: @pcsv., 2026-10-26

vGPU close to working (2026-10-26)

At 23:32 UTC on 2026-10-26 Amogh posted "Good news folks, vGPU is close to working on my end!" and said a couple of changes to cmpunlocker would follow. The vGPU-and-others branch is public (arabus, 2026-10-27) but not in master.

Reported 8 GB and 10 GB
Source: @_j3ns, 2026-10-26
Source: @arabus_74064, 2026-10-27

Tom's Hardware on the consumer-card port (2026-10-26)

On 2026-10-26 Tom's Hardware published an article on the port of cmpunlocker's compute unlock to RTX 20, 30 and 40 series cards, which removes a half-speed tensor throttle: double the peak tensor rate on the RTX 4090 and up to 80 percent more matrix math on the RTX 3090 Ti. ST noted that the article properly credited the project; the consumer port is Zagitta's, and he had not seen the article yet. mrpandagod: "the compute unlocks from cmpunlocker were ported over to consumer cards", which brought much more visibility to the unlock projects. This is Tom's Hardware's second article; the first, about the 170HX itself, came around 2026-08-19 (above).

Reported
Source: @stcord, 2026-10-26
Source: @zagitta, 2026-10-26
Source: @djpandaman, 2026-10-26
Source: Tom's Hardware, 2026-10-26

gpu-unlock 3.0 announced: the 170HX unlock without driver patching (2026-10-31 to 11-01)

On 2026-10-31 Zagitta reported that he had ported most of cmpunlocker to his gpu-unlock architecture, which works in the initramfs before the NVIDIA driver loads, so the driver no longer has to be patched. He called it nothing new, only the existing patches moved outside the driver. On 2026-11-01 he posted that a card survived suspend and resume and came back at Gen2 x4 with 65536 MiB, and listed what is slated for gpu-unlock 3.0: CMP 170HX support with no driver patching, and per-chip VRAM temperatures for Turing, Ampere, Ada and the 170HX as regular Linux temperature sensors. He has only 8 GB cards and wants 10 GB testers; ECC is not ported yet. Not released as of 2026-11-01. Details: cmpunlocker forks#Related consumer-card tools (not for the 170HX). On 2026-11-04 he asked whether people want ECC enablement for RTX 30 and 40 series cards in gpu-unlock, and later that day posted that nvidia-smi showed ECC enabled on a CMP 8 GB card without any patching of NVIDIA software, with support for the inforom flag that turns ECC on or off still to come. Early on 2026-11-05 (UTC) he said 3.0 was going through verification before he publishes it and that HBM ECC fault injection now worked, so he can check that ECC actually works, then showed ECC on an RTX 3090. Still not released as of 2026-11-05; status on ECC. On 2026-11-06 he asked another member to tell him if any HBM settings could be made to stick, since he had had no luck so far, and on 2026-11-07 he posted "Bit more gpu-unlock progress of integrating 170tune style hbm downclocking" with a screenshot (no numbers in the text). No release was posted by 2026-11-09. (Answered on 2026-11-17: the 3.0.0-beta branch lists the CMP 170HX as supported, see #gpu-unlock 3.0.0-beta published (2026-11-17 to 11-18). Source: repo github.com/Zagitta/gpu-unlock by Zagitta on GitHub) On 2026-11-10 he announced driverless P2P for 3.0 as well, working on GA102 and "most likely" on the CMP, with no code or numbers and nothing released with it; see P2P#Driverless P2P announced for gpu-unlock 3.0 (Zagitta, 2026-11-10). Source: @zagitta, 2026-11-10

Reported 8 GB
Source: @zagitta, 2026-10-31
Source: @zagitta, 2026-10-31
Source: @zagitta, 2026-10-31
Source: @zagitta, 2026-11-01
Source: @zagitta, 2026-11-01
Source: @zagitta, 2026-11-01
Source: @zagitta, 2026-11-04
Source: @zagitta, 2026-11-04
Source: @zagitta, 2026-11-04
Source: @zagitta, 2026-11-05
Source: @zagitta, 2026-11-05
Source: @zagitta, 2026-11-05
Source: @zagitta, 2026-11-06
Source: @zagitta, 2026-11-07

vGPU ready for testing (2026-11-04)

At 02:02 UTC on 2026-11-04 Amogh announced to the server that "vGPU is ready for testing". He called vGPU a turning point for the project's architecture and released a new sub-repo, amoghmunikote/cmptools, for managing vGPU settings on the CMP 170HX; it is a work in progress and he asked for feedback. The vGPU work itself is on cmpunlocker's vGPU-and-others branch. No tester results were posted by 2026-11-05. Setup notes: Virtual machines and passthrough#Other hypervisor notes.

Reported
Source: repo github.com/amoghmunikote/cmptools by amoghmunikote on GitHub, posted by @_j3ns, 2026-11-04

Research slows; no confirmed route for the 8 GB card (2026-11-09)

On 2026-11-09 OB88594 said it had been quite a while since anyone reported progress in the clean room (the separate research server). Zagitta had heard that the original researchers had moved to their own private channels, and said he had spent 4.78B DeepSeek V4.1 Flash tokens without getting closer to unlocking anything. Humvee55: progress is still happening but much slower these days, and the problems left are the hard ones. On what remains, in the order posted:

  • OB88594: for the 10 GB card the end point is already very clear, and the only thing missing is that nobody has opened recipes; at this stage the 8 GB card has no clear endpoint.
  • Zagitta: he thinks all the information is already out there, just not wrapped up in a form ordinary users can follow.
  • OB88594: the problem is that the 8 GB card still has no route to confirm the endpoint, and none of the suspected unlocks provided any technical information.
  • Humvee55: the 8 GB card has no such unlock, at least to his knowledge, and every Chinese unlock he has seen was false, with sellers who ghost.
  • OB88594: an 8 GB unlock would carry at least a 200 percent premium, so if one really exists it cannot be disclosed, especially by merchants; the clean room had recently studied a hardware approach without any new progress (the method is not described here).

The message that opened the thread is not reproduced here. The unverified unlock claims are on Rumours and claims to verify.

Reported 8 GB and 10 GB
Source: @ob88594, 2026-11-09
Source: @zagitta, 2026-11-09
Source: @scallion_9883, 2026-11-09
Source: @scallion_9883, 2026-11-09
Source: @zagitta, 2026-11-09
Source: @ob88594, 2026-11-09
Source: @ob88594, 2026-11-09
Source: @zagitta, 2026-11-09
Source: @ob88594, 2026-11-09
Source: @ob88594, 2026-11-09
Source: @scallion_9883, 2026-11-09
Source: @scallion_9883, 2026-11-09
Source: @scallion_9883, 2026-11-09
Source: @ob88594, 2026-11-09
Source: @ob88594, 2026-11-09

Update 2026-11-10: the next day Kate published GA100VFI, a hardware route for the 8 GB card: voltage glitching followed by permanent fuse programming, reported to give 80 GiB on nine of ten examined cards and about 120-126 SMs. Nobody else has reproduced it yet. See GA100VFI results and limits. Reported 8 GB Source: repo github.com/kate-land/ga100vfi by kate-land on GitHub, 2026-11-10 (Answered on 2026-11-17: members reproduced it and posted finished cards, see #Members report finished hardware-unlocked cards (2026-11-16 to 11-18). Source: @jonathanyjoerrington, 2026-11-17 Source: @zanooda, 2026-11-17)

10 GB card: SW-IFF on bare metal, a no-glitch FF burn, Gen3 and Gen4 x4 and the V/F offset (lab, 2026-11-16 and 11-17)

On 2026-11-16 the lab had one gate-burned 10 GB card in a VMware ESXi passthrough VM. Driver-time OPT writes took it from 74 to 76 and then 80 SMs, but enabling one of the three fused-off GPCs the same way failed at driver bind with FECS and HOST PRI timeouts. SW-IFF records armed inside the VM were wiped by every reset the guest could issue. Moved to a bare-metal host, the same arm and FLR worked, because a bare-metal FLR keeps the overlay and replays it at fuse sense. In order after that:

  • Defect-preserving maximum. The first card reached 122 SMs through SW-IFF; a second card, gate-burned on 2026-11-17, reached 108 (one of its GPCs is defective as a whole and stays off). Every factory-defective unit stayed masked. The count is the sum over enabled GPCs of 2 x (8 minus defective TPCs).
  • The gate activates on a bus reset. After the second card's RIR burn the override-disable status (0x820084) still read 1 after an FLR and read 0 after a secondary bus reset; a cold boot also works.
  • 40 GiB on both. Both cards have every disabled FBP also marked defective, and a SW-IFF probe that enabled all 12 FBPs still gave 40 GiB.
  • A permanent floorsweep with no glitch. With the gate burned, every precondition of the FF burn window was set in software. Seven FF records per card, written in reverse order and read back, made 122 and 108 SMs permanent; both counts held after a cold boot. The no-glitch route on the 10 GB card was first reported by @zarknoth.
  • Gen3 x4 on driver 615.71.09. lxwx's route, with cmpunlocker's Gen2 booter code kept in the build, trained the first card to 8 GT/s x4 at both ends; with cmp_fuse_bdf removed, the second card trained on the first attempt. A 30-minute soak with both cards at once passed with no AER or Xid errors.
  • V/F offset without a flash. Loading each card's own VBIOS image from memory with five bytes changed opened the GPC offset range to -1000 to +1000 MHz. At the same 250 W cap and cooling the 122-SM card gained 8.5 to 9.8 % (+190 to +220 MHz), the 108-SM card 10.4 % (+220 MHz) and the pair 10.0 %. Running the shroud blowers at full speed had earlier cleared a thermal throttle on the 108-SM card (+4.1 %).
  • Gen4 x4. A Gen4 driver build, a runtime PHY init and one config-space retrain gave 16 GT/s x4 at both ends on both cards, volatile, with no burn beyond the gate: 6.37 GB/s host to device and 6.76 GB/s device to host, 0 AER. A 30-minute soak on one card passed, then a 30-minute soak on both cards at once (0 AER, 0 Xid, 6.31 / 6.76 GB/s per card).
  • The "extra 4 SMs" after an FF burn are cmpunlocker's 70 to 74 RECONFIG override (TPC 0 of two GPCs on each card), not a new unlock.

Steps: SW-IFF unlock on the 10 GB card, PCIe Gen3 on the 10 GB card, PCIe Gen4 on the 10 GB card, Undervolting and power limits.

Proven 10 GB
Source: @darkmaniac7, 2026-11-16 (lab notes)
Source: @darkmaniac7, 2026-11-17 (lab notes)
Source: @zarknoth, 2026-11-15

November 2026

First community reproduction of the voltage-glitch unlock (2026-11-13)

Early on 2026-11-13 @deejay9983 questioned the GA100VFI write-up because the blog shows no screenshots, pictures or videos, and offered a 20 USD bet that it was hype; @onemillionkates (Kate) answered that she had posted all the relevant information and that a screenshot or video could be faked just as easily. Four hours later @dalzyyy posted a photo and wrote that his card was "burned to a100", done in one shot. Per @cute_sc2 and @finishtilt14 he used a Raspberry Pi Pico 2 (@samuel_hayden. thought the board did not look like one). @dalzyyy said the NVVDD probe in his photo only validates the voltage and is not strictly needed, that the Pico's ADC can be overclocked to about 4 MHz, and that a card that turned out merely unstable under load could be reverted quite easily, though he was not sure of the failure modes. He thinks the VBIOS does not really matter, and @cute_sc2 said cmpunlocker is not needed on such a card. No memory size, SM count or test numbers were posted in text. The method: Voltage-glitch unlock (GA100VFI).

Reported
Source: @deejay9983, 2026-11-13
Source: @onemillionkates, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @cute_sc2, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @samuel_hayden., 2026-11-13
Source: @cute_sc2, 2026-11-13
Source: @samuel_hayden., 2026-11-13
Source: @finishtilt14, 2026-11-13
Source: @dalzyyy, 2026-11-13
Source: @dalzyyy, 2026-11-13

Members report finished hardware-unlocked cards (2026-11-16 to 11-18)

On 2026-11-16 @mellojello_ said about 15 people had already replicated the voltage-glitch results (his count, no list). Members who posted finished cards, in the order posted:

  • @.shakdiesel (2026-11-17) finished his card after wiring and soldering he called "diabolical", with wires that kept coming off the pads, and recommends a digital microscope; he posted a screenshot of the result. Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
    Source: @.shakdiesel, 2026-11-17
  • @jonathanyjoerrington (2026-11-17) posted a readout without cmpunlocker; @kingsizexxxl read it as a 10 GB card, and he answered that it is an 8 GB card after the burn. Later that day an SM stress run on it covered 126 of 126 target SMs over 276 launches in 60 seconds. Source: @jonathanyjoerrington, 2026-11-17
    Source: @kingsizexxxl, 2026-11-17
    Source: @jonathanyjoerrington, 2026-11-17
    Source: @jonathanyjoerrington, 2026-11-17
  • @zanooda (2026-11-17): "it really works", "memtest passes, pcie gen4 works", 112 SMs (in answer to @wakeupmbrc1, who asked in Russian how many SMs). Source: @zanooda, 2026-11-17
    Source: @zanooda, 2026-11-17
    Source: @wakeupmbrc1, 2026-11-17
    Source: @zanooda, 2026-11-17
  • @killred (2026-11-18) posted a finished card and then a second one (screenshots, no numbers in text). Source: @killred, 2026-11-18
    Source: @killred, 2026-11-18

The same day @cmdaltesc summed up that a few people had unlocked their cards while he waits for a process with a very low chance of bricking. Method and builds: Voltage-glitch unlock (GA100VFI); the safety rules: Unlock without bricking.

Proven
Source: @mellojello_, 2026-11-16
Source: @cmdaltesc, 2026-11-17

gpu-unlock 3.0.0-beta published (2026-11-17 to 11-18)

On 2026-11-15, asked by @zanooda for a pointer because he would love to get rid of patched drivers, @zagitta said gpu-unlock would soon have CMP support "but only up to the same 64gb unlock", that he had ported CMP support to it so it is driverless, and that ECC can still be unlocked in software. On 2026-11-17 he added that gpu-unlock works with S3 sleep, posted a screenshot saying people were seeing results with gpu-unlock 3.0 (no numbers in the text), and said that apart from P2P the work was already done by the clean room server and Amogh, and he wrapped it up and applied it to 30-series cards. On 2026-11-18 he linked the 3.0.0-beta branch: a software unlock that "Has the same limitations as cmpunlocker for CMP cards"; on RTX 20, 30 and 40 cards it raises FP16 and BF16 tensor throughput to the level of professional cards, the beta enables P2P on 30 and 40 series, and none of it patches the NVIDIA driver. He has not looked at what the CMP 50HX, 70HX or 90HX need (the UEFI CMP 50 and 90 unlocking inspired him) and offered to add them as recipes. No CMP 170HX result with numbers was posted. Earlier steps: the gpu-unlock 3.0 announcement in October, above.

Reported
Source: @zanooda, 2026-11-15
Source: @zagitta, 2026-11-15
Source: @zagitta, 2026-11-15
Source: @zagitta, 2026-11-17
Source: @zagitta, 2026-11-17
Source: @zagitta, 2026-11-17
Source: @zagitta, 2026-11-18
Source: @zagitta, 2026-11-18
Source: @zagitta, 2026-11-18
Source: @zagitta, 2026-11-18
Source: repo github.com/Zagitta/gpu-unlock by Zagitta on GitHub

What was tried and did not work

The VBIOS route to more memory (2026-06-23)

On 2026-06-23 jiacheng_liu ran the vbios-memory path of the project's early deploy.py tool as a dry run and got "Not a PCI Option ROM (bad magic at 0x00)". adih answered that it did not work, that the code seemed to have been written by an AI from unconfirmed assumptions, and that flashing a modified VBIOS would only give a non-working device at that stage; jiacheng_liu then tried to flash anyway and hit hardware-level write protection. Memory was later unlocked in the driver instead (Driver unlock), and the August custom VBIOS plan was dropped (above).

Reported
Source: @jiacheng_liu, 2026-06-23
Source: @adih1266, 2026-06-23
Source: @adih1266, 2026-06-23
Source: @jiacheng_liu, 2026-06-23

Credits

Who found what, from the entries above. Each row gives the main post; the full credits are under each entry.

Finding Who Date Source
The exploit's proof of concept and the paper "A Canary in the Crypto Mine" Jon Pry and the private group paper posted 2026-06-26 Source: @_j3ns, 2026-06-26
Source: @meatsus, 2026-08-24
First to find the 80 GB of HBM on the 10 GB card Jon Pry (per MaitOPS) before 2026-07 Source: @_maitops, 2026-09-19
First compute unlock announced in this server Amogh 2026-06-23 Source: @_j3ns, 2026-06-23
First compute-unlock benchmark posted on the clean room server (SGEMM 12.28 TFLOPS; gpu-burn about 12,230 Gflop/s) counterstrikeaimgod, Rubbra_F 2026-07-12 Source: @counterstrikeaimgod, 2026-07-12 (CMP 170hx Clean Room Discussion server)
Source: @rubbra_f, 2026-07-12 (CMP 170hx Clean Room Discussion server)
First reproducible compute unlock Rubbra_F (per Petri Krohn) by 2026-07-13 Source: @petrikrohn_26497, 2026-07-13
Argued for releasing cmpunlocker publicly Petri Krohn 2026-07-14 Source: @petrikrohn_26497, 2026-07-14
cmpunlocker made public Amogh 2026-07-14 Source: @_j3ns, 2026-07-14
First reboot-persistent compute unlock Amogh 2026-07-16 Source: @_j3ns, 2026-07-16
Driverless Clean Room unlocker; memory with stock drivers the clean room, announced by Petri Krohn 2026-07-24 Source: @petrikrohn_26497, 2026-07-24
Gen2 reachable "with the correct register writes" Humvee55 2026-07-21 and 22 Source: @scallion_9883, 2026-07-21
MIG enabled jonathan.quai 2026-07-22 Source: @jonathan.quai, 2026-07-22
PCIe Gen2 unlock shipped Amogh 2026-07-24 Source: @_j3ns, 2026-07-24
Multi-card Gen2 retrain in the driver (patch 0008; upstream PR #18) Newman (fork bendy2) 2026-07-24 Source: @newman_08462, 2026-07-24
Early-boot 50 ms Gen2 retry (PR #24) Huzifei 2026-07-28 Source: @huzifei, 2026-07-28
Gen2 fix shipped in v0.2 Studebaker 2026-07-29 Source: @_studebaker_, 2026-07-29
P2P working with aikitoria's patch LimitlessTales, DeeJay 2026-07-29 and 30 Source: @limitlesstales, 2026-07-29
Source: @deejay9983, 2026-07-30
Software JTAG Amogh 2026-08-04 Source: @_j3ns, 2026-08-04
BAR1 unlock, adopted upstream with credit asm64 (asm64-hooligan) 2026-08-06, merged 2026-08-13 Source: @leesle., 2026-08-06
First fork with working P2P between four cards bayley (bayley_w) 2026-08-08 Source: @bayley_w, 2026-08-08
Source: repo github.com/bayley/cmpunlocker by bayley on GitHub, posted by @bayley_w, 2026-08-08
Found and fixed the reserved-region (late-PMA) bug bayley (bayley_w) 2026-08-06 to 08-11 Source: @bayley_w, 2026-08-11
P2P without kernel patches, 10x lower latency turbine 2026-08-13 Source: @turbine, 2026-08-13
Hardware ECC; made release-ready Humvee55; CUTE 2026-08-24; 2026-09-14 Source: @scallion_9883, 2026-08-24
Source: @cute_sc2, 2026-09-14
CMP 100-210 software unlocks Humvee55, Brazzo97 2026-09-08 Source: @brazzo97, 2026-09-08
Source: @scallion_9883, 2026-09-08
Gen2 fix for early windows (PR #35, closed) kmike 2026-09-11 Source: @kmike84, 2026-09-11
MIG patch validated, SGEMM 1.85 to 10.2 TFLOP/s ropuls 2026-09-15 Source: @ropuls, 2026-09-15
74 SMs Amogh 2026-09-24 Source: @_j3ns, 2026-09-24
RIR finding made public CUTE, corroborated by Amogh 2026-09-29 Source: @cute_sc2, 2026-09-29
v0.5 with ECC Amogh 2026-10-04 Source: @_j3ns, 2026-10-04
10 GB card from 74 to 122 SMs mrpandagod 2026-10-09 Source: @djpandaman, 2026-10-09
Keystone RIR burn confirmed (plan by orrorin, corrected by Petri Krohn) lxwx 2026-10-11 Source: @lxtend, 2026-10-11
PCIe Gen3 on the 10 GB card, process published lxwx 2026-10-12; 2026-10-19 Source: @lxtend, 2026-10-19
128 SMs at full clock on the 10 GB card lxwx 2026-10-17 Source: @lxtend, 2026-10-17
Compute unlock ported to consumer RTX cards Zagitta article 2026-10-26 Source: @zagitta, 2026-10-26
Floorsweep of the 8 GB card read with the driver bound: 2 FBPs and 2 to 3 GPCs per card gated but fuse-locked, 2 FBPs defective; 64 GB and 74 SM stay the reversible ceiling, about 80 GB latent, 96 GB not supported the lab (@darkmaniac7) 2026-11-05 Source: @darkmaniac7, 2026-11-05 (lab notes) Floorsweep read
Voltage-glitch unlock of the 8 GB card (GA100VFI): 80 GiB on nine of ten cards, about 120-126 SMs Kate 2026-11-10 Source: repo github.com/kate-land/ga100vfi by kate-land on GitHub, 2026-11-10 Voltage-glitch unlock (GA100VFI)
8 GB cards past 74 SMs after the glitch and FF burns (112 SMs with Gen4; 126 of 126 under a stress test) zanooda, jonathanyjoerrington 2026-11-17 Source: @jonathanyjoerrington, 2026-11-17 Source: @zanooda, 2026-11-17
CMP 170HX support in gpu-unlock 3.0.0-beta (driverless, the cmpunlocker unlocks) Zagitta 2026-11-17 Source: repo github.com/Zagitta/gpu-unlock by Zagitta on GitHub
SW-IFF on bare metal to each die's defect-preserving SM maximum (122 and 108 on two 10 GB cards); a VMware ESXi passthrough reset wipes the overlay the lab (@darkmaniac7) 2026-11-16 and 11-17 Source: @darkmaniac7, 2026-11-16 (lab notes) Source: @darkmaniac7, 2026-11-17 (lab notes)
A freshly burned RIR gate activates on a secondary bus reset or a cold boot, not an FLR the lab (@darkmaniac7) 2026-11-17 Source: @darkmaniac7, 2026-11-17 (lab notes)
122 and 108 SMs made permanent with FF records, no glitch, confirmed after a cold boot the lab (@darkmaniac7); no-glitch route first reported by zarknoth 2026-11-17 Source: @darkmaniac7, 2026-11-17 (lab notes)
Gen3 x4 on driver 615.71.09 on two 10 GB cards at once the lab (@darkmaniac7), on lxwx's route 2026-11-17 Source: @darkmaniac7, 2026-11-17 (lab notes)
V/F offset on the 10 GB card through an in-memory override of its own VBIOS, no flash the lab (@darkmaniac7), with Panchovix's vix loader mechanism 2026-11-17 Source: @darkmaniac7, 2026-11-17 (lab notes)
Gen4 x4 on two 10 GB cards, volatile, 16 GT/s at both ends the lab (@darkmaniac7) 2026-11-17 Source: @darkmaniac7, 2026-11-17 (lab notes)
Two 8 GB cards glitched with a Pico 2 W and burned to 122 and 120 SMs, the 80 GB fuse layout and PCIe fuses for 2.5-16 GT/s, confirmed after a cold boot the lab (@darkmaniac7), on dalzyu's Pico tool 2026-11-18 and 11-19 Source: @darkmaniac7, 2026-11-19 (lab notes) Voltage-glitch unlock: lab results and fuse findings
OPT_DISABLE_GEN3_SPEED located at FF chain 2 block 39 bit 9 (bit 1 does nothing) the lab (@darkmaniac7) 2026-11-19 Source: @darkmaniac7, 2026-11-19 (lab notes)

Related