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
  • Using a custom Module
  • Example
  1. Developer Guides
  2. For Attestation Issuers

Create a Module

PreviousCreate and register a SchemaNextRegister a Module

Last updated 5 months ago

are smart contracts that are registered in the "Module Registry" and that perform specific validation logic on attestations before they are issued into the registry.

Using a custom Module

A Module must implement the AbstractModuleV2 contract to be considered as valid by Verax. Hopefully, we provide all the core contracts of the Verax platform as an npm package to help developers create their own custom implementations.

  • Install the dependency: npm i @verax-attestation-registry/verax-contracts

  • Import the AbstractModuleV2 contract:

    import {AbstractModuleV2} from "@verax-attestation-registry/verax-contracts/contracts/abstracts/AbstractModuleV2.sol";
  • Define your custom Module:

    contract ExampleModule is AbstractModuleV2 { ... }

And now ... the floor is yours! You can add your custom functions, of course, but mostly you need to implement the run function that is called in the validation process, before registering the attestation payload.

When multiple Modules are used in a workflow, ensure that at most one Module processes msg.value to avoid accounting issues, as the total msg.value is forwarded to all Modules.

Example

// SPDX-License-Identifier: MIT
pragma solidity 0.8.21;

import {AbstractModule} from "@verax-attestation-registry/verax-contracts/contracts/abstracts/AbstractModule.sol";
import {AttestationPayload} from "@verax-attestation-registry/verax-contracts/contracts/types/Structs.sol";

contract ExampleModule is AbstractModule {

    error InsufficientFee();

    function run(
        AttestationPayload memory /*attestationPayload*/,
        bytes memory /*validationPayload*/,
        address /*initialCaller*/,
        uint256 value,
        address /*attester*/,
        address /*portal*/,
        OperationType /*operationType*/
    ) public pure override {
        if (value < 1000000000000000) revert InsufficientFee();
    }
}

This ExampleModule implements the AbstractModuleV2 contract.

In this example, we are checking that the paid value for this Attestation is at least 0.001 ETH. If it is the case, the process goes onto the next Module check, and if not, the process stops there and the transaction reverts.

♒
Modules