Incognito chain's code upgrade (tag: 20210531_1)

Hi folks,

We’ve just released a protocol upgrade for bug fixes, the latest code is published in 2 forms:

In order for your nodes to operate correctly, please update the latest code. Please note that, for the pNode, it should pull the latest docker image automatically. In case you encounter any issues with the code update, feel free to contact @support for assistance.

Thanks!

6 Likes

Still getting errors when trying to sync old shard blocks.

2021-05-31 10:59:33.321 shardprocess.go:141 [INF] BlockChain log: SHARD 2 | InsertShardBlock 586697 with hash 5022f6aaaf32f76bd4262955e4ed095297954e2c86c2b8f09fc57d9acaa4da2e Prev hash: 57f8635cebf6ec58af541437a875e3853bae581d6deededaeb415a07a4476867
2021-05-31 10:59:33.327 shardprocess.go:189 [INF] BlockChain log: SHARD 2 | Verify Pre Processing, block height 586697 with hash 5022f6aaaf32f76bd4262955e4ed095297954e2c86c2b8f09fc57d9acaa4da2e
2021-05-31 10:59:33.424 shardproducer.go:888 [INF] BlockChain log: Build Request Action Pairs [], metadata value &{BlockHash:[69 10 171 144 112 77 129 81 175 106 234 215 55 188 94 118 201 188 205 141 117 178 120 72 222 156 4 74 38 21 14 87] TxIndex:75 ProofStrs:[+QExoMUiYrzdWaGVyPByiKEb8wor8DQY+SSKWVN0BrTJP7dfoA+xsX8JJhhN4Ku8eIn7KSDCw7sWZfSVTIXAVgNn1Y9hoIhNubijoy3/0QuMOZK/fo2abqi997hIvi77te8UigdgoGyl2518MuZAgoOGG1/LRTtTdkQAn5Q0At7CLYLrorY3oCzGaR2FNlrqHgfgvn51jNwRUOQBhvdHcunPcJZxKEYAoAQPHCX09dgpjos5q+skgpsPxC2v9aWJ2hgE1s++xwFVoFxRWdMKGZeUUVT8DJJESrkCeKgRHYT5OHkz8VbNI2pxoAInUH0N9gfTkk53s8FCr+Ftj1Tp4zdsEyY57FrggwCKoHMJLK0wNmaFmSOXg5jour8VMqavwsciKCZZIGWo8J0+gICAgICAgIA= +QIRoMFhmMtHuoJtX+us2z4xIXYCaUnZOzQ6ThwoWCJx7H63oLODkWPRzcb65MRvFyqpv/N7Ilrh1aooFscnb/fYcVxloHDYVEjMrT8ZqlSa4yU+0GfiOonmkm/LQpCLSbucGEsnoBKSSQKU0ieiRUH8uo0h/6/h/iQQTHfBcyRgMLKNvHIroCLbYk3IXWL+9yd1OEYKV+uG/2rV3rsQf3SF3JhC4nusoA8x7lcWvdduFdE4mKsWvy8TBRr6pDZxlTKGO8IQfsTQoKfvTNs0k1J8nSpmlxrLc8z1BMiQBQwAW68KLzksHs4RoE1DepZrPIPdH9EJf3ASy67ypU07ijit72DPdpFRzRGjoGB3OMjA7NbI1XOhEBjDSYJWX+FsqY27vAY72TJeM60uoN6LPvItrgkvzk2JJv67+DYE7ZSyUNeUlvKSUfty2wMzoDfPtWYdiDtWpkOqSnYkPRDugGFsxGAEi2OISxFR9DonoKBgJTgnaNcxBhC9sOKB1vn2VwnlgptXNH1Bw0F2h8nBoPX/BCX377pKjG6gFytqDHVHVWmpJxMIG+okLCpQYQJloJOZ2kvBm+cMWIKfMcKdPgaGFAapnZkjOCAGYlYGGCKhoEyN8fv70uYRy8NsbH2yUQvUlPFNA83jJbOb/otOJYCAoHHGdWdOPIJ10b7WIEVRMgfE3kZNj9ex4o7J0Gb7eadYgA== +QJPILkCS/kCSAGDMsbquQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAQEAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPkBPfkBOpQ8jslCE/CaFXX3c0cIMBJN+0AELuGgLUtZeTXzzWf7Luvx203ryTTO5ce6pxU/mA/b6y50CE65AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARWORgkT0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZzEyUndGSGhTWVVCdE5DZGdqSmR1MW5ZRlNSczZoeURBS3F4aHZVRG8zV2VqNzlVUG1QakhxZ3o0ZUxUZVQxTThnN1lnV3JFYWR4dXBVNmZmNzlWZm9CZUJVaVE0RzdLc2ZyajNCWGoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA] IncTokenID:ffd8d42dc40a8d166ea4848baf8b5f6e912ad79875f4373070b59392b1756c8f MetadataBase:{Type:80}}
2021-05-31 10:59:33.424 shardproducer.go:892 [ERR] BlockChain log: Build Request Action Error -1006: Build request action error%!!(MISSING)(EXTRA []interface {}=[]) -1007: Verify proof and parse receipt%!!(MISSING)(EXTRA []interface {}=[]) invalid character 'i' looking for beginning of value
Verify proof and parse receipt

https://we.incognito.org/t/vnode-sync-errors-since-version-20210313-3/12390/2

I guess you were running the node without a correct configuration for GETH environment variable (that should be pointing to Infura). @khanhj will support you on this, thanks.

1 Like

Nope, all my tests have been with infura, using the script from this post How to setup your own node in a blink of an eye

Is there any way to verify that the infura lookup works? If I go to their dashboard it always displays as 0 requests today. Tried removing the project and creating a new one, following the instructions from step 3 in this post. How to host a Virtual Node But it made no difference.

I’ve been running all kinds of sync tests over the past week that have all failed. This release got my hope up. Not gonna hijack this thread anymore, I’ll restart from scratch using only 20210531_1 and update my own thread. Hopefully, someone on the team can figure something out eventually.

Update:
Turns out the installation script in the post linked above (and also currently in the github repository) has the wrong defaults and incorrect instructions.

4 Likes

Given an answer to your topic. Thanks!

2 Likes