Info

Cool Kangaroo
Author
Download ZIP (549.2 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

11
by rating

Issues

Grim Hawk Feb 5 at 10:57
Config params 32, 34 and 36 all being saved in lite-client and thus code looks overcomplicated.

As I understand only config_param 34 has to be stored for system to work properly.
Windows 10
Cool Kangaroo Feb 5 at 12:46
Why we need to keep config param 32 (List of validators from the previous key block):
The first key block in an epoch (starting key block) is signed by the previous epoch’s validators. We need to keep them to verify key block transactions if needed.

Why we need to keep config param 36 (List of validators from the next key block):
Transitioning key blocks introduce the next validator set. To ensure key block continuity, we must store them. Without this, the current validator set could manipulate the next set, compromising trustlessness.

We prune as much data as possible from key blocks, keeping our implementation gas-efficient (0.01 TON on testnet for submitting a new key block).
macOS
Nobody added any issues yet...

New Issue