Payment-gated webapp deployment requests #927

Open
opened 2024-08-16 20:57:18 +00:00 by dboreham · 2 comments
Owner

Following on from this issue, requirement is to have the deployer only honor deployment requests if an associated coin transfer has been made to its address.

Following on from this issue, requirement is to have the deployer only honor deployment requests if an associated coin transfer has been made to its address.
Author
Owner

Deployment requestor supplies the following information in the request record:

Payment transaction id, sender address, recipient address, amount.

Deployer filters requests specifying its address as recipient, verifies the transaction exists on-chain, then honors the deployment request.
The associated deployment record includes some sort of receipt that allows the payment transaction to be tied to a past deployment. This prevents replay attacks.

Deployment requestor supplies the following information in the request record: Payment transaction id, sender address, recipient address, amount. Deployer filters requests specifying its address as recipient, verifies the transaction exists on-chain, then honors the deployment request. The associated deployment record includes some sort of receipt that allows the payment transaction to be tied to a past deployment. This prevents replay attacks.
Author
Owner

First cut at deployer functionality: #928

First cut at deployer functionality: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/928
telackey was assigned by dboreham 2024-08-20 00:14:10 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#927
No description provided.