Skip to content

fix(docs): add FAQ entry about minimum history for Data Availability Layer #503

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
fassko merged 1 commit into from
Jan 14, 2025
Merged

fix(docs): add FAQ entry about minimum history for Data Availability Layer #503

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
5 changes: 5 additions & 0 deletions docs/fassets/guides/5-faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,8 @@ Yes, for an agent to stay operational, it must run continuously.
Do not restart the agent, as this may result in double payments.
The current solution is duplicating the database and launching a new agent instance.
You should monitor your database closely and, if access is lost, remove the agent from the available list, self-close FAssets, and backup agent keys.

### Is there a minimum history needed in the Data Availability Layer for agents?

No minimum history is required; it can be set to the latest block.
You need to start the [Data Availability Layer](/fdc/overview#data-availability-layer) before you can participate as an FAsset agent.
Loading