Error: "Unexpected trie node" during QANet operation on latest develop branch - non-blocking but persistent #3304
Description
Description
When running QANet using the latest develop branch, the following error log continuously appears but does not affect node operation:
error log:
lvl=error msg="Unexpected trie node" location=diff owner=0xe6ff2e3012de70e73c52919522ab1149b7c02f73a7d686b3924af990ca2798dc path="" expect=0x92f9c5af352701115bbd08acbe319c9bcb0a1ab062da8b8d69913a6de3cf5322 got=0x3d5f5a790ab106d066c8b5717e533ea4de5f8818e5315591a02a73d7c3f8931d blob=0xf90211a0ef63aad3896389b6ac99a2dd841144bf45f7b436a46fe8316516342ad4c6f448a05fbdcf3d5a7656c6667593d73fa5c5bb2886632c2ffda1188129900002d61af0a0446e18545855b4cc110383a7b4a6dfbeacdcf413c7388605b5fff9e6a019fe80a0049fd82bd5d1726c260182950a789500ef00edc851b1ebe87ee16f206ccc1d41a031075a8aef404375349009e79918fab6e15291329d71813e4dfa6f9753af5111a014c7ec6ee45924ff76ad87c65c36a87897b0324f20d6d8704e41b17831ff6511a080854e6068bdc4de80d59e2e2b7c79b1d882c4be9f6259ff9f0b9a1e93036edca0eb1f63f62ec47058759d889027e48d8d3a031e2b04218ea522302c9aa6c479c7a0568c8230d514fa44db263694c3c9c36db6bb7234d5f7167f26fa1b994f608a5fa020c4efc891077c088985d67ac3170ed9d8622c0ff0126d0fa18ef938529f6b31a0d1c40edaa31fb433fe736af1bd9471c2684eb5414a22d6fb4304a29870e949fda0b95f2937d29f08cacd5d8d7cee15386e0a1e010ba9fd027f9ce740eca1107330a046a0973eb06de6bd6834463dca0de40bfbe11aa4680692422105f74d8edc13f8a0edf5a7393be46a8bda9d03ae8b598a71727d0ddfcefe907ea1d7c62b6ef544e3a059d69637a382e044612e9b7ab1abd397e4b8fb30fa87db6d05a30f86b389281da0cec40b3604b361acdbd08062a06ec27a28babd1a3481e67a5c2104d1587bb8b480
Current Behavior
✅ Node continues to operate normally
❌ Error logs continuously generated
❌ Potential trie node inconsistency
❌ May indicate underlying data structure issues
Expected Behavior
No unexpected trie node errors during normal operation
Consistent trie node hashes
Clean error logs without persistent trie-related issues
Metadata
Metadata
Assignees
Labels
No labels