Smart Contracts in ISBE
Welcome to the ISBE Smart Contracts documentation. This section is designed to guide you from the first strategic decision to incident resolution in production, following a business and technical decision-oriented approach.
The documentation is organized into six main axes:
1. Choose your deployment modality
The decision with the greatest impact on control, effort, and pricing. Understand the differences between using the ISBE library, homologating your own contract, or performing a direct deployment.
2. Template Catalog
Is your asset fungible or unique? Do you need traceability or timestamping? Use our decision tree to find the pre-certified template (ERC20, ERC721, ERC3643, etc.) that best fits your use case.
3. Custom Contract Development
Full guide for when templates are not enough. Compliance requirements, homologation process (levels A, B, and C), and deliverables checklist.
4. Network Security and Governance
Understand the ISBE control model. Documentation on pausing mechanisms, address filtering, and why this model is the foundation of trust for regulated entities.
5. Practical Guides
Learn how to implement ISBE requirements with real code snippets. From advanced development with Diamond Storage to RBAC and basic pause.
6. Technical Reference
In-depth documentation for architects and advanced developers on the Diamond Pattern, the DID system, Core components, and governance infrastructure.
7. Problem Solving (FAQ)
Answers organized by project lifecycle: from doubts before deployment to incident management in production.
Recommended Workflow
- Select your Modality: Start by understanding how you will deploy. Modality 1 is recommended for most users.
- Consult the Catalog: Use the decision tree to see if a certified solution already exists.
- Validate Control Model: Review the governance model to ensure institutional compliance.
- Develop or Configure: Follow the technical guides based on your choice.
- Request Deployment: ISBE personnel will orchestrate the deployment after validating requirements.
Need help?
Consult our GitHub or contact the support team at soporte@redisbe.com