{"action":"closed","issue":{"url":"https://api.github.com/repos/gamerammo/clutchat/issues/3","repository_url":"https://api.github.com/repos/gamerammo/clutchat","labels_url":"https://api.github.com/repos/gamerammo/clutchat/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/gamerammo/clutchat/issues/3/comments","events_url":"https://api.github.com/repos/gamerammo/clutchat/issues/3/events","html_url":"https://github.com/gamerammo/clutchat/issues/3","id":305458431,"number":3,"title":"Token Implementation Strategy","user":{"login":"xcesiv","id":10799441,"avatar_url":"https://avatars3.githubusercontent.com/u/10799441?v=4","gravatar_id":"","url":"https://api.github.com/users/xcesiv","html_url":"https://github.com/xcesiv","followers_url":"https://api.github.com/users/xcesiv/followers","following_url":"https://api.github.com/users/xcesiv/following{/other_user}","gists_url":"https://api.github.com/users/xcesiv/gists{/gist_id}","starred_url":"https://api.github.com/users/xcesiv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xcesiv/subscriptions","organizations_url":"https://api.github.com/users/xcesiv/orgs","repos_url":"https://api.github.com/users/xcesiv/repos","events_url":"https://api.github.com/users/xcesiv/events{/privacy}","received_events_url":"https://api.github.com/users/xcesiv/received_events","type":"User","site_admin":false},"labels":[{"id":845558340,"url":"https://api.github.com/repos/gamerammo/clutchat/labels/enhancement","name":"enhancement","color":"a2eeef","default":true}],"state":"closed","locked":false,"assignee":{"login":"xcesiv","id":10799441,"avatar_url":"https://avatars3.githubusercontent.com/u/10799441?v=4","gravatar_id":"","url":"https://api.github.com/users/xcesiv","html_url":"https://github.com/xcesiv","followers_url":"https://api.github.com/users/xcesiv/followers","following_url":"https://api.github.com/users/xcesiv/following{/other_user}","gists_url":"https://api.github.com/users/xcesiv/gists{/gist_id}","starred_url":"https://api.github.com/users/xcesiv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xcesiv/subscriptions","organizations_url":"https://api.github.com/users/xcesiv/orgs","repos_url":"https://api.github.com/users/xcesiv/repos","events_url":"https://api.github.com/users/xcesiv/events{/privacy}","received_events_url":"https://api.github.com/users/xcesiv/received_events","type":"User","site_admin":false},"assignees":[{"login":"xcesiv","id":10799441,"avatar_url":"https://avatars3.githubusercontent.com/u/10799441?v=4","gravatar_id":"","url":"https://api.github.com/users/xcesiv","html_url":"https://github.com/xcesiv","followers_url":"https://api.github.com/users/xcesiv/followers","following_url":"https://api.github.com/users/xcesiv/following{/other_user}","gists_url":"https://api.github.com/users/xcesiv/gists{/gist_id}","starred_url":"https://api.github.com/users/xcesiv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xcesiv/subscriptions","organizations_url":"https://api.github.com/users/xcesiv/orgs","repos_url":"https://api.github.com/users/xcesiv/repos","events_url":"https://api.github.com/users/xcesiv/events{/privacy}","received_events_url":"https://api.github.com/users/xcesiv/received_events","type":"User","site_admin":false},{"login":"swaevior","id":33510992,"avatar_url":"https://avatars1.githubusercontent.com/u/33510992?v=4","gravatar_id":"","url":"https://api.github.com/users/swaevior","html_url":"https://github.com/swaevior","followers_url":"https://api.github.com/users/swaevior/followers","following_url":"https://api.github.com/users/swaevior/following{/other_user}","gists_url":"https://api.github.com/users/swaevior/gists{/gist_id}","starred_url":"https://api.github.com/users/swaevior/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/swaevior/subscriptions","organizations_url":"https://api.github.com/users/swaevior/orgs","repos_url":"https://api.github.com/users/swaevior/repos","events_url":"https://api.github.com/users/swaevior/events{/privacy}","received_events_url":"https://api.github.com/users/swaevior/received_events","type":"User","site_admin":false}],"milestone":null,"comments":1,"created_at":"2018-03-15T08:37:49Z","updated_at":"2018-04-14T04:16:30Z","closed_at":"2018-04-14T04:16:30Z","author_association":"OWNER","body":"# Gamerammo Token Implementation Strategy\r\nThis document provides an observation on the current state of the Gamerammo Token, the detailed objective reasoning for such an observation, a reflection on the observation in the form of an solution proposal, a recommended first course of action, and a prediction of expected results.\r\n\r\n## Overview\r\nThe Gamerammo Token is in need of definitive parameters, actionability, and production environment. It needs to comply with the highest standards of immutability on the chain & be able to go through any number of regulation years. The options based on our constraints for such a task are to build a token with a regulation contract built alongside the token, build a regulation reference library and corresponding token standard for such a case, or avoid regulatory discussion entirely by adverting key technical flags. \r\n\r\n### Objective\r\nWe have chosen to build a custom regulator and token standard. There is currently no Token Standard Implementation Strategy that brings all together what we aim to achieve in terms of fiscal data, security, and capability. Thus, we must either avoid regulatory discussion or develop our own Implementation Strategy. Given that we are in the United States. developing a product targeting so many users within that space, and need as much flexibility in our code as possible,  it is obvious to us we must build our own custom system. \r\n\r\n### Background\r\nThus far, we have find two token standards that meet the quality of standard we’re trying to achieve. The first being Dexeran’s [ERC-223 Token Standard](https://github.com/dexeran/ERC223-token-standard) which we have forked [here](https://github.com/gamerammo/ERC223-token-standard). This fills the gaps in the ERC-20 Standard that develop too much risk & are too loose on user inherit ability to wield a wallet that can send tokens. The second being the [R Token](https://github.com/harborhq/r-token) by Harbor, which we have formed [here](https://github.com/gamerammo/r-token). \r\n\r\n## Problems\r\nThe obstacles around which the problem of instituting a token implementation system for Gamerammo is the inherent lack of details in the structure of an ERC223 Token Standard and the R Token being designed for the ERC20 Standard.\r\n\r\n### ERC223 Token Standard\r\nThe ERC223 Token is purposefully design to fill gaps in the ERC20 Token Standard. That being said, it also implies the vast scope intended by the token. While good as a jumping off point, we need something more specific.Given the lack of token standards beyond ERC223 in this regard, we need a new standard.\r\n\r\n### R Token\r\nThe R Token is designed using the ERC20 Token Standard, which has security issues that we believe are unacceptable for a regulatory token standard. Thus, it must be at least re-vamped. Additionally, we want the regulatory system to be more autonomous and isolated from the smart contract of the token. Given the nature of using ERC223 & our networks objectuve, we will need something far more customized.\r\n\r\n## Proposed Solution\r\nGamerammo must design and implement its own Token Standard. A derivative of the ERC-223 token, it must adopted the same capabilities as the R Token & the regulator. Upon initial assessment, developing the specific regulatory functions within the Clutchat environment that are unique to it and the Gamerammo Token in tandem with optimal performance of the Token Standard within Clutchat the appropriate decision. Of course, keeping in mind that we aim to develop a Regulatory Token Standard for the Ethereum Classic Blockchain.\r\n\r\n### First Step\r\nTo do this we must first derive the answer for what all regulations the Regulatory Token Standard, deriving from these what we can from the R Token, apply these to the ERC-223, and make any additions or corrections so the code will compile and work on the ETC Blockchain.\r\n\r\n## End Goal\r\nThe end goal of resolving this issue using the proposed solution and taking the said first step should result in the production of a new Token Standard, a regulator, a  User Interface for gamers to interact with their account, and the Gamerammo Token.\r\n\r\n### Ludu Token Standard\r\nThe ERC-223 Regulatory Token Standard, code name Ludu Token Standard, will be the Token Standard in-which people use to develop an optimal token to compile with any sort of regulations. It will be a Smart Contract written in Solidity that will be usable as a fork token or node module that the contract creator may call to in reference. It will be able to interact with a reference regulations library that will be able to determine if the token in transit does or not does pass regulation guidelines specified by the developer by referencing an independent regulation processor that is independent of the exchange. In either scenario, the user will be prompted and deemed reliable for the money exchange set forth. This will be first developed as the Gamerammo Token and later adjusted for a more robust use case.\r\n\r\n### Regulator\r\nAn independent smart contract reference library that a Ludu Token Standard compliment smart contract will reference for functions to apply certain regulations or parts of regulations to an ERC-223 Token. This will become a new repository with regulations necessary for the Gamerammo Token being the first on the list.\r\n\r\n### Gamerammo Token\r\nGamerammo is the first example of a Ludu Token Standard compliment token. To be developed as the genesis token of the Gamerchain, an Ethereum Classic Network sidechain. The Gamerammo Token will follow the regulations set forth by the R Standard and lead to the development of a Wallet-like Interface.\r\n\r\n### “Wallet-like” Interface\r\nAn end-user system for interaction, a “wallet” of sorts, will be the end-users Interface with the regulator, managing their Gamerammo account, and interacting with the financial management tools will plan to offer them. Initial impression is to fork [EtherWallet](https://github.com/ethereumproject/etherwallet/). This may mean a forking of [ClassicMask](https://github.com/ethereumcommonwealth/classicmask/) is in order at some point as well.\r\n\r\n## Issue Details\r\n### __**Related Project(s)**__\r\n  + **[gamerammo/token](https://github.com/gamerammo/token)**\r\n    - _Gamerammo Token_: A hard fork of the [Ludu Token Standard](https://github.com/ludurel/ludu-token-standard)\r\n    - _Original Author_: [Ludurel](https://github.com/ludurel)\r\n    - _Initial Fork_: Commit [xxx](https://github.com/ludurel/ludu-token-standard)\r\n  + **[gamerammo/relativulator](https://github.com/ludurel/relativulator)**\r\n    -  _Regulation Specifications_: The working repo for [branch/gamerammo](https://github.com/ludurel/relativulator/tree/gamerammo) of the [Relativulator](https///github.com/ludurel/relativulator).\r\n    - _Original Author_:  [Ludurel](https//github.com/ludurel/relativulator)\r\n  + **[gamerammo/r-token](https://github.com/gamerammo/r-token)**\r\n    - _Original Repo_: This is  a reference fork of [R Token](https://github.com/harborhq/r-token) used  for testing.\r\n    - _Original Aurhor_: [Harbor](https://github.com/hardborhq)\r\n  + **[gamerammo/ERC223-token-standard](https://github.com/gamerammo/ERC223-token-standard)**\r\n    - _Original Repo_: This is a reference fork of [dexaran/ERC223-token-standard](https://github.com/dexaran/ERC223-token-Standard)\r\n    - _Original Author_: [Dexaran](https://github.com/dexaran)"}}
{"actor":{"display_login":"xcesiv"}}