fix: ScoreMultiplierBase 100 -> 10000 for meaningful trust scores
Without sufficient multiplier, integer division produces 0 for most component scores. Increasing to 10_000 ensures trust scores reflect actual staking, referral, tiki, and perwerde contributions.
This commit is contained in:
@@ -82,7 +82,7 @@
|
||||
//! type RuntimeEvent = RuntimeEvent;
|
||||
//! type WeightInfo = pezpallet_trust::weights::BizinikiwiWeight<Runtime>;
|
||||
//! type Score = u128;
|
||||
//! type ScoreMultiplierBase = ConstU128<100>;
|
||||
//! type ScoreMultiplierBase = ConstU128<10_000>;
|
||||
//! type UpdateInterval = ConstU32<14400>; // ~1 day in blocks
|
||||
//! type StakingScoreSource = StakingScore;
|
||||
//! type ReferralScoreSource = Referral;
|
||||
|
||||
@@ -552,7 +552,7 @@ impl pezpallet_collective::Config<CouncilCollective> for Runtime {
|
||||
|
||||
parameter_types! {
|
||||
/// Base multiplier for trust score calculation
|
||||
pub const ScoreMultiplierBase: u128 = 100;
|
||||
pub const ScoreMultiplierBase: u128 = 10_000;
|
||||
/// Update interval for trust scores (roughly 1 day in blocks)
|
||||
pub const TrustUpdateInterval: BlockNumber = DAYS;
|
||||
/// Maximum batch size for trust score updates
|
||||
|
||||
Reference in New Issue
Block a user