{"action":"created","issue":{"url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/176","repository_url":"https://api.github.com/repos/zcoinofficial/zcoin","labels_url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/176/labels{/name}","comments_url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/176/comments","events_url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/176/events","html_url":"https://github.com/zcoinofficial/zcoin/issues/176","id":293793009,"number":176,"title":"Take uptime to consideration for znode reward","user":{"login":"kp0z","id":34752212,"avatar_url":"https://avatars1.githubusercontent.com/u/34752212?v=4","gravatar_id":"","url":"https://api.github.com/users/kp0z","html_url":"https://github.com/kp0z","followers_url":"https://api.github.com/users/kp0z/followers","following_url":"https://api.github.com/users/kp0z/following{/other_user}","gists_url":"https://api.github.com/users/kp0z/gists{/gist_id}","starred_url":"https://api.github.com/users/kp0z/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kp0z/subscriptions","organizations_url":"https://api.github.com/users/kp0z/orgs","repos_url":"https://api.github.com/users/kp0z/repos","events_url":"https://api.github.com/users/kp0z/events{/privacy}","received_events_url":"https://api.github.com/users/kp0z/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-02-02T07:07:22Z","updated_at":"2018-02-07T11:40:56Z","closed_at":null,"author_association":"NONE","body":"Hi guys,\r\n\r\nI got a better understanding thanks to @oti-dev on #174 \r\n\r\nSo uptime so far is just used as an **entry requirement** for shortlist\r\n\r\nCould we consider uptime as another factor for the sorting algorithm inside the shortlist? E.g: the longer uptime a znode is, the higher rank it becomes?\r\n\r\nThanks."},"comment":{"url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/comments/363743569","html_url":"https://github.com/zcoinofficial/zcoin/issues/176#issuecomment-363743569","issue_url":"https://api.github.com/repos/zcoinofficial/zcoin/issues/176","id":363743569,"user":{"login":"kp0z","id":34752212,"avatar_url":"https://avatars1.githubusercontent.com/u/34752212?v=4","gravatar_id":"","url":"https://api.github.com/users/kp0z","html_url":"https://github.com/kp0z","followers_url":"https://api.github.com/users/kp0z/followers","following_url":"https://api.github.com/users/kp0z/following{/other_user}","gists_url":"https://api.github.com/users/kp0z/gists{/gist_id}","starred_url":"https://api.github.com/users/kp0z/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kp0z/subscriptions","organizations_url":"https://api.github.com/users/kp0z/orgs","repos_url":"https://api.github.com/users/kp0z/repos","events_url":"https://api.github.com/users/kp0z/events{/privacy}","received_events_url":"https://api.github.com/users/kp0z/received_events","type":"User","site_admin":false},"created_at":"2018-02-07T11:40:56Z","updated_at":"2018-02-07T11:40:56Z","author_association":"NONE","body":"so if a longevity node get pay it will be back to the end of qualified queue, i think our qualified queue (sort with last paid block) eliminates **double pay** quite well\r\ne.g. assume 1500 qualified nodes are static, we will have 150 nodes in shortlist, given node X get pay this round, i believe X will wait for 1350 blocks to get back in shortlist\r\n\r\nproblem with current _lotto_ algo in shortlist is that it doesn't guarantee (? pls correct me if im wrong) that a node will get pay :neckbeard: \r\nspecifically is this algo here https://github.com/zcoinofficial/zcoin/blob/master/src/znode.cpp#L144\r\n\r\nuptime is just my suggestion as a proof of service, can definitely use something else as long as it could determine a payment timeframe for nodes fairly 💵 \r\n\r\n"}}
{"actor":{"display_login":"kp0z"}}