Optional
submitSubmit a signed permission grant transaction for relay
The EIP-712 typed data that was signed
The user's signature
Promise resolving to the transaction hash
Optional
submitSubmit a signed permission revocation transaction for relay
The EIP-712 typed data that was signed
The user's signature
Promise resolving to the transaction hash
Optional
submitSubmit a signed trust server transaction for relay
The EIP-712 typed data that was signed
The user's signature
Promise resolving to the transaction hash
Optional
submitSubmit a signed untrust server transaction for relay
The EIP-712 typed data that was signed
The user's signature
Promise resolving to the transaction hash
Optional
submitSubmit a file addition for relay
The file URL to register
The user's address
Promise resolving to object with fileId and transactionHash
Optional
submitSubmit a file addition with permissions for relay
The file URL to register
The user's address
Array of encrypted permissions
Promise resolving to object with fileId and transactionHash
Optional
submitSubmit a comprehensive file addition with optional schema and permissions for relay
This is the preferred callback that supports all file addition scenarios. It can handle files with schemas, permissions, or both.
Complete parameters for file addition
The file URL to register
The user's address
Array of encrypted permissions (empty array if none)
Schema ID for validation (0 if none)
Promise resolving to object with fileId and transactionHash
Optional
storeStore a grant file for relay (e.g., upload to IPFS)
Relayer callback functions for handling gasless transactions.
Instead of hardcoding HTTP/REST API calls, users can provide custom callback functions to handle transaction relay in any way they choose (HTTP, WebSocket, direct blockchain submission, etc.).
Example