SignedContextV1

Git Source

Typed embodiment of some context data with associated signer and signature. The signature MUST be over the packed encoded bytes of the context array, i.e. the context array concatenated as bytes without the length prefix, then hashed, then handled as per EIP-191 to produce a final hash to be signed. The calling contract (likely with the help of LibContext) is responsible for ensuring the authenticity of the signature, but not authorizing who can sign. IN ADDITION to authorisation of the signer to known-good entities the expression is also responsible for:

Enforcing the context is the expected data (e.g. with a domain separator)
Tracking and enforcing nonces if signed contexts are only usable one time
Tracking and enforcing uniqueness of signed data if relevant
Checking and enforcing expiry times if present and relevant in the context
Many other potential constraints that expressions may want to enforce EIP-1271 smart contract signatures are supported in addition to EOA signatures via. the Open Zeppelin SignatureChecker library, which is wrapped by LibContext.build. As smart contract signatures are checked onchain they CAN BE REVOKED AT ANY MOMENT as the smart contract can simply return false when it previously returned true.

struct SignedContextV1 {
    address signer;
    uint256[] context;
    bytes signature;
}

Properties

Name	Type	Description
`signer`	`address`	The account that produced the signature for `context`. The calling contract MUST authenticate that the signer produced the signature.
`context`	`uint256[]`	The signed data in a format that can be merged into a 2-dimensional context matrix as-is.
`signature`	`bytes`	The cryptographic signature for `context`. The calling contract MUST authenticate that the signature is valid for the `signer` and `context`.