Context
call_args (migrations/0015_extrinsic_call_args.sql) already stores substrate-interface's
decoded JSON for every extrinsic, including presumably-nested structures for Utility.batch/
Multisig.asMulti/Proxy.proxy — but no code anywhere renders or flattens these specially
(grep across src/, workers/, apps/ui/src for "multisig"/"proxy call"/"nested call" returns
nothing but unrelated hits). This is purely a decode/render gap, not a capture gap.
Deliverables
See linked sub-issues 4.1 through 4.4.
Expected outcome
Batch calls, multisig approval chains, and proxy real-account substitution all render clearly
on the extrinsic detail page instead of showing opaque nested JSON.
maintainer-only.
Context
call_args(migrations/0015_extrinsic_call_args.sql) already stores substrate-interface'sdecoded JSON for every extrinsic, including presumably-nested structures for
Utility.batch/Multisig.asMulti/Proxy.proxy— but no code anywhere renders or flattens these specially(grep across
src/,workers/,apps/ui/srcfor "multisig"/"proxy call"/"nested call" returnsnothing but unrelated hits). This is purely a decode/render gap, not a capture gap.
Deliverables
See linked sub-issues 4.1 through 4.4.
Expected outcome
Batch calls, multisig approval chains, and proxy real-account substitution all render clearly
on the extrinsic detail page instead of showing opaque nested JSON.
maintainer-only.