Skip to main content

`GET /v1/parameter-values:viewEffective`

GET 
/v1/parameter-values:viewEffective

Results are served from a bounded TTL cache (design §10): the parameter-value write path is insert-only with effective_from, so a short TTL self-heals and no event-driven invalidation is needed. The posting money path never consults this cache - parameter resolution there is transactional by design (a stale fee rate is a correctness defect, not a latency trade).

resolve effective parameter value at a point in time, with hierarchy precedence (account > hierarchy > global).

Responses​

OK