the problem with these virtuals launches using Butler is the deployment tx actually doesn't include the deployer wallet, but there are two ways to get it: 1) aGDP(dot)io site: see the the first wallet address on top is 0xa42cAe963CaaA4218C8F045d153b2172f2459319 2) destination wallet of virtual fee distributution txs that reference the token in question, for example sends the cbBTC fees to 0xa42cAe963CaaA4218C8F045d153b2172f2459319 and the tx includes a reference txhash which confirms it is NOX fees so this is the SemiModularAccountBytecode wallet that receives the fees, unique address for each virtuals token. then you follow the outflows from that wallet which leads us to the dev of the coin a) 0xa6c9ba866992cfd7fd6460ba912bfa405ada9df0 b) 0xef4364fe4487353df46eb7c811d4fac78b856c7f c) 0xfbce8de3c262dfbbeef1ba9a7d2b9d752f537b79 (compare this to the clear example of KLARK where outflows are all going to michaelpham, the dev wallet) wallet (c) is accumulating the cbBTC but we get nothing because there's no activity from there. the intel comes from (a) and (b) wallets which are both deployed by 0x9547e85f3016303a2996271314bde78b02021a28 and this is the virtuals admin wallet linked to the prxvt and other virtuals lp migrations. again credit to @beeboopx FOLLOW HIM