WHAT THE HELL IS GOING ON... ?!?! (A plain English explanation will be found down the thread... 😉) What follows is a synthesis of the on-chain research by @Mijk_NL, the observable behavior of tracked wallets, and the interpretations circulating in the PulseChain/pDAI community as of mid-October 2026... 🔷 The core research finding: Mijk_NL released a block-pinned forensic dossier mapping how a small set of related wallets has used the governance systems that arrived with PulseChain’s full-state fork to accumulate admin roles, upgrade rights, and voting power across multiple inherited Ethereum DeFi protocols. The primary addresses are 48Fc (0x48Fc…0000), e121 (0x98c8…e121), and 5996 (0xB869…5996), plus wallets they funded. These sit inside the broader cluster long associated with interactions involving forked Maker remnants, Aave-style systems, L2 admin keys, and related infrastructure. Because the fork copied entire protocols (including their governance tokens and timelocks), wallets that later acquired sufficient voting power could propose and execute changes that granted themselves code-upgrade rights. Those rights control collateral parameters, market code, and, in some cases, treasuries. This is ordinary governance execution, not a private-key exploit of the protocol logic itself. Verified positions include: 🔹 Onyx (Compound-style fork): 48Fc is Timelock admin and direct admin of five markets, pending admin on the remaining twelve. The oETH market still holds a large quantity of forked ETH; the position remains unmoved. 🔹 Reserve / hyUSD: 48Fc executed upgrades to the BackingManager and stRSR implementations. Code control exists; full ownership of the token is not complete, and the replacement voting interface returns constant values. 🔹 Braintrust / BTRST: An executed proposal sent 3 million forked BTRST to 5996. 🔹 Origin / OUSD: 48Fc holds a large share of veOGV relative to current quorum. 🔹 Metronome: e121 (with 48Fc) holds the entirety of the measured esMET supply. Proposals to make e121 admin of the token and collateral markets have succeeded but remain unexecuted. 🔹 RAI / Reflexer, YAM, Ease, and others: Similar patterns of proposals, queuing, and cross-delegation appear. Some have succeeded or been queued; others were defeated or remain below quorum. Across the reviewed set, the core wallets account for dozens of proposals, with a minority fully executed, many queued or succeeded-but-unexecuted, and many defeated. Current dollar value of the controlled forked assets is low because most forked tokens trade at tiny fractions of their Ethereum counterparts. Most of the power is therefore armed rather than fully triggered. Large pots and Safes were still in place at the time of the research. Mijk explicitly noted that this dossier does not document new pDAI mints or direct Maker-module actions. The connection is the shared cluster: 5996 (historically linked in community research to pDAI/Maker-related operations) was funded by 48Fc and sits in the same group. 🔷 Status of the 5996 wallet: Mijk has stated that 5996 “seems compromised” and is now “irrelevant atm.” He wrote that its keys “were likely swept by a private-key sweeper (0xdca9), possibly on purpose,” and that the active operational hands going forward are 48Fc and e121. Community accounts, notably @yourfriendSOMMI, have framed the same development as activation of a “Dead Man’s Switch.” The claim is that the private key became publicly known, that any PLS sent to 5996 is immediately swept by an automated bot to another address, and that this dilutes 5996’s prior power to a third party. Some treat the timing with Richard Heart’s detention in Istanbul as non-coincidental; others treat it as operational security or a deliberate redistribution of capability inside the cluster. A sweeper bot is an automated script that watches a wallet whose key is known to be compromised and instantly transfers any incoming native token (here, PLS) to a different address. Observable outgoing transfers from 5996 to addresses in the 0xdca9 range are consistent with this pattern. The practical result is that 5996 can no longer reliably hold or receive PLS. The “dead man switch” language is metaphorical. It describes a mechanism that automatically moves control or residual value if the original holder becomes inactive or the key is exposed. Whether the sweep was arranged in advance by the prior operator, executed by an external party after a leak, or both is not independently proven outside the community discussion. The observable outcome is the same: 5996 is no longer a reliable holding or signing address, and subsequent activity is expected from the still-active linked wallets (primarily 48Fc and e121). 🔷 Synthesis of what is happening: A coordinated set of wallets has spent an extended period using the governance that shipped with the fork to place itself in admin and upgrade positions across a stack of forked lending markets, RToken-style components, and other DAOs. The positions are real and verifiable; most remain only partially executed. Current economic stakes are low. Separately, the historically prominent 5996 address has been rendered inert for practical purposes by a sweeper, and community commentary has labeled that development a dead-man-switch event timed with external legal pressure on the ecosystem’s most visible founder. The research itself is more precise and self-correcting than pure narrative. Claims are tied to receipts, admin-role reads, and proposal states. Earlier overstatements have been refined. At the same time, public discussion layers interpretive framing (chess moves, deliberate hand-offs, links to Heart’s detention, or extraction motives) on top of the on-chain facts. 🔷 Implications for pDAI: pDAI’s core token contract remains ownerless with no freeze function. Its price continues to be set by open-market trading and is currently a small fraction of a dollar. The findings above do not show new pDAI issuance. The relevance is indirect but material: 🔹 Practical control over surrounding forked infrastructure (lending markets that could interact with pDAI or related assets, Reserve-style components, Metronome, Origin governance, etc.) is concentrated in a small set of wallets. The ownerless character of the pDAI token itself does not extend to that broader stack. 🔹 With 5996 neutralized, any ongoing operational activity shifts to the remaining linked addresses. Continuity of the cluster’s positioning does not depend on 5996 remaining usable. 🔹 Armed admin and upgrade rights create optionality. They could later support mechanisms that increase demand for or interact with pDAI, or they could be used for extraction that further erodes confidence. Because most positions are not fully triggered and current values are low, neither outcome is imminent. 🔹 The combination of documented concentration of control, historical post-fork supply dynamics in the broader ecosystem, and the recent neutralization of a high-profile wallet reinforces the gap between the “fully decentralized / runs without any key holder” framing often applied to pDAI and the reality of a concentrated operator set acting on surrounding protocols. In short, the situation is one of real, methodical, partially armed control over forked DeFi infrastructure by a coordinated cluster, accompanied by the practical retirement of the 5996 address via sweeping (interpreted by parts of the community as a dead-man switch). Direct effects on pDAI’s own mechanics are absent in the latest verified work; the implications run through surrounding infrastructure control, latent optionality, and the persistent tension between decentralized rhetoric and concentrated on-chain agency. Mijk_NL will probably publish more detailed information on that subject. Trying to understand it myself, I tried to clarify that topic with this research analysis ... Hoping this helped... #pDAI still $1 INEVITABLE... ❤️💛🧡💚💙🩵💜🩷🤍❤️ xitter.cf/yourfriendSOMMI/status…