Skip to content

Commit

Permalink
Update introduction-self-custody.mdx
Browse files Browse the repository at this point in the history
Signed-off-by: dubravkoMC <[email protected]>
  • Loading branch information
dubravkoMC authored Jun 5, 2024
1 parent cf19b84 commit 0cd625c
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions pages/service/introduction-self-custody.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,22 @@ title: Self-custody

# Introduction to self-custody (beta)

Through our new self-custody implementation, you are able to set up self-custodial users with Beam. The implementation is a new service that works based on self-custodial private keys, and newly deployed account abstractions. Existing [Profiles](/service/profiles/introduction) that you created, won't be available in this new service.
Through the self-custody implementation, you are able to set up self-custodial users with Beam. The implementation is a service that works based on self-custodial private keys, and newly deployed account abstractions. Existing [Profiles](/service/profiles/introduction) that you created before with the Managed SDK won't be available in this service.

---

### What is self custody?

Self-custody means that in this new implementation, a private key only controllable by the user can sign for transactions. The private key for each user is generated in the browser when they start interacting with [Sessions](/service/sessions/introduction) and [Operations](/service/operations/introduction).
When they do, they will be required to authorize with a social identity, from which a private key is generated and sharded - and securely stored.
Self-custody means that a private key only controllable by the user can sign for transactions. The private key for each user is generated in the browser when they start interacting with [Sessions](/service/sessions/introduction) and [Operations](/service/operations/introduction).
When they do, they will be required to authorize with a social identity, from which a private key is generated and securely stored in shards.

---

### Disclaimer

Our self-custodial implementation is **subject to change**, while the basis of the implementation will remain more or less the same, we have different improvements in mind that will make the experience even better - for both you (the game developer) and the end user.
Our self-custodial implementation is **subject to change**.

While the basis of the implementation will remain more or less the same, we have different improvements in mind that will make the experience even better - for both you (the game developer) and the end user.

---

Expand Down

0 comments on commit 0cd625c

Please sign in to comment.