# Eviction Policy Currently, the amount of data that a user can write to the network is unbounded, introducing a potential for sybil attack. To mitigate such issue, in the future we will impose a data eviction policy and only expect the network's full node operator to retain the most recent 16MB of data with a valid schema. Data for each full node is bounded by the same data eviction policy. Once a per day by default, and as often as needed, each node will go through data for each peer and remove message record based on the following rules: * any non-archive messages with an invalid message hash * any non-archive messages not included in the most recent 16MB (size determined by serialized message hex) * any archive message with invalid schema The expectation for the user is that the network will always keep the most recent 16MB of data available to participants in the network. All history beyond the most recent 16MB will be kept available based on network participation (e.g. browser peers’ local storage), as well as any available archives. --- # Agent Instructions: 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: ``` GET https://docs.zkitter.com/developers/data/eviction-policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.