Verax Attestation Registry
  • 👋Introduction
  • ⚒️Getting Started
  • Core Concepts
    • High-Level Overview
    • Attestations
    • Schemas
    • Linked Data
    • Modules
    • Portals
    • Ecosystem
  • Developer Guides
    • ♒For Attestation Issuers
      • Create and register a Schema
      • Create a Module
      • Register a Module
      • Create a Portal
      • Register a Portal
      • Create an Attestation
      • Encoding Attestation Data
      • Revoke an Attestation
      • Replace an Attestation
      • Link Attestations
      • Bulk Create Attestations
      • EAS compatibility
    • 🧑‍🏫Tutorials
      • From a Schema to an Attestation
      • Using Ceramic to store the Attestation Payload
    • 🚀Examples
    • 🌐Using the Subgraph
    • 🛠️Using the SDK
  • Discover
    • 📚Modules Standard Library
      • ECDSAModule
      • ERC1271Module
      • FeeModule
      • IndexerModule
      • IssuersModule
      • SchemaModule
      • SenderModule
    • 🤝Integrations
  • Get Involved
    • Get in Touch
    • Contribute
    • Governance
      • Governance Charter
      • Governance Parameters
      • Overview of Governance
      • Proposal Templates
Powered by GitBook
On this page
  1. Developer Guides
  2. For Attestation Issuers

Bulk Create Attestations

For certain use cases, issuers may want to create Zttestations in bulk to save on transaction fees.

The AbstractPortal contract that every Portal inherits from defines the following function:

function bulkAttest(
    AttestationPayload[] memory attestationsPayloads,
    bytes[][] memory validationPayloads
) public payable;

This function is like the normal attest function but with a couple of differences. First, it takes an array of AttestationPayload structs as the first parameter, each one corresponding to a single Attestation. Second, it takes a two-dimensional array of validationPayloads in the second parameter. The first dimension of the array is a validation payload for each respective Attestation payload, the second dimension is the validation payload for each module in the module chain, to verify the respective Attestation.

This method may have unexpected behavior if one of the checks is done on the Attestation ID, as this ID won't be incremented before the end of the transaction. If you need to check the attestation ID, please use the attest method.

PreviousLink AttestationsNextEAS compatibility

Last updated 9 months ago

♒