Validator Scheme

Embedded within our platform's core is an intricate Validator Scheme, designed to fortify the withdrawal process with an unyielding layer of security. This framework delineates the strategic interconnection of several pivotal components: the Withdraw Signing API, a continuous scan for withdrawal requests, an Orders Database, and the Public Orders API.

Withdraw Signing API

This API is the keystone of the withdrawal authorization process. It perpetually scans for new withdrawal requests, forming the front line in the defense against unauthorized transactions.

Continuous Validation Process

Validators, denoted as Validator N, Validator N+1, and Validator N+2, are in perpetual vigilance. These sentinels of the system independently scour for new withdrawal requests, each maintaining their distinct, isolated orders data repository

Verification and Security Protocol

  • Upon detection of a new withdrawal request, each validator engages in a meticulous verification process. Utilizing its separately stored orders data, the validator ascertains the legitimacy of the request against a backdrop of historical order data.
  • These validators operate in stealth, shrouded from the public internet. They are dispersed across diverse hostings and are accessible only through disparate accounts, ensuring that pinpointing their IP addresses becomes a Sisyphean task, absent direct access to the office computer with deployment scripts.

Legitimacy Confirmation

Only upon affirmative validation does the withdrawal request receive the digital signature of approval. This signature is the quintessence of transaction legitimacy, ensuring that only validated requests reach the finality of execution.

API Integration and User Interface

  • The validated withdrawal request, now securely signed, is transmitted back to the user through the API. This marks the culmination of a rigorous, multi-tiered security protocol that upholds the sanctity of the user's assets.
This validator scheme is the embodiment of our platform's commitment to security, operational transparency, and architectural resilience. It is meticulously engineered to safeguard against any vector of compromise, thereby cementing user trust and maintaining the integrity of the transactional ecosystem.