when publishing a Deployer LRN, service providers should be able to set one or more recipient addresses for different Cosmos mainnet chains
payment should be 5$ worth of the token
tx hash supplied by the user, amount sent and price obtained from mintscan api
the ApplicationDeploymentRequest should include the chain-id of the relevant chain
stack orchestrator would then: a) using tx hash + chain-id, get amount sent then b) do the price check, c) if ok, proceed as usual
This feature requires updates to: this repo, stack orchestrator, and the service provider setup instructions.
rough outline:
1. when publishing a Deployer LRN, service providers should be able to set one or more recipient addresses for different Cosmos mainnet chains
2. payment should be 5$ worth of the token
3. tx hash supplied by the user, amount sent and price obtained from mintscan api
4. the ApplicationDeploymentRequest should include the chain-id of the relevant chain
5. stack orchestrator would then: a) using tx hash + chain-id, get amount sent then b) do the price check, c) if ok, proceed as usual
This feature requires updates to: this repo, stack orchestrator, and the service provider setup instructions.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
rough outline:
This feature requires updates to: this repo, stack orchestrator, and the service provider setup instructions.