Description
In the past, we've discussed block heights (whether as a new CAIP or as a "query parameter"). A more fundamental use case might be addressing across multiple namespaces a specific transaction, i.e. on both sides of an atomic swap or bridging transaction.
Another possible use-case, whether for the same or a separate CAIP, would be addressing the metadata of a specific transaction, such as transaction type, or even arbitrary metadata like input data, method calls, memos, etc. This could a path (i.e. another : followed by, say parameters[0] in the case of input data), a query param, or a separate CAIP. Would like to hear from more implementers before committing to anything that might be un-profilable or un-implementable on many namespaces, tho!
Perhaps related issue: How would we unambiguously address miner's/validators messages in blocks, i.e., The Times 03/Jan/2009 Chancellor on brink of second bailout for banks.? straightforward pathing bip122:000000000019d6689c085ae165831e93:666666:op_return or bip122:000000000019d6689c085ae165831e93:op_return/666666 by analogy to CAIP-19 syntax ?
Shout out to @sposth for raising this.