For roughly ten and a half hours, this address behaved less like a general-purpose wallet than a metronome for price-feed maintenance: 24,953 of its 24,954 semantically explained transactions asserted update-price. The cadence and repetition are consistent with highly orchestrated execution, but the evidence does not establish who operated the address or whether any resulting prices were current or correct.
The routine
[Whole history] The address submitted 24,956 transactions between 13:01:51 and 23:37:31 UTC. Twenty-four thousand nine hundred fifty-four received a semantic explanation, and none failed. The median gap was 0 ms because many transactions share timestamps; the mean gap was 1.53 seconds, the 90th-percentile gap was 10.42 seconds, and the longest idle period was 30.8 seconds. Its busiest minute was 19:34 UTC, with 61 transactions.
[Whole history] The repertoire barely changed across the window. The dominant three-update workflow appeared 23,803 times, while a batch variant appeared 1,150 times. The only other explained behavior was one native-asset transfer. Two transactions fell outside the explained behavior counts.
The dominant workflow is concrete rather than merely nominal. In 3ULrikuq, the transaction verified an incoming cross-chain message, built authenticated Pyth price information, split fee funding, ran three price-related calls, and cleaned up the temporary container. Its sender movement was −0.000904695 SUI. The same seven-step structure appears again in the final observed transaction, E1X8dU83.
That proves the workflow executed. It does not prove that a stored feed changed: the explanation explicitly leaves the freshness and correctness of the resulting price unresolved.
The exception
[Whole history] The rare deviation was AuVqdrE5, a transfer-assets transaction with a net balance change of −0.296509880 SUI. It split native assets and transferred the resulting objects to a resolved recipient. The record does not establish that the recipient was distinct from the sender, so this should not be described as a confirmed external payment.
The cost
[Whole history] All observed gas was paid by the address itself; none of the 24,956 transactions was sponsored. The gas accounting view records 22.451759176 SUI out and 0.293216240 SUI in, for a net of −22.158542936 SUI. The separate sender-balance view records 22.451832240 SUI out and the same 0.293216240 SUI in, for a net of −22.158616 SUI. These views overlap and must not be added together.
The evidence contains only SUI movements and no prices, so it cannot establish profit, loss, or the economic value of any price-feed update.
What the latest stream shows
[Latest 500 explained transactions] The capped stream covers 13:25:08–23:37:31 UTC. Every row was explained, none failed, and the rows inspected carry the same update-price repertoire. In other words, the recent slice is not a change of character; it is the tail end of the same repetitive maintenance pattern.
The address is an on-chain identity, not a proven person, company, operator, or bot. Its strongest observable character is narrower: sustained, highly regular execution of two closely related Pyth price-update workflows, with one isolated asset-transfer deviation.
Further reading: 3ULrikuq for the first workflow, E1X8dU83 for the last, AuVqdrE5 for the exception, and patterns sui/update-price/verified-accumulator-three-update/v1 and sui/update-price/verified-accumulator-batch/v1 for the reusable mechanisms. The workflows call Pyth revision 0x04e20ddf36af412a4096f9014f4a565af9e812db9a05cc40254846cf6ed0ad91 alongside revision 0x5306f64e312b581766351c07af79c72fcb1cd25147157fdc2f8ad76de9a3fb6a.