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

[venus-market] 借鉴boost统计算力方式? #5108

Closed
Tracked by #5205
Fatman13 opened this issue Jul 20, 2022 · 2 comments · Fixed by ipfs-force-community/droplet#188
Closed
Tracked by #5205

[venus-market] 借鉴boost统计算力方式? #5108

Fatman13 opened this issue Jul 20, 2022 · 2 comments · Fixed by ipfs-force-community/droplet#188
Assignees
Labels
C-dev-productivity Category: Developer productivity

Comments

@Fatman13
Copy link
Contributor

PR:filecoin-project/boost#638

原文:https://filecoinproject.slack.com/archives/C0328PT17JR/p1657560433692509

22 SP’s running Boost with a RBP of 16.25PiB and QAP of 47.11PiB

不知道能不能借鉴一下?

@Fatman13 Fatman13 added C-dev-productivity Category: Developer productivity design Venus feature/system design issues labels Jul 20, 2022
@hunjixin
Copy link
Contributor

具备可行性,可以判断到有哪些矿工使用了我们的venus-market

@Fatman13
Copy link
Contributor Author

6666 搞一搞,[doge]

@hunjixin hunjixin changed the title [libp2p] 借鉴boost统计算力方式? [venus-market] 借鉴boost统计算力方式? Jul 22, 2022
@diwufeiwen diwufeiwen mentioned this issue Jul 25, 2022
36 tasks
@Fatman13 Fatman13 mentioned this issue Aug 22, 2022
33 tasks
@Fatman13 Fatman13 added the C-triage Category: Need triage label Aug 22, 2022
@LinZexiao LinZexiao self-assigned this Aug 25, 2022
@LinZexiao LinZexiao moved this to In Progress in Venus Project Aug 25, 2022
@Fatman13 Fatman13 removed the C-triage Category: Need triage label Sep 2, 2022
Repository owner moved this from In Progress to Done in Venus Project Sep 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-dev-productivity Category: Developer productivity
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants