You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lite client tonlibjson, currently in use, comes with slow compilation time, and as a non-native, it is harder for non-C++ developers to inspect and subsequently make changes to the code.
The proposal is to replace it with the native version. I have also opened a TON bounty footstep for this issue, which you can find here: Rust Lite Client Instead of tonlibjson.
Do you feel that this proposal is well-motivated and worth discussing further?
[In case of a positive answer from 1] How should it be pursued further?
The lite client
tonlibjson
, currently in use, comes with slow compilation time, and as a non-native, it is harder for non-C++ developers to inspect and subsequently make changes to the code.The proposal is to replace it with the native version. I have also opened a TON bounty footstep for this issue, which you can find here: Rust Lite Client Instead of tonlibjson.
Do you feel that this proposal is well-motivated and worth discussing further?
[In case of a positive answer from 1] How should it be pursued further?
@hacker-volodya has suggested replacing it with the tonstack/lite-client he's working on. I myself propose writing a lite-client module on top of the tonlabs/ever-adnl library.
[In case of a positive answer from 1] Are you interested in sponsoring Rust Lite Client Instead of tonlibjson footstep to support this initiative?
The text was updated successfully, but these errors were encountered: