Node Identity System

The Node Identity System is StarMiner’s decentralized framework for verifying, classifying, and managing node participants across the network including Compute Providers, Validators, and Oracles. It ensures that every node has a verifiable identity, and that trust within the network is rooted in transparent performance, not centralized gatekeeping.

By combining on-chain role registration, off-chain attestation, and reputation-based scoring, StarMiner creates a permissionless infrastructure mesh that is resilient, accountable, and open to global participation.

---

Purpose of the Node Identity System

• Authenticate and authorize node roles without KYC or centralized verification

• Differentiate node types (e.g., Provider, Validator, Oracle) with specific privileges and requirements

• Track historical performance to drive task routing, reward multipliers, and governance influence

• Enforce minimum security and operational standards (e.g., uptime, hardware spec, attestation compliance)

• Support slashing and reward throttling in case of misbehavior or performance degradation

---

Identity Lifecycle

1. Registration

   • Nodes register through a smart contract by submitting:

     • Wallet address

     • Hardware specs and performance benchmark

     • Desired role (e.g., compute, validation, data feed)

     • Optional: Region, energy source, TEE capability

   • A small stake of AGPU or AMAX may be required as a security deposit.

2. Verification

   • The protocol conducts automated and community-supported checks:

     • Resource validation (e.g., GPU benchmark matching)

     • Location ping testing

     • TEE or TPM attestation (if required for premium workloads)

   • Validators and Oracles may undergo deeper scrutiny with bonding and role governance approval.

3. Activation

   • Once verified, the node receives a unique on-chain identity token tied to its wallet and metadata.

   • This token grants the node access to job routing, role-specific rewards, and governance eligibility.

4. Reputation Tracking

   • All node actions are tracked via a real-time scoring system:

     • Uptime and SLA compliance

     • Job success/failure rates

     • Dispute records or slashing history

     • Participation in governance (if eligible)

   • Scores affect:

     • Task priority and eligibility

     • AGPU reward multipliers

     • Inclusion in premium job queues (e.g., ZKML, C2D, TEE)

5. Revocation or Penalties

   • Nodes that fall below minimum thresholds may face:

     • Reduced job assignments

     • Loss of multipliers

     • Temporary delisting

     • Slashing of staked collateral (for Validators or Oracles)

---

Multi-Role Identity Support

Nodes can hold multiple identities if qualified. For example:

• A high-performance compute provider may also act as an oracle for hardware availability.

• Validators may participate in governance as AMAX holders and serve on dispute resolution committees.

The protocol assigns role-specific permissions, while all roles are linked to a singular wallet and identity record.

---

Privacy and Security Considerations

• No personal data (e.g., name, IP, location) is required to register

• Metadata is hashed and optionally encrypted for sensitive workloads

• Nodes operating in high-risk or regulated jurisdictions can enable privacy flags, requesting obfuscation or regional routing exclusion

• Hardware attestation (e.g., Intel SGX) supports proof-of-trust without identity disclosure

---

Use in Governance and Task Routing

The Node Identity System plays a foundational role in:

• Governance Voting Weighting: Validator eligibility and voting reputation

• Reward Optimization: Dynamic earnings scaling based on trustworthiness

• Job Assignment Logic: Premium or sensitive workloads only go to top-ranked or role-verified nodes

This ensures that trust flows from performance not central approval.