gm, a bit of a pressing issue …
when i tried to create/mint a 1/1, my “primary” contract (deployed with manifold, using the address im currently logged into studio with) isn’t showing up as an option;
and when i navigated to the settings section, i do see the said contract (“CADMONKEY”), but it’s not showing up with the manifold symbol and isn’t clickable/editable
contract address is:
0x1b0fd0FC8dcEdba6390fDd3973C2856e0399f831
deploying address is:
deployer.cadmonkey.eth
please find screenshots showing the issue below,
thank you for your help !
If it’s not showing up as a selectable contract to mint from, it’s likely owned by a workspace controlled by another wallet.
Have you tried signing off and logging in with your other wallet?
thanks for the response wilkins,
when i was doing some search, i was guessing that might be the issue, but the thing is that the said contract is deployed via the address that is used to sign in to studio right now as mentioned. when i tried to sign in with my other address (cadmonkey.eth instead of deployer.cadmonkey.eth), studio ui is asking me for an email which doesn’t really make sense as i’ve also tried logging in with two alt. email addresses and both returned with the result saying account doesn’t exist.
why would a “workspace” be controlled by another wallet when the contract is deployed via the current wallet, and the ui also doesn’t seem to recognize it as a contract deployed via the manifold platform, as shown in the screenshot above?
following up …
so i tried to login with cadmonkey.eth and register a new email to attach to the account - the contract new shows up (even though, again, the contract is not deployed by this address);
however, as i setup the token and tried to mint, it wouldnt let me until i switch in metamask from cadmonkey.eth to deployer.cadmonkey.eth, and after i did, it still woundnt let me go through the steps as shown in the screenshot below.
it all seems a bit convoluted - i dont used to have this issue with the previous ui …
TLDR:
Yes, sorry, it’s a bit convoluted because people created accounts with various logins, and when we tried to untangle everything, contract ownership was assigned to the originating account. In the past, we trusted on-chain admins and automatically showed contracts as long as you were an on-chain admin, but we disabled this because it could lead to a spoofing attack (someone could permissionlessly add you to a spoof contract and confuse you, causing you to mint to a contract they controlled).
Details:
Alright, so the contract:
0x1b0fd0FC8dcEdba6390fDd3973C2856e0399f831
Is owned by the workspace controlled by:
0x7cd29e0df7e442068e5751b638c9086fb62c50fa
So, if you log out of studio and login with 0x7cd29e0df7e442068e5751b638c9086fb62c50fa, you’ll see that contract and be able to mint from it. (Note: you should take note of your user profile email once you’re logged in)
If you want this contract ‘moved’ to another workspace, you’ll have to do the following:
- Be logged into an account that has your ‘destination’ workspace (where you want to move it to).
- Invite your 0x7cd29e0df7e442068e5751b638c9086fb62c50fa account to the ‘destination’ workspace (using the email you noted above)
- Log out, then login with 0x7cd29e0df7e442068e5751b638c9086fb62c50fa. Go into your Contract page → Settings and you can move it to another workspace.
Unknown error issue:
As for the ‘unknown error’, I’m not sure. Can you share the console error log when it the error pops up.
1 Like
understood now - thanks so much for the timely and helpful responses !!
i’ve successfully logged in via 0x7cd, added the other address as an authorized user and the error went away, and have minted the piece via the (correct) address, but still within the 0x7cd workspace.
will try the steps you outlined in order to move the workspace to the deployer address later today.
very much appreciated once again !
1 Like
