Skip to content

Fix technical inaccuracies in alert.md documentation #241

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

Merged
torrejonv merged 2 commits into from
Dec 1, 2025
Merged

Fix technical inaccuracies in alert.md documentation #241

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e38564
Fix technical inaccuracies in alert.md documentation
torrejonv Nov 27, 2025
eeb438f
Merge branch 'main' into docs/alert-md-documentation-corrections
torrejonv Nov 27, 2025
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
21 changes: 6 additions & 15 deletions docs/topics/services/alert.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The Service features are:

### UTXO Freezing

- Ability to freeze a set of UTXOs at a specific block height + 1.
- Ability to freeze a set of UTXOs at a specified block height.
- Frozen UTXOs are classified as such and attempts to spend them are rejected.

### UTXO Unfreezing
Expand Down Expand Up @@ -173,22 +173,13 @@ The Alert Service initializes the necessary components and services to start pro

3. The Blockchain Client interacts with the Blockchain Store to:

- Mark the specified block as invalid.
- Retrieve all transactions from the invalidated block.
- Mark the specified block and all child blocks as invalid in the database.
- Set the mined status to false for these blocks.
- Return the list of invalidated block hashes.

4. For each transaction in the invalidated block:
4. The Blockchain Client confirms the invalidation process to the Alert Service.

- The Blockchain Client re-validates the transaction.
- If the transaction is still valid, it's added back to the Block Assembly service, for re-inclusion in the next mined block.

5. The Blockchain Client then:

- Retrieves the block immediately preceding the invalidated block.
- Sets the chain tip to this previous block, effectively removing the invalidated block from the main chain.

6. The Blockchain Client confirms the invalidation process to the Alert Service.

7. Finally, the Alert Service returns the invalidation result to the P2P network.
5. Finally, the Alert Service returns the invalidation result to the P2P network.

## 3. Technology

Expand Down