# Issues & Recommendations

**1. RPC Node Inconsistency**

* Transactions may appear confirmed on the explorer but pending via RPC.
* Read calls (`eth_call`) can revert for recently created functions or NFTs.
* Some RPC endpoints return 500 errors or time out under load.

**2. Delayed Read-After-Write**

* Newly submitted data (functions, NFTs, transactions) may take several minutes to propagate across all nodes.
* Frontend verification may fail immediately after a successful write.

**3. Account Abstraction / Bundler**

* Same UserOperation works on other chains but fails on BlockDAG if RPC is out of sync.
* Ensure RPC endpoint used is fully synced before testing.

**4. Stuck Transactions / Pending Receipts**

* Transactions may remain in limbo temporarily.
* Avoid canceling or redeploying immediately; wait for network convergence.

### Recommendations

**For Builders / Developers**

* Use explorer as the source of truth when RPC and frontend disagree.
* Log RPC endpoint, transaction hash, and screenshots to help diagnose issues.
* Implement retry logic in frontend for reads that may fail temporarily.
* Allow non-blocking verification in UIs to prevent workflow interruption.


---

# 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.blockdagnetwork.io/known-issues/issues-and-recommendations.md?ask=<question>
```

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.