Yeah, it’s quite natural when we do it forward. However, in my opinion, it will be very lengthy and complicated to get quick insight. Otherwise, backward is more easy, so I make an assumption that when readers understood, they could construct a trie by dataset. Yeah, that’s what I think. Glad to see your conments.
Trước hết mình rất trân trọng công trình nghiên cứu của các bạn, đặc biệt là cố gắng trong việc phát triển một consensus nói riêng và cộng đồng blockchain Việt Nam nói chung. Nhưng, việc phê bình EOS và cố tận dụng nó để PR một cách gượng ép cho UN's consensus thật sự không phải là một cách làm khoa học đúng đắn.
Hi Park, first of all, I am so glad to see that you’re dedicating your time to read my old blog. Regarding to your point, it is correct and should be 0x20 because of HP encode for the leaf node. I just have re-corrected them and btw spent a hour on reading again whole blog for understanding wth i was writing :))).
Haha, so clever :))
In go-ethereum code, they have a block of constants like:
// Data item prefixes (use single byte to avoid mixing data types, avoid `i`).
headerPrefix = byte(“h”) // headerPrefix + num (uint64 big endian) + hash -> header
Rafael Sarres de Almeida Yep, a nice question. But note that “hello” and “world” were also decoded by RLP so to differentiate them, we need to take a look at their own headers (bold hex). Just the same as array header
0xcc, those headers also describe their data length, data type.
Hello sir, I’m a developer in a blockchain company and also an independent researcher about Ethereum, especially about Privacy. I’m trying to shape up a PoC that help to recover property and It seems to be related to uPort work.
I really appreciate that if you can read it.
Here the link…