LiskArchive/lisk-db

StateDB sometimes return key with internal prefix

Closed this issue · 0 comments

Expected behavior

When calling StateDB range, it should never expose the internal prefix

Actual behavior

In some case, range returns state db prefix 00

Steps to reproduce

Call range with key in cache/out of cache/deleted

Which version(s) does this affect? (Environment, OS, etc...)

0.3.1