Skip to main content

Modality 3: Direct Deployment

This modality is reserved for testing, development environments, or very specific use cases where there is no demanding sectoral regulation.

When to Choose It​

  • Projects in experimentation phase (PoC).
  • Use cases where an institutional guarantee from the network is not required.
  • When the Service Provider assumes full responsibility for the logic.

Step-by-Step Guide​

  1. Free Development: Develop your contract without strictly needing to follow ISBE's certified components.
  2. Binary Submission: Deliver the compiled code or deployment script to ISBE.
  3. Execution: ISBE performs the deployment under its technical responsibility.

What the Builder Delivers​

  • Binaries/Deployment Code: Files necessary for ISBE to execute the transaction.
  • Initialization Instructions: Parameters needed for the constructor or init functions.

What ISBE Returns​

  • Use Case Address: The unique entry point for your use case.

Control Implications​

In this modality, ISBE does not guarantee the existence of a PAUSER_ROLE under its control. Therefore, in a network emergency, ISBE can only act by requesting a pause from the Service Provider or, as a last resort, through address filtering at the node level, which is a much more aggressive measure with lower technical granularity.

See Network Security and Governance