The CLI which stores programs on chain could have an option to specify whether the program is intended to be publicly available, and if it is, then make an HTTP request to the program-metadata-web-service, which pulls the name and description etc, from Cargo.toml and makes that data available through a json http api.
The testnet status page uses this service to display names in the list of programs. And potentially the SDK could use it to make a 'program picker' for users.
However, the program-metadata-web-service is not yet deployed. And it requires you to build the program with docker in order that it can verify that the source code matches the on-chain binary.
The CLI which stores programs on chain could have an option to specify whether the program is intended to be publicly available, and if it is, then make an HTTP request to the program-metadata-web-service, which pulls the name and description etc, from Cargo.toml and makes that data available through a json http api.
The testnet status page uses this service to display names in the list of programs. And potentially the SDK could use it to make a 'program picker' for users.
However, the program-metadata-web-service is not yet deployed. And it requires you to build the program with docker in order that it can verify that the source code matches the on-chain binary.