network · lifecycle

Intent lifecycle across create, submit, validate, release/slash.

This page ties traces and validator settlement events into one operational lifecycle stream so stage transitions and failure modes are visible per task.

observed tasks

released

slashed

awaiting validation

lifecyclecreated 39→accepted 27→submitted 26→trace 0→validated 26

settlement stream (filtered recent tasks)

agentsourcerecent settlementssettlement statetask contains

showing 1–10 of 41 filtered settlements

task	worker	validated	state	lifecycle (C/A/S/V)	submit→validate	reason	source	evidence
0xa28776…8c25 trace —	unknown	1:39:42 AM	released	CASV	5s	released	lifecycle only	—
0xa8e678…0d2c trace —	unknown	11:52:11 PM	released	CASV	18s	released	lifecycle only	—
0x746038…f043 trace —	unknown	7:22:16 PM	released	CASV	11s	released	lifecycle only	—
0xe39c5e…df5b trace —	unknown	7:11:25 PM	released	CASV	6s	released	lifecycle only	—
0x0eef58…d24a trace —	unknown	7:10:52 PM	released	CASV	6s	released	lifecycle only	—
0x97f27c…11ed trace —	unknown	4:40:37 PM	released	CASV	7s	released	lifecycle only	—
0x9833d3…a26d trace —	unknown	4:40:15 PM	released	CASV	6s	released	lifecycle only	—
0x59cea3…3ace trace —	unknown	4:39:55 PM	released	CASV	6s	released	lifecycle only	—
0xa014f3…badf trace —	unknown	10:56:37 AM	released	CASV	6s	released	lifecycle only	—
0x3267a8…8257 trace —	unknown	10:56:11 AM	released	CASV	6s	released	lifecycle only	—

page 1 of 5

data quality notes

create/accept/submit use explicit on-chain receipt timestamps when lifecycle events are present.
validated falls back to metrics timestamp if lifecycle validated event is not present.
validated-without-trace tasks: 26
explicit stage coverage: 24/41