{"action":"created","issue":{"url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/15","labels_url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/15/comments","events_url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/15/events","html_url":"https://github.com/CryptoConsortium/CCSS/issues/15","id":87137974,"number":15,"title":"No discussion of full nodes","user":{"login":"petertodd","id":7042,"avatar_url":"https://avatars.githubusercontent.com/u/7042?v=3","gravatar_id":"","url":"https://api.github.com/users/petertodd","html_url":"https://github.com/petertodd","followers_url":"https://api.github.com/users/petertodd/followers","following_url":"https://api.github.com/users/petertodd/following{/other_user}","gists_url":"https://api.github.com/users/petertodd/gists{/gist_id}","starred_url":"https://api.github.com/users/petertodd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/petertodd/subscriptions","organizations_url":"https://api.github.com/users/petertodd/orgs","repos_url":"https://api.github.com/users/petertodd/repos","events_url":"https://api.github.com/users/petertodd/events{/privacy}","received_events_url":"https://api.github.com/users/petertodd/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-10T23:08:04Z","updated_at":"2015-06-11T15:39:22Z","closed_at":null,"body":"Without a full node you're trusting miners to verify for you, which means that you can be fooled into accepting invalid payments by someone with access to hashing power. This is not hard! Pool security is quite poor, and even worse, the security of the connections between hasher to pool is often poor and hijackable.\r\n\r\nThe standard should explicitly require transaction validation infrastructure to be using full nodes to determine what the current blockchain is at all levels. (remember the full nodes can use pruning) Secondly, the security of those full nodes is important, and should be held to nearly the same standards as other transaction validation infrastructure. For instance, a full node running on a VPS has similar risks to running an exchange on a VPS, in that if the exchange runs on a physically controlled server but the full node runs on a VPS, hackng the VPS can still cause the server to accept invalid transactions as valid."},"comment":{"url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/comments/111176722","html_url":"https://github.com/CryptoConsortium/CCSS/issues/15#issuecomment-111176722","issue_url":"https://api.github.com/repos/CryptoConsortium/CCSS/issues/15","id":111176722,"user":{"login":"Abstrct","id":196776,"avatar_url":"https://avatars.githubusercontent.com/u/196776?v=3","gravatar_id":"","url":"https://api.github.com/users/Abstrct","html_url":"https://github.com/Abstrct","followers_url":"https://api.github.com/users/Abstrct/followers","following_url":"https://api.github.com/users/Abstrct/following{/other_user}","gists_url":"https://api.github.com/users/Abstrct/gists{/gist_id}","starred_url":"https://api.github.com/users/Abstrct/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Abstrct/subscriptions","organizations_url":"https://api.github.com/users/Abstrct/orgs","repos_url":"https://api.github.com/users/Abstrct/repos","events_url":"https://api.github.com/users/Abstrct/events{/privacy}","received_events_url":"https://api.github.com/users/Abstrct/received_events","type":"User","site_admin":false},"created_at":"2015-06-11T15:39:22Z","updated_at":"2015-06-11T15:39:22Z","body":"Hey Peter,\r\n\r\nThanks for the suggestion, I think this addition to the standard makes a huge amount of sense. \r\n\r\nIs there somewhere in the standard that this fits already or do we need a new aspect? My initial review makes me think that it will need it's own section, likely under operations.\r\n\r\nPerhaps: 2.05 Transaction Validation \r\n\r\nIn addition to describing proper full node requirements, we could also use this section to prescribe best practices for unconfirmed transactions and dealing with orphaned transactions which once validated. \r\n\r\n "}}