Wallet connect and deployed contract
Coderkid
is this a bug? When walled it not connected, already deployed contract looks like not ever deployed...
Sabby Anandan
Hi, Coderkid! Great to see these questions. The status is determined based on the "contract name" and the "connected" wallet account. You will not see the status until that connection is made and successfully reconciled via API. I hope that clarifies.
Coderkid
Sabby Anandan: Yeah but, it makes life difficult if you develop something; during clarity camp, we keep writing a smart contact, and deploy it and try between 2 principals.. like in this case, I wrote a simple contact, let principal A to send STX to principal B... When I switch between wallets, project, and code there (because they are tied my e-mail) but deployment status is not...
Sabby Anandan
Coderkid: This could be a hassle for your
transfer-money
function; I can relate to the switching back-n-forth. The assumption we take on the contract list page is that if you're the owner/maintainer of the contract, you'd have a strict principal that deployed the contract, so that, as a combination, can help narrow down the status queries. We could take the approach of verifying the connection of
all
principles in a given wallet, but that could go into infinite combinations since the accounts in the Wallet don't have any limit. And it'd overwhelm the number of requests originating from the client, too.If you have any other ideas, I am all ears.