zold-io/zold

Are hosting bonuses occupied forever?

Open

#795 opened on Apr 2, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Ruby (54 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (203 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug

As docs says:

Every hour wts.zold.io server (you can see its source code) selects the best 8 nodes out of those it can see and pays them 1 ZLD, distributing equally. If it can’t find eight nodes, it uses as many as it can find.

https://blog.zold.io/2018/08/14/hosting-bonuses.html

It seems that current situatuion leaves no chance for new node holder to get a payment in a weeks or months. There's number of nodes with score of 100+. Those players blocks others from getting into "top" list. So it seems that there's no way for new node holder to get a reward unless old players leave network.

Probably newcomer supposed to just overwhelm old players with computational power? That's a little bit unclear for now.

My proposal is to make hosting bonuses distribution more encouraging, e.g.:

  • reward N top nodes
  • also reward M random nodes, excluding top ones

To Reproduce

Steps to reproduce the behavior:

  1. Run new node
  2. Wait for days
  3. Get nothing

Expected behavior

  1. Run new node
  2. Get a reward in reasonable amount of time

Contributor guide

Research direction
Propose a new algorithm for distributing hosting bonuses to reward both top nodes and random nodes to encourage newcomers. Investigate the current scoring system and suggest modifications.
Tech stack
ruby
Domain
backenddistributed systems
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Ruby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75