Skip to main content

Node Permissioning Request

This document describes the procedure for requesting permissioning for an execution node within the ISBE network (dev, pre, or pro environments).
Permissioning is mandatory for a node to join the network's P2P and begin syncing.


1. Required Information

To request access, the participant must provide:

  • Node Name: <Node_Name>
  • Public IP: <NODE_IP>
  • Full Enode: enode://...
  • Environment: dev / pre / pro
  • Participating Entity: name of the requesting organization
  • Contact Person: name and email

The enode is generated during the node installation (see instalación-nodo-regular.md).


2. Request Procedure

  1. Prepare all the information above.
  2. Send the request through the channel indicated by the ISBE team (form or internal email).
  3. ISBE will validate:
    • the enode structure,
    • that the IP is accessible,
    • that the node belongs to an authorized use case.

If information is missing, ISBE will request corrections before proceeding.


3. Technical Validation by ISBE

The infrastructure team will perform:

  • Checking the enode and public keys.
  • Verification of P2P port accessibility (30303/tcp).
  • Integration of the node into the permissioning list of the corresponding environment.
  • Updating bootnodes and propagation in the network.

Once completed, the node will be able to join the ISBE topology.


4. Confirmation and Syncing

When permissioning is active, ISBE will send a formal confirmation.

The node should:

  • Automatically connect to the bootnodes,
  • Start receiving peers,
  • Sync block height with the network.

Check status with:

curl -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":1}' http://localhost:8545

5. Responsibilities of the Authorized Node

Once authorized, the participant is responsible for:

  • Keeping their node operational and updated.
  • Ensuring the security of the host server.
  • Avoiding anomalous behavior (massive transactions, spam, etc.).
  • Notifying ISBE of any changes in:
    • Public IP,
    • Node key,
    • Migrations or reinstallations.

6. Summary

Requested ParameterDescription
<Node_Name>Internal node name
<NODE_IP>Public IP accessible by the ISBE network
EnodeUnique node identifier
Environmentdev / pre / pro
ContactEntity technical contact

The permissioning process is essential to guarantee a secure and stable permissioned network.