@@ -24,7 +24,7 @@ anyone as a Versioned Storage Service. It offers two core functionalities:
24
24
<img src =" http://www.plantuml.com/plantuml/png/VP2nJWCn44HxVyMKK4JqAQ8W8aGHA33GBxuXP-7p7lRUeVmzAz60X6YcsQTvezrtasRBL89bAyHBZBZBfn57hYmuY0bkYtw6SA-lkV30DITkTd1mY-l5HbRBIInhnIC_5dOBVjliVl9RT9ru8Ou_wJlhPGX5TSQRDhYddJ7BUV8cT8-hniIySlZJ-JmFOiJn0JUZrCg2Q6BybaRJ9YVwCjCff_zWUE7lZN59YRq7rY7iFVmhNm00 " />
25
25
</p >
26
26
27
- Clients can also use VSS for general metadata storage as well such as payment history, user metadata etc.
27
+ Clients can also use VSS for general metadata storage such as payment history, user metadata, etc.
28
28
29
29
### Motivation
30
30
@@ -37,18 +37,18 @@ data-integrity mechanisms. It even allows for the disabling of versioning altoge
37
37
making it simple to get started.
38
38
39
39
The project's design decisions prioritize features such as multi-device access, user privacy through client-side
40
- encryption(e.g. using key derived from bitcoin wallet), authorization mechanisms, data and version number verifiability,
40
+ encryption (e.g. using key derived from bitcoin wallet), authorization mechanisms, data and version number verifiability,
41
41
and modularity for seamless integration with different backend technologies.
42
42
43
43
### Modularity
44
44
45
- VSS can work out-of-box with minor configuration but is intended to be forked and customized based on the specific needs
45
+ VSS can work out-of-the- box with minor configuration but is intended to be forked and customized based on the specific needs
46
46
of wallet developers. This customization may include implementing custom authorization, encryption, or backend database
47
47
integration with different cloud providers. As long as the API contract is implemented correctly, wallets can
48
48
effortlessly switch between different instances of VSS.
49
49
50
- VSS ships with a PostgreSQL implementation by default and can be hosted in your favorite infrastructure/cloud provider (
51
- AWS/GCP) and its backend storage can be switched with some other implementation for KeyValueStore if needed.
50
+ VSS ships with a PostgreSQL implementation by default and can be hosted in your favorite infrastructure/cloud provider
51
+ ( AWS/GCP) and its backend storage can be switched with some other implementation for KeyValueStore if needed.
52
52
53
53
### Project Status
54
54
@@ -70,7 +70,7 @@ VSS is also integrated with [LDK-node] v0.4.x as alpha support.
70
70
71
71
### Development
72
72
73
- * ** Build & Deploy** : Refer to language specific folder for instructions related to build and deploy of VSS.
73
+ * ** Build & Deploy** : Refer to language- specific folder for instructions related to building and deploying VSS.
74
74
* ** Hosting** : VSS can either be self-hosted or deployed in the cloud. If a service provider is hosting VSS for multiple
75
75
users, it must be configured with ** HTTPS** , ** Authentication/Authorization** , and ** rate-limiting** .
76
76
* ** Authentication and Authorization** : Currently, the VSS-server
@@ -86,12 +86,11 @@ VSS is also integrated with [LDK-node] v0.4.x as alpha support.
86
86
``` rust
87
87
use ldk_node :: Builder ;
88
88
fn main () {
89
- let mut node_builder = Builder :: new ();
90
- ...
91
- let node = node_builder . build_with_vss_store_and_fixed_headers (vss_endpoint , store_id , HashMap :: new ()). unwrap ();
92
- node . start (). unwrap ();
93
- ...
94
- ...
89
+ let mut node_builder = Builder :: new ();
90
+ ...
91
+ let node = node_builder . build_with_vss_store_and_fixed_headers (vss_endpoint , store_id , HashMap :: new ()). unwrap ();
92
+ node . start (). unwrap ();
93
+ ...
95
94
}
96
95
```
97
96
* * * Using with Other Applications ** : VSS is designed to store application - related metadata . Clients can use
0 commit comments