[work in progress, updated continually]

Investigation 1: Coordinated sniping at the VULT launch

The VULT TEAM WALLET took part in the same payment arrangement as 26 wallets that bought at the VULT launch.

On 27 October 2025, the team wallet made a 1,000 USDC test buy before the first round. Another 26 wallets each spent 1,000 USDC as the first round opened and another 9,000 USDC as the second opened. That is the launch sniping examined here. The next day, all 27 wallets sent exactly one fifth of their purchased VULT to one receiving wallet. That wallet had already sent ETH to fund all 26 forwarding routes.

The group bought 1.57% of supply and later sold 87.68% of what it bought for about $312,715 in stablecoins.

Start with three checks: Identify the team wallet → verify the 26 wallets’ buys → compare what they all paid.

1

What buyers were told before the sale

Vultisig said its launch was intended to distribute the token widely. The official announcement described a buying limit of 1,000 USDC in the first round and 10,000 USDC total after the second round opened. It used both “per wallet” and “per user” when describing the limit.

Vultisig official account · 25 October 2025
Distribute $VULT to as many people as fair as possible

Launch article Original source · Archived source (indexed; replay not verified) · Preserved original post

A single wallet could fill the limit in two purchases. The question is what connected the 26 wallets that did exactly that. Their common payment route, shown below, gives an independent way to test that connection. The launch rules allowed immediate selling.

2

The whitelist administrator opened the route for the test buy

Three addresses had different roles. The token owner activated the whitelist. The whitelist administrator operated it. The VULT TEAM WALLET made the test purchase.

RoleAddressAction
VULT token owner0x8e247a480449c84a5fdd25974a8501f3efa4abb9Activated the launch whitelist.
Whitelist administrator0x9ad16d73f600fcdca5a61b7c56c73ae997626c18Added the pool and admitted the test address. Removed both after the buy.
VULT TEAM WALLET0xaf084252945b6a71a7ef5579c187de9c436041d5Signed the 1,000 USDC test purchase.

Before the scheduled rounds, the VULT contract permitted transfers between addresses already on the list. Adding the trading pool to that list meant the pool could deliver VULT to an approved buyer. The administrator added the pool first and the VULT TEAM WALLET in a batch of 500 addresses. The table follows what happened in order.

JP, @jpthor · 27 October 2025, 11:41:29 UTC
THE LAUNCHLIST IS SET

The post also included the test screenshot. Original X link · Archive · Saved copy

All 27 wallets appear in the 1,149-address list in the signed project code. They also appear on the earlier WEWE whitelist. That shows earlier eligibility. The coordinated VULT trades and payments are established separately below. See the list sources and address comparison.

UTCRecorded actionTransaction
26 Oct 14:00:23Token owner 8e247 activated the current buyer list.Activation
27 Oct 10:34:35Administrator 9ad16 added the trading pool to the ordinary address list, enabling the early route.Pool admitted
27 Oct 10:39:11The same administrator submitted a 500-address batch, including the VULT TEAM WALLET. 488 addresses were newly added.Buyer admitted
27 Oct 10:55:47The VULT TEAM WALLET bought 1,000 USDC of VULT, at position 6 in this block.Test purchase
27 Oct 10:55:47The administrator removed the pool at position 109 in that same block, closing the route.Pool removed
27 Oct 11:18:11The administrator removed the VULT TEAM WALLET.Buyer removed
Administrator actions and purchase, reconstructed from signed transactions and successful receipts. Positions are zero-based transactionIndex values.

The test buy was 1 hour, 3 minutes and 36 seconds before the administrator advanced the contract to round one. Another approved wallet used the early route twice, and a replay using a third funded and approved wallet also succeeded. The team wallet’s later 20% transfer is what links this test to the coordinated buying group.

Round one enabled at 11:59:23 UTC · Other early buy 1 · Other early buy 2

Signed project list · Preserved pinned source

3

The team’s own screenshot identifies the VULT TEAM WALLET

JP shared an image of an Ethereum transaction in the Vultisig Telegram group. Eight minutes later, the same image appeared in his public launch post acknowledging that the team had tested the contracts. The preserved image and the transaction can be compared without relying on anyone’s recollection.

The image shows six fee and gas fields. Together they match exactly one of the 211 transactions in the block, the 1,000 USDC purchase sent by 0xaf084252945b6a71a7ef5579c187de9c436041d5. That is the basis for the VULT TEAM WALLET label.

JP · 27 October 2025, 11:33:54 UTC
fyi these are the right gas settings!

Telegram message 756

Telegram message 756, dated 27 October 2025, 11:33:54 UTC in the export. The screenshot shows local time. Capture time unverified.
Telegram message 756, dated 27 October 2025, 11:33:54 UTC in the export. The screenshot shows local time. Capture time unverified. Original source
JP, @jpthor · 27 October 2025, 11:41:29 UTC
WE DID SOME SMALL TEST TRANSACTIONS TO VERIFY THE CONTRACTS WORK

Original X link · Archive · Saved copy

Wayback rendering captured 28 October 2026. Original post: 27 October 2025, 11:41:29 UTC.
Wayback rendering captured 28 October 2026. Original post: 27 October 2025, 11:41:29 UTC. Original X URL (currently unavailable) · Archived source · Preserved original post
Original X attachment. It matches the Telegram attachment byte for byte.
Original X attachment. It matches the Telegram attachment byte for byte. Original X URL (currently unavailable) · Archived source · Preserved original post
Field visible in the imageThe VULT TEAM WALLET’s 1,000 USDC purchase
Gas limit500,000
Gas used164,226
Gas price21.111901002 gwei
Priority fee21 gwei
Maximum fee400 gwei
Transaction fee0.003467123053954452 ETH
The full numeric comparison matches exactly one of the 211 transactions in the block: the VULT TEAM WALLET’s early buy.
4

The same 26 wallets filled both rounds

At 11:59:47 UTC on 27 October 2025, 26 wallets each bought 1,000 USDC of VULT in the same Ethereum block. At 13:01:11 UTC, the same 26 wallets each bought another 9,000 USDC in another single block. Each reached the advertised 10,000 USDC limit. Together they spent 260,000 USDC.

The 26 are the exact addresses in the table. The team wallet’s earlier purchase is separate from these 52 swaps. The next step compares what all 27 did with their purchased tokens.

First purchase block · Second purchase block

All 52 purchases
Each amount links to its purchase. First round: block 23,668,637. Second round: block 23,668,942.
5

All 27 sent one fifth of what they bought

At 12:00:47 UTC on 28 October, the VULT TEAM WALLET and the 26 launch buyers each sent 20% of the VULT they bought in a separate token transfer. Their 27 transactions sit back to back in one block and use identical fee settings. The team wallet’s payment is at transaction index 54, inside the run.

For example, the team wallet received 32,438.067221737680597966 VULT in the test and later sent 6,487.613444347536119593 VULT to 0x9f82582fc038673921f4b46528d2bde55375ac97. Divide the purchased amount by five and round down to the smallest VULT unit. The result is the exact amount sent. The same calculation works for every row.

These transfers took place the day after buying. The team wallet’s receipt shows a standalone token transfer directly to the receiving address. The 26 others sent their shares to 26 intermediate addresses, which forwarded the exact amounts to that same recipient.

Verify any of the 27 wallets

Select a wallet to see the purchase, the calculation, and the actual payment. The comparison uses the token’s smallest unit, so it is exact.

VULT bought
32,438.067221737680597966
One fifth, rounded down
6,487.613444347536119593
VULT sent
6,487.613444347536119593

The VULT TEAM WALLET sent its share directly to the common receiving wallet.

Test purchase · 20% transfer

All 27 payments and forwarding transactions
PositionBuying walletVULT boughtVULT paidRoute to receiving wallet
390xc19a78…fbef5758,244.32130911,648.864262via 0x7cd173…2fe6cf
400x631cba…f14a0358,272.94291011,654.588582via 0xae8596…3d15c5
410x70a3bc…bd697e58,759.46717411,751.893435via 0x923535…e04154
420x5fb00f…9411bc57,022.67475811,404.534952via 0x6fee9f…7d1232
430x2a1b66…d5c1d859,637.18581211,927.437162via 0x5d9b82…9eed70
440xaaae85…e491c958,798.24481811,759.648964via 0xd8c360…d0469b
450xf128c5…92497160,140.23988912,028.047978via 0xc05dc2…3a036f
460x25b84f…068a0a60,333.64141912,066.728284via 0x0cd598…c7be8d
470xc4ed1d…dafc2656,615.91662611,323.183325via 0x1101c7…808dd1
480xb74ee4…ad533159,065.47466611,813.094933via 0x02ab9d…f4ed97
490x7dbc21…a8d70f61,679.75860412,335.951721via 0x69026d…5b11e3
500xe8ace2…b33f4556,385.00139611,277.000279via 0x81d7e5…dae838
510x22ae88…74636160,725.71571412,145.143143via 0x487c52…4c6926
520x2b7437…9e641e59,624.38508411,924.877017via 0x74b22b…e2e94e
530x07987d…38377758,757.17241911,751.434484via 0xf80101…45f003
54af084 — test wallet32,438.0672226,487.613444Direct to 0x9f8258…75ac97
550x64dbd4…4b062a58,759.80234811,751.960470via 0x52b928…4bff85
560xf8fc64…315fbc58,228.31496311,645.662993via 0x05232f…f8a11a
570xd61910…95b3cf61,746.05798512,349.211597via 0xb07f26…5e0910
580x9d51ef…bb93d160,703.54339812,140.708680via 0x888c89…083202
590xd47e3b…5abece59,092.37534711,818.475069via 0x9bc892…ef69a8
600xced3ea…6d446a56,155.50120211,231.100240via 0xf6f8f3…1567e3
610x88e48f…edd10c61,676.53823412,335.307647via 0x6b949b…89448d
620xeb56e2…4004e758,604.61220211,720.922440via 0xc54e94…382cc3
630x711d74…4efd1f60,193.04212712,038.608425via 0x1bc4c0…0016e7
640x8bb114…e5068d61,153.45706412,230.691413via 0x25a39c…1a2e8d
650xbe5412…5c08eb58,117.64768911,623.529538via 0x9b7e9b…ee6d97
Actual block order. Token values are displayed to six decimals; each transfer equals one fifth rounded down to the smallest token unit. Every payment amount links to its transaction.

The VULT TEAM WALLET paid 0x9f8258…75ac97 directly. The other 26 used forwarding wallets. The address received 314,186.22 VULT in total.

Earlier launch phases restricted wallet-to-wallet transfers.

Complete payment block

6

The receiving wallet paid for the 26 forwarding routes in advance

At 10:51:23 UTC on 28 October, the wallet that would receive the 20% shares sent ETH to precisely the 26 forwarding addresses. It did this 69 minutes and 24 seconds before the buyers made their payments. The ETH covered the fees for forwarding the VULT.

This places the common recipient on both sides of the arrangement. It prepared the routes before the buyers paid, then received the exact shares through the routes it had funded. The VULT TEAM WALLET paid that recipient directly.

Recorded featureWhat it shows
Sender0x9f8258…75ac97
TransactionAdvance fee funding
RecipientsAll 26 forwarding addresses; no additional native-payment recipients
ETH delivered0.0380143 ETH across those 26 addresses
Later useEvery funded address forwarded the corresponding buyer’s exact 20% share
The decoded recipient list and successful executed transfers match all 26 forwarding routes.
7

Follow the purchase money, the remaining tokens and the sales

On 26 October, the 26 buyers moved 232,978 USDC to other wallets between 12:11:47 and 12:30:11 UTC. On launch day those counterparties returned the exact amounts between 11:35:35 and 11:44:11 UTC, before round one. In 15 of the 26 routes, the counterparty later received the buyer’s remaining VULT after the 20% payment. The same address pairs recur before the buys and after settlement.

Verify the 26 USDC round trips and where the remaining VULT went
BuyerCounterpartyUSDC26 Oct, sent (UTC)27 Oct, returned (UTC)Recipient of remaining VULT
0xc4ed1d…dafc260x39d1b1…1ae35b9,00012:11:4711:44:11Same wallet
0x7dbc21…a8d70f0x6c60a9…f44a9a9,00912:12:4711:43:23Same wallet
0x2a1b66…d5c1d80x4598d4…76d9fb9,00612:13:2311:43:11Same wallet
0x22ae88…7463610x92357e…37f8809,01512:13:5911:42:59Same wallet
0x25b84f…068a0a0xdcb317…c2df049,00112:14:3511:42:35Same wallet
0x631cba…f14a030xdd13ca…749b309,01012:15:1111:43:47Same wallet
0xd61910…95b3cf0x6223d9…f178099,00812:15:1111:42:23Same wallet
0xaaae85…e491c90xa24c44…c468029,00412:15:4711:42:11Same wallet
0xf128c5…9249710xedbe37…3878339,00212:16:1111:41:59Same wallet
0xb74ee4…ad53310xe19651…431b9c9,00112:17:1111:41:59Same wallet
0xbe5412…5c08eb0x109494…06f2229,00412:17:1111:41:23Same wallet
0x8bb114…e5068d0x28293d…e4385c8,99512:17:4711:41:11Same wallet
0x70a3bc…bd697e0x81dec4…dfbee48,95012:19:2311:40:47Same wallet
0x88e48f…edd10c0x74bb88…9fff1f8,90012:19:2311:40:23Different wallet
0xd47e3b…5abece0x1f2804…453cd38,99012:19:2311:40:35Same wallet
0x5fb00f…9411bc0xb09e99…b923928,90612:20:4711:39:47Different wallet
0x711d74…4efd1f0xff017e…b48a238,91012:21:1111:39:47Different wallet
0x64dbd4…4b062a0xd0a898…f02c278,90512:21:2311:38:23Different wallet
0x2b7437…9e641e0xe871ca…90fa8e8,92012:22:3511:37:11Different wallet
0x07987d…3837770xb120d4…691ba58,90412:23:1111:36:59Different wallet
0xeb56e2…4004e70x6eb982…8708b68,90212:23:1111:39:59Different wallet
0xf8fc64…315fbc0xa069c3…8382a18,90112:23:1111:38:11Different wallet
0xe8ace2…b33f450x5e6628…b787539,00012:23:3511:36:35Different wallet
0x9d51ef…bb93d10xa7acb9…f12a358,90012:24:2311:36:35Different wallet
0xced3ea…6d446a0x9b85e6…489c458,90512:25:2311:35:35Different wallet
0xc19a78…fbef570x62357e…2274e38,93012:30:1111:35:59Same wallet

In March 2024, the VULT TEAM WALLET sent ETH to a wallet that later funded two of the 26 buyers. All three used the same Binance deposit address for AEVO. The intermediary also held other funds.

Team wallet → intermediary (ETH) · Intermediary → buyer 1 (ETH) · Intermediary → buyer 2 (ETH)

VULT TEAM WALLET’s later routeAmount in USDC
Previously sent to the wallet receiving its remaining VULT9,100.019827
Further balance sent there195.000000
Proceeds from selling the remaining VULT5,924.731854
Combined transfer to the same AEVO-era deposit15,219.751681
The sale proceeds were part of a larger transfer, not a separate 5,924.73-USDC deposit. View that transfer.

Tokens bought, sold and held

Scope: VULT TEAM WALLET and 26 buyers. Snapshot: block 26,299,841, 29 October 2026, 17:17:35 UTC. Supply: 100 million VULT.

Token dispositionVULT, roundedShare of total supplyShare of this group’s purchases
Originally bought1,570,931.10241.570931%100%
Verified sales1,377,408.64531.377409%87.6810%
Still in the traced wallets37,522.45710.037522%2.3885%
Transferred onward; later disposition unresolved156,000.00000.156000%9.9304%

Nearly all held VULT was at 0x5b4baf…aeb110.

The 156,000 VULT went through 501704 to 0x1bff6b…e7e3, where it mixed with other deposits. Its later disposition is unresolved.

Sale proceeds

Sale routeGross stablecoin received
Remaining-token recipients and their traced child wallet259,155.693150 USDC
Common 20% receiving wallet’s two direct sales53,558.814277 USDT
Total, treating each stablecoin as $1Approximately $312,714.51

Gross receipts exceeded the 261,000 USDC purchase cost by about $51,715 before fees. This measures the group’s on-chain cash flow. Individual profits remain unknown.

The VULT TEAM WALLET bought 32,438.07 VULT for 1,000 USDC. It sent 6,487.61 VULT to the shared address. The remaining 25,950.45 VULT sold for 5,924.73 USDC.

Where the $312,714.51 went

Onward routeSale receipts associated with that route, at $1 per stablecoinWhat was traced
Bybit-boundApproximately $290,238.78242,720.950667 USDC generated by 24 buyers’ remaining-token recipients, routed through 1d6ec2 and e8f0bf; plus 47,517.831618 USDT from the common 20% receiving wallet, through c467f0.
Binance-boundApproximately $11,964.735,924.731854 USDC generated by JP’s test-wallet remaining-token route, through 7d5996; plus 6,040 USDT paid by the common 20% receiving wallet through 1f0891.
Other or incompletely traced routesApproximately $10,510.998,802.923973 USDC from the 9d813 route into a mixed onward payment; 1,707.086656 USDC from the 5b4baf child wallet’s sales; and a net 0.982659 USDT remainder in the common receiving-wallet reconciliation.
Total$312,714.51Gross sale receipts. Exchange customer accounts and any later fiat withdrawals remain unidentified.

The exchange deposits also carried other funds. The table attributes only VULT sale proceeds.

How the small and mixed routes reconcile

The common 20% receiving wallet’s 53,558.814277 USDT of sale receipts plus 0.006584 USDT of small additional receipts equals 47,517.831618 toward Bybit, 6,040 toward Binance and 0.989243 to another address. The net sale-only remainder is therefore 0.982659 USDT. Fungible balances are commingled; this is an accounting reconciliation, not identification of particular units.

The 9d813 route’s 8,802.923973 USDC of sale receipts joined other money before a mixed 18,226.741040 USDC onward transfer. The 5b4baf wallet later sent 125 USDC onward and 1,500 USDC to a router; its checked balance was 137.148896 USDC, including other receipts. These routes are not established as bank or exchange withdrawals. The source amounts and their proof grades are retained in the sale-destination reconciliation and underlying route records.

Exact onward transfers and later activity

Exact onward transfers and addresses

Observed amountRouteLast established classification
146,200.195798 USDC1d6ec2…dad3 → 260b36…4ceaBybit deposit / reserve address
98,080.341232 USDCe8f0bf…eb0e → 260b36…4ceaSeparate Bybit deposit / same reserve address
15,219.751681 USDCTest-wallet route → 7d5996…4084 → ee7ae8…4055Binance-labelled infrastructure; includes 9,295.019827 USDC beyond the VULT sale receipt
47,517.831618 USDTc467f0…217d → 18e296…82f6Bybit reserve address
6,040 USDT across two payments1f0891…f358 → 28c6c0…1d60Binance-labelled hot wallet; forwards also include other funds
18,226.741040 USDC, mixed sourcesa06fe1…072d → bb8054…fdb7Unclassified recipient

Exchange destinations are traceable on-chain. The credited customers and any cash withdrawals remain unknown. Full route records.

Activity continued after the launch

  • 3 April 2026: the 1f089 route forwarded 54 USDT from the earlier payment together with 2,259.21 USDT of new funds to Binance-labelled 28c6.
  • 3 October 2026: 9f825 sent 3.060450 USDT onward. The ledger traces that amount to later receipts, not to another VULT sale.
  • 10 October 2026: 1f089 forwarded another 6,401.825 USDT to Binance-labelled 28c6. This is not an additional traced VULT sale receipt.
  • 13 October 2026: 1d6ec sent 0.031355234449432796 ETH to an unclassified recipient. Transaction.
  • 23 October 2026: the mixed 1bff address sent 14.478 VULT onward. This is activity of the pooled address, not proof that this group’s deposited tokens were the tokens moved. Transaction.
Verify the quantities and snapshot balances

Exact arithmetic · Canonical transfer ledger and transaction links · All 27 purchase routes · Pinned balance results · Raw state request/response locators · Mixed-address transfer history and duplicate resolution · File hashes.

Use the canonical VULT contract 0xb788144df611029c60b859df47e79b7726c4deba, USDC 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 and USDT 0xdac17f958d2ee523a2206206994597c13d831ec7. Purchase and sale quantities are derived from exact token receipts; the independent accounting pass checked 217 outer transaction signatures and 305 transfer logs. The 71 new state reads are pinned to block 26,299,841. Provider state and receipt data are not independent consensus or trie proofs.

8

The 20% payment preceded Paaao’s public assurance

Paaao, @TheDivingPaaao · 28 October 2025, 16:07:31 UTC
But I can assure you, non in the team got rich or was sniping.

The post also defended JP. Original source · Archived source · Preserved original post

Wayback rendering captured 28 October 2026. Original post: 28 October 2025, 16:07:31 UTC.
Wayback rendering captured 28 October 2026. Original post: 28 October 2025, 16:07:31 UTC. Original source · Archived viewer · Capture provenance
Continuation of the same capture. The displayed time, 17:07:31 GMT+0100, is 16:07:31 UTC.
Continuation of the same capture. The displayed time, 17:07:31 GMT+0100, is 16:07:31 UTC. Original source · Archived viewer · Capture provenance

The VULT TEAM WALLET paid its share at 12:00:47 UTC. Paaao posted the assurance at 16:07:31 UTC, just over four hours later. The transaction record shows that the wallet the team had identified through its test had already participated in the same payment arrangement as the 26 coordinated buyers.

Team wallet’s 20% transfer · Preserved assurance and timestamp

9

What the records establish

The project’s whitelist administrator enabled the early purchase. The team’s post and the exact gas figures tie that purchase to the VULT TEAM WALLET. The wallet then paid 20% of its VULT to the same address that arranged and received the 26 other buyers’ 20% payments.

The team wallet’s separate transfer is the link: exact amount, same block of payments, same ultimate recipient. The recipient’s advance funding of all 26 forwarding wallets shows the collection was prepared before the buyers paid.

Check a wallet’s transactions · See the original and preserved lists · Inspect the common receiving wallet

The four source workbooks

SourceDistinct addressesOriginal sourcePreserved workbook
Earlier VULT list labelled Outdated1,100Original Google SheetExact XLSX export
WEWE1,149Original Google SheetExact XLSX export
Original VULT1,485Original Google SheetExact XLSX export
Later VULT activation1,368Original Google SheetExact XLSX export
Retrieved 27 October 2026. These exports are not immutable snapshots of a 2024 or 2025 launch-day state. The signed historical project code and on-chain admission records supply the separate historical evidence. Exact SHA-256 hashes · All 27 wallet rows as CSV