-
Notifications
You must be signed in to change notification settings - Fork 377
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
Add various versions of MPC contracts #1961
Comments
I appears that the testnet contract linked in docs ( It seems that this contract has been down/offline for over a week, with this transaction being the last successful one: In terms of the I believe the but it seems like when I immediately try again after a failed transaction times out, it will often work. So I believe it makes sense to change the address to that one. |
Okay, looks like the highlighted screenshot isn't correct, according to this comment: near/mpc#513 (comment) it looks like we need to be pointing to |
merged on #1975 |
Can we add the v5 one? It seems that people are mentioning using that in the Telegram channels. Can we add details on what that is, where the contract is, how it's different, when to use it, etc.? I wish I knew the answers so I could modify my PR, but I don't know and it doesn't seem to have been communicated externally as well as internally. |
@gagdiez can we add more info about our envs? You can find more information in the comment here: near/mpc#601 |
Fixed by #2035 |
Is your feature request related to a problem? Please describe.
As a user, I would like to discover the different MPC smart contract addresses in documentation instead of Telegram.
Describe the solution you'd like
Add the contract addresses and information to docs, covered in the final message here:
Additional context
Chain signatures is live and I believe we need internal folks to be updating the documentation when there are changes that affect partners and builders. It's unusual to not have an issue created when this is a known blocker for developers.
The text was updated successfully, but these errors were encountered: