Network concepts
Before diving into the main Network concepts, check out the overview and see some sample use cases.
As a Network developer, you need to understand Nektar Network fundamentals and select the type of trust required before turning your idea into code. To become part of the restaking layer, you need to develop two software components:
- On-chain smart contracts define rewards and fee schedules, and slashing rules to incentivize Operators to act responsibly and honestly. These are deployed on the Ethereum mainnet.
- Off-chain client software executes tasks according to distributed validation semantics and implements Network functionality. Operators run this software on their infrastructure.
Together, these components support your distributed network with cryptoeconomic security from repurposed collateral and rented compute.
Smart Contracts
Smart contracts define your Network rules and maintain the state relevant to its operation. They orchestrate everything from task generation to validation and reward distribution.
These contracts connect to both core Nektar contracts and your client software. They must adhere to protocol specifications for restaking layer integration and emit provable events to trigger off-chain execution. Operators listen for tasks, perform computations, sign results, and submit them back to the Network contracts.
Successful verification of results leads to rewards for Operators as per the contract rules. Invalid proofs or task failures may result in penalties through slashing conditions.
Contracts can also register Network, allow Delegators to delegate to Operators, and implement other middleware functions as needed.
Client Software
Client software is an Network module, provided to Operators as a binary executable, that adheres to the Nektar node specification. It completes tasks, then writes events to smart contracts for verification, rewards, and other actions.
Arbitrary Tasks
A task is a unit of work Operators commit to performing for your Network, which can range from computing data to verifying transactions. Define and implement tasks in the client software, and integrate them with smart contracts for task creation and response logic. You can also implement logic for task challenging, allowing results to be disputed with a bond-supported challenge.
Provide your client software to Operators so they can run tasks on their nodes, implementing the off-chain infrastructure business logic and contributing to the network's security and integrity.
Delegated Stake
Your Network will use Nektar's restaking primitives and be validated by Nektar’s Operators, who are backed by delegated repurposed assets from Delegators.
Specify upfront the group of repurposed assets (e.g. ETH) that your Network will use for shared security measures. This helps Operators make informed choices when registering for your Network. This configuration evaluates a subset of the Operator's restaked tokens, determines a specific weight for the Operator, and checks if Network has reached consensus.
Operator Signatures
Signatures ensure the integrity and authenticity of operations in the Nektar network, verifying that tasks are accurately completed by Operators.
Off-chain values are computed as part of the work Operators signed up to perform, aligned with Network contract business logic. Multiple Operators perform and sign off-chain computations, aggregate signatures, and validate and write the values on-chain.
Operator signatures identify participants and hold them accountable.
Rewards and Penalties
Nektar allows Networks to distribute rewards to Operators and Delegators.
Operators earn rewards by opting into Networks and performing tasks, while Delegators provide the capital as delegated stake. Operators risk losing part of their staked asset if they breach obligations or behave maliciously.
You can customize rewards parameters and slashing conditions to define how Operators are compensated or penalized for services in your context.
Rewards are calculated off-chain regularly (period to be determined), while penalties occur in real-time, automatically, and on-chain.
Interaction flow
Network interaction flow:
