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

[FIL-394 ]Verify if the client had allocations #243

Merged
merged 2 commits into from
Nov 7, 2024

Conversation

Filip-L
Copy link
Collaborator

@Filip-L Filip-L commented Nov 7, 2024

Deployment Considerations

@Filip-L Filip-L force-pushed the FIL-394-verify-if-the-client-exists-or-got-datacap branch from c6f2a3a to 1dc0991 Compare November 7, 2024 13:21
@Filip-L Filip-L temporarily deployed to production-fidl November 7, 2024 13:22 — with GitHub Actions Inactive
@@ -86,3 +87,20 @@ pub async fn get_allowance_for_client(address: &str) -> Result<String, reqwest::
.await?;
Ok(response.result)
}

pub async fn get_client_allocation(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

external_services/filecoin.rs and models/filecoin.rs contain stuff for communication with glif api.
datacapstats communication is in https://github.com/filecoin-project/filplus-backend/blob/main/fplus-lib/src/external_services/blockchain.rs

Also, blockchain.rs already has get_verified_clients function. What's different between that and the new one?

@Filip-L Filip-L temporarily deployed to production-fidl November 7, 2024 15:41 — with GitHub Actions Inactive
@Filip-L Filip-L merged commit 853208b into main Nov 7, 2024
4 checks passed
@Filip-L Filip-L deleted the FIL-394-verify-if-the-client-exists-or-got-datacap branch November 7, 2024 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants