Flex Kit Attributes
Last updated
Last updated
Flex Kit attributes are non-primary attestations (e.g. not COUNTRY, AML, DID, etc) by an attestor on a subject. Any entity can be an attestor and can attest to any data points. Likewise, any single entity can query any attestation if they find it useful.
Write an attestation about a given account. On initial call, _sigAccount
is required and is the signature of the _account
over the message: "I authorize [ISSUER_ADDRESS] to attest to my address [ACCOUNT_ADDRESS]"
On subsequent calls, _sigAccount
can be omitted.
Set the query fee for a given attribute name. The input for attribute name must be the raw name (i.e. it must not be SHA3-256(ISSUER_ADDR | RAW_ATTR_NAME).
Set write access for an issuer on a user's specific attribute name. This will default to false initially so once called, the user must continue to manage this boolean for the given issuer/attribute pair.
The input for attribute name must be the hashed value (i.e. SHA3-256(ISSUSER_ADDR | RAW_ATTR_NAME).
Withdraw any funds from query fees.
The attribute key is the hash of the issuer address and the attribute name. This ensure that multiple issuers can re-use the same attribute name without collision.
The query functions are similar to the ones found in . The functions also accept primary attributes (i.e. COUNTRY, AML, DID, etc) and will fetch the results from the QuadReader.