Problem
Pricing implicitly assumes a single asset. Real buyers will want to settle in a
stablecoin (USDC on Stellar), some in XLM, and enterprise contracts may be
denominated in fiat terms even when settled in crypto. A single-asset assumption
baked into the rate model is expensive to remove later.
What to do
- Rates carry the asset they are denominated in.
- Support a denomination asset distinct from the settlement asset, with an
explicit conversion step.
- If conversion uses an oracle, treat that as a trust assumption and document
it: which oracle, what staleness bound, what happens when it is unavailable.
Prefer failing closed over settling at a stale rate.
- Per-payer preferred settlement asset.
Acceptance criteria
Notes
An oracle is a new trust assumption in a protocol whose value is
trustlessness — introduce it deliberately and say so publicly, or avoid it by
requiring rates to be denominated in the settlement asset.
Problem
Pricing implicitly assumes a single asset. Real buyers will want to settle in a
stablecoin (USDC on Stellar), some in XLM, and enterprise contracts may be
denominated in fiat terms even when settled in crypto. A single-asset assumption
baked into the rate model is expensive to remove later.
What to do
explicit conversion step.
it: which oracle, what staleness bound, what happens when it is unavailable.
Prefer failing closed over settling at a stale rate.
Acceptance criteria
Notes
An oracle is a new trust assumption in a protocol whose value is
trustlessness — introduce it deliberately and say so publicly, or avoid it by
requiring rates to be denominated in the settlement asset.