Info

Merry Gnu
Author
Download ZIP (180 KB)

Testing and Issues

You can test this entry and submit issues during the testing period of the TON Trustless Bridge Challenge contest.

Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.

Voting

2
by rating

Issues

Grim Hawk Feb 5 at 13:51
lite-client code looks so concise and clean.

Potential Issues:
1. no tests
2. lite-client stores prev, cur and next validator sets (not sure if that's a problem, there submissions who only store cur set or even just a hash of cur set)
3. It looks like whole block is sent to lite-client (no pruned branches)
Windows 10
1
Merry Gnu Feb 5 at 14:21
Hey! Thanks for your report :)
1. There is an E2E test that checks the happy-path user_request -> transaction_checker -> block_checker -> transaction_checker -> user_response.
2. I've decided to make it more flexible because there are edge cases when you need to know not only the current set. Additionally, the task description contains "currently known epoch," so I decided that if we have a key_block, we know not only one epoch and we need to cover them all.
3. Yep, unfortunately, I had no time to move to the pruned branches approach. The task description contains "may have all unused branches pruned," so this means that they may have or may not have.

This is a very interesting challenge, but unfortunately, this was my first time with smart-contracts in my life and I have a main job, so I had about zero time to make it perfect :(
Nobody added any issues yet...

New Issue