Key Registry - Veilify

An inbox key is the public key a user registers so others can send to them. In the contract ABI it is the ReceivingKey struct.

registerReceivingKey

function registerReceivingKey(ReceivingKey calldata rk) public;

Checks

Check	Error
`address(keccak256(pkX ‖ pkY)) == msg.sender`	`NotAccountOwner(caller, expected)`
First 20 bytes of `keyData` == that address	`KeyDataAddressMismatch`
`pnk`, `ekX`, `ekY` < field modulus	`InvalidReceivingKey`
`(ekX, ekY)` on Grumpkin	`EncryptionKeyNotOnCurve`
Address has no other key	`KeyRotationTooSoon(type(uint256).max)`

Behaviour

Idempotent. Registering the same key again returns without changes.
Final. A different key for the same address is refused, forever.
On success: inserts rkHash into the key-registry tree and emits ReceivingKeyRegistered.

event ReceivingKeyRegistered(
    address indexed account,
    uint256 indexed index,
    uint256 hash,
    bytes32 pkX, bytes32 pkY, bytes32 keyData,
    bytes32 pnk, bytes32 ekX, bytes32 ekY
);

KEY_ROTATION_COOLDOWN, receivingKeyRotatableAt and ReceivingKeyRotated stay in the ABI for client compatibility. Rotation is disabled: receivingKeyRotatableAt returns 0 for unregistered addresses and type(uint256).max otherwise.

Views

Function	Returns
`hasReceivingKey(address)`	Whether the address registered
`_addressToReceivingKeyHash(address)`	Its `rkHash`
`keyRegistryRoot()`	Current registry root
`keyRegistrySize()`	Number of registered keys
`isKnownKeyRegistryRoot(uint256)`	Whether a root was ever valid
`isReceivingKeyRegistered(uint256 leaf)`	Whether an `rkHash` is in the tree
`receivingKeyUpdatedAt(address)`	Registration timestamp