Modality 1: Proxy Diamond with ISBE library
This is the recommended modality for most institutional use cases in ISBE. It leverages the Diamond pattern (EIP-2535) along with ISBE-certified standard libraries.
Key Advantages
- Preferred Pricing: Thanks to the maximum control guarantees for the network.
- Automatic Compliance: By using components already certified by ISBE, the homologation process for base logic is drastically streamlined.
- Low Development Effort: You only configure and deploy.
Step-by-Step Guide
- Access Control (RBAC): Configure initial roles (Admin, Operator, etc.) integrated with DIDs.
- Pausability: Ensure critical functions use the
whenNotPausedmodifier from the ISBE library. - Storage Integrity: Use the certified unstructured storage pattern from the library to prevent collisions.
- Traceability Events: Define standard events for auditing and action tracking.
- Testing and Analysis: Run the suite of unit and integration tests on the chosen configuration.
- Reproducible Build: Generate the necessary metadata and scripts for a deterministic build.
What the Builder Delivers
For this modality, the Builder must provide a project (Hardhat or Foundry) configured according to the following standards:
- Dependencies: Verification of the correct integration of
isbe-contracts. - Inheritance: Exclusive use of
DidDocumentDetailedInternal, omitting standardAccessControlandPausableimplementations from OpenZeppelin. - Storage: Comprehensive validation of storage integrity to prevent collisions between facets.
- Pausability: Mandatory implementation of certified pause mechanisms.
- Deployment Logic: Restriction on deploying contracts from within the logic; all creations must be channeled through the ISBE infrastructure.
- Method Exposure: Every public method must be properly annotated and cross-checked. If not, the integration of a whitelist will be required.
- Introspection: Implementation of
IEIP2535Introspectionto ensure full compatibility with theProxyIsbe.
What ISBE Returns
- Use Case Address: The unique entry point for your use case.
Control Implications
In this modality, ISBE maintains an irrevocable PAUSER_ROLE. This allows network governance to act immediately in response to serious incidents to protect asset integrity.