For this frozen window, 0xbd5c5da49c03cac396528e11ba1275c8499c7a389418b0a24bb888c454530965 repeated one five-call composition 184 times. Each transaction passed receipts through supporting construction, token-mint, attestation, and settlement steps. The stored explanation can describe those connected pieces, but it does not establish the complete transaction purpose.
This resembles queued or automated cross-chain message handling, not a proven identity or strategy. The address is an on-chain identity; the evidence does not establish who controls it, whether a transfer completed, or what value was involved.
One shape, repeated 184 times
The complete frozen-window record contains 184 transactions, from 13:07:15 to 23:35:56 UTC. The ledger and prose streams are capped at the latest 500 transactions, but this address has only 184, so they include the entire observed history.
Every row uses shape c0473645: five connected calls across two package revisions. The sequence is:
1. receive_message::receive_message 2. handle_receive_message::handle_receive_message 3. deconstruct_stamp_receipt_ticket_with_burn_message 4. receive_message::stamp_receipt 5. complete_receive_message
Circle independently documents the two package addresses as Sui’s CCTP v1 MessageTransmitter and TokenMessengerMinter packages. That makes this sequence consistent with cross-chain message reception and minting, but the address record itself does not prove the source chain, recipient, amount, or completion of any transfer. [Circle’s CCTP package documentation](https://developers.circle.com/cctp/v1/sui-packages)
The first transaction, 6Pk3iABz, a middle example, 54kMSM3W, and the final transaction, 2kMtWvvx, all carry the same five-step narrative. None has an asserted higher-level behavior. No execution failure is recorded for any of the 184 transactions.
Bursts, then a long silence
The rhythm is uneven rather than periodic: the mean gap is 206.1 seconds, the median is 23.419 seconds, and the 90th-percentile gap is 423.5 seconds. The longest idle period is about 3 hours 18 minutes. The busiest minute, 14:15 UTC, contains seven transactions.
Activity is concentrated early in the window: 7 transactions arrived during the 13:00 hour, 34 during 14:00, 47 during 15:00, 20 during 16:00, 42 during 17:00, and 31 during 18:00 UTC. There was then one transaction in each of the 19:00, 22:00, and 23:00 hours. That burst-and-pause pattern is consistent with a queued relaying process, although cadence alone does not prove automation or a shared operator.
Someone else paid every gas charge
All 184 transactions were sponsored by the same separate gas owner, 0x55d78c…a1edd5. The recorded gas total is 583,427,936 MIST, with each transaction charging 3,170,804 MIST. The sender and gas payer should not be treated as the same entity.
The system recorded no sender-bound movement entries for this address in this scope. That is missing movement evidence, not proof that no value moved. There are no prices or cross-asset accounting here, so this record cannot establish a payout, transfer amount, or profit.
What the record supports
The strongest description is narrow: this address repeatedly submitted the same CCTP-like five-call message-receive composition, with all gas sponsored by one other address, across a roughly ten-and-a-half-hour frozen window. The calls reached settlement-shaped steps, but the stored evidence withholds the complete purpose and any economic outcome.
Useful exits are 6Pk3iABz for the first observed attempt, 2kMtWvvx for the last, shape c047364558460e23307c46dd93ac170a3baf0f7ac6567b64ae5c09e4a4a05ba8, and package revisions 0x08d87d…f7ed1b and 0x2aa6c5…32b94e.