Skip to content

Dorac/ovips

 
 

Repository files navigation

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 Proposal
2 Virtual Assets Account Number (VAAN) David Riegelnig Standard Proposal
3 VASP Identity David Riegelnig Standard Proposal
6 Protocol messages cleanup Nika Gamkrelidze Standard Proposal
7 Session Layer David Riegelnig Standard Proposal
9 6 Layers of OpenVASP Felix Laufenberg Standard Proposal
10 Whisper as Transport Layer David Riegelnig Standard Proposal
11 VASP Registries David Riegelnig Standard Proposal
12 VASP Directory Felix Laufenberg Standard Proposal
13 OpenVASP Core Data Types David Riegelnig Standard Proposal
14 Message Family: Transfer (TFR) David Riegelnig Standard Proposal

About

OpenVASP improvement proposals

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published