Skip to content
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

Staking pool contract is out-of-date #229

Open
emlautarom1 opened this issue Jun 30, 2023 · 3 comments
Open

Staking pool contract is out-of-date #229

emlautarom1 opened this issue Jun 30, 2023 · 3 comments

Comments

@emlautarom1
Copy link

Twinstake is building a variation on the staking-pool contract with support for whitelisting. During development, we faced some issues related to the contract dependencies being out of date which are detailed in this PR: twinstake/permissioned-delegation-near#6.

In order to continue development, we would like to know what is the suggested upgrade path for this contract - be it either upgrade dependencies or start from scratch from a different template.

@robert-zaremba
Copy link

I wouldn't start from scratch. The contract is battle tested and used in prod.
Better to upgrade or use the old dependencies.

@frol
Copy link
Contributor

frol commented Jul 6, 2023

I would recommend just upgrading dependencies; it shouldn’t be too hard.

Note, don’t use Rust 1.70+ (use 1.69 or older): near/nearcore#9143

@emlautarom1
Copy link
Author

Unfortunately, upgrading dependencies resulted in integration tests to fail. Details about the issues are available here: twinstake/permissioned-delegation-near#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants