# Data Ingression Layer The Ingression Layer serves as the primary data intake for all user interactions and decentralized applications (dApps). It acts as the tunnel through which user inputs and dApp data are funneled for processing. ## **Core Functions:** 1. **Push Notifications from dApps:** The Ingression Layer receives data from dApps, including push notifications. It aggregates and structures these notifications, ensuring they are delivered to the correct endpoints. This ensures that users receive timely updates and messages from the various dApps they interact with. 2. **User Inputs for Chat and Payment Functions:** Users interact with the system via chat and payment functions. The Ingression Layer captures these interactions, identifying user intents and routing them to the appropriate channels for further processing. ## **Processing Workflow:** * **Data Capture:** The layer captures data from dApps and users, ensuring it's correctly structured for further processing. * **Transformation:** The layer transforms the data into a standardized format, facilitating seamless interaction between the different components of the SyncAI Node. * **Routing:** After capturing and transformation, the layer routes it to the appropriate subsystems based on predefined rules and user intents. The Ingression Layer is integral to the SyncAI Node, functioning as the gateway for all data from dApps and users. It ensures that data is accurately captured, routed, and transformed, maintaining the efficiency and integrity of the entire system. --- # 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.syncai.network/sync-node/data-ingression-layer.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.