{"action":"opened","issue":{"url":"https://api.github.com/repos/MoneroOcean/nodejs-pool/issues/22","repository_url":"https://api.github.com/repos/MoneroOcean/nodejs-pool","labels_url":"https://api.github.com/repos/MoneroOcean/nodejs-pool/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/MoneroOcean/nodejs-pool/issues/22/comments","events_url":"https://api.github.com/repos/MoneroOcean/nodejs-pool/issues/22/events","html_url":"https://github.com/MoneroOcean/nodejs-pool/issues/22","id":316588332,"number":22,"title":"Database explosion - longRunner possible bug.","user":{"login":"bobbieltd","id":29669374,"avatar_url":"https://avatars1.githubusercontent.com/u/29669374?v=4","gravatar_id":"","url":"https://api.github.com/users/bobbieltd","html_url":"https://github.com/bobbieltd","followers_url":"https://api.github.com/users/bobbieltd/followers","following_url":"https://api.github.com/users/bobbieltd/following{/other_user}","gists_url":"https://api.github.com/users/bobbieltd/gists{/gist_id}","starred_url":"https://api.github.com/users/bobbieltd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bobbieltd/subscriptions","organizations_url":"https://api.github.com/users/bobbieltd/orgs","repos_url":"https://api.github.com/users/bobbieltd/repos","events_url":"https://api.github.com/users/bobbieltd/events{/privacy}","received_events_url":"https://api.github.com/users/bobbieltd/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-22T15:28:29Z","updated_at":"2018-04-22T15:28:29Z","closed_at":null,"author_association":"NONE","body":"It’s only my theory that there is a bug in longRunner with troublesome network. I guess it won’t happen with Monero because Monero network with high hashrate and stable.\r\n\r\nIn theory, block with higher number will have timestamp higher. For example, block m and block n, if m>n, timestamp of block m will > timestamp of block n.\r\nWith pool forking (turtlecoin case), it makes two thing, two blocks with same height but different timestamp (one correct and one forked).\r\nWith timestamp attacks (turtlecoin and graft cases), block lower have higher timestamp.\r\n\r\nBy somehow, with these hapenning, database at my pools keep growing, turtlecoin (21G) and graft(24G).\r\nIf you have free time or find something in the future, I hope you can help to fix this."}}
{"actor":{"display_login":"bobbieltd"}}