Chapter 4 · Controller asks · Approver signs

Switching it on needs a signature.

Turning on enforcement is a policy change, so a named person signs the exact change first.

This chapter starts where chapters 1–3 leave off. Catch up in one go: the steps that are not signatures run for you, and your device asks once — the same signatures those chapters make.

  1. 1Connectruns for you
  2. 2Shadowruns for you
  3. 3Keyyour device signs
Behind this chapter
  1. Your AP system
  2. Connector
  3. Avouch
  4. Approver’s device
  5. Public log
  6. Anyone
  1. change to signAvouch → Approver’s device Sends the exact policy change to sign.Not yet
  2. signatureApprover’s device → Avouch Signs it.Not yet
  3. receiptAvouch → Public log Appends the receipt to the public log.Not yet
  4. now enforcingAvouch Switches payment approvals from shadow to enforce.Not yet
AvouchPolicy change request

Sign this change

Payment approvals

Shadow → Enforce

Nothing to sign yet. When the controller asks, the exact change appears here.

Drawn as a phone. The key itself is in this device’s own authenticator.