Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(Update): edit md typo in avs use cases #4455

Merged
merged 2 commits into from
Feb 26, 2024
Merged

docs(Update): edit md typo in avs use cases #4455

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e721c3
Update use-cases.md
JafarAz Feb 20, 2024
4788f36
Update use-cases.md
JafarAz Feb 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/docs/technology/restaking/use-cases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Use Cases
# AVS Use Cases

This section provides a brief overview on the some of the initial use cases for the Generalized Restaking layer:
This section provides a brief overview on the some of the initial AVS use cases for the Generalized Restaking layer:

## Securing an L1 network
## Securing an L1 network
A major use case that can be adopted by L1 blockchains will be the ability to power an existing or launch a new PoS chain leveraging the security of the Generalized Restaking layer. This flexibility allows chains to customize their security requirements and decouple the network launch from the token launch process. In this scenario, the AVS will be the L1 network.

## Restaked Rollups
Expand All @@ -12,7 +12,7 @@ Another application of the restaking layer is for Restaked Rollups. Initially, t
Middleware protocols such as Oracles, Bridges and Sidechains will not need to devote time and resources to their own security models, and can instead focus on their respective roles/services. Importantly, the security delivered to these protocols can be tailored to their needs, so that the cost of corrupting a middleware service equals the aggregate amount of all restaked assets via Picasso’s Restaking Layer. This means middleware services can no longer be the “weakest link” when it comes to security, making them less likely targets.
This is already in production on Solana to implement IBC on previously IBC-incompatible chains. This connection will happen via the first AVS for Solana IBC. The purpose of this AVS is to provide state proofs of Solana via existing validators of the host network running a lightweight sidecar to generate these proofs. The AVS for Solana IBC is described in detail in this Composable Research forum post.

## Reduced Solver Collateral Requirements
## Reduced Solver Collateral Requirements
Within the MANTIS workflow, solver collateral will be necessary. However, solvers will have the ability to integrate with the restaking layer, significantly reducing collateral requirements.

## Partial Block Building
Expand Down
Loading