> For the complete documentation index, see [llms.txt](https://docs.glitterfinance.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glitterfinance.org/glitter-crosschain-platform/token-bridge-v2/lifecycle-of-the-validator.md).
# Lifecycle of the validator
A user of the Glitter Bridge starts the bridging process by creating a deposit transaction on the origin network with a smart program. This transaction contains routing information about the target chain, target wallet, and information about bridged tokens and their amount.
Each validator periodically checks for the new deposit transactions on all configured chains with Glitter SDK Scroller. Validator first exclusively claims the latest scroller cursor for the available blockchain network from the shared database. This cursor is locked for other validators until the scrolling process is finished.
The retrieved transactions from Glitter SDK are validated against the validator's configuration including database settings of all existing tokens for each chain. Invalid transactions are stored in the `error_transactions` working as a dead letter queue for further investigation and possible retry mechanism (not implemented yet). If the transaction passes the validation process, the validator creates and signs a release transaction on the target chain and saves the serialized transaction blob in the `multisig_transactions` table.
Other validators are periodically checking the database for release transactions that are waiting for their signature. These transactions are picked up by the validator from the database, signed with the chain-specific mechanism, and the validator appends its id to the list of the signers stored in the database together with the transaction blob. Once the multi-signature threshold is achieved, the release transaction is picked up by a random validator and executed on the specific chain.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.glitterfinance.org/glitter-crosschain-platform/token-bridge-v2/lifecycle-of-the-validator.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.