In memory node | Algorand | Page 1

Hi @frail fractal. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

Based on the knowledge sources provided, I don't have specific information about an "in-memory mode" for Algorand nodes and how it would behave after a server restart.

The documentation mentions catchup processes and catchpoints, which are mechanisms for nodes to synchronize with the blockchain network. When a node restarts, it typically needs to catch up to the current state of the blockchain if it has fallen behind.

The knowledge sources describe:

The catchup process and related API endpoints like /v2/catchup/{catchpoint} Algod API
Node status information that includes catchpoint and catchup-related fields NodeStatusResponse
REST API endpoints for interacting with the Algorand node REST APIs

However, there is no specific mention of an "in-memory mode" for Algorand nodes or how such a configuration would handle restarts with respect to catchup requirements.

If you're running a node with a specific configuration or using a particular deployment method, I would recommend checking the official Algorand documentation for that specific setup or reaching out to Algorand's developer community for more targeted information.

#In memory node

If you're running a node with a specific configuration or using a particular deployment method, I would recommend checking the official Algorand documentation for that specific setup or reaching out to Algorand's developer community for more targeted information.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: