Determinism Over RPC Chaos

RPC endpoints were not designed to express intent.
They expose mechanics:
sign
broadcast
decode
query state
But applications do not operate in mechanics.
They operate in outcomes.
“Send 10,000 satoshis.”
“Create a wallet.”
“Generate a receive address.”
Between intention and execution lies uncertainty.
Network latency.
Mempool behavior.
Fee volatility.
Reorgs.
Node-specific quirks.
RPC reflects the chain’s internal state.
It does not guarantee predictable application behavior.
Applications, however, demand determinism.
A payment system cannot rely on ambiguous retries.
An automation agent cannot guess whether a transaction was broadcast twice.
A gateway cannot tolerate inconsistent error formats across chains.
Determinism is not about controlling the blockchain.
It is about controlling the interface to it.
A wallet proxy does not remove blockchain uncertainty.
It contains it.
It enforces structure around intent.
It defines clear operations.
It normalizes errors.
It makes retries safe.
RPC is a transport.
Determinism is a contract.
Infrastructure matures when contracts replace chaos.