【On-Chain Review】Stars AI: Quietly changed its implementation for the second time in five days; rules engine still unauditable
I checked once on November 14: the factory proxy’s implementation contract was switched in the early hours that day from an open-source version to an unpublished one, 0x622a…. Today (November 19), I checked the chain again, and the implementation slot for the same proxy had changed once more.
Evidence (all independently verifiable; checked midday on 2026-11-19):
1. The EIP-1967 implementation slot for factory proxy 0xD637dffD418505004a3D5541C7DFF64cc995E55C now points to 0x281d2acf3c962483594246a557fbfa3646b3f292, rather than the 0x622a2aa7d684e37d81b5a64c49fe9c6540b845c6 address seen on November 14.
2. The new implementation’s bytecode is 20,394 bytes, different from the old implementation’s 19,555 bytes, and has a different hash—it was not redeployed unchanged; it is different code.
3. A Sourcify v2 query for the new implementation returns null for match, creationMatch, and runtimeMatch—the source code is still unverified, and the rules engine remains unauditable.
4. owner() is still 0x30d261b5a708c444ef7e70cfa09b780d679b1111; it has not changed. According to my November 14 check, the owner can pause everything and change the 30% marketing wallet.
Methodology: For an upgradeable proxy, the rules are determined by the on-chain implementation slot, not the promotional page. The implementation has changed twice, so the rules have changed twice, and the previous audit findings are automatically invalidated.
$BTC $BNB $ETH
The above is a compilation of public information and personal analysis, and does not constitute investment advice.
I checked once on November 14: the factory proxy’s implementation contract was switched in the early hours that day from an open-source version to an unpublished one, 0x622a…. Today (November 19), I checked the chain again, and the implementation slot for the same proxy had changed once more.
Evidence (all independently verifiable; checked midday on 2026-11-19):
1. The EIP-1967 implementation slot for factory proxy 0xD637dffD418505004a3D5541C7DFF64cc995E55C now points to 0x281d2acf3c962483594246a557fbfa3646b3f292, rather than the 0x622a2aa7d684e37d81b5a64c49fe9c6540b845c6 address seen on November 14.
2. The new implementation’s bytecode is 20,394 bytes, different from the old implementation’s 19,555 bytes, and has a different hash—it was not redeployed unchanged; it is different code.
3. A Sourcify v2 query for the new implementation returns null for match, creationMatch, and runtimeMatch—the source code is still unverified, and the rules engine remains unauditable.
4. owner() is still 0x30d261b5a708c444ef7e70cfa09b780d679b1111; it has not changed. According to my November 14 check, the owner can pause everything and change the 30% marketing wallet.
Methodology: For an upgradeable proxy, the rules are determined by the on-chain implementation slot, not the promotional page. The implementation has changed twice, so the rules have changed twice, and the previous audit findings are automatically invalidated.
$BTC $BNB $ETH
The above is a compilation of public information and personal analysis, and does not constitute investment advice.