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
Hi there, Octopus Network is working on near-ibc which will enable IBC based cross-chain bridge on NEAR protocol.
We plan to integrate the latest ibc-rs. The latest version of ibc-rs to be released has a dependency on borsh 0.10 (due to the requirements of other dependencies, see this issue), but the current release version (4.1.1) of near-sdk-rs has a dependency on borsh 0.9.
I looked at the source code of the latest near-sdk-rs, and I found that the borsh dependency is still 0.9. So this will affect the release of the near-ibc project.
I'm wondering why this dependency is still not upgraded in near-sdk-rs, is there any special consideration? If not, we would like to see borsh upgraded to 0.10 in the next release of near-sdk-rs.
BTW. We also expect the env::ed25519_verify function to be available in the next release of near-sdk-rs, which will help us reduce the gas consumption of signature verification in tendermint light client in near-ibc contract, which is also very important for near-ibc.
Thank you!
The text was updated successfully, but these errors were encountered:
@riversyang Thanks for flagging it! There is a major push to borsh 1.0, and we already have a draft PR #1075 that checks that 1.0-alpha works as expected!
Hi there, Octopus Network is working on near-ibc which will enable IBC based cross-chain bridge on NEAR protocol.
We plan to integrate the latest ibc-rs. The latest version of
ibc-rs
to be released has a dependency onborsh 0.10
(due to the requirements of other dependencies, see this issue), but the current release version (4.1.1) ofnear-sdk-rs
has a dependency onborsh 0.9
.I looked at the source code of the latest
near-sdk-rs
, and I found that theborsh
dependency is still0.9
. So this will affect the release of thenear-ibc
project.I'm wondering why this dependency is still not upgraded in
near-sdk-rs
, is there any special consideration? If not, we would like to seeborsh
upgraded to0.10
in the next release ofnear-sdk-rs
.BTW. We also expect the
env::ed25519_verify
function to be available in the next release ofnear-sdk-rs
, which will help us reduce the gas consumption of signature verification in tendermint light client innear-ibc
contract, which is also very important fornear-ibc
.Thank you!
The text was updated successfully, but these errors were encountered: