-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Use new version of the connector. #527
Conversation
Instead use env::predecessor_account_id. Using signer_account_id has the same problems of using tx.origin in Ethereum. See link below for more details: ethereum/solidity#683
Need to use fixed near-sdk-version for compatibility with rainbow-token-connector. This restriction will be lifted once the special commit used by the connector lands on near-sdk-rs.
605c2cf
to
e02e307
Compare
e02e307
to
92ee49e
Compare
TODO: Don't use current pinned commit from token-connector, instead wait until it is merged into master
92ee49e
to
9b3a511
Compare
using new interface
dd946fa
to
641ede9
Compare
Closes #519 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, please check the commits
cli/package.json
Outdated
@@ -34,7 +34,7 @@ | |||
"rainbow-bridge-near2eth-block-relay": "1.0.0", | |||
"rainbow-bridge-watchdog": "1.0.0", | |||
"rainbow-bridge-testing": "1.0.0", | |||
"rainbow-token-connector": "near/rainbow-token-connector#0646850267c42057e92f2d670eebe79c9c9211f9", | |||
"rainbow-token-connector": "near/rainbow-token-connector#6855221404f81f987fcf1db9a860b2345149531a", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why we not using d6022357e8e59ea790ff52af80df40f6036d1ec9 -- the merge of NEP-141 migration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
atm of writing it, that PR haven't land, let's update.
@@ -8,4 +8,4 @@ edition = "2018" | |||
crate-type = ["cdylib", "rlib"] | |||
|
|||
[dependencies] | |||
near-sdk = "0.11.0" | |||
near-sdk = { git = "https://github.com/near/near-sdk-rs", rev = "613adcab6322e4f830efb4d5bde2a810ae642158" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check the commit please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is the right commit (the first in this PR: near/near-sdk-rs#325) It is already merged, after release we will be able to update.
9f7833e
to
1119efb
Compare
Use commit on master.
1119efb
to
edf2ea4
Compare
* fix: Don't use env::signer_account_id Instead use env::predecessor_account_id. Using signer_account_id has the same problems of using tx.origin in Ethereum. See link below for more details: ethereum/solidity#683 * fix: Use fixed near-sdk-version Need to use fixed near-sdk-version for compatibility with rainbow-token-connector. This restriction will be lifted once the special commit used by the connector lands on near-sdk-rs. * Add test to check near contracts are compiled correctly * Fix pipeline.yml syntax * Update near-sdk from eth-types * Recompile contracts * fix: Use new version of the connector. TODO: Don't use current pinned commit from token-connector, instead wait until it is merged into master * Update arguments to deploy locker using new interface * Use fixed amount of gas * Compile contracts * Update tests * Update cli/package.json Use commit on master.
This PR was created to trigger CI (and integration tests) with the new version of the connector
TODO: Don't use current pinned commit from token-connector, instead wait until it is merged into master