Skip to content

🔐 PR 13: Institutional Custody & Escrow Vaults (223, 246) #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ze0ro99 wants to merge 1 commit into
base: main
Choose a base branch
from
+29 −0
Open

🔐 PR 13: Institutional Custody & Escrow Vaults (223, 246) #128

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/PiRC-223-Institutional-Custody.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# PiRC-223: Multi-Signature Institutional Custody
Defines a secure vault for institutional participants requiring $M$ of $N$ signatures based on PiRC-209 verified DIDs.
---
## 3. Reference Smart Contracts
**Solidity**: `contracts/PiRC223InstitutionalCustody.sol`
**Soroban**: `contracts/soroban/src/custody.rs`

**Status**: Ready.
21 changes: 21 additions & 0 deletions docs/PiRC-246-Institutional-Escrow-Vaults.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# PiRC-246: Institutional Escrow Vaults

## 1. Executive Summary
This standard defines secure, multi-signature institutional escrow vaults. It ensures that large-scale wholesale capital transfers are held in trust until predefined cryptographic conditions (e.g., PiRC-245 settlement batching or PiRC-214 Oracle triggers) are met.

**Dependencies**: PiRC-209, PiRC-228
**Status**: Complete reference implementation

## 2. Architecture
- Multi-signature approval mechanisms
- Time-locked and condition-locked escrow
- Integration with Justice Engine for dispute resolution

## 3. Reference Smart Contracts
**Solidity**: `contracts/PiRC246EscrowVault.sol`
**Soroban**: `contracts/soroban/src/escrow_vault.rs`

## 4. Implementation Roadmap
- Phase 1: Multi-sig and time-lock logic
- Phase 2: Oracle-based condition triggers
- Phase 3: Justice Engine dispute integration