Marc-André Bombeck 4cd0adc46d docs(api): publish the factor-dependent reach of a step-up elevation ...

The contract now names which factors satisfy the fresh-factor routes and which
do not, carries `satisfiesFreshFactor` on the mint response so a client can pick
the ceremony before spending a proof, and describes the options endpoint's two
ceremony kinds. The second-factor status read is documented as plain
authentication — it carries no credential material, so it needs no elevation.

2026-07-19 14:29:34 +02:00

1.0 MiB

Raw Blame History