Skip to main content

FAQ - ISBE Client

General Questions​

What is the ISBE Client?​

The ISBE Client is the only way to access the ISBE blockchain network. It acts as a mandatory control layer that validates and filters all operations before they reach the Besu nodes.

Why is it necessary to use the ISBE Client?​

For three main reasons:

  1. Regulatory compliance: Helps with GDPR compliance through granular filtering and traceability.
  2. Security: Prevents unauthorized access and improper operations.
  3. Access control: Allows managing which operations are permitted on the network.

Can I access a Besu node directly without going through the ISBE Client?​

No. The ISBE Client is the only way to communicate with the network. Besu nodes are configured to accept connections only from the ISBE Client.

Filtering and Validation​

What types of operations can be filtered?​

The client can filter:

  • Specific transactions by hash.
  • Full contracts.
  • Specific functions in any contract.
  • Specific functions of a particular contract.
  • Specific JSON-RPC methods.

Are filters permanent?​

Not necessarily. Each filter can have:

  • Permanent filter: No time limit (endBlock = 0).
  • Temporal filter: Active from initialBlock to endBlock.

This allows for applying temporal restrictions, for example, during security incidents.

Why is access to my transaction blocked?​

If you receive a 403 error, it may be due to:

  • The transaction is blocked by privacy policies (GDPR).
  • The associated contract is under maintenance or disabled.
  • The function you are trying to query is restricted.
  • There is a temporal filter active due to a security incident.