-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Description
Problem
The API client expects a complete guardian-based social recovery system that doesn't exist in the ZHTP node.
Missing Endpoints (HIGH PRIORITY)
- POST /api/v1/guardian/add - Add a guardian
- GET /api/v1/guardian/list/{id} - List guardians for identity
- POST /api/v1/guardian/remove - Remove guardian
- POST /api/v1/guardian/accept - Accept guardian invite
- POST /api/v1/guardian/decline - Decline guardian invite
- POST /api/v1/guardian/recovery/initiate - Start recovery process
- POST /api/v1/guardian/recovery/approve - Guardian approves recovery
- GET /api/v1/guardian/recovery/status/{id} - Check recovery status
- POST /api/v1/guardian/recovery/cancel - Cancel recovery
Current Node Implementation
- NONE - Guardian subsystem entirely missing
Impact
- HIGH PRIORITY - Social recovery unavailable
- Users cannot add guardians for account security
- No multi-party account recovery
- Missing key security feature
Expected Behavior
POST /api/v1/guardian/add
- Request: { identity_id: string, guardian_id: string }
- Response: GuardianResponse with guardian info
- Should add guardian and send invite
GET /api/v1/guardian/list/{id}
- Response: Guardian array
- Should return all guardians for identity
POST /api/v1/guardian/recovery/initiate
- Request: { identity_id: string, guardian_ids: string array }
- Response: RecoverySession with recovery_id
- Should start recovery process requiring guardian approval
POST /api/v1/guardian/recovery/approve
- Request: { guardian_id: string, recovery_id: string, approval: boolean }
- Should record guardian approval for recovery
Implementation Location
ZHTP Node: New handler needed - zhtp/src/api/handlers/guardian/mod.rs
Priority
HIGH - Important security feature for alpha
Metadata
Metadata
Assignees
Labels
No labels