Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change from Claim_escrow_earnings -> Sign_Release function #30

Open
techrebelgit opened this issue Dec 7, 2024 · 1 comment
Open

change from Claim_escrow_earnings -> Sign_Release function #30

techrebelgit opened this issue Dec 7, 2024 · 1 comment
Assignees
Labels
core-dev For internal project developers

Comments

@techrebelgit
Copy link

The claim_escrow_earnings function was from previous focus on freelancers.
We added release_signer address because there are usecases weere the funds release will not happen as a claim by the service provider, but as a release signature either by the platform or even the client.
So we we need to modify so that the auth is to the release_signer address and no to the service_provider one.

Basically the release signer is who can release funds TOWARDs the service provider.

@techrebelgit techrebelgit added the core-dev For internal project developers label Dec 7, 2024
@techrebelgit techrebelgit added this to the Smart Contract V2 milestone Dec 7, 2024
@armandocodecr
Copy link
Contributor

The corresponding changes have already been added for what was requested in this issue.

Screenshot 2024-12-11 at 11 52 00 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-dev For internal project developers
Projects
None yet
Development

No branches or pull requests

2 participants