# Blockchain limitations #### Building and Syncing a Node Setting up a blockchain node can be extremely time-consuming, taking weeks or even months. The process is frustratingly slow, and it’s hard to predict when it will complete. As the Ethereum and Bitcoin blockchains grow daily, maintaining a stable network becomes increasingly challenging. Balancing blockchain configuration with hardware requirements can be costly and complex. While services like QuikNode and Infura offer nodes as a service, they may not provide all the APIs you need and can be expensive. #### Understanding APIs and Transactions Starting a blockchain application involves navigating a complex array of transactions and APIs. For instance, Ethereum transactions include internal transactions that can be difficult to manage and understand without simplification. #### Performance Issues Monitoring transactions for every address by scanning the blockchain is inefficient. Instead, you need a service that provides real-time notifications for transactions involving specific addresses, which can be achieved through a webhook API. --- # 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.crypitor.com/crypitor-service/overview/blockchain-limitations.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.