Skip to content

gittensor-ai-lab/sparkinfer: raise credibility threshold to 40% (min_credibility 0.4)#1564

Closed
ai-hpc wants to merge 1 commit into
entrius:testfrom
ai-hpc:sparkinfer-credibility-threshold
Closed

gittensor-ai-lab/sparkinfer: raise credibility threshold to 40% (min_credibility 0.4)#1564
ai-hpc wants to merge 1 commit into
entrius:testfrom
ai-hpc:sparkinfer-credibility-threshold

Conversation

@ai-hpc

@ai-hpc ai-hpc commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Sets the sparkinfer eligibility min_credibility to 0.4 (40%) in master_repositories.json — a contributor must reach ≥40% credibility before earning emissions on this repo.

Why: sparkinfer has seen repeated low-credibility farming — sybil pairs and coordinated copycat rings (documented in the repo's .github/FLAGGED.md). A 40% credibility floor makes fresh throwaway/sybil accounts ineligible until they've built a real track record, without affecting established contributors. Speedup-only scoring (fixed_base_score, eval:* label multipliers) is unchanged; this only gates who is eligible.

Only the sparkinfer entry's min_credibility changes (0.0 → 0.4); everything else (maintainer_cut, emission_share, label_multipliers) is untouched.

@xiao-xiao-mao xiao-xiao-mao Bot added the enhancement New feature or request label Jul 1, 2026
…40%)

Require >= 40% contributor credibility to earn on sparkinfer — raises the bar against low-credibility
sybil/copycat farming (documented in the repo's .github/FLAGGED.md). Only min_credibility changes
(0.0 -> 0.4); maintainer_cut / emission_share / label_multipliers untouched.
@ai-hpc ai-hpc force-pushed the sparkinfer-credibility-threshold branch from 406d41e to 3453192 Compare July 1, 2026 08:26
@ai-hpc ai-hpc changed the base branch from main to test July 1, 2026 08:26
@ai-hpc ai-hpc closed this Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants