Skip to content

continues clearout #27

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

Open
m4sterbunny wants to merge 1 commit into
base: main
Choose a base branch
from
Open

continues clearout #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Individuals or organizations that operate and maintain Validator Services. They

### Checkpoint

A finalized snapshot of Appchain states. At the end of each Pelagos epoch, validators agree on the current state root of every Appchain, bundle these into a single checkpoint, and commit it (along with its proofs) to one or more L1 restaking contracts.
A finalized snapshot of Appchain states. At the end of each Pelagos epoch, validators agree on the current state root of every Appchain, bundle these into a single checkpoint, and commit it (along with its proofs) to one or more L1 restaking contracts. <!-- here -->
Copy link
Collaborator Author

@m4sterbunny m4sterbunny Sep 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JekaMas we need to redefine checkpoint


### Checkpoint Merkle root

Expand Down Expand Up @@ -164,7 +164,7 @@ A Pelagos open-source node that includes L1/L2 oracles, sequencing consensus, Ap

### Validator set

The pool of validators authorized to participate in Pelagos' DAG consensus and TSS signing. It's dynamically updated based on restaking commitments from various L1 networks. A majority (⅔+1 by stake) must sign blocks, checkpoints, and external transactions.
The pool of validators authorized to participate in Pelagos' DAG consensus and TSS signing. <!-- It's dynamically updated based on restaking commitments from various L1 networks. A majority (⅔+1 by stake) must sign blocks, checkpoints, and external transactions. -->
Copy link
Collaborator Author

@m4sterbunny m4sterbunny Sep 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JekaMas AFAIK cutting the definition here is fine


<!-- ## W -->

Expand Down
2 changes: 1 addition & 1 deletion technology/consensus-at-scale.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The immutable database model provides a multichain, universal state, ensuring ef

The DAG database achieves this through its key attributes:
- Immutable state snapshots providing tamper-evident, incremental snapshots of blockchain states.
> These snapshots enable seamless synchronization and verifiable data integrity across Appchains, reinforced by restaking confirmations through Pelagos checkpoints.
> These snapshots enable seamless synchronization and verifiable data integrity across Appchains, reinforced by confirmations through Pelagos checkpoints.
Copy link
Collaborator Author

@m4sterbunny m4sterbunny Sep 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JekaMas pls ack if simple deletion works

- Incremental database design enabling rapid synchronization by processing
only relevant components, making it highly adaptable for diverse Appchain architectures.
- Advanced historical indexing enabling users to define comprehensive historical indexes across Appchains and external blockchains.
Expand Down