To submit a new OVIP, please open a PR. After copy-editing and acceptance, it will be published here.
OpenVASP is an open-source and community driven project. Thus anyone is encouraged to submit OVIPs and engage in discussion. Decisions on which OVIP proposal will be accepted and ratified will be made by a committee of members of the OpenVASP initiative. Having a OVIP here does not make it a formally accepted standard until its status becomes Final or Active.
We thank the Bitcoin community for introducing this process to handle standard improvement proposals, which the OVIP process follows in large parts.
| Number | Layer | Title | Owner | Type | Status |
|---|---|---|---|---|---|
| 1 | OVIP Purpose and Guidelines | Felix Laufenberg | Process | Accepted | |
| 2 | Virtual Assets Account Number (VAAN) | David Riegelnig | Standard | Accepted | |
| 3 | VASP Identity | David Riegelnig | Standard | Accepted | |
| 6 | Protocol messages cleanup | Nika Gamkrelidze | Standard | Superseded | |
| 7 | Session Layer | David Riegelnig | Standard | Accepted | |
| 9 | 6 Layers of OpenVASP | Felix Laufenberg | Standard | Accepted | |
| 10 | Whisper as Transport Layer | David Riegelnig | Standard | Accepted | |
| 11 | VASP Registries | David Riegelnig | Standard | Accepted | |
| 12 | VASP Directory | Felix Laufenberg | Standard | Accepted | |
| 13 | OpenVASP Core Data Types | David Riegelnig | Standard | Superseded | |
| 14 | Message Family: Transfer (TFR) | David Riegelnig | Standard | Accepted | |
| 15 | OpenVASP Credential | David Riegelnig | Standard | Accepted | |
| 16 | Waku for Message Layer | Felix Laufenberg | Standard | Accepted | |
| 17 | Increase InterVASP IVMS101 compatibility | Lucas Betschart | Standard | Accepted |