You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix invalid links to Walrus and zkLogin in README (#32)
* Fix invalid links to Walrus and zkLogin in README
Replaced previously invalid links for Walrus and zkLogin with valid URLs pointing to their official documentation to improve reference accuracy
* [Example app] Update Walrus services (#36)
---------
Co-authored-by: benr-ml <112846738+benr-ml@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Seal
2
2
3
-
Seal is a decentralized secrets management (DSM) service that relies on access control policies defined and validated on [Sui](https://docs.sui.io/concepts/components). Application developers and users can use Seal to secure sensitive data at rest on decentralized storage like [Walrus](https://docs.walrus.site/index.html), or on any other onchain / offchain storage.
3
+
Seal is a decentralized secrets management (DSM) service that relies on access control policies defined and validated on [Sui](https://docs.sui.io/concepts/components). Application developers and users can use Seal to secure sensitive data at rest on decentralized storage like [Walrus](https://docs.wal.app/), or on any other onchain / offchain storage.
4
4
5
5
> [!IMPORTANT]
6
6
> Seal Beta is in Testnet. Refer to the [Seal Beta Terms of Service](TermsOfService.md).
@@ -19,8 +19,8 @@ Seal is a decentralized secrets management (DSM) service that relies on access c
19
19
20
20
There are a number of Web3 use cases that could utilize Seal to secure sensitive data in a safe and scalable manner. Some of those are:
21
21
22
-
- Secure personal data on [Walrus](https://docs.walrus.site/index.html) or some other storage, such that it’s only accessible by the user who uploaded it.
23
-
- Share secure content stored on [Walrus](https://docs.walrus.site/index.html) or some other storage with a specific allowlist of users.
22
+
- Secure personal data on [Walrus](https://docs.wal.app/) or some other storage, such that it’s only accessible by the user who uploaded it.
23
+
- Share secure content stored on [Walrus](https://docs.wal.app/) or some other storage with a specific allowlist of users.
24
24
- Share gated content on a content subscription application with a verified list of subscribers.
25
25
- Realize end-to-end private messages using Sui and Walrus.
26
26
- Implement secure voting and MEV resilient trading in Move.
@@ -39,7 +39,7 @@ We’re looking for community feedback on what other capabilities would make sen
39
39
Even though Seal is supposed to be a generic and flexible secret management service for a variety of use cases, following are not its supposed goals. We do not recommend using Seal for such use cases and instead ask that you look for a more relevant product / service.
40
40
41
41
- Seal is not a key management service like [AWS KMS](https://aws.amazon.com/kms/) or any other such Web2 service, in the sense that Seal backends do not store any application or user specific keys. A Seal key server only stores its specific master key pair, where the master public key is used by users to encrypt sensitive data, and the master private key is used to derive identity-based keys to decrypt the data.
42
-
- Seal is not a privacy preserving technology like [zkLogin](https://docs.walrus.site/index.html). Instead Seal is supposed to be a collection of components allowing application developers and users to secure sensitive data on- or off-chain by using the security properties of threshold encryption, Sui, and Move.
42
+
- Seal is not a privacy preserving technology like [zkLogin](https://docs.sui.io/concepts/cryptography/zklogin). Instead Seal is supposed to be a collection of components allowing application developers and users to secure sensitive data on- or off-chain by using the security properties of threshold encryption, Sui, and Move.
43
43
- Seal should not be used to store highly sensitive data like a user’s wallet keys, or regulated personal data like PHI (personal health information), or any local / state / federal government-level secret data, or other data of similar sensitivity. Some advanced capabilities may be added to Seal in future to allow using it for some of such use cases, but those do not exist yet.
0 commit comments