Orchestration: optimize timeoutHeight
parameter for transactions, queries, and transfers
#9324
Labels
timeoutHeight
parameter for transactions, queries, and transfers
#9324
What is the Problem Being Solved?
As an orchestration API developer, I want to make sure we arrive at the correct abstraction and default values for the
timeoutHeight: bigint
|timeoutTimestamp: bigint
parameter required for cross-chain transactions and queries.The following messages require this parameter, in some form or another, and will default to
0
/0n
if nothing is provided. When the value is0
, it seems this results in an unbound timeout. An unbound timeout can degrade DX + UX.timeoutHeight
andtimeoutTimestamp
fields (the generated TS types say both are required, but i think it's actually one or the other)height
field used for timing out a querytimeoutHeight
field used for timing out a tx messageDescription of the Design
revisionHeight
is somethingChainInfo
can reliably provideSecurity Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: