If you try:
stellar registry publish-hash --wasm-name tansu ...
...and don't know that you need to add unverified/tansu instead, you get this error message:
error: Missing signing key for account GAMPJROHOAW662FINQ4XQOY2ULX5IEGYXCI4SMZYE75EHQBR6PSTJG3M
This is because GAMP… is the admin of the root registry, and you are trying to publish to the root registry. But what an unintelligible error message! No one is going to know what to do with that. We should say something like:
Account {source_account} is not allowed publishing to the {channel} Registry. Try publishing to `unverified` instead:
stellar registry publish-hash --wasm-name unverified/tansu ...
Then you can request your contract be added to the {channel} Registry by creating an issue at https://github.com/stellar-registry/gov/issues/new
This should obviously say deploy if they tried to deploy, and show the original command with the name prefixed with unverified. If they try to publish to oz/ or some other contract for which they don't have permission, it should switch oz/ to unverified/, not naïvely prefix with unverified/ and end up with unverified/oz/lol.
If you try:
...and don't know that you need to add
unverified/tansuinstead, you get this error message:This is because
GAMP…is the admin of the root registry, and you are trying to publish to the root registry. But what an unintelligible error message! No one is going to know what to do with that. We should say something like:This should obviously say
deployif they tried to deploy, and show the original command with the name prefixed withunverified. If they try to publish tooz/or some other contract for which they don't have permission, it should switchoz/tounverified/, not naïvely prefix withunverified/and end up withunverified/oz/lol.