You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an Issuer,
I want to issue off-chain attestations through the SDK,
So that I can save on gas fees when the payload I want to attest is large
NOTE: The Offchain Schema is (bytes32 schemaId, string uri) with ID 0xa288e257097a4bed4166c002cb6911713edacc88e30b6cb2b0104df9c365327d
Currently, the SDK allows reading off-chain Attestations by fetching the off-chain payload from the uri field of the attested payload. If the payload is encoded (starting with 0x), the SDK decodes it by using the Schema declared in the schemaId field.
Now, we need to extend this functionality to support issuing off-chain Attestations via the SDK.
Acceptance Criteria:
Dedicated function for issuing off-chain Attestations:
The SDK will provide a dedicated function to handle off-chain attestations.
This function will push the off-chain payload to its destination (initially IPFS, with later support for Ceramic, Arweave, Greenfield, etc.).
Issuing an on-chain Attestation:
After uploading the off-chain payload, the SDK will issue an on-chain Attestation.
The uri field in the Attestation will contain the link to the off-chain payload.
The schemaId field will refer to the ID of the Schema describing the off-chain payload.
Schema validation: If the Schema describing the off-chain payload isn’t registered in the SchemaRegistry, an error will be thrown.
Timeout handling: Implement a timeout mechanism to handle cases where pushing the off-chain payload takes too long.
Issuer responsibility: The Issuer must provide all required credentials (e.g., API keys) to push the off-chain payload to the targeted service (e.g., IPFS).
Initial focus on IPFS: The first implementation will focus on issuing off-chain payloads to IPFS, with support for additional services (e.g., Ceramic) in future iterations.
Technical Notes:
The SDK should support retry logic for uploading the off-chain payload.
Consider edge cases like large payloads and timeouts for various services (IPFS, Ceramic, etc.).
Error messages should be clear and specific when Schema validation or payload upload fails.
The text was updated successfully, but these errors were encountered:
As an Issuer,
I want to issue off-chain attestations through the SDK,
So that I can save on gas fees when the payload I want to attest is large
NOTE: The Offchain Schema is
(bytes32 schemaId, string uri)
with ID0xa288e257097a4bed4166c002cb6911713edacc88e30b6cb2b0104df9c365327d
Currently, the SDK allows reading off-chain Attestations by fetching the off-chain payload from the
uri
field of the attested payload. If the payload is encoded (starting with0x
), the SDK decodes it by using the Schema declared in theschemaId
field.Now, we need to extend this functionality to support issuing off-chain Attestations via the SDK.
Acceptance Criteria:
uri
field in the Attestation will contain the link to the off-chain payload.schemaId
field will refer to the ID of the Schema describing the off-chain payload.Technical Notes:
The text was updated successfully, but these errors were encountered: