# Extropy Engine — 63 Known Gaps (v3.1 reference index)

**Part of:** Extropy Engine v3.1
**Status:** Living document. Each gap is an issue to be resolved through implementation, governance, or further spec work.

Gaps are grouped into 13 categories. Each entry is a *known* unresolved question identified during the v3.0 → v3.1 stress test. Counts in parentheses are the number of gaps in that category.

---

## [identity] Identity & DID (6)

1. Genesis-key compromise before any social-recovery guardians are designated.
2. Cross-context reputation correlation → de-anonymization risk.
3. Verifiable-credential issuer revocation propagation.
4. DID portability across substrate forks.
5. Long-tail of dormant DIDs and reputation decay rules.
6. Pseudonym ↔ legal-identity bridge for off-chain enforcement (deliberately not specified).

## [psll] PSLL (5)

7. Storage growth bound for high-activity users.
8. Encrypted-private-note key escrow on social recovery.
9. Multi-device write reconciliation.
10. Selective-disclosure proof library choice.
11. Export bundle format versioning.

## [handshake] Handshake protocol (5)

12. Capability-token replay across contexts.
13. Asymmetric-capacity DoS by well-resourced peers.
14. Handshake timeout defaults across latency regimes.
15. Counter-offer semantics formalization.
16. Multi-party (>2) handshake composition.

## [quest] Quest market (6)

17. Sponsor-attestor collusion detection beyond dispute quests.
18. Quest-completion verification for off-chain real-world tasks.
19. Stake decay function parameters.
20. Cross-context quest portability.
21. Solver discoverability for niche reputation contexts.
22. Quest cancellation by sponsor mid-flight.

## [reputation] Reputation system (5)

23. Reputation-vector dimensionality bound.
24. Sybil cost calibration over time.
25. Slashing appeal mechanics.
26. Reputation transferability on legitimate identity migration.
27. Cold-start onboarding curve.

## [substrate] Substrate / Holochain (5)

28. DHT shard-fault behavior under partition.
29. Source-chain validation rule upgrades.
30. Membrane (capability) revocation latency.
31. Bridging to non-Holochain peers.
32. Performance ceiling at network scale.

## [gov] Governance (5)

33. Voter-apathy quorum failure recovery.
34. Proposal-spam prevention beyond reputation cost.
35. Constitutional changes vs ordinary changes boundary.
36. Audit-window challenge mechanics.
37. Cross-context proposals (touching >1 scope).

## [ux] UX / PAI surface (4)

38. PAI hallucination on consequential signed actions.
39. Explanation surface for reputation deltas.
40. Onboarding without prior reputation.
41. Accessibility for non-technical users.

## [privacy] Privacy & disclosure (4)

42. Traffic-analysis correlation across published claims.
43. Long-term anonymity-set erosion.
44. Selective disclosure for *negative* claims.
45. PAI provider as side-channel.

## [security] Security (5)

46. PAI prompt-injection from incoming handshakes.
47. Malicious capability-token grants.
48. Eclipse attacks on the DHT.
49. Key-rotation race conditions.
50. Supply-chain risk for PAI runtimes.

## [economics] Economics & incentives (5)

51. Reputation inflation/deflation control.
52. Cross-domain reputation arbitrage.
53. Free-rider attestor problem.
54. Bootstrap incentives without monetary tokens.
55. Interaction with external monetary systems (deliberately minimized).

## [legal] Legal / jurisdictional (4)

56. Pseudonymous-identity legal recognition.
57. Liability surface for attestors of harmful claims.
58. Cross-border data-locality for PSLL hosting.
59. Compliance interfaces (when users opt-in).

## [process] Process & spec hygiene (4)

60. Versioning policy for breaking spec changes.
61. Deprecation pathway for obsolete reputation contexts.
62. Reference-implementation conformance test suite.
63. Documentation localization.

---

## How to use this list

- Each gap is intended to become a tracked issue (GitHub `#7..#69`-style range).
- v3.1 ships *despite* these gaps; they are explicitly known and bounded.
- Resolutions should reference back to this file and update the corresponding entry's status.