Understand NexaID

NexaID is fundamental layer of the zkTLS protocols that provides decentralized security and robustness, with driving the demand for data verifications and monetizations.

​

Roles of The Network

​

1. Attestor Node

An attestor node is a computing node of the NexaID, which forms a secure computation layer for executing zkTLS protocol. The attestor node is designated to run zkTLS tasks with zkTLS software including web version (NexaID extension) and mobile versions (NexaID AppClips and NexaID Instant Apps) on indicated data sources. For security consideration , the attestor node runs inside a Trusted Execution Environment (TEE), ensuring runtime integrity and providing stronger version control. Any operator of the attestor node is required to stake a certain amount of tokens as collateral to secure his participation in the network activities. The attestor can earn incomes on successfully running the network task. If the zkTLS task is not run correctly, it will also be punished.

​

2. Developer

A developer within NexaID builds zkTLS app by utilizing NexaID SDK.

​

3. Client

A client is an end user who directly allocates a zkTLS task to the network through a dapp built by a developer.

​

Network Architecture and Workflow

The NexaID system contracts act as the core hub and the dispatcher to manage the network activities. They need to handle fee settlement, stakings, rewards, and penalties about zkTLS tasks. In the network, normally a session starts with a task created by a client. The task is sent to the contracts to be processed by the network attestors. Within the task session, a selected attestor will perform a chosen zkTLS protocol (MPC Mode or Proxy Mode) with the client, to verify the web data which is specified in the task (dapp) and issue zkTLS proofs. Another core component is NexaID SDK, which is used implicitly in the network activities. The SDK is normally integrated and used by the zkTLS dapps, to send tasks to the contracts and locate the selected attestor. The SDK is the true vehicle to run the zkTLS protocol with the attestor, and create the related zkTLS proofs.

​

Network Economics

Clients shall pay task fees with crypto tokens to the verification service provided by the network. The fee shall be paid to the system contracts prior to the task execution. The fees from the executed task will be shared by the attestor which actually runs the zkTLS session with the client, and the protocol. Attestor shall stake a certain number of tokens and waits for a while before it can onboard as an official node. Attestor will have to wait for a certain period to exit the staking before returning the locked funds.

​

Penalties

If an attestor does not execute the zkTLS protocol honestly and instead arbitrarily signs on the zkTLS session, penalties will apply. The correctness of the protocol execution is validated through TEE attestation. If a node’s instability leads to execution failures or timeouts, the task output must be reported to the system contracts. A pre-defined threshold will determine whether penalties apply: within a given time window, a certain failure rate may be tolerated without punishment, while exceeding a specified timeout rate will trigger penalties. The penalty mechanism is designed as an incremental means of network security, and will not be introduced on the first day of the mainnet launch. In the staging phases, there will be no penalty mechanism, only authorized nodes will be allowed to join the network. When the penalty mechanism is formally introduced, task execution will be verified through TEE attestations, ensuring that correctness of the cryptographic operations can be enforced and validated.

​

Network Governance

The governance mechanism will primarily be responsible for network upgrades, parameter adjustments, and other key decisions affecting the system. In the early stages, governance will not be activated, allowing the network to focus on stability and adoption. Once introduced, governance will cover parameters such as the minimum staking requirement for attestor nodes, the unbonding period for attestor nodes, the minimum staking requirement for clients, the unbonding period for regular stakers, and the allowable range for the proportion of staking rewards distributed by regular stakers to their delegated attestor nodes.