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

Add various versions of MPC contracts #1961

Closed
mikedotexe opened this issue May 8, 2024 · 6 comments · Fixed by #1975 or #2035
Closed

Add various versions of MPC contracts #1961

mikedotexe opened this issue May 8, 2024 · 6 comments · Fixed by #1975 or #2035
Assignees
Labels
enhancement New feature or request

Comments

@mikedotexe
Copy link
Contributor

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:

chain-siggy-chaos

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.

@mikedotexe mikedotexe added the enhancement New feature or request label May 8, 2024
@thisisjoshford thisisjoshford moved this to Backlog 🥶 in DevRel May 13, 2024
@mikedotexe
Copy link
Contributor Author

I appears that the testnet contract linked in docs (multichain-testnet-2.testnet ) here:
https://docs.near.org/build/chain-abstraction/chain-signatures#create-a-chain-signature

It seems that this contract has been down/offline for over a week, with this transaction being the last successful one:
https://testnet.nearblocks.io/txns/6dJzPYBSPgidGvpt7JRX5qeMAjd7p4sMtHXZFanDtfxi

In terms of the v2 contract, I created this issue after seeing a problem:
near/mpc#590

I believe the v5 version is the one we're supposed to use. I've seen this error still:
near/mpc#591

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.

@mikedotexe
Copy link
Contributor Author

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 v2.multichain-mpc.testnet. I've updated the pull request

@thisisjoshford thisisjoshford moved this from Backlog 🥶 to In Progress 🏗️ in DevRel May 20, 2024
@bucanero bucanero linked a pull request May 20, 2024 that will close this issue
@gagdiez
Copy link
Collaborator

gagdiez commented May 20, 2024

merged on #1975

@mikedotexe
Copy link
Contributor Author

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.

@volovyks
Copy link
Contributor

@gagdiez can we add more info about our envs? You can find more information in the comment here: near/mpc#601

@volovyks volovyks reopened this May 21, 2024
@gagdiez gagdiez moved this from In Progress 🏗️ to Backlog 🥶 in DevRel Jun 5, 2024
@PiVortex PiVortex moved this from Backlog 🥶 to In Progress 🏗️ in DevRel Jun 10, 2024
@PiVortex PiVortex self-assigned this Jun 10, 2024
@PiVortex
Copy link
Contributor

PiVortex commented Jul 1, 2024

Fixed by #2035

@PiVortex PiVortex closed this as completed Jul 1, 2024
@github-project-automation github-project-automation bot moved this from In Progress 🏗️ to Shipped 🚀 in DevRel Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Status: Done
4 participants