For the frozen Sui window on 2026-07-19, this sender submitted 34,869 transactions over roughly ten hours and thirty-six minutes. Every one was sponsored: a separate gas-owner address covered the transaction. The activity is highly repetitive, but its economic outcome remains deliberately narrow.
The rhythm of a configured strategy
Across the complete history, 22,136 transactions asserted the behavior execute-configured-strategy—99.28% of the 22,296 rows that received a transaction-level structural explanation, or 63.48% of all eligible transactions. The remaining 12,573 rows did not receive a named transaction-wide purpose.
The cadence is striking. The whole-history median gap was 234 milliseconds, the 90th-percentile gap was about 3.1 seconds, and the longest idle period was 13.9 seconds. The busiest minute was 18:08 UTC, with 617 transactions. The longest uninterrupted run of successful execution records was 2,660 transactions. This is consistent with a continuously operating automated process, though the evidence does not establish who operated it or whether the activity was profitable.
The latest-500 stream is a concentrated snapshot of the same pattern. From 23:27:35.550 to 23:37:42.097 UTC, 495 rows carried the named strategy interpretation and five failed at the same call. Their median gap was 214 milliseconds.
What the strategy label does—and does not—mean
The reusable pattern sui/execute-configured-strategy/roster-f0003/v1 points to a configured-strategy coordinator on revision 0xa6d0bd…f66af7. The contract analysis describes that revision as an execution wrapper forwarding SUI, DeepBook, pool, reward, configuration, clock, and numeric-control objects to a linked implementation identified as stonker.
That establishes a strategy-execution attempt, not a specific swap, arbitrage trade, venue action, or profit. The wrapper does not reveal which conditional path the downstream implementation selected.
The failures repeat too
In the complete history, 164 transactions failed. 160 of those—97.56% of all failures—stopped at the same verification call. Four failures had no recorded abort site.
The representative latest-stream failure 6fn9hDUZ shows the boundary clearly: it attempted a four-step transaction, aborted at step zero with a Move abort, rolled back application changes, and never ran the remaining three steps. Reaching that call proves an attempt, not a completed strategy action.
Sponsored execution, but no attributed asset movement
The complete-history value-flow record contains no sender-attributed asset movements. The latest 500 rows likewise contain no movement records. This does not prove that no tokens moved elsewhere in the transaction; it means the stored evidence does not attribute movements to this sender.
The complete history accumulated 97,557,711,020 MIST in net gas charges. Three separate gas-owner addresses appear: one on 34,625 rows, with two others covering the remaining 244. The sender itself is an on-chain identity, not a proven person, company, operator, or bot.
Where to look next
CFrryxAS is an ordinary named strategy attempt near the start of the latest-500 stream. 6fn9hDUZ is the useful failure exception. N3MZN8wi is the final recorded named attempt at checkpoint 300615185. Together they show the dossier’s central pattern: machine-like repetition, sponsored gas, a stable failure site, and no proven exchange outcome or sender-level asset flow.