diff --git a/.gitignore b/.gitignore index ab54f6e..525a4fb 100644 --- a/.gitignore +++ b/.gitignore @@ -3,4 +3,6 @@ .vscode .idea .history -.DS_Store \ No newline at end of file +.DS_Store +GOOGLE_APPLICATION_CREDENTIALS.json +tally.db \ No newline at end of file diff --git a/api/README.md b/api/README.md index d2f8119..88039d7 100644 --- a/api/README.md +++ b/api/README.md @@ -7,6 +7,9 @@ Apis: /getBPs +/getAllAuditors + +/getAuditor/ ## Envirement @@ -15,10 +18,17 @@ Apis: $ pip3 install -r requirements.txt ``` -## init db + + + +## set google translation credentials +## copy the Google auth file in the api directory and rename it GOOGLE_APPLICATION_CREDENTIALS.json + + + ### Setup supervisor for deamon @@ -55,11 +65,14 @@ killasgroup=true ### Set crontab ```shell -$ vim /etc/crontab +$ crontab -e # add command 0 0 * * * curl localhost:8000/getJson >> /path/to/crontab.log 2>&1 - +0 0 * * * curl localhost:8000/getAuditorJson >> /path/to/crontab.log 2>&1 +# 3min call tally json files +*/4 0 * * * ./minutely_get_tally.sh >> /path/to/crontab.log 2>&1 +/root/referendum/api/minutely_get_tally.sh ``` ### Set nginx @@ -98,5 +111,118 @@ supervisord start boswps Or: -Login http://localhost:9001, operation it with UI. +Login http:// localhost:9001, operation it with UI. + +## init dataset +```shell +curl localhost:8000/getJson && curl localhost:8000/getAuditorJson +``` +### Support Languages(Power By Google) + +| 语言 | ISO-639-1 代码| +| ---- | ---- | +|南非荷兰语 |af| +|阿尔巴尼亚语 |sq| +|阿姆哈拉语 |am| +|阿拉伯语 |ar| +|亚美尼亚语 |hy| +|阿塞拜疆语 |az| +|巴斯克语 |eu| +|白俄罗斯语 |be| +|孟加拉语 |bn| +|波斯尼亚语 |bs| +|保加利亚语 |bg| +|加泰罗尼亚语 |ca| +|宿务语 ceb |(ISO-639-2)| +|中文（简体） |zh-CN (BCP-47) 程序传入cn| +|中文（繁体） |zh-TW (BCP-47) 程序传入tw| +|科西嘉语 |co| +|克罗地亚语 |hr| +|捷克语 |cs| +|丹麦语 |da| +|荷兰语 |nl| +|英语 |en| +|世界语 |eo| +|爱沙尼亚语 |et| +|芬兰语 |fi| +|法语 |fr| +|弗里斯兰语 |fy| +|加利西亚语 |gl| +|格鲁吉亚语 |ka| +|德语 |de| +|希腊语 |el| +|古吉拉特语 |gu| +|海地克里奥尔语 |ht| +|豪萨语 |ha| +|夏威夷语 |haw (ISO-639-2)| +|希伯来语 |he**| +|印地语 |hi| +|苗语 |hmn (ISO-639-2)| +|匈牙利语 |hu| +|冰岛语 |is| +|伊博语 |ig| +|印度尼西亚语 |id| +|爱尔兰语 |ga| +|意大利语 |it| +|日语 |ja| +|爪哇语 |jw| +|卡纳达语 |kn| +|哈萨克语 |kk| +|高棉语 |km| +|韩语 |ko| +|库尔德语 |ku| +|吉尔吉斯语 |ky| +|老挝语 |lo| +|拉丁语 |la| +|拉脱维亚语 |lv| +|立陶宛语 |lt| +|卢森堡语 |lb| +|马其顿语 |mk| +|马尔加什语 |mg| +|马来语 |ms| +|马拉雅拉姆语 |ml| +|马耳他语 |mt| +|毛利语 |mi| +|马拉地语 |mr| +|蒙古语 |mn| +|缅甸语 |my| +|尼泊尔语 |ne| +|挪威语 |no| +|尼杨扎语（齐切瓦语） |ny| +|普什图语 |ps| +|波斯语 |fa| +|波兰语 |pl| +|葡萄牙语（葡萄牙、巴西） |pt| +|旁遮普语 |pa| +|罗马尼亚语 |ro| +|俄语 |ru| +|萨摩亚语 |sm| +|苏格兰盖尔语 |gd| +|塞尔维亚语 |sr| +|塞索托语 |st| +|修纳语 |sn| +|信德语 |sd| +|僧伽罗语 |si| +|斯洛伐克语 |sk| +|斯洛文尼亚语 |sl| +|索马里语 |so| +|西班牙语 |es| +|巽他语 |su| +|斯瓦希里语 |sw| +|瑞典语 |sv| +|塔加路语（菲律宾语） |tl| +|塔吉克语 |tg| +|泰米尔语 |ta| +|泰卢固语 |te| +|泰语 |th| +|土耳其语 |tr| +|乌克兰语 |uk| +|乌尔都语 |ur| +|乌兹别克语 |uz| +|越南语 |vi| +|威尔士语 |cy| +|班图语 |xh| +|意第绪语 |yi| +|约鲁巴语 |yo| +|祖鲁语 |zu| diff --git a/api/auditor_tally.json b/api/auditor_tally.json new file mode 100755 index 0000000..5627a6f --- /dev/null +++ b/api/auditor_tally.json @@ -0,0 +1,398 @@ +{ + "appleofmyeye": { + "id": "appleofmyeye", + "candidate": { + "candidate_name": "appleofmyeye", + "locked_tokens": "100.0000 BOS", + "total_votes": 3100, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "1": 1, + "total": 1, + "proxies": 0, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 3100, + "total": 3100 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 3100, + "total": 3100 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "https://static.vecteezy.com/system/resources/previews/000/437/407/non_2x/vector-apple-icon.jpg", + "bio": "Aspire to become the best apple auditor", + "contact": "996996" + }, + "is_auditor": false + }, + "eoscityioeos": { + "id": "eoscityioeos", + "candidate": { + "candidate_name": "eoscityioeos", + "locked_tokens": "100.0000 BOS", + "total_votes": 20528359802, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "1": 6, + "total": 6, + "proxies": 1, + "accounts": 5 + }, + "accounts": { + "0": 0, + "1": 235554530, + "total": 235554530 + }, + "proxies": { + "0": 0, + "1": 20292805272, + "total": 20292805272 + }, + "staked": { + "0": 0, + "1": 20528359802, + "total": 20528359802 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "", + "bio": "Hello, this is chester and as co-funder from eosCityand, my background is cloud solution design as had been work in IBM/Intel as solution architect.\nI play as miner of ethernum/litcoin since 2015, since 2018, i'm mvoing focus into EOS as well, we are focus on the community building of EOS/BOS including training, \neducation for EOS/BOS, we also have couple of articles published for BOS brief features and EOS smart contract code development. \nMeanwhile we also providng technology service support for DAPP dev and infrastructure service for DAPP needs, recently, we have business case to work with enterprise customer\nfor integration BOS as platform solution in the IOT.\nWe are actively in the Asia including Taiwan and Hongkong and continue to work on the EOS/BOS blockchain solution to enterprise and to end-user, we can provide\ndifferent point of view including technolgy and usability view to help to know what's most importnat feature for BOS chain.", + "contact": "chester.kuo@gmail.com" + }, + "is_auditor": false + }, + "happybeancat": { + "id": "happybeancat", + "candidate": { + "candidate_name": "happybeancat", + "locked_tokens": "100.0000 BOS", + "total_votes": 0, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "https://images.pexels.com/photos/542502/pexels-photo-542502.jpeg?auto=compress&cs=tinysrgb&dpr=2&h=750&w=1260", + "bio": "I am a happy cat, hope to become a good wps auditor", + "contact": "happycat@cat.com" + }, + "is_auditor": false + }, + "icelandesert": { + "id": "icelandesert", + "candidate": { + "candidate_name": "icelandesert", + "locked_tokens": "100.0000 BOS", + "total_votes": 0, + "is_active": 1, + "unstaking_end_time_stamp": "2019-08-16T03:18:45" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "", + "bio": "afd", + "contact": "adf" + }, + "is_auditor": false + }, + "kuqwwiqyxuxt": { + "id": "kuqwwiqyxuxt", + "candidate": { + "candidate_name": "kuqwwiqyxuxt", + "locked_tokens": "100.0000 BOS", + "total_votes": 11387680376, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "1": 2, + "total": 2, + "proxies": 1, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 150002, + "total": 150002 + }, + "proxies": { + "0": 0, + "1": 11387530374, + "total": 11387530374 + }, + "staked": { + "0": 0, + "1": 11387680376, + "total": 11387680376 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "", + "bio": "徐勇 DappPub联合创始人\n12年毕业于同济大学计算机系，曾工作于豆瓣网和饿了么，之前有一次创业经历。\n在区块链行业涉及的工作包括技术、产品、经济模型、行业研究等方面", + "contact": "xuyong@dap.pub" + }, + "is_auditor": false + }, + "myramyramyra": { + "id": "myramyramyra", + "candidate": { + "candidate_name": "myramyramyra", + "locked_tokens": "100.0000 BOS", + "total_votes": 13464873831, + "is_active": 1, + "unstaking_end_time_stamp": "2019-09-20T11:31:54" + }, + "stats": { + "votes": { + "1": 3, + "total": 3, + "proxies": 3, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 13464873831, + "total": 13464873831 + }, + "staked": { + "0": 0, + "1": 13464873831, + "total": 13464873831 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "https://eosignite.com/wp-content/uploads/2018/08/myra-280x280.png", + "bio": "Myra graduated from China’s prestigious Central Judicial Police Academy and has eight years of experience in consulting and primary account management. Myra is an extraordinary female entrepreneur who has been an integral element of investment and the founding of four high-tech companies. Myra is the co-founder of international endeavors of Omnia Spot Limited and Webao.co. In 2018, she joined EOS Gravity to fully implement her technical skills to expand the community department overseas. She currently is the Deputy Executive Director of the EOS Alliance and a Custodian of EOS DAC (Decentralized Autonomous Community).", + "contact": "wang.khaleesi@gmail.com" + }, + "is_auditor": false + }, + "sevenbos2345": { + "id": "sevenbos2345", + "candidate": { + "candidate_name": "sevenbos2345", + "locked_tokens": "100.0000 BOS", + "total_votes": 20292842610, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "1": 2, + "total": 2, + "proxies": 1, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 37338, + "total": 37338 + }, + "proxies": { + "0": 0, + "1": 20292805272, + "total": 20292805272 + }, + "staked": { + "0": 0, + "1": 20292842610, + "total": 20292842610 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "", + "bio": "Economics Ph.D, graduated from Central University of Finance and Economics, had been a vising scholar in Georgia Institute of technology U.S.A, serve as the chief economist of KOFO Foundation and the former chief researcher fellow in Huobi Academy of Blockchain Application. Author of \"block chain: reshaping the economy and the world\" (CITIC Publishing House) and \"the application of blockchain in the insurance industry” included in the \"Chinese Fintech Development Report 2017\" (Social Scientific Publishing House); participate in the establishment and optimization of SMARTChain blockchain assets assessment model, has rich experience in technology trend, blockchain application and investment areas.\n", + "contact": "hypiota@sina.com" + }, + "is_auditor": false + }, + "sheldonhuang": { + "id": "sheldonhuang", + "candidate": { + "candidate_name": "sheldonhuang", + "locked_tokens": "0.0000 BOS", + "total_votes": 0, + "is_active": 0, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "https://stocksandwich.com/stock-images/thumbnails/mans-best-friend_large.jpg", + "bio": "### BIOS \n\nAim to become one of the best auditor (auditor test)\n*Lean*\n\n**Bold Size**", + "contact": "example@example.com" + }, + "is_auditor": false + }, + "testertester": { + "id": "testertester", + "candidate": { + "candidate_name": "testertester", + "locked_tokens": "0.0000 BOS", + "total_votes": 0, + "is_active": 0, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "https://66.media.tumblr.com/026b8fe1a1b843feff56babe49d2de51/tumblr_ppam2zwV0J1sfie3io1_1280.jpg", + "bio": "# Auditor Markdown Test\n---\n__Advertisement :)__\n\n- __[pica](https://nodeca.github.io/pica/demo/)__ - high quality and fast image\n resize in browser.\n- __[babelfish](https://github.com/nodeca/babelfish/)__ - developer friendly\n i18n with plurals support and easy syntax.\n\nYou will like those projects!\n\n---\n\n\n##### h5\n###### h6\n\n\n## Horizontal Rules\n\n___\n\n---\n\n***\n\n\n\n\n## Tables\n\n| Option | Description |\n| ------ | ----------- |\n| data | path to data files to supply the data that will be passed into templates. |\n| engine | engine to be used for processing templates. Handlebars is the default. |\n| ext | extension to be used for dest files. |\n\nRight aligned columns\n\n| Option | Description |\n| ------:| -----------:|\n| data | path to data files to supply the data that will be passed into templates. |\n| engine | engine to be used for processing templates. Handlebars is the default. |\n| ext | extension to be used for dest files. |\n\n\n### [Custom containers](https://github.com/markdown-it/markdown-it-container)\n\n::: warning\n*here be dragons*\n:::\n", + "contact": "example@example.com" + }, + "is_auditor": false + }, + "victor233333": { + "id": "victor233333", + "candidate": { + "candidate_name": "victor233333", + "locked_tokens": "100.0000 BOS", + "total_votes": 20292842610, + "is_active": 1, + "unstaking_end_time_stamp": "1970-01-01T00:00:00" + }, + "stats": { + "votes": { + "1": 2, + "total": 2, + "proxies": 1, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 37338, + "total": 37338 + }, + "proxies": { + "0": 0, + "1": 20292805272, + "total": 20292805272 + }, + "staked": { + "0": 0, + "1": 20292842610, + "total": 20292842610 + }, + "block_num": 43254093 + }, + "bio": { + "avatar": "", + "bio": "Victor是区块链治理的深耕者，曾深度参与EOS、GXC、LAMB、BOS等多条公链的社区治理，并提出了多个对于社区发展有着导向性的提案。作为EOS华语治理社区的核心成员、EMAC911小组的创始成员、BOS核心仲裁庭仲裁员，累计参与过超过300场各大公链的治理会议，并与EMAC911小组成员一起冻结了超过价值1500万RMB的被盗EOS。同时对于区块链争议解决机制有着非常深入的研究和实操经验。Victor也是国内最大的高校区块链社区——Young区块链社区的创始人之一，Young社区目前有30+所高校加入，将为区块链行业输送更多的优质人才以及为区块链从业者对接各类高校资源提供帮助。\nVictor is a deep-rooted person in blockchain management. He has been deeply involved in community governance of EOS, GXC, LAMB, BOS and other public chains, and has proposed several proposals for community development. As a core member of the EOS Chinese language governance community, a founding member of the EMAC911 team, and an arbitrator of the BOS core arbitral tribunal, he has participated in more than 300 governance meetings of major public chains and has frozen more than 15 million RMB with the EMAC911 team members. Steal EOS. At the same time, it has very in-depth research and practical experience for the blockchain dispute resolution mechanism. Victor is also one of the founders of the Young Blockchain Community, the largest blockchain community in China. The Young community currently has 30+ colleges and universities to join, which will bring more talents and blockchains to the blockchain industry. Practitioners can help with the resources of various colleges and universities.", + "contact": "603409320@qq.com" + }, + "is_auditor": false + } +} \ No newline at end of file diff --git a/api/index.py b/api/index.py index 0c992c2..5c4634a 100755 --- a/api/index.py +++ b/api/index.py @@ -1,11 +1,24 @@ from flask import Flask import flask from eospy.cleos import Cleos +from init_db import * from utils import * +from translation import * import json -from init_db import * from urllib.request import urlopen +# init global config +cfg = Config.select().limit(1).get() +# init_log +init_log('getBPs') +init_log('json') +init_log('auditorjson') +init_log('getAllAuditors') +init_log('getAllProposals') +init_log('review') +init_log('finish') + + # constants BOS_URLS = [ 'https://api.boscore.io' @@ -13,10 +26,12 @@ ,'https://api-bos.eospacex.com' ] -TALLY_API = "https://s3.amazonaws.com/bos.referendum/referendum/tallies/latest.json" -VOTE_TOTAL_API = "https://s3.amazonaws.com/bos.referendum/referendum/summaries/latest.json" - -BP_TOTAL_VOTES = 311193750652 +TALLY_API = cfg.TALLY_API +VOTE_TOTAL_API = cfg.VOTE_TOTAL_API +AUDITOR_TOTAL_API = cfg.AUDITOR_TOTAL_API +BP_TOTAL_VOTES = cfg.BP_TOTAL_VOTES +PROPOSAL_MEET_DAYS = cfg.PROPOSAL_MEET_DAYS +AUDITOR_MEET_DAYS = cfg.PROPOSAL_MEET_DAYS # util func def test_net_is_working(urls): @@ -52,84 +67,192 @@ def bpinfos(): resp = flask.Response(result) resp.headers['Access-Control-Allow-Origin'] = '*' return resp - +# init proposal data and daily caculate propsal condition meet @app.route('/getJson') def jsoninfo(): logger = reactive_log('json') - url_index = test_net_is_working(BOS_URLS) - logger.info('BOS Node ['+ str(url_index) + '] is working:' + BOS_URLS[url_index]) - ce = Cleos(url=BOS_URLS[url_index]) - - - # BP_TOTAL_VOTES = float(int(ce.get_table('eosio','eosio','global')['rows'][0]['total_activated_stake'])/10000) - # csv_file = csv.reader(open('sum.csv','r')) - # for s in csv_file: - # BP_TOTAL_VOTES - try: - rawtext = urlopen(VOTE_TOTAL_API, timeout=15).read() - NEW_BP_TOTAL_VOTES = json.loads(rawtext.decode('utf8'))['bp_votes'] + BP_TOTAL_VOTES = cfg.BP_TOTAL_VOTES + # try: + with open("vote_total_tally.json", 'r') as f: + NEW_BP_TOTAL_VOTES = json.loads(f.read())['bp_votes'] BP_TOTAL_VOTES = int(NEW_BP_TOTAL_VOTES) if int(NEW_BP_TOTAL_VOTES) > 0 else BP_TOTAL_VOTES - except Exception as err: - logger.error(err) print(BP_TOTAL_VOTES) - # try: # get tally json file proposals = {} - try: - rawtext=urlopen(TALLY_API,timeout=15).read() - proposals = json.loads(rawtext.decode('utf8')) - except Exception as err: - logger.error(err) + # try: + with open("proposal_tally.json", 'r') as f: + proposals = json.loads(f.read()) # get Voted Total #iterater the current proposals - for proposal in proposals: - proposal_item = proposals[proposal] - vote_key = proposal_item['stats']['votes'] - stake_key = proposal_item['stats']['staked'] - staked_total = float(int(proposal_item['stats']['staked']['total'])) if 'total' in stake_key else 0 - vote_total = proposal_item['stats']['votes']['total'] if 'total' in vote_key else 0 - vote_yes = proposal_item['stats']['votes']['1'] if '1' in vote_key else 0 - vote_no = proposal_item['stats']['votes']['0'] if '0' in vote_key else 0 + for proposal in proposals: + proposal_item = proposals[proposal] + vote_key = proposal_item['stats']['votes'] + stake_key = proposal_item['stats']['staked'] + staked_total = float(int(proposal_item['stats']['staked']['total'])) if 'total' in stake_key else 0 + vote_total = proposal_item['stats']['votes']['total'] if 'total' in vote_key else 0 + vote_yes = proposal_item['stats']['votes']['1'] if '1' in vote_key else 0 + vote_no = proposal_item['stats']['votes']['0'] if '0' in vote_key else 0 + _meet_conditions_days = 0 + _approved_by_vote = 0 + _approved_by_vote_date = None + _approved_by_BET = 0 + _reviewed_by_BET_date = None + _approved_by_BPs = 0 + _approved_by_BPs_date = None + _review = 0 + _review_date = None + _finish = 0 + _finish_date = None + # check if the proposal exists + try: + propos_count = Proposal.select().where(Proposal.name == proposal).count() + logger.info("propos_count:"+str(propos_count)) + # the proposal exists + if propos_count > 0: + # check if the proposal is passed + propos = Proposal.get(Proposal.name == proposal) + if propos.approved_by_vote == 1: + pass + elif proposal_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): + propos = Proposal.get(Proposal.name == proposal) + meet = propos.meet_conditions_days + # abv = propos.approved_by_vote + abvd = propos.approved_by_vote_date + _approved_by_vote = 1 if int(meet) >= PROPOSAL_MEET_DAYS else 0 + _approved_by_vote_date = datetime.now() if abvd == None else abvd + # if meet >= 0 and abv != False and abvd != None: + nrow = (Proposal.update( + json_info = proposal_item + , vote_total = vote_total + , staked_total = staked_total + , vote_bp_total = BP_TOTAL_VOTES + , vote_yes = vote_yes + , vote_no = vote_no + , meet_conditions_days = int(meet) + 1 if int(meet) < PROPOSAL_MEET_DAYS + 1 else int(meet) + , approved_by_vote = _approved_by_vote + , approved_by_vote_date = _approved_by_vote_date + ).where(Proposal.name == proposal).execute()) + else: + nrow = (Proposal.update( + json_info = proposal_item + , vote_total = vote_total + , staked_total = staked_total + , vote_bp_total = BP_TOTAL_VOTES + , vote_yes = vote_yes + , vote_no = vote_no + , meet_conditions_days = 0 + , approved_by_vote = 0 + , approved_by_vote_date = None + , approved_by_BET = 0 + , reviewed_by_BET_date = None + , approved_by_BPs = 0 + , approved_by_BPs_date = None + , review = 0 + , review_date = None + , finish = 0 + , finish_date = None + ).where(Proposal.name == proposal).execute()) + else: + if proposal_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): + _approved_by_vote = 1 + _approved_by_vote_date = datetime.now() + else: + pass + new_proposal = Proposal(name = proposal + , json_info = proposal_item + , vote_total = vote_total + , staked_total = staked_total + , vote_bp_total = BP_TOTAL_VOTES + , vote_yes = vote_yes + , vote_no = vote_no + , meet_conditions_days = _meet_conditions_days + , approved_by_vote = _approved_by_vote + , approved_by_vote_date = _approved_by_vote_date + , approved_by_BET = _approved_by_BET + , reviewed_by_BET_date = _reviewed_by_BET_date + , approved_by_BPs = _approved_by_BPs + , approved_by_BPs_date = _approved_by_BPs_date + , review = 0 + , review_date = None + , finish = _finish + , finish_date = _finish_date) + new_proposal.save() + except Exception as err: + logger.error(err) + alarm(err) + logger.info("proposal name: " + proposal) + logger.info("vote total: " + str(vote_total)) + logger.info("staked total: " + str(staked_total)) + logger.info("bpvote total: " + str(BP_TOTAL_VOTES)) + logger.info("ratio:" + str(int(staked_total)/int(BP_TOTAL_VOTES))) + logger.info("vote yes: " + str(vote_yes)) + logger.info("vote no: " + str(vote_no)) + logger.info("___________________") + resp = flask.Response(proposals) + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + # except Exception as err: + # return err + +# init auditor data and daily caculate auditor condition meet +@app.route('/getAuditorJson') +def aujsoninfo(): + logger = reactive_log('auditorjson') + # url_index = test_net_is_working(BOS_URLS) + # logger.info('BOS Node ['+ str(url_index) + '] is working:' + BOS_URLS[url_index]) + # ce = Cleos(url=BOS_URLS[url_index]) + BP_TOTAL_VOTES = cfg.BP_TOTAL_VOTES + # try: + with open("vote_total_tally.json", 'r') as f: + NEW_BP_TOTAL_VOTES = json.loads(f.read())['bp_votes'] + BP_TOTAL_VOTES = int(NEW_BP_TOTAL_VOTES) if int(NEW_BP_TOTAL_VOTES) > 0 else BP_TOTAL_VOTES + print(BP_TOTAL_VOTES) + auditors = {} + with open("auditor_tally.json","r") as f: + auditors = json.loads(f.read()) + #iterater the current auditors + for auditor in auditors: + auditor_item = auditors[auditor] + vote_key = auditor_item['stats']['votes'] + stake_key = auditor_item['stats']['staked'] + staked_total = float(int(auditor_item['stats']['staked']['total'])) if 'total' in stake_key else 0 + vote_total = auditor_item['stats']['votes']['total'] if 'total' in vote_key else 0 + vote_yes = auditor_item['stats']['votes']['1'] if '1' in vote_key else 0 + vote_no = auditor_item['stats']['votes']['0'] if '0' in vote_key else 0 _meet_conditions_days = 0 _approved_by_vote = 0 _approved_by_vote_date = None - _approved_by_BET = 0 - _reviewed_by_BET_date = None - _approved_by_BPs = 0 - _approved_by_BPs_date = None - _review = 0 - _review_date = None - _finish = 0 - _finish_date = None - # check if the proposal exists + + # check if the auditor exists try: - propos = Proposal.select().where(Proposal.name == proposal).count() - logger.info("result"+str(propos)) - # the proposal exists - if propos > 0: - # check if the proposal is passed - if proposal_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): - propos = Proposal.get(Proposal.name == proposal) - meet = propos.meet_conditions_days - # abv = propos.approved_by_vote - abvd = propos.approved_by_vote_date - _approved_by_vote = 1 if int(meet) >= 20 else 0 + audits_count = AuditorTally.select().where(AuditorTally.name == auditor).count() + logger.info("audits_count:"+str(audits_count)) + # the auditor exists + if audits_count > 0: + audits = AuditorTally.get(AuditorTally.name == auditor) + if audits.approved_by_vote == 1: + pass + # check if the auditor is passed + if auditor_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): + audits = AuditorTally.get(AuditorTally.name == auditor) + meet = audits.meet_conditions_days + # abv = audits.approved_by_vote + abvd = audits.approved_by_vote_date + _approved_by_vote = 1 if int(meet) >= AUDITOR_MEET_DAYS else 0 _approved_by_vote_date = datetime.now() if abvd == None else abvd # if meet >= 0 and abv != False and abvd != None: - nrow = (Proposal.update( - json_info = proposal_item + nrow = (AuditorTally.update( + json_info = auditor_item , vote_total = vote_total , staked_total = staked_total , vote_bp_total = BP_TOTAL_VOTES , vote_yes = vote_yes , vote_no = vote_no - , meet_conditions_days = int(meet) + 1 - , approved_by_vote = _approved_by_vote - , approved_by_vote_date = _approved_by_vote_date - ).where(Proposal.name == proposal).execute()) + , meet_conditions_days = int(meet) + 1 if int(meet) < AUDITOR_MEET_DAYS + 1 else int(meet) , approved_by_vote = _approved_by_vote , approved_by_vote_date = _approved_by_vote_date + ).where(AuditorTally.name == auditor).execute()) else: - nrow = (Proposal.update( - json_info = proposal_item + nrow = (AuditorTally.update( + json_info = auditor_item , vote_total = vote_total , staked_total = staked_total , vote_bp_total = BP_TOTAL_VOTES @@ -138,23 +261,16 @@ def jsoninfo(): , meet_conditions_days = 0 , approved_by_vote = 0 , approved_by_vote_date = None - , approved_by_BET = 0 - , reviewed_by_BET_date = None - , approved_by_BPs = 0 - , approved_by_BPs_date = None - , review = 0 - , review_date = None - , finish = 0 - , finish_date = None - ).where(Proposal.name == proposal).execute()) + ).where(AuditorTally.name == auditor).execute()) else: - if proposal_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): + if auditor_base_condition_ckeck(BP_TOTAL_VOTES, staked_total, vote_yes, vote_no): _approved_by_vote = 1 _approved_by_vote_date = datetime.now() else: pass - new_proposal = Proposal(name = proposal - , json_info = proposal_item + new_auditor = AuditorTally( + name = auditor + , json_info = auditor_item , vote_total = vote_total , staked_total = staked_total , vote_bp_total = BP_TOTAL_VOTES @@ -163,41 +279,182 @@ def jsoninfo(): , meet_conditions_days = _meet_conditions_days , approved_by_vote = _approved_by_vote , approved_by_vote_date = _approved_by_vote_date - , approved_by_BET = _approved_by_BET - , reviewed_by_BET_date = _reviewed_by_BET_date - , approved_by_BPs = _approved_by_BPs - , approved_by_BPs_date = _approved_by_BPs_date - , review = 0 - , review_date = None - , finish = _finish - , finish_date = _finish_date) - new_proposal.save() + ) + new_auditor.save() except Exception as err: logger.error(err) - logger.info("proposal name: " + proposal) + alarm(err) + logger.info("auditor name: " + auditor) logger.info("vote total: " + str(vote_total)) logger.info("staked total: " + str(staked_total)) + logger.info("bpvote total: " + str(BP_TOTAL_VOTES)) + logger.info("ratio:" + str(int(staked_total)/int(BP_TOTAL_VOTES))) logger.info("vote yes: " + str(vote_yes)) logger.info("vote no: " + str(vote_no)) logger.info("___________________") - resp = flask.Response(proposals) + resp = flask.Response(auditors) + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + +@app.route('/getAllAuditors/') +def auditorsinfo(lang='en'): + if(checkSupportLang(lang) != True): + resp = flask.Response(json.dumps({'error':'language not support'}), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + if(lang == 'cn'): + lang='zh-CN' + if(lang == 'tw'): + lang='zh-TW' + logger = reactive_log('getAllAuditors') + with open("auditor_tally.json",'r') as f: + auditors = json.loads(f.read()) + for auditor in auditors: + try: + propos = AuditorTally.select().where(AuditorTally.name == auditor).count() + logger.info("result"+str(propos)) + # the auditor exists + if propos > 0: + propos = AuditorTally.get(AuditorTally.name == auditor) + auditors[auditor]['meet_conditions_days'] = propos.meet_conditions_days + auditors[auditor]['approved_by_vote'] = propos.approved_by_vote + auditors[auditor]['approved_by_vote_date'] = str(propos.approved_by_vote_date) + else: + auditors[auditor]['meet_conditions_days'] = 0 + auditors[auditor]['approved_by_vote'] = 0 + auditors[auditor]['approved_by_vote_date'] = "" + tpropos = AuditorTanslate.select().where((AuditorTanslate.name == auditor) & (AuditorTanslate.lang == lang)).count() + # tanslate part + if tpropos > 0: + tpropos = AuditorTanslate.select().where((AuditorTanslate.name == auditor) + & (AuditorTanslate.lang == lang)).get() + auditors[auditor]['bio']['bio'] = tpropos.bio + else: + tbio = translate_text(auditors[auditor]['bio']['bio'],lang) + print(tbio) + new_auditor = AuditorTanslate( + name = auditor + , lang = lang + , bio = tbio + ) + new_auditor.save() + auditors[auditor]['bio']['bio'] = tbio + except Exception as err: + logger.error(err) + alarm(err) + resp = flask.Response(json.dumps(auditors), mimetype='application/json') resp.headers['Access-Control-Allow-Origin'] = '*' return resp - # except Exception as err: - # return err +@app.route('/getAllAuditors') +def auditorsinfoorigin(lang='en'): + logger = reactive_log('getAllAuditors') + # try: + with open("auditor_tally.json",'r') as f: + auditors = json.loads(f.read()) + for auditor in auditors: + try: + propos = AuditorTally.select().where(AuditorTally.name == auditor).count() + logger.info("result"+str(propos)) + # the auditor exists + if propos > 0: + propos = AuditorTally.get(AuditorTally.name == auditor) + auditors[auditor]['meet_conditions_days'] = propos.meet_conditions_days + auditors[auditor]['approved_by_vote'] = propos.approved_by_vote + auditors[auditor]['approved_by_vote_date'] = str(propos.approved_by_vote_date) + else: + auditors[auditor]['meet_conditions_days'] = 0 + auditors[auditor]['approved_by_vote'] = 0 + auditors[auditor]['approved_by_vote_date'] = "" + except Exception as err: + logger.error(err) + alarm(err) + resp = flask.Response(json.dumps(auditors), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + +@app.route('/getAllProposals/') +def proposals(lang='en'): + if(checkSupportLang(lang) != True): + resp = flask.Response(json.dumps({'error':'language not support'}), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + if(lang == 'cn'): + lang='zh-CN' + if(lang == 'tw'): + lang='zh-TW' + logger = reactive_log('getAllProposals') + with open("proposal_tally.json") as f: + proposals = json.loads(f.read()) + for proposal in proposals: + try: + propos = Proposal.select().where(Proposal.name == proposal).count() + logger.info("result"+str(propos)) + # the proposal exists + if propos > 0: + propos = Proposal.get(Proposal.name == proposal) + proposals[proposal]['meet_conditions_days'] = propos.meet_conditions_days + proposals[proposal]['approved_by_vote'] = propos.approved_by_vote + proposals[proposal]['approved_by_vote_date'] = str(propos.approved_by_vote_date) + proposals[proposal]['approved_by_BET'] = propos.approved_by_BET + proposals[proposal]['reviewed_by_BET_date'] = str(propos.reviewed_by_BET_date) + proposals[proposal]['approved_by_BPs'] = propos.approved_by_BPs + proposals[proposal]['approved_by_BPs_date'] = str(propos.approved_by_BPs_date) + proposals[proposal]['review'] = propos.review + proposals[proposal]['review_date'] = str(propos.review_date) + proposals[proposal]['finish'] = propos.finish + proposals[proposal]['finish_date'] = str(propos.finish_date) + else: + proposals[proposal]['meet_conditions_days'] = 0 + proposals[proposal]['approved_by_vote'] = 0 + proposals[proposal]['approved_by_vote_date'] = "" + proposals[proposal]['approved_by_BET'] = 0 + proposals[proposal]['reviewed_by_BET_date'] = "" + proposals[proposal]['approved_by_BPs'] = 0 + proposals[proposal]['approved_by_BPs_date'] = "" + proposals[proposal]['review'] = 0 + proposals[proposal]['review_date'] = "" + proposals[proposal]['finish'] = "" + proposals[proposal]['finish_date'] = 0 + tpropos = ProposalTanslate.select().where((ProposalTanslate.name == proposal) & (ProposalTanslate.lang == lang)).count() + # tanslate part + if tpropos > 0: + tpropos = ProposalTanslate.select().where((ProposalTanslate.name == proposal) & (ProposalTanslate.lang == lang)).get() + proposals[proposal]['proposal']['title'] = tpropos.title + proposal_json = json.loads( + proposals[proposal]['proposal']['proposal_json']) + proposal_json['content'] = tpropos.content + proposals[proposal]['proposal']['proposal_json'] = proposal_json + else: + ttitle = translate_text(proposals[proposal]['proposal']['title'], lang, True) + proposal_json = json.loads( + proposals[proposal]['proposal']['proposal_json']) + tcontent = translate_text(proposal_json['content'], lang) + print(ttitle) + new_proposal = ProposalTanslate( + name = proposal + , lang = lang + , title = ttitle + , content = tcontent + ) + new_proposal.save() + proposals[proposal]['proposal']['title'] = ttitle + proposal_json['content'] = tcontent + proposals[proposal]['proposal']['proposal_json'] = proposal_json + except Exception as err: + logger.error(err) + alarm(err) + resp = flask.Response(json.dumps(proposals), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp @app.route('/getAllProposals') -def proposals(): +def proposalsorigin(): logger = reactive_log('getAllProposals') - try: - rawtext=urlopen(TALLY_API,timeout=15).read() - proposals = json.loads(rawtext.decode('utf8')) - except Exception as err: - logger.error(err) + with open("proposal_tally.json") as f: + proposals = json.loads(f.read()) for proposal in proposals: - # print("@@@@"+str(proposals[proposal])) try: propos = Proposal.select().where(Proposal.name == proposal).count() logger.info("result"+str(propos)) @@ -227,28 +484,112 @@ def proposals(): proposals[proposal]['review_date'] = "" proposals[proposal]['finish'] = "" proposals[proposal]['finish_date'] = 0 + except Exception as err: logger.error(err) + alarm(err) resp = flask.Response(json.dumps(proposals), mimetype='application/json') resp.headers['Access-Control-Allow-Origin'] = '*' return resp + +@app.route('/getProposal//') +def proposal(proposal_name, lang='en'): + if(checkSupportLang(lang) != True): + resp = flask.Response(json.dumps({'error':'language not support'}), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp + if(lang == 'cn'): + lang='zh-CN' + if(lang == 'tw'): + lang='zh-TW' + logger = reactive_log('getProposal') + with open("proposal_tally.json","r") as f: + proposals = json.loads(f.read()) + + try: + propos = Proposal.select().where(Proposal.name == proposal_name).count() + logger.info("result"+str(propos)) + # the proposal exists + if propos > 0: + + propos = Proposal.get(Proposal.name == proposal_name) + proposals[proposal_name]['meet_conditions_days'] = propos.meet_conditions_days + proposals[proposal_name]['approved_by_vote'] = propos.approved_by_vote + proposals[proposal_name]['approved_by_vote_date'] = str(propos.approved_by_vote_date) + proposals[proposal_name]['approved_by_BET'] = propos.approved_by_BET + proposals[proposal_name]['reviewed_by_BET_date'] = str(propos.reviewed_by_BET_date) + proposals[proposal_name]['approved_by_BPs'] = propos.approved_by_BPs + proposals[proposal_name]['approved_by_BPs_date'] = str(propos.approved_by_BPs_date) + proposals[proposal_name]['review'] = propos.review + proposals[proposal_name]['review_date'] = str(propos.review_date) + proposals[proposal_name]['finish'] = propos.finish + proposals[proposal_name]['finish_date'] = str(propos.finish_date) + else: + proposals[proposal_name]['meet_conditions_days'] = 0 + proposals[proposal_name]['approved_by_vote'] = 0 + proposals[proposal_name]['approved_by_vote_date'] = "" + proposals[proposal_name]['approved_by_BET'] = 0 + proposals[proposal_name]['reviewed_by_BET_date'] = "" + proposals[proposal_name]['approved_by_BPs'] = 0 + proposals[proposal_name]['approved_by_BPs_date'] = "" + proposals[proposal_name]['review'] = 0 + proposals[proposal_name]['review_date'] = "" + proposals[proposal_name]['finish'] = "" + proposals[proposal_name]['finish_date'] = 0 + tpropos = ProposalTanslate.select().where((ProposalTanslate.name == proposal_name) & (ProposalTanslate.lang == lang)).count() + tpropos = int(tpropos) + print(tpropos) + print(proposal_name) + print(lang) + # tanslate part + if tpropos > 0: + rpropos = ProposalTanslate.select().where( + (ProposalTanslate.name == proposal_name) & (ProposalTanslate.lang == lang)).get() + + proposals[proposal_name]['proposal']['title'] = rpropos.title + proposal_json = json.loads( + proposals[proposal_name]['proposal']['proposal_json']) + proposal_json['content'] = rpropos.content + proposals[proposal_name]['proposal']['proposal_json'] = proposal_json + else: + print('starting') + ttitle = translate_text(proposals[proposal_name]['proposal']['title'], lang, True) + print(ttitle) + + proposal_json = json.loads( + proposals[proposal_name]['proposal']['proposal_json']) + tcontent = translate_text(proposal_json['content'], lang) + # print(tcontent) + new_proposal = ProposalTanslate( + name = proposal_name + , lang = lang + , title = ttitle + , content = tcontent + ) + new_proposal.save() + proposals[proposal_name]['proposal']['title'] = ttitle + proposal_json['content'] = tcontent + proposals[proposal_name]['proposal']['proposal_json'] = proposal_json + + except Exception as err: + logger.error(err) + alarm(err) + resp = flask.Response(json.dumps(proposals[proposal_name]), mimetype='application/json') + resp.headers['Access-Control-Allow-Origin'] = '*' + return resp @app.route('/getProposal/') -def proposal(proposal_name): +def proposalorigin(proposal_name): logger = reactive_log('getProposal') - try: - rawtext=urlopen(TALLY_API,timeout=15).read() - proposals = json.loads(rawtext.decode('utf8')) - except Exception as err: - logger.error(err) + with open("proposal_tally.json","r") as f: + proposals = json.loads(f.read()) try: propos = Proposal.select().where(Proposal.name == proposal_name).count() logger.info("result"+str(propos)) # the proposal exists if propos > 0: - propos = Proposal.get(Proposal.name == proposal_name) proposals[proposal_name]['meet_conditions_days'] = propos.meet_conditions_days proposals[proposal_name]['approved_by_vote'] = propos.approved_by_vote @@ -275,6 +616,7 @@ def proposal(proposal_name): proposals[proposal_name]['finish_date'] = 0 except Exception as err: logger.error(err) + alarm(err) resp = flask.Response(json.dumps(proposals[proposal_name]), mimetype='application/json') resp.headers['Access-Control-Allow-Origin'] = '*' return resp @@ -308,13 +650,14 @@ def review(proposal_name): return resp except Exception as err: logger.error(err) + alarm(err) resp = flask.Response(json.dumps({"result":"ERROR"}), mimetype='application/json') resp.headers['Access-Control-Allow-Origin'] = '*' return resp @app.route('/finish/') def finish(proposal_name): - logger = reactive_log('review') + logger = reactive_log('finish') try: propos = Proposal.select().where(Proposal.name == proposal_name).count() logger.info("result"+str(propos)) @@ -339,6 +682,7 @@ def finish(proposal_name): return resp except Exception as err: logger.error(err) + alarm(err) resp = flask.Response(json.dumps({"result":"ERROR"}), mimetype='application/json') resp.headers['Access-Control-Allow-Origin'] = '*' return resp diff --git a/api/init_db.py b/api/init_db.py index db792da..5571a90 100755 --- a/api/init_db.py +++ b/api/init_db.py @@ -1,17 +1,19 @@ from peewee import * -from datetime import date,datetime +from datetime import date, datetime import os DATABASE = "tally.db" -# os.environ.get('DB_PWD') -# db = SqliteDatabase(DATABASE) -db = PostgresqlDatabase('d3cjkjmhbkt11i', user='dtzkpiirdsycdh', password=os.environ.get('DB_PWD'), host='ec2-54-247-178-166.eu-west-1.compute.amazonaws.com', port=5432) +os.environ.get('DB_PWD') +db = SqliteDatabase(DATABASE) +# db = PostgresqlDatabase('d3cjkjmhbkt11i', user='dtzkpiirdsycdh', password=os.environ.get('DB_PWD'), host='ec2-54-247-178-166.eu-west-1.compute.amazonaws.com', port=5432) + class BaseModel(Model): class Meta: database = db + class Proposal(BaseModel): name = CharField(unique=True, index=True) json_info = TextField() @@ -22,17 +24,77 @@ class Proposal(BaseModel): vote_bp_total = BigIntegerField() meet_conditions_days = IntegerField() approved_by_vote = BooleanField() - approved_by_vote_date = DateTimeField(null = True) + approved_by_vote_date = DateTimeField(null=True) approved_by_BET = BooleanField() - reviewed_by_BET_date = DateTimeField(null = True) + reviewed_by_BET_date = DateTimeField(null=True) approved_by_BPs = BooleanField() - approved_by_BPs_date = DateTimeField(null = True) + approved_by_BPs_date = DateTimeField(null=True) review = BooleanField() - review_date = DateTimeField(null = True) + review_date = DateTimeField(null=True) finish = BooleanField() - finish_date = DateTimeField(null = True) + finish_date = DateTimeField(null=True) timestamp = DateTimeField(default=datetime.now) + +class AuditorTally(BaseModel): + name = CharField(unique=True, index=True) + json_info = TextField() + vote_total = BigIntegerField() + vote_yes = SmallIntegerField() + vote_no = SmallIntegerField() + staked_total = BigIntegerField() + vote_bp_total = BigIntegerField() + meet_conditions_days = IntegerField() + approved_by_vote = BooleanField() + approved_by_vote_date = DateTimeField(null=True) + timestamp = DateTimeField(default=datetime.now) + + +class ProposalTanslate(BaseModel): + name = CharField(index=True) + lang = CharField(index=True) + title = TextField() + content = TextField() + timestamp = DateTimeField(default=datetime.now) + + +class AuditorTanslate(BaseModel): + name = CharField(index=True) + lang = CharField(index=True) + bio = TextField() + timestamp = DateTimeField(default=datetime.now) + + +class Config(BaseModel): + TALLY_API = TextField() + VOTE_TOTAL_API = TextField() + AUDITOR_TOTAL_API = TextField() + BP_TOTAL_VOTES = BigIntegerField() + PROPOSAL_VOTE_RATIO = FloatField() + AUDITOR_VOTE_RATIO = FloatField() + PROPOSAL_YES_NO_RATIO = FloatField() + AUDITOR_YES_NO_RATIO = FloatField() + PROPOSAL_MEET_DAYS = IntegerField() + AUDITOR_MEET_DAYS = IntegerField() + + db.connect() -db.create_tables([Proposal]) +db.create_tables( + [Proposal, AuditorTally, AuditorTanslate, ProposalTanslate, Config]) db.close() + +dbconfig = Config.create( + TALLY_API='https://s3.amazonaws.com/bos.referendum/referendum/tallies/latest.json', + VOTE_TOTAL_API='https://s3.amazonaws.com/bos.referendum/referendum/summaries/latest.json', + AUDITOR_TOTAL_API='https://s3.amazonaws.com/bos.referendum/referendum/auditor.tallies/latest.json', + BP_TOTAL_VOTES=311193750652, + PROPOSAL_VOTE_RATIO=0.4, + AUDITOR_VOTE_RATIO=0.03, + PROPOSAL_YES_NO_RATIO=1.5, + AUDITOR_YES_NO_RATIO=1.5, + PROPOSAL_MEET_DAYS=20, + AUDITOR_MEET_DAYS=20 +) + +dbconfig.save() +cfg = Config.select().limit(1).get() diff --git a/api/minutely_get_tally.sh b/api/minutely_get_tally.sh new file mode 100755 index 0000000..bf24cf1 --- /dev/null +++ b/api/minutely_get_tally.sh @@ -0,0 +1,14 @@ +# 定时下载任务 + + +tmp=`wget https://s3.amazonaws.com/bos.referendum/referendum/forum.tallies/latest.json` +find latest.json -exec mv {} /root/referendum/api/proposal_tally.json \; + + + +tmp=`wget https://s3.amazonaws.com/api.boswps.com/eosio/stats/latest.json` +find latest.json -exec mv {} /root/referendum/api/vote_total_tally.json \; + + +tmp=`wget https://api.boswps.com/referendum/auditor.tallies/latest.json` +find latest.json -exec mv {} /root/referendum/api/auditor_tally.json \; diff --git a/api/proposal_tally.json b/api/proposal_tally.json new file mode 100644 index 0000000..14b4f1e --- /dev/null +++ b/api/proposal_tally.json @@ -0,0 +1,1276 @@ +{ + "beosinboside": { + "id": "beosinboside_20190701", + "proposal": { + "proposal_name": "beosinboside", + "proposer": "beosinbosbos", + "title": "在线BOS-IDE免费版本", + "proposal_json": "{\"content\":\"# 在线BOS-IDE免费版本 提案\\n\\n目录\\n\\n提案背景\\n\\n提案介绍\\n\\n技术优势\\n\\n提案执行\\n\\n提案目标\\n\\n提案预算\\n\\n## 1、提案背景\\n\\n随着近期BOS生态及社区热度的上升，越来越多有着区块链技术背景的开发者开始关注BOS生态，其中每一个区块链开发程序员都需要一个界面友好、操作方便的IDE，BOS开发也是一样。但是，目前市场上传统开发工具不能同时具备 BOS智能合约编译、部署、测试功能，且占用内存较大，给开发者造成了一定困扰。\\n\\n为了让BOS生态更安全、更丰富，从技术全面和技术保障上最大程度的帮助BOS开发者组织资源，我们推出了BOS智能合约集成开发环境“Beosin BOS-IDE”，该开发工具同时支持BOS智能合约在线编辑、编译、一键部署和调试等多种功能，供所有开发者免费使用。\\n\\n相比于市面上其他IDE产品，“Beosin BOS-IDE”更加人性化、集成度更高、学习门槛更低，“Beosin BOS-IDE”的推出，目标是让BOS开发者能节省时间和精力、建立统一标准、管理开发工作，可谓是事半功倍。\\n\\n## 2、提案介绍\\n\\n“Beosin BOS-IDE”，首款集在线编辑、编译、部署、运行调试于一体的智能合约开发工具，支持BOS区块链平台（图1）。 ![ ](https://www.lianantech.com/static/img/img1.27a2dec.png)\\n\\n图1：Beosin BOS-IDE界面\\n\\n“Beosin BOS-IDE”的使用在web 端，无需在本地安装工具及插件，搭建开发环境。其具备多个编译器版本可供选择，运行速度快，工具界面清晰明了，还具备代码联想、错误行标记、错误提示等功能，从技术全面和技术保障上最大程度地帮助BOS开发者组织资源，使IDE更加人性化、集成度更高、学习门槛更低，让开发者能节省时间和精力，高效进行开发工作，同时也能助力BOS生态安全。\\n\\n## 3、技术优势\\n\\n“Beosin BOS-IDE” 最大的优势在于以下8点：\\n\\n1、首款具备在线编辑、编译、运行调试、部署于一体的BOS开发工具\\n\\n2、无需搭建开发环境，无需安装，在线操作\\n\\n3、一切交互均以图形化方式\\n\\n4、支持多个编译器版本\\n\\n5、支持多种BOS节点部署运行\\n\\n6、运行速度快、提示信息明确，极大提升了用户体验\\n\\n7、开发人员可以高效完成BOS智能合约开发等工作\\n\\n8、协助开发者在开发过程中提高漏洞风险意识，避免安全隐患\\n\\n## 4、提案执行\\n\\n1、2019年4月初，发布Besosin BOS-IDE第一个版本，支持在线编辑、编译、部署、运行测试等功能\\n\\n2、2019年5月，开放eosio.token账户、新增账户permission设置等功能\\n\\n3、2019年6月，新增账户查表、transaction查询、action traces查询等功能\\n\\n4、2019年7月-9月，优化完善工具，新增自动化测试功能、静态检测等功能，为BOS开发者提供更大的便利\\n\\n5、2019年9月-12月，提升服务器的并发量，优化前端UI，提升用户体验\\n\\n6、2019年持续更新完善BOS-IDE，持续更新对BOS新版本的支持，根据BOS平台新特性和开发者需求不断完善BOS-IDE。\\n\\n## 5、提案目标\\n\\n“Beosin BOS-IDE”是成都链安团队了解到市场上传统开发工具不能同时具备BOS 智能合约编译、部署、测试功能，且占用内存较大，给开发者造成了一定困扰，出于给开发者创造一个更加优质的开发环境的初衷而研发的，同时旨在推动区块链行业对于安全问题防御能力的提升，更好地维护区块链产业安全。\\n\\n## 6、提案预算\\n\\n一共申请95万个bos，前期需要30万bos，后期65万个bos 1.开发人工费用：50万bos 2.维护费用：15万bos 3.服务器租用费用：10万bos 4.安全运维人员监控费用：20万bos\",\"type\":\"referendum-v1\",\"incentives\":\"950000.0000 BOS\",\"receiptor\":\"beosinbosbos\"}", + "created_at": "2019-07-01T09:07:56" + }, + "stats": { + "votes": { + "1": 1, + "total": 1, + "proxies": 0, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 28301, + "total": 28301 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 28301, + "total": 28301 + }, + "block_num": 43385214 + } + }, + "betbospropos": { + "id": "betbospropos_20190821", + "proposal": { + "proposal_name": "betbospropos", + "proposer": "sheldonhuang", + "title": "BET选举设计和DPOS波达计数法实现 / Design of BET Election and Implementation of DPOS Borda Count ", + "proposal_json": "{\"content\":\"English Version: https://docs.google.com/document/d/1V96w3L5BGPtrvLpoUYsJUUNsC6yH0RFB7LSByghYx50/\\n# 1. 提案背景\\n\\nBOSCore是一个由社区发起的技术驱动的EOSIO侧链，成功推出了BOS提案系统（WPS）。[BOS执行团队](https://boscore.io/en/team.html)是 [WPS流程](https://boswps.io/#/help/process)的一个关键组成部分。 根据最初的设计，我们的目标是让BOS社区治理特别是WPS更加去中心化。 该提案旨在提供一种设计模型：DPOS波达计数法投票方案，该投票方案让投票更加**基于共识**而**不是大户主导**，让整个BOS生态和WPS系统更加开放和平衡。\\n\\n\\n\\n# 2. BET介绍\\n\\nBOSCore Executive Team 简称 BET，是一群由EOSIO社区成员组成针对BOSCore项目进行社区化运作的组织。该组织最多包含25名成员，通过BOS持币者投票表决的方式选举出主席和副主席两个职位。\\n\\n决策规则如下：\\n\\n- **多数决议**：重要决定需要得到N / 2 + 1 BET成员的批准和支持。【majority decision】\\n- **少数决议**：日常决定需要得到N / 3 + 1 BET成员的批准和支持。【minority decision】\\n- 只有BET成员可参与BET会议：BET成员不能委派成员资格。\\n\\n为了敦促BET成员为BOSCore项目建设作出贡献，主席和BET成员必须在当选后签署《BET成员准则》 *BET Members Code of Ethic*。\\n\\n\\n\\n## 2.1 BET选举\\n\\nBET候选人在必须在竞选前将10,000枚BOS质押到到bet.bos合约中。所质押的BOS必须在竞选期间和成功当选的整个任期内保持质押状态。如果该BET成员从BET离职，BET成员该成员质押的BOS将在三个月退还给该BET成员。\\n\\n首届BET成员选举暂定于2020年1月底举行。\\n\\n要正式当选为BET成员，必须满足以下两个门槛：\\n\\n- 选举开始时，投票数至少是当前现有选票的15％;和，\\n- 满足投票的比例连续20天。\\n\\n选举将在[boswps.io](http://boswps.io)网站上进行。\\n\\nBET成员的任期为6个月。在任期结束时，BET成员可以通过**多数决议**再次连任6个月。 BET成员职位没有任期限制，只要他们继续通过**多数决议**即可再次当选。\\n\\n可以在**多数决议**的任何时候启动对BET成员的移除。但是，连续错过两次或更多连续预定会议的BET成员可能会被**少数决议**决定删除。\\n\\n注意：如果BET成员决定在结束任期之前退出和/或根据**多数决议**将其移除，则10,000 BOS将在退回之前的预期期限结束日期之后保留3个月。\\n\\n## 2.2 BET成员责任：\\n\\n- 持续不断地促进BOS及其生态系统的发展;\\n- 配合主席的工作;\\n- 持续监督BET主席的工作\\n- 通过**多数决议**选择和/或弹劾主席。\\n\\n## 2.3 BOS BET主席\\n\\nBOS BET将对主席和副主席进行内部选举。主席从活跃的BET成员中选出。每个主席职位的任期为1年。主席必须由**多数决议**选出。在选举过程中，主席不得为自己投票。在第一个任期结束时，主席可以通过**多数决议**再次连任1年。主席最多可连续两个任期。如果主席未能当选为BET，则该职位将由BETs重新选举。\\n\\n#### 主席责任：\\n\\n- 每3个月为BET成员分配激励津贴，包括分配给主席自己;\\n- 制定BOS生态系统整体改进战略计划\\n- 为开发者和基础设施指定的0.8％通货膨胀的激励策略并进行分配\\n\\n## 2.4 评审员激励：\\n\\nBOS整体通胀的0.15％将作为BET的运营资金和工资。另外0.05％的通货膨胀将留给BOS WPS系统的评审员。\\n\\n## 2.5 BET规则变更：\\n\\nBOS持有者社区可以通过BOS WPS提交提案来更改BOS BET 的规则，此提案必须符合以下阈值：\\n\\n- 投票数至少占当前BP选票的60％\\n- 上一个阈值连续20天满足。\\n\\n## 2.6 BET成员准则\\n\\n我已同意担任BOS执行团队成员，并且我同意在作为成员的整个任期内认真遵守以下BET成员准则：\\n\\n- 诚实和诚信 - 我将诚实地行事。不会做任何辜负和有害于我所服务的社区的信任的事情。\\n\\n- 关心，勤奋和专业 - 我将用勤奋，能力，全心全意地参加和所有的我需要参加的BET相关会议。我将以负责任的态度，尽职尽责地促进BOS生态系统的发展。\\n\\n- 利益冲突 - 我不会做任何与BOS BET团队有关的实际或潜在利益冲突以及对BOS有害的事。如果我发现任何BET成员有违反利益冲突原则的行为，我会立即向主席报告。我不会为我自己或任何利益相关方而损害BOS生态系统。作为BET成员，我不会寻求任何特殊利益或特权。我的行为只会符合BET的最佳利益。\\n\\n# 3. BET DPOS波达计数法投票方案\\n## 3.1 序言\\n\\n自从 BM 将 DPOS 引入 EOS 以来，如何更好的选出超级节点就成了社区争论的焦点，一票多投，一票多投可弃权制，一票一投等等，BOS 沿用了 EOS 的投票机制即一票多投（一票25投，可弃权）机制，然而由于帕累托法则的存在，导致票权会集中在少数人手中，再加上一票多投的机制允许持票人间可以进行换票，从而最终导致超级节点被控制在少数持票人手中，进而加剧筹码的不平衡，进一步导致贫富差距增大。\\n\\n为此在投票方案设计中我们尝试着引入改进的“波达计数法”[^1]投票机制来缓解这一问题。“波达计数法”曾是罗马议会采用的投票制度，BET 将采用基于 DPOS 改进的“波达计数法”来进行选举，并以期找到一个更为合理的投票方案，从而在保证 DPOS 系统安全和公平上能做出积极的改进。\\n\\n## 3.2 关于股权证明机制和投票选举\\n\\n关于股权证明机制文章有很多这里不再进行原理性的重复论述。本文仅就筹码集中与安全性方面进行讨论。为便于理解，我们将对上述进行简化：\\n\\n1. 假设所有投票所用票权皆来自投票者本人\\n2. 将简化原模型为概率发现模型\\n\\n接下来我们假设：\\n\\n- 某个持有人持股占比为 Q\\n- 作弊隐秘度函数 H\\n- 作弊被发现后损失函数 F(Q）\\n- 维护系统稳定情形下一般收益函数为 X(Q）\\n- 作弊收益 W\\n\\n*注意：这里假设的函数只用来做定性分析*\\n\\n于是我们可以简单的得到该持股人的策略关系即：\\n\\n```\\n根据 W+(H-1)*F(Q) 与 X(Q) 的大小关系进而决定相应的策略\\n```\\n\\n因为 F 是 Q 的正相关函数，X 也是 Q 的正相关函数，而 W 是带有投机性的随机参数，因此可以断定随着 Q 的增大其作弊收益会显著降低。在理性自然人假设下其选择维持公正是优势策略，因此从这个角度来看 POS 机制是稳定的模型。\\n事实上更进一步的分析时当我们加入道德参数，并将可监督性量化可以的得到股权结构与股东收益之间的如下关系和结论：\\n\\nA) 股权绝对集中结构\\n\\n```\\n股权绝对集中于经营者，则监督困难，经营者道德值减小乃至变为负值。\\n经营者责任心(→min)=经营者道德(→-)×{1+经营者资产所有权(max)}\\n股东收益(→min)=经营者责任心(→min）×经营者能力×经营条件\\n```\\n\\nB) 股权相对集中结构\\n\\n```\\n 股权相对集中，可以激励经营者，稳定骨干队伍，产生制衡监督。\\n 经营者责任心(→max)=经营者道德(→max)×{1+经营者资产所有权(max)}\\n 股东收益(→max)=经营者责任心(→max）×经营者能力×经营条件\\n```\\n\\nC) 股权分散结构\\n\\n```\\n股权过于分散，监督动力不足，经营者道德值也会减小乃至变为负值。\\n经营者责任心(→min)=经营者道德(→-)×{1+经营者资产所有权(min)}\\n股东收益(→min)=经营者责任心(→min）×经营者能力×经营条件\\n```\\n\\n所以，股权相对集中是优先选择的股权结构（详细的知识请参见股权结构相关书籍和论文）。\\n\\n因此我们需要在系统主体稳定的前提下尽量避免大户集权，那么有没有一种选票方案是理想的解决之法呢？\\n\\n## 3.3 投票与选举\\n\\n在详细讨论这个问题之前我们先来尝试着定义一下问题：\\n\\n```\\n假设有 N 个人参加选举，共有 K 个人进行投票，且每个投票者心中对于候选人的满意程度存在着一个排列， \\n目的是制定一个选举方案，最终可以得到多数“公正”的投票结果。\\n```\\n\\n那么什么是公正的呢？这里我们采用 Arrow 的五条规则[^2]：\\n\\n1. 每一个选民的影响力都一样，更进一步说，就是非独裁的\\n2. 选民除了不能不理性之外，没有其他任何关于其心目中排序的限制\\n3. 如果所有选民都认为 A>B，则选举结果也要显示 A>B\\n4. 选举结果关于 A 和 B 的排序，应该只由卷宗内 A 和 B 的相对顺序决定，与任何第三者无关\\n5. 如果所有选民都是理性地将选择对象排序，而且诚实投票，则选举的结果也要显示理性的排序\\n\\n但不幸的是有多种证明方法[^3][^4][^5]可以证明这样的“公正”是不存在的，这也是 Arrow 不可能定理的内容。因为我们的方案会在“波达计数法”的方案基础上进行修改，这里我们对其情形下的定理给出证明：\\n\\n设给定的 k 个整数 m1、m2、...mk，令 σ(1,2,...,n) 为 (1,2,...,n) 的置换群，定义如下映射：\\n\\n[![math01](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math01.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math01.png)\\n\\n对于任意一组数 t1>t2>...>tn，用上述 k 个置换做一个 n×k 矩阵：\\n\\n[![math02](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math02.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math02.png)\\n\\n依次定义n个数：\\n\\n[![math03](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math03.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math03.png)\\n\\n于是有：\\n\\n[![math04](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math04.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math04.png)\\n\\n我们知道对于上述等式可以找到n组数：\\n\\n[![math05](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math05.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math05.png)\\n\\n使得对应的：\\n\\n[![math06](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math06.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math06.png)\\n\\n满足：\\n\\n[![math07](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math07.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math07.png)\\n\\n从上面的推导可以看出存在多个解，也就是说“波达计数法”同样是不稳定的。 那么问题出在哪里呢？事实上是因为我们的假设条件制约了这样的公正性。\\n\\n学者 Saari[^6] 在他的论文中对上述问题进行了详细的论述。Saari 的论点之一就是 Arrow 的第4、5条的条件会互相「抵销」，因此其对上述第四条规则有进行了修正，如下：\\n\\n```\\n4'.选举结果关于 A 和 B 的排序，应该只由卷宗内 A 和 B 的相对顺序和距离决定，与任何第三者无关。\\n```\\n\\n那么在这样的假设下 Saari 证明了：\\n\\n```\\n在多于两个候选人前提下“波达计数法”选举程序是『公正』的 \\n```\\n\\n具体的技术细节请参考 Saari 的相关论文。也就是说从这个意义上来说“波达计数法”选举程序是更优的。因此我们尝试着在该结论下结合 DPOS 方案进行 BET 投票的适配。\\n\\n## 3.3 BET 投票方案\\n\\n接下来我们先给出投票方案的整体描述：\\n\\n设参加选举人数为N，K个人进行投票。我们的投票规则如下：\\n\\n1. 对于任意的投票人要求其给出一个序列 Ln，该序列的顺序即为其心目中候选人适合与否的排列顺序\\n\\n2. 投票人投票权重为其所持有并抵押的 Token 数量记为 Pi\\n\\n3. 给定一个函数 F(i)，该函数返回对于序列不同序号的打分\\n\\n4. 对于任意的候选人其记分规则如下：\\n\\n Vk = ∑ F(i,j)*Pi\\n\\n5. 排序所有参加选举候选人，得出最终当选序列。\\n\\nBET 将采用如下 F 函数：\\n\\n```\\nF(i) = (N+1-i)/N\\n```\\n\\n证明：\\n\\n> 假设任何投票人其手中所持 Token 数⌊Pi⌋即是票数，且每次只能投1票， \\n> 如此可将**每个投票人**看作是一个具有相同投票意愿投票者的集合。 \\n> 在此假设下，进一步来看这就变成了 ∑⌊Pi⌋ 人进行“波达计数法”投票的模型， \\n> 因此其具有与“波达计数法”方案相同的理论特性。\\n\\n进一步来看对于任意的持票人 Pi 由于他需要对所有的参选人都进行投票（排序），也就是说其对于任意一个参选人都做了贡献，只不过贡献的程度是按照函数 F 来进行的，也就是说设 Pi>Pj 且对于任意的 k>l 有 F(k) (∑F(i) * Pi)/(∑F(i) * Pj)\\n```\\n\\n其中 i，j 分别排在在对方的序列中劣势位置，因此对比一票多投的方案明显的削弱了其票权的作用。\\n\\n下面是不同 F 函数下与一票多投控制力进行的对比。\\n\\n> 线下面积为一票多投制投票者的投票最大值\\n\\n[![math08](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math08.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math08.png)\\n\\n> 线下面积为 F 为“波达计数法”时的投票最大值\\n\\n[![math09](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math09.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math09.png)\\n\\n> 线下面积为 F 为 X^(-σ) 方案时的投票最大值\\n\\n[![math10](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math10.png)](https://raw.githubusercontent.com/boscore/Documentation/master/imgs/dops_borad_count_math10.png)\\n\\n虽然并不严谨但可以直观的感受到它们之间的不同之处。接下来我们通过几个简单的例子来说明该方案的特性与优势。\\n\\n#### 案例一\\n\\n假设存在三个投票人 A，B，C，为了讨论方便我们假设候选人也是同样的三人，并假设其优先投票给自己，我们的投票准则是在三人中选择两人胜出。\\n\\n我们假设 A，B，C 分别持有 Token 数量为 at，bt，ct，假设在 A 与 B 进行串谋，如果采用 EOS 现行的投票方案，只要 `at+bt>ct` 则 C 将丧失了最终的权利，但在 BET 的方案下需要 `at+2bt>2ct`（这里假设 a>b ），才能得到相应的结果。在各个候选人相差不悬殊的情形下，可以实现 A，C 当选。\\n\\n#### 案例二\\n\\n假设有一个拥有2000万 Token 的大户 A，另外的一些候选人的支持者只在100万到600万之间，如果采用 EOS 的策略，那么在其他候选人无法达成一致的前提下，A几乎可以控制整个当选人顺序。由于 A 的强大控制力导致许多候选人会选择和 A 进行交易，最终导致 A 的控制力进一步加强。\\n\\n但对于 BET 方案来说，情况将变得不一样了，例如我们采用`(n+1-i)/n`作为 F 函数，n 这里假设为25，那么对大户 A 来说其对于某第 i 个支持账户所能提供的贡献值为`(n+1-i)/n*2*10^7` ，例如当 i 为20时其贡献值为480万；也就是说当有一个投票者手中持有的 Token 超过该值时，那么选择和这个 Token 持有者合作是比与 A 合作更优的策略。\\n\\n因此这能在一定程度上减弱 A 的控制力同时又能保证尽可能多的利益相关者的利益，同时由于该方案是**必需投满**票方案，在理性人假设下投票者为了利益最大化除了投给自己之外一定会将剩余的票权投给对系统稳定性最大的候选人，进而保证系统的安全和稳定。\\n\\n## 3.4 总结\\n\\n该方案是对现有 EOS 投票方案的进一步探索，借助 Saari 等人的研究成果，以期能使 BET 投票方案更加完善，该方案相较于现行的 EOS 方案有更强的抗大票权者控制能力，同时又保证委托制的安全性。但正如 Arrow 不可能定理说的那样，当限定在某些条件下时完美的投票方案是不存在的。因此我们希望在合理的假设的前提下能够变得更好。\\n\\n[^1]: [波达计数法，Borda Count](https://en.wikipedia.org/wiki/Borda_count) \\n[^2]: Kenneth J. Arrow: A Difficulty in the concept of social welfare. In Journal of Political Economy Vol. 58, No. 4 (Aug., 1950), pp. 328-346 \\n[^3]: B steven j Paradoxes in Politics: An Introduction to the Nonobvious in Political Science \\n[^4]: Michel A. Habib and Alexander Ljungqvist Firm Value and Managerial Incentives: A Stochastic Frontier Approach \\n[^5]: Charles R. Hadlock. • ”Discrete Mathematical Models: With Applications to Social, Biological, and Environmental. Problems” byFred Roberts. ...... Prentice-Hall, Englewood Cliffs, N.J., 1976. \\n[^6]: D.G.Saari choice electration Mathematics and Voting \",\"type\":\"referendum-v1\",\"incentives\":\"0.0000 BOS\",\"receiptor\":\"sheldonhuang\"}", + "created_at": "2019-08-21T18:01:00" + }, + "stats": { + "votes": { + "1": 38, + "total": 38, + "proxies": 23, + "accounts": 15 + }, + "accounts": { + "0": 0, + "1": 55676366693, + "total": 55676366693 + }, + "proxies": { + "0": 0, + "1": 130179999674, + "total": 130179999674 + }, + "staked": { + "0": 0, + "1": 185856366367, + "total": 185856366367 + }, + "block_num": 43385214 + } + }, + "bosantifraud": { + "id": "bosantifraud_20190524", + "proposal": { + "proposal_name": "bosantifraud", + "proposer": "atticlabhelp", + "title": "BOS Antifraud Shield", + "proposal_json": "{\"content\":\"The lack of diligence of ECAF and deliberation of 15 BP at EOS lead fraudsters who managed to steal money to exchange EOS for fiat/crypto and to withdraw money from EOS chain before the accounts have been added to the blacklist. And the last incidents have demonstrated us the failure of both the blacklist and ECAF. The AtticLab team studied that almost all Block Producers have signed the transaction that was in the blacklist. Everything due to human inattentiveness. One of those latest bright examples is a lost of 2 000 000 EOS.The frozen blacklist account gm3dcnqgenes was invalidated, resulting in 2.09 million EOS were transferred. The reason for this failure is that the newly entered BP of the 21 did not update the blacklist configuration on time, and the attacker caught the opportunity. Only part of such funds was locked, a big part of stolen funds there withdraw before BPs are.\\n\\nOur idea is to create an internal tool which attackers would have no access to. In order to counteract, it is obligatory to:\\n\\n1. Act very quickly\\n2. Interact with the exchanges\\n3. Track the whole onchain transaction\\n\\nMore - https://medium.com/eosatticlab/boscore-proposal-bos-antifraud-shield-1c6623171c4a\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-24T11:37:16" + }, + "stats": { + "votes": { + "1": 6, + "total": 6, + "proxies": 0, + "accounts": 6 + }, + "accounts": { + "0": 0, + "1": 9057658615, + "total": 9057658615 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 9057658615, + "total": 9057658615 + }, + "block_num": 43385214 + } + }, + "bosdacfcwp11": { + "id": "bosdacfcwp11_20190610", + "proposal": { + "proposal_name": "bosdacfcwp11", + "proposer": "bosdacserver", + "title": "Support for the development of the DAC Factory", + "proposal_json": "{\"content\" : \"**Support for the development of the DAC Factory**

**Introduction**

From its earliest design days the eosio software has been marketed as a way to launch Decentralised Autonomous Communities (DACs). Block.one, the creator of the eosio software, even had a keynote presentation which highlighted how eos would usher in an era of DACs where all participants had aligned interests and which were transparent, auditable, trustworthy and inclusive.

eosDAC took up the challenge and became the first functioning DAC on the EOS Mainnet. eosDAC has also produced open source code and tools to help others set up DACs.

The eosDAC website ([http://eosDAC.io](http://eosdac.io)) has a wealth of information on DACs. Also, as examples, the eosDAC member client is walked through in detail here - [https://www.youtube.com/watch?v=ORlMwVyHqxI](https://www.youtube.com/watch?v=ORlMwVyHqxI) and the scripts to set up a DAC are detailed here - [https://steemit.com/dac/@eosdac/tutorial-launching-your-own-dac-on-the-jungle-test-network-with-eosdac](https://steemit.com/dac/@eosdac/tutorial-launching-your-own-dac-on-the-jungle-test-network-with-eosdac)

**The DAC Factory**

Despite the considerable progress that has been made, there is a still a technical barrier for would-be-DACs to overcome. To address this, and to meet one of its stated goals of being the DAC enabler, eosDAC is planning to create a hosted solution (working title "the DAC Factory") that will allow communities to set up and run their DACs using a simple user interface.

To facilitate this, eosDAC is asking for support from partners to assist with development where there is a mutual win-win situation.

The BOSCore chain is a technically ambitious eosio chain which has affordable EOS RAM and has been pioneering inter blockchain communication. This makes the BOSCore chain a good partner for DACs and the chain could benefit from eosDAC highlighting the benefits of the BOScore chain for prospective DACs.

**Requests**

The primary needs for the DAC factory are outlined below.

1. Upgrades to the DAC toolkit smart contracts to allow multiple DACs to utilise the same accounts. This will allow all users to utilise eosDAC security features and apply technical upgrades easily. There are 4 primary smart contracts which will be subject to significant modifications - eosdactokens, daccustodian, dacmultisigs and dacproposals.

BOS contribution requested for section - 250000

| **Line Item** | **Amount (BOS)** |
| Upfront | 100000 |
| On completion of design document specifying required changes to eosdactokens | 10000 |
| On completion of design document specifying required changes to daccustodian | 30000 |
| On completion of design document specifying required changes to dacproposals | 35000 |
| On testable completion of design changes of eosdactokens | 10000 | | On testable completion of design changes of dacmultisigs | 10000 |
| On testable completion of design changes of daccustodian | 25000 |
| On testable completion of design changes of dacproposals | 30000 |

2. Design and Implementation of multiple configurable token contracts for use by DACs. This will allow DACs to choose a customized token with it's own economics.

BOS Contribution requested for section - 150000.

| **Line Item** | **Amount** |
| Upfront | 50000 |
| On completion of design document | 50000 |
| On testable completion of implementation | 50000 |

3. Design, development and testing of a no-frills user interface for a hosted DAC factory

BOS Contribution requested for section - 500000.

| **Line Item** | **Amount** |
| Upfront | 100000 |
| On completion of design of changes to the DAC member client for multiDAC contracts | 100000 |
| On completion of the defined working interface for set up of a DAC | 100000 |
| On completion of full design of screen and UX flow for Setup | 100000 |
| On completion of changes to the defined changes to the DAC member client | 100000 |

**Team**

The team will include established eosDAC contributors such as Michael Yeates, Luke Stokes, Dallas Johnson and Piecesandbits. The funds will also allow eosDAC to add to its cohort of projects managers, designers, developers and testers. BOS community members with EOS development skills who want to be part of this development are encouraged to contact the team on Discord.

**Limitations and assumptions**

A) Although the DAC factory will create and token and its permissions, the DAC Factory is not intended to handle the token distribution and users will be advised to seek advice from other parties, such as lawyers and KYC providers, in respect to this.
B) Other funders, including eosDAC itself will also be contributing to the development costs. As such BOSCore will be credited as a key partner in the development of the DAC Factory.
C) Although the BOSCore chain will be promoted by eosDAC but eosDAC reserves the right to run the DAC Factory on other eosio chains.
D) It is assumed that the core BOSCore code will not have require significant differences to the eosio core platform.
E) The target version of the eosio CDT software is 1.6.x\", \"type\" : \"referendum-v1\"}", + "created_at": "2019-06-10T23:37:17" + }, + "stats": { + "votes": { + "1": 4, + "total": 4, + "proxies": 0, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 985134160, + "total": 985134160 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 985134160, + "total": 985134160 + }, + "block_num": 43385214 + } + }, + "boseagleeye1": { + "id": "boseagleeye1_20190621", + "proposal": { + "proposal_name": "boseagleeye1", + "proposer": "beosinbosbos", + "title": "Eagle Eye (BOS)", + "proposal_json": "{\"content\":\"# Eagle Eye (BOS)提案\\n\\n \\n\\n目录\\n\\n提案背景\\n\\n提案介绍\\n\\n技术优势\\n\\n提案执行\\n\\n提案目标 \\n\\n提案预算\\n\\n \\n\\n## **1.** **提案背景**\\n\\n \\n\\n区块链带来安全与便利的同时，也带来挑战。由于区块链分布式和不可篡改的特点，催生出许多新的商业模式，但该技术目前仍不够完善，这导致更多的网络攻击瞄向区块链。据统计，2018 年区块链安全事件发生 138 起，而进入 2019 年之后，区块链安全事故数量是有增无减。\\n\\n为防范区块链特有的交易风险和安全威胁，成都链安推出Eagle Eye态势感知和安全管控平台，解决现有区块链安全防御手段上没有全局视角统一安全监管、无法将生态中各相关方串联起来挖掘出有价值的安全威胁的问题，为用户提供安全和运营方面的全面保障，使用户可以聚焦于自身的业务实现上，无需花费更多精力在安全保障和运营监控分析上。\\n\\n \\n\\n \\n\\n## **2.** **提案介绍**\\n\\n \\n\\nEagle Eye是成都链安面对区块链特有的交易风险和安全威胁推出的态势感知和安全管控平台。\\n\\nEagle Eye以区块链上数据收集、关联分析挖掘为核心，结合交易所、钱包、DApp等链上重要环节上的威胁情报，利用大数据和人工智能技术解决现有区块链安全防御手段上没有全局视角统一安全监管、无法将生态中各相关方串联起来挖掘出有价值的安全威胁的问题。Eagle Eye根据交易风险和安全威胁的趋势变化进行态势预警、报警和处置，后续还将提供交互式分析和挖掘工具，使用户以可视化方式自主分析相关安全事件和对交易追踪溯源。\\n\\nEagle Eye全面检测链上资产、区块链生态中各相关方的安全漏洞、威胁和交易风险，具备全面及时的态势感知、安全预警和响应处置能力。 \\n\\nEagle Eye态势感知平台为链平台面向项目方提供态势呈现和运维管理两种界面。态势呈现大屏为用户呈现全网和项目方的安全态势分析，运营态势为用户提供项目方的交易分析统计信息。用户通过态势感知平台随时了解当前安全状态和运营状态：\\n\\n \\n\\n![img](https://www.lianantech.com/static/img/%E5%9B%BE%E7%89%872.9b4ead6.png)\\n\\n安全态势呈现大屏示意图\\n\\n![img](https://www.lianantech.com/static/img/%E5%9B%BE%E7%89%873.f6730c3.png) \\n\\n运营态势呈现示意图\\n\\n \\n\\n \\n\\n## **3.** **技术优势**\\n\\n \\n\\nEagle Eye具备资产感知、漏洞感知、威胁感知、风险感知、预警感知、处置感知六大态势感知能力。\\n\\n![img](https://www.lianantech.com/static/img/%E5%9B%BE%E7%89%874.6df97fc.png)\\n\\n \\n\\n- 数据采集和处理方面：支持对BOS链上数据的采集和处理，支持公开来源区块链相关威胁情报的获取\\n\\n- 大数据存储方面：海量数据归一化存储，实时高并发访问\\n\\n- 采用AI安全分析\\n\\n- 与威胁情报系统联动\\n\\n- 对预警事件按照发生位置、影响范围、危害程度等条件进行分类，支持分级别、多类别的预警,精准推送给预警事件的相关方。\\n\\n- 将区块链分为安全和运营两个部分提供了安全态势和运营态势的大屏呈现，便于用户实时监控安全和运营态势，在检测到用户相关预警事件时，通过大屏动画和声音提醒用户及时处理预警事件。\\n\\n- 提供运营管理功能，用户通过运营管理页面配置安全和运营策略，包括链上帐号管理、报警记录管理、预警信息管理和安全策略配置。\\n\\n \\n\\n## **4.** **使用环境**\\n\\n \\n\\n必备设备为一台管理终端，同时配备两台态势呈现大屏则使用效果更好。软件使用chrome浏览器即可打开态势感知系统。\\n\\n \\n\\n## **5.** **提案执行**\\n\\n \\n\\n1、2019年7月，发布BOS链平台β版本，具备资产感知、漏洞感知、威胁感知、风险感知、预警感知、处置感知六大态势感知能力。\\n\\n2、2019年9月，发布BOS链平台Release版本，项目方可以入住态势感知系统 \\n\\n3、2019年10月-12月，针对BOS用户的使用反馈，进一步优化系统使用体验，并不断增强各项感知能力指数，给用户更加全面和安全的保障\\n\\n4、2019年，紧跟BOS 链平台的更新和升级，不断完善系统感知能力，增加预警报警模型，并对BOS用户提供更多定制化服务。\\n\\n5、2019年，对态势感知系统进行安全运维，提供安全事件的分析、确认、预警和报警服务。\\n\\n \\n\\n## **6.** **提案目标**\\n\\n\\n\\nEagle Eye的目标是为用户的应用项目提供安全和运营方面的全面保障，使用户聚焦于自身的业务实现上，安全保障和运营监控分析可以依托于Eagle Eye。\\n\\n\\n\\n## **7.** **提案预算**\\n\\n\\n\\n一共需要95万bos支持，前期需要50万bos\\n\\n1.开发费用：50万bos\\n\\n2.维护费用：20万bos\\n\\n3.服务器费用：10万bos\\n\\n4.安全运维费用：15万bos\",\"type\":\"referendum-v1\",\"incentives\":\"0.0000 BOS\",\"receiptor\":\"beosinbosbos\"}", + "created_at": "2019-06-21T03:51:08" + }, + "stats": { + "votes": { + "0": 1, + "1": 13, + "total": 14, + "proxies": 10, + "accounts": 4 + }, + "accounts": { + "0": 150002, + "1": 67568381, + "total": 67718383 + }, + "proxies": { + "0": 0, + "1": 54800610003, + "total": 54800610003 + }, + "staked": { + "0": 150002, + "1": 54868178384, + "total": 54868328386 + }, + "block_num": 43385214 + } + }, + "bosfirewallx": { + "id": "bosfirewallx_20190701", + "proposal": { + "proposal_name": "bosfirewallx", + "proposer": "slowmistiobp", + "title": "FireWall.X on BOSCore: Powerful firewall for smart contract", + "proposal_json": "{\"content\":\"FireWall.X on BOSCore: Powerful firewall for smart contract\\n\\n# Proposal Background\\n\\nIn the latter half of 2018, EOSIO ecosystem security events were frequent. Many DApp smart contracts were hacked, resulting in a large number of EOS was stolen. SlowMist security team analyzed a large number of smart contract attack techniques, and discovered some of the major pain points and challenges surrounding the safety precautions of smart contracts. So we decided to develop a general smart contract firewall to resist hacker attacks.\\n\\n# Proposal Introduction\\n\\nFireWall.X on BOSCore is a powerful and practical firewall for smart contracts, similar to traditional firewalls for operating systems which control network traffic, FireWall.X on BOSCore can also execute control over inline actions and prevent unauthorized access to smart contracts. Used in combination with oracle technology, there is the added benefit of risk management, which will help prevent hackers from obtaining any account information contained in smart contracts.\\n\\nCooperate with FireWall.X on BOSCore web console, developers can control the blacklist and whitelist of DApp user freely, prohibit access by malicious users, limit the contract account use DApp, check the call frequency and abnormal call log. At the same time, FireWall.X on BOSCore provides common account detection interfaces and malicious transfer recognition for developers in the SDK, developers can also according to the need to call. \\n\\n[FireWall.X](https://firewallx.io/index-en.html)(on EOSIO) is the world’s first firewall for smart contracts. Over the past six months, it has access to dozens of DApps, providing security protection for DApp for a total of 30,000,000 times, and successfully intercepting more than 130,000 attacks. In April 2019, FireWall.X(on EOSIO) received [a interview about #BuiltOnEOSIO by Block.one](https://medium.com/@eosio/builtoneosio-firewall-x-mitigates-the-risk-of-attacks-for-apps-5ead07941b7c).\\n\\n# Proposal Execution\\n\\nThree developers and two operators from SlowMist security team will be responsible for the project. We will do this in five stages.\\n\\nStage 1: Develop firewall smart contract and SDK intelligent contract code for FireWall.X on BOSCore based on the characteristics of BOSCore for three weeks.\\n\\nStage 2: Set up BOSCore full nodes and develop nodeos plugin to obtain smart contract deployment record (setcode/setabi), for five weeks.\\n\\nStage 3: Release FireWall.X on BOSCore beta and collect feedback, for two weeks.\\n\\nStage 4: Release FireWall.X on BOSCore stable, create a FAQ and SDK documentation, for a week.\\n\\nStage 5: Continuously monitor and track smart contract attack on the blockchain, maintain firewall blacklist and contract account database.\\n\\n# Proposal Goal\\n\\nOur goal is to turn FireWall.X on BOSCore into a general on-chain smart contract firewall and improve the security of DApp smart contract on the BOS chain.\\n\\n# Proposed Budget\\n\\nThe project is expected to cost about 500,000 BOS.\\n\\nStage 1: 350,000 BOS, which is used to pay for the human and development costs of three developers and technical support in the event of an attack.\\n\\nStage 2: 150,000 BOS, which is used to pay for the human cost of 2 operators, as well as continuous firewall data maintenance and community operation.\\n\\n# 提案背景\\n\\n2018 年下半年，EOSIO 生态安全事件频发，不少 DApp 智能合约被黑客攻击，造成了大量的 EOS 被盗。慢雾安全团队分析了大量的智能合约攻击手法，总结发现 DApp 项目方在安全防御上存在很大的痛点和难点，由此我们决定开发一款通用的智能合约防火墙来抵御黑客攻击。\\n\\n# 提案简介\\n\\nFireWall.X on BOSCore 是一个强大、简洁而实用的智能合约防火墙，就像传统的操作系统防火墙可以实现对网络流量的管控一样，FireWall.X on BOSCore 可以实现对智能合约调用的管控，阻止非法访问。同时结合预言机技术还可以实现风险控制，防止智能合约的账号资产被攻击者窃取。\\n\\n配合 FireWall.X on BOSCore 控制台，开发者可以自由控制 DApp 的用户黑白名单，禁止恶意用户访问，限制合约账号使用 DApp，查看调用频率以及查看异常调用日志，同时在 SDK 内为开发者提供了常用的账号检测接口、恶意转账识别接口，开发者也可根据需要调用。\\n\\n[FireWall.X](https://firewallx.io/)(on EOSIO) 是全球首个智能合约防火墙，上线半年以来，已接入数十个 DApp，累计为 DApp 提供安全防护达 30,000,000 次，成功拦截攻击次数 130,000 多次，并在 2019 年 4 月[获得 Block.one #BuiltOnEOSIO 专题采访报道](https://medium.com/@eosio/builtoneosio-firewall-x-mitigates-the-risk-of-attacks-for-apps-5ead07941b7c)。\\n\\n# 提案执行\\n\\n来自慢雾安全团队的 3 名开发者和 2 名运营人员将会负责这个项目。我们将分五个阶段进行：\\n\\n第一阶段：结合 BOSCore 的特性，为 FireWall.X on BOSCore 开发防火墙智能合约及 SDK 智能合约代码，为期三周\\n\\n第二阶段：搭建 BOSCore 全节点，开发 nodeos 插件来获取智能合约部署记录(setcode/setabi)，为期五周\\n\\n第三阶段：发布 FireWall.X on BOSCore 测试版并收集反馈，为期两周\\n\\n第四阶段：发布 FireWall.X on BOSCore 正式版本，并配套制作 FAQ 及 SDK 接入文档，为期一周\\n\\n第五阶段：持续监测、追踪链上智能合约攻击行为，维护防火墙黑名单、合约账号数据库\\n\\n# 提案目标\\n\\n我们的目标是把 FireWall.X on BOSCore 打造成一个通用的链上智能合约防火墙，提升 BOS 链上 DApp 智能合约的安全性。\\n\\n# 提案预算\\n\\n本项目预计花费约 500,000 BOS；\\n\\n研发阶段：350,000 BOS，用于支付 3 名开发者的人力和开发成本，以及在攻击事件发生时的技术支撑；\\n\\n运营阶段：150,000 BOS，用于支付 2 名运营人员的人力成本，以及持续的防火墙数据维护、社区运营。\",\"type\":\"referendum-v1\",\"incentives\":\"500000.0000 BOS\",\"receiptor\":\"slowmistiobp\"}", + "created_at": "2019-07-01T09:54:29" + }, + "stats": { + "votes": { + "1": 3, + "total": 3, + "proxies": 1, + "accounts": 2 + }, + "accounts": { + "0": 0, + "1": 6580948913, + "total": 6580948913 + }, + "proxies": { + "0": 0, + "1": 20292805272, + "total": 20292805272 + }, + "staked": { + "0": 0, + "1": 26873754185, + "total": 26873754185 + }, + "block_num": 43385214 + } + }, + "bosmeetups": { + "id": "bosmeetups_20190524", + "proposal": { + "proposal_name": "bosmeetups", + "proposer": "atticlabhelp", + "title": "BOS Europe Meetups", + "proposal_json": "{\"content\":\"BOS Blockchain is developing very rapidly, but unfortunately, it is almost unknown in Europe and Eastern Europe.\\n\\nAttic Lab is Block Producer at majority blockchains and EOS based blockchains from the mainnet launch — EOS, BOS, ORE, Tezos, IOST, Waves, Cosmos, Irisnet, Dash, Qtum, Decred. We gathered huge experience in optimizing chain as well as creating off-chain tools — https://github.com/atticlab/ for improving blockchain usage and promote mass adoption. Solid knowledge of computer science, software engineering and finance helps us to build blockchain-based solutions from scratch as well as to collaborate with other blockchain teams as an equal partner. But for those purpose that all developments could work successfully and bring all the benefits and satisfaction to Users, no doubt there must be one thing — the audience.\\n\\nRead more - https://medium.com/eosatticlab/boscore-proposal-bos-europe-meetups-54cbe47ec7d5\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-24T11:47:33" + }, + "stats": { + "votes": { + "1": 7, + "total": 7, + "proxies": 1, + "accounts": 6 + }, + "accounts": { + "0": 0, + "1": 9057658615, + "total": 9057658615 + }, + "proxies": { + "0": 0, + "1": 20292805272, + "total": 20292805272 + }, + "staked": { + "0": 0, + "1": 29350463887, + "total": 29350463887 + }, + "block_num": 43385214 + } + }, + "bosnationwp2": { + "id": "bosnationwp2_20190823", + "proposal": { + "proposal_name": "bosnationwp2", + "proposer": "bosnationftw", + "title": "BOS WPS Enhancement Proposal / BOS WPS提案优化", + "proposal_json": "{\"content\":\"# BOS WPS Enhancement Proposal\\n\\nEOS Nation is proud to have delivered a fully functional [Worker Proposal System (WPS)](https://boswps.io/#/poll_detail?proposal=bosnationwps) on the BOS network. It has already enabled over 2.1 million BOS to be deployed to 3 projects that bring value to BOS and EOSIO as a whole. And there are many more projects with proposals in progress waiting to earn funding for valuable development, governance, and community building initiatives.\\n\\nWe’ve learned a lot watching the system in action and have been gathering feedback from users and the BOS Core team. Based on these learnings, we’ve already deployed some upgrades and are continuing to work on new features to improve the system and unlock even more value for EOSIO chains.\\n\\n### Scope of work already deployed for version 2\\n\\n- [auditor.bos - update auditor v2.0 smart contract](https://github.com/boscore/referendum/pull/73)\\n- [auditor.bos - enforce JSON input](https://github.com/boscore/referendum/issues/68)\\n- [vote tally - update tally to auditor v2.0](https://github.com/boscore/referendum/pull/75)\\n- [vote tally - add features](https://github.com/boscore/referendum/pull/72)\\n- [eosio.forum - set RAM payer as `get_self()`](https://github.com/boscore/referendum/pull/56)\\n- [eosio.forum - update README](https://github.com/boscore/referendum/pull/67)\\n- [eosio.forum - remove `expires_at`](https://github.com/boscore/referendum/pull/58)\\n\\n### Scope of work in development for version 3\\n\\n- [Allow multiple init escrows & fund escrow using memo name](https://github.com/boscore/referendum/issues/76)\\n - This would allow multiple escrows to be initialized and funded at a later date.\\n- [Vote tally V3.0](https://github.com/boscore/referendum/tree/master/vote-tally)\\n - Host vote tally results on Cloudflare to improve performance in China\\n - Integrate Python API into Vote Tally\\n - Store historical voting data\\n - Calculate eligible proposals which meet conditions\\n - create another table\\n- [BOS Executive Team smart contract](https://github.com/boscore/bet.bos/blob/develop/README.md)\\n\\n### Request\\n\\nFor development of version 2 and 3 of the BOS WPS, EOS Nation is requesting **450,000 BOS**.\\n\\n# BOS WPS提案优化\\n\\n能够在BOS网络上提供功能齐全的[工人提案系统（WPS）](https://boswps.io/#/poll_detail?proposal=bosnationwps)，EOS Nation感到很自豪。 已经使超过210万个BOS部署到3个项目，这些项目为整个BOS和EOSIO带来了价值。 还有更多项目正在运行中，正在为有价值的发展，治理和社区建设计划\\n\\n筹集资金。\\n\\n我们已经从系统的实际操作运行中学到了很多，并且，我们一直在收集用户和BOS核心团队的反馈。 基于这些经验，我们已经部署了升级，并且正在继续开发新功能，以对系统做出改进，并为EOSIO链去创造更多价值。\\n\\n### 版本2已部署的工作范围\\n\\n- [auditor.bos - update auditor v2.0 smart contract](https://github.com/boscore/referendum/pull/73)\\n- [auditor.bos - enforce JSON input](https://github.com/boscore/referendum/issues/68)\\n- [vote tally - update tally to auditor v2.0](https://github.com/boscore/referendum/pull/75)\\n- [vote tally - add features](https://github.com/boscore/referendum/pull/72)\\n- [eosio.forum - set RAM payer as `get_self()`](https://github.com/boscore/referendum/pull/56)\\n- [eosio.forum - update README](https://github.com/boscore/referendum/pull/67)\\n- [eosio.forum - remove `expires_at`](https://github.com/boscore/referendum/pull/58)\\n\\n### 版本3的开发工作范围\\n\\n- [允许多个初始化托管和资金托管的使用备忘录名称](https://github.com/boscore/referendum/issues/76)\\n - 这将使得多个托管在之后能被初始化并获取资助。\\n- [3.0版本计票机制](https://github.com/boscore/referendum/tree/master/vote-tally)\\n - 主机计票结果显示，Cloudflare在中国的性能将有所改善\\n - 将Python API集成到计票中\\n - 存储历史投票数据\\n - 计算符合条件的提案\\n- [BOS执行团队智能合约](https://github.com/boscore/bet.bos/blob/develop/README.md)\\n\\n### 需求\\n\\n为了开发BOS WPS的第2版和第3版，EOS Nation正在提出450,000个BOS的需求。\\n\",\"type\":\"referendum-v1\",\"incentives\":\"450000.0000 BOS\",\"receiptor\":\"bosnationftw\"}", + "created_at": "2019-08-23T03:38:20" + }, + "stats": { + "votes": { + "0": 1, + "1": 3, + "total": 4, + "proxies": 3, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 6580948912, + "total": 6580948912 + }, + "proxies": { + "0": 2392754800, + "1": 23009727714, + "total": 25402482514 + }, + "staked": { + "0": 2392754800, + "1": 29590676626, + "total": 31983431426 + }, + "block_num": 43385214 + } + }, + "bosnationwps": { + "id": "bosnationwps_20190524", + "proposal": { + "proposal_name": "bosnationwps", + "proposer": "xksddkpnmhus", + "title": "BOS On-Chain Worker Proposal and Escrow system", + "proposal_json": "{\"content\":\"BOS On-Chain Worker Proposal and Escrow system\\n\\nWith 100 million BOS tokens from the BOS token generation earmarked for distribution to projects seeking funding, an on-chain worker proposal and escrow system is required to bring transparency, accountability and stakeholder oversight to the distribution process.\\n\\nEOS Nation has already completed development for such system and deployed it to the BOS Mainnet. Leveraging work and learnings gained developing the EOS referendum system and borrowing from new innovations developed by eosDAC, we’ve deployed a system that enables token holders to request funds for proposed work, vote to approve funding, and elect auditors to validate work and release funds to developers as milestones are met. To compensate our team for the work already completed (and prove its utility), we’re leveraging the system we built to request 515,000 BOS tokens. \\n\\n\\nScope of work deployed\\n\\nVote Tally\\nUsed to calculate votes for all on-chain proposals posted through the eosio.forum contract. Aggregates all the staked BOS token weights for each user, proxy, and auditor and hosts aggregated data as AWS S3 Bucket.\\n\\nEscrow\\nAn escrow contract designed for securing funds for approved work and distributing them when work is completed. Funds can be released by BET if they are satisfied by the work completed. Block Producers can release or return the funds in the case of a dispute.\\n\\nAuditor\\nEOSIO Smart Contract used to create elections for auditors. Elected auditors are granted MSIG permission to the BOS auditor authority and are rewarded for providing an opinion in the case of a dispute to release funds for completed work.\\n\\f\\nRequests\\n515,000 BOS tokens for work already delivered, broken down as follows:\\n\\n\\nDESCRIPTION AMOUNT\\nTally schematics design 15,000 BOS\\nBOS Referendum backend tally with Nodeos Table Snapshots development 55,000 BOS\\nBOS Referendum Tally Unit testing 35,000 BOS\\nDeploy smart contracts (forum, escrow, auditor) 10,000 BOS\\nEscrow smart contract development 105,000 BOS\\nEscrow smart contract unit tests 65,000 BOS\\nAuditor smart contract development 65,000 BOS\\nAuditor smart contract unit tests 110,000 BOS\\nAdministration 55,000 BOS\\n\\nTOTAL 515,000 BOS\\n\\nhttps://docs.google.com/document/d/1b_-04zubLY1Ajqh1qnoK7FJvoitfjrR-s8HNFBRv8-E/edit?usp=sharing\\n\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-24T14:45:37" + }, + "stats": { + "votes": { + "1": 66, + "total": 66, + "proxies": 19, + "accounts": 47 + }, + "accounts": { + "0": 0, + "1": 54091554763, + "total": 54091554763 + }, + "proxies": { + "0": 0, + "1": 110236907511, + "total": 110236907511 + }, + "staked": { + "0": 0, + "1": 164328462274, + "total": 164328462274 + }, + "block_num": 43385214 + } + }, + "bossnapshots": { + "id": "bossnapshots_20190620", + "proposal": { + "proposal_name": "bossnapshots", + "proposer": "wps.sweden", + "title": "Provide up to date snapshots to support IBC and history nodes", + "proposal_json": "{\"content\":\"Chinese in bottom - 中文在底部\\n--- \\n
\\nWe will provide snapshots that are currently updated every 12 hours for EOS and every 24h for BOS, Meetone and Worbli.
\\nBOS: EOS: Worbli: Meetone: \\n\\n## Problem - Troubleshooting IBC and supporting history nodes\\n\\nAs described in this article: \\n\\nOne of the issues with IBC that needs to be solved is to provide a solution for when relay nodes lack specific data.\\n\\n> Fault description: Let's take the transfer from Chain A to Chain B as an example. Assuming that a cross-chain transfer transaction occurs in the 10000 blocks, Chain B's relay (relay B) requests a bunch of headers from Chain A's relay (relay A), for example, requests headers 10000-10085, a total of 86 headers.\\n\\n> According to the BP signature verification logic in EOSIO, relay A needs to get blockroot_merkle of block 10000, but on ordinary nodes, only blockroot_merkle of blocks in forkdb can be obtained, so ibc_plugin uses the block's extension to record blockroot_merkle for some blocks. If in the process of using IBC, if for some reason, such as the administrator change a normal fullnode to a relay node at header_num greater than 10000, relay A may failed to obtain blockroot_merkle of block 10000, then the subsequent cross-chain behavior can not be carried out.\\n\\n> Restoration:\\n\\n> First: Look for a snapshot whose block num of the head is less than 10000, for example 9000, and then start the relay node with this snapshot. At this time, the relay node can get the blockroot_merkle of the 10000 blocks. Second: reinitialize the IBC system (see below for details).\\n\\nEach time the IBC system needs to be reinitialized you will need a place to fetch an up to date snapshot. This is to quick and efficiently get everything back in order.\\n\\nWe as a community are working towards the goal of phasing out v1 history (the plugin has been deprecated by block.one). The most probable way ahead is that we go through state-history and use that plugin to index an external database, i.e. Hyperion which uses elastic search.\\n\\n## Solution - Providing a tool that increase efficiency of IBC and history nodes.\\n\\nOur solution is to bring an convenient place to download an up to date snapshot of the chain.\\n\\nYou will find updated snapshots every 6 hours for EOS, BOS, Worbli and Meetone to optimize the recovery of the IBC protocol.\\n\\nThere are multiple ideas to solve the history issue and currently it is most likely that the state-history solution will be used. The availability of snapshots will ease the process of keeping a state-history node synced. Which means it will be more reliable for everyone wanting to use it. By using a new history solution we can get back in sync faster, use less storage and provide better indexing.\\n\\n## Execution Plan\\n\\nWe have already built and executed the plan, and it is open and available for anyone and everyone to use. For the coming future our work is to make sure they stay up to date with little to no issues along the way.\\n\\nTo develop our snapshot portals we have involved 3 people in our team, and for the future it will most likely involve one of us couple of hours per month.\\n\\nYou find our snapshots platforms here:\\n\\n[EOS Snapshots](https://snapshots.eossweden.org/)
\\n[BOS Snapshots](https://snapshots.bossweden.org/)
\\n[Meetone Snapshots](https://snapshots.meetsweden.org/)
\\n[Worbli Snapshots](https://snapshots.meetsweden.org/)
\\n\\n## Fund Release Plan\\n\\nWe provide the snapshot platform for the community to use however they deem fit. This proposal is an open letter to find out if the community value our solution to one of the current IBC and history problems.\\n\\nOur request comes in at a symbolic sum of 50,000 BOS per chain we initiated a snapshot portal for.
\\nThis amount is thought to re compensate the time we spent putting it together and to cover parts of the future expenses involving the snapshot platforms.\\n\\n### We kindly ask for 200,000 BOS to compensate for building and maintaining this project.\\n\\nThis will cover our costs for the coming 8 months - Until February 2020.\\n\\n## Team\\n\\nEric - CTO - [Telegram](https://t.me/xebb82/)
\\nVahid - CEO - [Telegram](https://t.me/vahidtoosi1/)
\\nHenrik - Tech wizard - [Telegram](https://t.me/pnxmode/)
\\nAnders - Daily operations - [Telegram](https://t.me/orcus/)
\\nGunnar - Tech Genious - [Telegram](https://t.me/gunnarpope/)
\\nJavier - APP developer - [Telegram](https://t.me/javierjmc/)
\\nAlex - Community - [Telegram](https://t.me/alexfengshuo/)
\\n\\n## Relevant Links\\n\\nWebsite: | | |
\\nTelegram:
\\nWechat: ID: eossweden
\\nTwitter:
\\n\\n---\\n\\n## 提供最新的快照以支持IBC（跨链通信）和历史节点\\n\\n我们节点目前为EOS主网提供每12小时更新一次的快照，并为BOS、Meetone和Worbli提供每24小时更新一次的快照。
\\nBOS: [https://snapshots.bossweden.org](https://snapshots.bossweden.org/) \\nEOS: [https://snapshots.eossweden.org](https://snapshots.eossweden.org/) \\nWorbli: [https://snapshots.worblisweden.org](https://snapshots.worblisweden.org/) \\nMeetone: [https://snapshots.meetsweden.org](https://snapshots.meetsweden.org/)\\n\\n## 挑战 - IBC的故障排查；历史节点的支持\\n\\n如本文所述：\\n\\n\\n\\n目前需要解决的IBC问题之一，是为中继节点上特定数据的缺失提供解决方案。\\n\\n> 故障描述：例如，我们需要将数据从链A转移到链B。假设在10000个区块中发起跨链转移事务，链B的中继（中继B）从链A的中继（中继A）请求一些区块头，例如，请求区块头10000-10085，总共86个区块头。\\n\\n> 根据EOSIO中的BP签名验证逻辑，中继A需要获取第10000个区块的blockroot_merkle（默克尔树区块根），但是在普通节点上，只有forkdb中区块的blockroot_merkle（默克尔树区块根）可被获得，因此ibc_plugin只能使用区块的扩展来记录某些区块的blockroot_merkle（默克尔树区块根）。如果在使用IBC的过程中，如果由于某种原因，管理员将一个正常的完整节点更改为header_num（区块头数）大于10000的中继节点，那么中继A可能无法获得第10000个区块的blockroot_merkle（默克尔树区块根），那么后续的跨链行为则可以不被执行。\\n\\n> 恢复：\\n\\n> 第一步：查找区块头的区块数小于10000的快照，例如9000，然后使用此快照启动中继节点。此时，中继节点可以获得这10000个区块的blockroot_merkle（默克尔树区块根）。\\n>\\n> 第二步：重新初始化IBC系统（详见下文）。\\n\\n每次需要重新初始化IBC系统时，我们都需要一个地方来获取最新的快照。这是为了快速有效地将所有内容整理回来。\\n\\n我们作为一个社区正在努力实现逐步淘汰v1历史的目标（该插件已被Block.One弃用）。最可能的方法是我们通过状态历史并使用该插件来索引外部数据库，比如，使用弹性搜索的hyperion。\\n\\n## 解决方案 - 提供可提高IBC和历史节点效率的工具\\n\\n我们的解决方案是为链上的最新快照提供一个易下载的地方。\\n\\n我们将提供每6小时更新一次的EOS，BOS，Worbli和Meetone快照，以优化IBC协议的恢复。\\n\\n解决历史问题有多种想法，目前很可能会使用状态历史解决方案。快照的可用性将简化保持状态历史节点同步的过程。这意味着它对每个用户来说都更可靠。通过使用新的历史解决方案，我们可以更快地恢复同步、使用更少的存储并提供更好的索引。\\n\\n## 执行计划\\n\\n我们已经制定并执行了该计划，并保持开放，让任何人都可以使用。我们未来的工作，是确保它们始终保持更新，不出现或极少出现问题，来保证最少停机时间。\\n\\n为了开发我们的快照门户，需要我们团队的三位成员参与。未来，我们需要每月花费几小时来维护它们。\\n\\n以下我们的快照平台：\\n\\n[EOS Snapshots](https://snapshots.eossweden.org/)
\\n[BOS Snapshots](https://snapshots.bossweden.org/)
\\n[Meetone Snapshots](https://snapshots.meetsweden.org/)
\\n[Worbli Snapshots](https://snapshots.meetsweden.org/)
\\n\\n## 基金使用计划\\n\\n我们提供快照平台供社区随意使用。该提案是一封看社区是否重视我们对当前IBC和历史问题解决方案的公开信。\\n\\n我们的诉求是为每个开发快照的链申请50,000个BOS的基金。
该金额包括我们开发和维护快照门户所用的时间成本，并涵盖了涉及快照平台的未来部分费用。\\n\\n### 所以，我们总共申请200,000个BOS来支持建设和维护这个项目。\\n\\n这会涵盖未来8个月的成本 - 直到2020年2月。\\n\\n## 团队\\n\\nEric - CTO - [Telegram](https://t.me/xebb82/)
\\nVahid - CEO - [Telegram](https://t.me/vahidtoosi1/)
\\nHenrik - Tech wizard - [Telegram](https://t.me/pnxmode/)
\\nAnders - Daily operations - [Telegram](https://t.me/orcus/)
\\nGunnar - Tech Genious - [Telegram](https://t.me/gunnarpope/)
\\nJavier - APP developer - [Telegram](https://t.me/javierjmc/)
\\nAlex - Community - [Telegram](https://t.me/alexfengshuo/)
\\n\\n## Relevant Links\\n\\nWebsite: | | |
\\nTelegram:
\\nWechat: ID: eossweden
\\nTwitter:
\\n\",\"type\":\"referendum-v1\",\"incentives\":\"200000.0000 BOS\",\"receiptor\":\"wps.sweden\"}", + "created_at": "2019-06-20T19:52:44" + }, + "stats": { + "votes": { + "1": 7, + "total": 7, + "proxies": 3, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 5300100000, + "total": 5300100000 + }, + "proxies": { + "0": 0, + "1": 20709607239, + "total": 20709607239 + }, + "staked": { + "0": 0, + "1": 26009707239, + "total": 26009707239 + }, + "block_num": 43385214 + } + }, + "boswallets": { + "id": "boswallets_20190524", + "proposal": { + "proposal_name": "boswallets", + "proposer": "atticlabhelp", + "title": "BOS Wallets", + "proposal_json": "{\"content\":\"BOS is fast growing blockchain, but mostly presented in the Asian region. It’s enough difficult for the user, which does not understand Chinese to be updated with latest updates and to buy token for local fiat currency. Western and Eastern region is big enough to be ignored but involvement of mentioned requires adaptation and localization of wallets.\\nTo popularise the BOS for a population of central and eastern Europe through localization of wallet, creation of educational materials, airdrop for new users and etc. We can reach around 1 000 000 users every month on our social media — https://twitter.com/atticlab_it . Besides, we are about to maintain all the functions in the BOS ecosystem. To do this, we will create tutorials and video tutorials. In addition to support the basic function of BOS ecosystem, the BOS wallet should support all dApps so that the user could log in at any time and use his preferable application, also with this wallet you can register in any other wallet with a blink of an eye.\\n\\nAs it was mentioned earlier , we have a large audience coverage in eastern Europe. We definitely could use this audience as a wallet users for BOS. This means that we want to create the wallet that will fully support BOS ecosystem. As a benefit, we will translate it into several European languages ​​(English, Russian, Spanish, French, and etc.) it should be mentioned that we can do the same with the web version. In case you have no chance to use the mobile wallet you can use the web version of it. In addition, all the BOS proposals and REX will be available in the wallet.\\n\\n Read more - https://medium.com/eosatticlab/boscore-proposal-bos-wallets-da9f83a9d6da\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-24T11:51:59" + }, + "stats": { + "votes": { + "0": 1, + "1": 11, + "255": 1, + "total": 13, + "proxies": 1, + "accounts": 12 + }, + "accounts": { + "0": 8805746, + "1": 9066006487, + "total": 9074812233 + }, + "proxies": { + "0": 0, + "1": 0, + "255": 1146991705, + "total": 1146991705 + }, + "staked": { + "0": 8805746, + "1": 9066006487, + "255": 1146991705, + "total": 10221803938 + }, + "block_num": 43385214 + } + }, + "bprdproposal": { + "id": "bprdproposal_20190611", + "proposal": { + "proposal_name": "bprdproposal", + "proposer": "bosbornforbb", + "title": "The Decentralized LInkedIn", + "proposal_json": "{\"content\":\"BPRD项目 去中心化的LinkedIn\\n \\n 提案背景\\n 1、在招聘市场，对个人数据的隐私性、真实性有越来越多的需求。个人 隐私的泄漏对个人造成很大的困 扰。同时数据的真实性在当前个人互联网信用缺失的时代受到了更大的挑战。\\n 2、保护个人隐私变得越来越重要，同时很多公司、结构、个人对数据的真实性变得越来越渴求，并且愿 意为数据的真实性买单。用户一边要求隐私保护，另一边公司要求数据的真 实性。\\n 3、区块链技术发展的近十年，可以说改变了传统的信用体系和存储方式，区块链应用需要去挑战传统行 业已经固有的商业逻辑和发展轨迹，所以区块链落地应用如何结合、如何匹配对于商业场景变得尤为重 要，也是发展必须面临的挑战。BPRD项目致力于利用区 块链同互联网结合打造具有落地价 值的产品应 用，解决 现阶段人才市 场的困境。\\n \\n提案介绍\\n BPRD项目是Blockchain Personal Rsume Data(个人链上履历数据)的简称 \\n 1、简单说就是用户的履历数据不是存储在中心化的服务器上，而是存储到社区维护的去中心化的区块\\n链上，从而使个人履 历数据具有 归个人、不可 篡改两大特性 \\n 2、同时在数据不可篡改的基础上BPRD项目引入履历校验机制，用户邀请或BPRD平台根据用户间的弱\\n关系链自动分发其他用户校验履历的真实性，最终履历的真实性被确定 \\n 3、第三方机构过个人支付token获取经过校验的个人简历数据，免去了背调的流程\\n \\n提案目标——打造去中心化的Linkedin\\n 1、基于区块链技术确保用户数据的隐私 性，让数据回归用户本身;\\n 2、建立个人履 历数据的相互 评价机制 对简历的真实度达成共识\\n 3、通过token激励设计，推动职场人、猎 头、公司共同参与，搭建起一个覆盖 全球人才信息 资产的区块链\\n 4、最终BPRD将记录价值千亿的人才资 产信息。\\n \\n为什么选择BOS\\n 1、经过半年的发展，BOS已经成为EOS社区最活跃的EOS侧链，由大量的活跃用户，获客成本比较低 \\n 2、改进的实用型拜占庭共识协议将区块确认的不可逆时间由原来的3分钟缩减到现在的3秒，达到了互\\n联网级别的需求\\n 3、BOS低保创建账号、内置红包DAPP创建账号，由BOS基金会支持，降低了用 户创建账号的成本和门槛 \\n 4、BPRD致力于成为BOSS侧链的第一个互联网落地应用，促进BOSS生态的完善和里程碑式发展\\n \\n提案实施——数据隐私性\\n 用户履历数据通过BPRD客户端使用自己保管的密码对数据对称加密后保存到链上，确保数据归个人\\n提案实施——数据授权\\n 数据授权—非对称加密\\n 提案实施—分发校验\\n 用户上传履历数据成功后邀请相关用户对此履历数据真实性作校验，校验结果保存到链上\\n 提案实施—token模型\\n 1、用户上传简历获取token激励 \\n 2、公司、猎头支付token获取简历 \\n 3、用户校验简历获取token激励 \\n\\n产品规划——时间轴\\n 2019 年6月-7月：基于BOS公链通过合约方式来实 现产品DEMO，实现数据的加密、 分发、解密查看、校验等功能\\n 2019年7月-8月：批量导入履历数据，小范 围内产 品化，为下一步研发作准备，同时 设计开发合约分发校验机制\\n 2019 年9月：一期产品上线\\n 2019年10月...：产品更新迭代\\n \\n资金规划\\n 费用申请:10万BOS\\n 1、团队(8万 BOS):web前端:1人\\n 合 约:1人\\n 2、服务器(0.5万 BOS):阿里服务器(4c32g 500g配置两台)\\n 3、宣发费用:(1.5万BOS)\\n \\n \",\"type\":\"referendum-v1\",\"incentives\":\"100000.0000\",\"receiptor\":\"bosbornforbb\"}", + "created_at": "2019-06-11T09:55:22" + }, + "stats": { + "votes": { + "1": 2, + "total": 2, + "proxies": 0, + "accounts": 2 + }, + "accounts": { + "0": 0, + "1": 145335, + "total": 145335 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 145335, + "total": 145335 + }, + "block_num": 43385214 + } + }, + "btconbos": { + "id": "btconbos_20190529", + "proposal": { + "proposal_name": "btconbos", + "proposer": "kedar.moon", + "title": "Bitcoin Light Client: BOSWPS Proposal", + "proposal_json": "{ \"type\": \"referendum-v1\", \"content\": \"# DecentralBank BOS Proposal: Bitcoin Light Client\n\n We propose to build a Bitcoin Light Client directly onto the BOS chain.\n\n This will allow BOS smart contracts to listen for Bitcoin payments and trigger actions based on BTC payments trustlessly on-chain.\n\n ## Technical Details \n\n All the block headers from the Bitcoin chain will be synced to a BOS smart contract. These block headers can be used to produce Merkle proofs that a transaction has been included in a Bitcoin block. \n\n When a valid Merkle proof is provided for a transaction, that transaction's details are registered in the smart contract, and other smart contracts will be able to take action based on that payment.\n\n ## Milestones & Funding\n\n* Sync Block Headers (end of July)\n* Merkle proof verification for transactions (mid-September)\n\n For each phase of development, we are requesting 200,000 BOS in funding (total 400,000 BOS). This funding will go toward bringing an additional developer onto the project. \n\n ## Use Cases\n\n* Trustlessly listen for a BTC transaction to swap BOS for BTC\n* Dapps can accept Bitcoin as payment for services. For example, a betting dapp can accept Bitcoin as a payment and run an action when the payment has finalized without relying on a trusted source.\n\n ## Team\n\n DecentralBank is developing a blockchain for algorithmic stablecoins and is focused on building core infrastructure for EOSIO blockchains. \n\n The co-founders are Kedar Iyer and Sam Kazemian, and the team includes Travis Moore, the CTO of Everipedia. Together, these 3 were the developers behind the Everipedia protocol and website. \"}", + "created_at": "2019-05-29T00:22:26" + }, + "stats": { + "votes": { + "1": 11, + "total": 11, + "proxies": 7, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 4039445759, + "total": 4039445759 + }, + "proxies": { + "0": 0, + "1": 43372091885, + "total": 43372091885 + }, + "staked": { + "0": 0, + "1": 47411537644, + "total": 47411537644 + }, + "block_num": 43385214 + } + }, + "chintaionbos": { + "id": "chintaionbos_20190525", + "proposal": { + "proposal_name": "chintaionbos", + "proposer": "fsoryhwynckt", + "title": "BOS Network Development & Enhancement Plan: Increasing Network value with Chintai/通过 Chintai 提升BOS网络价值", + "proposal_json": "{\"content\":\"![](https://i.loli.net/2019/05/26/5ce96680590ed83033.png)\\n\\n## Proposal Background/提案背景\\n\\nThe foundational elements of the Chintai leasing engine are nearing completion. Our sights are set on leveraging Chintai to fundamentally change existing industries, and open the doors for new blockchain-based use cases. \\n\\n`Chintai` is targeting mass-adoption. \\n\\nWe will support this mission by providing a market efficiency layer for utility-based tokenized assets, build several products to enhance existing applications, and provide a foundation for any token to easily realize the benefits of leasing. \\n\\nWe believe our mission is squarely aligned with the values and goals of the BOS network, and look forward to bringing our services to BOS. \\n\\nTo date, Chintai has serviced the following: \\nTotal EOS Borrowed (Total Volume): 56,491,275 EOS\\nTotal Interest Paid: 222,658 EOS. \\n\\nChintai 租赁引擎的基础部件已接近完工。我们的目标是利用 Chintai 从根本上改变现有行业，并为基于区块链的新的用户场景打开大门。\\n\\nChintai 的目标是实现大规模落地应用。我们将会为基于实用性的代币化资产提供市场效率层，以支持这一使命，我们会创建多个产品来增强现有的应用程序，并部署一个相应的社交平台与我们的服务互补。\\n\\n我们相信，Chintai 的使命与 BOS 网络的价值和目标是一致的，并期待能够将我们的服务带给 BOS。\\n\\n迄今为止，Chintai 实现了如下的服务数据: \\nEOS 租借总量: 56,491,275 EOS\\n所支付利息总计: 222,658 EOS\\n\\n\\n## Chintai and BOS/Chintai 与 BOS\\n\\nThe Chintai team has been designing the platform to facilitate leasing of any token, and develop readiness to deploy on any EOSIO chain. \\n\\nWe would like to bring our services to the BOS network, add further enhancements to BOS that are specifically useful for the network, and continue development that will increase BOS network & token value. \\n\\nChintai 团队对平台持续打磨，致力于将其设计为可以便于为任何代币提供租赁服务，并为部署至任意 EOSIO 链做好准备。\\n\\n我们希望将我们的服务引入 BOS 网络，为BOS 进行进一步增强，使其对网络尤其有用，并继续开发，以提升 BOS 网络和代币的价值。\\n\\n\\n## Proposal Introduction/提案介绍\\n\\nChintai will be able to provide numerous services and enhancements to the BOS network that will help create a flourishing dApp ecosystem. After initial development that is required to bring the Chintai platform to BOS, we would pursue and implement the following enhancements: \\n\\n\\nChintai 将为 BOS 网络提供多种服务和增强功能，这将有助于创建一个繁荣的 dApp 生态系统。在完成将 Chintai 平台引入 BOS 所需的初始开发之后，我们将着手实现如下的功能:\\n\\n\\n1\\\\. Market efficiency layer whereby resources and token utility can be accessed at lower costs, and token holders can receive income for lending. In the case of lenders and borrowers, price volatility risk is mitigated. Any BOS token could be leased on the Chintai platform.\\n\\n2\\\\. Automatic resource management for dApps and users. Chintai will be able to provide “pay as you go” services for dApps - all users are 100% covered in this program.\\n\\n3\\\\. Chintai API for dApps to integrate leasing of NFT or other tokens directly into their platform UI.\\n\\n4\\\\. NFT and Collectable standard for leasing. Any token contract will be able to easily adapt to our token standard for leasing, with no significant changes to pre-existing token contracts. \\n\\n5\\\\. We will also deploy other features on the BOS network, which include a OTC leasing market, P2P accounts for leasing, REX UI with full leasing metrics such as APR, and borrowing rates. \\n\\n1\\\\. 在市场效率层，可以以较低的成本访问资源和代币实用程序，使得代币持有者可以通过出租获得收入。对于出租者和租借者而言，缓解了价格波动的风险。任何 BOS 代币都可以在 Chintai 平台上出租。\\n\\n2\\\\. dApps 和用户的自动资源管理。Chintai 将能够为dApps提供“即用即付”的服务—-覆盖所有的用户。\\n\\n3\\\\. 用于 dApps 的Chintai API，可以借助 Chintai API，将NFT或其他代币的租赁功能直接集成至 dApp 的 UI 之中。\\n\\n4\\\\. NFT和收藏品的租赁标准。任何代币合约都能够轻松地适应我们的代币租赁标准，而无需对现有的代币合约进行重大更改。\\n\\n5\\\\. 我们还将在 BOS 网络上部署其他功能，包括场外租赁市场(OTC)、P2P租赁账户功能、带有完整租赁指标的REX UI，可以显示包括年化收益率(APR)和借款利率在内的指标。\\n\\n## Proposal and Execution/提案及执行计划\\n\\nYearly cost of Running Chintai on BOS\\nChintai 在 BOS 上运行的年度成本\\n\\n### Phase 1/阶段1\\n\\nDevelopment to launch Chintai on the BOS network with standard leasing markets, REX UI, new UI for ALL leasing markets, and OTC.\\n\\nDev Time: 3 months\\n\\n用于开发在 BOS 网络上线 Chintai 的标准租赁市场、REX UI、适用于所有租赁市场的新 UI 和OTC市场。\\n\\n开发时长: 3 个月\\n\\n### Phase 2/阶段2\\n\\nDevelopment and deployment of Automatic Resource Management on BOS\\n\\nDev Time: 2 weeks\\n\\n在 BOS 上开发和部署自动资源租赁功能\\n\\n开发时间: 2 周\\n\\n\\n### Phase 3/阶段三\\n\\nDevelopment and deployment of P2P accounts on BOS\\nDev Time: 1 month\\n\\n在 BOS 上开发和部署 P2P 账号\\n开发时间: 1 个月\\n\\n\\n\\n### Phase 4/阶段4\\n\\nDevelopment and Deployment of NFT standard and Chintai API on BOS\\n\\nDev Time: 2 Months\\n\\n在 BOS 上开发和部署 NFT 标准及 Chintai API\\n\\n开发时间: 2 个月\\n\\n\\nTotal Development time: 6 ½ months\\n\\n总计开发时间: 6个半月\\n\\n## Proposal Goal/提案目标\\n\\nAll of the features from phase 1-4 would provide a robust foundation whereby all basic leasing needs would be available to the BOS network. We also expect to continue development of many more features, including futures markets, that could easily be adapted to run on the BOS network. \\n\\n第 1-4 阶段的所有功能都将会提供一个健壮的基础，使 BOS 网络能够满足所有的基础租赁需求。我们还希望继续开发更多的功能，包括期货市场，这些功能可以很容易地在 BOS 网络上运行。\\n\\n\\n## Proposed Budget/预算\\n\\nWe reinvest 100% of our Block Producer rewards into our team salaries, development, EOSIO community events, and more.\\n\\nGiven our financial situation, we would like to ask that our reputation for being an excellent development team that produces impactful work is considered a determining factor for receiving 1M BOS to begin development. \\n\\nThe capital will be immediately liquidated in order to hire an additional developer, and pursue the agenda outlined. \\n\\n我们将 100% 的出块奖励再投资到我们的团队工资、开发、EOSIO 社区活动等事项之中。\\n\\n考虑到我们的财务状况，我们希望可以我们作为一个优秀开发团队的声誉作为决定性因素之一，以申请获得 100万 BOS 启动资金用于开发。\\n\\n这笔资金将会立即派上用场，用于聘请一名额外的开发者参与开发工作，使得计划可以如期完成。\\n\\n## More Info/更多信息\\n\\nlink: https://docs.google.com/document/d/11KI3QbiDvLEXwd9KDJ8mMamj9xX37nZHE-HSHO2RxUU\\n中文: https://docs.google.com/document/d/1VqXT6LiSmTmkPbxZF8dZeRje1Mmoa0-mYtCBCbYGCus\\n\\nChintai: chintai.io\\nContact Us: @RyanBethem, @shuke0327\\n\\n\\n\\n\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-25T16:16:33" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43385214 + } + }, + "chintaitobos": { + "id": "chintaitobos_20190529", + "proposal": { + "proposal_name": "chintaitobos", + "proposer": "chintaionbos", + "title": "Enhancing the BOS network with Chintai 通过 Chintai 增强 BOS 网络", + "proposal_json": "{\"content\":\"Chintai will be able to provide numerous services and enhancements to the BOS network that will help create a flourishing dApp ecosystem. \\n\\n## Proposal Name\\n\\n Enhancing the BOS network with Chintai\\n\\n## Problem\\n\\nWithout token leasing, any token on the BOS network is limited by the necessity of token ownership to access token utility. This puts economic constraints on developers, businesses, and users. Token holders are also deprived of the opportunity to make passive income from holding cryptocurrency.\\n\\nBy providing a platform for individuals to access token utility at lower costs through leasing tokens, the potential for network growth is significantly expanded.\\n\\nBusinesses can operate at significantly lower costs. Additionally, tokens that allow passive income opportunities through token leasing are far more attractive to own when compared to tokens that have no  passive income potential beyond price increase.\\n\\nToken leasing also opens the potential for other products like decentralized automated resource management, which eradicates the need for dApps and their users to manage CPU/NET. Without automated resource management, businesses and users are burdened with tracking their resources.\\n\\nNo other businesses have attempted to develop functionality that is comparable with the full scope of Chintai. We are pioneering the development of token leasing and related products that are made possible by token leasing on EOSIO. Our reputation precedes us as a team that has already engineered a solution for token leasing - our goal is to bring the next installment of [Chintai enhancements to the BOS network, including the CHEX token.](http://chintai.io)\\n\\n## Solution\\n\\nChintai will be able to provide numerous services and enhancements to the BOS network that will help create a flourishing dApp ecosystem. We can solve resource management, allow businesses to get access to resources at lower costs, and enable passive income streams that make the BOS token and all other BOS based tokens more attractive for investors. We can do all of this by providing the Chintai Token Leasing platform that has a matching engine which runs entirely on smart contracts.\\n\\n### Token Leasing\\n\\nMarket efficiency layer whereby resources and token utility can be accessed at lower costs, and token holders can receive income for lending. In the case of lenders and borrowers, price volatility risk is mitigated. Any BOS token could be leased on the Chintai platform. Chintai will offer a high-performance decentralized token leasing exchange to facilitate trades. Our engine and UI will be able to facilitate leasing of any utility token, in addition to NFT/SFTs. REX will also be included in the UI.\\n\\n### Decentralized automated resource management for dApps and users. \\n\\nChintai will be able to provide “pay as you go” services for BOS network dApps - all user CPU costs are 100% covered in this program. Without this solution dApps and users are required to manage their resources. Our service is fully decentralized, and always based on the market rate for CPU/NET costs.  \\n\\n[https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4](https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4)\\n\\n## Competitors\\n\\nToken leasing is being pursued by Scatter for specific purposes but they do not have a working product. They also do not appear to have the capacity to enable token leasing for any token. Since they lack a matching engine, Scatter is also lacks the ability to create organic markets, and are instead limited to providing a “market place”.\\n\\nAutomated Resource management has been developed by Dunya labs. However, their service is not decentralized, nor scalable. Since they depend on one or two whales/middle men to provide liquidity for their clients, dApps could lose access to resources at any point (not trustless). Additionally, they have to charge an artificially high rate/fee in order to keep their “liquidity provider”. Chintai relies entirely on the free market, and therefore does not have artificially high rates/fees, nor rely on paying anyone in order to stay in business.\\n\\n## Execution Plan\\n\\n### PHASE 1: BOS Leasing CPU/NET - 3mo development - Expected deployment August to September 2019\\n\\nThis portion of the project includes development time and milestones for deploying basic leasing functionality on the BOS network. Included along with the following milestones will be the Chintai 2.0 for high performance trading.\\n\\n* Lease matching engine including cross market order matching, and p2p functionality (1mo)\\n\\n* Auxiliary Functions and Controls (1mo)\\n\\n* Unit, Component and System Testing (1mo)\\n\\n* New Chintai 2.0 UI to seamlessly integrate all BOS lending markets with a cross-blockchain backend\\n\\n### PHASE 2: Automated Leasing 1mo development - Expected deployment September to October 2019\\n\\nThis portion of the project plan includes deployment of automated leasing functionality on the BOS network.\\n\\n* Nodeos plugin modifications (2 weeks)\\n\\n* Automated Resourcing Smart Contract (2 weeks)\\n\\n* Integration of BOS REX with the Chintai 2.0 UI\\n\\n### PHASE 3: Leasing of any token, including NFT/SFT - 2mo development - Expected deployment November - December 2019\\n\\nThis portion of the project includes leasing of any utility token including NFT/SFTs\\n\\n* Extensions to lease matching engine (3 weeks)\\n\\n* Token Pairing System - automatic listing for new or old tokens (1 weeks)\\n\\n* CHEX integration (4 weeks)\\n\\n## Fund Release Plan\\n\\nThe Chintai team is requesting 1 million BOS tokens are released in four tranches. All tranches specify development costs. Project management, RAM and server costs are baked into our calculations. Servers cost $250 dollars per month. Project management is 8-12k USD per month and RAM will be subject to current prices and usage.\\n\\n**TRANCHE 1**: The first tranche we are requesting 150K BOS tokens. This would be equivalent to roughly 20K USD or 2mo salary for one developer in USA/Europe. We are planning to hire an additional developer on the basis of this proposal being approved. This will help us achieve the goals outlined in this proposal in a more efficient manner, and begin all necessary steps to achieve the project goal. The funds will be used immediately for a new hire, and supporting the initial development costs.\\n\\n**TRANCHE 2**: Upon completion of phase 1 we are requesting 450k BOS tokens are released. We will have four full time developers working on this phase (80 hours per week minimum per developer) in addition to project management to ensure completion. Their respective salaries total about 50K USD per month for three months. This Tranche will help support roughly 67,500 USD or a little over ⅓ of the total project costs. Chintai will support the other ⅔ of development costs.  \\n\\n**TRANCHE 3**:  Upon completion of phase 2 we are requesting 100K BOS tokens are released. Development costs will include two developers working full time (80 per week minimum). 100k BOS tokens at current prices will cover 15K in development costs or about ¾ of total development costs.\\n\\n**TRANCHE 4**: Upon completion of phase 3 we are requesting 300k BOS are released. Development costs include 4 full time developers.  \\n\\n## Team\\n\\n### David Packham\\n\\nDavid has a 20yr career in finance and asset management in London, working for a range of global institutions in areas covering FinTech, business strategy and programme management. David studied economics and business systems analysis and design, and is a decentralist with a passionate belief in the potential of blockchain to change the world by increasing personal freedoms and reducing inequality. As general project manager of Chintai, he seeks to ensure all facets of the product meet the highest industry standards. He is also responsible for authoring the CHEX token white paper.\\n\\n### Charles Holtzkampf\\n\\nCharles Holtzkampf leads the infrastructure efforts at Chintai and is helping to design the underlying tech stack for Chintai. He has spent the past 20 years honing his skills in all matters of IT, from designing high performance VDI clusters to maintaining a 4000 node networking cluster for a leading business centre provider. He has spent time working as a security penetration tester and dabbles in Python development. In his lifetime he started a starfish type organisation called BOMelakiesie and for a time hosted the Burning man Afrika's website. He has extensive experience with programming, performance monitoring, increasing efficiency and infrastructure automation. His goal as the director of infrastructure is to ensure the Chintai platform is stable and secure.\\n\\n### Phillip Hamnett\\n\\nPhillip has 9 years of experience developing software in C++ and embedded C. He started his career as a physicist working in complexity theory, where he developed Monte Carlo simulations to model traffic flow in cities. Then he moved on to data analysis for the ATLAS experiment at the Large Hadron Collider, where he searched for new particles at extremely high energies. After he finished his Ph.D, he moved into the aerospace industry, developing software for Airbus. Finally, he has joined us and is working full time on the development of the Chintai platform. He is well known in the EOSIO community for being the Chintai smart contract developer, one of the experts for EOSIO smart contracts, and is regularly seeked for consultation for contract audit\\n\\n### Michael Fletcher\\n\\nMichael is a back end developer with 5 years industrial experience in the logistic automation sector. He's contributed to the development of systems used by some of the biggest companies on the planet. Specialising in creating real time, business critical, distributed systems. He is the core back end developer for Chintai and has played a crucial role in coding the matching engine, OTC market, and other core features of the Chintai platform.\\n\\n### Andrew Coutts\\n\\nAndrew is a full stack developer with experience building tools for the EOS community such as the RAM trading platform at www.buyeosram.io and the EOS Resource Planner at www.eosrp.io. He previously spent 4 years in the Application Performance Management (APM) industry as a subject matter expert on enterprise application monitoring & performance for companies like GEICO, Fannie Mae, and Marriott International. Prior to this Andrew spent 3 years as a core developer for the Magic Lantern Firmware Project, a free & open source firmware hack for Canon DSLR cameras. Andrew is passionate about blockchain and open source technologies and hopes to make a positive impact in the EOS community by helping to mature the ecosystem with more advanced tools and community platforms. He is best known for his work in developing the Chintai UI, which will be upgrade in early June.\\n\\n### Sean Kang\\n\\nSean has more than ten years of experiences in banking, finance, and urban engineering. He began his career as an account manager with the largest bank in Canada, operated various businesses in Korea and Canada, and lived in the United States. Sean discovered EOS while pursuing his Ph.D. degree in urban planning for the development of smart cities. He envisions our daily lives being fundamentally influenced by smart cities that leverage scalable blockchain technology. Combining his abilities as an urban planner to listen, understand, and implement what the community wants with his diverse cultural background enables Sean to deliver comprehensive solutions for the EOS community. He his main role pertains to business development and community relations in Korea.\\n\\n### Kai Jing\\n\\nKai has a background in Chemical Engineering and Software Engineering. He worked as a software developer and product manager in Guangzhou, specializing in the e-commerce industry. After discovering EOS in July, 2017, Kai decided to devote his time to helping people learn about EOS. He has written and translated several articles that cover EOS, including the Chinese version of EOS.io Technical Whitepaper v2.0\\\\. Kai is also a KOLs on BIHU with around 40,000 people in his following. Kai contributes to Chintai with his expertise in business development, and community relations in China.\\n\\n### Ryan Bethem\\n\\nRyan is passionate about grassroots campaigns related to social justice and financial equality. Before entering the blockchain industry, he was a Psychologist in San Francisco, specializing in psychoanalytic treatment of complex trauma and group therapy. Using a background in the psychology of group dynamics, public relations, politics and philosophy allows him to offer a unique perspective on the development of the EOSIO ecosystem and product development. He hopes to see EOSIO become a hub for redefining how communities can govern to amplify personal autonomy, raise the bar for quality of life, and set people free from exploitative third parties. As the Chintai product manager, Ryan is responsible for marketing, public relations, community, and forming strategic partnerships.\\n\\n### Liam Wu\\n\\nLiam has lived on three continents in the past twenty years and speaks fluent English, Spanish, and Chinese (Mandarin and Cantonese). His diverse upbringing allows him to view the blockchain industry with a unique integration of cultural perspectives. A combination of an awareness of cultural diversity, an intuitive sense of how to nourish communities, and an intrinsic understanding of community engagement have enabled Liam to develop projects such as EOS911\\\\. He is fascinated by blockchain technology, and plans to invest his youthful energy into encouraging the adoption of the nacint technology, while developing solutions for problems faced by the EOSIO community. With Chintai Liam is a jack of all trades and conduct business analysis, helps form strategic partnerships, and completes tasks that help the Chintai project flourish.\\n\\n## Relevant Links\\n\\nChintai Website & CHEX Token [Chintai.io](http://chintai.io)\\n\\nChintai 1.0 Exchange\\n\\n[Chintai 1.0](https://eos.chintai.io/exchange/EOS7D)\\n\\nAutomated Resource Management: [https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4](https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4)\\n\\n\\n## 提案名称\\n\\n通过 Chintai，提升 BOS 网络\\n\\n## 问题\\n\\n若缺乏相应的代币租赁功能，BOS 网络上的代币都会受限于代币所有权的制约，无法充分利用代币的应用特性。这给开发人员、企业和用户带来了经济约束。代币持有者也被剥夺了持有加密货币获取被动收益的机会。\\n\\n通过为个人提供平台，通过租用代币以更低的成本使用代币的应用功能，BOS 网络的增长潜力得到了显著扩展。\\n\\n企业可以以低得多的成本运营。此外，通过代币租赁获得被动收入机会的代币，相比于除了价格上涨之外没有任何被动收入潜力的代币，对自己更具吸引力。\\n\\n代币租赁还为去中心化的自动化资源管理等其他产品提供了潜力，这消除了dApps及其用户管理CPU/NET的需要。如果没有自动资源管理，企业和用户就会疲于跟踪他们的资源状况。\\n\\n目前还没有其他企业尝试开发出可以与 Chintai 的全部功能相媲美的功能。我们在EOSIO上率先开发了代币租赁及其相关产品，使其成为可能。Chintai 的团队在 EOS 社区中有良好的声誉，我们设计了代币租赁解决方案，目标是[将 Chintai 的下一阶段的增强功能引入至BOS网络，包括 CHEX 代币](http://chintai.io)。\\n\\n## 解决方案\\n\\nChintai 将为BOS网络提供大量服务和增强特性，这将有助于创建一个繁荣的 dApp 生态系统。我们可以解决资源管理问题，让企业以更低的成本获得资源，并启用被动收入流，使BOS代币和所有其他基于BOS的代币对投资者更具吸引力。\\n\\n我们可以通过提供 Chintai 代币租赁平台来实现这一切，该平台具有完全基于智能合约运行的撮合引擎。\\n\\n### 代币租赁\\n\\n市场效率层，使资源和代币的应用性可以以较低的成本获得，代币持有者可以获得租赁收入。对于出租者而言，价格波动风险得到了缓解。任何 BOS 代币都可以在Chintai平台上租用。Chintai将提供高性能的去中心化代币租赁交易所，方便交易。除了NFT/ SFT 之外，我们的引擎和UI将能够方便租赁任何应用型代币。除此之外，我们也会将REX加入至UI中。\\n\\n### 为dApps和用户提供去中心化的自动化资源管理\\n\\nChintai将能够为BOS网络 dApps 提供“即付即用”服务——所有用户的CPU成本都将在此计划中得到100%的覆盖。没有这个解决方案，dApps和用户就需要管理他们的资源。我们的服务是去中心化的，并且总是基于CPU/NET的市场租赁利率来设置。\\n\\n[https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4](https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4)\\n\\n## 竞争者\\n\\n Scatter 也将代币租赁列入他们的构想之中，但他们还没有提供可用的产品。Scatter 目前看来也无法提供为一切代币提供租赁功能的能力。由于他们缺乏匹配的引擎，Scatter 局限于提供一个内置的“marketplace”，却无法提供创建自发市场的能力。\\n\\nDunya实验室开发了自动化资源管理系统。然而，他们的服务不是去中心化的，可扩展性也受到制约。由于他们依赖于少数的大户/中间人为客户提供流动的EOS，dapp可能会在任何时候失去对资源的使用权(并非去信任的)。此外，他们需要收取人为的高利率/费用，以维系其“流动性提供者”。Chintai 完全依赖于自由市场，因此不存在人为的高利率/费用，也不需要为了业务的继续经营而进行类似方式的支付。\\n\\n## 执行计划\\n\\n### 阶段 1: BOS 租赁 CPU/NET - 开发时间 3 个月 - 预期部署时间  2019 年 8 月 至 9 月\\n\\n项目的这一部分包括在BOS网络上部署基本租赁功能的开发时间和里程碑。与以下里程碑一起包含在内的是用于高性能交易的 Chintai 2.0。\\n\\n* 租赁匹配引擎，包括跨市场订单匹配，p2p功能(1个月)\\n* 辅助功能与控制功能(1个月)\\n* 单元、组件和系统测试(1个月)\\n* 全新Chintai 2.0 UI集成\\n\\n### 阶段 2: 自动租赁功能 - 开发时间 1 个月 - 预期部署时间 2019 年 9月 至 10月\\n\\n项目计划的这一部分包括在 BOS 网络上部署自动租赁功能。\\n\\n* Nodeos插件修改(2周)\\n* 自动资源管理智能合约(2周)\\n* 将REX集成在UI中\\n\\n### 阶段 3: 包含 NFT/SFT 在内的任意代币提供租赁功能 - 开发时间 2 个月 - 预期部署时间 2019 年 11月 - 12月\\n\\n项目计划的此部分包括： 为任意代币(包括 NFT/SFT) 提供租赁功能\\n\\n* 租赁撮合引擎插件 (3 周)\\n\\n* 代币匹配系统 - 为代币实现自动上架的功能 (1周)\\n\\n* CHEX 接入 (4周)\\n\\n## 基金发放计划\\n\\nChintai 团队申请将 100万 BOS代币分四批进行发放。所有部分都对开发成本进行了详细说明。我们将项目管理、RAM和服务器成本考虑在内。服务器每月花费 250 美元。项目管理费用为每月8千-1.2万美元，RAM将根据当前价格和使用情况而定。\\n\\n**1 期**: 第一期我们需要15万的 BOS代币。这相当于在美国/欧洲的一个开发人员大约2万美元或2个月的工资。若该提案被批准，我们计划额外雇用一个开发者。这将帮助我们以更有效的方式实现本提案中概述的目标，并开始实现项目目标的所有必要步骤。这些资金将立即用于招聘新员工，并支持最初的开发成本。\\n\\n**2 期**: 在完成第1阶段后，我们申请发放 45 万个 BOS 代币。除了项目管理之外，我们还将有4名全职开发人员在此阶段工作(每个开发人员每周至少 80 小时)，以确保完成。他们各自的工资总计约为每月5万美元，持续三个月时间。这部分将帮助支持大约 67500 美元或略超过项目总成本的⅓。另外的⅔ 开发成本会由 Chintai 承担。\\n\\n**3 期**: 在完成第2阶段后，我们将请求释放10万个BOS代币。开发成本将包括两名全职开发人员(每周至少80小时)的费用。100 k BOS 代币以目前的价格计算，将帮助支付大约 1.5 万美元的开发成本，或者说开发成本的3/4。\\n\\n**4 期**: 在第三阶段完成后，我们请求发放 30万 BOS, 覆盖 4 名全职开发人员的开发成本。\\n\\n## 团队\\n\\n### David Packham\\n\\nDavid 在金融与资产管理领域有超过 20 年的从业经验，曾在金融技术、商业战略和项目管理等领域曾为诸多全球性机构工作。David所学专业为经济学和商业系统分析与设计，他是一个去中心化主义者，对区块链技术在增加个人自由和减少不平等来改变世界的潜力方面，他充满热情与信念。作为 Chintai 的主导者，他致力于确保产品的各个方面都符合最高的行业标准。David 也是 CHEX 代币模型白皮书的撰写者。\\n\\n### Charles Holtzkampf\\n\\nCharles 主导了 Chintai 的架构设计，并帮助设计了 Chintai 的技术选型。Charles Holtzkampf 拥有 20 年的 IT 经验，在编程、性能监控、提高效率和web服务方面也具备丰富的经验。他曾担任过安全渗透测试人员，并涉足Python开发。Charles 曾创建一个名为 BOMelakiesie 的海星类型的组织。作为 Chintai 的 CTO，Charles 致力于确保平台的稳定和安全性。\\n\\n### Phillip Hamnett\\n\\nPhillip 负责 Chintai 的智能合约开发工作，有着九年的软件开发经验，使用 C++ 和 嵌入式 C 语言编程。他曾是复杂性理论领域的物理学家，并曾负责高能物理领域的数据分析工作。完成博士学位后，Phillip 进入航空领域，为空客(Airbus)开发软件。如今 Phillip 是 EOSIO 智能合约开发方面的专家之一，最近为 MyKEY 项目提供了安全审计。\\n\\n### Michael Fletcher \\n\\nMichael 曾在物流自动化行业从事后端开发，有着 5 年的软件开发经验。他曾为一些全球性的大公司所使用的系统做出了开发贡献。Michael 专注于创建实时、涉及核心业务的分布式系统. Michael 是 Chintai 的核心后端开发者，在Chintai各平台开发过程中(订单撮合引擎，OTC市场，其他核心特性)起到了关键作用。\\n\\n### Andrew Coutts\\n\\nAndrew是全栈开发者，拥有为EOS社区构建工具的丰富经验，曾经创建了 RAM 交易工具 buyeosram 以及 EOS资源规划工具 eosrp.io。加入 Chintai 之前，他曾在应用程序性能管理(APM)行业工作了四年，担任应用程序监控专家。Andrew 对区块链和开源技术充满热情，希望通过更先进的工具和社区平台来帮助生态系统发展成熟，从而对EOS社区产生积极的影响。Andrew 负责 Chintai 的前端UI开发工作。\\n\\n### Sean Kang\\n\\nSean 主要负责韩国社区的社区关系与BD工作。他在银行，金融和城市工程等领域有超过十年的经验。他曾在加拿大最大的银行担任客户经理，在韩国和加拿大经营各种业务。在攻读智慧城市发展城市规划博士学位时，Sean 发现了 EOS。他设想，借助于可扩展性的区块链技术，智能城市会为我们的生活带来深刻影响。结合他作为城市规划师的聆听、理解和执行社区需求的能力，以及他多元的文化背景，Sean能够为 EOS 社区提供全面的解决方案。\\n\\n### 荆凯(Kai Jing)\\n\\n技术作者，程序员和产品经理。毕业于华南理工大学，有着化学工程的背景和多年电子商务行业的从业经历，目前主要负责 Chintai 的中国社区工作。在认识到了区块链的潜力、尤其是EOS的潜力之后，荆凯被其魅力所吸引，而走入了区块链行业和EOS社区。他坚信，EOS具有将区块链技术引入日常生活大规模应用的潜力。决定将自己更多的时间投入到学习和帮助人们了解 EOS 上，通过币乎等平台，写作和翻译了许多关于 EOS 的文章，是 EOSIO 技术白皮书第二版的译者之一。\\n\\n### Ryan Bethem\\n\\nRyan 热衷于与社会正义和经济平等相关的草根运动。在进入区块链行业之前，他是旧金山的一名心理学家，专攻复杂创伤的精神分析治疗和团体治疗。借助于他在群体动力学、公共关系、政治和哲学等领域的心理学背景，他为EOS生态系统的发展提供了独特的视角。他希望EOS能够重新定义社区管理方式，以扩大个人自主权，提高生活质量的标准，并让人们摆脱第三方的剥削。Ryan 是 Chintai 的产品经理，负责市场营销、公关与社区工作。\\n\\n### Liam Wu \\n\\nLiam 负责 Chintai 的商业分析等工作，在促成战略合作、促进社区发展等方面，起到了关键作用。Liam 在过去20年里在三个大洲生活过，能够说流利的英语、西班牙语和汉语(普通话和广东话)。他的多元化成长经历，使他能够以独特的文化视角来看待区块链行业。Liam 对文化多样性的认识，对如何培育社区的直觉，以及对社区参与的内在理解，使他能够参与主导 EOS911 这样的项目。他对区块链技术非常着迷，并计划将他年轻的精力投入到促进区块链技术大规模应用的实践之中，同时为EOS社区面临的问题开发解决方案。\\n\\n## 相关链接\\n\\nChintai 网站 & CHEX 代币 [Chintai.io](http://chintai.io)\\n\\nChintai 1.0 交易平台\\n\\n[Chintai 1.0](https://eos.chintai.io/exchange/EOS7D)\\n\\n自动资源管理: [https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4](https://medium.com/@ChintaiEOS/resource-management-solved-1caecbee00c4)\\n\\n\",\"type\":\"referendum-v1\",\"incentives\":\"1000000.0000\",\"receiptor\":\"eos42freedom\"}", + "created_at": "2019-05-29T01:41:59" + }, + "stats": { + "votes": { + "1": 28, + "total": 28, + "proxies": 8, + "accounts": 20 + }, + "accounts": { + "0": 0, + "1": 25763075329, + "total": 25763075329 + }, + "proxies": { + "0": 0, + "1": 61407733123, + "total": 61407733123 + }, + "staked": { + "0": 0, + "1": 87170808452, + "total": 87170808452 + }, + "block_num": 43385214 + } + }, + "constantstab": { + "id": "constantstab_20190524", + "proposal": { + "proposal_name": "constantstab", + "proposer": "orbiter.moon", + "title": "Constant  —  a BOS Stablecoin", + "proposal_json": "{\"content\":\"## Brief\\nWe present a proposal for a highly liquid, USD-pegged stablecoin system based on Dan Larimer’s “PEX” spec. This system leverages the Bancor algorithm, a price feed oracle, and incentivized liquidity providers to create a robust framework for issuing and maintaining decentralized stablecoins on a blockchain.\\n\\nThis protocol will exist as a set of smart contracts, meaning that it will be decentralized, censorship-resistant, transparent, and auditable. Many dApps and services will be able to take advantage of a native stablecoin for various use cases, so this project will serve as a public good that can be leveraged by any project on the chain. We believe that the existence of a stablecoin on the BOS network will enable new use cases for dApps and will increase the value of the network.\\n\\n\\n## Motivation\\nStablecoins are blockchain-based tokens that have many of the useful properties of decentralized cryptocurrencies, but are also price-stable. Stablecoins are a foundational piece of infrastructure for every smart contract platform. While centralized, custodian-based stablecoins like Tether have proven to be relatively successful, they suffer from a number of issues as the result of their centralized architecture. In order for dApps and smart contract platforms to reach their full potential, they must have native stablecoins that are decentralized.\\n\\nWe plan to build a protocol for an EOSIO-native decentralized stablecoin that is based on a novel new design . This design was created by Dan Larimer, the creator of EOSIO and also the first person to build a decentralized stablecoin (bitUSD). As the creator of the world’s first decentralized stablecoin, Dan is among the most experienced innovators in this area. He has drawn upon his previous experience building bitUSD, as well as lessons learned from observing Dai, Steem Dollars, and other stablecoin projects, to create a new type of stablecoin system that directly addresses many of the issues proposed by previous iterations.\\n\\nNot all stablecoins are created equal. The first generation of decentralized stablecoins (bitUSD, Dai, etc) are based on an innovative but limited model. Collateral is deposited in a smart contract that creates the stablecoins, which represent a debt to the smart contract. This model maintains a robust peg, but it often runs into difficult issues at scale, as we’ve seen with both bitUSD and Dai. bitUSD has encountered issues around liquidity and ultimately failed to maintain its peg for a significant period of time. Dai has had issues around balancing supply and demand, and the team has had to resort to raising the interest rates on smart contract loans significantly. Dan’s new model follows a slightly similar model but makes important changes to increase stablecoin liquidity, lower the probability of a black swan event, and incentivize users to provide collateral to the system without charging excessive rates.\\n\\n\\n## Oracles\\nOracles are one of the most important aspects of any stablecoin protocol. In order to accurately gauge the price of the collateral, the ratio of collateral to debt, and the price of the pegged asset, stablecoin protocols need to integrate price information from the outside world. This is done through an oracle, which is any system for gathering off-chain data that feeds onto the blockchain.\\n\\nBecause oracles are such an integral piece of infrastructure for stablecoin projects, they are often the most vulnerable part of any system. In order for a decentralized stablecoin protocol to be successful, it must have a robust oracle system in place. Part of our work will be exploring various oracle systems in order to integrate the most robust, decentralized, and manipulation-resistant system possible. We will draw on existing work, such as the BOS oracle contract and the Delphi Oracle by EOS Titan.\\n\\n\\n## Execution Plan + Milestones\\n- Phase 1: Basic Build (5 Weeks Total)\\n - Basic Contracts (4 weeks)\\n - Oracle System (1 week)\\n- Phase 2: Testing and Deployment (5 Weeks Total)\\n - Review, Testing, Documentation, and Bug Fixes (2 weeks)\\n - User Interface Buildout (2 weeks)\\n - Mainnet Deployment (1 week)\\n\\n\\n## Budget and Fund Release Plan\\nBudget: 350,000 BOS\\n\\nWe propose a fund release plan based on major project milestones. This gives strong motivation to us as project creators and also provides strong guarantees to the grant administrators. We believe that we can complete this project in 2.5 months, and we request 350,000 BOS upon completion.\\n\\nWe believe that this project can bring very large amounts of value to the EOSIO ecosystem and to BOS specifically.\\n\\nWe plan to have 2 C++ developers to develop the contracts and 1 product manager that will test, document and organize the project for approximately 2.5 months duration. We will also have an external audit of the code done before mainnet deployment. The funds will primarily be used for development and product.\\n\\n\\n## Team\\nOrbiter Solutions offers full-service development and consulting for EOSIO-based software. Our leadership team consists of César Rodríguez and Myles Snider. César is a full-stack blockchain engineer with vast experience in EOSIO. He built the first block explorer and web wallet for the EOS mainnet, created Nebula Protocol, and has done extensive work with testing and auditing code for EOSIO projects. Myles hails from a finance and research background, leading research at Multicoin Capital before founding Aurora EOS, a mainnet block producer. He also created The Stablecoin Index and has consulted with a number of projects in the stablecoin space. He is widely recognized as a leading expert in the stablecoin field.\\n\\nOrbiter Solutions brings to the table a perfect combination of experience in stablecoins and EOSIO, putting us in a unique position to successfully deliver a project like this. Stablecoins are complicated financial instruments. To successfully build a product like this requires not just a deep understanding of blockchain software and smart contracts, but also expertise in the specific financial, economic, and game theoretic factors that can make or break a stablecoin. Our background and experience uniquely position us to take advantage of this opportunity.\\n\\nMore info: https://medium.com/@orbitersolutions/orbiter-solutions-bos-proposal-constant-an-eosio-stablecoin-d62dbbf8660e\\n\\n\\n## Relevant Links\\nhttps://github.com/bytemaster/pex\\n\\nhttps://hackernoon.com/how-liquid-tokens-work-a4ba30f2482b\\n\\nhttps://hackernoon.com/how-bancor-relays-work-c712a374374f\\n\\nhttps://stablecoinindex.com/\\n\\nhttps://multicoin.capital/2018/01/17/an-overview-of-stablecoins/\\n\\nhttps://messari.io/resource/stablecoins\\n\\nhttps://hackernoon.com/stablecoins-designing-a-price-stable-cryptocurrency-6bf24e2689e5\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-24T16:15:48" + }, + "stats": { + "votes": { + "1": 10, + "total": 10, + "proxies": 2, + "accounts": 8 + }, + "accounts": { + "0": 0, + "1": 1962415, + "total": 1962415 + }, + "proxies": { + "0": 0, + "1": 3100808317, + "total": 3100808317 + }, + "staked": { + "0": 0, + "1": 3102770732, + "total": 3102770732 + }, + "block_num": 43385214 + } + }, + "dappxlinkeco": { + "id": "dappxlinkeco_20190627", + "proposal": { + "proposal_name": "dappxlinkeco", + "proposer": "dappxlinkbos", + "title": "DappLinks Ecosystem Empowerment Platform; DappLinks生态赋能平台", + "proposal_json": "{\"content\":\"### Content\\n\\nProposal Background Proposal Introduction Application Scenarios Technical Strengthens Proposal Implementation Proposal Objective Proposal Budget \\n\\n## 1. Proposal Background\\n\\nAfter Ethereum Blockchain was established, decentralized applications (DApp) move from ideas to the reality. However, due to the TPS (transaction per second) restrictions on the Ethereum blockchain infrastructure, DApp cannot be used in the large-scale business applications. In 2018, EOS blockchain mainnet was launched, and the DApp ecosystem based on EOS network is booming because of better technical performance than Ethereum. In 2019, the dencentralized cross-chain technology is realized based on the BOSCore side chain of EOSIO, which facilitates the development of EOSIO ecosystem; Meanwhile, some other excellent public chain projects like IOST, ELF, ZIL, etc. are also showing up in the market, which makes the DApp ecosystem have substantial development. \\n\\n## 2. Proposal Introduction\\n\\nRight now, there is tough competition in the DApp market, and users still have some problem when they are using DApp. For example, it is still difficult to access the DApps, and also hard to quantify the promotion effects and deliver the ads accurately. Opaque smart contract, repeated development of different public chains, and other issues make DApp market undertake lots of pain points which are required to be solved urgently. \\n\\nThe establishment of DAppLinks, the decentralized empowerment platform which supports DApps built on different chains, is based on the cross-chain smart contract technology, which combines DAppLinks SDK, DApp Browser and decentralized wallet to empower different traffic channels and developers. It solves the long-term issues in the DApp market with the help of distribution technology in the traditional Internet industry and “transparent”, “immutable”, and “traceable” features in the blockchain technology, which will definitely disrupt the DApp market. \\n\\n## 3. DAppLinks will make the following disruptive changes\\n\\n#### 3.1 Smooth user experience\\n\\nThe mission of DAppLinks is to provide a more flat distribution mode for the DApp market by connecting various resources. In order to reduce the work load for DApp developers to integrate so many decentralized wallets, DAppLinks platform will connect the wallets itself so that DApp developers can integrate the decentralized wallets easily with the DAppLinks SDK. Thus, users don’t need to import the private key repeatedly any more. \\n\\n#### 3.2 OnePush channel promotion empowerment\\n\\nThe channels can provide their users with one-stop DApp experience with the self-developed DAppLinks SDK and DApp Explorer, which means the users can manage their wallets with authorized 3rd party private keys to integrate and use DApp in the website or App from the channel side. It makes the channels earn more promotion income, and realize the mode that CPS, CPA and DApp developers can make long term win-win collaboration. Meanwhile, the channels can also bring better blockchain experience to their users, and improve the application scenarios in the website or App, which is helpful to increase the user satisfaction and stickiness and finally brings more income to the channels. \\n\\n#### 3.3 Accurate traffic distribution\\n\\nDAppLinks not only provides better user experience and convenient channel distribution to the DApp ecosystem, but also realizes industry upgrade with technical improvement, which connects the centralized account system in the channel side and decentralized wallet system in the DApp which are incompatible originally. After solving the data island, we can create more value with user data on the premise that the user privacy is protected. \\n\\n#### 3.4 Efficient multi-chain payment solution\\n\\nThrough integrating the DAppLinks SDK, DApp developers will not need to worry about the complicated blockchain infrastructure technology, but concentrate on the application development and optimization. DApp developers can publish the application to different public chains easily via the DAppLinks SDK. Thus, the developing cost could be much less at the beginning, and the DApp publication efficiency will be greatly improved. Finally, users will enjoy better interactive experience and would like to stay in the DApp ecosystem. \\n\\nDAppLinks will provide abundant application scenarios:\\n\\n## 4. Application Scenarios\\n\\n#### 4.1 Cryptocurrency Exchange\\n\\nExchange users can experience the DApp easily and conveniently without leaving the exchange environment via DAppLinks to understand user experience and product updates. Since it is a mess in the blockchain industry, it will be very helpful for users to understand and evaluate the future value of the tokens they have invested or planned to invest with the DApp experience. Meanwhile, exchanges which provide this experience to their users will also get honest feedback from them, and more information can facilitate users to exchange on the platform, which will bring the exchanges more commission. \\n\\n#### 4.2 Blockchain Media\\n\\nDAppLinks empowers the blockchain medias to run the business for existing market. Through connection with DAppLinks, blockchain medias can have access to the one-stop DApp promotion and distribution. The medias with high user stickiness can continuously share the benefits from the development of excellent DApp. With the promotion of the blockchain medias, more and more Internet users start to understand and accept blockchain concept, but due to the difficult access of DApp, there is still some pain point that lots of people pay attention, but very low conversion rate. DAppLinks distribution platform solution will increase DApp conversion rate by largely reducing the threshold to use the DApp. \\n\\n#### 4.3 DApp Store\\n\\nAs a carrier of information generation in the DApp, DApp store naturally undertakes the tasks to DApp distribution and promotion. Due to the blockchan technical restrictions, DApp store has the same format with centralized Internet product for better user experience. Through integration with DAppLinks, DApp store will become the entrance for users to enjoy convenient experience, especially now most of the DApp can be shown as Web front-end form.\\n\\n**DAppLinks ecosystem empowers technical advantages:**\\n\\nDAppLinks chooses BOS as the infrastructure development platform, and it will provide sharding management based on EOSIO. Users can use different network shards and discard other useless information in the nodes. Even though the information is a mess on the overall network, the design convenience allows blockchain applications to spread information in an orderly manner. WebAssembly is applied rather than Solidity to guarantee the compatibility with C ++ programming. In addition, DAppLinks will confirm the synchronized timestamp with access control for all the nodes in the EOSIO network. DAppLinks will confirm control message and history blogs can be spread out instantly in case of emergency.\\n\\nDAppLinks control information load and disassembly via network stratification, and it means to complete send or report, pack and unpack, which will be finished by different hardware and software. \\n\\nThe technical difficulties of DAppLinks are the private key management solution for DApp integration, the authorization management from DAppLinks platform to external platforms, and the reform of the existing technical solution. \\n\\n## 5. Proposal Implementation\\n\\nTotal 1 million BOS will be the incentive which is exclusive for BOSCore chain to conduct long-term development and maintenance. This proposal is only to apply for the first phase BOS funding. \\n\\n#### 5.1 Phase 1: 360,000 BOS\\n\\nComplete the BOSCore chain development and integrate with at least two of DAPPX, unico.one, 8BTC, JINSE Meida, Bishijie, Bihu, Biyong, PPS and Youku to start comprehensive ecosystem cooperation. \\n\\n| Costs | Budget/BOS |\\n| ------------------------------------------ | ---------- |\\n| Product Development | 120,000 |\\n| DevOps | 5,000 |\\n| Channel Promotion and Business Cooperation | 180,000 |\\n| Community Operations | 450,000 |\\n| Miscellaneous | 10,000 |\\n\\n#### 5.2 Phase 2 (Expect higher Channel and Business Cooperation Cost)\\n\\nCollaborate with blockchain media as BOSCore ecosystem browser solution and integrate with the top blockchain media, like 8btc, JINSE Media, Bishijie, Bihu, Biyong, bee and so on. Develop the cooperation with the rest platforms in Phase 2 according to the progress in Phase 1. \\n\\n## 6. Summary\\n\\n#### 6.1 Great business value\\n\\n**DappLinks will work together with top public chains, media and DApp community in the blockchain industry,**which will share the traffic of tens of millions of users to guarantee the stable growth of BOS expanding channels and application.\\n\\n#### 6.2 Proposal Objective\\n\\nExpand more channels for BOS application, and enhance the scenarios for BOS circulation.\\n\\n#### 6.3 Proposal period and budget\\n\\nPhase 1: Development period is 2 months, from 20th-April, 2019 to 20th-June, 2019, amount is 360,000 BOS, which is used for BOS development and integration, and connection with the selected projects;\\n\\nPhase 2: Development period is not confirmed yet, amount is not confirmed yet as well, which is used to connect with the rest projects and maintenance.\\n\\n# DappLinks 生态赋能平台\\n\\n### 目录\\n\\n提案背景 提案介绍 应用场景 技术优势 提案执行 提案目标 提案预算\\n\\n## 1.提案背景\\n\\n自以太坊问世后，去中心化应用DApp因智能合约从构想走进现实。然而，受限于以太坊POW共识的交易频次，DApp在以太坊上无法大规模商用。2018年中EOS公链的上线，各方面优于以太坊的EOS让在EOS上的DApp生态蓬勃发展；2019年基于EOSIO的BOSCore侧链上线，实现了去中心化的跨链，很好的促进了EOSIO生态的发展；IOST、ELF、ZIL等优秀共链也进入市场，让整个DApp生态有了更长足的发展。\\n\\n### 2. 提案介绍\\n\\n支持多链的去中心化应用赋能平台DAppLinks的诞生，是基于跨多链区块链智能合约技术的基础上，利用DAppLinks SDK及DApp 浏览器与去中心化钱包相结合，赋能各流量渠道与开发者，通过将互联网技术与区块链技术结合，利用传统互联网渠道分发的技术以及区块链“透明化”、“不可篡改”和“可追溯性”的特点将有效解决长期困扰DApp市场的问题，将为DApp市场带来颠覆性改变。\\n\\n如今，Dapp市场竞争激烈，用户在使用Dapp上依然存在一些问题。例如，用户获取门槛高，难以量化推广效果和精准投放、合约不透明、多公链重复开发等问题，让Dapp市场痛点明显，亟待解决。\\n\\n## 3. DAppLinks将做以下颠覆性改变\\n\\n#### 3.1 流畅的用户体验\\n\\nDAppLinks诞生的使命便是通过链接各方资源为DApp市场提供更扁平的分发方式。为了减少DApp开发者对接诸多去中心化钱包的工作，DAppLinks将以平台的方式完成与各主流去中心化钱包的对接工作，使得DApp开发者在推广时只需要与DAppLinks SDK进行对接便可一站式集成市面上主流的去中心化数字钱包，从而为用户提供DApp内无需重复导入私钥的使用体验。\\n\\n#### 3.2 一键式的渠道推广赋能\\n\\n通过使用自主研发的DAppLinks SDK与DApp浏览器为渠道方赋能，使得渠道方可以为其用户提供一站式的DApp体验服务，即用户可以通过授权第三方私钥管理的去中心化钱包，在渠道方的网站或App内无缝接入DApp并使用。这使得渠道方可以获得更多的DApp推广收入，并真正实现CPS、CPA等与DApp开发者实现长期合作共赢的推广模式。同时，渠道方为其用户带去了更多区块链应用的真实便捷的体验，丰富了用户在渠道方网站或应用内的使用场景，这也将有助于渠道方提升自由用户的满意度和粘性。最终为渠道方带去更多的收入。\\n\\n#### 3.3 精准的流量分发\\n\\nDAppLinks对DApp生态的链接不仅带来用户体验的提升和渠道投放的便捷性，更通过技术改造实现行业升级，将原本无法兼容的渠道中心化账户体系与DApp的去中心化账户体系链接起来。打通数据孤岛后，我们可以将在保护用户隐私的前提下利用用户数据为行业创造更大的价值。\\n\\n#### 3.4 高效的多公链交付方案\\n\\n通过集成DAppLinks SDK，DApp开发者可以不再关心复杂的公链底层技术，只需要聚焦于应用本身的开发与优化。通过DAppLinks SDK，DApp开发者在完成应用开发后可以一键将其发布在各主流公链之上。由此DApp开发者的早期开发成本可被大大降低，同时DApp生态的发行效率也将被大大提升，最终受益的终端用户在感受到由此带来的良好交互体验后将更愿意留在DApp生态中。\\n\\n## 4. 应用场景\\n\\n**DAppLinks将提供丰富的场景应用**\\n\\n#### 4.1. 加密货币交易所\\n\\n通过DAppLinks，交易所用户可以不离开交易所环境便快捷地体验承载某加密货币的DApp，了解其用户体验和更新迭代情况。由于现在区块链行业鱼龙混杂，相信对DApp的真实体验效果将帮助用户非常好得了解和判断所投资或计划投资的加密货币的未来价值。同时，为用户提供了这种增值服务的交易所也将获得用户更多的忠诚度回馈，并且更多的信息将促进用户交易从而获得更多交易佣金。\\n\\n#### 4.2 区块链媒体\\n\\nDAppLinks的出现为区块链媒体经营存量 市场进行了赋能。通过与DAppLinks的对接，区块链媒体可一站式获得DApp推广运营分发的 红利。用户粘性高的区块链媒体更可以持续分享优质DApp的发展红利。在区块链媒体的努力普及下，越来越的普通互联网用户开始了解和接受区块链的理念，然而由于DApp的高使用门槛，始终存在着高关注低转化的痛点。DAppLinks的分发平台方案将通过大幅降低用户使用门槛而提升DApp用户转化率。\\n\\n#### 4.3 DApp应用商店\\n\\n作为DApp信息聚合的载体，DApp应用商店天然承担着应用分发和推广的责任。由于区块链存储技术的瓶颈，为了换取更好的用户体验，DApp应用商店现在的主流是中心化的互联网产品形态。通过与DAppLinks的集成，DApp应用商店可以成为用户非常便捷的体验和使用DApp的入口，尤其是在大多数DApp都能以web前端形式呈现的当下。\\n\\n**DAppLinks生态赋能平台技术优势**\\n\\nDAppLinks选择BOS作为DAppLinks底层链开发平台，基于EOSIO上开发DAppLinks将提供分片管理，用户可以使用不同的网络分区，并抛弃节点上的其他无用信息；即使整个网络上的信息繁杂，但设计上的便利性让区块链应用程序的信息能够有序传播；DAppLinks采用更智能方式来向用户收取费用，相比传统收费方式更加合理智能；使用WebAssembly而不是Solidity来确保C ++工具链的兼容性。除此之外，DAppLinks还将确认EOSIO网络所有节点的访问控制同步的时间戳。 DAppLinks会确认控制消息和历史日志在紧急情况下得以实时传播。\\n\\nDAppLinks通过网络分层就是将网络节点所要完成的数据的发送或转发、打包或拆包，控制信息的加载或拆出等工作，分别由不同的硬件和软件模块去完成。\\n\\nDAppLinks的技术实现难点在于DApp连接私钥管理的方案，从自身平台管理扩展到外部平台授权管理，对现有的技术方案进行底层改造。\\n\\n## 5. 提案执行\\n\\n用总共100万BOS为激励，专属对接BOSCore链，进行长期的开发和维护。**本次提案仅申请第一期BOS基金。**\\n\\n#### 5.1 第一期：36万BOS\\n\\n完成BOSCore链开发接入，至少接入DAPPX、unico.one、巴比特、金色财经、币世界、币乎、币用、PPS、优酷的其中两家，全面进行生态合作。\\n\\n| 支出项 | 预算/BOS |\\n| ------------------ | -------- |\\n| 产品研发投入 | 12万 |\\n| 后期运维 | 0.5万 |\\n| 渠道推广和商务合作 | 18万 |\\n| 社群运营 | 4.5万 |\\n| 其他开销 | 1万 |\\n\\n#### 5.2 第二期 (预期会有更多的渠道推广和商务合作费用)\\n\\n作为BOSCore生态浏览器解决方案与区块链行业媒体合作，接入区块链行业头部流量媒体，如8btc、金色财经、币世界、币乎、币用、bee币360等。根据项目第一期发展进度，第二期继续衔接拓展剩余的平台进行合作。\\n\\n## 6. 总结\\n\\n#### 6.1 商业价值巨大\\n\\n以上头部媒体流量资源充沛，每家媒体用户均在80万人以上，日均UV（独立访客）就高达50万左右，高峰时能达到100万，覆盖超过90%的区块链爱好者及加密货币用户日常媒介圈层。\\n\\n**DappLinks均与区块链行业头部公链、媒体、Dapp社区**合作，将获得千万级用户的流量共享权利，能有效保证BOS拓展渠道和流通使用的稳定增长。\\n\\n目前为止，以上合作方均已进入长期稳定的合作阶段。\\n\\n#### 6.2 提案目标\\n\\n拓展BOS的使用渠道，增强BOS的流通场景。\\n\\n#### 6.3 提案周期预算\\n\\n第一期：开发周期约2月，2019年4月20日-6月20日，金额36万BOS，用于BOS开发接入，以及前期优选项目对接；\\n\\n第二期：开发周期待定，金额待定，用于剩余优选项目的对接与维护。\",\"type\":\"referendum-v1\",\"incentives\":\"360000.0000 BOS\",\"receiptor\":\"dappxlinkbos\"}", + "created_at": "2019-06-27T15:00:38" + }, + "stats": { + "votes": { + "1": 14, + "total": 14, + "proxies": 10, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 231353792, + "total": 231353792 + }, + "proxies": { + "0": 0, + "1": 54800610003, + "total": 54800610003 + }, + "staked": { + "0": 0, + "1": 55031963795, + "total": 55031963795 + }, + "block_num": 43385214 + } + }, + "dcartmarket1": { + "id": "dcartmarket1_20190818", + "proposal": { + "proposal_name": "dcartmarket1", + "proposer": "qibdezknfhnh", + "title": "DCart - Digital Asset Marketplace", + "proposal_json": "{\"content\":\"Integrate DCart.io Digital asset marketplace with BOS blockchain. DCart is a digital asset marketplace where users can trade gaming items, digital art or any digital items. DCart also provides a portal where users can easily convert digital items to NFTs on BOS blockahin and start trading DCart. DCart is currently live on EOS,Wax and worbli chains. We would like to extend the functionality and support to BOS Chain.\",\"type\":\"referendum-v1\",\"incentives\":\"60000.0000 BOS\",\"receiptor\":\"qibdezknfhnh\"}", + "created_at": "2019-08-18T16:00:00" + }, + "stats": { + "votes": { + "1": 1, + "total": 1, + "proxies": 0, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43385214 + } + }, + "derupromises": { + "id": "derupromises_20190615", + "proposal": { + "proposal_name": "derupromises", + "proposer": "dancinglions", + "title": "DERU - Promises on the Blockchain. / 德鲁（DERU）——区块链的承诺。", + "proposal_json": "{\"content\":\"-----\nDERU - Promises on the Blockchain. / 德鲁（DERU）——区块链的承诺。\nderupromises\n387500\ndec, 2019\n-----\n\n\n# DERU - Promises on the Blockchain.\n*Secure your promise on the blockchain*\n\n## Mission\n\n**Improve Cooperation!**\n\n\n## What is Deru?\n\nDeru Truth Bonds allow users to lock away crypto currency as a guarantee against any promises or commitment. It have many use cases in many industries:\n\n* an escrow service between two parties.\n* any general promise to many people, with a financial penalty against breaking it\n* Reputation. For example, a news organization making a promise that there will be no factual errors in their reporting.\n* A Letter of Credit in international trade.\n* In the BOS eco-system, Deru can even work as a guarantee of Block Producer performance.\n\nA Key to success is creating a useful, understandable, reliable product, then nurturing a community around it.\n\n\n\n## Who Judges Promises?\n\nDeru 2.0 will allow anyone to register as an arbitrator AND specify the fee they will charge for arbitrating cases. To be successful, Deru needs to economically incentivize a community of arbitrators.\n\nDeru 2.0 will be designed around the needs of a community of judges. Only when good people have economic incentive to evaluate promises will Deru be a success.\n\n\n\nWhite Paper for Deru 0.9: http://deru.io/wp-content/uploads/2019/05/Deru-WhitePaper-0.9.pdf\n\n\n## VOCABULARY\n\n*Promiser* - The party making a commitment and creating a bond.\n\n*Promise* - The guarantee made by the promiser.\n\n*Bond* - A commitment secured by some amount of crypto currency.\n\n*Period* - The time period during which the promiser pledges to abide by their promise.\n\n*Grace Period* - An additional period of time immediately after the period during which claims can still be made. (This is necessary to mitigate last-second violations of a promise.)\n\n*Claim* - An appeal made against a promise claiming it was violated.\n\n*Claimant* - The party making a claim.\n\n*Award* - The portion of a bond awarded to a claimant when an arbitrator deems the claim valid.\n\n*Standing* - The set of parties (EOS Accounts) able to make claims against a promise. (The initial version of Deru Truth Bonds allow these options: all EOS account holders, specific accounts, users who meet a description -- e.g. my customers.)\n\n*Benefactor* - The person or party receiving the funds from a bond after a successful claim. (You can specify the claimant, specific account(s), or burning tokens.)\n\n*Arbitrator* - A person who assesses claims. (*Oracle* was proposed as an alternative term.)\n\n*Arbitrator Forum* - In later versions, promisers will be able to choose arbitrator forums instead of individual arbitrators. Also, groups of arbitrators will be able to register as a forum to consolidate their reputations.\n\n*Appeal* - Future versions of Deru Truth Bonds may allow a two-step arbitration process where either the claimant or the promiser has some recourse to appeal decisions which they consider unfair. (As an alternative to an explicit appeal process, a similar thing may be achieved by requiring arbitrators to postbonds which promise that they are decisions will not be deemed flawed by some third party oversight board.)\n\n\n\n## Road Map\n\n\n![Deru Roadmap English](https://cryptolions.io/wp-content/uploads/2019/06/bos-deru-roadmap-en.png)\n\n\n## Funding\n\n| **Task** | **est. hours** | **BOS** |\n| ------------------------------ |:-------------:| ----- |\n| Deru 2.0 (beta) | 300 | 187500 |\n| Community Engagement / Finalize Design / Integrations | 240 | 150000 |\n| Official Launch / Marketing | 80 | 50000 |\n| **Total:** | | 387,500 |\n\n\n\n## Contact:\n\n\nEmail:\nroman@cryptolions.io\nshe@cryptolions.io\n\nTelegram: \nhttps://t.me/CryptoLions_io\nhttps://t.me/DeruTruthBonds\n\nWeChat: SHE18347264709\n\n\nInformation:\n\nhttp://deru.io/\n\n\n==========\n\n# 德鲁（DERU）——区块链的承诺。\n\n\n*基于区块链之上确保您的承诺*\n\n## 任务\n\n**改善合作！**\n\n\n## 什么是德鲁（DERU）？\n\n德鲁信用债券（Deru Truth Bonds）允许用户锁定加密货币作为对任何承诺或约定的担保。\n它在许多行业中有许多例子：\n\n用来抓住某人或某物囚犯的身体束缚，特别是绳索或链条。\n\n特别是与法律力量的协议。\n\n\n* 双方之间的托管服务。\n\n* 对许多人而言的任何一般承诺，以及违反它的经济处罚\n* 声誉。例如，新闻机构承诺在报告中不会出现任何实际错误。\n\n* 国际贸易中的“信用证”。\n\n* 在BOS生态系统中，德鲁（Deru）甚至可以作为节点性能的保证。\n\n成功的关键是创造一个有用的、可理解的、可靠的产品，然后建立一个基于它的社区生态。\n\n\n## 谁评判承诺？\n\n德鲁2.0（Deru 2.0）将允许任何人注册成为仲裁员并指定他们将对仲裁案件所收取的费用。为了取得成功，德鲁（Deru）需要以经济方式激励社区仲裁员。\n\n\n德鲁2.0（Deru 2.0）将围绕评判社区的需求而设计。只有当优秀的人有经济激励时来评判承诺时，德鲁（Deru）才能获得成功。\n\n\n德鲁0.9（Deru 0.9）白皮书：http：//deru.io/wp-content/uploads/2019/05/Deru-WhitePaper-0.9.pdf\n\n## 词汇\n\n*承诺人* - 作出承诺并建立联系的一方。\n\n\n*承诺* - 承诺人提供的保证。\n\n\n*债券* - 一个由一定数量的加密货币作为担保的承诺。\n\n\n*期限* - 承诺人承诺遵守承诺的时间段。\n\n\n*宽限期* - 在此期限之后的仍然可以提出索赔的一段时间。\n（这对于减轻最后一秒违反承诺是必要的。）\n\n*索赔* - 针对声称遭受违反承诺提出的上诉。\n\n\n*索赔人* - 提出索赔的一方。\n\n\n*奖励* - 当仲裁员认为索赔有效时，授予索赔人的债券部分。\n\n\n*常设* - 能够对承诺提出索赔的一组当事人（EOS账户）。 （德鲁信用债券（Deru Truth Bonds）的初始版本允许这些选项：所有EOS帐户持有者，特定帐户，符合描述的用户——例如“我的客户”。）\n\n*施惠者* - 成功申请后从债券获得资金的个人或一方。\n（您可以指定申请人，特定帐户或烧录代币。）\n\n*仲裁员* - 评估索赔的人。 （“Oracle”被提议作为替代术语。）\n\n*仲裁员论坛* -在以后的版本中，承诺者将能够选择仲裁员论坛而不是单独的仲裁员。此外，仲裁组将能够注册成为巩固其声誉的论坛。\n\n\n*上诉* - 德鲁信用债券（Deru Truth Bonds）的未来版本可能允许两步仲裁程序，其中索赔人或承诺人可以诉诸他们认为不公平的上诉决定。\n（作为明确上诉程序的替代方案，可以通过要求仲裁员进行后期债券来实现类似的事情，这些债券承诺他们的决定不会被某些第三方监督委员会视为有缺陷。）\n\n## 路线图\n\n\n![Deru Roadmap Chinese](https://cryptolions.io/wp-content/uploads/2019/06/bos-deru-roadmap-cn.png)\n\n\n\n## 基金\n\n| **任务** | **时间， 小时** | **BOS** |\n| ------------------------------ |:-------------:| ----- |\n| Deru 2.0（测试版） | 300 | 187500 |\n| 社区参与/完成设计/集成 | 240 | 150000 |\n| 官方发布/运营 | 80 | 50000 |\n| **总计：** | | 387,500 |\n\n\n\n## 联系方式:\n\n\nEmail: \nroman@cryptolions.io\nshe@cryptolions.io\n\nTelegram:\nhttps://t.me/CryptoLions_io\nhttps://t.me/DeruTruthBonds\n\nWeChat: SHE18347264709\n\ninfo: http://deru.io/\n\",\"type\":\"referendum-v1\",\"incentives\":\"387500.0000\",\"receiptor\":\"bosbornforbb\"}", + "created_at": "2019-06-15T13:55:54" + }, + "stats": { + "votes": { + "1": 8, + "total": 8, + "proxies": 4, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 2118381310, + "total": 2118381310 + }, + "proxies": { + "0": 0, + "1": 26161803840, + "total": 26161803840 + }, + "staked": { + "0": 0, + "1": 28280185150, + "total": 28280185150 + }, + "block_num": 43385214 + } + }, + "ecoboostwps1": { + "id": "ecoboostwps1_20190627", + "proposal": { + "proposal_name": "ecoboostwps1", + "proposer": "ecoboostwps1", + "title": "海角论坛：BOSCore生态最聚合的信息交流与资源整合平台", + "proposal_json": "{\"content\":\"## 提案背景：\\n\\n作为EOS的最强侧链BOSCore凭借IBC跨链转账和3秒LIB的特性以及数字资产自由港的愿景，在行业内已享有不小的知名度。但是BOSCore生态推广长久以来面临几个问题。\\n\\n一， 社区成员信息交流不顺畅，查找目标信息低效。由于社区成员所在社群过多，群内消息频刷、繁杂，导致社区成员错过重要信息或者无法及时快速找到自己想要的信息。\\n\\n二， 与BOSCore雷同或重名的项目容易误导社区成员。\\n\\n三， BOSCore链上的相关信息不够整合，分散于各处。\\n\\n \\n\\n## 提案目标：\\n\\n促进BOSCore生态繁荣，扩大BOSCore影响力。为BOSCore社区引入更多新成员，并为BOSCore社区成员和开发者提供交流与资源整合的平台。\\n\\n \\n\\n## 提案简介：\\n\\n海角论坛是一个为BOSCore社区成员提供的信息交流和资源整合的平台。它有效地解决了上述问题。\\n\\n \\n\\n海角论坛是web网页版。社区成员可以直接使用BOS账号进行登录，其他用户可以通过注册论坛获取一个BOS账号，从而扩大BOSCore生态的影响。\\n\\n \\n\\n海角论坛会发行10亿token,用于优质内容生产者激励。后期众多广告商会入驻平台，届时广告收入全部分发给平台token持有者，平台方分毫不取。\\n\\n \\n\\n海角论坛分为六大部分，分别是论坛、BOSCore英雄榜、新闻与快讯、BOSCore资源、DAPP展示、区块信息。\\n\\n \\n\\n##### 一、论坛：下设五个版块。\\n\\n每个板块都设置2到3个版块版主，版主拥有特殊标识与权限。版主有权根据帖子内容对帖子进行加精、置顶或者删除处理，方便社区成员高效便捷地查看信息。版主任期为一个月，可连任。所有社区成员都有资格竞争成为版主，共同参与论坛建设，繁荣BOSCore生态。\\n\\n \\n\\n第1个板块为科普专区。该区内有新手引导、区块链知识科普、EOS科普和BOSCore科普。有利于新手了解与学习。\\n\\n \\n\\n第2个板块为BOS币价交流专区。进入该专区，首先映入眼帘的是BOS币价的K线图，一目了然。下面是持币用户的吐槽交流区。持币用户可以根据帖子的标题轻松找到相同境遇或相同观点的其他持币用户，并与之交流。这种方式比社群刷屏信息交流更精准更高效。\\n\\n \\n\\n第3个版块为DAPP推荐与吐槽区。社区成员根据自己的使用体验给出BOSCore链上的DAPP评分和推荐理由。好评对DAPP开发者是一种激励，同时也能为该DAPP带来大量用户，而吐槽则有利于开发者精准地了解DAPP的不足之处，并据此进行迭代优化。该版块也为社区成员选择DAPP提供了很好的依据。\\n\\n \\n\\n第4个版块为开发者技术交流专区。现在大多数开发者的技术交流分享都比较分散。而该版块集合了BOSCore链上的开发者和有志于参与BOSCore的开发者，信息交流更具有针对性。\\n\\n \\n\\n第5个版块为建议和投诉专区。社区成员可以在此举报那些利用BOSCore之名行骗的个人或组织，或者列出与BOSCore高度类似的项目，帮助社区成员辨别，谨防上当受骗。从而净化BOSCore社区，进一步提升BOSCore品牌形象。社区成员还可以在此提出对BOSCore的改进建议。集思广益，BOSCore生态才能更加繁荣。凡举报属实或建议被采纳者都会得到平台token奖励。\\n\\n \\n\\n##### 二、BOSCore英雄榜：\\n\\n该部分主要是通过荣誉和奖励，提升社区成员和DAPP开发者的积极性。该部分以一个周和一个月为节点来评选出BOSCore链上最受欢迎的DAPP排行、论坛最活跃用户排行以及精华帖排行。排行前几位者都将有机会获得平台token奖励。\\n\\n \\n\\n##### 三、新闻与快讯：\\nBOSCore的最新动向都会第一时间发布于此，方便社区成员知晓，社区成员也可以在新闻下方进行评论，点赞和交流。\\n\\n \\n\\n##### 四、BOSCore资源：\\n该部分会接入支持BOS的钱包与交易所的API。\\n\\n \\n\\n##### 五、DAPP展示：\\n该部分展示BOSCore链上的所有DAPP信息。\\n\\n \\n\\n##### 六、区块信息：\\n该部分可查询BOSCore所有区块信息，包括区块高度、节点信息、内存信息、交易记录等，为BOSCore社区成员提供了更方便的区块查询入口。\\n\\n \\n\\n## 提案执行：\\n\\n开发共需要4个月。\\n\\n1. 产品及交互设计, 完成prototype2周\\n\\n2. 核心功能开发 完成poc 包括账号体系, 论坛交互, 资讯平台 4周\\n\\n3. 核心功能完善 多模块调试 4周\\n\\n4. 用户体验优化 2周\\n\\n5. 性能优化 2周\\n\\n6. beta测试 2周\\n\\n \\n\\n## 提案预算：\\n\\n共需要95万个BOS。其中开发需要60万个BOS，服务器费用为25万个BOS，而维护费用为10万个BOS。\",\"type\":\"referendum-v1\",\"incentives\":\"950000.0000 BOS\",\"receiptor\":\"ecoboost1111\"}", + "created_at": "2019-06-27T07:05:01" + }, + "stats": { + "votes": { + "0": 1, + "1": 34, + "total": 35, + "proxies": 15, + "accounts": 20 + }, + "accounts": { + "0": 2000, + "1": 59120124541, + "total": 59120126541 + }, + "proxies": { + "0": 0, + "1": 106244392381, + "total": 106244392381 + }, + "staked": { + "0": 2000, + "1": 165364516922, + "total": 165364518922 + }, + "block_num": 43385214 + } + }, + "engineertool": { + "id": "engineertool_20190527", + "proposal": { + "proposal_name": "engineertool", + "proposer": "maodaishanbs", + "title": "Wallet for engineers", + "proposal_json": "{\"content\":\"EOSIO released eosio-java, which supplied best practice for accessing EOS blockchain.\\nI wish to supply a wallet on it to aim on:\\n1. Supply special functions especially useful for developers. ex.\\n Contract browser, can search contracts and execute it.\\n Get available rpc nodes, history nodes, p2p nodes, and test speed.\\n etc. \\n2. Developers can reference to it to create their own wallets.Make it easier to join BOS.\\n3. Engineers can easily realize their own functions on it.\\n4. Engineers can easily use it to access to BOS (support most useful rpc interfaces), can get more detailed information than business wallets and can do more operations on it. It's for engineers!\\n5. At lease support BOS main net, BOS test net, EOS main net, EOS test net.\\n\\nTarget fund amount: 50000.0000 BOS\\nTarget develop time: 6 weeks.\\nThanks all!\\n\",\"type\":\"referendum-v1\",\"incentives\":\"50000.0000\",\"receiptor\":\"maodaishanbs\"}", + "created_at": "2019-05-27T03:23:03" + }, + "stats": { + "votes": { + "1": 2, + "255": 1, + "total": 3, + "proxies": 1, + "accounts": 2 + }, + "accounts": { + "0": 0, + "1": 412200, + "total": 412200 + }, + "proxies": { + "0": 0, + "1": 0, + "255": 1146991705, + "total": 1146991705 + }, + "staked": { + "0": 0, + "1": 412200, + "255": 1146991705, + "total": 1147403905 + }, + "block_num": 43385214 + } + }, + "eosiosg11112": { + "id": "eosiosg11112_20190606", + "proposal": { + "proposal_name": "eosiosg11112", + "proposer": "wuqcscxdaqhn", + "title": "BOS OTC SaaS Payment Platform update version", + "proposal_json": "{\"content\":\"# Proposal Background\\n\\nAt this moment, blockchain DApps are lack of convenient fiat exchange channels for their own tokens. \\n\\nUsers would have to go through several steps to get the tokens, \\n\\n1) Create an blockchain address, \\n\\n2) Register on an centralised exchange, and do KYC, \\n\\n3) Use OTC or Exchange Fiat Channel to deposit fund and purchase the DApp token, \\n\\n4) Transfer your token to your blockchain address and Login to DApp to use. \\n\\nThe whole process is tedious and it is not ideal for first time blockchain DApp users as the learning curve is too stiff. Therefore, it is not good for DApp promotion and user retain. \\n\\nIf BOSCore would like to facilitate better DApp ecosystem, an OTC SaaS payment platform should be established. The platform will use its own advantage of technology, to integrate various components into the system, and provides a simple OTC service for DApps and end users. This could largely reduce the friction of users to use DApps, creating a better support to project and end users.\\n\\n \\n\\n# Proposal Introduction\\n\\nBOS OTC SaaS payment platform, a solution we would like to propose to the BOSCore eco-fund team is to use code script to integrate an OTC service SDK in DApps. This platform could facilitate the end users to use 3rd party payment such as Alipay or Paypal to purchase tokens on BOSCore for immediate use or experience in DApps. \\n\\nTherefore, we would like to have a reliable team to build a secure, fast and convenient payment platform with at least 4 features of service such as \\n\\n1. OTC plug-in, \\n\\n2. Fiat exchange channels, \\n\\n3. Settlement centre and， \\n\\n4. Trading centre. \\n\\n![img](https://i.imgur.com/Q1SvbfR.png) \\n\\nFigure 1: OTC SaaS Payment Platform Design Proposal\\n\\n# Application Scenario\\n\\nUsers will scan QR code on posters to download DApp. After registration, they enter DApp for service or entertainment, when they want to purchase the tokens, a SDK interface will enable a 3rd party payment channel such as Alipay or Paypal for immediate swap.\\n\\n \\n\\n# Proposal Execution\\n\\nPhase 1: Feature and UX/UI Design, 4 weeks\\n\\nThis requires the team to design product interface.\\n\\nPhase 2: Alpha version development, 12 weeks\\n\\nThe team will develop all 4 modules of the platform and integrate it into an easy-to-use solution.\\n\\nPhase 3: Testing, Bug fix, 1 week\\n\\nPhase 4: Deployment and Launch, 1 week\\n\\nA final product with user guide for people to use\\n\\nTotal project length is 4.5 months.\\n\\n \\n\\n# Proposal Goal\\n\\nTo successful deliver a product of the OTC SaaS Service system.\\n\\n# Proposal Budget\\n\\nBudget: 1,000,000 BOS, including manpower and development cost.\\n\\n| Cost Centre | Budget/BOS |\\n| ------------------------ | ---------- |\\n| Manpower and Development | 500,000 |\\n| Maintenance | 100,000 |\\n| Business Development | 250,000 |\\n| Community | 100,000 |\\n| Miscellaneous | 50,000 |\\n\\n\\n\\n# 提案背景\\n\\n目前区块链项目缺乏方便使用的代币兑换渠道，在将通证经济模型带入DApp的过程中，用户的使用体验往往不佳。\\n\\n传统的区块链充值渠道一般需要经过以下几个步骤：\\n\\n1. 用户需要创建区块链账户。\\n\\n2. 注册交易所并完成KYC。\\n\\n3. 通过OTC充值交易所或者通过交易所的渠道出入金，然后兑换相应DApp代币。\\n\\n4. 提币到账户，再登录DApp中进行使用。过程繁琐，对很多首次接触区块链的用户来说，学习成本高，体验差。对DApp的推广和用户留存都不利。\\n\\nBOSCore 本身提出的口号是为DApp而生，而目前现有的工具和服务都不能够为DApp的推广带来便捷的使用场景。因此BOSCore急需一个OTC SaaS支付平台的解决方案，旨在利用已有的技术，开发OTC承兑服务的SDK，将代币的OTC服务直接嵌入到DApp内。方便用户在登录使用DApp的过程中，直接完成代币的购买。这一方案将极大的降低DApp的使用摩擦，为项目的推广和用户的留存创造良好的基础。\\n\\n \\n\\n# 提案介绍\\n\\nBOS OTC SaaS支付平台，采用代码集成的方式，将OTC端口做成SDK的形式，方便部署到DApp中，为落户BOSCore的DApp项目团队提供可靠的一站式BOSCore链上DApp代币的OTC承兑服务，技术方案需要搭建合理的技术架构支付平台，完成OTC/做市团队、支付平台、DApp三方之间，快速安全的信息传递和链接（图1）。\\n\\n支付平台内需要有至少以下4大块服务\\n\\n1. OTC接入平台\\n\\n2. 财务结算中心\\n\\n3. 交易中心\\n\\n4. 出入金平台\\n\\n才能最终达成用户使用第三方支付进行OTC代币兑换的效果。\\n\\n![img](https://i.imgur.com/Krx6MHx.png) \\n\\n图1: OTC SaaS支付平台架构设想\\n\\n# 应用场景\\n\\n用户在看到DApp上线的文案海报宣发后，扫描二维码，下载DApp，注册并进入应用，在需要充值代币时，DApp界面可以弹出支付二维码，让用户以支付宝或者Paypal的扫码支付形式，用法币直接兑换成DApp代币。充值确认秒级到账。用户随后马上开始体验DApp服务。\\n\\n \\n\\n# 提案执行\\n\\n阶段1: 完成功能设计和UX/UI设计，4星期\\n\\n阶段2: 完成Alpha版本的开发，12星期\\n\\n阶段3: 测试，Bug修复，4星期\\n\\n阶段4: 部署发布，2星期\\n\\n总计4个半月\\n\\n# 提案目标\\n\\n完成OTC SaaS支付平台项目的开发与部署。\\n\\n \\n\\n# 提案预算\\n\\n申请经费：总额100万BOS，包含团队的开支和开发的成本。\\n\\n \\n\\n| 时间点 | 提案通过 | 项目完成 |\\n| ----------- | -------- | -------- |\\n| 释放BOS金额 | 20万 | 80万 |\\n\\n 表1: BOS金额释放流程\\n\\n \\n\\n| 支出项 | 预算/BOS |\\n| ------------------ | -------- |\\n| 产品研发投入 | 50万 |\\n| 后期运维 | 10万 |\\n| 渠道推广和商务合作 | 25万 |\\n| 社群运营 | 10万 |\\n| 其他开销 | 5万 |\",\"type\":\"referendum-v1\",\"incentives\":\"1000000.0000\",\"receiptor\":\"bosotcsaving\"}", + "created_at": "2019-06-06T07:31:45" + }, + "stats": { + "votes": { + "1": 12, + "total": 12, + "proxies": 9, + "accounts": 3 + }, + "accounts": { + "0": 0, + "1": 217424843, + "total": 217424843 + }, + "proxies": { + "0": 0, + "1": 34507804731, + "total": 34507804731 + }, + "staked": { + "0": 0, + "1": 34725229574, + "total": 34725229574 + }, + "block_num": 43385214 + } + }, + "eosstudioide": { + "id": "eosstudioide_20190619", + "proposal": { + "proposal_name": "eosstudioide", + "proposer": "eosstudiosam", + "title": "EOS Studio on BOSCore: Graphical IDE for dApp development", + "proposal_json": "{\"content\":\"## Proposal Background\\n\\nWhen developing dApps on blockchains, many developers face the problem that they have to learn numerous tools, manage them separately, and operate them on the command line. Our goal is to build an IDE (integrated development environment) and bring those tools together in a graphical interface as a single application. We released EOS Studio for EOSIO mainnet in February 2019 and since then we've attracted thousands of developers and received very positive feedbacks. Many dApp development teams have already used EOS Studio as their standard tool for developing dApps. Meanwhile, EOS Studio was recommended by Daniel Larimer on Twitter and has been listed in Block.one's developer portal as the only IDE made by the community.\\n\\nBOS blockchain was born and designed for dApps and bringing benefits for dApp developers and users. Every developer needs a powerful and easy-to-use environment to build a project from end to end. An IDE for BOS would significantly help BOS developers when they are working with complex codes for smart contracts. We hope a BOS version of EOS Studio can help to attract and incubate more quality dApps on the BOS network. Moreover, we will keep going further to release new features such as a web IDE for BOS. The web IDE will further lower the barrier for dApp development and we hope to bring more developers to the BOS community. It is also a platform to share open sourced smart contracts (like GitHub) so that developers can learn from each other.\\n\\nOur team, Obsidian Labs, is a silicon valley based startup focused on blockchain technology. Our founders were YC alumni and have been working together on blockchain for more than two years. In 2018, our team won the 3rd place in EOS Global Hackathon in San Francisco.\\n\\n\\n## Proposal Introduction\\n\\nEOS Studio would provide a graphical integrated development environment (IDE) for developing decentralized applications (dApps) on the cross-platform blockchain networks. By integrating numerous tools into a graphical interface, we believe EOS Studio on BOSCore can help developers improve their efficiency substantially throughout the entire dApp development process. Key features of EOS Studio on BOSCore will include BOS Code Editor, Contract Inspector, Network Manager and many more: \\n\\n\\n### BOS Code Editor\\n\\n- Build dApps more easily and efficiently with a powerful GUI\\n- Highlight and autocomplete for BOS syntax\\n- Templates of BOS system contracts\\n- One click to build a BOS smart contract\\n- Show build errors inline\\n- Deploy to local, testnet, or BOS mainnet\\n\\n### Contract Inspector\\n\\n- Graphical interface to interact with BOS smart contracts\\n- Form generation from abi for action parameter inputs\\n- Modify authorizations for signing a transaction\\n- Visualize the database in tables\\n- Save execution parameters and results to “History”\\n- Save common used parameters to “Bookmarks”\\n\\n### Network Manager\\n\\n- Manage multiple versions of BOS main software and BOS compiler\\n- View logs for block production\\n- Advanced configuration for BOS node instance\\n- Switch between local environment, testnet or BOS mainnet\\n- Integrated tools such as faucet, keypair manager, memory manager, etc\\n\\nWith EOS Studio on BOSCore, developers can complete the entire dev process from local development, test and debug on testnet, and final deployment on BOS mainnet.\\n\\n\\n## Proposal Execution\\n\\n3-5 people from Obsidian Labs will move on to execute this project. In the future we will add 1-2 more to keep BOS Studio updated with latest features.\\n\\nStage 1: Develop the basic modules for EOS Studio on BOSCore, 6 weeks;\\n\\nStage 2: Release the beta version and collect feedbacks for optimizing EOS Studio on BOSCore, 2 weeks;\\n\\nStage 3: Final stability test and security test, 1 week;\\n\\nStage 4: Final release of EOS Studio on BOSCore, together with online tutorials and medium articles, 1 week.\\n\\n\\n## Proposal Goal\\n\\nIn general, our mission is to push forward the adoption of blockchain technology and offer services and products valuable for developers. BOS is a young and rapidly growing dApp blockchain and there are many demands to be tapped. Our first goal is to deliver a complete IDE for BOS, and we will keep making more tutorials and organizing workshops for the BOS community.\\n\\n\\n## Execution Team\\n\\n**Phil Li**, co-founder of Obsidian Labs, YC alumni, PhD from Massachusetts Institute of Technology, 3rd place of EOS Global Hackathon in San Francisco. Full stack developer with experience on mobile & web applications, blockchain and smart contract. Core developer of EOS Studio.\\n\\n**Sam Sun**, co-founder of Obsidian Labs, YC alumni, Master from Newcastle University. Organizer of EOSIO/BOS developer meetups and workshops in China, Korea, Singapore and the other regions in Asia.\\n\\n**Rose Ren**, co-founder of Obsidian Labs, Bachelor from University of Michigan, Ann Arbor. 3rd place of EOS Hackathon in San Francisco. Former PR & Marketing director at Nebulas. Former investment manager at Continue Capital and Danhua Captial.\\n\\n**Leon Liang**, frontend developer at EOS Studio.\\n\\n**Sabrina Zhang**, product manager at EOS Studio.\\n\\n\\n## Proposal Budget\\n\\n**500,000 BOS**, including manpower and development cost.\\n\\nStage 1: 300,000 BOS, including the manpower and development costs of 3-5 developers for EOS Studio on BOSCore;\\n\\nStage 2: 100,000 BOS, including the costs of 1-2 developers for supporting the latest product feature updates;\\n\\nStage 3: 100,000 BOS, including the costs of making Medium tutorials, YouTube videos, Workshops and Meetups for developers.\\n\\n\\n\\n## 提案背景\\n\\n对于 BOSCore 或是 EOSIO 这样“年轻“的公链来说，由于相应的开发工具并不完备，开发者需要花大量的时间去学习使用各种相关组件，单独管理这些组件，并在命令行上操作它们。基于此，我们希望构建一个完整的图形化集成开发环境（IDE, Intergrated Development Environment)，将所有的相关开发组件和工具作为一个整体集成在应用程序中。我们将这个应用程序命名为 EOS Studio，并在 2019 年 2 月发布了第一个正式版本。之后的短短三个月内，EOS Studio 吸引了 EOSIO 上的数千名开发者，并得到了来自节点、开发者、项目方们积极的反馈和支持。目前，EOS Studio 已经被 Block.one 作为唯一的社区开发工具列入到官方开发文档中，同时 Block.one 的 CTO Daniel Larimer (BM) 也多次在个人推特上推荐 EOS Studio。此外，全球 EOSIO 社区中大部分的开发团队，也都已经在使用 EOS Studio 作为标准开发工具。\\n\\n无论是传统互联网还是区块链，大型技术团队或小型开发团队，每个开发者都渴望有功能强大且易于使用的集成开发环境来一站式地完成项目开发工作。BOS 作为一条专门为 dApp 生态设计的应用区块链，也需要为 dApp 开发提供更友好的基础设施。通过我们支持 BOS 生态的集成开发环境工具，开发者可以在 BOS 上更简便地去处理复杂的代码或智能合约，这将有效帮助 BOS 生态吸引和培养更多优质的 dApp。除此之外，我们还将为 BOS 上的版本增加更多的新功能，这将进一步降低 dApp 开发者的入门门槛，从而吸引更多的开发者加入 BOS 社区；我们还会在网页版中提供一个开源的智能合约共享平台（就像GitHub一样），通过这个平台开发人员可以更方便地相互学习和交流，并直接在网页中部署和执行代码。\\n\\n我们的团队黑曜石实验室（Obsidian Labs）是一家专注于区块链技术的硅谷创业公司。公司创始人来自硅谷知名孵化器 Y Combinator，并在之后的两年间一直协同工作。2018年，我们的团队在 EOS 官方的全球黑客马拉松获得了旧金山站第三名，并作为唯一的华人团队进入全球总决赛。\\n\\n\\n\\n## 提案简介\\n\\nEOS Studio on BOSCore 是一个图形化的集成开发环境 (IDE)，用于在跨平台区块链网络上开发去中心化应用程序 (dApp)。 通过将众多开发组件集成到一个完整工具中，EOS Studio on BOSCore 可以帮助 BOS 上的开发者大幅提高开发效率。 EOS Studio on BOSCore 主要功能包括 BOS 代码编辑器，合约查看器，网络管理器等：\\n\\n\\n### BOS 代码编辑器\\n\\n- 功能强大的 GUI，可以更轻松，更高效地构建 dApp \\n- 代码高亮显示和自动完成 BOS 语法\\n- 众多 BOS 系统合约模板\\n- 一键创建 BOS 智能合约\\n- 在命令中提示代码错误\\n- 一键部署到本地，测试网或 BOS 主网\\n\\n### 合约查看器\\n\\n- 与 BOS 智能合约交互的图形界面\\n- 从abi表单生成动作参数\\n- 输入修改签署交易的授权\\n- 在表格中加入可视化数据库\\n- 将执行参数和结果保存到“历史记录”中\\n- 将常用参数保存到“书签”中\\n\\n### 网络管理器\\n\\n- 管理多个版本的 BOS 应用程序和编译器\\n- 查看出块日志\\n- BOS 节点事例的高级配置\\n- 在本地环境，测试网或 BOS 主网之间切换\\n- 集成诸如 faucet, keypair manager, memory manager 等工具\\n\\n使用 EOS Studio on BOSCore，开发者可以一站式地完成本地开发、测试网调试，最终在 BOS 主网部署的完整开发流程。\\n\\n\\n\\n## 提案执行\\n\\n来自黑曜石实验室的 3-5 名开发和运营人员将会负责这个项目。另外，我们将再添加 1-2 名开发者负责产品的更新。\\n\\n第一阶段：为 EOS Studio on BOSCore 开发基本模块，为期六周\\n\\n第二阶段：发布 EOS Studio on BOSCore 测试版并收集反馈，为期两周\\n\\n第三阶段：进行产品的稳定性测试和安全性测试，为期一周\\n\\n第四阶段：发布 EOS Studio on BOSCore 正式版本，并配套制作视频和文章教程，为期一周\\n\\n\\n\\n## 提案目标\\n\\n我们的目标是通过 EOS Studio on BOSCore 推动区块链技术普及给开发者，并为开发者提供有价值的产品和服务。 BOS 是一个年轻且快速发展的去中心化应用区块链，一个成熟的完整开发环境会吸引大量的开发者来 BOS 上部署他们的应用。 具体来说，第一阶段我们希望能尽快上线 EOS Studio on BOSCore，为 BOS 上的开发者提供完整功能的工具。在此之后，我们将在 BOS 社区中制作大量的开发者教程，和 BOSCORE 一同举办各种线上和线下开发者活动，以便开发者能更方便地上手 EOS Studio on BOSCore。\\n\\n\\n\\n## 执行团队\\n\\n**Phil Li**，首席执行官，硅谷孵化器 Y Combinator 校友，Obsidian Labs 创始人，全栈工程师，EOS Studio 核心开发者。Phil 本科毕业于北京大学，后赴美国麻省理工学院攻读博士，曾带领团队获得旧金山 EOS Global Hackathon 第三名。Phil 具有丰富的移动端和网页端开发经验，熟悉区块链和智能合约方面的开发。\\n\\n**Sam Sun**，首席增长官，硅谷孵化器 Y Combinator 校友，Obsidian Labs 合伙人，毕业于英国纽卡斯尔大学，曾在中国，韩国，新加坡和亚洲其他地区举办大量的区块链开发者活动。\\n\\n**Rose Ren**，品牌战略官，Obsidian Labs 创始人，毕业于密歇根大学安娜堡分校。曾任 Nebulas 的公关和营销总监，并曾在Continue Capital 和丹华资本负责投资事务。\\n\\n**Leon Liang**，香港科技大学计算机硕士，EOS Studio 前端开发工程师。\\n\\n**Sabrina Zhang**，EOS Studio 产品经理。\\n\\n\\n\\n## 提案预算\\n\\n本项目预计花费约 500,000 BOS；\\n\\n第一阶段：300,000 BOS，用于支付 3-5 名开发者的人力和开发成本；\\n\\n第二阶段：100,000 BOS，用于支付 1-2 名开发者的产品迭代，同步更新支持 BOS 链最新功能；\\n\\n第三阶段：100,000 BOS，用于支付制作开发教程、视频、和举办线下开发者活动成本。\\n\\n\",\"type\":\"referendum-v1\",\"incentives\":\"500000.0000 BOS\",\"receiptor\":\"eosstudiosam\"}", + "created_at": "2019-06-19T07:07:40" + }, + "stats": { + "votes": { + "0": 1, + "1": 19, + "total": 20, + "proxies": 10, + "accounts": 10 + }, + "accounts": { + "0": 150002, + "1": 12232807654, + "total": 12232957656 + }, + "proxies": { + "0": 0, + "1": 54800610003, + "total": 54800610003 + }, + "staked": { + "0": 150002, + "1": 67033417657, + "total": 67033567659 + }, + "block_num": 43385214 + } + }, + "historyindex": { + "id": "historyindex_20190522", + "proposal": { + "proposal_name": "historyindex", + "proposer": "cc32dninexxx", + "title": "Chronicle and History Indexer", + "proposal_json": "{\"content\":\"The project aims to build a new solution for EOSIO blockchain history service. It will be scalable from a cheap server to a high-end server cluster, and provide a rich variety of data and services apart from traditional account history.\\n\\nThe project is described in detail at \\nhttps://medium.com/@cc32d9/fundraising-for-chronicle-and-history-indexer-26e0a06c2d1d\\n\\nThere is already a prototype being tested and indexing EOS mainnet, because it's the biggest available dataset and a great measure of database scalability.\\n\\nThe total project budget is US$32,500. \\n\\nTelos community has granted 100k TLOS in work proposal, and it covers about 15% of the total budget in current prices. \\n\\nThis work proposal aims to cover the rest of the budget, and the target claim is 250000 BOS.\\n\\nTarget delivery date: end of September 2019\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-22T20:16:36" + }, + "stats": { + "votes": { + "0": 2, + "1": 6, + "255": 2, + "total": 10, + "proxies": 1, + "accounts": 9 + }, + "accounts": { + "0": 2000, + "1": 1505363180, + "255": 2609200003, + "total": 4114565183 + }, + "proxies": { + "0": 383885875, + "1": 0, + "total": 383885875 + }, + "staked": { + "0": 383887875, + "1": 1505363180, + "255": 2609200003, + "total": 4498451058 + }, + "block_num": 43385214 + } + }, + "hyperion.api": { + "id": "hyperion.api_20190525", + "proposal": { + "proposal_name": "hyperion.api", + "proposer": "bosriobrazil", + "title": "Hyperion History on BOS", + "proposal_json": "{\"content\":\"![alt text](https://cdn-images-1.medium.com/max/800/1*a-gNhYLCGA6sNovlBhxjsw.png \\\"Header\\\")\\n\\n## Problem\\n\\nOne of the earliest bottlenecks to arise on EOSIO-based blockchains were the exponentially growing size of full history data for the networks. For example, in the 9 months of EOS Mainnet the full history had grown to more than 5Tb of storage and took weeks to synchronize. As a result, maintaining the infrastructure for full history API could cost more than USD 15k/month.\\n\\nEOS Rio team proposed a new approach to data storage structure and developed an Elasticsearch based history API service that has optimized storage and low response times. This significantly reduced database size and the costs to maintain a full history node.\\n\\nThe availability of high-quality, low latency history API services is critical to support the development of dApps, block explorers, and wallets. This makes us believe that the implementation, maintenance, and evolution of Hyperion History generates value for the BOSCore ecosystem.\\n\\nHyperion History API is already operating on BOS Mainnent and providing full history blockchain data. In this proposal, the EOS Rio Team expresses its commitment to the constant evolution of Hyperion History and making the service available for the broadest possible user base.\\n\\n## Solution - Hyperion History API\\nHyperion History is a scalable history API solution for EOSIO based blockchains. It reduces database size in about 85% when compared to the original history_plugin.\\n\\nHyperion History implements a new approach to data structure and storage:\\n\\n1. actions are stored in a flattened format\\n2. a parent field is added to the inline actions to point to the parent global sequence\\n3. if the inline action data is identical to the parent, it is considered a notification and thus removed from the database\\n4. no blocks or transaction data are stored, all information can be reconstructed from actions\\n5. no transaction validation information is stored, as all information can be verified on the block information using the Chain API, dApps do not use History for that.\\n\\nWith those changes, the API format focus on delivering shorter response times, lower bandwidth overhead, and ease-of-use for UI/UX developers. The optimized data structure tends to reduce CPU and bandwidth consumption making infrastructure more scalable.\\n\\nTo further improve performance, we engineered a multi-threaded indexer that extracts data from the state history plugin, allowing for faster ingestion times with the proper hardware optimization. We also introduced an “ABI History Caching Layer” component to prevent deserialization failures when parallel processing historical data over ABI modifications.\\n\\n## Competitors\\nOther teams have responded to the challenge of creating History solutions for EOSIO. Suitable solutions were implemented and are running, creating a more robust ecosystem, each with a unique approach to the problem. However, Hyperion History main differentials are in the format change, optimizing API performance with shorter response times, lower bandwidth overhead, and ease-of-use for UI/UX developers. Also, allowing database size reduction of about 85% and faster injection times.\\n\\n## Execution Plan\\nFollows a detailed roadmap for Hyperion History. This plan is subject to changes depending on the most pressing needs of the BOS community and will be updated with new deliveries as the demand appears.\\n\\nAs a general rule, our main development priority will always be on stability and data integrity.\\n\\n![alt text](https://cdn-images-1.medium.com/max/800/1*5_Q10ylURPt2OZjtm5Y-HA.png \\\"Execution Plan\\\")\\n\\nDeliverables can be tracked and monitored here: https://github.com/eosrio/Hyperion-History-API\\n\\nGeneral project updates can be found at:\\n\\n- https://eosrio.io/hyperion/\\n- https://t.me/eosrio\\n- https://medium.com/@eosriobrazil\\n\\n## Fund Release Plan\\nThe Hyperion History project includes not only the application development but also the infrastructure operation to serve the BOSCore community continually. EOS Rio team will keep the public Hyperion node running as long as we have the resources to do so. In that scenario, we are considering the following funding plan:\\n\\n| Phase \\t| Duration (weeks) \\t| Allocation (hours) \\t| BOS \\t|\\n|----------------------------\\t|------------------\\t|--------------------\\t|------------\\t|\\n| Integrity Check Scripts \\t| 3 \\t| 90 \\t| 171,000.00 \\t|\\n| Data Streaming API \\t| 4 \\t| 120 \\t| 228,000.00 \\t|\\n| eosio v1.8.0 compatibility \\t| 3 \\t| 90 \\t| 171,000.00 \\t|\\n| Indexer control interface \\t| 4 \\t| 120 \\t| 228,000.00 \\t|\\n| Maintenance \\t| 26 \\t| 104 \\t| 197,600.00 \\t|\\n| \\t| \\t| TOTAL \\t| 995,600.00 \\t|\\n\\n#### Integrity Check Scripts\\nDevelopment of scripts and methods to aid cluster operators on verifying history data integrity. Those tools should also be able to repair any missed data detected.\\n\\n#### Data Streaming API\\nA Websocket based API that will allow users to receive real time data from actions that notify specific accounts. This can be used by dapps and wallets to notify the users, receiving information from actions in real time. We plan to include different types of filters on the requests.\\n\\n#### EOSIO v1.8.0 compatibility\\nThis release will include breaking changes on the state history plugin that changes to the action structure, meaning that the current implementation of Hyperion History should be carefully adapted to make full usage of the new format. \\n\\n#### Indexer control interface\\nGraphical user interface to simplify monitoring and maintenance of nodes running Hyperion History. This allows cluster operators to perform routine actions and optionally show cluster status to the community.\\n\\n#### Maintenance\\nCost to help cover the maintenance of a high-performance Elasticsearch cluster providing Hyperion History to serve the BOS Mainnet.\\n\\n## Team\\nEOS Rio Team will be responsible for the project under the technical leadership of our CTO, Igor Lins e Silva. Here follows a brief description of EOS Rio Founders.\\n\\nIgor Lins e Silva - Head of Technology\\nEarly-adopter of the EOSIO platform and one of the most proficient engineers on EOSIO based networks, Igor is recognized for his thought leadership on DPoS Blockchain infrastructure and dApp development. Igor is an automation and control engineer and a machine learning and image processing masters drop-out. github.com/igorls/\\n\\nDominique Deschatre - Head of Development \\nCombining a vision for product ownership, natural talent for user experience, great front-end coding skills and experience in developing multi-platform native mobile apps, Domi manages a diverse and resourceful team of devs that ship quality user-friendly software at breakneck speed while focusing on long term product development.\\n\\nThiago Canellas - Head of Strategy\\nWith more than 10 years experience working in multiple roles in startups, from CFO to head of customer success, and a top-management consulting background, Canellas is responsible for supporting all areas and make sure things are running smoothly in EOS Rio. He is also responsible for the long term vision of EOS Rio.\\n\\nRelevant Links\\n - Github Repository: https://github.com/eosrio/Hyperion-History-API\\n - Medium Article: https://medium.com/@eosriobrazil/presenting-hyperion-history-api-solution-f8a8fda5865b\\n\\n## 解决方案简介\\n\\n基于EOSIO的区块链最早出现的瓶颈之一是网络的完整历史数据的指数级增长。例如，在EOS Mainnet的9个月中，完整的历史记录已经增长到超过5Tb的存储空间，需要花费数周时间才能同步。因此，维护完整历史API的基础架构可能会花费超过15,000美元/月。\\n\\nEOS Rio团队提出了一种新的数据存储结构方法，并开发了基于Elasticsearch的历史API服务，该服务优化了存储并缩短了响应时间。 这显着减少了数据库大小和维护完整历史节点的成本。\\n\\n高质量、低响应时间的历史API服务可用性是支持DApp，块浏览器和钱包开发的关键。\\n\\n我们坚信Hyperion 历史数据解决方案在实现、维护和发展为BOSCore生态系统创造无限价值。\\n\\nHyperion History API已在BOS Mainnent上运行，并提供完整的历史区块链数据。在此提案中，EOS Rio 团队表达了对Hyperion History不断发展的承诺，并为用户群提供最广泛服务。\\n\\n## 解决方案- Hyperion History API\\n\\nHyperion History是基于EOSIO区块链的可扩展历史数据API解决方案。与原始history_plugin相比，它将数据库大小降低了大约85％。\\n\\nHyperion History实现了一种新的数据结构和存储方法：\\n\\n 1. 动作以展平格式存储。\\n 2. 将父字段添加到内联操作以指向父全局序列。\\n 3. 如果内联操作数据与父操作数据相同，则将其视为通知，从而从数据库中删除。\\n 4. 不存储块或事务数据，可以从动作重建所有信息。\\n 5. 没有存储交易验证信息，因为可以使用Chain API在块信息上验证所有信息，DApp不使用历史记录。\\n\\n通过这些更改，API格式专注于缩短响应时间，降低带宽开销，并使UI / UX开发人员更易于使用。优化的数据结构倾向于减少CPU和带宽消耗，使基础架构更具可扩展性。\\n\\n为了进一步提高性能，我们设计了一个多线程索引器，从状态历史插件中提取数据，通过适当的硬件优化实现更快的摄取时间。我们还引入了“ABI历史缓存层”组件，以防止在ABI修改时并行处理历史数据时出现反序列化失败。\\n\\n## 其他团队情况\\n\\n其他团队已经回应了为EOSIO创建历史解决方案的挑战。实施了良好的解决方案，并且正在运行，创建一个更加强大的生态系统，但是，Hyperion History的主要区别在于格式更改，优化API性能，缩短响应时间，降低带宽开销，并使UI / UX开发人员更易于使用。此外，允许数据库大小减少约85％以及更快的注入时间。\\n\\n## 项目进程执行计划\\n\\n遵循Hyperion History的开发计划。该计划可能会根据BOS社区最迫切的需求而变化，并会根据需求随新的交付情况进行更新。作为一般规则，我们的主要发展优先事项始终是稳定性和数据完整性。\\n\\n![alt text](https://cdn-images-1.medium.com/max/1000/1*J4AcLMV8kngt6jSi-yNI-g.png \\\"Execution Plan\\\")\\n\\n可以在此处跟踪和监控可交付成果：https://github.com/eosrio/Hyperion-History-API\\n\\n可以在以下位置找到常规项目更新：\\n\\n- https://eosrio.io/hyperion/\\n- https://t.me/eosrio\\n- https://medium.com/@eosriobrazil\\n\\n## 基金发布计划\\n\\nHyperion项目不仅包括应用程序开发，还包括不断为BOSCore社区提供服务的基础架构操作。只要我们有足够的资源，EOS Rio团队将保持Hyperion节点的运行。在这种情况下，我们正在考虑以下资金计划：\\n\\n| 项目 \\t| 时间周期(周) \\t| 分配单位(小时) \\t | BOS \\t|\\n|----------------------------\\t|------------------\\t|--------------------\\t|------------\\t|\\n| 完整性检查模块 \\t| 3 \\t| 90 \\t| 171,000.00 \\t|\\n| 数据流API \\t| 4 \\t| 120 \\t| 228,000.00 \\t|\\n| eosio v1.8.0 兼容性 \\t| 3 \\t| 90 \\t| 171,000.00 \\t|\\n| 索引器控制界面 \\t| 4 \\t| 120 \\t| 228,000.00 \\t|\\n| 基础设施维护 \\t| 26 \\t| 104 \\t| 197,600.00 \\t|\\n| \\t| \\t| TOTAL \\t| 995,600.00 \\t|\\n\\n#### 完整性检查脚本\\n开发脚本和方法以帮助集群运营商验证历史数据的完整性。 这些工具还应该能够修复检测到的任何遗漏数据。\\n\\n#### 数据流API\\n基于Websocket的API，允许用户从通知特定帐户的操作中接收实时数据。 dapps和wallets可以使用它来通知用户，实时接收来自操作的信息。我们计划在请求中包含不同类型的过滤器。\\n\\n#### EOSIO v1.8.0兼容性\\n此版本将包括状态历史插件的更改，这将更改操作结构，这意味着应仔细调整Hyperion History的当前实现以利用新格式。\\n\\n#### 索引器控制界面\\n图形用户界面，简化了运行Hyperion History的节点的监控和维护。这允许集群操作员执行例行操作，并可选择将集群状态公开给社区。\\n\\n#### 基础设施维护\\n帮助维护高性能Elasticsearch集群的成本，该集群提供Hyperion History以服务于BOS Mainnet。\\n\\n## 团队介绍\\n\\n我们的首席技术官Igor Lins e Silva 将领导整个项目开发。\\n\\nEOS Rio 团队组成简介：\\n\\nIgor Lins e Silva - 技术负责人\\nEOS.IO平台的早期采用者和基于EOS.IO的网络上最熟练的工程师之一，Igor因其在DPoS区块链基础设施和DApp开发方面的思想领导地位而闻名。Igor是一名自动化及控制工程师，有机器学习和图像处理大师学习经历。github.com/igorls/\\n\\nDominique Deschatre - 开发主管\\n结合产品所有愿景和用户体验的天才，具有出色的前端编码技能和开发多平台原生移动应用程序的经验，她带领一个多元化，资源丰富的开发团队，以极快的速度提供高质量的用户友好应用，并专注于长期的产品开发。\\n\\nThiago Canellas - 战略主管\\n拥有超过10年的创业公司多岗位经验，从首席财务官到客户成功负责人，以及最高管理层的咨询背景，Canellas负责支持所有领域并保障EOS Rio项目顺利搭乘。他负责构架EOS Rio的长期愿景。\\n\\n更多更详细介绍，请点击：\\n - Github: https://github.com/eosrio/Hyperion-History-API\\n - Medium: https://medium.com/@eosriobrazil/presenting-hyperion-history-api-solution-f8a8fda5865b\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-25T09:21:25" + }, + "stats": { + "votes": { + "1": 49, + "total": 49, + "proxies": 26, + "accounts": 23 + }, + "accounts": { + "0": 0, + "1": 43322465220, + "total": 43322465220 + }, + "proxies": { + "0": 0, + "1": 120328251514, + "total": 120328251514 + }, + "staked": { + "0": 0, + "1": 163650716734, + "total": 163650716734 + }, + "block_num": 43385214 + } + }, + "indextokenex": { + "id": "indextokenex_20190613", + "proposal": { + "proposal_name": "indextokenex", + "proposer": "ilaogestudio", + "title": "INdex - BOS automated token exchange", + "proposal_json": "{\"content\":\"# INdex - BOS automated token exchange\\n\\n## Introduction\\n\\nTarget of this project is to create a protocol on BOS that allows automated on-chain token exchange between tokens issued on BOS.\\n\\nThis project's architecture mainly draws on the models of Uniswap.\\n\\nUniswap is a protocol for automated token exchange on Ethereum. It is designed around ease-of-use, gas efficiency, censorship resistance, and zero rent extraction. It is useful for traders and functions particularily well as a component of other smart contracts which require guaranteed on-chain liquidity.\\n\\nMost exchanges maintain an order book and facilitate matches between buyers and sellers. Uniswap smart contracts hold liquidity reserves of various tokens, and trades are executed directly against these reserves. Prices are set automatically using the constant product ([`x*y=k`](https://ethresear.ch/t/improving-front-running-resistance-of-x-y-k-market-makers/1281)) market maker mechanism, which keeps overall reserves in relative equilibrium. Reserves are pooled between a network of liquidity providers who supply the system with tokens in exchange for a proportional share of transaction fees.\\n\\nINdex is a fully decentralized exchange. whole source code for all smart contracts and interfaces will be open-source and public.\\n\\n## Function Details\\n\\n### Creating Exchanges\\n\\nINdex can create any exchanges with token and BOS system token.\\n\\n### BOS ⇄ Tokens Trades\\n\\nEach exchange is associated with a single token and holds a liquidity pool of both BOS and that token. The exchange rate between BOS and token is based on the relative sizes of their liquidity pools within the contract. This is done by maintaining the relationship `bos_pool * token_pool = invariant`. This invariant is held constant during trades and only changes when liquidity is added or removed from the market.\\n\\nWhen BOS is sent to the contract, `bos_pool` increases. In order to maintain the relationship `bos_pool * token_pool = invariant`, `token pool` is decreased by a proporitonal amount. The amount by which `token_pool` is decreased is the amount of tokens purchased. This change in reserve ratio shifts the BOS to Token exchange rate, incentivizing trades in the opposite direction.\\n\\nThe format is:\\n\\n$tokenReceived = tokenPool - \\\\frac{bosPool*tokenPool}{bosSent + bosPool}$\\n\\nIf consider the fee, the format will be:\\n\\n$tokenReceived = tokenPool - \\\\frac{bosPool*tokenPool}{bosSent - fee + bosPool}$\\n\\n\\nThe same logic when TOKEN is sent to the contract.\\n\\n### TOKEN ⇄ TOKEN Trades\\n\\nSince BOS is used as a common pair for all TOKENs, it can be used as an intermediary for direct A TOKEN to ANOTHER TOKEN swaps. \\n\\n### Providing Liquidity\\n\\n#### Adding Liquidity\\n\\nAdding liquidity requires depositing an equivalent value of BOS and TOKENs into contract.\\n\\nThe first liquidity provider to join a pool sets the initial exchange rate by depositing what they believe to be an equivalent value of BOS and Tokens. If this ratio is off, arbitrage traders will bring the prices to equilibrium at the expense of the initial liquidity provider.\\n\\nAll future liquidity providers deposit BOS and TOKENs using the exchange rate at the moment of their deposit. If the exchange rate is bad there is a profitable arbitrage opportunity that will correct the price.\\n\\n\\n####Removing Liquidity\\n\\nThe same logic as adding liquidity.\\n\\n#### Liquidity Share\\n\\nLiquidity share are minted to track the relative proportion of total reserves that each liquidity provider has contributed. They are highly divisible and can be burned at any time to return a proporitonal share of the markets liquidity to the provider.\\n\\nWith given $bosDepositd$\\n\\n$tokensDeposited=tokenPool*\\\\frac{bosDeposited}{bosPool}$\\n\\n$addShare=totalShare*\\\\frac{bosDeposited}{bosPool}$\\n\\n$newTotalShare = addShare + totalShare$\\n\\nAdding liquidity and hold liquidity share can benefit from exchange fee.\\n\\n### Fee Structure\\n\\n- BOS to TOKEN trades\\n - 0.3% fee paid in BOS\\n- TOKEN to BOS trades\\n - 0.3% fee paid in TOKEN\\n- TOKEN to TOKEN trades\\n - 0.3% fee paid in TOKEN tokens for TOKEN to BOS swap on input exchange\\n - 0.3% fee paid in BOS for BOS to TOKEN swap on output exchange\\n - Effectively 0.5991% fee on input TOKEN\\n\\nThere is a 0.3% fee for swapping between BOS and TOKENs. This fee is split by liquidity providers proportional to their contribution to liquidity reserves. Since TOKEN to TOKEN trades include both an TOKEN to BOS swap and a BOS to TOKEN swap, the fee is paid on both exchanges. There are no platform fees.\\n\\nSwapping fees are immediately deposited into liquidity reserves. Since total reserves are increased without adding any additional share tokens, this increases that value of all shares equally. This functions as a payout to liquidity providers that can be collected by burning shares.\\n\\nSince fees are added to liquidity pools, the invariant increases at the end of every trade. Within a single transaction, the `invariant` represents `bos_pool * token_pool` at the end of the previous transaction.\\n\\n\\n## Development Plan\\n\\n- Contracts  :  3 weeks\\n\\n- User interface :  3 weeks\\n\\n- Testing : 2 weeks\\n\\n## Proposal Budget\\n\\nBudget: 300,000 BOS\\n\\nIncluding contract development, UI design, website development and code review.\\n\\n## Team\\n\\nThe team ( https://laoge.studio/ ) are very experienced in develop solutions for EOSIO Blockchains. We have C++ developers that will take care of the contracts and frontend engineer who will create the website of the project.\\n\\n## Relevant Links\\n\\n[https://uniswap.io](https://uniswap.io/)\\n\\nhttps://hackmd.io/s/HJ9jLsfTz\\n\\n# INdex - BOS上的即时代币交易所\\n\\n## 简介\\n\\n该项目的目标是创建一个运行在BOS上的链上即时自动交易协议，来交易发行在BOS上的代币。\\n\\n该项目主要借鉴了运行在以太坊上的Uniswap项目。\\n\\nUniswap是一个运行在以太坊上的自动交易协议，它围绕易用性，低资源消耗而设计。它通过智能合约来实现了自动交易，同时为交易提供流动性。\\n\\n大多数的交易所都是通过挂单撮合的模式来完成资产之间的交易。Uniswap智能合约持有交易对双边的资产储备，交易发起者直接与智能合约进行交易，通过底池资金形成价格，交易会立刻成交。使用 （资产A底池 * 资产B底池 = 常数） 的做市商机制自动设定价格，使整体储备保持相对均衡。流动性提供者为智能合约提供资产储备金，以换取按比例分摊的交易费用。\\n\\nINdex 是一个完全去中心化的交易所，完整的智能合约代码将会开源。\\n\\n## 功能细节\\n\\n### 创建交易对\\n\\nINdex 可以创建BOS系统代币和任意代币之间的交易对。\\n\\n### BOS ⇄ 代币 交易\\n\\n每一个交易对都由包含BOS和代币的流动性底池组成，交易价格由底池中双边的余额确定，通过保持`bos底池 * 代币底池 = 定值`来形成价格。这个`定值`在交易前后保持不变，除非对交易对增加或抽走流动性。\\n\\n当交易者发送BOS到智能合约，`bos底池`金额增加，为了保证`定值`不变，`代币底池`按比例减少，而减少的部分会发送给交易者，就是买到的代币。\\n\\n计算公式:\\n\\n$购得代币 = 代币底池 - \\\\frac{bos底池*代币底池}{付出bos + bos底池}$\\n\\n如果将手续费考虑进去，公式是:\\n\\n$购得代币 = 代币底池 - \\\\frac{bos底池*代币底池}{付出bos - 手续费 + bos底池}$\\n\\n当发送代币到合约，逻辑也是相同的，会得到相应的BOS。\\n\\n### 代币 ⇄ 代币 交易\\n\\n既然代币与BOS之间已经由交易对，那么可以自动连接这些交易对，使用BOS作为中转直接交易两种代币。\\n\\n### 提供流动性\\n\\n#### 增加流动性\\n\\n增加流动性需要同时向智能合约底池存入交易对边的资金。\\n\\n初始流动性提供者通过存入双边资金设置初始价格。如果价格不合理，套利者将会快会通过交易改变价格。\\n\\n之后的流动性提供者，需要根据当时价格存入相对应的双边资产。\\n\\n#### 抽走流动性\\n\\n与增加流动性同理。\\n\\n#### 流动性股份\\n\\n流动性股份用于追踪每个流动性提供者贡献的总储备的相对比例。\\n\\n如果流动性提供者希望为交易对提供特定金额$bosDepositd$的流动性\\n\\n那么同时也需要存入代币：\\n\\n$tokensDeposited=tokenPool*\\\\frac{bosDeposited}{bosPool}$\\n\\n获得的股份为：\\n$addShare=totalShare*\\\\frac{bosDeposited}{bosPool}$\\n\\n总股份增加为：\\n$newTotalShare = addShare + totalShare$\\n\\n为交易对提供流动性可以获得交易手续费的收入。\\n\\n### 手续费结构\\n\\n- BOS购买代币\\n - 0.3% 手续费用BOS支付\\n- 代币购买BOS\\n - 0.3% 手续费通过代币支付\\n- 代币购买其他代币\\n - 0.3% 手续费使用代币支付，用来购买BOS\\n - 0.3% 手续费使用BOS支付用来购买另一个代币\\n - 用购买的代币计算，大约为 0.5991% 的费率\\n\\n0.3%的手续费将自动归入流动性底池而不增加流动性股份，所以每股对应的底池金额将会缓慢增加，最终手续费通过这种形式支付给流动性提供者。\\n\\n\\n## 开发计划\\n\\n- 合约: 3周\\n\\n- 用户界面: 3周\\n\\n- 测试: 2周\\n\\n## 申请预算\\n\\n预算: 300,000 BOS\\n\\n包括智能合约开发、界面设计、前端网站开发和代码审计。\\n\\n## 团队\\n\\n老哥工作室 ( https://laoge.studio/ ) 在EOSIO区块链领域拥有大量的开发经验，其中包括DAPP，钱包，浏览器等一系列配套设施的开发。\\n\\n## 相关参考连接\\n\\n[https://uniswap.io](https://uniswap.io/)\\n\\nhttps://hackmd.io/s/HJ9jLsfTz\",\"type\":\"referendum-v1\",\"incentives\":\"300000.0000\",\"receiptor\":\"ilaogestudio\"}", + "created_at": "2019-06-13T15:21:04" + }, + "stats": { + "votes": { + "1": 7, + "total": 7, + "proxies": 2, + "accounts": 5 + }, + "accounts": { + "0": 0, + "1": 4003886156, + "total": 4003886156 + }, + "proxies": { + "0": 0, + "1": 21439796977, + "total": 21439796977 + }, + "staked": { + "0": 0, + "1": 25443683133, + "total": 25443683133 + }, + "block_num": 43385214 + } + }, + "mansaboscomm": { + "id": "mansaboscomm_20190604", + "proposal": { + "proposal_name": "mansaboscomm", + "proposer": "bosmansawps1", + "title": "Mansa: BOS Community Management", + "proposal_json": "{\"content\":\"\\n\\n**Table of Contents**\\n\\n[Proposal Background](#_Toc9782803)\\n\\n[Proposal Introduction](#_Toc9782804)\\n\\n[Application Scenario](#_Toc9782805)\\n\\n[Proposal Execution](#_Toc9782806)\\n\\n[Proposal Goal](#_Toc9782807)\\n\\n[Execution Team](#_Toc9782808)\\n\\n[Proposal Budget](#_Toc9782809)\\n\\n \\n\\n \\n\\n\\n\\n# **Proposal Background**\\n\\nAs the blockchain boom reached its peak in 2017, blockchain projects have sprung up, and competition has not only existed in the underlying infrastructure technology of the blockchain, but also in the operation of the brand management, public relations and community management of the project execution team. In the area of blockchain, code is law, consensus is market value, and consensus could only be achieved by professional community operations.\\n\\nGood community management requires the following:\\n\\n1. In-depth analysis of project and product brands.\\n\\n2. Have a variety of collaboration channels.\\n\\n3. Short-term and long-term brand management and development for projects.\\n\\n4. Implement strong execution on brand, PR and community operations.\\n\\n5. Clear planning for the modular operation of the community.\\n\\nUnder the effective combination of brand management and community management operation, high-quality projects can form long-term stable supporters and community, who will help the brands to achieve more offline acquaintance marketing, and increase the brand's organic vitality and flexibility as well as more effective maintenance of public image during public relations issues.\\n\\nBOSCore is a community-based project whose technical strength has been recognized by the industry, but currently lacks more professional operation in brand management, public relations and community management. The ideal consensus effect was not achieved in current situations.\\n\\n# **Proposal Introduction**\\n\\nMansa Capital is an integrated marketing specialist for blockchain projects. The team has extensive experience in community management, public relations and brand marketing for blockchain projects, and has served on blockchain projects such as JKR, IOEX, BHIC, and MINEBIT.\\n\\nThe goal of this proposal is to create BOSCore's unique brand strategies, operational solutions and long-term brand public relations and community management processes. BOSCore provides effective assistance in investment and financing and long-term business strategy.\\n\\nThe executions of the proposal is divided into five following aspects.\\n\\n1. Develop a community growth plan that matches equipment, tools, and people according to the plan.\\n\\n2. Develop a community's operational promotion plan, implement activity rules according to the community operation system based on parallel ripple model and the ranch theory, and improve the community activity together with the PR schedule and activities.\\n\\n3. Converting end users into BOSCore supports, through the community brand activities, educate the user's perception of BOSCore, and complete the process from get to know to understanding, to the supporters, and eventually to word of mouth.\\n\\n4. Within 3 months, the Chinese community users will be organically grown to 60,000 people, and the community will be effectively communicated and managed according to brand needs.\\n\\n5. Promote the BOSCore community brand around the PR planning and activity planning within three months.\\n\\n# **Application Scenario**\\n\\nAt the time of the release of BOSCore, there were a number of new media reports on the network that made false reports on the project. The public relations team can respond in real time, release information, and resolve the crisis with strong real-time response.\\n\\nThe increase in the community can enhance brand awareness while helping BOSCore offline activities. Use the community to conduct offline acquaintance marketing. Let more people understand and recognize the BOSCore brand.\\n\\nUse acquaintance marketing to achieve stronger organic growth for the community. Better community growth through private invitations.\\n\\nAccording to the ecology of BOSCore, the Mansa team planned and organized a joint brand campaign together with 20 organizations, and carried out in-depth cooperation with the ecological partners such as wallet, BOSCore BPs, DApps, blockchain media, exchanges, financial institutions, etc. in order to attract more users and awareness to BOSCore. From May 15th to May 25th, in the airdrop activities jointly with TOKENPOCKET wallet, 20 active communities were established, nearly 7,000 community users, and more than 1,700 actual users.\\n\\n# **Proposal Execution**\\n\\nExecutive team of 7-10 people\\n\\n- Stage 1: Form a community growth of 20,000 people, completing the accumulation of seed users in the BOSCore community, 4 weeks\\n\\n- Stage 2: Form a community growth of 20,000 people, establish a reasonable community management system, and use acquaintance marketing to establish a reasonable project support group, 4 weeks\\n\\n- Stage 3: Form a community growth of 20,000 people, complete the process and community system of the long-term brand strategy, and help the project to make longer-term strategic assistance, 4 weeks\\n\\nThe total project phase is 3 months\\n\\n# **Proposal Goal**\\n\\nIn three months, we would like to achieve community growth of 60,000 people, and established 4-5 media cooperation channels. The offline autonomous organizations brought by community management are to cover 30 major cities in China. At the same time, we would like to assist BOSCore in implementing team communication, brand management, and to offer support to its long-term financing requirement and business development.\\n\\n# **Execution Team**\\n\\n- Mansa Wang, founder of MANSA CAPINTAL, graduated from Wuhan University, a serial entrepreneur, brand marketing expert, guest lecturer at the University of International Business and Economics, and is well versed in user growth and user operations.\\n\\n- Mansa Long, co-founder of MANSA CAPITAL, graduated from Beijing University of Aeronautics and Astronautics, an early investor in the blockchain.\\n\\n- Mansa Yin, MANSA CAPITAL Technical Consultant, graduated from Tsinghua University, ex CTO of a public listed company.\\n\\n- Mansa Zhang, MANSA CAPITAL Head of Market Making, Master of Finance at Peking University, has a bachelor's degree in English. He has worked for a top private equity fund, managing traditional fund sizes up to 2 billion, and blockchain funds up to 10,000 BTC.\\n\\n- Mansa Dong, MANSA CAPITAL Head of Market Management, Risk Management and Trading Strategy Architect, graduated from Beijing University of Aeronautics and Astronautics with 6 years of trading experience. He worked for a top private equity fund, managing traditional fund size up to 1 billion, blockchain fund scale Up to 10,000 BTC.\\n\\n- The operation executive team consists of 7 master's degree holders from the Renmin University and Beijing University of Aeronautics and Astronautics. A high-quality and highly educated team can quickly learn and understand the project and execute the operation plan in an orderly manner.\\n\\n# **Proposal Budget**\\n\\nBudget: 800,000 BOS, including manpower, brand management, collaborative channel development and community development/management cost.\\n\\n \\n\\n| Milestone | Phase I Completion |\\n| --------- | ------------------ |\\n| BOS | 800,000 |\\n\\n \",\"type\":\"referendum-v1\",\"incentives\":\"800000.0000\",\"receiptor\":\"bosmansamoon\"}", + "created_at": "2019-06-04T03:02:05" + }, + "stats": { + "votes": { + "0": 2, + "1": 33, + "total": 35, + "proxies": 17, + "accounts": 18 + }, + "accounts": { + "0": 2101, + "1": 32663985427, + "total": 32663987528 + }, + "proxies": { + "0": 0, + "1": 95283980662, + "total": 95283980662 + }, + "staked": { + "0": 2101, + "1": 127947966089, + "total": 127947968190 + }, + "block_num": 43385214 + } + }, + "omegaautodex": { + "id": "omegaautodex_20190526", + "proposal": { + "proposal_name": "omegaautodex", + "proposer": "nebulablocks", + "title": "💫 Omega — BOS automated token exchange", + "proposal_json": "{\"content\":\"## Brief\\nCreate a protocol on top of EOSIO blockchains that allows automated on-chain token exchange between EOSIO tokens.\\n\\nThis protocol will allow users to contribute to the exchange liquidity pools and earn commissions (in the form of exchange fees) for doing so.\\n\\nExchange rates for trades are calculated based on a simple equation: x * y = k . The exchange rate of a token will always be at a particular point lying on the resulting curve of this equation.\\n\\nOmega is censorship-resistant, has no single point of failure, and completely eliminates rent-seeking intermediaries. It has no native token, no listing fees and the whole source code for all smart contracts and interfaces will be open-source and public.\\n\\n## Solution\\nCurrently, there is no solution for decentralized token swaps on BOSCore. Not only will this proposal create that solution, it will also allow BOS token holders to add liquidity to the pools and earn revenue from the fees generated.\\n\\nOmega is uniquely differentiated from other DEX projects because it maintains no order book. Omega exchange contracts set prices automatically using a bonding curve mechanism known as a constant product.\\n\\nA widget that can be embedded in websites to do quick and easy token swaps will be provided in the final solution.\\n\\nOur solution is highly influenced by the great work done by Uniswap backed by Ethereum foundation with $100,000.\\n\\n## Competitors\\nIn BOSCore there is not another liquidity pool provider that provides the basic functionalities that Omega will bring. On EOS Mainnet there is Bancor. The main difference is that Bancor uses their own token and token holders can’t earn fees adding liquidity to the pools.\\n\\nWith our solution we could allow instant liquidity to BOSCore tokens, and using the powerful IBC we could even add liquidity to EOS/BOS pair (or any other token that it’s transported by IBC.\\n\\nAnother idea that could be possible with our contracts, its to create Initial Coin Offers based on the creation of a liquidity pool for a new token.\\n\\n## Execution Plan\\nPhase 1: Contracts — 3 weeks\\n\\nPhase 2: User interface widget + landing page, — 3 weeks\\n\\nPhase 3: Testing, Bug fixing & Documentation — 2 weeks\\n\\nPhase 4: Deployment and Launch — 1 week\\n\\n## Fund Release Plan\\nBudget: 450,000 BOS\\n\\nWe plan to have 2 C++ developers to develop the contracts, 1 UI developer for landing + interfaces and 1 product manager that will test, document and organize project for approximately 3 months duration. We will also use the budget for marketing, integrations and hosting.\\n\\nEthereum had last year a grant of 100,000$ for the same project. We believe we can make it for less than half of the Ethereum budget.\\n\\n## Team\\nThe team behind Nebula Protocol ( https://nebulaprotocol.com/ ) are very experienced in develop solutions for EOSIO Blockchains. We have 2 fulltime C++ developers that will take care of the contracts and 1 frontend engineer who will create the widget and libraries needed to accomplish the project.\\n\\n## Relevant Links\\nhttps://uniswap.io\\n\\nhttps://hackmd.io/s/HJ9jLsfTz\\n\\nhttps://ethresear.ch/t/improving-front-running-resistance-of-x-y-k-market-makers/1281\\n\\nhttps://firstblock.news/news/46270bbf-6b3d-34ca-83f4-555cfc7162ef\\n\\nhttps://www.coindesk.com/bancor-uniswap-dex-competition\\n\\nhttps://blog.ethereum.org/2018/08/17/ethereum-foundation-grants-update-wave-3/\",\"type\":\"referendum-v1\"}", + "created_at": "2019-05-26T13:43:13" + }, + "stats": { + "votes": { + "1": 25, + "total": 25, + "proxies": 4, + "accounts": 21 + }, + "accounts": { + "0": 0, + "1": 26046570429, + "total": 26046570429 + }, + "proxies": { + "0": 0, + "1": 29993720939, + "total": 29993720939 + }, + "staked": { + "0": 0, + "1": 56040291368, + "total": 56040291368 + }, + "block_num": 43385214 + } + }, + "operations11": { + "id": "operations11_20190603", + "proposal": { + "proposal_name": "operations11", + "proposer": "pacificproxy", + "title": "Community Governance & Daily Operations ", + "proposal_json": "{\"content\":\"\\n\\nThe proposal will be implemented from January 25st.\\n\\n\\n\\n## Proposal background\\n\\n\\n\\nBOSCore is a community-initiated EOS side chain. We could see that any public chain is ultimately inseparable from governance. Governance is the catalyst for ecological growth. Governance is the cohesive force of community development. Community governance plays a different role in each stage of the public chain development. The role of organizing community members to participate in the discussion of ecological construction, could condense the BOSCore community consensus, expand the influence of BOSCore brand, and force to help BOSCore ecological prosperity.\\n\\n\\n\\nBOS Pacific is the BOSCore node team initiated by Node Pacific Tech. Node Pacific is the world's largest public chain operation crowdsourcing platform and node operator. Currently, it participates in the core block nodes of nearly 20 mainstream public chains domestic and overseas.In-depth participation in public chain ecological operations, and leading community governance, such as the successful creation of EOS core governance community EMAC, IOST core governance community ICAC, GXChain core governance community GCAC, Lambda core governance community LCAC.\\n\\n\\n\\nBOS Pacific is also looking forward a lot to contributing to the ecological management of BOSCore with a wealth of community governance experience.\\n\\n\\n\\n## Proposal information\\n\\n\\n\\nBasic information\\n\\n\\n\\n1. Proposal name: Proposal for the construction of core governance domestic and overseas communities & daily operation\\n\\n \\n\\n2. Submit function points: core governance community\\n\\n \\n\\n3. The latest submission time after the proposal is passed:January 23 - June 25（long-term operation in the future)\\n\\n \\n\\n## Proposal content\\n\\n\\n\\nBOS Pacific will launch the BOSCore core governance community, call on the partners who are interested in governance in the BOSCore ecosystem to join the BOSCore core governance community BCAC.\\n\\n\\n\\nBCAC does not have arbitration function, does not participate in governance implementation, and only conducts training and education for BOSCore governance, aiming to converge the BOSCore community consensus.\\n\\n\\n\\nBCAC hopes to continue to build and improve the BOSCore governance community, attract global blockchain technology and governance enthusiasts to understand and participate in BOSCore, build a rich and diverse governance communication community for BOSCore, and gradually transform BOSCore into community-based governance and expand continuously. The cohesiveness of BOSCore forms a powerful and irreplaceable consensus mechanism.\\n\\n\\n\\n## Proposal execute\\n\\n\\n\\n-- Governance community expansion\\n\\n\\n\\n -- Commission establishment & committee development \\n\\n\\n\\n--The media announcement \\n\\n\\n\\n--Community bounty Community governance\\n\\n\\n\\n### \\n\\n### 1.Governance community expansion \\n\\n\\n\\nThe BOSCore core governance community has expanded to 400+, collecting user opinions and suggestions, and actively organizing and conducting a series of community activities, including: community user topic discussion, topic sharing, node interview, conference organization, etc.\\n\\n\\n\\na. Discussion topic introduction: Take a topic discussion as an example to prepare the process: \\n\\n\\n\\nBefore the topic discussion: \\n\\n\\n\\n-- Make a microphone form to collect community user questions and suggestions \\n\\n\\n\\n-- Communicate with community users and guide community users to fill out forms \\n\\n\\n\\n-- Discuss with the committee members to select topics to discuss and discuss in the BCAC community \\n\\n\\n\\n-- Identify topic discussion time and topic, communicate with community users, and prepare activity materials before the topic discussion (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the topic discussion: \\n\\n\\n\\n-- Hosting and guiding community users to discuss, after content discussion topics are discussed: -- Communicate with community users to understand the feelings and shortcomings of the experience, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\n\\n\\nb. Topic sharing introduction: Take a topic sharing as an example to prepare the process: \\n\\n\\n\\nBefore sharing the topic: \\n\\n\\n\\n-- Communicate with the node, the application party, and the project party to determine the theme and time to share, and prepare the activity materials before the sharing (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the topic sharing: \\n\\n\\n\\n-- Hosting and guiding community users to participate and ask questions. After sharing the topic: \\n\\n\\n\\n-- Communicate with the users and share the guests to understand the feelings and experiences, and organize the articles (both Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nc. Node exclusive interview: Take one node exclusive interview as an example to prepare the process:\\n\\n\\n\\nBefore the interview: \\n\\n\\n\\n-- Prepare an interview, contact the node and communicate the content and form of the interview, determine the theme and time, and prepare the activity materials before the sharing (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the interview: \\n\\n\\n\\n--hosting, and make questions \\n\\n\\n\\nAfter the interview: \\n\\n\\n\\n-- Organizing and publishing articles (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nd.Meeting: Take a meeting as an example to prepare the process: \\n\\n\\n\\nBefore the meeting: \\n\\n\\n\\n-- Communicate frequently with community users, node teams, committees, and identify and determine meeting themes and times \\n\\n\\n\\n-- Inviting guests to the meeting, and preparing to share the pre-event materials (poster, media announcement, copy preparation), and the notice of meeting \\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Identify invited guests, host, guide community users to participate and express opinions and suggestions, content \\n\\n\\n\\nAfter the meeting: Communicate with the users and share the guests to understand the feelings and experiences, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\n\\n\\n\\n\\n### 2.Commission establishment & committee development \\n\\n\\n\\nConduct committee recruitment activities (filtrating & communication & campaign & establishment); establish committee charter (write & modify & confirm); establish proposal application process; continue to export quality proposals for BOSCore community; frequently communicate with members to help promote committee members' work Track and execute the proposal; provide BOS rewards to committees that have made actual contributions, and call more people to join BOSCore's ecological construction. \\n\\n\\n\\nProposal: Prepare the process with a proposal as an example: \\n\\n\\n\\n-- Before the proposal: Communicate frequently with community users, nodes, project parties, and application parties, tap their expertise, promote feasibility proposals, and guide them to write proposals based on the proposal template;\\n\\n\\n\\n -- Proposal: Submit proposals and assist in advancing the work of the proposed members, follow up on the proposal process; and call for more people to join BOSCore's ecological construction; \\n\\n\\n\\n-- After the proposal: The designated secretary department follows up on the progress of the proposal and reports it regularly.\\n\\n\\n\\n\\n\\n### 3.Media announcement\\n\\n\\n\\nSet up channels for media outlets domestic and overseas export high-quality articles for BOSCore. Eacha article and official event will be announced in the communities and officials. Party platform promotion. The publishing platform includes, but is not limited to, Wechat public web, Weibo, Bihu, Mars Finance, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc., each number of reading will over 10,000 totally.\\n\\n\\n\\n\\n\\n### 4.Community bounty\\n\\n\\n\\nIn order to encourage the community to develop better and mobilize more participating users, Bounty live domestic and overseas will be non scheduled (such as UGC,activity execution, interactive sharing, DApp recommendation, etc.)\\n\\n\\n\\n## Proposal target\\n\\n\\n\\n1. The total number of community members will be increased to 400+;\\n\\n \\n\\n2. Unscheduled topic discussion or topic sharing (at least once a month), Chinese and English node exclusive interviews at least one week, online meeting 1-2 sessions per week;\\n\\n \\n\\n3. Collect proposal 4+;\\n\\n \\n\\n4. Original articles 5+, publishing platform: Wechat public web, Weibo,Bihu, Mars, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc. (Chinese and English channels, covering 100,000+ users, reading over 200,000+) Ps: The average number of single meetings is not less than 10% of the BCAC community.\\n\\n \\n\\n\\n\\n## Proposal budget\\n\\n\\n\\n\\n\\nApplication for funding : total 530,000 BOS \\n\\n\\n\\nCommunity operating costs (manpower, material, market) 430000\\n\\n\\n\\nCommunity Incentives (Committee & Community Bounty) - 100,000 (with invented clarity)\\n\\n\\n\\n\\n\\n------\\n\\n\\n\\n提案从1月23日开始执行\\n\\n\\n\\n## 提案背景\\n\\n\\n\\nBOSCore是由社区发起的EOS侧链，我们能看到任何一条公链最终都离不开治理，治理是生态壮大的催化剂，治理是社区发展的凝聚力量，社区治理在公链各个阶段发挥着不同的作用， 组织社区成员参与生态建设的讨论，能够凝聚BOSCore社区共识，扩大BOSCore品牌影响 力，助力BOSCore生态繁荣。\\n\\n\\n\\nBOS Pacific是由Node Pacific Tech（节点亚太）发起的BOSCore节点团队，Node Pacific 是全球最大的公链运营众包平台和节点运营商，目前参与了国内外近20条主流公链的核心出块节点；深度参与公链生态运营，并主导社区治理，如成功打造EOS核心治理社区EMAC， IOST核心治理社区ICAC，公信链核心治理社区GCAC，Lambda核心治理社区LCAC等。 BOS Pacific也非常期望能带着较为丰富的社区治理经验，为BOSCore的生态治理搭建贡献一份力量。\\n\\n\\n\\n## 提案信息\\n\\n\\n\\n基本信息 \\n\\n\\n\\n1、提案名称：BOSCore海内外核心治理社区搭建&日常运营提案\\n\\n\\n\\n 2、提交功能点：核心治理社区 \\n\\n\\n\\n3、提案在公投通过后最晚提交时间：1月23日-6月25日(未来会长期运营）\\n\\n\\n\\n## 提案内容\\n\\n\\n\\nBOS Pacific会发起BOSCore核心治理社区，号召BOSCore生态中对治理感兴趣的小伙伴加入，共建BOSCore核心治理社区BCAC。\\n\\n\\n\\nBCAC不具备仲裁功能，不参与治理执行，仅做BOSCore治理的培训和教育，旨在凝聚BOSCore社区共识。\\n\\n\\n\\nBCAC希望能够持续推进搭建、完善BOSCore治理社区，吸引全球区块链技术以及治理爱好者了解，参与BOSCore，为BOSCore搭建一个丰富多样的治理交流社区，逐步将BOSCore向社区化治理逐步过渡，不断扩大BOSCore的凝聚力，形成强有力、不可替代的共识机制。\\n\\n\\n\\n## 提案执行\\n\\n\\n\\n--治理社区的扩展\\n\\n\\n\\n--委员会成立&委员会发展 \\n\\n\\n\\n--媒体宣发 \\n\\n\\n\\n--社区bounty\\n\\n\\n\\n\\n\\n\\n\\n社区治理\\n\\n\\n\\n\\n\\n### 1.治理社区的扩展 \\n\\n\\n\\nBOSCore核心治理社区人员扩充至400+，收集用户意见和建议，积极组织和开展一系列社区活动，方式包括：社区用户话题讨论，主题分享，节点专访，会议组织等。\\n\\n\\n\\na. 话题讨论介绍：以一次话题讨论为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n话题讨论前： \\n\\n\\n\\n--制作麦克表单收集社区用户问题和建议 \\n\\n\\n\\n--和社区用户沟通并引导社区用户填写表单 \\n\\n\\n\\n--和委员会成员讨论选取可讨论的话题，在BCAC社区进行讨论 \\n\\n\\n\\n--确定话题讨论时间与主题，和社区用户沟通，同时准备话题讨论前的活动材料（海报，媒体宣发，文案准备） \\n\\n\\n\\n话题讨论间： \\n\\n\\n\\n--主持、引导社区用户讨论，内容整理话题讨论后：\\n\\n\\n\\n--和社区用户沟通了解心得感受及不足之处，内容传播（中英文，海内外平台）\\n\\n\\n\\nb. 主题分享介绍：以一次主题分享为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n主题分享前： \\n\\n\\n\\n--和节点、应用方、项目方沟通确定可分享的主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备）\\n\\n\\n\\n主题分享间： \\n\\n\\n\\n--主持、引导社区用户参与并提出问题，内容整理\\n\\n\\n\\n主题分享后： \\n\\n\\n\\n--和提问用户及分享嘉宾沟通了解感受及心得，整理宣发文章（中英文，海内外平台）\\n\\n\\n\\nc. 节点专访：以一次节点专访为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n专访前： \\n\\n\\n\\n--准备专访问题，联系节点并沟通专访内容、形式，确定主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备） \\n\\n\\n\\n专访间： \\n\\n\\n\\n--主持、提问、内容整理专访后： \\n\\n\\n\\n--整理宣发文章（中英文，海内外平台）\\n\\n\\n\\n\\n\\nd. 会议：以一次会议为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n会议前： \\n\\n\\n\\n--和社区用户、节点团队、委员会频繁沟通，挖掘和确定会议主题和时间 \\n\\n\\n\\n--邀请会议嘉宾，同时准备分享前的活动材料（海报，媒体宣发，文案准备）、预告\\n\\n\\n\\n会议中： \\n\\n\\n\\n--确定邀请嘉宾，主持，引导社区用户参与并发表意见和建议，内容整理 \\n\\n\\n\\n会议后：\\n\\n\\n\\n和提问用户及分享嘉宾沟通了解感受及心得，内容传播（中英文，海内外平台）\\n\\n\\n\\n\\n\\n\\n\\n### 2.委员会成立&委员会发展 \\n\\n\\n\\n展开委员会招募活动（筛选&沟通&竞选&成立）；确立委员会章程（撰写&修改&确认）； 确立提案申请流程；持续为BOSCore社区输出优质提案；频繁与成员沟通，协助推进委员会成员的工作内容；对提案进行跟踪和执行；对有实际贡献的委员会提供BOS奖励，号召更多人加入BOSCore的生态建设。\\n\\n\\n\\n提案：以一次提案为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n--提案前：和社区用户，节点、项目方、应用方频繁沟通，挖掘他们的擅长点，促成可行性提案，同时引导他们根据提案模版撰写提案； \\n\\n\\n\\n--提案间：提交提案，并协助推进提案成员的工作内容，跟进提案进程；同时号召更多人加入BOSCore的生态建设； \\n\\n\\n\\n--提案后：指定秘书部成员跟进提案进展，并定期汇报。\\n\\n\\n\\n\\n\\n\\n\\n### 3.媒体宣发 \\n\\n\\n\\n搭建海内外媒体宣发渠道，为BOSCore输出优质文章，每一次文章和官方活动都会在社区和官方平台宣传。 发布平台包括且不限于：公众号、微博、币乎、火星财经、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等，每篇总阅读量过1万。\\n\\n\\n\\n\\n\\n\\n\\n### 4.社区bounty \\n\\n\\n\\n为了激励社区更好发展，调动更多参与用户，会不定期进行海内外社区Bounty（如UGC，活动执行，互动分享，DApp推荐等）\\n\\n\\n\\n\\n\\n## 提案目标\\n\\n\\n\\n1. 社区总人数增至400+；\\n\\n \\n\\n2. 不定期举行话题讨论或主题分享（每月至少一次）、中英文节点专访每周至少一篇、线上会议每周1-2 场；\\n\\n \\n\\n3. 收集提案4+；\\n\\n \\n\\n4. 原创文章5+，发布平台：公众号、微博、币乎、火星、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等； （中英文渠道，覆盖10万＋用户，阅读量过20万＋） 补充：平均单次会议人数不少于BCAC社群人数10%\\n\\n \\n\\n\\n\\n## 提案预算\\n\\n\\n\\n申请经费：总额53万 BOS \\n\\n\\n\\n社区运营成本（人员，物料，市场）--43万 \\n\\n\\n\\n社区激励（委员会&社区bounty）--10万（附带分发明晰）\",\"type\":\"referendum-v1\",\"incentives\":\"530000.0000\",\"receiptor\":\"bospacificok\"}", + "created_at": "2019-06-03T06:10:31" + }, + "stats": { + "votes": { + "0": 1, + "1": 43, + "total": 44, + "proxies": 16, + "accounts": 28 + }, + "accounts": { + "0": 8805746, + "1": 51772804417, + "total": 51781610163 + }, + "proxies": { + "0": 0, + "1": 94900094787, + "total": 94900094787 + }, + "staked": { + "0": 8805746, + "1": 146672899204, + "total": 146681704950 + }, + "block_num": 43385214 + } + }, + "operations14": { + "id": "operations14_20190529", + "proposal": { + "proposal_name": "operations14", + "proposer": "pacificproxy", + "title": "Community Governance & Daily Operations Stage 1", + "proposal_json": "{\"content\":\"\\n\\nThe proposal will be implemented from May 1st.\\n\\n\\n\\n## Proposal background\\n\\n\\n\\nBOSCore is a community-initiated EOS side chain. We could see that any public chain is ultimately inseparable from governance. Governance is the catalyst for ecological growth. Governance is the cohesive force of community development. Community governance plays a different role in each stage of the public chain development. The role of organizing community members to participate in the discussion of ecological construction, could condense the BOSCore community consensus, expand the influence of BOSCore brand, and force to help BOSCore ecological prosperity.\\n\\n\\n\\nBOS Pacific is the BOSCore node team initiated by Node Pacific Tech. Node Pacific is the world's largest public chain operation crowdsourcing platform and node operator. Currently, it participates in the core block nodes of nearly 20 mainstream public chains domestic and overseas.In-depth participation in public chain ecological operations, and leading community governance, such as the successful creation of EOS core governance community EMAC, IOST core governance community ICAC, GXChain core governance community GCAC, Lambda core governance community LCAC.\\n\\n\\n\\nBOS Pacific is also looking forward a lot to contributing to the ecological management of BOSCore with a wealth of community governance experience.\\n\\n\\n\\n## Proposal information\\n\\n\\n\\nBasic information\\n\\n\\n\\n1. Proposal name: Proposal for the construction of core governance domestic and overseas communities & daily operation\\n\\n \\n\\n2. Submit function points: core governance community\\n\\n \\n\\n3. The latest submission time after the proposal is passed: two months\\n\\n \\n\\n4. The proposal will be executed in two phases (first phase: May 1 - May 31, second phase June 1 - June 30)\\n\\n \\n\\n## Proposal content\\n\\n\\n\\nBOS Pacific will launch the BOSCore core governance community, call on the partners who are interested in governance in the BOSCore ecosystem to join the BOSCore core governance community BCAC.\\n\\n\\n\\nBCAC does not have arbitration function, does not participate in governance implementation, and only conducts training and education for BOSCore governance, aiming to converge the BOSCore community consensus.\\n\\n\\n\\nBCAC hopes to continue to build and improve the BOSCore governance community, attract global blockchain technology and governance enthusiasts to understand and participate in BOSCore, build a rich and diverse governance communication community for BOSCore, and gradually transform BOSCore into community-based governance and expand continuously. The cohesiveness of BOSCore forms a powerful and irreplaceable consensus mechanism.\\n\\n\\n\\n## Proposal execute\\n\\n\\n\\n-- Governance community expansion\\n\\n\\n\\n -- Commission establishment & committee development \\n\\n\\n\\n--The media announcement \\n\\n\\n\\n--Community bounty Community governance\\n\\n\\n\\n### \\n\\n### 1.Governance community expansion \\n\\n\\n\\nThe BOSCore core governance community has expanded to 400+, collecting user opinions and suggestions, and actively organizing and conducting a series of community activities, including: community user topic discussion, topic sharing, node interview, conference organization, etc.\\n\\n\\n\\na. Discussion topic introduction: Take a topic discussion as an example to prepare the process: \\n\\n\\n\\nBefore the topic discussion: \\n\\n\\n\\n-- Make a microphone form to collect community user questions and suggestions \\n\\n\\n\\n-- Communicate with community users and guide community users to fill out forms \\n\\n\\n\\n-- Discuss with the committee members to select topics to discuss and discuss in the BCAC community \\n\\n\\n\\n-- Identify topic discussion time and topic, communicate with community users, and prepare activity materials before the topic discussion (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the topic discussion: \\n\\n\\n\\n-- Hosting and guiding community users to discuss, after content discussion topics are discussed: -- Communicate with community users to understand the feelings and shortcomings of the experience, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\n\\n\\nb. Topic sharing introduction: Take a topic sharing as an example to prepare the process: \\n\\n\\n\\nBefore sharing the topic: \\n\\n\\n\\n-- Communicate with the node, the application party, and the project party to determine the theme and time to share, and prepare the activity materials before the sharing (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the topic sharing: \\n\\n\\n\\n-- Hosting and guiding community users to participate and ask questions. After sharing the topic: \\n\\n\\n\\n-- Communicate with the users and share the guests to understand the feelings and experiences, and organize the articles (both Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nc. Node exclusive interview: Take one node exclusive interview as an example to prepare the process:\\n\\n\\n\\nBefore the interview: \\n\\n\\n\\n-- Prepare an interview, contact the node and communicate the content and form of the interview, determine the theme and time, and prepare the activity materials before the sharing (poster, media announcement, copy preparation) \\n\\n\\n\\nDuring the interview: \\n\\n\\n\\n--hosting, and make questions \\n\\n\\n\\nAfter the interview: \\n\\n\\n\\n-- Organizing and publishing articles (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nd.Meeting: Take a meeting as an example to prepare the process: \\n\\n\\n\\nBefore the meeting: \\n\\n\\n\\n-- Communicate frequently with community users, node teams, committees, and identify and determine meeting themes and times \\n\\n\\n\\n-- Inviting guests to the meeting, and preparing to share the pre-event materials (poster, media announcement, copy preparation), and the notice of meeting \\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Identify invited guests, host, guide community users to participate and express opinions and suggestions, content \\n\\n\\n\\nAfter the meeting: Communicate with the users and share the guests to understand the feelings and experiences, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\n\\n\\n\\n\\n### 2.Commission establishment & committee development \\n\\n\\n\\nConduct committee recruitment activities (filtrating & communication & campaign & establishment); establish committee charter (write & modify & confirm); establish proposal application process; continue to export quality proposals for BOSCore community; frequently communicate with members to help promote committee members' work Track and execute the proposal; provide BOS rewards to committees that have made actual contributions, and call more people to join BOSCore's ecological construction. \\n\\n\\n\\nProposal: Prepare the process with a proposal as an example: \\n\\n\\n\\n-- Before the proposal: Communicate frequently with community users, nodes, project parties, and application parties, tap their expertise, promote feasibility proposals, and guide them to write proposals based on the proposal template;\\n\\n\\n\\n -- Proposal: Submit proposals and assist in advancing the work of the proposed members, follow up on the proposal process; and call for more people to join BOSCore's ecological construction; \\n\\n\\n\\n-- After the proposal: The designated secretary department follows up on the progress of the proposal and reports it regularly.\\n\\n\\n\\n\\n\\n### 3.Media announcement\\n\\n\\n\\nSet up channels for media outlets domestic and overseas export high-quality articles for BOSCore. Eacha article and official event will be announced in the communities and officials. Party platform promotion. The publishing platform includes, but is not limited to, Wechat public web, Weibo, Bihu, Mars Finance, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc., each number of reading will over 10,000 totally.\\n\\n\\n\\n\\n\\n### 4.Community bounty\\n\\n\\n\\nIn order to encourage the community to develop better and mobilize more participating users, Bounty live domestic and overseas will be non scheduled (such as UGC,activity execution, interactive sharing, DApp recommendation, etc.)\\n\\n\\n\\n## Proposal target\\n\\n\\n\\n1. The total number of community members will be increased to 400+;\\n\\n \\n\\n2. Unscheduled topic discussion or topic sharing (at least once a month), Chinese and English node exclusive interviews at least one week, online meeting 1-2 sessions per week;\\n\\n \\n\\n3. Collect proposal 2+;\\n\\n \\n\\n4. Original articles 5+, publishing platform: Wechat public web, Weibo,Bihu, Mars, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc. (Chinese and English channels, covering 100,000+ users, reading over 200,000+) Ps: The average number of single meetings is not less than 10% of the BCAC community.\\n\\n \\n\\n\\n\\n## Proposal budget\\n\\n\\n\\n\\n\\nApplication for funding at the first phase: total 200,000 BOS \\n\\n\\n\\nCommunity operating costs (manpower, material, market) 150,000 \\n\\n\\n\\nCommunity Incentives (Committee & Community Bounty) - 50,000 (with invented clarity)\\n\\n\\n\\n\\n\\n------\\n\\n\\n\\n提案从5月1日开始执行\\n\\n\\n\\n## 提案背景\\n\\n\\n\\nBOSCore是由社区发起的EOS侧链，我们能看到任何一条公链最终都离不开治理，治理是生态壮大的催化剂，治理是社区发展的凝聚力量，社区治理在公链各个阶段发挥着不同的作用， 组织社区成员参与生态建设的讨论，能够凝聚BOSCore社区共识，扩大BOSCore品牌影响 力，助力BOSCore生态繁荣。\\n\\n\\n\\nBOS Pacific是由Node Pacific Tech（节点亚太）发起的BOSCore节点团队，Node Pacific 是全球最大的公链运营众包平台和节点运营商，目前参与了国内外近20条主流公链的核心出块节点；深度参与公链生态运营，并主导社区治理，如成功打造EOS核心治理社区EMAC， IOST核心治理社区ICAC，公信链核心治理社区GCAC，Lambda核心治理社区LCAC等。 BOS Pacific也非常期望能带着较为丰富的社区治理经验，为BOSCore的生态治理搭建贡献一份力量。\\n\\n\\n\\n## 提案信息\\n\\n\\n\\n基本信息 \\n\\n\\n\\n1、提案名称：BOSCore海内外核心治理社区搭建&日常运营提案\\n\\n\\n\\n 2、提交功能点：核心治理社区 \\n\\n\\n\\n3、提案在公投通过后最晚提交时间：两个月 \\n\\n\\n\\n4、提案分两个阶段实施（第一个阶段：5月1日-5月31日，第二个阶段6月1日-6月30日）\\n\\n\\n\\n## 提案内容\\n\\n\\n\\nBOS Pacific会发起BOSCore核心治理社区，号召BOSCore生态中对治理感兴趣的小伙伴加入，共建BOSCore核心治理社区BCAC。\\n\\n\\n\\nBCAC不具备仲裁功能，不参与治理执行，仅做BOSCore治理的培训和教育，旨在凝聚BOSCore社区共识。\\n\\n\\n\\nBCAC希望能够持续推进搭建、完善BOSCore治理社区，吸引全球区块链技术以及治理爱好者了解，参与BOSCore，为BOSCore搭建一个丰富多样的治理交流社区，逐步将BOSCore向社区化治理逐步过渡，不断扩大BOSCore的凝聚力，形成强有力、不可替代的共识机制。\\n\\n\\n\\n## 提案执行\\n\\n\\n\\n--治理社区的扩展\\n\\n\\n\\n--委员会成立&委员会发展 \\n\\n\\n\\n--媒体宣发 \\n\\n\\n\\n--社区bounty\\n\\n\\n\\n\\n\\n\\n\\n社区治理\\n\\n\\n\\n\\n\\n### 1.治理社区的扩展 \\n\\n\\n\\nBOSCore核心治理社区人员扩充至400+，收集用户意见和建议，积极组织和开展一系列社区活动，方式包括：社区用户话题讨论，主题分享，节点专访，会议组织等。\\n\\n\\n\\na. 话题讨论介绍：以一次话题讨论为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n话题讨论前： \\n\\n\\n\\n--制作麦克表单收集社区用户问题和建议 \\n\\n\\n\\n--和社区用户沟通并引导社区用户填写表单 \\n\\n\\n\\n--和委员会成员讨论选取可讨论的话题，在BCAC社区进行讨论 \\n\\n\\n\\n--确定话题讨论时间与主题，和社区用户沟通，同时准备话题讨论前的活动材料（海报，媒体宣发，文案准备） \\n\\n\\n\\n话题讨论间： \\n\\n\\n\\n--主持、引导社区用户讨论，内容整理话题讨论后：\\n\\n\\n\\n--和社区用户沟通了解心得感受及不足之处，内容传播（中英文，海内外平台）\\n\\n\\n\\nb. 主题分享介绍：以一次主题分享为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n主题分享前： \\n\\n\\n\\n--和节点、应用方、项目方沟通确定可分享的主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备）\\n\\n\\n\\n主题分享间： \\n\\n\\n\\n--主持、引导社区用户参与并提出问题，内容整理\\n\\n\\n\\n主题分享后： \\n\\n\\n\\n--和提问用户及分享嘉宾沟通了解感受及心得，整理宣发文章（中英文，海内外平台）\\n\\n\\n\\nc. 节点专访：以一次节点专访为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n专访前： \\n\\n\\n\\n--准备专访问题，联系节点并沟通专访内容、形式，确定主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备） \\n\\n\\n\\n专访间： \\n\\n\\n\\n--主持、提问、内容整理专访后： \\n\\n\\n\\n--整理宣发文章（中英文，海内外平台）\\n\\n\\n\\n\\n\\nd. 会议：以一次会议为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n会议前： \\n\\n\\n\\n--和社区用户、节点团队、委员会频繁沟通，挖掘和确定会议主题和时间 \\n\\n\\n\\n--邀请会议嘉宾，同时准备分享前的活动材料（海报，媒体宣发，文案准备）、预告\\n\\n\\n\\n会议中： \\n\\n\\n\\n--确定邀请嘉宾，主持，引导社区用户参与并发表意见和建议，内容整理 \\n\\n\\n\\n会议后：\\n\\n\\n\\n和提问用户及分享嘉宾沟通了解感受及心得，内容传播（中英文，海内外平台）\\n\\n\\n\\n\\n\\n\\n\\n### 2.委员会成立&委员会发展 \\n\\n\\n\\n展开委员会招募活动（筛选&沟通&竞选&成立）；确立委员会章程（撰写&修改&确认）； 确立提案申请流程；持续为BOSCore社区输出优质提案；频繁与成员沟通，协助推进委员会成员的工作内容；对提案进行跟踪和执行；对有实际贡献的委员会提供BOS奖励，号召更多人加入BOSCore的生态建设。\\n\\n\\n\\n提案：以一次提案为例\\n\\n\\n\\n准备流程： \\n\\n\\n\\n--提案前：和社区用户，节点、项目方、应用方频繁沟通，挖掘他们的擅长点，促成可行性提案，同时引导他们根据提案模版撰写提案； \\n\\n\\n\\n--提案间：提交提案，并协助推进提案成员的工作内容，跟进提案进程；同时号召更多人加入BOSCore的生态建设； \\n\\n\\n\\n--提案后：指定秘书部成员跟进提案进展，并定期汇报。\\n\\n\\n\\n\\n\\n\\n\\n### 3.媒体宣发 \\n\\n\\n\\n搭建海内外媒体宣发渠道，为BOSCore输出优质文章，每一次文章和官方活动都会在社区和官方平台宣传。 发布平台包括且不限于：公众号、微博、币乎、火星财经、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等，每篇总阅读量过1万。\\n\\n\\n\\n\\n\\n\\n\\n### 4.社区bounty \\n\\n\\n\\n为了激励社区更好发展，调动更多参与用户，会不定期进行海内外社区Bounty（如UGC，活动执行，互动分享，DApp推荐等）\\n\\n\\n\\n\\n\\n## 提案目标\\n\\n\\n\\n1. 社区总人数增至400+；\\n\\n \\n\\n2. 不定期举行话题讨论或主题分享（每月至少一次）、中英文节点专访每周至少一篇、线上会议每周1-2 场；\\n\\n \\n\\n3. 收集提案2+；\\n\\n \\n\\n4. 原创文章5+，发布平台：公众号、微博、币乎、火星、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等； （中英文渠道，覆盖10万＋用户，阅读量过20万＋） 补充：平均单次会议人数不少于BCAC社群人数10%\\n\\n \\n\\n\\n\\n## 提案预算\\n\\n\\n\\n第一阶段申请经费：总额20万 BOS \\n\\n\\n\\n社区运营成本（人员，物料，市场）--15万 \\n\\n\\n\\n社区激励（委员会&社区bounty）--5万（附带分发明晰）\",\"type\":\"referendum-v1\",\"incentives\":\"200000.0000\",\"receiptor\":\"bospacificok\"}", + "created_at": "2019-05-29T05:47:31" + }, + "stats": { + "votes": { + "total": 0, + "proxies": 0, + "accounts": 0 + }, + "accounts": { + "0": 0, + "1": 0, + "total": 0 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 0, + "total": 0 + }, + "block_num": 43385214 + } + }, + "operations15": { + "id": "operations15_20190529", + "proposal": { + "proposal_name": "operations15", + "proposer": "pacificproxy", + "title": "Community Governance & Daily Operations Stage 2", + "proposal_json": "{\"content\":\"\\n\\nThe proposal will be implemented from May 1st.\\n\\n\\n\\n# Proposal background\\n\\n\\n\\nBOSCore is a community-initiated EOS side chain. We could see that any public chain is ultimately inseparable from governance. Governance is the catalyst for ecological growth. Governance is the cohesive force of community development. Community governance plays a different role in each stage of the public chain development. The role of organizing community members to participate in the discussion of ecological construction, could condense the BOSCore community consensus, expand the influence of BOSCore brand, and force to help BOSCore ecological prosperity.\\n\\n\\n\\nBOS Pacific is the BOSCore node team initiated by Node Pacific Tech. Node Pacific is the world's largest public chain operation crowdsourcing platform and node operator. Currently, it participates in the core block nodes of nearly 20 mainstream public chains domestic and overseas.In-depth participation in public chain ecological operations, and leading community governance, such as the successful creation of EOS core governance community EMAC, IOST core governance community ICAC, GXChain core governance community GCAC, Lambda core governance community LCAC.\\n\\n\\n\\nBOS Pacific is also looking forward a lot to contributing to the ecological management of BOSCore with a wealth of community governance experience.\\n\\n# Proposal information\\n\\n\\n\\nBasic information\\n\\n\\n\\n1. Proposal name: Proposal for the construction of core governance domestic and overseas communities & daily operation\\n\\n \\n\\n2. Submit function points: core governance community\\n\\n \\n\\n3. The latest submission time after the proposal is passed: two months\\n\\n \\n\\n4. The proposal will be executed in the second phase ： June 1 - June 30\\n\\n\\n\\n# Proposal content\\n\\n\\n\\nBOS Pacific will launch the BOSCore core governance community, call on the partners who are interested in governance in the BOSCore ecosystem to join the BOSCore core governance community BCAC.\\n\\n\\n\\nBCAC does not have arbitration function, does not participate in governance implementation, and only conducts training and education for BOSCore governance, aiming to converge the BOSCore community consensus.\\n\\n\\n\\nBCAC hopes to continue to build and improve the BOSCore governance community, attract global blockchain technology and governance enthusiasts to understand and participate in BOSCore, build a rich and diverse governance communication community for BOSCore, and gradually transform BOSCore into community-based governance and expand continuously. The cohesiveness of BOSCore forms a powerful and irreplaceable consensus mechanism.\\n\\n\\n\\n# Proposal execute\\n\\n\\n\\n-- Governance community expansion\\n\\n\\n\\n-- Commission establishment & committee development\\n\\n\\n\\n--The media announcement\\n\\n\\n\\n--Community bounty Community governance\\n\\n\\n\\n\\n\\n### 1.Governance community expansion \\n\\n\\n\\nThe BOSCore core governance community has expanded to 400+, collecting user opinions and suggestions, and actively organizing and conducting a series of community activities, including: community user topic discussion, topic sharing, node interview, conference organization, etc.\\n\\n\\n\\na. Discussion topic introduction: Take a topic discussion as an example to prepare the process:\\n\\n\\n\\nBefore the topic discussion:\\n\\n\\n\\n-- Make a microphone form to collect community user questions and suggestions\\n\\n\\n\\n-- Communicate with community users and guide community users to fill out forms\\n\\n\\n\\n-- Discuss with the committee members to select topics to discuss and discuss in the BCAC community\\n\\n\\n\\n-- Identify topic discussion time and topic, communicate with community users, and prepare activity materials before the topic discussion (poster, media announcement, copy preparation)\\n\\n\\n\\nDuring the topic discussion:\\n\\n\\n\\n-- Hosting and guiding community users to discuss, after content discussion topics are discussed:\\n\\n\\n\\n-- Communicate with community users to understand the feelings and shortcomings of the experience, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nb. Topic sharing introduction: Take a topic sharing as an example to prepare the process:\\n\\n\\n\\nBefore sharing the topic:\\n\\n\\n\\n-- Communicate with the node, the application party, and the project party to determine the theme and time to share, and prepare the activity materials before the sharing (poster, media announcement, copy preparation)\\n\\n\\n\\nDuring the topic sharing: \\n\\n\\n\\n-- Hosting and guiding community users to participate and ask questions. After sharing the topic:\\n\\n\\n\\n-- Communicate with the users and share the guests to understand the feelings and experiences, and organize the articles (both Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nc. Node exclusive interview: Take one node exclusive interview as an example to prepare the process:\\n\\n\\n\\nBefore the interview: \\n\\n\\n\\n-- Prepare an interview, contact the node and communicate the content and form of the interview, determine the theme and time, and prepare the activity materials before the sharing (poster, media announcement, copy preparation)\\n\\n\\n\\nDuring the interview: \\n\\n\\n\\n--hosting, and make questions\\n\\n\\n\\nAfter the interview: \\n\\n\\n\\n-- Organizing and publishing articles (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\nd.Meeting: Take a meeting as an example to prepare the process:\\n\\n\\n\\nBefore the meeting:\\n\\n\\n\\n-- Communicate frequently with community users, node teams, committees, and identify and determine meeting themes and times\\n\\n\\n\\n-- Inviting guests to the meeting, and preparing to share the pre-event materials (poster, media announcement, copy preparation), and the notice of meeting\\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Identify invited guests, host, guide community users to participate and express opinions and suggestions, content\\n\\n\\n\\nAfter the meeting: Communicate with the users and share the guests to understand the feelings and experiences, content dissemination (Chinese and English, domestic and overseas platforms)\\n\\n\\n\\n\\n\\n### 2.Commission establishment & committee development\\n\\n### \\n\\nConduct committee recruitment activities (filtrating & communication & campaign & establishment); establish committee charter (write & modify & confirm); establish proposal application process; continue to export quality proposals for BOSCore community; frequently communicate with members to help promote committee members' work Track and execute the proposal; provide BOS rewards to committees that have made actual contributions, and call more people to join BOSCore's ecological construction.\\n\\n\\n\\nProposal: Prepare the process with a proposal as an example:\\n\\n\\n\\n-- Before the proposal: Communicate frequently with community users, nodes, project parties, and application parties, tap their expertise, promote feasibility proposals, and guide them to write proposals based on the proposal template; \\n\\n\\n\\n-- Proposal: Submit proposals and assist in advancing the work of the proposed members, follow up on the proposal process; and call for more people to join BOSCore's ecological construction;\\n\\n\\n\\n-- After the proposal: The designated secretary department follows up on the progress of the proposal and reports it regularly.\\n\\n\\n\\n\\n\\n### 3.Media announcement\\n\\n\\n\\nSet up channels for media outlets domestic and overseas export high-quality articles for BOSCore. Eacha article and official event will be announced in the communities and officials. Party platform promotion.\\n\\n\\n\\nThe publishing platform includes, but is not limited to, Wechat public web, Weibo, Bihu, Mars Finance, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc., each number of reading will over 10,000 totally.\\n\\n### \\n\\n\\n\\n### 4.Community bounty\\n\\n\\n\\nIn order to encourage the community to develop better and mobilize more participating users, Bounty live domestic and overseas will be non scheduled (such as UGC,activity execution, interactive sharing, DApp recommendation, etc.)\\n\\n\\n\\n\\n\\n## Proposal target\\n\\n\\n\\n1. The total number of community members will be increased to 400+;\\n\\n \\n\\n2. Unscheduled topic discussion or topic sharing (at least once a month), Chinese and English node exclusive interviews at least one week, online meeting 1-2 sessions per week;\\n\\n \\n\\n3. Collect proposal 2+;\\n\\n \\n\\n4. Original articles 5+, publishing platform: Wechat public web, Weibo,Bihu, Mars, Gyro Finance, Facebook, Twitter,Reddit, steemit, medium, starteos, bos.sh, EOS newsletter, etc. (Chinese and English channels, covering 100,000+ users, reading over 200,000+)\\n\\n \\n\\nPs: The average number of single meetings is not less than 10% of the BCAC community.\\n\\n\\n\\n\\n\\n## Proposal budget\\n\\n\\n\\nApplication for funding at the second phase: total 200,000 BOS\\n\\n\\n\\nCommunity operating costs (manpower, material, market) 150,000\\n\\n\\n\\nCommunity Incentives (Committee & Community Bounty) - 500,000 (with invented clarity)\\n\\n\\n\\n\\n\\n------\\n\\n\\n\\n提案从5月1日开始执行\\n\\n\\n\\n\\n\\n## 提案背景\\n\\n\\n\\n\\n\\nBOSCore是由社区发起的EOS侧链，我们能看到任何一条公链最终都离不开治理，治理是生态壮大的催化剂，治理是社区发展的凝聚力量，社区治理在公链各个阶段发挥着不同的作用， 组织社区成员参与生态建设的讨论，能够凝聚BOSCore社区共识，扩大BOSCore品牌影响力，助力BOSCore生态繁荣。\\n\\n\\n\\nBOS Pacific是由Node Pacific Tech（节点亚太）发起的BOSCore节点团队，Node Pacific 是全球最大的公链运营众包平台和节点运营商，目前参与了国内外近20条主流公链的核心出块节点；深度参与公链生态运营，并主导社区治理，如成功打造EOS核心治理社区EMAC， IOST核心治理社区ICAC，公信链核心治理社区GCAC，Lambda核心治理社区LCAC等。\\n\\n\\n\\nBOS Pacific也非常期望能带着较为丰富的社区治理经验，为BOSCore的生态治理搭建贡献一份力量。\\n\\n\\n\\n\\n\\n## 提案信息\\n\\n\\n\\n基本信息\\n\\n\\n\\n1、提案名称：BOSCore海内外核心治理社区搭建&日常运营提案\\n\\n\\n\\n2、提交功能点：核心治理社区\\n\\n\\n\\n3、提案在公投通过后最晚提交时间：两个月\\n\\n\\n\\n4、提案第二阶段：6月1日-6月30日\\n\\n\\n\\n\\n\\n## 提案内容\\n\\n\\n\\nBOS Pacific会发起BOSCore核心治理社区，号召BOSCore生态中对治理感兴趣的小伙伴加入，共建BOSCore核心治理社区BCAC。\\n\\n\\n\\nBCAC不具备仲裁功能，不参与治理执行，仅做BOSCore治理的培训和教育，旨在凝聚BOSCore社区共识。\\n\\n\\n\\nBCAC希望能够持续推进搭建、完善BOSCore治理社区，吸引全球区块链技术以及治理爱好者了解，参与BOSCore，为BOSCore搭建一个丰富多样的治理交流社区，逐步将BOSCore向社区化治理逐步过渡，不断扩大BOSCore的凝聚力，形成强有力、不可替代的共识机制。\\n\\n\\n\\n\\n\\n## 提案执行\\n\\n\\n\\n--治理社区的扩展\\n\\n\\n\\n--委员会成立&委员会发展\\n\\n\\n\\n--媒体宣发\\n\\n\\n\\n--社区bounty\\n\\n\\n\\n社区治理\\n\\n\\n\\n\\n\\n### 1.治理社区的扩展\\n\\n\\n\\nBOSCore核心治理社区人员扩充至400+，收集用户意见和建议，积极组织和开展一系列社区活动，方式包括：社区用户话题讨论，主题分享，节点专访，会议组织等。\\n\\n\\n\\na. 话题讨论介绍：以一次话题讨论为例准备流程：\\n\\n\\n\\n话题讨论前：\\n\\n\\n\\n--制作麦克表单收集社区用户问题和建议\\n\\n\\n\\n--和社区用户沟通并引导社区用户填写表单\\n\\n\\n\\n--和委员会成员讨论选取可讨论的话题，在BCAC社区进行讨论\\n\\n\\n\\n--确定话题讨论时间与主题，和社区用户沟通，同时准备话题讨论前的活动材料（海报，媒体宣发，文案准备）\\n\\n\\n\\n话题讨论间：\\n\\n\\n\\n--主持、引导社区用户讨论，内容整理话题讨论后：\\n\\n\\n\\n--和社区用户沟通了解心得感受及不足之处，内容传播（中英文，海内外平台）\\n\\n\\n\\nb. 主题分享介绍：以一次主题分享为例准备流程：\\n\\n\\n\\n主题分享前：\\n\\n\\n\\n--和节点、应用方、项目方沟通确定可分享的主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备）\\n\\n\\n\\n主题分享间：\\n\\n\\n\\n--主持、引导社区用户参与并提出问题，内容整理主题分享后：\\n\\n\\n\\n--和提问用户及分享嘉宾沟通了解感受及心得，整理宣发文章（中英文，海内外平台）\\n\\n\\n\\nc. 节点专访：以一次节点专访为例准备流程：\\n\\n\\n\\n专访前：\\n\\n\\n\\n--准备专访问题，联系节点并沟通专访内容、形式，确定主题和时间，同时准备分享前的活动材料（海报，媒体宣发，文案准备）\\n\\n\\n\\n专访间：\\n\\n\\n\\n--主持、提问、内容整理专访后：\\n\\n\\n\\n--整理宣发文章（中英文，海内外平台）\\n\\n\\n\\nd. 会议：以一次会议为例准备流程：\\n\\n\\n\\n会议前：\\n\\n\\n\\n--和社区用户、节点团队、委员会频繁沟通，挖掘和确定会议主题和时间\\n\\n\\n\\n--邀请会议嘉宾，同时准备分享前的活动材料（海报，媒体宣发，文案准备）、预告会议中：\\n\\n\\n\\n--确定邀请嘉宾，主持，引导社区用户参与并发表意见和建议，内容整理\\n\\n\\n\\n会议后：和提问用户及分享嘉宾沟通了解感受及心得，内容传播（中英文，海内外平台）\\n\\n\\n\\n\\n\\n### 2.委员会成立&委员会发展\\n\\n\\n\\n展开委员会招募活动（筛选&沟通&竞选&成立）；确立委员会章程（撰写&修改&确认）； 确立提案申请流程；持续为BOSCore社区输出优质提案；频繁与成员沟通，协助推进委员会成员的工作内容；对提案进行跟踪和执行；对有实际贡献的委员会提供BOS奖励，号召更多人加入BOSCore的生态建设。\\n\\n\\n\\n提案：以一次提案为例准备流程：\\n\\n\\n\\n--提案前：和社区用户，节点、项目方、应用方频繁沟通，挖掘他们的擅长点，促成可行性提案，同时引导他们根据提案模版撰写提案；\\n\\n\\n\\n--提案间：提交提案，并协助推进提案成员的工作内容，跟进提案进程；同时号召更多人加入BOSCore的生态建设；\\n\\n\\n\\n--提案后：指定秘书部成员跟进提案进展，并定期汇报。\\n\\n### \\n\\n\\n\\n### 3.媒体宣发\\n\\n\\n\\n搭建海内外媒体宣发渠道，为BOSCore输出优质文章，每一次文章和官方活动都会在社区和官方平台宣传。\\n\\n\\n\\n发布平台包括且不限于：公众号、微博、币乎、火星财经、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等，每篇总阅读量过1万。\\n\\n\\n\\n\\n\\n### 4.社区bounty\\n\\n\\n\\n为了激励社区更好发展，调动更多参与用户，会不定期进行海内外社区Bounty（如UGC，活动执行，互动分享，DApp推荐等）\\n\\n\\n\\n\\n\\n## 提案目标\\n\\n\\n\\n1. 社区总人数增至400+；\\n\\n \\n\\n2. 不定期举行话题讨论或主题分享（每月至少一次）、中英文节点专访每周至少一篇、线上会议每周1-2 场；\\n\\n\\n\\n3. 收集提案2+；\\n\\n \\n\\n4. 原创文章5+，发布平台：公众号、微博、币乎、火星、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等；\\n\\n \\n\\n（中英文渠道，覆盖10万＋用户，阅读量过20万＋） 补充：平均单次会议人数不少于BCAC社群人数10%\\n\\n\\n\\n\\n\\n# 提案预算\\n\\n\\n\\n第一阶段申请经费：总额20万 BOS\\n\\n\\n\\n社区运营成本（人员，物料，市场）--15万\\n\\n\\n\\n社区激励（委员会&社区bounty）--5万（附带分发明晰）\",\"type\":\"referendum-v1\",\"incentives\":\"200000.0000\",\"receiptor\":\"bospacificok\"}", + "created_at": "2019-05-29T06:11:31" + }, + "stats": { + "votes": { + "1": 1, + "total": 1, + "proxies": 0, + "accounts": 1 + }, + "accounts": { + "0": 0, + "1": 28301, + "total": 28301 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 28301, + "total": 28301 + }, + "block_num": 43385214 + } + }, + "simpassets11": { + "id": "simpassets11_20190615", + "proposal": { + "proposal_name": "simpassets11", + "proposer": "dancinglions", + "title": "Improve Simple Assets and Deploy to Bos Core / ＃改进简单资产（Simple Assets）并部署至Bos Core", + "proposal_json": "{\"content\":\"-----\nImprove Simple Assets and Deploy to Bos Core / ＃改进简单资产（Simple Assets）并部署至Bos Core\nsimpassets11\n261875\ndec, 2019\n-----\n\n\n# Improve Simple Assets and Deploy to Bos Core\n\n\n## What is Simple Assets?\n\nSimple Assets is an elegant, powerful Digital Asset standard for EOSIO blockchains.\n\nFor users, it’s a guarantee of ownership of digital items.\n\nFor developers, it saves hundreds of hours, and also makes their assets available for buying, selling and borrowing on various market places.\n\nSimple Assets supports for fungible and non-fungible tokens, renting assets, containerizing them, batch functionality, alerts for easier tracking, and more.\n\n\n## How can a dapp use Simple Assets?\n\nThere are two ways:\n\n1) They can call the contract simpleassets on the EOS mainnet. (We are in the process of deploying it to sister chains as well.) The contract is like a Dapp for Dapps. To ensure that control of the contract is decentralized, we are creating the multisig described above.\n\n2) Dapps can take our opensource standard and deploy it themselves with our without modifications. The mutlisign described in this article would then not apply. In this case the onus is on the Dapp.\n\n\n## What Improvements do we want to make to Simple Assets?\n\n* Allow change of `author` . This will allow games to send their items to other games.\n\n* Create and maintain a separate Github repo from which developers can self-deploy Simple Assets.\n\n* Improve Chinese translation.\n\n* Create more supporting documentation.\n\n\n## Road Map\n\n![Simple Assets Roadmap English](https://cryptolions.io/wp-content/uploads/2019/06/bos-SA-roadmap-en.png)\n\n\n## Funding\n\n| **Task** | **est. hours** | **BOS** |\n| ------------------------------ |:-------------:| ----- |\n| New Features (change author) | 120 | 112500 |\n| Github for self-deployment | 60 | 56250 |\n| improved translations | 30 | 9375 |\n| | | |\n| Deploy with improvements to BOS | 20 | 18750 |\n| Organize Multi Sig with BOS BPs | 40 | 25000 |\n| Organize Multi-Language Resources for Developers | 80 | 40000 |\n| **Total:** | | 261,875 |\n\n\n## Contact\n\nEmail:\nroman@cryptolions.io\nshe@cryptolions.io\n\nTelegram: https://t.me/CryptoLions_io\n\nWeChat: SHE18347264709\n\nInformation:\n\nhttps://medium.com/@cryptolions\nhttps://github.com/cryptolions/simpleassets\n\nAnnouncing Simple Assets:\nhttps://medium.com/@cryptolions/announcing-simple-assets-v0-1-1-e04dce8f2c02\nhttps://medium.com/@cryptolions/eosio%E5%8C%BA%E5%9D%97%E9%93%BE%E6%95%B0%E5%AD%97%E4%BA%A7%E5%93%81-simple-assets-alpha-%E7%AE%80%E4%BB%8B-71e26d4cbb71\n\nOwnership Authority:\nhttps://medium.com/@cryptolions/digital-assets-we-need-to-think-about-ownership-authority-a2b0465c17f6\nhttps://medium.com/@cryptolions/%E6%95%B0%E5%AD%97%E8%B5%84%E4%BA%A7-%E6%88%91%E4%BB%AC%E9%9C%80%E8%A6%81%E8%80%83%E8%99%91-%E6%89%80%E6%9C%89%E6%9D%83-b5f1a8368046\n\n\n==========\n\n\n＃改进简单资产（Simple Assets）并部署至Bos Core\n\n## 什么是简单资产（Simple Assets）？\n\n简单资产（Simple Assets）是EOSIO区块链的优雅，强大的数字资产标准。\n\n对于用户来说，它是数字项目所有权的保证。\n\n\n对于开发人员来说，它可以节省数百小时，并且还可以在各种市场上购买，出售和借用资产。\n\n简单资产（Simple Assets）支持可替代和不可替代的代币，租用资产，将其容纳，批处理功能，警报以便于跟踪等。\n\n## dapp如何使用简单资产（Simple Assets）？\n\n有两种方法：\n\n1）他们可以在EOS主网上调用simpleassets合约。\n\n（我们也正在将它部署到其它EOS姐妹链中。）合约就像Dapps的Dapp。为了确保合约的控制权是分散的，我们正在创建上述的多签（multisig）。\n\n2）Dapps可以采用我们的开源标准，并在没有修改的情况下自行部署。然后，本文中描述的多签（mutlisign）将不适用时。在这种情况下，责任在Dapp上。\n\n\n## 我们想对简单资产（Simple Assets）做哪些改进？\n\n* 允许更改`author`。这将允许游戏将他们的项目发送到其他游戏。\n\n* 创建并维护一个单独的Github库，开发人员可以从中自行部署Simple Assets.ddd\n\n* 改进中文翻译。\n\n* 创建更多支持文档。\n\n## 路线图\n\n![Simple Assets Roadmap Chinese](https://cryptolions.io/wp-content/uploads/2019/06/bos-SA-roadmap-cn.png)\n\n\n## 基金\n\n| **任务** | **时间， 小时** | **BOS** |\n| ------------------------------ |:-------------:| ----- |\n| 新功能（更改资产创建者） | 120 | 112500 |\n| Github进行自我部署 | 60 | 56250 |\n| 改进翻译 | 30 | 9375 |\n| | | |\n| 改进并部署至BOS | 20 | 18750 |\n| 在BOS中组织BPs 多签（Multi Sig） | 40 | 25000 |\n| 为开发人员提供更多语言版本资源 | 80 | 40000 |\n| **总计:** | | 261,875 |\n\n\n## 联系\n\nEmail:\n\nroman@cryptolions.io\nshe@cryptolions.io\n\nTelegram: https：//t.me/CryptoLions_io\n\n微信： SHE18347264709\n\nInfo：\n\nhttps://medium.com/@cryptolions\nhttps://github.com/cryptolions/simpleassets\n\n宣布简单资产(Simple Assets)：/n/nhttps://medium.com/@cryptolions/announcing-simple-assets-v0-1-1-e04dce8f2c02\nhttps://medium.com/@cryptolions/eosio%E5%8C%BA%E5%9D%97%E9%93%BE%E6%95%B0%E5%AD%97%E4%BA%A7%E5%93%81-simple-assets-alpha-%E7%AE%80%E4%BB%8B-71e26d4cbb71\n\n所有权机构：\n\nhttps://medium.com/@cryptolions/digital-assets-we-need-to-think-about-ownership-authority-a2b0465c17f6\nhttps://medium.com/@cryptolions/%E6%95%B0%E5%AD%97%E8%B5%84%E4%BA%A7-%E6%88%91%E4%BB%AC%E9%9C%80%E8%A6%81%E8%80%83%E8%99%91-%E6%89%80%E6%9C%89%E6%9D%83-b5f1a8368046\n\n\",\"type\":\"referendum-v1\",\"incentives\":\"261875.0000\",\"receiptor\":\"bosbornforbb\"}", + "created_at": "2019-06-15T13:56:52" + }, + "stats": { + "votes": { + "1": 6, + "total": 6, + "proxies": 2, + "accounts": 4 + }, + "accounts": { + "0": 0, + "1": 2062277371, + "total": 2062277371 + }, + "proxies": { + "0": 0, + "1": 3152076126, + "total": 3152076126 + }, + "staked": { + "0": 0, + "1": 5214353497, + "total": 5214353497 + }, + "block_num": 43385214 + } + }, + "trainingcpcp": { + "id": "trainingcpcp_20190529", + "proposal": { + "proposal_name": "trainingcpcp", + "proposer": "pacificproxy", + "title": "BOSCore Training Course", + "proposal_json": "{\"content\":\"## **Background to the proposal**\\n\\n\\n\\nBOS ecological management is developing, BCAC (BOS core governance community) has been completed. At present, the next development direction of the whole BOS community is not clear, the community members have different knowledge and understanding of BOS, and the understanding of BOS governance rules is not very clear. Therefore, professional training courses are needed to make a unified science popularization for community users, so that new users can also quickly and conveniently understand BOS, and participate in and invest in BOS, which is very important to expand the number of BOS users. Only when more and more people realize the advantages and irreplaceable nature of BOS More and more people are involved in BOS ecology. Therefore, this proposal will give a series of training programs, clear the direction of the initial development of the BCAC community.\\n\\n \\n\\n## **Proposal information** \\n\\n\\n\\n Essential information \\n\\n \\n\\n1. Proposal name: BOS Professional training Curriculum Construction and Curriculum Promotion proposal\\n\\n \\n\\n2. Submit functional points: training, promotion\\n\\n \\n\\n3. The latest submission time of the proposal after the referendum is adopted: (June 3-August 31）two months at the latest\\n\\n \\n\\n\\n\\n## Content of the proposal\\n\\n\\n\\nSet up a series of BOS related education and training courses to systematically train community members.\\n\\n \\n\\nSyllabus (for reference only):\\n\\n \\n\\n①BOS basic knowledge and its Development course (2 times 3 classes)\\n\\n \\n\\n②BOS basic technical details, such as master network startup details, BOS intelligent contract writing, security issues, etc. (2 / 3 classes)\\n\\n \\n\\n③The composition of the BOS global community, the main BP introduction and the main character introduction, etc. (1 lesson)\\n\\n \\n\\n④A detailed explanation of BOS Ecological Management Model (1 / 2 classes)\\n\\n \\n\\n⑤Detailed explanation of BOS assessor system (1 / 2 classes)\\n\\n \\n\\n⑥Introduction by BCAF arbitral tribunal (1 class)\\n\\n \\n\\n⑦Detailed explanation of the EOS Convention, main issues for amending the Convention and preparations for referendums. (1 / 2 classes)\\n\\n \\n\\n\\n\\n \\n\\n## **Implementation of proposals**\\n\\n\\n\\n1.The ZOOM meeting discusses the proposal and confirms the final course.\\n\\n\\n\\n2.After the meeting, the host will pull the group and confirm the specific time of the lecturer.\\n\\n\\n\\n3.The propaganda of domestic media and overseas media.\\n\\n \\n\\n\\n\\n\\n\\n1.The proposal discussed at the ZOOM meeting and the confirmation of the final course.\\n\\n \\n\\nBCAC community launches meetings, poster production and community promotion\\n\\n \\n\\nA.The sponsor describes the content of the proposal and where it needs to be discussed at the meeting, and perfects the proposal at the meeting.\\n\\n \\n\\nPersonnel arrangement (operation 2 + design 1)\\n\\n \\n\\nPrior to the meeting:\\n\\n \\n\\nPrepare the PPT content of the training course, as well as the preheating (poster, personnel, copywriting, equipment preparation) meeting room before the meeting:\\n\\n \\n\\n2.after presiding over and maintaining the order of the meeting in Chinese and English, and guiding the participants to participate in the question meeting:\\n\\n \\n\\nCommunicate with participants to understand needs and facilitate proposals\\n\\n \\n\\n-collation and dissemination of the contents of the meeting\\n\\n \\n\\nAfter the meeting, the host pulled the group and confirmed the specific time of the lecturer.\\n\\n \\n\\nConfirmation of the specific time of the lecturer\\n\\n \\n\\nStaffing arrangements (operation 1)\\n\\n \\n\\nPreparation process:\\n\\n \\n\\n-pull the group and negotiate\\n\\n \\n\\nComplete the form of the specific lecturer and the teaching time\\n\\n \\n\\n3.Promotion of domestic media and overseas media\\n\\n \\n\\na. The push of the WeChat public number\\n\\n \\n\\nFollow-up:\\n\\n \\n\\nA follow-up report on the progress of the proposal\\n\\n \\n\\nb. The push of overseas Media\\n\\n \\n\\n\\n\\n## **Proposal objective**\\n\\n \\n\\n1.Identify BOS community systematic training courses, and determine trainers and training time.\\n\\n \\n\\n2.Complete the training course, than through the media channel to publish the training course to the entire community.\\n\\n \\n\\n3.Lower the threshold for new community members to understand BOS.\\n\\n \\n\\n4.Through this training course to explore the advantages and characteristics of BOS community members, to pave the way for the subsequent revision of the BOS Convention.\\n\\n \\n\\nAddition: the average number of single meetings is not less than 10 per cent of the BCAC community\\n\\n\\n\\n\\n\\n## **Proposed budget**\\n\\n \\n\\nApplication funds: total 250000 BOS (training courses, promotion)\\n\\n\\n\\n\\n\\n------\\n\\n\\n\\n## 提案背景\\n\\n\\n\\nBOS生态治理正在展开，BCAC（BOS核心治理社区）已经构建完成。目前整个BOS社区的下一步发展方向还未明确，社区成员对于BOS的认识和了解程度各不相同，对于BOS治理细则的了解还不是十分清楚，所以需要专业性的培训课程来对社区用户做一个统一的科普，使得新用户也可以快捷方便的了解BOS，从而参与和投资BOS，这对于扩大BOS的用户量是十分重要的。只有越来越多的人认识到了BOS的优势和不可替代性才有越来越多的人参与到BOS生态之中。所以本提案将给出一系列的培训大纲，明确BCAC社区初期发展的方向。\\n\\n\\n\\n## 提案信息\\n\\n\\n\\n基本信息\\n\\n\\n\\n1、提案名称：BOS专业性培训课程构建及课程推广提案\\n\\n\\n\\n2、提交功能点：培训、推广\\n\\n\\n\\n3、提案在公投通过后最晚提交时间：两个月（6月3日-8月31日）\\n\\n \\n\\n \\n\\n## 提案内容\\n\\n\\n\\n创立一系列的BOS相关教育培训课程，对社区成员进行系统化培训。\\n\\n\\n\\n课程大纲（仅供参考）：\\n\\n\\n\\n①BOS基础知识及其发展历程（2-3次课）\\n\\n\\n\\n②BOS基础技术细节，如主网启动细节，BOS智能合约的编写，安全问题等（2-3次课）\\n\\n\\n\\n③BOS全球社区的构成，主要的BP简介以及主要的人物介绍等（1次课）\\n\\n\\n\\n④BOS生态治理模式详解（1-2次课）\\n\\n\\n\\n⑤BOS评审员制度详解（1-2次课）\\n\\n\\n\\n⑥BCAF仲裁庭介绍（1次课）\\n\\n\\n\\n⑦EOS公约详解，修订公约的主要问题以及公投的准备工作。（1-2次课）\\n\\n \\n\\n \\n\\n \\n\\n \\n\\n## 提案执行\\n\\n\\n\\n1. ZOOM会议进行提案的讨论以及最终课程的确认。\\n\\n \\n\\n2. 会后由主持人进行拉群并进行授课人具体时间确认。\\n\\n \\n\\n3. 国内媒体及海外媒体的宣传。\\n\\n \\n\\n\\n\\n \\n\\n### 1.ZOOM会议进行的提案讨论以及最终课程的确认。\\n\\n\\n\\n\\n\\nBCAC社区进行发起会议、海报的制作及社区的推广\\n\\n\\n\\na. 提案人讲述提案内容以及需要会议讨论的地方，并在会议上进行提案的完善。\\n\\n\\n\\nb. 人员安排（运营2+设计1）\\n\\n\\n\\n会议前：\\n\\n\\n\\n--准备培训课程讲演PPT内容，同时准备会议前的预热（海报，人员，文案，设备准备） 会议间：\\n\\n\\n\\n--中英文主持与维持会议秩序，并引导参会人员参与提问会议后：\\n\\n\\n\\n--和参会人员沟通了解需求和促成提案\\n\\n\\n\\n--会议内容的整理和宣发\\n\\n \\n\\n \\n\\n\\n\\n### 2.会后主持人拉群并进行授课人具体时间确认。\\n\\n \\n\\na. 授课人具体时间确认\\n\\n\\n\\n人员安排（运营1）\\n\\n\\n\\n准备流程：\\n\\n\\n\\n--拉群并协商\\n\\n\\n\\n--完成具体授课人及授课时间的表单\\n\\n\\n\\n \\n\\n \\n\\n \\n\\n### 3.国内媒体及海外媒体的宣传\\n\\n \\n\\na.微信公众号的推送\\n\\n\\n\\n后续：\\n\\n\\n\\n提案进展的跟踪报道\\n\\n\\n\\nB. 海外媒体的推送\\n\\n \\n\\n \\n\\n \\n\\n## 提案目标\\n\\n \\n\\n1. 确定BOS社区系统化培训课程，并确定培训人员以及培训时间。\\n\\n \\n\\n2. 完成整套培训课程，比通过媒体渠道将培训课程发布到整个社区。\\n\\n \\n\\n3. 降低新进社区成员了解BOS的门槛。\\n\\n \\n\\n4. 通过此次培训课程发掘BOS社区成员的优势以及特点，为之后的BOS公约修订做铺垫。\\n\\n \\n\\n补充：平均单次会议人数不少于BCAC社群人数10%\\n\\n \\n\\n \\n\\n \\n\\n## 提案预算\\n\\n \\n\\n申请经费：总额 25万 BOS（培训课程、推广）\\n\\n\",\"type\":\"referendum-v1\",\"incentives\":\"250000.0000\",\"receiptor\":\"victor233333\"}", + "created_at": "2019-05-29T08:45:49" + }, + "stats": { + "votes": { + "1": 4, + "total": 4, + "proxies": 1, + "accounts": 3 + }, + "accounts": { + "0": 0, + "1": 24000, + "total": 24000 + }, + "proxies": { + "0": 0, + "1": 1146991705, + "total": 1146991705 + }, + "staked": { + "0": 0, + "1": 1147015705, + "total": 1147015705 + }, + "block_num": 43385214 + } + }, + "unicocaptain": { + "id": "unicocaptain_20190821", + "proposal": { + "proposal_name": "unicocaptain", + "proposer": "unicocaptain", + "title": "Unico平台-BOS游戏专属推广基金", + "proposal_json": "{\"content\":\"## 提案名称\\n\\nUnico平台-BOS游戏专属推广基金\\n\\n## 问题\\n\\n- BOS生态的问题，用户基数少，用户以僵尸用户和羊毛党为主，游戏日活很低；\\n\\n- EOSIO游戏生态流量分散问题，当前市场缺乏可以对接多个公链的游戏，将各个公链的流量进行整合、汇总和相互倒流的游戏平台；\\n\\n- 目前链游领域还无专业的发行平台，导致游戏开发者需要分散大量精力对接不同渠道，协同推进游戏发行和运营，无法专注在开发优质游戏上。\\n\\n## Unico游戏平台\\n\\n Unico搭建了BOS全网的首个游戏平台，引入BOS全网首款高质量RPG“驯龙大师”，并且为“驯龙大师”提供了全面的运营资源，包括并且不限于免费BOS账户、客服、直播资源、PR、BOS空投等；Unico游戏平台为BOS生态做出了独特的贡献。\\n\\n## 激励细则\\n\\n 由Unico积极引进优质的游戏dApp到BOS上；对表现优秀的游戏dApp给予激励；按照以下的规则发放给游戏dApp：\\n\\n1. 综合考虑游戏dApp的活跃用户数和交易量决定排名，根据排名进行激励发放；\\n2. 游戏dApp活跃度排名越靠前，所获激励越多；\\n3. 分批把币直接打到游戏dApp分红合约账户，一旦发现他们私自挪用就剥夺资格并且拉黑；\\n4. 奖励以 BOS 形式发放。\\n\\n**要求** 启动初期：dApp必须拥有超过50个每日活跃用户（DAU）或其24小时交易量（VOL）必须超过2000BOS。 注明：后期会根据实际情况进行调整；\\n\\n**注意** 数据收集从每周一00:00开始（UTC），每周日（UTC）23:59结束。每日活跃用户是指每周平均DAU，每日交易量是每周平均每日交易量。\\n\\n如果排名中的合格dApp数量低于20，则前5名dApp将根据其活动和每日交易量每周共享20,000 BOS 的奖金池。 如果排名中合格的dApp数量在20到50之间，前十名dApp将根据其活动和每日交易量每周共享50,000BOS的奖池。\\n\\n启动初期：按照游戏日活激励 50人起步，奖励2万个BOS 100人起步，奖励5万个BOS 200人起步，奖励10万个BOS 注明：后期会根据实际情况进行调整；\\n\\n## 基金拨款和配置\\n\\n项目成本是多少，资金应该如何配置？ 50万，unico平台空投致游戏分红合约账户；10万账户补贴，40万游戏基金。 专款专用，unico不会挪用，全部按照严格的标准和规则发放BOS生态里的dApp，帮助dApp提高对客户激励奖池以及进行媒体PR。\\n\\n## Unico平台介绍方案\\n\\n1. 游戏发行\\n\\n- Unico为DApp游戏开发者提供全套游戏发行服务，包含定制化的游戏预售和游戏运营服务；\\n- 对于传统游戏开发商，Unico可以为其做链改，并且对接相应的公链团队争取基金会奖励；\\n- 0渠道分成！任何游戏可以轻松入驻；\\n\\n![图片](https://wx3.sinaimg.cn/mw690/006mODl1gy1g67g9ag4iqj3091054414.jpg)\\n\\n2. 用户社区\\n\\n- 用户社区涵盖了OGC、PGC和UGC内容；\\n- UT的运用会大大激励玩家社区中的内容产出质量和数量，并且有多种创意玩法激活用户的激情，营造良好的游戏社区氛围；\\n- 社区POS节点设计，让用户积极参与社区治理；\\n\\n![图片](https://wx2.sinaimg.cn/mw690/006mODl1gy1g67g9dwgtuj309l05mgng.jpg)\\n\\n3. 通过第三方OTC提供游戏付费通道\\n\\n- 为入驻链游提供\\n\\n 稳定\\n\\n 的链上结算方案 —— UB游戏积分支付体系\\n\\n - UB购买价格恒定 1 UB = 1 RMB\\n - 进行游戏购买\\n - 游戏内消费 （通过道具交易/领取分红）获取UB\\n - 由合规的专业OTC商家提供，保证7*24小时稳定\\n\\n![图片](https://wx2.sinaimg.cn/mw690/006mODl1gy1g67g9g482dj306d09nmxq.jpg)\\n\\n4. 游戏交易市场\\n\\n- **游戏资产代币化和多链钱包**\\n\\n 提供通用的标准化游戏资产协议（含NFT），可以在不同游戏中继承和共享游戏资产。\\n\\n- **内置代币交易合约**\\n\\nUB-BOS交易合约和游戏币-UB交易对，所有Unico的游戏都可免费调用，用户可以在游戏内快速进行代币转换。\\n\\n- **FT资产交易所+NFT资产交易所**\\n\\nUnico自带FT&NFT交易所，用户可以直接在交易所交易自己的链游游戏资产，无需登录游戏。 采用标准：dGoods轻量化和灵活化的模式，并通过提供强大的虚拟物品标准为EOSIO生态提供代币逻辑扩展能力。（曾接受EOS Galaxy投资的游戏Mythical.Games，提出广为接受的代币标准dGoods。） 具体参考: https://github.com/MythicalGames/dgoods\\n\\n## 相关链接\\n\\n[https://unico.one](https://unico.one/)\",\"type\":\"referendum-v1\",\"incentives\":\"500000.0000 BOS\",\"receiptor\":\"unicocaptain\"}", + "created_at": "2019-08-21T11:27:11" + }, + "stats": { + "votes": { + "0": 1, + "1": 9, + "total": 10, + "proxies": 9, + "accounts": 1 + }, + "accounts": { + "0": 2000, + "1": 0, + "total": 2000 + }, + "proxies": { + "0": 0, + "1": 34507804731, + "total": 34507804731 + }, + "staked": { + "0": 2000, + "1": 34507804731, + "total": 34507806731 + }, + "block_num": 43385214 + } + }, + "unicorntube1": { + "id": "unicorntube1_20190605", + "proposal": { + "proposal_name": "unicorntube1", + "proposer": "nicholasyao1", + "title": "UnicornTube —— A Bos Storge", + "proposal_json": "{\"content\":\"【UnicornTube proposal】\\nProposal background：\\n1. The BOS block has limited storage space and needs a distributed network that can handle large file storage.\\nAt the end of 2017, Ethereum was congested by the whole network because of “a cat”. This cat is a CryptoKitties. Secondly, Bitcoin is also often congested by the network, which leads to huge transactions that cannot be confirmed. One of the reasons is that the block size is limited. This is like our computer, the capacity is getting smaller and smaller, the computer will become more and more stuck, and even crashes. As the strongest side chain BOS of EOS, it also needs to face the problem of expansion. In the future, there will be more DApp access and more people participating, which will generate more and more transactions and data. New solutions to meet future needs, and combining with IPFS technology is a good attempt.\\n\\n2. Unsafe centralized storage\\nEquifax, one of the three major US credit rating agencies, learned of the hacker attack on July 29 and announced the news more than a month later. About 209,000 people have stolen their credit card numbers and 182,000 people have their personal identification information stolen, causing huge losses. The largest information disclosure case in history warns of the potential problems with centralized management of this data, and distributed storage technology can reduce this large data breach.\\n\\nThe main content of the proposal:\\nThe proposal name is UnicornTube, the project 1.0 product will realize the global movie video sharing and aggregation platform based on BOS blockchain + IPFS technology; UnicornTube 2.0 realizes the cloud document management platform of distributed storage on the chain. IPFS technology enables large file transfer and distributed storage, helping users to commercialize idle storage space through sharing, and realize content value through video sharing.( more pictures: https://mp.weixin.qq.com/s/OLvAMjibOKwtvpXZHUS5Qg)\\n\\nTechnically, it is based on the combination of IPFS and BOS networking technologies. IPFS network technology is responsible for the distributed storage and distribution of files, and then the BOS network is responsible for the basic operations of smart contracts, IPFS file hashing, and account management and network connections.\\n\\n1.0 launched the UnicornTube video platform. Users can perform registration, login, video browsing, uploading, etc., while supporting interactive operations such as likes, comments, rewards, and related management functions of digital wallets. The UnicornTube video platform has two main smart contracts, one for video uploads and one for ad bidding. When users upload files, they need to use BOS to pay a certain fee. The video files will be transmitted to the operation team for review. After the audit is successful, the video files will be added to the IPFS network, and the hash value obtained by the IPFS calculation file (in the form of Memo) is chained to the BOS blockchain. Advertising bidding smart contracts, different positions or types of ads will have a minimum bid price for advertisers to bid, for example, 10 BOS start, the successful bidder can hang in the approximate position to maintain a week of advertising. Advertisers can bid through our official portal. He can select the ad slot and the number of BOS he wants to bid, and use the BOS wallet to call the smart contract method on our webpage to complete the auction. At the same time, the official will show the current real-time auction details. Then, after the auction is over, the smart contract judges that the bidding order with the highest bid wins and can choose to upload the advertising content, which will be displayed at the corresponding moment. Advertisers who fail to bid will refund BOS.\\n\\nSo what is the difference between UnicornTube and traditional video platforms?\\n1, using HLS live broadcast technology, allowing users to watch smooth, and reduce unnecessary bandwidth overhead, using IPFS technology to distribute content, faster than traditional video platform, with a better viewing experience.\\n2, the traditional video platform storage once the hacker breaks through, the loss is huge, and UnicornTube decentralized storage uses P2P distributed technology to allow the accessed resources to be scattered in each user's software client, fragmentation The resources are stored and the files are encrypted. The security is higher than that of the centralized video platform.\\n3, the traditional advertising by the platform side unified pricing, pricing is not free, is not conducive to advertisers; and UnicornTube platform advertising market determines the final price, pricing is free, the market demand determines the price.\\n4, the traditional film and television platform requires the platform to bear the high cost of bandwidth and hardware alone, so that the profit margin that can be distributed to the creators is relatively small, and UnicornTube is to use the idle resources shared by the society, naturally there is more profit space. Give to the creator. At the same time, the creators who browse the total timetable will have high token rewards.\\n5. On UnicornTube, active behaviors such as frequent viewing, praise and commentary have the opportunity to obtain certain airdrop rewards, so that viewers can make money by watching movies. This is the advantage that traditional video platforms do not have.\\n\\nHowever, the blockchain video platform is not what we ultimately want to do. The 1.0 version is a product transition phase. After the 1.0 version of the video platform is completed, we will develop more challenging office application scenarios and bring the real charm of distributed storage. It is the highlight of the life of everyone.\\n\\nProject 2.0 will introduce a distributed file management client that supports more file type storage. It allows each user to customize a cloud of blockchain technology. All files have a hash link, designed to Everyone provides permanent storage capacity. The user can purchase the storage capacity package on the client and upload the file to the private cloud disk. The private cloud disk cannot be directly viewed.\\n\\nSo how is privatization done? \\nFirst, the user chooses to upload the private file. At this time, the system will use the user's BOS public key address to encrypt the file and upload it to IPFS. The file hash value is on the BOS chain. This file is externally encrypted. For the user, the user can obtain the source file by decrypting the file with his private key. In short, it is like a decentralized Dropbox client, which is a distributed file supporting large files on the BOS network. The way it is stored.\\n\\nTechnical difficulties:\\n1. (Project 1.0) The above two smart contracts need to be guaranteed for security and high availability, and will be submitted to the professional organization for code review after development.\\n2. (Project 2.0) Design and develop the UnicornTube client that ordinary users will use. Everyone mines and improves P2P efficiency. (The client automatically synchronizes certain data, spends a certain amount of storage space and bandwidth, and rewards UTC based on contribution)\\n3, (Project 2.0) to achieve PoSt space-time certification, that is to achieve the above reward mechanism, as an incentive layer to allow users to provide storage services, while designing UTC file storage protocol (a control of the number of backups of each file in the IPFS network, Readability, connectivity protocols) enable stored files to maintain integrity, multiple backups, and fast synchronization.\\n\\nProposal budget：\\nThe total application amount is 850,000 BOS, including the development expenses and operating activities of the R&D team of more than 8 people.\\n\\nThe first phase，the development cycle is about March, the total amount is 420,000 BOS, UnicornTube phase one, using IPFS technology to realize the distributed UnicornTube film and television platform in the BOS network, third-party smart contract code review, smart contract upload review process, IPFS Document retrieval and transmission, smart contract advertising bidding, member users login system.\\n\\nThe second phase，the development cycle is about 3 months, the amount is 430,000 BOS, the distributed file management client, the Dropchain of the blockchain. Privatization uploads, manages files, supports distributed storage of multiple document types (PDF, Words, Png etc...), and exposes and shares files.\\n---------------------------------------------------------------------------\\n\\n【UnicornTube提案】\\n提案背景（痛点）\\n1、BOS区块存储空间有限，需要可处理大文件存储的分布式网络\\n2017年年底，以太坊因为“一只猫”而导致全网拥堵，这只猫就是以太猫。其次比特币也时常网络拥堵，导致巨额交易无法确认，其中的原因之一，就是区块容量大小有限。这就好比我们的电脑，容量越来越小，电脑也会越来越卡，甚至出现死机情况。作为 EOS 的最强侧链 BOS，也一样需要面对扩容问题，未来将会有更多的DApp接入和更多的人参与，就会产生越来越多的交易和数据，此刻就需要加入新的方案来满足未来的需求，而与 IPFS 技术结合就是一个不错的尝试。\\n\\n2、中心化存储不安全\\n美国三大个人信用评估机构之一的Equifax 在7月29日得知了遭到黑客袭击的消息，并在一个多月后宣布了这一消息。约有20.9万人的信用卡号码被盗，18.2万人的个人识别信息被窃取，产生了巨额的损失。这起史上最大的信息泄露案件，警示这数据的集中管理可能产生的问题，而分布式储存的技术能够降低这种大型数据泄露事件的发生。\\n\\n提案的主要内容:\\n提案名称为UnicornTube，该项目1.0 产品将实现基于BOS区块链 + IPFS技术的全球电影视频分享、聚合平台；UnicornTube 2.0实现链上分布式存储的云文档管理平台。IPFS 技术，能够实现大文件的传输和分布式存储，帮助用户将闲置的存储空间通过共享实现商品化，通过视频分享实现内容价值化。（想看更多图片：https://mp.weixin.qq.com/s/OLvAMjibOKwtvpXZHUS5Qg）\\n\\n技术上，它是基于星际文件系统（IPFS）和BOS网络技术结合开发的。IPFS 网络技术负责文件的分布式储存和分发，然后BOS网络负责智能合约、IPFS文件哈希上链，以及账户管理和网络连接等基础操作。\\n\\n产品形态上，1.0推出UnicornTube视频平台。用户可以进行注册、登陆、视频的浏览、上传等操作，同时支持比如点赞、评论、打赏的互动操作和数字钱包的相关管理功能。其中UnicornTube 视频平台主要的智能合约有两个，一个发生在视频上传，另一个发生在广告竞标。用户上传文件时，需要利用BOS支付一定的费用，视频文件会先传输给运营团队审核，审核成功后视频文件会加入到IPFS网络中，并把IPFS计算文件得到的哈希值（文件唯一标识）（以Memo的形式）上链到BOS区块链上。而广告竞标智能合约，不同位置或类型的广告都会有个最低竞拍价，供广告商竞标，比方说，10个BOS起拍，中标者可在约好的位置上挂维持一周的广告。广告商可通过我们官方的入口进行竞标广告，他可以选择广告位以及他想竞标的BOS数量，并直接使用BOS钱包在我们的网页上调用智能合约方法，即可完成竞拍。同时官方会展示当前实时竞拍详情。那么竞拍结束后，智能合约判断出价最高的竞拍单获胜并可以选择上传广告内容，会在对应的时刻展示。竞拍失败的广告商会退还BOS。\\n\\n那么UnicornTube 与中心化影视平台有哪些区别呢？\\n1、使用HLS 直播技术，让用户观看流畅，且减少不必要的额带宽开销，使用IPFS技术来分发内容，比中心服务器的网站更迅速，具有更好的观影体验。\\n2、中心化的影视平台存储一旦被黑客突破，造成的损失是巨大的，而UnicornTube 去中心化的存储利用P2P分布式技术，让被访问的资源分散地保存在每个用户的软件客户端，碎片化地储存资源，并且文件都使用了加密技术，相比中心化影视平台安全性会更高。\\n3、中心化的广告由平台方统一定价，定价不自由，不利于广告商；而UnicornTube 平台广告又市场决定最终价格，定价自由，由市场需求决定价格。\\n4、中心化影视平台需要平台独自承担带宽与硬件的高额成本，使得可以分给创作者的利润空间比较少，而UnicornTube 则是将社会共享的闲置资源利用起来，自然有更多的利润空间可以给到创作者。同时浏览总时长排行进榜的创作者会活动高额的代币奖励。\\n5、在UnicornTube 上，观众观影时常、点赞和评论等活跃行为有机会获得一定的空投奖励，让观众的看电影都可以挣钱，这是传统影视平台没有的好处。\\n\\n然而，区块链影视平台不是我们最终想做的，1.0版本作为一个产品过渡阶段，影视平台落地后，我们将会研发更具挑战的办公应用场景，发挥分布式存储真正的魅力，能融入每个人的生活，这才是重头戏。\\n\\n项目2.0版本将推出分布式文件管理客户端，支持更多的文件类型存储，它允许每个用户都可自定义一个区块链技术的云盘，所有文件都有个哈希链接，旨在为每个人提供永久的存储能力。用户可以在客户端购买存储容量套餐，上传文件到私有的云盘中，私有云盘无法被直接查看。\\n\\n那么是怎么做到私有化？ 首先用户选择上传私有文件，此时系统会使用用户的BOS公钥地址去加密文件并上传至IPFS，文件哈希值上BOS链。此文件对外是加密的，对用户而言，用户使用其私钥解密文件即可获得源文件，简单来说，就好比一个去中心化的Dropbox客户端，成为BOS网络上支持大文件的分布式存储的方式。\\n\\n技术难点：\\n1、（项目1.0）上述的两个智能合约，需要保证其安全性和高可用性，会在开发完后提交专业机构进行代码审核\\n2、（项目2.0）设计并开发出普通用户都会使用的UnicornTube客户端，人人挖矿，提高P2P效率。（客户端自动同步一定的数据，花费用户一定的存储空间和带宽，并根据贡献奖励UTC）\\n3、（项目2.0）实现PoSt时空证明，即实现上述的奖励机制，作为激励层来让用户提供存储服务，同时设计出UTC文件存储协议（一种控制各个文件在IPFS网络中的备份数、可读性、连通性的协议），使得存储的文件能够保持完整性、多备份性、可快速同步等状态。\\n\\n提案周期预算:\\n申请经费总额85万个BOS，包含投入8人以上研发团队的开发开支和运营活动的成本。\\n第一期：开发周期约3月，金额42万BOS，UnicornTube 阶段一，利用IPFS技术，实现在BOS网络中的分布式UnicornTube影视平台，第三方智能合约代码审核， 智能合约上传审核流程， IPFS文件检索和传输，智能合约广告位竞标，会员用户登陆系统。\\n第二期：开发周期约3月，金额43万BOS，推出分布式文件管理客户端，区块链的Dropbox。私有化上传、管理文件， 支持多种文档类型的分布式存储 （ PDF，Words，Png etc...),文件的公开与分享。\",\"type\":\"referendum-v1\",\"incentives\":\"850000.0000\",\"receiptor\":\"bosjobcasino\"}", + "created_at": "2019-06-05T12:46:31" + }, + "stats": { + "votes": { + "1": 5, + "total": 5, + "proxies": 0, + "accounts": 5 + }, + "accounts": { + "0": 0, + "1": 2375577, + "total": 2375577 + }, + "proxies": { + "0": 0, + "1": 0, + "total": 0 + }, + "staked": { + "0": 0, + "1": 2375577, + "total": 2375577 + }, + "block_num": 43385214 + } + }, + "universal": { + "id": "universal_20190605", + "proposal": { + "proposal_name": "universal", + "proposer": "bosauthority", + "title": "Comprehensive, Universal and fully Integrated Explorer/Wallet for BOS", + "proposal_json": "{\"type\":\"referendum-v1\",\"content\":\"## Comprehensive, Universal and fully Integrated Explorer/Wallet for BOS\\n\\nBOS Improvement Proposal \\nBy EOS Authority\\n\\n## Brief\\n\\nEOS Authority is a founding block producer of the EOS Mainnet and BOS chain. We gathered a huge experience working with the community and helping them out. We have extensive support lines (Email, Telegram, Social Media and phone calls). We have taken our experience from all of the interaction with the community and want to encourage transparency, accountability, fairness and promote mass adoption. Solid knowledge or user problems combined with incredible engineering talent allow us to build blockchain-based solutions for the community.\\n\\n## Problems to be addressed\\n\\n1. Multiple accounts held by token holders\\n 1. Token holders have several accounts on-chain\\n 2. Current explorers don’t present an unified version of accounts\\n2. No symbiosis between chains\\n 1. A lot of EOS Mainnet token holders don’t know about BOS\\n 2. Improve access to side-chains - Interoperability\\n 3. How to scale, how to improve the EOSIO ecosystem\\n3. Raising barrier against Scams\\n 1. Education to token holders\\n 2. Security Audits are required\\n 3. Secure and reliable messaging - No more scam websites\\n 4. Best practices\\n 5. Real-time account monitoring\\n4. Support multiple wallets\\n 1. Constant support for new mobile wallets\\n 2. New hardware wallets - Ledger\\n 3. Up and coming list of wallets and systems\\n5. Discoverability of functionality & community\\n 1. Increase token holder participation - Referendum & Polls\\n 2. Airgrabs/Airdrops\\n 3. Education and Usability focus\\n\\n## The EOS Authority Solution\\n\\nHere is how our Comprehensive, Universal and fully Integrated Explorer/Wallet for BOS will help BOS token holders grow the ecosystem and how it addresses the problems.\\n\\n## Solution 1: Multiple accounts held by token holders\\n\\nAddressing the issues of \\n - Multiple accounts on chain \\n - Unified accounts list \\n - Combined security dashboard \\n\\n**Exhibit 1.1: At a glance view of several accounts** \\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img1.png)\\n\\n
**Combines all BOS accounts (multiple) includes BOS Testnet**
\\n\\nThis will be a great resource for BOS holders and BOS developers.\\n\\n**Exhibit 1.2: Add several accounts** \\nClicking on “Add account” will let you add several accounts into the list of accounts\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img2.png)\\n\\nSimply click on “Add account” and manage a whole list. The Testnet accounts can be hidden if required, the TestNet accounts can also be deleted.\\n\\n## Solution 2: Increasing participation cross chain - BOS & EOS and other EOSIO Chains\\n\\nHere we address these issues \\n - Increasing awareness of different EOSIO side chains \\n - Improve access to side-chains - Interoperability \\n - How to scale, how to improve the EOSIO ecosystem \\n\\n**Exhibit 2.1: Manage multiple accounts across multiple chains** \\nGet a combined view of standing of multiple EOS accounts and multiple chains. \\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img3.png)\\n\\n**Exhibit 2.2: Easily add or remove different accounts on various chains** \\nThis includes the various testnets.\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img4.png)\\n\\nWe believe this will raise awareness among token holders of the different chains and will feature heavily as EOSIO moves into IBC and more.\\n\\n## Solution 3: Raising barriers against scams\\n\\nHow do we address these problems \\n - Education to token holders \\n - Security Audits are required \\n - Secure and reliable messaging - No more scam websites \\n - Best practices \\n - Real-time account monitoring \\n\\n**Exhibit 3.1: Account security audit** \\nWe make recommendations to token holders to improve account security and increase voter participation\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img5.png)\\n\\n - Indication and guidance on separate owner and active keys \\n - Recommendation to keep tokens staked \\n - Voting for Block Producers \\n - Real time notifications of actions on Telegram and on email.\\n\\n**Exhibit 3.2: Secure and reliable messaging** \\nEasy to view alerts that indicate new messages that can show users notification about the account and further details.\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img6.png)\\n\\nExpanding the messages list will show a detailed history, secure way to access airdrops, more information about the chain, etc.\\n\\nEasy side-bar to get notifications\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img7.png)\\n\\n**Exhibit 3.3: Secure messages on Email and Telegram** \\nThis forms a key part of our system. We are able to let users know that their account has been undelegated and how they can restore access to their account if they have separate keys. We will alert users on every transaction and show a balance.\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img8.png)\\n\\n
**Alerts on both email and telegram**
\\n\\n## Solution 4: Support for multiple wallets\\n\\nThe main problems to solve are \\n - Constant support for new mobile wallets \\n - New hardware wallets - Ledger \\n - Up and coming list of wallets and systems \\n\\nWe want to be able to solve the widest possible range of wallets and solutions\\n\\n**Exhibit 4.1: Support for wide range of wallets** \\nWe want to be able to support - Adding by account name, Scatter, Ledger, Mobile - All wallets and many more. We expect to see many powerful wallets appear in the future. We hope to support them all in the hope that we can fully integrate them and support all their features.\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img9.png)\\n\\n**Exhibit 4.2: Developer friendly** \\nIn addition to support with a lot of variety of wallets, we also support cleos command generation from within the platform for every action on the system.\\n\\nWe do this by making the contracts available\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img10.png)\\n\\nAlso making the cleos statements available\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img11.png)\\n\\n## Solution 5: Discoverability of functionality & community\\n\\nWe aim to solve these problems: \\n - Increase token holder participation - Referendum & Polls \\n - Education and Usability focus\\n\\n**Exhibit 5.1 - Polls system** \\nWe were one of the first to present a polls system to the community. We want BOS token holders to enjoy similar aspects.\\n\\nWe understand that BOS will have auditors and several roles. We hope to customise what we have to reach these token holders.\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img12.png)\\n\\n - List of all the polls and referendums on the system \\n - Easily accessible from the left menu\\n\\nCombined view of all aggregate statistics\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img13.png)\\n\\nEasy view of all the comments and participation\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img14.png)\\n\\nDetailed voting statistics\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img15.png)\\n\\nVoting breakdown and analysis\\n\\n![](https://eosauthority.com/common/images/authority-polls/bos/poll1/img16.png)\\n\\n**Exhibit 5.2 - Education and usability** \\nWith detailed information on how to use the various parts of the system and video and written guides, FAQs\\n\\n## Constant video guides\\n\\n![](http://deveos.eosauthority.com/common/images/authority-polls/bos/poll1/img17.png)\\n\\n## FAQs\\n\\n![](http://deveos.eosauthority.com/common/images/authority-polls/bos/poll1/img18.png)\\n\\nDetailed step by step articles and more.\\n\\n## Competitors\\n\\nIn simple words, we aim to be Comprehensive, Universal and fully Integrated Explorer/Wallet for BOS.\\n\\nComprehensive - We want to support all the features on the BOS chain \\nUniversal - We want to integrate with all the chains connecting them all to BOS \\nFully integrated - All the features in one place \\nExplorer - We will have a full explorer to view all the accounts, contracts and more\\n\\nWe have competitors or parties working on each of the aspects but we believe we are unique in trying to address all of the various challenges in one place.\\n\\n## Execution Plan\\n\\n800,000 BOS that goes for developing and testing\\n\\nPhase 1 - Project start to integrate with BOS\\n\\nPhase 2 - Full integration of available chain features with BOS \\n - BOS explorer \\n - BOS Dashboard / Account security \\n - Integrating all the features of the wallet/explorer \\n - Support for Scatter, Ledger (Hardware wallet), Cleos, Mobile wallets\\n\\nPhase 3 - Poll system \\n - Ability to list polls \\n - Vote on Polls \\n - Detailed statistics \\n - BOS specific functionality.\\n\\nPhase 4 - Promotion to the BOS ecosystem and larger audience \\n - We want to take an agile development approach, we will deploy each phase as it is ready for the community to use.\\n\\n## Fund Release Plan\\n\\nThe funding from the WPS will help us but will not cover the entire cost of team, salaries, servers and infrastructure. We aim to absorb the extra costs to give the BOS ecosystem a boost with our incredible tool set. The contribution from the WPS will help bolster our funding and help us do more for the BOS community and wider EOSIO community as a whole.\\n\\nFunding goal is 800,000 BOS that goes for developing and testing with the aim of hosting the system and running associated servers.\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n
Phase 1Phase 2Phase 3Phase 4
0 BOS400,000 BOS400,000 BOS0 BOS
Project Start5 weeks6 weeksOngoing
\\n\\nPhase 3, the dates are dependent on the time it takes to complete the specification for the polls system.\\n\\n**Total funding - 800,000 BOS \\nTotal duration - 11 weeks (2.5 months)**\\n\\n## Team\\n\\nThis project is in safe hands. It will be driven by the team behind EOS Authority that has delivered similar projects on the EOS Mainnet successfully. We understand the wide range of audience, the nature of projects on EOSIO.\\n\\nThe delivery team will be led by Rohan Abraham of EOS Authority. The team formed for BOS project. It will be led by 1 Project Director and additionally staffed by 3 other web developers, 1 designer, 1 tester and a project assistant.\\n\\n## Relevant links\\n\\n[https://eosauthority.com](https://eosauthority.com)\\n\\n[https://eosauthority.com/dashboard](https://eosauthority.com/dashboard)\"}", + "created_at": "2019-06-05T17:03:19" + }, + "stats": { + "votes": { + "1": 11, + "total": 11, + "proxies": 6, + "accounts": 5 + }, + "accounts": { + "0": 0, + "1": 10230207912, + "total": 10230207912 + }, + "proxies": { + "0": 0, + "1": 63757731103, + "total": 63757731103 + }, + "staked": { + "0": 0, + "1": 73987939015, + "total": 73987939015 + }, + "block_num": 43385214 + } + }, + "wpspromotion": { + "id": "wpspromotion_20190603", + "proposal": { + "proposal_name": "wpspromotion", + "proposer": "pacificproxy", + "title": "BOSCore WPS global promotion", + "proposal_json": "{\"content\":\"The proposal will be implemented from May 10st.\\n\\n\\n\\n## Proposal Background\\n\\n\\n\\nBOSCore is a EOS side chain initiated by the community. We can see that any public chain cannot be separated from governance in the end. Governance is the cohesion of community development. Community governance plays different roles in each stage of the public chain. Organizing community members to participate in the discussion of ecological construction can gather the consensus of BOSCore community, expand the influence of BOSCore brand, and help BOSCore ecological prosperity.\\n\\n\\n\\nBOS Pacific is a BOSCore Node team initiated by Node Pacific Tech, which is the world's largest public chain and crowdsourcing platform operator.At present, it is the core BP node of nearly 20 mainstream public chains at home and abroad. It is deeply involved in the public chain ecological operation and leads the community governance, such as successfully building the EOS core governance community EMAC, IOST core governance community ICAC, GXChain core governance community GCAC, Lambda core governance community LCAC, etc.\\n\\n\\n\\nBOS Pacific is also looking forward to contributing to BOSCore's ecological governance with rich experience in community governance.\\n\\n\\n\\n## Proposal Information\\n\\n\\n\\nThe basic information\\n\\n\\n\\n1. Proposal name: BOSCore referendum system /WPS global promotion proposal\\n\\n \\n\\n2. Submit function points: Core promotion\\n\\n\\n\\n3. The latest time for the proposal to be submitted after passed in the referendum: May 10-June25（long-term operation in the future)\\n\\n \\n\\n\\n\\n## Proposal Content\\n\\n\\n\\nBOS Pacific will launch the BOSCore core governance community and call on partners who are interested in governance in the BOSCore ecology to join in and build the BOSCore core governance community together.\\n\\n\\n\\nBCAC does not have the function of arbitration, does not participate in the implementation of governance, and only does the training and education of BOSCore governance, aiming to gather the consensus of BOSCore community.\\n\\n\\n\\nBCAC hopes to continuously promote the construction and improvement of BOSCore governance community, attract global blockchain technology and governance enthusiasts to understand and participate in BOSCore, build a rich and diverse governance communication community for BOSCore, and gradually improve BOSCore to community governance, constantly expand the cohesion of BOSCore, and form a strong and irreplaceable consensus mechanism.\\n\\n\\n\\n## Proposal Perform\\n\\n\\n\\n--BOSCore referendum system promotion\\n\\n\\n\\n-- recruitment and election of reviewers\\n\\n\\n\\n-- community presentation of the proposal (meeting)\\n\\n\\n\\n\\n\\n### 1.Promotion of BOSCore referendum system\\n\\n\\n\\nPresentation of Referendum system /WPS global conference -- 2 meetings in English and Chinese\\n\\n\\n\\nReferendum system presentation meeting: (taking a meeting as an example)\\n\\n\\n\\nPersonnel arrangement (operation 2+ design 1)\\n\\n\\n\\nBefore the meeting:\\n\\n\\n\\n-- Prepared PPT contents of the referendum system speech, and prepared the preheating before the meeting (posters, personnel, copywriting, equipment preparation).\\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Presided over and maintained the order of the meeting in both Chinese and English, and guided participants to participate in the questions\\n\\n\\n\\nAfter the meeting:\\n\\n\\n\\n-- Communicate with participants to understand requirements and promote proposals\\n\\n\\n\\n-- Organizing and publicizing the content of the meeting\\n\\n\\n\\n\\n\\n### 2.Recruitment, election and establishment of reviewers\\n\\n\\n\\nA. Recruitment of reviewers\\n\\n\\n\\nPersonnel arrangement (operation 1)\\n\\n\\n\\nPreparation process:\\n\\n\\n\\n-- Prepare the reviewers recruitment articles and make the registration form\\n\\n\\n\\n-- Communicate with community users and relevant personnel and guide them to fill in the form\\n\\n\\n\\nB. Reviewer election conference\\n\\n\\n\\nPersonnel arrangement (operation 2+ design 1)\\n\\n\\n\\nBefore the meeting:\\n\\n\\n\\n-- Confirm the meeting time according to the candidates for the registration reviewer\\n\\n\\n\\n-- Guide candidates to prepare for the reviewer manifesto\\n\\n\\n\\n-- Prepare the preheating before the meeting (posters, personnel, copywriting, equipment preparation)\\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Interpret the standards of reviewers in detail, and guide each participant to make their own declaration, opinions and opinions\\n\\n\\n\\nAfter the meeting:\\n\\n\\n\\n-- Communicate with the candidate reviewers and give a definite response time\\n\\n\\n\\n-- Organizing and publicizing the content of the meeting\\n\\n\\n\\n\\n\\n### 3.Community presentation of the proposal\\n\\n\\n\\nA. Proposal presentation: (take a proposal as an example)\\n\\n\\n\\nPersonnel arrangement (operation 2+ design 1)\\n\\n\\n\\nBefore the meeting:\\n\\n\\n\\n-- Prepare the preheating before the meeting (posters, personnel, copywriting, equipment preparation)\\n\\n\\n\\n--Invite the proposer to introduce the proposal at the meeting\\n\\n\\n\\nDuring the meeting:\\n\\n\\n\\n-- Presided over and maintained the order of the meeting in both Chinese and English\\n\\n\\n\\nAfter the meeting:\\n\\n\\n\\n-- Organizing the content and publicizing the media after the meeting\\n\\n\\n\\nFollow-up:\\n\\n\\n\\nReport on the progress of the proposal\\n\\n\\n\\n\\n\\n## Proposal Target\\n\\n\\n\\n1. Detailed explanation of the proposal process in both Chinese and English;\\n\\n \\n\\n2. Referendum system /WPS global conference -- 1-2 meetings, in Chinese and English\\n\\n \\n\\n3. Selection of reviewers (recruitment, election, establishment) -- one month, at least two meetings, both in Chinese and English\\n\\n \\n\\n4. Proposal meeting publicity -- no less than once a week (no limit on the number of proposals within 2 months)\\n\\n \\n\\n5. Over 15+ original articles published on Wechat official accounts, Weibo, Bihu,Huoxing24, Tuoluocaijing, Facebook, Twitter, Reddit,Steemit, Medium, Starteos, Bos.sh,IMEOS, etc.; (Chinese and English channels, covering more than 100,000 users, and reading volume more than 200,000)\\n\\n \\n\\nAddition: the average number of participants in a single meeting is no less than 10% of the BCAC community\\n\\n\\n\\n\\n\\n## Proposal Budget\\n\\n\\n\\nApplied funds: 350,000 BOS (personnel, materials, marketing)\\n\\n\\n\\n\\n\\n------\\n\\n\\n\\n提案从5月10日开始执行\\n\\n\\n\\n## 提案背景\\n\\n\\n\\nBOSCore是由社区发起的EOS侧链，我们能看到任何一条公链最终都离不开治理，治理是生态壮大的催化剂，治理是社区发展的凝聚力量，社区治理在公链各个阶段发挥着不同的作用， 组织社区成员参与生态建设的讨论，能够凝聚BOSCore社区共识，扩大BOSCore品牌影响力，助力BOSCore生态繁荣。\\n\\n\\n\\nBOS Pacific是由Node Pacific Tech（节点亚太）发起的BOSCore节点团队，Node Pacific 是全球最大的公链运营众包平台和节点运营商，目前参与了国内外近20条主流公链的核心出块节点；深度参与公链生态运营，并主导社区治理，如成功打造EOS核心治理社区EMAC， IOST 核心治理社区ICAC，公信链核心治理社区GCAC，Lambda核心治理社区LCAC等。\\n\\n\\n\\nBOS Pacific也非常期望能带着较为丰富的社区治理经验，为BOSCore的生态治理搭建贡献一份力量。\\n\\n\\n\\n\\n\\n## 提案信息\\n\\n\\n\\n基本信息\\n\\n\\n\\n1、提案名称：BOSCore公投系统/WPS全球推广提案\\n\\n\\n\\n2、提交功能点：BOSCore WPS公投系统核心推广\\n\\n\\n\\n3、提案在公投通过后最晚提交时间：5月10日-6月25日（未来会长期运营）\\n\\n\\n\\n## 提案内容\\n\\n\\n\\nBOS Pacific会发起BOSCore核心治理社区，号召BOSCore生态中对治理感兴趣的小伙伴加入，共建BOSCore核心治理社区BCAC。\\n\\n\\n\\nBCAC不具备仲裁功能，不参与治理执行，仅做BOSCore治理的培训和教育，旨在凝聚BOSCore社区共识。\\n\\n\\n\\nBCAC希望能够持续推进搭建、完善BOSCore治理社区，吸引全球区块链技术以及治理爱好者了解，参与BOSCore，为BOSCore搭建一个丰富多样的治理交流社区，逐步将BOSCore向社区化治理逐步过渡，不断扩大BOSCore的凝聚力，形成强有力、不可替代的共识机制。\\n\\n\\n\\n\\n\\n## 提案执行\\n\\n\\n\\n--BOSCore公投系统推广\\n\\n\\n\\n--评审员招募与选举\\n\\n\\n\\n--提案的社区展示（会议）\\n\\n\\n\\n\\n\\n### 1.BOSCore公投系统推广\\n\\n\\n\\n公投系统/WPS全球会议展演—2次会议，中英文\\n\\n\\n\\na. 公投系统讲演会议：以一次会议为例人员安排（运营2+设计1）\\n\\n\\n\\n会议前：\\n\\n\\n\\n--准备公投系统讲演PPT内容，同时准备会议前的预热（海报，人员，文案，设备准备） 会议间：\\n\\n\\n\\n--中英文主持与维持会议秩序，并引导参会人员参与提问会议后：\\n\\n\\n\\n--和参会人员沟通了解需求和促成提案\\n\\n\\n\\n--会议内容的整理和宣发\\n\\n\\n\\n\\n\\n### 2.评审员招募、选举、成立\\n\\n\\n\\na. 评审员招募\\n\\n\\n\\n人员安排（运营1）\\n\\n\\n\\n准备流程：\\n\\n\\n\\n--准备评审员招募文章、制作报名表单\\n\\n\\n\\n--和社区用户及相关人员沟通并引导社区用户及相关人员填写表单\\n\\n\\n\\nb.评审员选举会议\\n\\n\\n\\n人员安排（运营2+设计1）\\n\\n\\n\\n会议前：\\n\\n\\n\\n--根据报名评审员的候选人沟通及确定会议时间\\n\\n\\n\\n--引导候选人准备竞选评审员宣言\\n\\n\\n\\n--准备会议前的预热（海报，人员，文案，设备准备）\\n\\n\\n\\n会议中：\\n\\n\\n\\n--详细解读评审员标准，并引导每一位参会人员发表自己的宣言、看法和意见会议后：\\n\\n\\n\\n--和候选评审员沟通并给予确定回复的时间\\n\\n\\n\\n--会议内容的整理和宣发\\n\\n\\n\\n\\n\\n### 3.提案的社区展示\\n\\n\\n\\na.提案展示：以一个提案为例人员安排（运营2+设计1） 会议前：\\n\\n\\n\\n--准备会议前的预热（海报，人员，文案，设备准备）\\n\\n\\n\\n--邀请提案者在会上介绍提案相关内容会议中：\\n\\n\\n\\n--会上的中英文主持与维持会议秩序， 会议后：\\n\\n\\n\\n--会后的内容整理与媒体宣发后续：\\n\\n\\n\\n提案进展的跟踪报道\\n\\n\\n\\n\\n\\n## 提案目标\\n\\n\\n\\n1. 提案流程中英文详解；\\n\\n \\n\\n2. 公投系统/WPS全球会议展演—1-2次会议，中英文\\n\\n\\n\\n3. 评审员评选（招募，选举，成立）—周期1个月，至少2次会议，中英文\\n\\n\\n\\n4. 提案会议公示—每周不少于1次（2个月内，提案数不限）\\n\\n\\n\\n5. 原创文章15+，发布平台：公众号、微博、币乎、火星、陀螺财经、Facebook、Twitter、Reddit、steemit、medium、starteos、bos.sh、EOS快讯等；\\n\\n\\n\\n（中英文渠道，覆盖10万＋用户，阅读量过20万＋）\\n\\n\\n\\n补充：平均单次会议人数不少于BCAC社群人数10%\\n\\n\\n\\n\\n\\n## 提案预算\\n\\n\\n\\n申请经费：总额 35万 BOS（人员，物料，市场）\\n\\n\",\"type\":\"referendum-v1\",\"incentives\":\"350000.0000\",\"receiptor\":\"bospacificok\"}", + "created_at": "2019-06-03T06:21:39" + }, + "stats": { + "votes": { + "1": 48, + "total": 48, + "proxies": 17, + "accounts": 31 + }, + "accounts": { + "0": 0, + "1": 50481771753, + "total": 50481771753 + }, + "proxies": { + "0": 0, + "1": 95283980662, + "total": 95283980662 + }, + "staked": { + "0": 0, + "1": 145765752415, + "total": 145765752415 + }, + "block_num": 43385214 + } + } +} \ No newline at end of file diff --git a/api/requirements.txt b/api/requirements.txt index c89089f..a7e10d2 100755 --- a/api/requirements.txt +++ b/api/requirements.txt @@ -4,3 +4,6 @@ peewee gunicorn supervisor psycopg2-binary +google-cloud-translate +requests +markdown \ No newline at end of file diff --git a/api/set_translate_credentials.sh b/api/set_translate_credentials.sh new file mode 100755 index 0000000..b704330 --- /dev/null +++ b/api/set_translate_credentials.sh @@ -0,0 +1,4 @@ +pwd=`pwd` +env="export GOOGLE_APPLICATION_CREDENTIALS='${pwd}/GOOGLE_APPLICATION_CREDENTIALS.json'" +env >> /etc/profile +source /etc/profile \ No newline at end of file diff --git a/api/supervisor.ini b/api/supervisor.ini index 790a173..d55170c 100644 --- a/api/supervisor.ini +++ b/api/supervisor.ini @@ -1,10 +1,10 @@ [program:boswps] -directory = /path/to/boswps-api +directory = /root/referendum/api command = gunicorn -w 4 api:app -stderr_logfile = /path/to/supervisord.d/log/boswps-stderr.log -stdout_logfile = /path/to/supervisord.d/log/boswps-stdout.log +stderr_logfile = /root/referendum/api/supervisord.d/log/boswps-stderr.log +stdout_logfile = /root/referendum/api/supervisord.d/log/boswps-stdout.log autostart = false autorestart = true user = root stopasgroup=true -killasgroup=true +killasgroup=true \ No newline at end of file diff --git a/api/translation.py b/api/translation.py new file mode 100644 index 0000000..61c8e99 --- /dev/null +++ b/api/translation.py @@ -0,0 +1,22 @@ +from google.cloud import translate +from google.oauth2 import service_account +import os +import markdown + +def translate_text(text, target='en',title=False): + try: + text = markdown.markdown(text, output_format='html5', extensions=['extra']) if title == False else text + credentials_path = os.path.dirname(os.path.realpath(__file__)) + os.sep + 'GOOGLE_APPLICATION_CREDENTIALS.json' + credentials = service_account.Credentials.from_service_account_file(credentials_path) + translate_client = translate.Client( + credentials=credentials) + result = translate_client.translate( + text, target_language=target, format_ = 'html') + return result['translatedText'] + except Exception as err: + print(err) + + +if __name__ == '__main__': + p = translate_text("# DecentralBank BOS Proposal: Bitcoin Light Client We propose to build a Bitcoin Light Client directly onto the BOS chain. This will allow BOS smart contracts to listen for Bitcoin payments and trigger actions based on BTC payments trustlessly on-chain. ## Technical Details All the block headers from the Bitcoin chain will be synced to a BOS smart contract. These block headers can be used to produce Merkle proofs that a transaction has been included in a Bitcoin block. When a valid Merkle proof is provided for a transaction, that transaction's details are registered in the smart contract, and other smart contracts will be able to take action based on that payment. ## Milestones & Funding * Sync Block Headers (end of July) * Merkle proof verification for transactions (mid-September) For each phase of development, we are requesting 200,000 BOS in funding (total 400,000 BOS). This funding will go toward bringing an additional developer onto the project. ## Use Cases * Trustlessly listen for a BTC transaction to swap BOS for BTC * Dapps can accept Bitcoin as payment for services. For example, a betting dapp can accept Bitcoin as a payment and run an action when the payment has finalized without relying on a trusted source. ## Team DecentralBank is developing a blockchain for algorithmic stablecoins and is focused on building core infrastructure for EOSIO blockchains. The co-founders are Kedar Iyer and Sam Kazemian, and the team includes Travis Moore, the CTO of Everipedia. Together, these 3 were the developers behind the Everipedia protocol and website. ", target='ja') + print(p) diff --git a/api/utils.py b/api/utils.py index 630e612..242f92c 100755 --- a/api/utils.py +++ b/api/utils.py @@ -3,31 +3,42 @@ import re,logging import threading import time - +from init_db import * +import requests +import json + +def checkSupportLang(lang): + list = ['af', 'sq', 'am', 'ar', 'hy', 'az', 'eu', 'be', 'bn', 'bs', 'bg', 'ca', 'ceb', 'cn', 'tw', 'co', 'hr', 'cs', 'da', 'nl', 'en', 'eo', 'et', 'fi', 'fr', 'fy', 'gl', 'ka', 'de', 'el', 'gu', 'ht', 'ha', 'haw', 'he**', 'hi', 'hmn ', 'hu', 'is', 'ig', 'id', 'ga', 'it', 'ja', 'jw', 'kn', 'kk', 'km', 'ko', 'ku', 'ky', + 'lo', 'la', 'lv', 'lt', 'lb', 'mk', 'mg', 'ms', 'ml', 'mt', 'mi', 'mr', 'mn', 'my', 'ne', 'no', 'ny', 'ps', 'fa', 'pl', 'pt', 'pa', 'ro', 'ru', 'sm', 'gd', 'sr', 'st', 'sn', 'sd', 'si', 'sk', 'sl', 'so', 'es', 'su', 'sw', 'sv', 'tl', 'tg', 'ta', 'te', 'th', 'tr', 'uk', 'ur', 'uz', 'vi', 'cy', 'xh', 'yi', 'yo', 'zu'] + if lang in list: + return True + else: + return False # Check if condition match # proposal votes > 40% staked_total all net # Yes / No >= 1.5 -def proposal_base_condition_ckeck(bp_votes = 0, staked_total = 10, yes = 0, no = 0): - VOTE_RATIO = 0.4 - YES_NO_RATIO = 1.5 - if bp_votes * VOTE_RATIO <= staked_total and no == 0 and yes > 1.5: - return True - else: - return False + + +def proposal_base_condition_ckeck(bp_votes=0, staked_total=10, yes=0, no=0): + VOTE_RATIO = cfg.PROPOSAL_VOTE_RATIO + YES_NO_RATIO = cfg.PROPOSAL_YES_NO_RATIO try: - if bp_votes * VOTE_RATIO <= staked_total and yes / no > YES_NO_RATIO: + if bp_votes * VOTE_RATIO <= staked_total and (no == 0 or yes / no > YES_NO_RATIO): return True else: return False except ZeroDivisionError as err: print(err) -def auditor_base_condition_ckeck(bp_votes = 0, staked_total = 10, yes = 0, no = 0): - VOTE_RATIO = 0.03 - YES_NO_RATIO = 1.5 + +def auditor_base_condition_ckeck(bp_votes=0, staked_total=10, yes=0, no=0): + VOTE_RATIO = cfg.AUDITOR_VOTE_RATIO + YES_NO_RATIO = cfg.AUDITOR_YES_NO_RATIO + print(VOTE_RATIO) + print(YES_NO_RATIO) try: - if bp_votes * VOTE_RATIO <= staked_total and yes / no > YES_NO_RATIO: + if bp_votes * VOTE_RATIO <= staked_total and (no == 0 or yes / no > YES_NO_RATIO): return True else: return False @@ -37,7 +48,7 @@ def auditor_base_condition_ckeck(bp_votes = 0, staked_total = 10, yes = 0, no = # Create log default dir './quant/log/' 7days -def init_log(log_name, path = './quant/log/', backupCount=7): +def init_log(log_name, path = './log/', backupCount=7): # create the logger # create the handler，for writing logfile @@ -185,11 +196,33 @@ def round4(num): def round3(num): return round(float(num), 3) +def alarm(msg): + pass + # api = 'http://monitor.enjoyshare.net/alarm_upload' + # data = { + # 'type': 3, + # 'code': '86fcad64-5e8d-4b08-84af-c33f61faa428', + # 'node': 'wps hk server', + # 'extra': ''} + # data["extra"] = str(msg) + # headers = {'Content-Type': 'application/json'} + # res = requests.post(url=api, headers=headers, data=json.dumps(data)) + # print(res) + -if __name__ == '__main__': - result = proposal_base_condition_ckeck(100, 10, 7, 3) - print(result) - result = auditor_base_condition_ckeck(100, 10, 7, 3) - print(result) +if __name__ == '__main__': + # dict = {'hello':''} + # dict["hello"] = "123" + # print(dict) + pass + # api = 'http://monitor.enjoyshare.net/alarm_upload' + # data = { + # 'type': 3, + # 'code': '86fcad64-5e8d-4b08-84af-c33f61faa428', + # 'node': 'wps hk server #2', + # 'extra': 'for testing wps notifications 2'} + # headers = {'Content-Type': 'application/json'} + # res = requests.post(url=api, headers=headers, data=json.dumps(data)) + # print(res) diff --git a/api/vote_total_tally.json b/api/vote_total_tally.json new file mode 100755 index 0000000..1745713 --- /dev/null +++ b/api/vote_total_tally.json @@ -0,0 +1,7 @@ +{ + "block_num": 43383655, + "bp_votes": 398112411429, + "bp_producers_votes": 133237242066, + "bp_proxy_votes": 264875169363, + "currency_supply": 1014107095.3465 +} \ No newline at end of file diff --git a/contracts/eosio.forum/README-cn.md b/contracts/eosio.forum/README-cn.md index fcb66f1..e00cde4 100644 --- a/contracts/eosio.forum/README-cn.md +++ b/contracts/eosio.forum/README-cn.md @@ -29,24 +29,6 @@ 使用选民的帐户和提案的名称来调用 `unvote` 命令。 一个 `unvote` 命令就可以从提案中完全删除你的投票，并清除与该投票相关的RAM用量。 -提案处于活跃状态时，提议者可以手动使其过期。 -调用 `expire` 命令，它只有 `proposal_name` 这个参数。 -它可以将提案的 `expires_at` 字段修改为当前时间，而不是等待它原始的到期时间。 - -提案过期后（无论是手动还是自动过期），进入3天的冻结期。 -在此冻结期内，该提案被锁定，并且不能调用任何操作（包括改投票、删除投票和清理）。 -这时间段是为了让多个工具可以查询结果以进行交叉验证的。 -一旦结束冻结期，可以通过 `clnproposal` 命令清理提案。 -`clnproposal` 命令接受 `proposal_name` 和 `max_count` 两个值。 -`clnproposal` 是按批处理的，每批删除的提案中一定数量的投票（`max_count` 变量可定义数量）。 -一旦提案中的所有投票都被删除，提案本身就会被删除。 - -提案清理会有效地回收所有用于投票和提案本身的RAM。RAM将返还给选民（投票）和提议者（提案）。 - -任何人都可以调用 `clnproposal` 命令，没有任何限制。 -这样是没有风险的，因为只有过了冻结期限的过期提案才能被清理。 -所以提案清理命令是可以放心用的。 - ### 开发 需要的软件： @@ -150,10 +132,9 @@ constexpr static uint32_t FREEZE_PERIOD_IN_SECONDS = 2; // NEVER MERGE LIKE THIS 以下列表是可有的操作： - [propose](#action-propose)（提案） -- [expire](#action-expire)（过期时间） +- [cancel](#action-cancel) - [vote](#action-vote)（投票） - [unvote](#action-unvote)（撤销投票） -- [clnproposal](#action-clnproposal)（清除提案） - [post](#action-post)（发布帖子） - [unpost](#action-unpost)（撤销发布了的帖子） - [status](#action-status)（状态） @@ -170,7 +151,6 @@ constexpr static uint32_t FREEZE_PERIOD_IN_SECONDS = 2; // NEVER MERGE LIKE THIS - `proposal_name` (type `name`) - 提案的名称，把它与其他提案区别开来的ID - `title` (type `string`) - 提案的标题 (必须少于1024个字符) - `proposal_json` (type `string`) - 提案的 JSON 元数据，还没有具体规格，请见[JSON结构指南](#json-structure-guidelines) -- `expires_at` (type `time_point_sec`) - 提案的到期日期，不得超过6个月，ISO 8601字符串格式（UTC）**不含** 时区修饰符。 ##### 拒绝情况 @@ -178,12 +158,11 @@ constexpr static uint32_t FREEZE_PERIOD_IN_SECONDS = 2; // NEVER MERGE LIKE THIS - 当 `proposal_name` 已经存在时 - 当 `title` 超过1024个字符时 - 当 `proposal_json` JSON无效或太大时（必须是JSON对象且小于32768个字符） -- 当 `expires_at` 日期早于现在或晚于6个月之后时 ##### 例如 ``` -eosc tx create eosio.forum propose '{"proposer": "proposer1", "proposal_name": "example", "title": "The title, for list views", "proposal_json": "", "expires_at": "2019-01-30T17:03:20"}' -p proposer1@active +eosc tx create eosio.forum propose '{"proposer": "proposer1", "proposal_name": "example", "title": "The title, for list views", "proposal_json": ""}' -p proposer1@active ``` 或 @@ -232,7 +211,7 @@ eosc forum vote voter1 example 0 对于已过期且在其3天的冻结期的提案，是不可能 `unvote` 的。 如果提案已过期且冻结期已过，则可以对提案进行 `unvote`。 -为了社区的利益，你应该调用 [clnproposal](#action-clnproposal) ，直到提案被完全清理、投票都被删除，以便RAM能被释放给所有选民。 + ##### 参数 @@ -257,77 +236,30 @@ eosc forum unvote voter1 example ------------------------- -#### Action `expire` +#### Action `cancel` -立即使当前活跃的提案到期。 只有提案的原创建者才能执行此操作，对已过期的提案无效。 +Is used to cancel a `proposal_name` authorized by the `proposer`. -##### 参数 +##### Parameters -- `proposal_name` (type `name`) - 想要使过期的提案名称 +- `proposer` (type `name`) - The original proposer +- `proposal_name` (type `name`) - The proposal's name to cancel -##### 拒绝情况 +##### Rejections -- 当缺少原提案创建者的签名时 -- 当`proposal_name`不存在时 -- 当`proposal_name`已经过期时 +- When missing signatures of proposal's `proposer` +- When `proposal_name` does not exist -##### 例如 +##### Example ``` -eosc tx create eosio.forum expire '{"proposal_name": "example"}' -p proposer1@active -``` -或 -``` -eosc forum expire proposer1 example +eosc tx create eosio.forum cancel '{"proposer": "proposer1", "proposal_name": "example"}' -p proposer1@active ``` **注意** `proposal1` 必须与当初 `example` 提案的创建者相同。 ------------------------- -#### Action `clnproposal` - -当没有更多相关投票的时候，可清理投票和提案本身。 -迭代性操作，接受 `max_count` 值。它删除 `max_count` 值的票数。 -当提案里不再有选票的时候，提案本身也会被删除。 - -这可以有效清除提案及其所有投票所占用的RAM，多次调用操作直到所有选票都被删除。 - -只有在提案过期，并且过了它的3天冻结期，提案才能被清除。在冻结期间，提案被锁定并且不接受任何操作。 - -由于只有过期的提案可以被清理，任何人都可以调用此操作，无需授权。 - -选民、提议者或任何社区成员都可以呼叫 `clnproposal` 命令来清理与提案相关的RAM。 - -**注意**由于它仅通过提案作者发布的手动操作或者已经超过其 `expires_at` 的值而过期， -因此，任何人都可以安全地调用，因为提案已经有效地终止了它的生命周期。 - -##### 参数 - -- `cleaner_account` (type `name`) - 支付CPU/网络带宽的账户 -- `proposal_name` (type `name`) - 要清除的提案 -- `max_count` (type `uint64`) - 批量清除的投票数 - -##### 拒绝情况 - -- 当`proposal_name`尚未过期时 -- 当`proposal_name`过期但在其3天冻结期内时 - -**注意**给予 `max_count` 的值太大会增加此交易失败的概率， -由于可能导致CPU使用率过高。 找到最佳点以避免这种情况。 - -##### 例如 - -``` -eosc tx create eosio.forum clnproposal '{"proposal_name": "example", "max_count": 100}' -p voter1@active -``` -或 -``` -eosc forum clean-proposal [cleaner_account_name] example 100 -``` - -------------------------- - #### Action `post` 发布一个帖子。 @@ -442,7 +374,6 @@ eosc forum status voter2 "" - `title`（type`string`） - 提案的标题，提案的简要说明 - `proposal_json`（type`tring`） - 元数据的JSON提议，尚无规范，请见[JSON结构指南](#json-structure-guidelines) - `created_at`（type` time_point_sec`） - 创建提案的日期，ISO 8601字符串格式（UTC）**不含**时区修饰符。 -- `expires_at`（type`time_point_sec`） - 提案过期的日期，ISO 8601字符串格式（UTC）**不含**时区修饰符。 ##### 指数 - 一号（`1` type `name`) - 按 `proposal_name` 字段索引 diff --git a/contracts/eosio.forum/README.md b/contracts/eosio.forum/README.md index 33aa22c..6e2de67 100644 --- a/contracts/eosio.forum/README.md +++ b/contracts/eosio.forum/README.md @@ -28,34 +28,13 @@ vote value of `0` (negative vote) and you perform a second `vote` action on the this time with a value of `1` (positive vote), your current vote for the proposal is now `1`. There is no decay once you have voted. Once you vote, it does not change, nor is it removed -until you either call `unvote`, or the proposal has been cleaned up by the `clnproposal` action. +until you either call `unvote`. Once a vote has been cast, a user can remove its vote via the `unvote` action. The `unvote` action is called using the voter's account and proposal's name. An `unvote` action completely removes your vote from the proposal and clears the RAM usage associated to that vote. -While a proposal is still active a proposer can decide to manually expire it -by calling the `expire` action which receives as its only argument the `proposal_name`. -This amends the proposal's `expires_at` field to the current time instead of waiting for -its original expiration date to be reached. - -Once a proposal is expired (be it manually or automatically if it passed its expiration date), the -proposal enters a 3 day freeze period. Within this freeze period, the proposal is locked -and no actions can be called on it (no vote changes, no vote removal (`unvote`) and no clean up). -This is to allow a period where multiple tools can query the results for cross-verification. -Once a proposal has ended its freeze period, it's now possible to clean it via the `clnproposal` action. -The `clnproposal` action receives the `proposal_name` and a `max_count` value. `clnproposal` is done in -batch, each batch removing an amount of votes on the proposal (received via the `max_count` variable). -Once all votes are removed on a proposal, the proposal itself is removed. - -The clean proposal effectively reclaims all RAM consumed for votes and for the proposal itself. The -RAM is thus given back to voters (for their votes) and to the proposer (for the proposal). - -The `clnproposal` action can be called by anybody, there are no restrictions. There is no risk since -only expired proposals that have passed their freeze period can be cleaned. Thus, no issues can -arise by cleaning proposals. - ### Development Prerequisites: @@ -184,10 +163,9 @@ details about the status: Here is the list of possible actions: - [propose](#action-propose) -- [expire](#action-expire) +- [cancel](#action-cancel) - [vote](#action-vote) - [unvote](#action-unvote) -- [clnproposal](#action-clnproposal) - [post](#action-post) - [unpost](#action-unpost) - [status](#action-status) @@ -202,7 +180,6 @@ Propose a new proposal to the community. - `proposal_name` (type `name`) - The proposal's name, its ID among all proposals - `title` (type `string`) - The proposal's title (must be less than 1024 characters) - `proposal_json` (type `string`) - The proposal's JSON metadata, no specification yet, see [Proposal JSON Structure](#proposal-json-structure-guidelines) -- `expires_at` (type `time_point_sec`) - The expiration date of the proposal, must be no later than 6 months in the future, ISO 8601 string format (in UTC) **without** a timezone modifier. ##### Rejections @@ -210,12 +187,11 @@ Propose a new proposal to the community. - When `proposal_name` already exists - When `title` is longer than 1024 characters - When `proposal_json` JSON is invalid or too large (must be a JSON object and be less than 32768 characters) -- When `expires_at` date is earlier than now or later than 6 months in the future ##### Example ``` -eosc tx create eosio.forum propose '{"proposer": "proposer1", "proposal_name": "example", "title": "The title, for list views", "proposal_json": "", "expires_at": "2019-01-30T17:03:20"}' -p proposer1@active +eosc tx create eosio.forum propose '{"proposer": "proposer1", "proposal_name": "example", "title": "The title, for list views", "proposal_json": ""}' -p proposer1@active ``` OR @@ -257,12 +233,6 @@ Remove your current active vote, effectively reclaiming the stored RAM of the vo your vote will not count anymore (neither positively or negatively) on the current proposal's voting statistics. -It's **not** possible to `unvote` on a proposal that is expired but within its freeze period of 3 days. -If the proposal is expired and the freeze period has elapsed, it's possible to `unvote` on the proposal. -To be nice to the community however, you should call [clnproposal](#action-clnproposal) until the proposal -is fully cleaned up so that every vote will be removed and RAM will be freed for all voters. - - ##### Parameters - `voter` (type `name`) - The actual voter's account @@ -272,7 +242,6 @@ is fully cleaned up so that every vote will be removed and RAM will be freed for - When missing signature of `voter` - When `proposal_name` does not exist -- When `proposal_name` is expired but within its freeze period of 3 days ##### Example @@ -284,75 +253,28 @@ OR eosc forum unvote voter1 example ``` -#### Action `expire` +#### Action `cancel` -Immediately expires a currently active proposal. The proposal can only be expired by the original proposer -that created it. It's not valid to expire an already expired proposal. +Is used to cancel a `proposal_name` authorized by the `proposer`. ##### Parameters -- `proposal_name` (type `name`) - The proposal's name to expire +- `proposer` (type `name`) - The original proposer +- `proposal_name` (type `name`) - The proposal's name to cancel ##### Rejections - When missing signatures of proposal's `proposer` - When `proposal_name` does not exist -- When `proposal_name` is already expired ##### Example ``` -eosc tx create eosio.forum expire '{"proposal_name": "example"}' -p proposer1@active -``` -OR -``` -eosc forum expire proposer1 example +eosc tx create eosio.forum cancel '{"proposer": "proposer1", "proposal_name": "example"}' -p proposer1@active ``` **Note** `proposer1` must be the same as the one that created initially the `example` proposal. -#### Action `clnproposal` - -Clean a proposal from all its votes and the proposal itself once there are no more associated votes. The action -works iteratively, receiving a `max_count` value. It removes as many as `max_count` votes. When there -are no more votes, the proposal itself is deleted. - -This effectively clears all the RAM consumed for a proposal and all its votes. Call the action multiple -times until all votes are removed. - -It's possible to clean a proposal only if it has expired and if its freeze period of 3 days has fully -elapsed. Within the freeze period, the proposal is locked and no actions can be performed on it. -Since only expired proposals can be cleaned, anybody can invoke this action, no authorization is required. -Voters, proposers, or any community member is invited to call `clnproposal` to clean the RAM related to -a proposal. - -**Note** Since a proposal can expire only by a manual action issued by the proposal's author or if it -has passed its `expires_at` value, it's safe to be called by anybody since the proposal has effectively -terminated its lifecycle. - -##### Parameters -- `cleaner_account` (type `name`) - The account that CPU/NET will be charged to -- `proposal_name` (type `name`) - The proposal's name to clean -- `max_count` (type `uint64`) - The amount of votes to clean out in this batch - -##### Rejections - -- When `proposal_name` is not expired yet -- When `proposal_name` is expired but within its freeze period of 3 days - -**Note** Giving a `max_count` that is too big increases the probability that the transaction -fails due to excessive CPU usage. Find the sweet spot to avoid that. - -##### Example - -``` -eosc tx create eosio.forum clnproposal '{"proposal_name": "example", "max_count": 100}' -p voter1@active -``` -OR -``` -eosc forum clean-proposal [cleaner_account_name] example 100 -``` - #### Action `post` ##### Parameters @@ -457,7 +379,6 @@ eosc forum status voter2 "" - `title` (type `string`) - The proposal's title, a brief description of the proposal - `proposal_json` (type `string`) - The proposal's JSON metadata, no specification yet, see [Proposal JSON Structure Guidelines](#proposal-json-structure-guidelines) - `created_at` (type `time_point_sec`) - The date at which the proposal's was created, ISO 8601 string format (in UTC) **without** a timezone modifier. -- `expires_at` (type `time_point_sec`) - The date at which the proposal's will expire, ISO 8601 string format (in UTC) **without** a timezone modifier. ##### Indexes - First (`1` type `name`) - Index by `proposal_name` field diff --git a/contracts/eosio.forum/resources/forum.contracts.md b/contracts/eosio.forum/resources/forum.contracts.md index 0c57845..808077a 100644 --- a/contracts/eosio.forum/resources/forum.contracts.md +++ b/contracts/eosio.forum/resources/forum.contracts.md @@ -1,30 +1,3 @@ -

clnproposal

- -## Description - -This action is used to clear the RAM being used to store all information related to -{{ proposal_name }}. All associated votes must be cleared before {{ proposal_name }} -can be cleared from the RAM of {{ proposer }}. - -This action can be called by any user, requiring no authorization. - -This action can only be called 72 hours after {{ expires_at }} has been reached. -{{ expires_at }} is set at the moment that {{ proposal_name }} is created, and can -only be updated by {{ proposer }}. This will allow time to compute a tally of all -associated votes before it can be cleared. - -The user who calls `clnproposal` will pay the CPU and NET bandwidth required -to process the action. They will need to specify `max_count` to ensure that the -action can be processed within a single block's maximum allowable limits. - -

expire

- -## Description - -`expire` can only be called by {{ proposer }}. - -`expire` is used to modify the value of `expires_at` to the current time at which the action is called. Once `expire` has been called, no more `vote` actions will be accepted for {{ proposal_name }}. {{ proposal_name }} can be cleared from RAM 72 hours after {{ proposer }} has called the `expire` action. -

post

## Description @@ -72,9 +45,6 @@ I, {{ poster }} understand that this action will not remove the message from cir `unvote` allows a user to remove their vote of {{ vote_value }} they have previously cast on {{ proposal_name }}. -`unvote` will not function during the 72 hour period after -{{ proposal_name }} has expired at {{ expires_at }}. - The RAM that was used to store the vote shall be freed-up immediately after `unvote` has been called by {{ voter }}. @@ -92,12 +62,6 @@ If I, {{ voter }}, am registered as a proxy and am casting votes on behalf of ot I, {{ voter }}, stipulate I have not and will not accept anything of value in exchange for this `vote`, on penalty of confiscation of these tokens, and other penalties. -

extend

- -## Description - -`extend` is used to extend the {{ expires_at }} timestamp value of a {{ proposal_name }} authorized by the {{ proposer }}. -

cancel

## Description