Known Issues — Datakeeper Node

[superhacker2002]

This issue is a standard operational known-issues log, maintained by the team transparently for our community. It reflects our commitment to open communication — most issues here are edge cases affecting a subset of nodes, not systemic failures.

We update it regularly. Please check here before creating a new bug report.

Last update: 2026-08-12
Current recommended version: v4.1.2 (or latest)

---

Critical

1. Transaction sending error: status is not successful / transaction reverted

• Description: Fill Roothash transactions sending freezes and ends with the reverted status. The next proof transactions are not sent due to the absence of the snapshot creation
• Affected: A subset of Datakeepers has reported this issue
• Status: In progress. The fix will be included in v4.1.3
• Workaround: None confirmed yet. Please share your node logs in Discord support if you encounter this error

---

High Priority

1. Errors when sending transaction 0xbd12599d (Fill User)

• Description: Failures occur when the node tries to send the Fill User transaction (0xbd12599d).
• Affected: A subset of Datakeepers has reported this issue
• Status: In progress. The fix will be included in v4.1.3
• Workaround: There is no need to take any action; the algorithm will be updated in future versions to reduce the number of errors.

2. Transaction sending fails with context deadline exceeded (RPC timeout)

• Description: Node fails to send the proof transaction with the error context deadline exceeded". This can cause the node to skip cycles. The issue appears related to RPC availability/latency (potentially on the user's end) rather than the protocol itself, but is still under review.
• Affected: A subset of Datakeepers has reported this issue
• Status: In progress. The fix will be included in v4.1.3
• Workaround: Try switching your RPC endpoint

---

Medium / Low Priority

• (empty for now)

---

Recently Fixed

• v4.1.2 — Fixed nonce too low in certain cases

---

How to report a new issue

1. Make sure the problem is not already listed above.
2. Please, submit a ticket on Discord by applying Node logs and providing a detailed description of the problem.

Useful links:

• Latest Releases
• Documentation
• FAQ