anchor.diff:      "cn_uuid": "15966912-8fad-41cd-bd82-abe6468354b5",
       "guid": "97496DD1C8F053DE7450CD854D9C95B4",
       "pin": "123456",
  -    "recovery_token": "jmzbhT2PXczgber9jyOSApRP337gkshM7EqK5gOhAcg=",
  +    "recovery_tokens": [{
  +        "created": 123456789,
  +        "token": "jmzbhT2PXczgber9jyOSApRP337gkshM7EqK5gOhAcg="
  +    }, {
  +        "created": 2233445566,
  +        "token": "QmUgc3VyZSB0byBkcmluayB5b3VyIG92YWx0aW5l"
  +    }]
       "pubkeys": {
          "9e": "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYA...",
          "9d": "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYA...",
  
positive.code: | Yes
  | The pin of the provisioned token.
  
  | recovery_token
  | Yes
  | The recovery token used to recover the encryption keys of a zpool protected
  by this token.  Also used when replacing a token.
  
  | pubkeys
  | Yes
  
negative.code: 
  #### Interaction: ZFS
  
  After setup has completed kbmd will manage the `rfd77:config` ZFS property on
  the pool itself directly. This will be read during boot and written during
  recovery or rekeying. kbmd itself will also make the libzfs call to provide
  key material to the pool during the unlock process (since it needs to do this
  