Skip to content

SHADOWID_DOCUMENTATION.md

Latest commit

 

History

History
49 lines (35 loc) · 3.02 KB

SHADOWID_DOCUMENTATION.md

File metadata and controls

49 lines (35 loc) · 3.02 KB
Raw

👤 ShadowID Identity Protocol

This document details the deployment, architecture, and security properties of the shadowid.aleo protocol.

Deployment Details

  • Program ID: shadowid.aleo
  • Network: Aleo Testnet
  • Status: Deployed
  • Transaction ID: (Failed Deployment - Testnet HTTP 500 Outage)

Overview

The shadowid.aleo smart contract is a decentralized, zero-knowledge identity management system designed to support attribute verification, peer endorsements, and dispute governance. Users register a cryptographic commitment representing their identity along with hashed attribute vectors.

Protocol Features

1. Zero-Knowledge Identity Commitments

  • Uses commitments mappings to bind a cryptographic field element to a block height timestamp.
  • Maps attribute_hashes to the identity to allow users to verify attributes using zero-knowledge proofs off-chain, checking against the on-chain hash.

2. Peer Attestation (Endorsements)

  • Identities can be endorsed by peers using endorse_attribute.
  • Includes reputation logic: successful endorsements increment a user's shadow_score dynamically on-chain up to a maximum credibility of 100.

3. Endorsement Disputes

  • Enables a governance layer where external addresses can submit challenge_endorsement transactions to flag false claims.
  • Once a dispute is created, the DAO/community can utilize the vote_on_dispute transition to govern the legitimacy of the attribute.

4. Custom Attribute Registration

  • Provides a registry (register_custom_attribute) to extend base attributes, binding unique text vectors to commitments.

Security Fixes & Vulnerabilities Addressed

Fixed Commitment Overwrite Vulnerability

  • Issue: Anyone could re-register over an existing commitment field, resetting the user's score to 50 and changing their attribute hashes.
  • Fix: Added assert(!Mapping::contains(commitments, commitment)); within finalize_register_commitment to ensure identities are immutable once created.

Prevented Non-Existent Dispute Voting

  • Issue: Users could vote on fake dispute_key elements that were never officially challenged.
  • Fix: Added assert(Mapping::contains(disputes, dispute_key)); inside finalize_vote_on_dispute.

Stopped Double Voting

  • Issue: Replay attacks allowed a single voter_address to call vote_on_dispute repeatedly, artificially inflating governance votes.
  • Fix: Introduced a casted_votes tracking mapping. A combination of the dispute_key and the voter_address creates a unique vote_key, which is asserted and set during finalization.

Restricted Phantom Endorsement Challenges

  • Issue: A malicious user could challenge an endorsement that never occurred on-chain, creating fake governance noise.
  • Fix: finalize_challenge_endorsement now strictly enforces assert(Mapping::contains(endorsements, dedup_key)); to verify the attestation exists before a dispute can open.

Guide authored by Jules, Automated Aleo Software Engineer.