eos.store Steem Profile | Ecosynthesizer

@eos.store

steemit.com/@eos.store

VOTING POWER100.00%

DOWNVOTE POWER100.00%

RESOURCE CREDITS100.00%

REPUTATION PROGRESS24.69%

Net Worth

0.538USD

STEEM

0.635STEEM

SBD

0.605SBD

Own SP

3.786SP

Detailed Balance

STEEM
balance	0.394STEEM	STEEM
market_balance	0.000STEEM	STEEM
savings_balance	0.000STEEM	STEEM
reward_steem_balance	0.241STEEM	STEEM
STEEM POWER
Own SP	3.786SP	SP
Delegated Out	0.000SP	SP
Delegation In	0.000SP	SP
Effective Power	3.786SP	SP
Reward SP (pending)	0.545SP	SP
SBD
sbd_balance	0.075SBD	SBD
sbd_conversions	0.000SBD	SBD
sbd_market_balance	0.000SBD	SBD
savings_sbd_balance	0.000SBD	SBD
reward_sbd_balance	0.530SBD	SBD

{
  "balance": "0.394 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.241 STEEM",
  "vesting_shares": "6164.870944 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "sbd_balance": "0.075 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.530 SBD",
  "conversions": []
}

Account Info

name	eos.store
id	944892
rank	1,060,006
reputation	13757815831
created	2018-04-17T03:08:27
recovery_account	blocktrades
proxy	None
post_count	19
comment_count	0
lifetime_vote_count	0
witnesses_voted_for	0
last_post	2018-08-20T02:18:09
last_root_post	2018-08-20T02:18:09
last_vote_time	2018-10-11T06:52:45
proxied_vsf_votes	0, 0, 0, 0
can_vote	1
voting_power	9,799
delayed_votes	0
balance	0.394 STEEM
savings_balance	0.000 STEEM
sbd_balance	0.075 SBD
savings_sbd_balance	0.000 SBD
vesting_shares	6164.870944 VESTS
delegated_vesting_shares	0.000000 VESTS
received_vesting_shares	0.000000 VESTS
reward_vesting_balance	1106.397925 VESTS
vesting_balance	0.000 STEEM
vesting_withdraw_rate	0.000000 VESTS
next_vesting_withdrawal	1969-12-31T23:59:59
withdrawn	0
to_withdraw	0
withdraw_routes	0
savings_withdraw_requests	0
last_account_recovery	1970-01-01T00:00:00
reset_account	null
last_owner_update	1970-01-01T00:00:00
last_account_update	2018-05-06T07:14:15
mined	No
sbd_seconds	0
sbd_last_interest_payment	1970-01-01T00:00:00
savings_sbd_last_interest_payment	1970-01-01T00:00:00

{
  "id": 944892,
  "name": "eos.store",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM8BYVSa8JugxbWUuq4VjiKpV9RCwTfHk2QqyM4V5eRv2QC6GB4q",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6MEUkzUgimR2AvJbGTy1xFoVjMcJtJvww5b5eL92khAuQyLAXH",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5kGkRBYXfQPAMdtwA82uS5xGGP1An4YWsNqarWV9C5MM85LFz3",
        1
      ]
    ]
  },
  "memo_key": "STM4uMqkUDVNDF5Pwpr1og3XNH9sbzDreQRDqoTrHjkiYZ3cn3rvm",
  "json_metadata": "{\"profile\":{\"name\":\"EosStore\",\"website\":\"http://www.eos.store\",\"profile_image\":\"https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg\",\"cover_image\":\"https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg\"}}",
  "posting_json_metadata": "{\"profile\":{\"name\":\"EosStore\",\"website\":\"http://www.eos.store\",\"profile_image\":\"https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg\",\"cover_image\":\"https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg\"}}",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "2018-05-06T07:14:15",
  "created": "2018-04-17T03:08:27",
  "mined": false,
  "recovery_account": "blocktrades",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 19,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "6041573525",
    "last_update_time": 1539240765
  },
  "downvote_manabar": {
    "current_mana": 0,
    "last_update_time": 1523934507
  },
  "voting_power": 9799,
  "balance": "0.394 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.075 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2018-05-06T06:39:00",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.530 SBD",
  "reward_steem_balance": "0.241 STEEM",
  "reward_vesting_balance": "1106.397925 VESTS",
  "reward_vesting_steem": "0.545 STEEM",
  "vesting_shares": "6164.870944 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 1139,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2018-08-20T02:18:09",
  "last_root_post": "2018-08-20T02:18:09",
  "last_vote_time": "2018-10-11T06:52:45",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "13757815831",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 1060006
}

Withdraw Routes

Incoming	Outgoing
Empty	Empty

{
  "incoming": [],
  "outgoing": []
}

From Date

To Date

steemitboardreplied to @eos.store / steemitboard-notify-eosstore-20190417t034813000z

2019/04/17 03:48:12 UTC

32,112,565|c7b5ae6

parent author	eos.store
parent permlink	eos-store-block-producer-report
author	steemitboard
permlink	steemitboard-notify-eosstore-20190417t034813000z
title
body	Congratulations @eos.store! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eos.store/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@eos.store) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=eos.store)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata	{"image":["https://steemitboard.com/img/notify.png"]}
Transaction Info	Block #32112565/Trx c7b5ae6202e5b0624a0452db11d9422a8f3c853c

View Raw JSON Data

{
  "trx_id": "c7b5ae6202e5b0624a0452db11d9422a8f3c853c",
  "block": 32112565,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-04-17T03:48:12",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "eos-store-block-producer-report",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-eosstore-20190417t034813000z",
      "title": "",
      "body": "Congratulations @eos.store! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eos.store/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@eos.store) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=eos.store)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

eos.storefollowed @dan

2018/11/08 16:03:48 UTC

27,524,117|10039ea

required auths	[]
required posting auths	["eos.store"]
id	follow
json	["follow",{"follower":"eos.store","following":"dan","what":["blog"]}]
Transaction Info	Block #27524117/Trx 10039eaddadd5e2200b8ebf7b32d315b9403ff40

View Raw JSON Data

{
  "trx_id": "10039eaddadd5e2200b8ebf7b32d315b9403ff40",
  "block": 27524117,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-08T16:03:48",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "eos.store"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"eos.store\",\"following\":\"dan\",\"what\":[\"blog\"]}]"
    }
  ]
}

eos.storeupvoted (100.00%) @donkeypong / attack-of-the-heffalump-bees-part-6-of-6

2018/10/11 06:52:45 UTC

26,707,336|75e31b8

voter	eos.store
author	donkeypong
permlink	attack-of-the-heffalump-bees-part-6-of-6
weight	10000 (100.00%)
Transaction Info	Block #26707336/Trx 75e31b81832b14bfa7271e18385e24acfcb13267

View Raw JSON Data

{
  "trx_id": "75e31b81832b14bfa7271e18385e24acfcb13267",
  "block": 26707336,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-10-11T06:52:45",
  "op": [
    "vote",
    {
      "voter": "eos.store",
      "author": "donkeypong",
      "permlink": "attack-of-the-heffalump-bees-part-6-of-6",
      "weight": 10000
    }
  ]
}

eos.storefollowed @igorls

2018/08/24 05:52:15 UTC

25,340,265|3df207e

required auths	[]
required posting auths	["eos.store"]
id	follow
json	["follow",{"follower":"eos.store","following":"igorls","what":["blog"]}]
Transaction Info	Block #25340265/Trx 3df207eca826ce11df736bcf79eecd385558fad3

View Raw JSON Data

{
  "trx_id": "3df207eca826ce11df736bcf79eecd385558fad3",
  "block": 25340265,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-24T05:52:15",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "eos.store"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"eos.store\",\"following\":\"igorls\",\"what\":[\"blog\"]}]"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / eos-store-block-producer-report

2018/08/20 15:32:54 UTC

25,236,714|16b8316

voter	tsto
author	eos.store
permlink	eos-store-block-producer-report
weight	10000 (100.00%)
Transaction Info	Block #25236714/Trx 16b831648fa1bd85e0b024bc8c4cc4fdc03c10b3

View Raw JSON Data

{
  "trx_id": "16b831648fa1bd85e0b024bc8c4cc4fdc03c10b3",
  "block": 25236714,
  "trx_in_block": 27,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T15:32:54",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: eos-store-block-producer-report

2018/08/20 02:18:09 UTC

25,220,825|1568bcd

parent author
parent permlink	roadmap
author	eos.store
permlink	eos-store-block-producer-report
title	EOS Store Block Producer Report
body	<html> <h2><strong>1. Public website URL and at least one social media account (all social media links offered by candidate will be shared in report)</strong></h2> <ul> <li>Official Website: <a href="https://www.eos.store/">https://www.eosstore.co</a></li> <li>Email: [email protected] </li> <li>Github: <a href="https://github.com/eosstore">https://github.com/eosstore </a></li> <li>Telegram: <a href="https://t.me/StoreEos">https://t.me/StoreEos </a></li> <li>Twitter: <a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a></li> <li>Wechat official account：EosStore </li> </ul> <h2>2. Links to the following ID information</h2> <ul> <li>Official block producer candidate: <strong>EOS Store</strong></li> <li>Location of company headquarters: <strong>Beijing, China</strong></li> <li>Expected location of servers: <strong>Tokyo, Taiwan</strong></li> <li>Type of servers: <strong>Cloud</strong></li> </ul> <h2>Employees</h2> <h3>Lu Haifeng  (CEO of EOS Store)</h3> <p>Mr. Lu, graduating from School of Economics and Management of Tsinghua University with finance MBA as his major, invested EOS token in its early stages. He is one of the first entrepreneurs based in Garage Cafe, an enthusiast of block chain technology and EOS believer holding over 7-digit  EOS token.</p> <p><img src="https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]" width="512" height="512"/></p> <h3>Simon ( CTO of EOS Store)</h3> <p>Simon has full participation in the R&D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Proficient in 5 more programming languages, Simon has built a micro e-commerce system by himself. Besides, he also has done more research on artificial intelligence.Now, Simon devotes himself into the blockchain technology and the subversive revolution it will bring about.</p> <p><img src="https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]" width="512" height="512"/></p> <h3>JJ   (COO of EOS Store)</h3> <p>As an early supporter of EOS, JJ worked in investment & Internet areas for 5 years. She was the Chinese representative of a EB5 project responsible for the recruitment of its second phase in mainland China. As a senior marketing consultant of MLN Singapore, JJ once successfully helped dozens of entrepreneurs find perfect resource match. Besides, she also worked for Red Castle as its CMO, promoting the communication between China’s startup teams and startupers from such six countries as the UK, the US and Chile.</p> <p><img src="https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]" width="520" height="520"/></p> <h2>3. Estimate of technical specifications and total expenditure for resources by June 3, 2018</h2> <p>As a blockchain system supporting very high TPS, EOS nodes require strong hardware and network bandwidth, and need to ensure that services are highly available; In order to prevent hackers from malicious attacks, nodes need strict security protection; In addition, high-level monitoring systems as well as operation and maintenance teams are required to ensure the stable operation of the system. As the whole network traffic of EOS increases gradually, the node hardware and related configurations need to be upgraded smoothly. As EOS BPC, we will provide the main-network node and test-network node. <br> As a whole, we provide “one active plus two standbys” deployment mode and divide the hardware configuration into multiple phases. When the EOS network traffic reaches 70% of the capacity of the master node in the first phase, we will migrate to the second phase, and then the third and the fourth phase accordingly.<br> </p> <p>The first phase<br> Master node (AWS x1e.16xlarge) vCPU:64  Memory:1Tb   Bandwidth:10Gb  Storage:AWS EFS 100Tb  Location:Japan<br> Two standby nodes（AWS x1e.16xlarge） vCPU:64  Memory:1Tb   Bandwidth:10Gb  Storage:AWS EFS 100Tb  Location:Japan, Singapore<br> The second phase<br> Master node (AWS x1e.32xlarge) vCPU:128  Memory:2Tb   Bandwidth:25Gb  Storage:AWS EFS 200Tb  Location:Japan<br> Two standby nodes（AWS x1e.32xlarge） vCPU:128  Memory:2Tb   Bandwidth:25Gb  Storage:AWS EFS 200Tb  Location:Japan, Singapore<br> The configuration of test node  vCPU:16  Memory:128G Bandwidth:1Gb  Storage:AWS EFS 10Tb  Location:Japan<br> Monitoring, Operating and maintaining<br> Use AWS's monitoring service and set alarm thresholds. If there is any abnormality,the operation and maintenance teams will be notified to perform maintenance via the social system; In addition, automatic processing mechanism for service fault is required to be developed, thus to promising the high availability of the service.<br> Network Security Select strict safety precautions,such as using DDoS attack protection, WAF, traffic cleaning, key management, risk control, penetration testing;The most stringent security measures are adopted at the operating system level and the cloud gateway level.<br> Total budget<br> About 600k$ per year.</p> <h2>4. Estimated scaling plan for hardware after June 3, 2018</h2> <p>As mentioned above,the hardware configuration takes multiple phases. Each phase has a master node and two standby nodes.From the previous phase to the next phase,we will start three new nodes at first. When these nodes have synchronized all the data and can run stably, they will become the working nodes. At this time, the three nodes in the previous phase will be deleted and the smooth migration will be completed. </p> <h2>5. Community benefit project outline, only for projects expected to be public by June 3, 2018</h2> <p>Every member of Eos. EosStore community is EOS holder. To provide these community members with better services, we share EOS-related information and hold EOS events regularly. Meanwhile, to better serve app developers, we have set up EOS college to provide technical training and exchange. EOS holders now can access the community by voting for us and receive some exclusive benefits such as votig, technical development training and project investment in the community.  <br> Surrounding the community, store and fund, the future development of EOS ecosystem is determined by each community member based on consensus, and we believe that EOS ecosystem will become better based on the shared vision and consensus.  </p> <h2>6. Listing of Telegram and node names for community testnet participation.</h2> <p>Node name: eos.store Telegram: <a href="https://t.me/StoreEos">https://t.me/StoreEos</a> Textnet: node add is 13.230.91.225, http port is 8888, p2p port is 9876 </p> <h3>7. Block Producer Candidate Roadmap on values, community project timeline, finances, transparency, or any other topic the candidate deems important. Please show the direction and future of your candidacy in a Steem post for the community. Any roadmap labeled as such by the block producer candidate will earn a check mark - community gauges the effort.  </h3> <p>EosStore has made a variety of technology preparation and joined EOS Force testnet before building its testnet on AWS cloud host and performing DDoS test. A high availability proposal and daemons have been written before a stress test. Meanwhile, EosStore has formulate its operation and maintenance plan to ensure safely stable operation of BP. Besides, we participated in such activities as 2018 Global Graphene Developer Conference and built EosStore community. 2 Q&M and 4 R&D have been configured to set up system respectively and to implement various kinds of tests. Next, EosStore will develop DApp and some development auxiliary tools, making it easier for developers to develop DApp. Activities for developers will be organized to make the EOS ecosystem grow. 2 O&M and 6 R&D will be configured, developing DApp and its auxiliary tools respectively. Then 2 O&M and 8 R&D will be configured, responsible for the development of underling source code, DApp and its auxiliary tools.</p> <h3>8. Position on Dividends (The sharing of Block Producer inflation rewards with unaffiliated voters, AKA "vote buying.”) Please describe the block producer candidate's stance on sharing inflation rewards and/or paying dividends to EOS token holders. Will the organization offer payment to EOS token voters for any reason, including BP elections AND worker proposals? Does the organization have a written policy of no-payment for votes? If so, please provide a link.  </h3> <p>EosStore will neither promise any types of dividend nor enter into an alliance with some voters. We strongly object to introducing the idea of dividend in the EOS community. Vote-buying should be prohibited absolutely, as a massive vote-buying may lead to the collapse of EOS economic mode. In terms of how to attract more votes, the three key elements is determined.(a) we will establish and expand our at the node of maintenance and the development of EOS technology advantage.(b), we establish a high quality professional community for developers to develop technical training (c) we will assume the role of incubator, cultivate excellent EOS Dapp project and contribute to the EOS ecosystem.We believe that voters real, meaningful returns is a long-term vision, given the greater the overall interests of EOS community and focuses on how to use the actual strategy to extend the EOS ecosystem.<br> We will be completely independent of the voters.We have neither any dividend commitment, no association with voters.This is our bottom line.In showing us the independence of the voters, we will not make any intentional announcement.Our strategy is to establish and maintain a highly transparent with public relations.We warmly welcome the community to public scrutiny. </p> </html>
json metadata	{"tags":["roadmap","views","and","dividends"],"image":["https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]","https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]","https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]"],"links":["https://www.eos.store/","https://github.com/eosstore","https://t.me/StoreEos","https://twitter.com/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #25220825/Trx 1568bcd0815a54f1d02766f980f2fd81347e1f6f

View Raw JSON Data

{
  "trx_id": "1568bcd0815a54f1d02766f980f2fd81347e1f6f",
  "block": 25220825,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T02:18:09",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "roadmap",
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report",
      "title": "EOS Store Block Producer Report",
      "body": "<html>\n<h2><strong>1. Public website URL and at least one social media account (all social media links offered by candidate will be shared in report)</strong></h2>\n<ul>\n  <li>Official Website: <a href=\"https://www.eos.store/\">https://www.eosstore.co</a></li>\n  <li>Email: [email protected]&nbsp;</li>\n  <li>Github: <a href=\"https://github.com/eosstore\">https://github.com/eosstore&nbsp;</a></li>\n  <li>Telegram: <a href=\"https://t.me/StoreEos\">https://t.me/StoreEos&nbsp;</a></li>\n  <li>Twitter: <a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a></li>\n  <li>Wechat official account：EosStore&nbsp;</li>\n</ul>\n<h2>2. Links to the following ID information</h2>\n<ul>\n  <li>Official block producer candidate: <strong>EOS Store</strong></li>\n  <li>Location of company headquarters: <strong>Beijing, China</strong></li>\n  <li>Expected location of servers: <strong>Tokyo, Taiwan</strong></li>\n  <li>Type of servers: <strong>Cloud</strong></li>\n</ul>\n<h2>Employees</h2>\n<h3>Lu Haifeng &nbsp;(CEO of EOS Store)</h3>\n<p>Mr. Lu, graduating from School of Economics and Management of Tsinghua University with finance MBA as his major, invested EOS token in its early stages. He is one of the first entrepreneurs based in Garage Cafe, an enthusiast of block chain technology and EOS believer holding over 7-digit &nbsp;EOS token.</p>\n<p><img src=\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\" width=\"512\" height=\"512\"/></p>\n<h3>Simon ( CTO of EOS Store)</h3>\n<p>Simon has full participation in the R&amp;D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Proficient in 5 more programming languages, Simon has built a micro e-commerce system by himself. Besides, he also has done more research on artificial intelligence.Now, Simon devotes himself into the blockchain technology and the subversive revolution it will bring about.</p>\n<p><img src=\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\" width=\"512\" height=\"512\"/></p>\n<h3>JJ &nbsp;&nbsp;(COO of EOS Store)</h3>\n<p>As an early supporter of EOS, JJ worked in investment &amp; Internet areas for 5 years. She was the Chinese representative of a EB5 project responsible for the recruitment of its second phase in mainland China. As a senior marketing consultant of MLN Singapore, JJ once successfully helped dozens of entrepreneurs find perfect resource match. Besides, she also worked for Red Castle as its CMO, promoting the communication between China’s startup teams and startupers from such six countries as the UK, the US and Chile.</p>\n<p><img src=\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\" width=\"520\" height=\"520\"/></p>\n<h2>3. Estimate of technical specifications and total expenditure for resources by June 3, 2018</h2>\n<p>As a blockchain system supporting very high TPS, EOS nodes require strong hardware and network bandwidth, and need to ensure that services are highly available; In order to prevent hackers from malicious attacks, nodes need strict security protection; In addition, high-level monitoring systems as well as operation and maintenance teams are required to ensure the stable operation of the system. As the whole network traffic of EOS increases gradually, the node hardware and related configurations need to be upgraded smoothly. As EOS BPC, we will provide the main-network node and test-network node.&nbsp;<br>\nAs a whole, we provide “one active plus two standbys” deployment mode and divide the hardware configuration into multiple phases. When the EOS network traffic reaches 70% of the capacity of the master node in the first phase, we will migrate to the second phase, and then the third and the fourth phase accordingly.<br>\n</p>\n<p>The first phase<br>\nMaster node (AWS x1e.16xlarge) vCPU:64 &nbsp;Memory:1Tb &nbsp;&nbsp;Bandwidth:10Gb &nbsp;Storage:AWS EFS 100Tb &nbsp;Location:Japan<br>\nTwo standby nodes（AWS x1e.16xlarge） vCPU:64 &nbsp;Memory:1Tb &nbsp;&nbsp;Bandwidth:10Gb &nbsp;Storage:AWS EFS 100Tb &nbsp;Location:Japan, Singapore<br>\nThe second phase<br>\nMaster node (AWS x1e.32xlarge) vCPU:128 &nbsp;Memory:2Tb &nbsp;&nbsp;Bandwidth:25Gb &nbsp;Storage:AWS EFS 200Tb &nbsp;Location:Japan<br>\nTwo standby nodes（AWS x1e.32xlarge） vCPU:128 &nbsp;Memory:2Tb &nbsp;&nbsp;Bandwidth:25Gb &nbsp;Storage:AWS EFS 200Tb &nbsp;Location:Japan, Singapore<br>\nThe configuration of test node &nbsp;vCPU:16 &nbsp;Memory:128G Bandwidth:1Gb &nbsp;Storage:AWS EFS 10Tb &nbsp;Location:Japan<br>\nMonitoring, Operating and maintaining<br>\nUse AWS's monitoring service and set alarm thresholds. If there is any abnormality,the operation and maintenance teams will be notified to perform maintenance via the social system; In addition, automatic processing mechanism for service fault is required to be developed, thus to promising the high availability of the service.<br>\nNetwork Security&nbsp;Select strict safety precautions,such as using DDoS attack protection, WAF, traffic cleaning, key management, risk control, penetration testing;The most stringent security measures are adopted at the operating system level and the cloud gateway level.<br>\nTotal budget<br>\nAbout 600k$ per year.</p>\n<h2>4. Estimated scaling plan for hardware after June 3, 2018</h2>\n<p>As mentioned above,the hardware configuration takes multiple phases. Each phase has a master node and two standby nodes.From the previous phase to the next phase,we will start three new nodes at first. When these nodes have synchronized all the data and can run stably, they will become the working nodes. At this time, the three nodes in the previous phase will be deleted and the smooth migration will be completed.&nbsp;</p>\n<h2>5. Community benefit project outline, only for projects expected to be public by June 3, 2018</h2>\n<p>Every member of Eos. EosStore community is EOS holder. To provide these community members with better services, we share EOS-related information and hold EOS events regularly. Meanwhile, to better serve app developers, we have set up EOS college to provide technical training and exchange. EOS holders now can access the community by voting for us and receive some exclusive benefits such as votig, technical development training and project investment in the community. &nbsp;<br>\nSurrounding the community, store and fund, the future development of EOS ecosystem is determined by each community member based on consensus, and we believe that EOS ecosystem will become better based on the shared vision and consensus. &nbsp;</p>\n<h2>6. Listing of Telegram and node names for community testnet participation.</h2>\n<p>Node name: eos.store&nbsp;Telegram: <a href=\"https://t.me/StoreEos\">https://t.me/StoreEos</a> Textnet: node add is 13.230.91.225, http port is 8888, p2p port is 9876&nbsp;</p>\n<h3>7. Block Producer Candidate Roadmap on values, community project timeline, finances, transparency, or any other topic the candidate deems important. Please show the direction and future of your candidacy in a Steem post for the community. Any roadmap labeled as such by the block producer candidate will earn a check mark - community gauges the effort. &nbsp;</h3>\n<p>EosStore has made a variety of technology preparation and joined EOS Force testnet before building its testnet on AWS cloud host and performing DDoS test. A high availability proposal and daemons have been written before a stress test. Meanwhile, EosStore has formulate its operation and maintenance plan to ensure safely stable operation of BP. Besides, we participated in such activities as 2018 Global Graphene Developer Conference and built EosStore community. 2 Q&amp;M and 4 R&amp;D have been configured to set up system respectively and to implement various kinds of tests. Next, EosStore will develop DApp and some development auxiliary tools, making it easier for developers to develop DApp. Activities for developers will be organized to make the EOS ecosystem grow. 2 O&amp;M and 6 R&amp;D will be configured, developing DApp and its auxiliary tools respectively. Then 2 O&amp;M and 8 R&amp;D will be configured, responsible for the development of underling source code, DApp and its auxiliary tools.</p>\n<h3>8. Position on Dividends (The sharing of Block Producer inflation rewards with unaffiliated voters, AKA \"vote buying.”) Please describe the block producer candidate's stance on sharing inflation rewards and/or paying dividends to EOS token holders. Will the organization offer payment to EOS token voters for any reason, including BP elections AND worker proposals? Does the organization have a written policy of no-payment for votes? If so, please provide a link. &nbsp;</h3>\n<p>EosStore will neither promise any types of dividend nor enter into an alliance with some voters. We strongly object to introducing the idea of dividend in the EOS community. Vote-buying should be prohibited absolutely, as a massive vote-buying may lead to the collapse of EOS economic mode.&nbsp;In terms of how to attract more votes, the three key elements is determined.(a) we will establish and expand our at the node of maintenance and the development of EOS technology advantage.(b), we establish a high quality professional community for developers to develop technical training (c) we will assume the role of incubator, cultivate excellent EOS Dapp project and contribute to the EOS ecosystem.We believe that voters real, meaningful returns is a long-term vision, given the greater the overall interests of EOS community and focuses on how to use the actual strategy to extend the EOS ecosystem.<br>\nWe will be completely independent of the voters.We have neither any dividend commitment, no association with voters.This is our bottom line.In showing us the independence of the voters, we will not make any intentional announcement.Our strategy is to establish and maintain a highly transparent with public relations.We warmly welcome the community to public scrutiny.&nbsp;</p>\n</html>",
      "json_metadata": "{\"tags\":[\"roadmap\",\"views\",\"and\",\"dividends\"],\"image\":[\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\",\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\",\"https://steemitimages.com/0x0/https://www.eos.store/static/img/person/[email protected]\"],\"links\":[\"https://www.eos.store/\",\"https://github.com/eosstore\",\"https://t.me/StoreEos\",\"https://twitter.com/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / eos-store-supports-the-eos-alliance

2018/08/18 13:42:33 UTC

25,176,928|1530edd

voter	tsto
author	eos.store
permlink	eos-store-supports-the-eos-alliance
weight	10000 (100.00%)
Transaction Info	Block #25176928/Trx 1530edd08c2490f84205a5611805409bbacae171

View Raw JSON Data

{
  "trx_id": "1530edd08c2490f84205a5611805409bbacae171",
  "block": 25176928,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-18T13:42:33",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "eos-store-supports-the-eos-alliance",
      "weight": 10000
    }
  ]
}

steeming-hotupvoted (3.00%) @eos.store / eos-store-supports-the-eos-alliance

2018/08/18 13:12:57 UTC

25,176,336|4e21e13

voter	steeming-hot
author	eos.store
permlink	eos-store-supports-the-eos-alliance
weight	300 (3.00%)
Transaction Info	Block #25176336/Trx 4e21e13914b982904755feda75e857a21f050af2

View Raw JSON Data

{
  "trx_id": "4e21e13914b982904755feda75e857a21f050af2",
  "block": 25176336,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-18T13:12:57",
  "op": [
    "vote",
    {
      "voter": "steeming-hot",
      "author": "eos.store",
      "permlink": "eos-store-supports-the-eos-alliance",
      "weight": 300
    }
  ]
}

eos.storepublished a new post: eos-store-supports-the-eos-alliance

2018/08/18 13:11:42 UTC

25,176,311|732a201

parent author
parent permlink	support
author	eos.store
permlink	eos-store-supports-the-eos-alliance
title	EOS Store Supports the EOS Alliance
body	<html> <p><img src="https://steemitimages.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv/eosstore%20logo%E9%BB%91%E8%89%B2%20%E5%B8%A6%E6%96%87%E5%AD%97%20copy%403x.jpg" width="969" height="318"/></p> <p>                                                                             <img src="https://cdn-images-1.medium.com/max/1600/1*vhXt_i0sA6qX6ClHlhf3Rw.jpeg" width="200" height="200"/>                                                                                   </p> <p><br></p> <p>The EOS Alliance, as a nonprofit entity unveiled today, will serve the EOS community by streamlining and facilitating communication and education that affects EOS token holders, Block Producers, application creators and other stakeholders. We at EOS Store here extend our warm congratulations to the Alliance and are proud to stand by it. EOS Store team, comprised of firm EOS believers and enthusiasts of block chain technology, is committed to building a decentralized community featuring self-ownership, openness, equality and mutual-trust with EOS holders. The idea of EOS Store coincides with that of EOS Alliance.  Besides, Haifeng Lu, our founder and also as a board member of the Alliance, repeatedly expressed the importance of communication for EOS community in online and offline activities. “Voices from community should not be ignored”, as Mr. Lu said, “EOS Store will listen to community members. Everything facilitates the growing of EOS community and the prosperity of EOS ecosystem we will support”. <strong>Leadership of the EOS Alliance</strong> The EOS Alliance will launch initially with a seven (7) member Board, expanding as needed in a process currently under draft. Within 12 months, the EOS Alliance intends to have a fully elected board, to include members of diverse backgrounds and geographic regions, representing a variety of EOS community stakeholders and perspectives. The initial board members are expected to be:  </p> <ul> <li>A seat reserved for special appointment, held in the interim by Lightning Clearwater III, also serving as the Alliance’s General Counsel</li> <li>Brock Pierce, Chairman of the Bitcoin Foundation and former partner at Block.one</li> <li>Galia Benartzi, Co-founder of Bancor and LiquidEOS</li> <li>Peter Li, founder of EOS Gravity, a community leader and Block Producer</li> <li>Haifeng Lu, founder of EOS Store, a Block Producer</li> <li>Nix Nolledo, Philippine Technology Entrepreneur, founder of Blockchain Startup ODX</li> <li>AKON, multi-platinum music artist and blockchain enthusiast</li> </ul> <p>In addition, two observer seats have been established for representatives to be selected by the paid Block Producers via a mechanism to be decided by them. Staff initially will include interim Executive Director Thomas Cox, former Block.one VP of Product (where he led the work on EOS’s governance mechanisms), Deputy Executive Director Myra Wang (Dan Wang), formerly of the influential Chinese community EOS Gravity, and Communications Director Kevin Wilcox, co-founder of EOS Go. <strong>Mandate of the EOS Alliance</strong> The EOS Alliance will serve under its guiding vision of Empowering EOS For All to curate and coordinate various existing efforts within the EOS community. The Alliance will:  </p> <ul> <li>Facilitate multi-language conversations (initially in English, Korean and Chinese) and education around key ecosystem issues, debates and developments.</li> <li>Refrain, in accordance with its bylaws (now being drafted), from gaining any executive power within EOS governance structures.</li> <li>Facilitate discussion and help workgroups make clear recommendations.</li> </ul> <p>As its first act, the EOS Alliance has already begun forming a series of working groups with diverse community participation to inform and advise on the ecosystem’s most challenging topics. Congrats the EOS Alliance again and thanks everyone that contributes to the Alliance. Wish our community to be more prosperous! For more information about the EOS Alliance, clicks <a href="https://medium.com/@eosalliance1/eos-alliance-launches-with-the-mandate-to-empower-eos-for-all-d17055d86a98">here</a>。 </p> <p><br></p> <p><strong>EosStore ｜ Get your commercial DApp ideas off the ground.</strong></p> <p><strong>Contact us</strong></p> <p>Email：[email protected]<br> Telegram：<a href="https://t.me/StoreEos">https://t.me/StoreEos</a><br> Website：<a href="https://www.eos.store/">https://www.eos.store</a><br> Twitter：<a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a><br> Github：<a href="https://github.com/eosstore">https://github.com/eosstore</a><br> Steemit：<a href="https://steemit.com/@eos.store">https://steemit.com/@eos.store</a></p> </html>
json metadata	{"tags":["support","eos","alliance"],"image":["https://steemitimages.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv/eosstore%20logo%E9%BB%91%E8%89%B2%20%E5%B8%A6%E6%96%87%E5%AD%97%20copy%403x.jpg","https://cdn-images-1.medium.com/max/1600/1*vhXt_i0sA6qX6ClHlhf3Rw.jpeg"],"links":["https://medium.com/@eosalliance1/eos-alliance-launches-with-the-mandate-to-empower-eos-for-all-d17055d86a98","https://t.me/StoreEos","https://www.eos.store/","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #25176311/Trx 732a201e2e18368466a99366a58370d42e12a1e3

View Raw JSON Data

{
  "trx_id": "732a201e2e18368466a99366a58370d42e12a1e3",
  "block": 25176311,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-18T13:11:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "support",
      "author": "eos.store",
      "permlink": "eos-store-supports-the-eos-alliance",
      "title": "EOS Store Supports the EOS Alliance",
      "body": "<html>\n<p><img src=\"https://steemitimages.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv/eosstore%20logo%E9%BB%91%E8%89%B2%20%E5%B8%A6%E6%96%87%E5%AD%97%20copy%403x.jpg\" width=\"969\" height=\"318\"/></p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<img src=\"https://cdn-images-1.medium.com/max/1600/1*vhXt_i0sA6qX6ClHlhf3Rw.jpeg\" width=\"200\" height=\"200\"/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>\n<p><br></p>\n<p>The EOS Alliance, as a nonprofit entity unveiled today, will serve the EOS community by streamlining and facilitating communication and education that affects EOS token holders, Block Producers, application creators and other stakeholders. We at EOS Store here extend our warm congratulations to the Alliance and are proud to stand by it. EOS Store team, comprised of firm EOS believers and enthusiasts of block chain technology, is committed to building a decentralized community featuring self-ownership, openness, equality and mutual-trust with EOS holders. The idea of EOS Store coincides with that of EOS Alliance. &nbsp;Besides, Haifeng Lu, our founder and also as a board member of the Alliance, repeatedly expressed the importance of communication for EOS community in online and offline activities. “Voices from community should not be ignored”, as Mr. Lu said, “EOS Store will listen to community members. Everything facilitates the growing of EOS community and the prosperity of EOS ecosystem we will support”. <strong>Leadership of the EOS Alliance</strong> The EOS Alliance will launch initially with a seven (7) member Board, expanding as needed in a process currently under draft. Within 12 months, the EOS Alliance intends to have a fully elected board, to include members of diverse backgrounds and geographic regions, representing a variety of EOS community stakeholders and perspectives. The initial board members are expected to be: &nbsp;</p>\n<ul>\n  <li>A seat reserved for special appointment, held in the interim by Lightning Clearwater III, also serving as the Alliance’s General Counsel</li>\n  <li>Brock Pierce, Chairman of the Bitcoin Foundation and former partner at Block.one</li>\n  <li>Galia Benartzi, Co-founder of Bancor and LiquidEOS</li>\n  <li>Peter Li, founder of EOS Gravity, a community leader and Block Producer</li>\n  <li>Haifeng Lu, founder of EOS Store, a Block Producer</li>\n  <li>Nix Nolledo, Philippine Technology Entrepreneur, founder of Blockchain Startup ODX</li>\n  <li>AKON, multi-platinum music artist and blockchain enthusiast</li>\n</ul>\n<p>In addition, two observer seats have been established for representatives to be selected by the paid Block Producers via a mechanism to be decided by them. Staff initially will include interim Executive Director Thomas Cox, former Block.one VP of Product (where he led the work on EOS’s governance mechanisms), Deputy Executive Director Myra Wang (Dan Wang), formerly of the influential Chinese community EOS Gravity, and Communications Director Kevin Wilcox, co-founder of EOS Go. <strong>Mandate of the EOS Alliance</strong> The EOS Alliance will serve under its guiding vision of Empowering EOS For All to curate and coordinate various existing efforts within the EOS community. The Alliance will: &nbsp;</p>\n<ul>\n  <li>Facilitate multi-language conversations (initially in English, Korean and Chinese) and education around key ecosystem issues, debates and developments.</li>\n  <li>Refrain, in accordance with its bylaws (now being drafted), from gaining any executive power within EOS governance structures.</li>\n  <li>Facilitate discussion and help workgroups make clear recommendations.</li>\n</ul>\n<p>As its first act, the EOS Alliance has already begun forming a series of working groups with diverse community participation to inform and advise on the ecosystem’s most challenging topics. Congrats the EOS Alliance again and thanks everyone that contributes to the Alliance. Wish our community to be more prosperous! For more information about the EOS Alliance, clicks <a href=\"https://medium.com/@eosalliance1/eos-alliance-launches-with-the-mandate-to-empower-eos-for-all-d17055d86a98\">here</a>。&nbsp;</p>\n<p><br></p>\n<p><strong>EosStore ｜ Get your commercial DApp ideas off the ground.</strong></p>\n<p><strong>Contact us</strong></p>\n<p>Email：[email protected]<br>\nTelegram：<a href=\"https://t.me/StoreEos\">https://t.me/StoreEos</a><br>\nWebsite：<a href=\"https://www.eos.store/\">https://www.eos.store</a><br>\nTwitter：<a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a><br>\nGithub：<a href=\"https://github.com/eosstore\">https://github.com/eosstore</a><br>\nSteemit：<a href=\"https://steemit.com/@eos.store\">https://steemit.com/@eos.store</a></p>\n</html>",
      "json_metadata": "{\"tags\":[\"support\",\"eos\",\"alliance\"],\"image\":[\"https://steemitimages.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv/eosstore%20logo%E9%BB%91%E8%89%B2%20%E5%B8%A6%E6%96%87%E5%AD%97%20copy%403x.jpg\",\"https://cdn-images-1.medium.com/max/1600/1*vhXt_i0sA6qX6ClHlhf3Rw.jpeg\"],\"links\":[\"https://medium.com/@eosalliance1/eos-alliance-launches-with-the-mandate-to-empower-eos-for-all-d17055d86a98\",\"https://t.me/StoreEos\",\"https://www.eos.store/\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / eosstore-statement-of-ownership

2018/08/09 22:37:18 UTC

24,928,506|1bba77c

voter	tsto
author	eos.store
permlink	eosstore-statement-of-ownership
weight	10000 (100.00%)
Transaction Info	Block #24928506/Trx 1bba77c4ff68032820a95bca673ce8e1c1a544c6

View Raw JSON Data

{
  "trx_id": "1bba77c4ff68032820a95bca673ce8e1c1a544c6",
  "block": 24928506,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-09T22:37:18",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "eosstore-statement-of-ownership",
      "weight": 10000
    }
  ]
}

ubgupvoted (1.00%) @eos.store / eosstore-statement-of-ownership

2018/08/08 16:49:21 UTC

24,892,765|1d4fa46

voter	ubg
author	eos.store
permlink	eosstore-statement-of-ownership
weight	100 (1.00%)
Transaction Info	Block #24892765/Trx 1d4fa4646b2bce53b0a1883d66b7938f3ca99b66

View Raw JSON Data

{
  "trx_id": "1d4fa4646b2bce53b0a1883d66b7938f3ca99b66",
  "block": 24892765,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-08T16:49:21",
  "op": [
    "vote",
    {
      "voter": "ubg",
      "author": "eos.store",
      "permlink": "eosstore-statement-of-ownership",
      "weight": 100
    }
  ]
}

fastresteemupvoted (1.00%) @eos.store / eosstore-statement-of-ownership

2018/08/08 16:43:54 UTC

24,892,656|6687f2b

voter	fastresteem
author	eos.store
permlink	eosstore-statement-of-ownership
weight	100 (1.00%)
Transaction Info	Block #24892656/Trx 6687f2b8ad2f3b01b7cb9b1f9a2bcc33750256e0

View Raw JSON Data

{
  "trx_id": "6687f2b8ad2f3b01b7cb9b1f9a2bcc33750256e0",
  "block": 24892656,
  "trx_in_block": 29,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-08T16:43:54",
  "op": [
    "vote",
    {
      "voter": "fastresteem",
      "author": "eos.store",
      "permlink": "eosstore-statement-of-ownership",
      "weight": 100
    }
  ]
}

eos.storepublished a new post: eosstore-statement-of-ownership

2018/08/08 16:43:33 UTC

24,892,649|bb5f1af

parent author
parent permlink	statement
author	eos.store
permlink	eosstore-statement-of-ownership
title	EosStore Statement of Ownership
body	<html> <p>EosStore Statement of Ownership EosStore is comprised of true believers and enthusiasts in blockchain technology, determined to join hands with EOS token holders to build a decentralized community, featuring freedom, openness, equality, mutual trust and efficiency. As a block producer, we are total independent, self-funded and owned by three co-founders as below: </p> <p>Haifeng Lu (CEO) </p> <p>Simon Wong (CTO) </p> <p>Jingjing Ji (COO) </p> </html>
json metadata	{"tags":["statement","ownership"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #24892649/Trx bb5f1afee35bbd37f0ba232f48e34a357dd6ff98

View Raw JSON Data

{
  "trx_id": "bb5f1afee35bbd37f0ba232f48e34a357dd6ff98",
  "block": 24892649,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-08T16:43:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "eosstore-statement-of-ownership",
      "title": "EosStore Statement of Ownership",
      "body": "<html>\n<p>EosStore Statement of Ownership EosStore is comprised of true believers and enthusiasts in blockchain technology, determined to join hands with EOS token holders to build a decentralized community, featuring freedom, openness, equality, mutual trust and efficiency. As a block producer, we are total independent, self-funded and owned by three co-founders as below:&nbsp;</p>\n<p>Haifeng Lu (CEO)&nbsp;</p>\n<p>Simon Wong (CTO)&nbsp;</p>\n<p>Jingjing Ji (COO)&nbsp;</p>\n</html>",
      "json_metadata": "{\"tags\":[\"statement\",\"ownership\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

steemitboardreplied to @eos.store / steemitboard-notify-eosstore-20180706t202411000z

2018/07/06 20:24:12 UTC

23,947,596|e694ffb

parent author	eos.store
parent permlink	2018-7-1-eos-information-weekly-or-eosstore
author	steemitboard
permlink	steemitboard-notify-eosstore-20180706t202411000z
title
body	Congratulations @eos.store! You have completed the following achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstpayout.png)](http://steemitboard.com/@eos.store) You got your First payout <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> Do not miss the last post from @steemitboard: [SteemitBoard World Cup Contest - Russia vs Croatia](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-russia-vs-croatia) --- Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)! Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then [Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) and get one more award!
json metadata	{"image":["https://steemitboard.com/img/notify.png"]}
Transaction Info	Block #23947596/Trx e694ffb0a27516dd12be9ec3d94e3383c237e58b

View Raw JSON Data

{
  "trx_id": "e694ffb0a27516dd12be9ec3d94e3383c237e58b",
  "block": 23947596,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-06T20:24:12",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-eosstore-20180706t202411000z",
      "title": "",
      "body": "Congratulations @eos.store! You have completed the following achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstpayout.png)](http://steemitboard.com/@eos.store) You got your First payout\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the last post from @steemitboard:**\n[SteemitBoard World Cup Contest - Russia vs Croatia](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-russia-vs-croatia)\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

blockecologyupvoted (100.00%) @eos.store / 2018-7-1-eos-information-weekly-or-eosstore

2018/07/06 18:12:03 UTC

23,944,955|039d3df

voter	blockecology
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23944955/Trx 039d3dff6f8112b74b62f9a2479c9a8b22996f8e

View Raw JSON Data

{
  "trx_id": "039d3dff6f8112b74b62f9a2479c9a8b22996f8e",
  "block": 23944955,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-06T18:12:03",
  "op": [
    "vote",
    {
      "voter": "blockecology",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

eos.storereceived 0.241 STEEM, 0.433 SBD, 0.639 SP author reward for @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/07/03 08:50:45 UTC

23,848,674|virtual

author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
sbd payout	0.433 SBD
steem payout	0.241 STEEM
vesting payout	1041.298513 VESTS
Transaction Info	Block #23848674/Virtual Operation #4

View Raw JSON Data

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 23848674,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2018-07-03T08:50:45",
  "op": [
    "author_reward",
    {
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "sbd_payout": "0.433 SBD",
      "steem_payout": "0.241 STEEM",
      "vesting_payout": "1041.298513 VESTS"
    }
  ]
}

blocktheoryupvoted (100.00%) @eos.store / 2018-7-1-eos-information-weekly-or-eosstore

2018/07/02 16:58:54 UTC

23,838,189|0b2756f

voter	blocktheory
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23838189/Trx 0b2756f89bd1c2862f1ae34f1bb8c380cc1044eb

View Raw JSON Data

{
  "trx_id": "0b2756f89bd1c2862f1ae34f1bb8c380cc1044eb",
  "block": 23838189,
  "trx_in_block": 51,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T16:58:54",
  "op": [
    "vote",
    {
      "voter": "blocktheory",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

tstoupvoted (100.00%) @eos.store / 2018-7-1-eos-information-weekly-or-eosstore

2018/07/02 12:36:09 UTC

23,832,938|d4ecc39

voter	tsto
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23832938/Trx d4ecc3985a1f41370ee23976a8552a07df1f9d19

View Raw JSON Data

{
  "trx_id": "d4ecc3985a1f41370ee23976a8552a07df1f9d19",
  "block": 23832938,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T12:36:09",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

a-a-areplied to @eos.store / re-eosstore-2018-7-1-eos-information-weekly-or-eosstore-20180702t023049052z

2018/07/02 02:30:48 UTC

23,820,832|6d670bb

parent author	eos.store
parent permlink	2018-7-1-eos-information-weekly-or-eosstore
author	a-a-a
permlink	re-eosstore-2018-7-1-eos-information-weekly-or-eosstore-20180702t023049052z
title
body	# # upvote for me please? https://steemit.com/news/@bible.com/6h36cq #
json metadata	{"tags":["information"],"links":["https://steemit.com/news/@bible.com/6h36cq"],"app":"steemit/0.1"}
Transaction Info	Block #23820832/Trx 6d670bb893ec84d91c61a92e970868167302dc43

View Raw JSON Data

{
  "trx_id": "6d670bb893ec84d91c61a92e970868167302dc43",
  "block": 23820832,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T02:30:48",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "author": "a-a-a",
      "permlink": "re-eosstore-2018-7-1-eos-information-weekly-or-eosstore-20180702t023049052z",
      "title": "",
      "body": "#\n# upvote for me please? https://steemit.com/news/@bible.com/6h36cq\n#",
      "json_metadata": "{\"tags\":[\"information\"],\"links\":[\"https://steemit.com/news/@bible.com/6h36cq\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

eddardupvoted (100.00%) @eos.store / 2018-7-1-eos-information-weekly-or-eosstore

2018/07/02 02:30:42 UTC

23,820,830|032e8b7

voter	eddard
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23820830/Trx 032e8b7affade9227feab3392fb2e5d08ba3a39d

View Raw JSON Data

{
  "trx_id": "032e8b7affade9227feab3392fb2e5d08ba3a39d",
  "block": 23820830,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T02:30:42",
  "op": [
    "vote",
    {
      "voter": "eddard",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

alphabotupvoted (1.00%) @eos.store / 2018-7-1-eos-information-weekly-or-eosstore

2018/07/02 02:30:15 UTC

23,820,821|d26fab5

voter	alphabot
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
weight	100 (1.00%)
Transaction Info	Block #23820821/Trx d26fab50be74cdb323e0015594f8f5d7572e3372

View Raw JSON Data

{
  "trx_id": "d26fab50be74cdb323e0015594f8f5d7572e3372",
  "block": 23820821,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T02:30:15",
  "op": [
    "vote",
    {
      "voter": "alphabot",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "weight": 100
    }
  ]
}

eos.storepublished a new post: 2018-7-1-eos-information-weekly-or-eosstore

2018/07/02 02:30:00 UTC

23,820,816|2bbc162

parent author
parent permlink	information
author	eos.store
permlink	2018-7-1-eos-information-weekly-or-eosstore
title	[2018.7.1 Eos information weekly] \| EosStore
body	<html> <p>Hi, EOSers,<br> </p> <p>Recently, EosStore is giving full support for DApp mainly by organizing weekly technology salons and technical trainings, and by launching development kit. We welcome developers with good projects to communicate with us.<br> EosStore Weekly Report is as follows:<br> </p> <ol> <li>Attending EOS BP Meetings. Only two regular meetings this week. </li> </ol> <p>Main points of discussion on June 25th BP meeting</p> <ol> <li>Update 1.0.6</li> <li>Unregistered Token Contract</li> <li>Referendum</li> <li>Keybase Group admin</li> <li>EMLG video  release</li> <li>BP Tooling</li> <li>Moti introducing ECAF funding </li> </ol> <p>Main points of discussion on June 28th BP meeting</p> <ol> <li>RAM Q&A</li> <li>BP upgrade to v1.0.7 confirmation</li> <li><a href="https://docs.google.com/document/d/1Rbq6tpI_hxjGWYvgL63qfkvZdjqvudWXN1Z6Rm4QJ2s">EMLG Video release</a>confirmation</li> <li>Registered Tokens update</li> <li><a href="https://docs.google.com/document/d/1-KfOHXQpUjf4HfM07o8nEb5JRjiM6VVNzLkz1GJFgN4">Referendum Smart Contract</a>update</li> <li><a href="https://docs.google.com/document/d/1_yxFrdiKcA3uw-Lx5ouvwnG8GiJP-jlN73wipVfOpRc">Keybase group members</a>update</li> <li><a href="https://github.com/eoscanada/eosio.forum">Forum</a>update</li> <li>ECAF funding info - Moti from ECAF was requested to give more info about ECAF funding</li> <li>ECAF Communication Methods - We need to solidify a means of communication from ECAF to BPs, as well as ECAF to community. Should not be figured out in this call, but rather a subgroup should be formed</li> <li><a href="https://docs.google.com/document/d/1ZnXAtdiqndZdnDmvF1yBTnV0XKjU6HdmEC3kGWcPUqo/edit">Who should be present on these calls? Is it by rank? Community involvement? Limit of participant slots per team? (we need more hard-fast rules for this)</a></li> </ol> <p>Links of relevant meeting records are as follows:</p> <ul> <li>BP meeting on June 25th：<a href="https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit">https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit</a></li> <li>BP meeting on June 28th：<a href="https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6">https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6</a></li> </ul> <ol> <li>Participating in EOS Governance of Mandarin Community Meetings and puting forward opinions and suggetions</li> <li>Developing the blacklist detection tool to check whether BPs have updated the blacklist correctly or not</li> <li>On June 27, 2018, EosStore & EOS Cannon translated the proposed [Draft Proposal for ECAF's Official Notification System] released by ECAF in Steemit and promoted it to the Chinese community and BPs.</li> <li>June 30th, 2018, EosStore held the third offline technology salon activity. The activity mainly shared such two themes as EOS Block Producer Election and Smart Contract to provide details of EOS mainnet launch and DApp implementation for developers.</li> <li>By June 24th 14:52,2018, eosstorebest is ranked at 18th among 21 block producers.</li> </ol> <p>have a good day ~</p> <p><br> <strong>EosStore ｜ Get your commercial DApp ideas off the ground.</strong></p> <p><br> Email：[email protected]</p> <p>Telegram：<a href="https://t.me/StoreEos">https://t.me/StoreEos</a></p> <p>Website：<a href="https://www.eos.store/">https://www.eos.store</a> </p> <p>Twitter：<a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a> </p> <p>Github：<a href="https://github.com/eosstore">https://github.com/eosstore</a> </p> <p>Steemit：<a href="https://steemit.com/@eos.store">https://steemit.com/@eos.store</a><br> </p> </html>
json metadata	{"tags":["information","weekly"],"links":["https://docs.google.com/document/d/1Rbq6tpI_hxjGWYvgL63qfkvZdjqvudWXN1Z6Rm4QJ2s","https://docs.google.com/document/d/1-KfOHXQpUjf4HfM07o8nEb5JRjiM6VVNzLkz1GJFgN4","https://docs.google.com/document/d/1_yxFrdiKcA3uw-Lx5ouvwnG8GiJP-jlN73wipVfOpRc","https://github.com/eoscanada/eosio.forum","https://docs.google.com/document/d/1ZnXAtdiqndZdnDmvF1yBTnV0XKjU6HdmEC3kGWcPUqo/edit","https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit","https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6","https://t.me/StoreEos","https://www.eos.store/","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #23820816/Trx 2bbc162fcecb00fd5304c5a3c9aebbde208a7fb5

View Raw JSON Data

{
  "trx_id": "2bbc162fcecb00fd5304c5a3c9aebbde208a7fb5",
  "block": 23820816,
  "trx_in_block": 34,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-02T02:30:00",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "information",
      "author": "eos.store",
      "permlink": "2018-7-1-eos-information-weekly-or-eosstore",
      "title": "[2018.7.1 Eos information weekly] | EosStore",
      "body": "<html>\n<p>Hi, EOSers,<br>\n</p>\n<p>Recently, EosStore is giving full support for DApp mainly by organizing weekly technology salons and technical trainings, and by launching development kit. We welcome developers with good projects to communicate with us.<br>\nEosStore Weekly Report is as follows:<br>\n</p>\n<ol>\n  <li>Attending EOS BP Meetings. Only two regular meetings this week.&nbsp;</li>\n</ol>\n<p>Main points of discussion on June 25th BP meeting</p>\n<ol>\n  <li>Update 1.0.6</li>\n  <li>Unregistered Token Contract</li>\n  <li>Referendum</li>\n  <li>Keybase Group admin</li>\n  <li>EMLG video &nbsp;release</li>\n  <li>BP Tooling</li>\n  <li>Moti introducing ECAF funding&nbsp;</li>\n</ol>\n<p>Main points of discussion on June 28th BP meeting</p>\n<ol>\n  <li>RAM Q&amp;A</li>\n  <li>BP upgrade to v1.0.7 confirmation</li>\n  <li><a href=\"https://docs.google.com/document/d/1Rbq6tpI_hxjGWYvgL63qfkvZdjqvudWXN1Z6Rm4QJ2s\">EMLG Video release</a>confirmation</li>\n  <li>Registered Tokens update</li>\n  <li><a href=\"https://docs.google.com/document/d/1-KfOHXQpUjf4HfM07o8nEb5JRjiM6VVNzLkz1GJFgN4\">Referendum Smart Contract</a>update</li>\n  <li><a href=\"https://docs.google.com/document/d/1_yxFrdiKcA3uw-Lx5ouvwnG8GiJP-jlN73wipVfOpRc\">Keybase group members</a>update</li>\n  <li><a href=\"https://github.com/eoscanada/eosio.forum\">Forum</a>update</li>\n  <li>ECAF funding info - Moti from ECAF was requested to give more info about ECAF funding</li>\n  <li>ECAF Communication Methods - We need to solidify a means of communication from ECAF to BPs, as well as ECAF to community. Should not be figured out in this call, but rather a subgroup should be formed</li>\n  <li><a href=\"https://docs.google.com/document/d/1ZnXAtdiqndZdnDmvF1yBTnV0XKjU6HdmEC3kGWcPUqo/edit\">Who should be present on these calls? Is it by rank? Community involvement? Limit of participant slots per team? (we need more hard-fast rules for this)</a></li>\n</ol>\n<p>Links of relevant meeting records are as follows:</p>\n<ul>\n  <li>BP meeting on June 25th：<a href=\"https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit\">https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit</a></li>\n  <li>BP meeting on June 28th：<a href=\"https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6\">https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6</a></li>\n</ul>\n<ol>\n  <li>Participating in EOS Governance of Mandarin Community Meetings and puting forward opinions and suggetions</li>\n  <li>Developing the blacklist detection tool to check whether BPs have updated the blacklist correctly or not</li>\n  <li>On June 27, 2018, EosStore &amp; EOS Cannon translated the proposed [Draft Proposal for ECAF's Official Notification System] released by ECAF in Steemit and promoted it to the Chinese community and BPs.</li>\n  <li>June 30th, 2018, EosStore held the third offline technology salon activity. The activity mainly shared such two themes as EOS Block Producer Election and Smart Contract to provide details of EOS mainnet launch and DApp implementation for developers.</li>\n  <li>By June 24th 14:52,2018, eosstorebest is ranked at 18th among 21 block producers.</li>\n</ol>\n<p>have a good day ~</p>\n<p><br>\n<strong>EosStore ｜ Get your commercial DApp ideas off the ground.</strong></p>\n<p><br>\nEmail：[email protected]</p>\n<p>Telegram：<a href=\"https://t.me/StoreEos\">https://t.me/StoreEos</a></p>\n<p>Website：<a href=\"https://www.eos.store/\">https://www.eos.store</a>&nbsp;</p>\n<p>Twitter：<a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a>&nbsp;</p>\n<p>Github：<a href=\"https://github.com/eosstore\">https://github.com/eosstore</a>&nbsp;</p>\n<p>Steemit：<a href=\"https://steemit.com/@eos.store\">https://steemit.com/@eos.store</a><br>\n</p>\n</html>",
      "json_metadata": "{\"tags\":[\"information\",\"weekly\"],\"links\":[\"https://docs.google.com/document/d/1Rbq6tpI_hxjGWYvgL63qfkvZdjqvudWXN1Z6Rm4QJ2s\",\"https://docs.google.com/document/d/1-KfOHXQpUjf4HfM07o8nEb5JRjiM6VVNzLkz1GJFgN4\",\"https://docs.google.com/document/d/1_yxFrdiKcA3uw-Lx5ouvwnG8GiJP-jlN73wipVfOpRc\",\"https://github.com/eoscanada/eosio.forum\",\"https://docs.google.com/document/d/1ZnXAtdiqndZdnDmvF1yBTnV0XKjU6HdmEC3kGWcPUqo/edit\",\"https://docs.google.com/document/d/1Lfwg7NCbhq3v_jCHoZuthyHTkktFwm7DQN0dH-x-nDs/edit\",\"https://docs.google.com/document/d/1rAH5fnf1yD9zGGkHOlO-DdUsN_UxSnTTfUAwI5JvYhQ/edit#heading=h.au51mny0sx6\",\"https://t.me/StoreEos\",\"https://www.eos.store/\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

blocktheoryremoved vote from (0.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/28 21:52:54 UTC

23,728,928|e060f6b

voter	blocktheory
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	0 (0.00%)
Transaction Info	Block #23728928/Trx e060f6b57413b71ca99bf39cfaa08b9d0102bf97

View Raw JSON Data

{
  "trx_id": "e060f6b57413b71ca99bf39cfaa08b9d0102bf97",
  "block": 23728928,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-28T21:52:54",
  "op": [
    "vote",
    {
      "voter": "blocktheory",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 0
    }
  ]
}

cigarbuttsreplied to @eos.store / re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180627t111404917z

2018/06/27 11:14:09 UTC

23,687,355|df48adc

parent author	eos.store
parent permlink	statement-of-updating-the-blacklist-from-ecaf
author	cigarbutts
permlink	re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180627t111404917z
title
body	What's the CN corporate registration number for EOS Capital?
json metadata	{"tags":["statement"],"app":"steemit/0.1"}
Transaction Info	Block #23687355/Trx df48adcdaa8054e795625e7b8101906ed03aef1d

View Raw JSON Data

{
  "trx_id": "df48adcdaa8054e795625e7b8101906ed03aef1d",
  "block": 23687355,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-27T11:14:09",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "author": "cigarbutts",
      "permlink": "re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180627t111404917z",
      "title": "",
      "body": "What's the CN corporate registration number for EOS Capital?",
      "json_metadata": "{\"tags\":[\"statement\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

eos.storefollowed @ecaf

2018/06/27 03:45:36 UTC

23,678,384|86d5301

required auths	[]
required posting auths	["eos.store"]
id	follow
json	["follow",{"follower":"eos.store","following":"ecaf","what":["blog"]}]
Transaction Info	Block #23678384/Trx 86d5301484ff65af3acee2c99ab9dc42ed3365c2

View Raw JSON Data

{
  "trx_id": "86d5301484ff65af3acee2c99ab9dc42ed3365c2",
  "block": 23678384,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-27T03:45:36",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "eos.store"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"eos.store\",\"following\":\"ecaf\",\"what\":[\"blog\"]}]"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 22:51:57 UTC

23,672,511|7a83023

voter	tsto
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23672511/Trx 7a83023fb17519bacfd8bb615477ae93eeeb8808

View Raw JSON Data

{
  "trx_id": "7a83023fb17519bacfd8bb615477ae93eeeb8808",
  "block": 23672511,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T22:51:57",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

soleoneupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 22:06:27 UTC

23,671,601|3ba3a3f

voter	soleone
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23671601/Trx 3ba3a3f04d0bcf3d083481ed5d5628fa745bcf30

View Raw JSON Data

{
  "trx_id": "3ba3a3f04d0bcf3d083481ed5d5628fa745bcf30",
  "block": 23671601,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T22:06:27",
  "op": [
    "vote",
    {
      "voter": "soleone",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

blocktheoryupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 19:46:33 UTC

23,668,803|af8f8c5

voter	blocktheory
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23668803/Trx af8f8c58eeca795fac5c23a0245752924e08f492

View Raw JSON Data

{
  "trx_id": "af8f8c58eeca795fac5c23a0245752924e08f492",
  "block": 23668803,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T19:46:33",
  "op": [
    "vote",
    {
      "voter": "blocktheory",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

ammoniteremoved vote from (0.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 16:22:00 UTC

23,664,713|4e2c18b

voter	ammonite
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	0 (0.00%)
Transaction Info	Block #23664713/Trx 4e2c18bf2af2c4d935a2ba03af6336ff7a21b006

View Raw JSON Data

{
  "trx_id": "4e2c18bf2af2c4d935a2ba03af6336ff7a21b006",
  "block": 23664713,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T16:22:00",
  "op": [
    "vote",
    {
      "voter": "ammonite",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 0
    }
  ]
}

scottisatthepoolupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 15:05:48 UTC

23,663,189|d788179

voter	scottisatthepool
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23663189/Trx d788179af473c1d000dcebb13fffd841745deb05

View Raw JSON Data

{
  "trx_id": "d788179af473c1d000dcebb13fffd841745deb05",
  "block": 23663189,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T15:05:48",
  "op": [
    "vote",
    {
      "voter": "scottisatthepool",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

h3o2honeycombupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 13:58:03 UTC

23,661,834|2a6ba66

voter	h3o2honeycomb
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23661834/Trx 2a6ba66da03d7f91afc9a02393e0e8dfb4212625

View Raw JSON Data

{
  "trx_id": "2a6ba66da03d7f91afc9a02393e0e8dfb4212625",
  "block": 23661834,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T13:58:03",
  "op": [
    "vote",
    {
      "voter": "h3o2honeycomb",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

sublimatereplied to @eos.store / re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180626t120759278z

2018/06/26 12:08:12 UTC

23,659,637|6113f49

parent author	eos.store
parent permlink	statement-of-updating-the-blacklist-from-ecaf
author	sublimate
permlink	re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180626t120759278z
title
body	> The information of these frozen accounts did not appear in following channels: >>3. Zoom video meeting on June 21st <br> Hi, i would like to ask the following: * Who from @eos.store was on the meetings? and * How come eos.store and gen mining did not updated the blacklist while the others 19 did? (missing channels?) <hr> PD: Concerns that only requires 1 Bp to push a trx, was not about `2/3+1` ? or i am missing the point here?
json metadata	{"tags":["statement"],"users":["eos.store"],"app":"steemit/0.1"}
Transaction Info	Block #23659637/Trx 6113f490d7904702d9469200c1b3a39d3ddd23ea

View Raw JSON Data

{
  "trx_id": "6113f490d7904702d9469200c1b3a39d3ddd23ea",
  "block": 23659637,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T12:08:12",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "author": "sublimate",
      "permlink": "re-eosstore-statement-of-updating-the-blacklist-from-ecaf-20180626t120759278z",
      "title": "",
      "body": "> The information of these frozen accounts did not appear in following channels: \n\n>>3. Zoom video meeting on June 21st\n\n\n\n<br>\nHi, i would like to ask the following:\n\n* *Who from @eos.store was on the meetings?* \n\n  and\n\n* *How come eos.store and gen mining did not updated the blacklist while the others 19 did?* (missing channels?) \n<hr>\n\n**PD:** **C**oncerns that only requires **1** Bp to push a trx, was not about `2/3+1` ? or i am missing the point here?",
      "json_metadata": "{\"tags\":[\"statement\"],\"users\":[\"eos.store\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

tsamainvestupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 11:31:42 UTC

23,658,907|c159de5

voter	tsamainvest
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23658907/Trx c159de5375f653ff3cd1a56bec8a1181d3611c0e

View Raw JSON Data

{
  "trx_id": "c159de5375f653ff3cd1a56bec8a1181d3611c0e",
  "block": 23658907,
  "trx_in_block": 47,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T11:31:42",
  "op": [
    "vote",
    {
      "voter": "tsamainvest",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

ammoniteupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 11:29:27 UTC

23,658,862|224b434

voter	ammonite
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23658862/Trx 224b43481e2e20ff377dc552ecb61509a5924d05

View Raw JSON Data

{
  "trx_id": "224b43481e2e20ff377dc552ecb61509a5924d05",
  "block": 23658862,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T11:29:27",
  "op": [
    "vote",
    {
      "voter": "ammonite",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

mrlemmer11upvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:52:09 UTC

23,656,916|318b328

voter	mrlemmer11
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23656916/Trx 318b328b5bbf2120d00949d17558981a912614a1

View Raw JSON Data

{
  "trx_id": "318b328b5bbf2120d00949d17558981a912614a1",
  "block": 23656916,
  "trx_in_block": 36,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:52:09",
  "op": [
    "vote",
    {
      "voter": "mrlemmer11",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

yogevmupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:33:18 UTC

23,656,539|111bdb0

voter	yogevm
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23656539/Trx 111bdb0513aaf6779c04d15720449c0913df2276

View Raw JSON Data

{
  "trx_id": "111bdb0513aaf6779c04d15720449c0913df2276",
  "block": 23656539,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:33:18",
  "op": [
    "vote",
    {
      "voter": "yogevm",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:20:21 UTC

23,656,280|a8d4b03

parent author
parent permlink	statement
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
title	Statement of Updating the Blacklist from ECAF
body	@@ -451,22 +451,20 @@ %3Cbr%3E -%0AThe Community +%3C/p%3E%0A%3Cp%3EECAF has @@ -493,13 +493,16 @@ ts, -while +however, the @@ -570,22 +570,11 @@ ting -, and non of a + no for @@ -611,16 +611,17 @@ e found. + The comm @@ -784,12 +784,12 @@ ls: -a. t +1. T hree @@ -872,12 +872,12 @@ e.; -b. g +2. G ithu @@ -906,17 +906,17 @@ st did; -c +3 . Zoom v @@ -954,12 +954,11 @@ in -k +K ey - base @@ -1123,22 +1123,16 @@ in time. -  %3C/p%3E%0A%3Cp%3E
json metadata	{"tags":["statement","blacklist"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #23656280/Trx a8d4b0368225d68cc45765acad6f70d2f80ee7f5

View Raw JSON Data

{
  "trx_id": "a8d4b0368225d68cc45765acad6f70d2f80ee7f5",
  "block": 23656280,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:20:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "title": "Statement of Updating the Blacklist from ECAF",
      "body": "@@ -451,22 +451,20 @@\n %3Cbr%3E\n-%0AThe Community\n+%3C/p%3E%0A%3Cp%3EECAF\n  has\n@@ -493,13 +493,16 @@\n ts, \n-while\n+however,\n  the\n@@ -570,22 +570,11 @@\n ting\n-, and non of a\n+ no\n  for\n@@ -611,16 +611,17 @@\n e found.\n+ \n The comm\n@@ -784,12 +784,12 @@\n ls: \n-a. t\n+1. T\n hree\n@@ -872,12 +872,12 @@\n e.; \n-b. g\n+2. G\n ithu\n@@ -906,17 +906,17 @@\n st did; \n-c\n+3\n . Zoom v\n@@ -954,12 +954,11 @@\n  in \n-k\n+K\n ey\n- \n base\n@@ -1123,22 +1123,16 @@\n in time.\n-&nbsp;\n %3C/p%3E%0A%3Cp%3E\n",
      "json_metadata": "{\"tags\":[\"statement\",\"blacklist\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

mjhombupvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:11:21 UTC

23,656,100|93b83ae

voter	mjhomb
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23656100/Trx 93b83ae63db0188ee3c4b1e0f6da64dacc85e526

View Raw JSON Data

{
  "trx_id": "93b83ae63db0188ee3c4b1e0f6da64dacc85e526",
  "block": 23656100,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:11:21",
  "op": [
    "vote",
    {
      "voter": "mjhomb",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

cryptosupvoted (10.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:10:24 UTC

23,656,081|6957128

voter	cryptos
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	1000 (10.00%)
Transaction Info	Block #23656081/Trx 69571284029443e3932fc24ce9cdcf332b47edb6

View Raw JSON Data

{
  "trx_id": "69571284029443e3932fc24ce9cdcf332b47edb6",
  "block": 23656081,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:10:24",
  "op": [
    "vote",
    {
      "voter": "cryptos",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 1000
    }
  ]
}

indend007upvoted (100.00%) @eos.store / statement-of-updating-the-blacklist-from-ecaf

2018/06/26 09:08:39 UTC

23,656,046|6f898f7

voter	indend007
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
weight	10000 (100.00%)
Transaction Info	Block #23656046/Trx 6f898f7cc9404da188a36d79f8a35492bda13aa5

View Raw JSON Data

{
  "trx_id": "6f898f7cc9404da188a36d79f8a35492bda13aa5",
  "block": 23656046,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T09:08:39",
  "op": [
    "vote",
    {
      "voter": "indend007",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: statement-of-updating-the-blacklist-from-ecaf

2018/06/26 08:51:21 UTC

23,655,700|7c2a6a9

parent author
parent permlink	statement
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
title	Statement of Updating the Blacklist from ECAF
body	@@ -1095,19 +1095,19 @@ ays, we -has +did not upd
json metadata	{"tags":["statement","blacklist"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #23655700/Trx 7c2a6a96bdaef700b896210183c2b9330621e163

View Raw JSON Data

{
  "trx_id": "7c2a6a96bdaef700b896210183c2b9330621e163",
  "block": 23655700,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T08:51:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "title": "Statement of Updating the Blacklist from ECAF",
      "body": "@@ -1095,19 +1095,19 @@\n ays, we \n-has\n+did\n  not upd\n",
      "json_metadata": "{\"tags\":[\"statement\",\"blacklist\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storepublished a new post: statement-of-updating-the-blacklist-from-ecaf

2018/06/26 08:50:42 UTC

23,655,687|056f198

parent author
parent permlink	statement
author	eos.store
permlink	statement-of-updating-the-blacklist-from-ecaf
title	Statement of Updating the Blacklist from ECAF
body	<html> <p>June 26th, 9:55 (Beijing Time) , some voices and discussions about “EosStore updating of the blacklist from ECAF” appeared in Telegram channel EOS Gov. Unfortunately, 3570 EOS had been transferred out from a account(ID:guzdonzugmge). As a block producer, we pay highly and close attention to it and feel regretful for the loss of EOS in these accounts.  </p> <p><br> In view of this, EosStore hereby makes this statement: </p> <p><br> The Community has provided two blacklists, while the second blacklist was not discussed in the community Zoom meeting, and non of a formal announcement of it could be found.The communication system of ECAF is not perfect for ECAF itself is at preliminary stage. The information of these frozen accounts did not appear in following channels: a. three Telegram channels: EOSIO Gov, EOS Validation(EMLG) and EOS BP Infrastructure.; b. github as the first blacklist did; c. Zoom video meeting on June 21st. Only in key base and EOS 911 could you find this information. Plus current massive fake news, like a fake ECAF arbitration order these days, we has not updated the blacklist in time. </p> <p><br> As a block producer devoted to the fair benefits of all token holders, that any loss brought by this inaction is the last thing we want to see. If the Community and other BPs reach a consensus that we need to be responsible for the loss of 3570 EOS, we will absolutely compensate for these accounts to protect the property of related token holders. </p> <p><br> As ECAF has no official channel to publish its announcement currently, in order not to make this kind of thing happen again, EosStore now sends an invitation to all BPs to co-develop a software providing publishing platform for ECAF arbitration orders. Hope BPs join us to make sure the voice of ECAF be executed duly and consistently.</p> <p><br></p> <p>EosStore</p> <p>June 26th 2018</p> </html>
json metadata	{"tags":["statement","blacklist"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #23655687/Trx 056f1985d4eeb82c03f3d04c8c8e1fed62ab2b61

View Raw JSON Data

{
  "trx_id": "056f1985d4eeb82c03f3d04c8c8e1fed62ab2b61",
  "block": 23655687,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-26T08:50:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "statement-of-updating-the-blacklist-from-ecaf",
      "title": "Statement of Updating the Blacklist from ECAF",
      "body": "<html>\n<p>June 26th, 9:55 (Beijing Time) , some voices and discussions about “EosStore updating of the blacklist from ECAF” appeared in Telegram channel EOS Gov. Unfortunately, 3570 EOS had been transferred out from a account(ID:guzdonzugmge). As a block producer, we pay highly and close attention to it and feel regretful for the loss of EOS in these accounts. &nbsp;</p>\n<p><br>\nIn view of this, EosStore hereby makes this statement:&nbsp;</p>\n<p><br>\nThe Community has provided two blacklists, while the second blacklist was not discussed in the community Zoom meeting, and non of a formal announcement of it could be found.The communication system of ECAF is not perfect for ECAF itself is at preliminary stage. The information of these frozen accounts did not appear in following channels: a. three Telegram channels: EOSIO Gov, EOS Validation(EMLG) and EOS BP Infrastructure.; b. github as the first blacklist did; c. Zoom video meeting on June 21st. Only in key base and EOS 911 could you find this information. Plus current massive fake news, like a fake ECAF arbitration order these days, we has not updated the blacklist in time.&nbsp;</p>\n<p><br>\nAs a block producer devoted to the fair benefits of all token holders, that any loss brought by this inaction is the last thing we want to see. If the Community and other BPs reach a consensus that we need to be responsible for the loss of 3570 EOS, we will absolutely compensate for these accounts to protect the property of related token holders.&nbsp;</p>\n<p><br>\nAs ECAF has no official channel to publish its announcement currently, in order not to make this kind of thing happen again, EosStore now sends an invitation to all BPs to co-develop a software providing publishing platform for ECAF arbitration orders. Hope BPs join us to make sure the voice of ECAF be executed duly and consistently.</p>\n<p><br></p>\n<p>EosStore</p>\n<p>June 26th 2018</p>\n</html>",
      "json_metadata": "{\"tags\":[\"statement\",\"blacklist\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

blocktheoryupvoted (100.00%) @eos.store / 2018-6-24-eos-information-weekly-or-eosstore

2018/06/25 21:18:42 UTC

23,641,850|d18a853

voter	blocktheory
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23641850/Trx d18a8535f3301cca48794d36bff8e31add648a65

View Raw JSON Data

{
  "trx_id": "d18a8535f3301cca48794d36bff8e31add648a65",
  "block": 23641850,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T21:18:42",
  "op": [
    "vote",
    {
      "voter": "blocktheory",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

tstoupvoted (100.00%) @eos.store / 2018-6-24-eos-information-weekly-or-eosstore

2018/06/24 12:32:36 UTC

23,602,540|4fcc1f3

voter	tsto
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
weight	10000 (100.00%)
Transaction Info	Block #23602540/Trx 4fcc1f3c2bd7737d1196afc42977a6c3bc6a6e0f

View Raw JSON Data

{
  "trx_id": "4fcc1f3c2bd7737d1196afc42977a6c3bc6a6e0f",
  "block": 23602540,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T12:32:36",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: 2018-6-24-eos-information-weekly-or-eosstore

2018/06/24 09:57:27 UTC

23,599,437|4a009fe

parent author
parent permlink	eosstore
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
title	[2018.6.24 Eos information weekly] \| EosStore
body	@@ -1152,16 +1152,17 @@ mToken%0A%0A +%0A 6. Versi
json metadata	{"tags":["eosstore","weekly","information","eos"],"links":["https://t.me/StoreEos","https://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store"],"app":"steemit/0.1","format":"markdown"}
Transaction Info	Block #23599437/Trx 4a009fec6d3e5768d81941fef1e4fad3d89bbb4d

View Raw JSON Data

{
  "trx_id": "4a009fec6d3e5768d81941fef1e4fad3d89bbb4d",
  "block": 23599437,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T09:57:27",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eosstore",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "title": "[2018.6.24 Eos information weekly] | EosStore",
      "body": "@@ -1152,16 +1152,17 @@\n mToken%0A%0A\n+%0A\n 6. Versi\n",
      "json_metadata": "{\"tags\":[\"eosstore\",\"weekly\",\"information\",\"eos\"],\"links\":[\"https://t.me/StoreEos\",\"https://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

eos.storepublished a new post: 2018-6-24-eos-information-weekly-or-eosstore

2018/06/24 09:57:09 UTC

23,599,431|d14064b

parent author
parent permlink	eosstore
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
title	[2018.6.24 Eos information weekly] \| EosStore
body	@@ -982,16 +982,20 @@ ducers.%0A +%0A5. The EosS @@ -1070,60 +1070,8 @@ st%0A%0A -5. How to vote through the fire coin mine pool App%0A%0A *
json metadata	{"tags":["eosstore","weekly","information","eos"],"links":["https://t.me/StoreEos","https://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store"],"app":"steemit/0.1","format":"markdown"}
Transaction Info	Block #23599431/Trx d14064bc3cbce4d151758ce8d73c533265e3499e

View Raw JSON Data

{
  "trx_id": "d14064bc3cbce4d151758ce8d73c533265e3499e",
  "block": 23599431,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T09:57:09",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eosstore",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "title": "[2018.6.24 Eos information weekly] | EosStore",
      "body": "@@ -982,16 +982,20 @@\n ducers.%0A\n+%0A5. \n The EosS\n@@ -1070,60 +1070,8 @@\n st%0A%0A\n-5. How to vote through the fire coin mine pool App%0A%0A\n    *\n",
      "json_metadata": "{\"tags\":[\"eosstore\",\"weekly\",\"information\",\"eos\"],\"links\":[\"https://t.me/StoreEos\",\"https://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

ubgupvoted (1.00%) @eos.store / 2018-6-24-eos-information-weekly-or-eosstore

2018/06/24 09:50:00 UTC

23,599,288|3996b0e

voter	ubg
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
weight	100 (1.00%)
Transaction Info	Block #23599288/Trx 3996b0e295ebf9d463d68481db88d45366080747

View Raw JSON Data

{
  "trx_id": "3996b0e295ebf9d463d68481db88d45366080747",
  "block": 23599288,
  "trx_in_block": 65,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T09:50:00",
  "op": [
    "vote",
    {
      "voter": "ubg",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "weight": 100
    }
  ]
}

a-a-areplied to @eos.store / re-eosstore-2018-6-24-eos-information-weekly-or-eosstore-20180624t094937231z

2018/06/24 09:49:39 UTC

23,599,281|81831b9

parent author	eos.store
parent permlink	2018-6-24-eos-information-weekly-or-eosstore
author	a-a-a
permlink	re-eosstore-2018-6-24-eos-information-weekly-or-eosstore-20180624t094937231z
title
body	# Go to @bible.com
json metadata	{"tags":["eosstore"],"users":["bible.com"],"app":"steemit/0.1"}
Transaction Info	Block #23599281/Trx 81831b92190da3d0fc826e490de32e99d361489e

View Raw JSON Data

{
  "trx_id": "81831b92190da3d0fc826e490de32e99d361489e",
  "block": 23599281,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T09:49:39",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "author": "a-a-a",
      "permlink": "re-eosstore-2018-6-24-eos-information-weekly-or-eosstore-20180624t094937231z",
      "title": "",
      "body": "# Go to @bible.com",
      "json_metadata": "{\"tags\":[\"eosstore\"],\"users\":[\"bible.com\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

eos.storepublished a new post: 2018-6-24-eos-information-weekly-or-eosstore

2018/06/24 09:49:00 UTC

23,599,268|bb4ac7a

parent author
parent permlink	eosstore
author	eos.store
permlink	2018-6-24-eos-information-weekly-or-eosstore
title	[2018.6.24 Eos information weekly] \| EosStore
body	Hi, EOSers, Recently, EosStore is giving full support for DApp mainly by organizing weekly technology salons and technical trainings, and by launching development kit. We welcome developers with good projects to communicate with us. EosStore Weekly Report is as follows: 1. Attending global BP Zoom meetings on time everyday (It was laborious to follow these meetings until late night) . Major discussions of global BP Zoom meetings this week were as follows: 1）System Contract Upgrade 1）System Contract Upgrade 2）Action Plan proposal 3）Block Producer Traditions proposal 4）Call Schedule - Recording & Release 5）Unregistered Tokens 6）Referendum Smart Contract Update 7）ECAF Funding 2. Involving in recommending and reviewing of ECAF arbitration candidates. 3. Participating in the meeting to establish the EOS-related fund, strongly supporting the EOSPioneer fund technically and financially. 4. By June 24th 14:52,2018, eosstorebest is ranked at 18th among 21 block producers. The EosStore has compiled some voting tools, as follows. Vote for eosstorebest 5. How to vote through the fire coin mine pool App * How to vote in huobipool * How to vote in Pomelo * How to vote in imToken 6. Version 1.1 of EosStore website has been partially developed and now in its testing phase. More DApp has been listed. New functions are waiting for you to experience. 7. The Technology Salon of EosStore is scheduled to hold next week. Welcome more developers join the activity and follow our WeChat official account to know more about it. Have a good day :) EosStore ｜ Get your commercial DApp ideas off the ground. Contact us Email：[email protected] Telegram：https://t.me/StoreEos Website：https://www.eos.store Twitter：https://twitter.com/StoreEos Github：https://github.com/eosstore Steemit：https://steemit.com/@eos.store
json metadata	{"tags":["eosstore","weekly","information","eos"],"links":["https://t.me/StoreEos","https://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store"],"app":"steemit/0.1","format":"markdown"}
Transaction Info	Block #23599268/Trx bb4ac7a21ba73028b04817a2c075e7e7ab60f3c8

View Raw JSON Data

{
  "trx_id": "bb4ac7a21ba73028b04817a2c075e7e7ab60f3c8",
  "block": 23599268,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-24T09:49:00",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eosstore",
      "author": "eos.store",
      "permlink": "2018-6-24-eos-information-weekly-or-eosstore",
      "title": "[2018.6.24 Eos information weekly] | EosStore",
      "body": "Hi, EOSers,\n\nRecently, EosStore is giving full support for DApp mainly by organizing weekly technology salons and technical trainings, and by launching development kit.  We welcome developers with good projects to communicate with us.\n\nEosStore Weekly Report is as follows:\n\n1. Attending global BP Zoom meetings on time everyday (It was laborious to follow these meetings until late night) . Major discussions of global BP Zoom meetings this week were as follows:\n\n1）System Contract Upgrade\n1）System Contract Upgrade\n2）Action Plan proposal\n3）Block Producer Traditions proposal\n4）Call Schedule - Recording & Release \n5）Unregistered Tokens\n6）Referendum Smart Contract Update\n7）ECAF Funding\n\n2. Involving in recommending and reviewing of ECAF arbitration candidates. \n\n3. Participating in the meeting to establish the EOS-related fund, strongly supporting the EOSPioneer fund technically and financially.\n\n4. By June 24th 14:52,2018,  eosstorebest is ranked at 18th among 21 block producers.\nThe EosStore has compiled some voting tools, as follows. Vote for eosstorebest\n\n5. How to vote through the fire coin mine pool App\n\n   * How to vote in huobipool\n   * How to vote in Pomelo\n   * How to vote in imToken\n\n6. Version 1.1 of EosStore website has been partially developed and now in its testing phase. More DApp has been listed. New functions are waiting for you to experience.\n\n7. The Technology Salon of EosStore is scheduled to hold next week. Welcome more developers join the activity and follow our WeChat official account to know more about it.\n\nHave a good day :)\n\n\n\nEosStore ｜ Get your commercial DApp ideas off the ground.\n\n\nContact us\n\nEmail：[email protected]\nTelegram：https://t.me/StoreEos\nWebsite：https://www.eos.store \nTwitter：https://twitter.com/StoreEos \nGithub：https://github.com/eosstore \nSteemit：https://steemit.com/@eos.store",
      "json_metadata": "{\"tags\":[\"eosstore\",\"weekly\",\"information\",\"eos\"],\"links\":[\"https://t.me/StoreEos\",\"https://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

blocktheoryupvoted (100.00%) @eos.store / a-statement-from-the-eos-mainnet-launch-group

2018/06/14 00:49:48 UTC

23,300,568|a9bded6

voter	blocktheory
author	eos.store
permlink	a-statement-from-the-eos-mainnet-launch-group
weight	10000 (100.00%)
Transaction Info	Block #23300568/Trx a9bded61f363575afee3c0e4a2b005561e45337b

View Raw JSON Data

{
  "trx_id": "a9bded61f363575afee3c0e4a2b005561e45337b",
  "block": 23300568,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-14T00:49:48",
  "op": [
    "vote",
    {
      "voter": "blocktheory",
      "author": "eos.store",
      "permlink": "a-statement-from-the-eos-mainnet-launch-group",
      "weight": 10000
    }
  ]
}

tstoupvoted (100.00%) @eos.store / a-statement-from-the-eos-mainnet-launch-group

2018/06/01 10:26:45 UTC

22,938,384|d82a3d2

voter	tsto
author	eos.store
permlink	a-statement-from-the-eos-mainnet-launch-group
weight	10000 (100.00%)
Transaction Info	Block #22938384/Trx d82a3d2a04c76c54bb9c3ab954da23c11c82976f

View Raw JSON Data

{
  "trx_id": "d82a3d2a04c76c54bb9c3ab954da23c11c82976f",
  "block": 22938384,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-01T10:26:45",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "a-statement-from-the-eos-mainnet-launch-group",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: a-statement-from-the-eos-mainnet-launch-group

2018/06/01 05:35:51 UTC

22,932,569|0b4e808

parent author
parent permlink	statement
author	eos.store
permlink	a-statement-from-the-eos-mainnet-launch-group
title	A STATEMENT FROM THE EOS MAINNET LAUNCH GROUP
body	<html> <p><img src="https://cdn.steemitimages.com/0x0/https://cdn.steemitimages.com/DQmY8j5dzQxAKmd2oUxT6skq6uyVkHhZZ82j7u9R99uPBpj/Header.png" width="2000" height="1094"/></p> <p>One Mainnet Called EOS.</p> <p>On May 25th, 2018 the EOS Mainnet Launch Group (EMLG) united under the promise of delivering one mainnet which will be called EOS. In an effort to be as transparent to the community as possible we offer our plan for the launch.</p> <h2>The Token Freeze</h2> <p>The ERC-20 EOS token distribution will end on June 1st at 22:59:59 UTC. Per the EOS crowdsale Ethereum smart contract, the ERC-20 tokens will be frozen 23 hours after the end of the token distribution. Once the freeze is completed we will begin the Phases of Launch process. If you have not done so, please be sure <a href="https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew">to generate your EOS keypair and map them to the ETH address which holds your EOS ERC-20 tokens.</a></p> <h2>Be Smart. Be Vigilant</h2> <p>The ecosystem will be wrought with scams during this time. <strong>Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so.</strong> Ignoring this warning could result in tokens lost. Please visit <a href="https://bp.eosgo.io/">https://bp.eosgo.io/</a> to learn more about block producer candidates.</p> <h1>Overview: Phases of Launch</h1> <p><em>There are no times associated with each phase because ensuring each phase is completed successfully is more important than each being completed quickly. The launch process may take days to complete.</em></p> <ul> <li><strong>Verify Snapshot & Boot</strong>: Snapshot taken and verified by EMLG and third parties. Boot process initiated.</li> <li><strong>Testing</strong>: Allow time for EMLG and third parties to verify that the tokens have been loaded according to the snapshot file, and that the software performs well.</li> <li><strong>Enable</strong>: Release joint statement from Block Producer community that it is safe to import private keys and vote. Voting beings.</li> <li><strong>Activation</strong> - Declare the EOS Mainnet active.<br> <strong>Only after all 4 phases are complete do we have an irreversible blockchain. Until then rollback and restart of the chain is possible. This essential technical due diligence, including validation testing, could take days to complete.</strong></li> </ul> <h1>Phases in Detail</h1> <h4>Verify Snapshot & Boot</h4> <p>The EMLG will use the official snapshot tool to produce a final snapshot of the frozen ERC-20 EOS tokens. The community is encouraged to use the same tools to produce their own copies of the snapshot and verify that it matches the EMLG’s copy exactly. Once the snapshot has been verified, Appointed Block Producers will be established within the launch group. These Appointed Block Producers are temporary and only exist to ensure that the network is booted correctly and stable throughout the verification and voting process. No block rewards are awarded at this time.</p> <h4>Testing</h4> <p>Once Appointed Block Producers have completed the boot process and ensured that the token balances are correct the network will be opened for third party verification. Anyone who wishes to verify the network at this stage may do so, and tools will be released by the community to help facilitate this verification.<br> The EMLG will clone the network at this stage and conduct their own in-depth acceptance testing as well. This stage will continue for a 48-hour period to allow for the completion of these tests. If a major bug is found which requires code changes then the 48-hour window will be reset to allow for ample time to test these new changes. The decision to reset the 48-hour window will be at the sole discretion of the EMLG.<br> <strong>Transactions or votes staked during this period are not safe and can be undone or lost.</strong></p> <h4>Enable</h4> <p>At this stage a statement will be released by the EMLG and the network will be opened to the general token-holder community. For an EOSIO chain to be considered enabled, 15% of all tokens-holders must use their private keys and stake votes for at least one Block Producer. The length of this phase will be as long as it takes for the token-holder community to act. <em>So get out there and vote!</em> Many block producers have developed tutorials on how to vote. A community voting portal has been developed and you can follow updates on its construction on Twitter <a href="https://twitter.com/eosportal">@eosportal</a>. As stated above, <strong>Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so.</strong></p> <h4>Activation</h4> <p>Once 15% of tokens are staked and used to vote the chain is considered valid and normal functions are activated. All Appointed Block Producers will be immediately replaced by the Elected Block Producers that have been voted in by the community.</p> <h2>Next Steps</h2> <p>In the next joint statement we will release the details of the “Verify” period and the tools used to facilitate third party verification of both the software and the token balances.</p> <h2>Onward to Launch</h2> <p>The EOS mainnet is the first step toward a new generation of blockchain technology that will fundamentally affect how we interact with one another. We look forward to sharing this experience with you, the token holder. Thank you for your support.<br> <strong>The EOS Mainnet Launch Group</strong> <a href="https://steemit.com/trending/eoslaunch">#EOSLaunch</a></p> <h1>EOS 메인넷 런치: 이벤트의 순서</h1> <h2>EOS라 불리는 하나의 메인넷</h2> <p>5월 25일, 2018 EOS 메인넷 런치 그룹(EMLG)은 EOS라고 불릴 하나의 메인넷을 런칭하자는 일념하에 결성되었습니다. 커뮤니티에 가능한 한 투명하게 모든 것을 진행하고자 런치 계획을 공개합니다.</p> <h2>토큰 Freeze</h2> <p>ERC-20 EOS토큰 분배는 6월 1일 22:59:59 UTC에 끝날 것입니다. 이더리움 스마트 컨트랙트 위의 EOS Crowdsale 당 ERC-20 토큰은 토큰 분배 후 23시간동안 얼어있을 것입니다. Freeze가 끝나면 런치 프로세스를 시작할 것입니다. 만약 아직 하지 않았다면, <a href="https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew">EOS 키페어를 만들고 ERC-20을 들고있는 이더리움 주소에 맵핑해두기</a>를 명심하세요.</p> <h2>똑똑하고, 재빠르게</h2> <p>생태계는 온갖 사기 행각으로 가득할 것입니다. <strong>본인의 프라이빗 키를 절대 본인이 신뢰하는 최소한 5개의 블록 프로듀서들의 공동 성명이 발표되기 전에 공개하지 마세요.</strong> 이 경고를 무시한다면 토큰을 잃게 될 수 있습니다. <a href="http://koreos.io/">http://koreos.io</a> 에 방문하여 블록 프로듀서 후보들에 대해 알 수 있습니다.</p> <h1>개요: 런치의 단계</h1> <p><em>각 단계별로 시간을 정해두진 않았는데, 그 이유는 각 단계가 성공적으로 끝나는 것이 빠르게 끝나는 것 보다 중요하기 때문입니다. 런치 프로세스는 완성까지 몇 일이 소요될 수 있습니다.</em></p> <ul> <li><strong>스냅샷 입증 & 부트</strong>: 스냅샷은 EMLG와 제 3 그룹에 의해 기록되고 입증될 것입니다. 부트 과정이 시작됩니다.</li> <li><strong>테스팅</strong>: EMLG와 제 3 그룹은 스냅샷 파일에 따라 로드된 토큰을 확인하고 소프트웨어가 잘 작동하는지 테스트할 시간을 가지게 됩니다.</li> <li><strong>시작</strong>: 블록 프로듀서 커뮤니티는 프라이빗 키를 가져와서 투표를 해도 안전하다는 합동 성명서를 내게 됩니다. 투표가 시작됩니다.</li> <li><strong>활성화</strong> - EOS 메인넷 활성화를 공표합니다.<br> <strong>4 단계가 완료된 이후에만 비가역 블록체인을 볼 수 있습니다. 롤백과 체인의 재시작이 가능해집니다. 이 핵심적인 기술적 실사(due diligence)는 검증 테스팅(validation testing)을 포함하는데, 몇 시간이 걸린다기 보다 몇 일이 걸릴 수 있습니다.</strong></li> </ul> <h1>각 단계의 자세한 설명</h1> <h4>스냅샷 검증(Verify) & 부트</h4> <p>EMLG는 공식적인 스냅샷 툴을 이용하여 최종적인 (frozen) ERC-20 EOS 토큰 스냅샷을 생성합니다. 커뮤니티는 같은 툴을 활용해서 스냅샷 복사본을 만들어 그것이 EMLG의 복사본과 정확히 일치하는지 검증하는 과정을 거치기를 권고합니다. 스냅샷이 검증되면, 임시* 블록 프로듀서(ABP; Appointed Block Producer)들은 런치 그룹 내에서 설정될 것입니다. 이 ABP들은 일시적이며 네트워크가 잘 부팅되었는고 검증과 투표 과정에서 안정적인지를 확실히 하기 위해 존재합니다. 이 때에는 블록 보상이 주어지지 않습니다.</p> <h4>테스팅</h4> <p>임시 블록 프로듀서가 부트 과정을 완료하고 토큰 밸런스가 맞으면 네트워크는 제 3 그룹의 검증(verification)을 위해 열릴 것입니다. 이 스테이지에서 네트워크를 검증하고자 하는 그 어느 누구든 해볼 수 있고, 이 검증 과정을 도울 수 있도록 커뮤니티가 툴을 배포할 것입니다.<br> EMLG는 이 단계에서 네트워크를 복제(clone)하고 면밀하게 그들 각각의 승인 테스팅(acceptance testing)도 진행합니다. 이 스테이지는 테스팅이 완료될 수 있도록 48시간 동안 계속 될 것입니다. 코드 변경이 필요한 주요 버그가 발견되면, 48시간의 기간이 리셋되어 이 새로운 변화들을 테스팅할 수 있도록 충분한 시간을 들일 것입니다. 48시간 리셋은 EMLG만의 재량으로 의해 결정될 것입니다.<br> <strong>이 기간동안 이루어진 거래나 투표는 안전하지 않으며 끝나지 않거나 유실될 수 있습니다.</strong></p> <h4>Enable</h4> <p>이 스테이지에서는 EMLG에 의해 성명서가 발표되고 네트워크는 일반 토큰홀더 커뮤니티에게 열릴 것입니다. EOSIO 체인이 개시되기(enabled) 위해서는, 모든 토큰 홀더의 15%가 그들의 프라이빗 키를 사용하고 최소한 하나의 블록 프로듀서에 투표해야 합니다. 이 단계는 토큰홀더 커뮤니티가 활동할 수 있는 만큼의 충분한 기간동안 진행됩니다. <em>나가서 투표합시다!</em> 많은 블록 프로듀서들은 어떻게 투표해야 하는지에 대한 튜토리얼을 제공해 왔습니다. 커뮤니티 보팅 포탈이 개발되었고 여러분은 트위터로 업데이트를 확인할 수 있습니다 <a href="https://twitter.com/eosportal">@eosportal</a>. 위에 언급했듯, <strong>본인의 프라이빗 키를 절대 본인이 신뢰하는 최소한 5개의 블록 프로듀서들의 공동 성명이 발표되기 전에 공개하지 마세요.</strong></p> <h4>활성화(Activation)</h4> <p>15%의 토큰이 스테이크되고 투표에 쓰이면 체인은 유효하다고 판단되며, 정상 기능들이 활성화됩니다. 모든 임시 블록 프로듀서(Appointed Block Producer)들은 커뮤니티에 의해 선출된 블록 프로듀서(Elected Block Producer)로 대체됩니다.</p> <h2>다음 단계</h2> <p>이 다음 공동 성명은 “검증(Verify)” 기간의 상세 내용을 배포하고, 제 3 그룹이 소프트웨어와 토큰 잔고를 검증하는데 사용할 툴(tool)을 배포할 것입니다.</p> <h2>런치를 위한 전진</h2> <p>EOS 메인넷은 우리가 서로와 상호작용하는 방법을 근본적으로 바꿀 새로운 세대의 블록체인 기술에 한발짝 더 나아갑니다. 우리는 이 경험을 토큰 홀더인 여러분과 함께 하기를 기대합니다. 응원해 주셔서 감사합니다.<br> <strong>EOS 메인넷 런치 그룹</strong> <a href="https://steemit.com/trending/eoslaunch">#EOSLaunch</a></p> <h1>只有一条名为 EOS 的主网</h1> <p>2018年5月25日，EOS主网启动团队(EMLG) 达成共识，承诺只会承认一条名为 EOS 的主网。我们致力于确保社区尽可能公开透明，基于此，我们提供了自己的主网启动方案。</p> <h2>代币冻结</h2> <p>ERC-20 格式的 EOS 代币将会于 UTC 时间（世界标准时间）6月1日 22:59:59结束(北京时间6月2日06:59:59)，根据 EOS 的众筹智能合约设定，ERC-20 代币会在代币发布结束23个小时后冻结。冻结完成后，我们会开始主网启动的流程，请确保你的EOS已经做过了映射。如果你没有映射，请确保生成你的密钥对，并将它们映射到持有你的 ERC - 20 格式的 EOS 代币的以太坊地址。</p> <h2>保持机灵，保持警惕</h2> <p>这段时间内，我们预计将会有很多诈骗分子出现。请不要在任何地方导入你的私钥，除非看到你信任的至少5个节点发布联合声明可以安全导入。若忽略此警告可能导致代币丢失。请访问 IMEOS解更多关于节点候选者的信息。</p> <h1>概述：主网启动阶段</h1> <p>每个阶段都没有时间要求，因为比起每个阶段快速完成，确保每个阶段都成功完成更加重要。启动过程可能需要几天才能完成。</p> <ul> <li><strong>检验确认快照和启动</strong>：EMLG 和第三方会进行快照和检验确认。启动程序初始化。</li> <li><strong>测试</strong>：让 EMLG 和第三方有时间检验 Token 是否已经根据快照的文件加载，并且软件运行良好。投票开始。</li> <li><strong>启用</strong>：BP社区发布联合声明：可以安全导入私钥并投票。</li> <li><strong>激活</strong> :声明 EOS 主网有效。<br> <strong>只有在这4个步骤都完成之后，我们才将拥有一个不可逆的区块链。在此之前，我们不排除回滚或重启该链的可能性。这些必要步骤，包括验证测试，将耗费大量精力，有可能将耗时数日来完成。</strong></li> </ul> <h2>启动步骤的细节信息</h2> <h4>验证快照&启动</h4> <p>主网启动团队（EMLG）将会使用官方快照工具来生成冻结ERC-20代币的最终快照文件。鼓励社区使用同一组工具来生成快照文件，并且检验它是否与主网启动团队的快照完全一致。一旦这个快照被检验确认，指定出块节点（ABPs）将会在启动团队中被指定。这些被指定的出块节点只是临时担当超级节点的职务，其存在单纯是为了保证主网能以正确的方式启动，以及保证在检验确认和投票的整个阶段是稳定的。此阶段指定节点不会获得任何出块奖励。</p> <h4>测试</h4> <p>一旦节点们完成了启动环节，并且确认代币余额正确，主网将会开放由第三方进行检验确认。我们欢迎任何个人或团体在当前环节来此对本网络进行检验，而检验所需的工具将由BP社区发布，以促成该检验确认的顺利进行。<br> EMLG将在当前环节中复制主网，并对此网络进行彻底的验收测试。本阶段将历时48小时以便这一系列测试得以完成。一旦在过程中发现重大BUG以致需要修改代码，那么这48个小时的时间窗口就将会重置，以确保我们有充裕的时间对新增的改动进行测试修复。至于过程中是否对48小时的时间窗口进行充值，将由EMLG酌情决定。<br> 在此期间发生的事务或进行的投票是不安全的，有可能会丢失或者被撤销。</p> <h4>启用</h4> <p>一旦上一阶段结束，主网将会对持币社区开放。为了激活EOSIO主链，15%的代币持有者必须导入他们的私钥并且至少向一位节点候选人投票。私钥导入和投票环节的时间长度将取决于持币者的行动效率。“为尽快启动主链，请一起来投票吧！”许多节点已经制作了关于如何进行投票的教程。目前已经开发出一个社区投票入口。您可以在<a href="https://steemit.com/@eosportal">@eosportal</a>的Twitter页面上获取投票入口架构的最新动态。再次重点强调，请不要在任何地方导入你的私钥，除非看到你信任的至少5个节点发布联合声明可以安全导入。</p> <h4>激活</h4> <p>一旦15%的代币用于投票，主链就被认为是可靠的并且常规的功能会被激活。21个指定节点会立即被21个被社区选举出来的节点所代替。</p> <h2>接下来的步骤</h2> <p>在下一份联合声明中，我们将公布“验证”期的细节以及被用于帮助第三方进行验证的工具。</p> <h2>向主网上线进发</h2> <p>EOS主网将会开创一个区块链科技的新时代，这种科技将极大地影响我们之间的交互方式。在我们努力确保主网的成功上线的同时，也希望将此经验分享给广大的持币者，感谢您的支持。<br> EOS主网启动团队 <a href="https://steemit.com/trending/eos">#EOS</a>启动</p> </html>
json metadata	{"tags":["statement"],"image":["https://cdn.steemitimages.com/0x0/https://cdn.steemitimages.com/DQmY8j5dzQxAKmd2oUxT6skq6uyVkHhZZ82j7u9R99uPBpj/Header.png"],"links":["https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew","https://bp.eosgo.io/","https://twitter.com/eosportal","https://steemit.com/trending/eoslaunch","http://koreos.io/","https://steemit.com/@eosportal","https://steemit.com/trending/eos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22932569/Trx 0b4e8084ad42037cbee4c5536664ef8254f4d821

View Raw JSON Data

{
  "trx_id": "0b4e8084ad42037cbee4c5536664ef8254f4d821",
  "block": 22932569,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-01T05:35:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "a-statement-from-the-eos-mainnet-launch-group",
      "title": "A STATEMENT FROM THE EOS MAINNET LAUNCH GROUP",
      "body": "<html>\n<p><img src=\"https://cdn.steemitimages.com/0x0/https://cdn.steemitimages.com/DQmY8j5dzQxAKmd2oUxT6skq6uyVkHhZZ82j7u9R99uPBpj/Header.png\" width=\"2000\" height=\"1094\"/></p>\n<p>One Mainnet Called EOS.</p>\n<p>On May 25th, 2018 the EOS Mainnet Launch Group (EMLG) united under the promise of delivering one mainnet which will be called EOS. In an effort to be as transparent to the community as possible we offer our plan for the launch.</p>\n<h2>The Token Freeze</h2>\n<p>The ERC-20 EOS token distribution will end on June 1st at 22:59:59 UTC. Per the EOS crowdsale Ethereum smart contract, the ERC-20 tokens will be frozen 23 hours after the end of the token distribution. Once the freeze is completed we will begin the Phases of Launch process. If you have not done so, please be sure <a href=\"https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew\">to generate your EOS keypair and map them to the ETH address which holds your EOS ERC-20 tokens.</a></p>\n<h2>Be Smart. Be Vigilant</h2>\n<p>The ecosystem will be wrought with scams during this time. <strong>Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so.</strong> Ignoring this warning could result in tokens lost. Please visit <a href=\"https://bp.eosgo.io/\">https://bp.eosgo.io/</a> to learn more about block producer candidates.</p>\n<h1>Overview: Phases of Launch</h1>\n<p><em>There are no times associated with each phase because ensuring each phase is completed successfully is more important than each being completed quickly. The launch process may take days to complete.</em></p>\n<ul>\n  <li><strong>Verify Snapshot &amp; Boot</strong>: Snapshot taken and verified by EMLG and third parties. Boot process initiated.</li>\n  <li><strong>Testing</strong>: Allow time for EMLG and third parties to verify that the tokens have been loaded according to the snapshot file, and that the software performs well.</li>\n  <li><strong>Enable</strong>: Release joint statement from Block Producer community that it is safe to import private keys and vote. Voting beings.</li>\n  <li><strong>Activation</strong> - Declare the EOS Mainnet active.<br>\n<strong>Only after all 4 phases are complete do we have an irreversible blockchain. Until then rollback and restart of the chain is possible. This essential technical due diligence, including validation testing, could take days to complete.</strong></li>\n</ul>\n<h1>Phases in Detail</h1>\n<h4>Verify Snapshot &amp; Boot</h4>\n<p>The EMLG will use the official snapshot tool to produce a final snapshot of the frozen ERC-20 EOS tokens. The community is encouraged to use the same tools to produce their own copies of the snapshot and verify that it matches the EMLG’s copy exactly. Once the snapshot has been verified, Appointed Block Producers will be established within the launch group. These Appointed Block Producers are temporary and only exist to ensure that the network is booted correctly and stable throughout the verification and voting process. No block rewards are awarded at this time.</p>\n<h4>Testing</h4>\n<p>Once Appointed Block Producers have completed the boot process and ensured that the token balances are correct the network will be opened for third party verification. Anyone who wishes to verify the network at this stage may do so, and tools will be released by the community to help facilitate this verification.<br>\nThe EMLG will clone the network at this stage and conduct their own in-depth acceptance testing as well. This stage will continue for a 48-hour period to allow for the completion of these tests. If a major bug is found which requires code changes then the 48-hour window will be reset to allow for ample time to test these new changes. The decision to reset the 48-hour window will be at the sole discretion of the EMLG.<br>\n<strong>Transactions or votes staked during this period are not safe and can be undone or lost.</strong></p>\n<h4>Enable</h4>\n<p>At this stage a statement will be released by the EMLG and the network will be opened to the general token-holder community. For an EOSIO chain to be considered enabled, 15% of all tokens-holders must use their private keys and stake votes for at least one Block Producer. The length of this phase will be as long as it takes for the token-holder community to act. <em>So get out there and vote!</em> Many block producers have developed tutorials on how to vote. A community voting portal has been developed and you can follow updates on its construction on Twitter <a href=\"https://twitter.com/eosportal\">@eosportal</a>. As stated above, <strong>Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so.</strong></p>\n<h4>Activation</h4>\n<p>Once 15% of tokens are staked and used to vote the chain is considered valid and normal functions are activated. All Appointed Block Producers will be immediately replaced by the Elected Block Producers that have been voted in by the community.</p>\n<h2>Next Steps</h2>\n<p>In the next joint statement we will release the details of the “Verify” period and the tools used to facilitate third party verification of both the software and the token balances.</p>\n<h2>Onward to Launch</h2>\n<p>The EOS mainnet is the first step toward a new generation of blockchain technology that will fundamentally affect how we interact with one another. We look forward to sharing this experience with you, the token holder. Thank you for your support.<br>\n<strong>The EOS Mainnet Launch Group</strong> <a href=\"https://steemit.com/trending/eoslaunch\">#EOSLaunch</a></p>\n<h1>EOS 메인넷 런치: 이벤트의 순서</h1>\n<h2>EOS라 불리는 하나의 메인넷</h2>\n<p>5월 25일, 2018 EOS 메인넷 런치 그룹(EMLG)은 EOS라고 불릴 하나의 메인넷을 런칭하자는 일념하에 결성되었습니다. 커뮤니티에 가능한 한 투명하게 모든 것을 진행하고자 런치 계획을 공개합니다.</p>\n<h2>토큰 Freeze</h2>\n<p>ERC-20 EOS토큰 분배는 6월 1일 22:59:59 UTC에 끝날 것입니다. 이더리움 스마트 컨트랙트 위의 EOS Crowdsale 당 ERC-20 토큰은 토큰 분배 후 23시간동안 얼어있을 것입니다. Freeze가 끝나면 런치 프로세스를 시작할 것입니다. 만약 아직 하지 않았다면, <a href=\"https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew\">EOS 키페어를 만들고 ERC-20을 들고있는 이더리움 주소에 맵핑해두기</a>를 명심하세요.</p>\n<h2>똑똑하고, 재빠르게</h2>\n<p>생태계는 온갖 사기 행각으로 가득할 것입니다. <strong>본인의 프라이빗 키를 절대 본인이 신뢰하는 최소한 5개의 블록 프로듀서들의 공동 성명이 발표되기 전에 공개하지 마세요.</strong> 이 경고를 무시한다면 토큰을 잃게 될 수 있습니다. <a href=\"http://koreos.io/\">http://koreos.io</a> 에 방문하여 블록 프로듀서 후보들에 대해 알 수 있습니다.</p>\n<h1>개요: 런치의 단계</h1>\n<p><em>각 단계별로 시간을 정해두진 않았는데, 그 이유는 각 단계가 성공적으로 끝나는 것이 빠르게 끝나는 것 보다 중요하기 때문입니다. 런치 프로세스는 완성까지 몇 일이 소요될 수 있습니다.</em></p>\n<ul>\n  <li><strong>스냅샷 입증 &amp; 부트</strong>: 스냅샷은 EMLG와 제 3 그룹에 의해 기록되고 입증될 것입니다. 부트 과정이 시작됩니다.</li>\n  <li><strong>테스팅</strong>: EMLG와 제 3 그룹은 스냅샷 파일에 따라 로드된 토큰을 확인하고 소프트웨어가 잘 작동하는지 테스트할 시간을 가지게 됩니다.</li>\n  <li><strong>시작</strong>: 블록 프로듀서 커뮤니티는 프라이빗 키를 가져와서 투표를 해도 안전하다는 합동 성명서를 내게 됩니다. 투표가 시작됩니다.</li>\n  <li><strong>활성화</strong> - EOS 메인넷 활성화를 공표합니다.<br>\n<strong>4 단계가 완료된 이후에만 비가역 블록체인을 볼 수 있습니다. 롤백과 체인의 재시작이 가능해집니다. 이 핵심적인 기술적 실사(due diligence)는 검증 테스팅(validation testing)을 포함하는데, 몇 시간이 걸린다기 보다 몇 일이 걸릴 수 있습니다.</strong></li>\n</ul>\n<h1>각 단계의 자세한 설명</h1>\n<h4>스냅샷 검증(Verify) &amp; 부트</h4>\n<p>EMLG는 공식적인 스냅샷 툴을 이용하여 최종적인 (frozen) ERC-20 EOS 토큰 스냅샷을 생성합니다. 커뮤니티는 같은 툴을 활용해서 스냅샷 복사본을 만들어 그것이 EMLG의 복사본과 정확히 일치하는지 검증하는 과정을 거치기를 권고합니다. 스냅샷이 검증되면, 임시* 블록 프로듀서(ABP; Appointed Block Producer)들은 런치 그룹 내에서 설정될 것입니다. 이 ABP들은 일시적이며 네트워크가 잘 부팅되었는고 검증과 투표 과정에서 안정적인지를 확실히 하기 위해 존재합니다. 이 때에는 블록 보상이 주어지지 않습니다.</p>\n<h4>테스팅</h4>\n<p>임시 블록 프로듀서가 부트 과정을 완료하고 토큰 밸런스가 맞으면 네트워크는 제 3 그룹의 검증(verification)을 위해 열릴 것입니다. 이 스테이지에서 네트워크를 검증하고자 하는 그 어느 누구든 해볼 수 있고, 이 검증 과정을 도울 수 있도록 커뮤니티가 툴을 배포할 것입니다.<br>\nEMLG는 이 단계에서 네트워크를 복제(clone)하고 면밀하게 그들 각각의 승인 테스팅(acceptance testing)도 진행합니다. 이 스테이지는 테스팅이 완료될 수 있도록 48시간 동안 계속 될 것입니다. 코드 변경이 필요한 주요 버그가 발견되면, 48시간의 기간이 리셋되어 이 새로운 변화들을 테스팅할 수 있도록 충분한 시간을 들일 것입니다. 48시간 리셋은 EMLG만의 재량으로 의해 결정될 것입니다.<br>\n<strong>이 기간동안 이루어진 거래나 투표는 안전하지 않으며 끝나지 않거나 유실될 수 있습니다.</strong></p>\n<h4>Enable</h4>\n<p>이 스테이지에서는 EMLG에 의해 성명서가 발표되고 네트워크는 일반 토큰홀더 커뮤니티에게 열릴 것입니다. EOSIO 체인이 개시되기(enabled) 위해서는, 모든 토큰 홀더의 15%가 그들의 프라이빗 키를 사용하고 최소한 하나의 블록 프로듀서에 투표해야 합니다. 이 단계는 토큰홀더 커뮤니티가 활동할 수 있는 만큼의 충분한 기간동안 진행됩니다. <em>나가서 투표합시다!</em> 많은 블록 프로듀서들은 어떻게 투표해야 하는지에 대한 튜토리얼을 제공해 왔습니다. 커뮤니티 보팅 포탈이 개발되었고 여러분은 트위터로 업데이트를 확인할 수 있습니다 <a href=\"https://twitter.com/eosportal\">@eosportal</a>. 위에 언급했듯, <strong>본인의 프라이빗 키를 절대 본인이 신뢰하는 최소한 5개의 블록 프로듀서들의 공동 성명이 발표되기 전에 공개하지 마세요.</strong></p>\n<h4>활성화(Activation)</h4>\n<p>15%의 토큰이 스테이크되고 투표에 쓰이면 체인은 유효하다고 판단되며, 정상 기능들이 활성화됩니다. 모든 임시 블록 프로듀서(Appointed Block Producer)들은 커뮤니티에 의해 선출된 블록 프로듀서(Elected Block Producer)로 대체됩니다.</p>\n<h2>다음 단계</h2>\n<p>이 다음 공동 성명은 “검증(Verify)” 기간의 상세 내용을 배포하고, 제 3 그룹이 소프트웨어와 토큰 잔고를 검증하는데 사용할 툴(tool)을 배포할 것입니다.</p>\n<h2>런치를 위한 전진</h2>\n<p>EOS 메인넷은 우리가 서로와 상호작용하는 방법을 근본적으로 바꿀 새로운 세대의 블록체인 기술에 한발짝 더 나아갑니다. 우리는 이 경험을 토큰 홀더인 여러분과 함께 하기를 기대합니다. 응원해 주셔서 감사합니다.<br>\n<strong>EOS 메인넷 런치 그룹</strong> <a href=\"https://steemit.com/trending/eoslaunch\">#EOSLaunch</a></p>\n<h1>只有一条名为 EOS 的主网</h1>\n<p>2018年5月25日，EOS主网启动团队(EMLG) 达成共识，承诺只会承认一条名为 EOS 的主网。我们致力于确保社区尽可能公开透明，基于此，我们提供了自己的主网启动方案。</p>\n<h2>代币冻结</h2>\n<p>ERC-20 格式的 EOS 代币将会于 UTC 时间（世界标准时间）6月1日 22:59:59结束(北京时间6月2日06:59:59)，根据 EOS 的众筹智能合约设定，ERC-20 代币会在代币发布结束23个小时后冻结。冻结完成后，我们会开始主网启动的流程，请确保你的EOS已经做过了映射。如果你没有映射，请确保生成你的密钥对，并将它们映射到持有你的 ERC - 20 格式的 EOS 代币的以太坊地址。</p>\n<h2>保持机灵，保持警惕</h2>\n<p>这段时间内， 我们预计将会有很多诈骗分子出现。请不要在任何地方导入你的私钥，除非看到你信任的至少5个节点发布联合声明可以安全导入。若忽略此警告可能导致代币丢失。请访问 IMEOS解更多关于节点候选者的信息。</p>\n<h1>概述：主网启动阶段</h1>\n<p>每个阶段都没有时间要求，因为比起每个阶段快速完成，确保每个阶段都成功完成更加重要。启动过程可能需要几天才能完成。</p>\n<ul>\n  <li><strong>检验确认快照和启动</strong>：EMLG 和第三方会进行快照和检验确认。启动程序初始化。</li>\n  <li><strong>测试</strong>：让 EMLG 和第三方有时间检验 Token 是否已经根据快照的文件加载，并且软件运行良好。投票开始。</li>\n  <li><strong>启用</strong>：BP社区发布联合声明：可以安全导入私钥并投票。</li>\n  <li><strong>激活</strong> :声明 EOS 主网有效。<br>\n<strong>只有在这4个步骤都完成之后，我们才将拥有一个不可逆的区块链。在此之前，我们不排除回滚或重启该链的可能性。这些必要步骤，包括验证测试，将耗费大量精力，有可能将耗时数日来完成。</strong></li>\n</ul>\n<h2>启动步骤的细节信息</h2>\n<h4>验证快照&amp;启动</h4>\n<p>主网启动团队（EMLG）将会使用官方快照工具来生成冻结ERC-20代币的最终快照文件。鼓励社区使用同一组工具来生成快照文件，并且检验它是否与主网启动团队的快照完全一致。一旦这个快照被检验确认，指定出块节点（ABPs）将会在启动团队中被指定。这些被指定的出块节点只是临时担当超级节点的职务，其存在单纯是为了保证主网能以正确的方式启动，以及保证在检验确认和投票的整个阶段是稳定的。此阶段指定节点不会获得任何出块奖励。</p>\n<h4>测试</h4>\n<p>一旦节点们完成了启动环节，并且确认代币余额正确，主网将会开放由第三方进行检验确认。我们欢迎任何个人或团体在当前环节来此对本网络进行检验，而检验所需的工具将由BP社区发布，以促成该检验确认的顺利进行。<br>\nEMLG将在当前环节中复制主网，并对此网络进行彻底的验收测试。本阶段将历时48小时以便这一系列测试得以完成。一旦在过程中发现重大BUG以致需要修改代码，那么这48个小时的时间窗口就将会重置，以确保我们有充裕的时间对新增的改动进行测试修复。至于过程中是否对48小时的时间窗口进行充值，将由EMLG酌情决定。<br>\n在此期间发生的事务或进行的投票是不安全的，有可能会丢失或者被撤销。</p>\n<h4>启用</h4>\n<p>一旦上一阶段结束，主网将会对持币社区开放。为了激活EOSIO主链，15%的代币持有者必须导入他们的私钥并且至少向一位节点候选人投票。私钥导入和投票环节的时间长度将取决于持币者的行动效率。“为尽快启动主链，请一起来投票吧！”许多节点已经制作了关于如何进行投票的教程。目前已经开发出一个社区投票入口。您可以在<a href=\"https://steemit.com/@eosportal\">@eosportal</a>的Twitter页面上获取投票入口架构的最新动态。再次重点强调，请不要在任何地方导入你的私钥，除非看到你信任的至少5个节点发布联合声明可以安全导入。</p>\n<h4>激活</h4>\n<p>一旦15%的代币用于投票，主链就被认为是可靠的并且常规的功能会被激活。21个指定节点会立即被21个被社区选举出来的节点所代替。</p>\n<h2>接下来的步骤</h2>\n<p>在下一份联合声明中，我们将公布“验证”期的细节以及被用于帮助第三方进行验证的工具。</p>\n<h2>向主网上线进发</h2>\n<p>EOS主网将会开创一个区块链科技的新时代，这种科技将极大地影响我们之间的交互方式。在我们努力确保主网的成功上线的同时，也希望将此经验分享给广大的持币者，感谢您的支持。<br>\nEOS主网启动团队 <a href=\"https://steemit.com/trending/eos\">#EOS</a>启动</p>\n</html>",
      "json_metadata": "{\"tags\":[\"statement\"],\"image\":[\"https://cdn.steemitimages.com/0x0/https://cdn.steemitimages.com/DQmY8j5dzQxAKmd2oUxT6skq6uyVkHhZZ82j7u9R99uPBpj/Header.png\"],\"links\":[\"https://steemit.com/eos/@sandwich/how-to-update-the-eos-public-key-mapped-registered-to-your-ethereum-wallet-with-myetherwallet-mew\",\"https://bp.eosgo.io/\",\"https://twitter.com/eosportal\",\"https://steemit.com/trending/eoslaunch\",\"http://koreos.io/\",\"https://steemit.com/@eosportal\",\"https://steemit.com/trending/eos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

steemitboardreplied to @eos.store / steemitboard-notify-eosstore-20180530t221351000z

2018/05/30 22:13:51 UTC

22,894,942|35abec1

parent author	eos.store
parent permlink	a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem
author	steemitboard
permlink	steemitboard-notify-eosstore-20180530t221351000z
title
body	Congratulations @eos.store! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/posts.png)](http://steemitboard.com/@eos.store) Award for the number of posts published Click on any badge to view your Board of Honor. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` Do not miss the [last announcement](https://steemit.com/steemitboard/@steemitboard/steemitboard-new-level-notifications) from @steemitboard! > Do you like SteemitBoard's project? [Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) and get one more award!
json metadata	{"image":["https://steemitboard.com/img/notify.png"]}
Transaction Info	Block #22894942/Trx 35abec1579d6eaa7016a8c9e178427cabc2074bc

View Raw JSON Data

{
  "trx_id": "35abec1579d6eaa7016a8c9e178427cabc2074bc",
  "block": 22894942,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-30T22:13:51",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-eosstore-20180530t221351000z",
      "title": "",
      "body": "Congratulations @eos.store! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/posts.png)](http://steemitboard.com/@eos.store) Award for the number of posts published\n\nClick on any badge to view your Board of Honor.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n**Do not miss the [last announcement](https://steemit.com/steemitboard/@steemitboard/steemitboard-new-level-notifications) from @steemitboard!**\n\n> Do you like **SteemitBoard**'s project? **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem

2018/05/29 06:13:24 UTC

22,846,936|668a547

voter	tsto
author	eos.store
permlink	a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem
weight	10000 (100.00%)
Transaction Info	Block #22846936/Trx 668a547c146f0e982bef28a5df9c25db34e2e88d

View Raw JSON Data

{
  "trx_id": "668a547c146f0e982bef28a5df9c25db34e2e88d",
  "block": 22846936,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-29T06:13:24",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem",
      "weight": 10000
    }
  ]
}

alejandrobetanupvoted (100.00%) @eos.store / a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem

2018/05/29 03:48:51 UTC

22,844,046|74a7e2f

voter	alejandrobetan
author	eos.store
permlink	a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem
weight	10000 (100.00%)
Transaction Info	Block #22844046/Trx 74a7e2ff7ae32335114e57e52afe57899c49a91b

View Raw JSON Data

{
  "trx_id": "74a7e2ff7ae32335114e57e52afe57899c49a91b",
  "block": 22844046,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-29T03:48:51",
  "op": [
    "vote",
    {
      "voter": "alejandrobetan",
      "author": "eos.store",
      "permlink": "a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem

2018/05/29 03:48:00 UTC

22,844,029|fa8ff31

parent author
parent permlink	salon
author	eos.store
permlink	a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem
title	A salon themed on “What opportunity could be seized by a developer in EOS ecosystem”
body	<html> <p><img src="https://images.eos.store/eosstore-mart-1.jpg" width="830" height="454"/></p> <p>On May 26th, EosStore held a salon themed on “What opportunity could be seized by a developer in EOS ecosystem” at X-elerator of Tsinghua SEM, an incubator for young entrepreneurs. The activity, prepared for EOS technology zealots, aimed to discuss opportunities brought by EOS ecosystem and preparations for EOS mainnet launch.</p> <p>The salon was a respond to last activity: On May 20th, an offline technology salon was held successfully by EosStore, attracting nationwide EOS fanciers to attend. Many DApp developers desired to have a further communication on some technical issues with EosStore team and hoped it could organize more same activities. Hence EosStore arranged this salon in particular, creating an in-depth discussion for more enthusiasts of EOS technology.</p> <p>There were two speakers of this activity. One is Ji Jingjing, partner of EOS Capital and responsible for EosStore marketing affairs. The other is Alex who is the dean of block chain institute of EosStore and good at solving technical problems. Besides, Kongyixueyuan（a vocational school for block chain technology training ）and 8BTC (the first website reporting bitcoin news in China ) co-held this salon with EosStore. Vertical portals like Finacerun, Cointime and Block360. Pro given a full report to this activity.</p> <p>As a partner of EOS Capital, Ji Jingjing made her sharing firstly. She explained a closed-loop ecosystem created by EosStore with a fund, a DApp store and a community being three in one. “EOS itself is an operation system of business applications. We believe lots of such apps will achieve their practical use in EOS ecosystem. Jingjing said, “We want to help more developers and their prime projects, thus to promote the practical use of more apps and co-develop a prosperous EOS ecosystem with all developers.”</p> <p><img src="https://images.eos.store/eosstore-mart-2.jpg" width="830" height="562"/></p> <p>JJ said that EosStore had received dozens of DApp projects from developers and communicated with over 40 of them. After a preliminary selection, some DApps had been presenting at the DApp store of EosStore.</p> <p>With many air tokens appearing after the subsidence of block chain frenzy, only EOS has realized its practical use, from which we could see the promising future block chain technology from EOS. At the end of her sharing, Jingjing expressed that EosStore team will unceasingly uphold the slogan of “focusing on the practical use of commercial applications”, co-building a highly efficient decentralized community featuring freedom, equality and mutual-respect. </p> <p><img src="https://images.eos.store/eosstore-mart-4.jpg" width="830" height="554"/></p> <p>Ensuring came a technical sharing given by Alex, dean of block chain institute of EosStore. He explained whole procedures of EOS mainnet launch and functions of some smart contracts and RAM. Besides, he elaborated on the block chain generation mechanism—Byzantine Fault Tolerance plus DPOS mechanism, and explained why did BM use these principles on EOS to answer questions from attendees.</p> <p>EosStore developed a Baas-based basic architecture--Docker+OpenShift, providing an access for users to easy development. At last, Alex shared how to launch EOS node by Docker and took a projects on EosStore as an example.</p> <p>Q&A session lighted the atmosphere after the end of Alex’s sharing， with many EOS fanciers actively raising questions and delivering in-depth discussions of some technical questions. Meanwhile, EosStore released its recruitment, hoping to find more talents to join its team via this technology salon.</p> <p><img src="https://images.eos.store/eosstore-mart-3.jpg" width="830" height="554"/></p> <p>This technology salon not only meant a better understanding of EosStore for EOS fanciers, but also displayed the superior technical capability of the team. Attendees strengthened their faith and belief in block chain technology after this discussion and study. EOS has a promising future and a new era of block chain is coming. EosStore will always support and provide guidance to all EOS technology zealots. </p> <p><br></p> <p>Email: [email protected] </p> <p>Website: <a href="http://www.eos.store/">http://www.eos.store</a> </p> <p>Twitter: <a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a> </p> <p>Github: <a href="https://github.com/eosstore">https://github.com/eosstore</a> </p> <p>Eosgo: <a href="https://steemit.com/@eos.store">https://steemit.com/@eos.store</a></p> <p>Telegram: <a href="https://t.me/StoreEos">https://t.me/StoreEos</a></p> </html>
json metadata	{"tags":["salon","eos","ecosystem"],"image":["https://images.eos.store/eosstore-mart-1.jpg","https://images.eos.store/eosstore-mart-2.jpg","https://images.eos.store/eosstore-mart-4.jpg","https://images.eos.store/eosstore-mart-3.jpg"],"links":["http://www.eos.store/","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22844029/Trx fa8ff31dd340022d48b0adb414d046ba8e6e6e84

View Raw JSON Data

{
  "trx_id": "fa8ff31dd340022d48b0adb414d046ba8e6e6e84",
  "block": 22844029,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-29T03:48:00",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "salon",
      "author": "eos.store",
      "permlink": "a-salon-themed-on-what-opportunity-could-be-seized-by-a-developer-in-eos-ecosystem",
      "title": "A salon themed on “What opportunity could be seized by a developer in EOS ecosystem”",
      "body": "<html>\n<p><img src=\"https://images.eos.store/eosstore-mart-1.jpg\" width=\"830\" height=\"454\"/></p>\n<p>On May 26th, EosStore held a salon themed on “What opportunity could be seized by a developer in EOS ecosystem” at X-elerator of Tsinghua SEM, an incubator for young entrepreneurs. The activity, prepared for EOS technology zealots, aimed to discuss opportunities brought by EOS ecosystem and preparations for EOS mainnet launch.</p>\n<p>The salon was a respond to last activity: On May 20th, an offline technology salon was held successfully by EosStore, attracting nationwide EOS fanciers to attend. Many DApp developers desired to have a further communication on some technical issues with EosStore team and hoped it could organize more same activities. Hence EosStore arranged this salon in particular, creating an in-depth discussion for more enthusiasts of EOS technology.</p>\n<p>There were two speakers of this activity. One is Ji Jingjing, partner of EOS Capital and responsible for EosStore marketing affairs. The other is Alex who is the dean of block chain institute of EosStore and good at solving technical problems. Besides, Kongyixueyuan（a vocational school for block chain technology training ）and 8BTC (the first website reporting bitcoin news in China ) co-held this salon with EosStore. Vertical portals like Finacerun, Cointime and Block360. Pro given a full report to this activity.</p>\n<p>As a partner of EOS Capital, Ji Jingjing made her sharing firstly. She explained a closed-loop ecosystem created by EosStore with a fund, a DApp store and a community being three in one. “EOS itself is an operation system of business applications. We believe lots of such apps will achieve their practical use in EOS ecosystem. Jingjing said, “We want to help more developers and their prime projects, thus to promote the practical use of more apps and co-develop a prosperous EOS ecosystem with all developers.”</p>\n<p><img src=\"https://images.eos.store/eosstore-mart-2.jpg\" width=\"830\" height=\"562\"/></p>\n<p>JJ said that EosStore had received dozens of DApp projects from developers and communicated with over 40 of them. After a preliminary selection, some DApps had been presenting at the DApp store of EosStore.</p>\n<p>With many air tokens appearing after the subsidence of block chain frenzy, only EOS has realized its practical use, from which we could see the promising future block chain technology from EOS. At the end of her sharing, Jingjing expressed that EosStore team will unceasingly uphold the slogan of “focusing on the practical use of commercial applications”, co-building a highly efficient decentralized community featuring freedom, equality and mutual-respect.&nbsp;</p>\n<p><img src=\"https://images.eos.store/eosstore-mart-4.jpg\" width=\"830\" height=\"554\"/></p>\n<p>Ensuring came a technical sharing given by Alex, dean of block chain institute of EosStore. He explained whole procedures of EOS mainnet launch and functions of some smart contracts and RAM. Besides, he elaborated on the block chain generation mechanism—Byzantine Fault Tolerance plus DPOS mechanism, and explained why did BM use these principles on EOS to answer questions from attendees.</p>\n<p>EosStore developed a Baas-based basic architecture--Docker+OpenShift, providing an access for users to easy development. At last, Alex shared how to launch EOS node by Docker and took a projects on EosStore as an example.</p>\n<p>Q&amp;A session lighted the atmosphere after the end of Alex’s sharing， with many EOS fanciers actively raising questions and delivering in-depth discussions of some technical questions. Meanwhile, EosStore released its recruitment, hoping to find more talents to join its team via this technology salon.</p>\n<p><img src=\"https://images.eos.store/eosstore-mart-3.jpg\" width=\"830\" height=\"554\"/></p>\n<p>This technology salon not only meant a better understanding of EosStore for EOS fanciers, but also displayed the superior technical capability of the team. Attendees strengthened their faith and belief in block chain technology after this discussion and study. EOS has a promising future and a new era of block chain is coming. EosStore will always support and provide guidance to all EOS technology zealots.&nbsp;</p>\n<p><br></p>\n<p>Email: [email protected]&nbsp;</p>\n<p>Website: <a href=\"http://www.eos.store/\">http://www.eos.store</a>&nbsp;</p>\n<p>Twitter: <a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a>&nbsp;</p>\n<p>Github: <a href=\"https://github.com/eosstore\">https://github.com/eosstore</a>&nbsp;</p>\n<p>Eosgo: <a href=\"https://steemit.com/@eos.store\">https://steemit.com/@eos.store</a></p>\n<p>Telegram: <a href=\"https://t.me/StoreEos\">https://t.me/StoreEos</a></p>\n</html>",
      "json_metadata": "{\"tags\":[\"salon\",\"eos\",\"ecosystem\"],\"image\":[\"https://images.eos.store/eosstore-mart-1.jpg\",\"https://images.eos.store/eosstore-mart-2.jpg\",\"https://images.eos.store/eosstore-mart-4.jpg\",\"https://images.eos.store/eosstore-mart-3.jpg\"],\"links\":[\"http://www.eos.store/\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storereplied to @eostribe / re-eostribe-eos-bp-security-statement-20180529t022842664z

2018/05/29 02:28:42 UTC

22,842,443|8e51c8e

parent author	eostribe
parent permlink	eos-bp-security-statement
author	eos.store
permlink	re-eostribe-eos-bp-security-statement-20180529t022842664z
title
body	This is a good article with a lot of good security advice, but I suggest that the Ghostbuster team and the Canada team and other core teams can communicate deeply, make up for each other's shortcomings, and finally reach the same starting point, such as reaching a compatible solution that will not cause the community to split up, only in this way can we start a main network in the whole world. The following figure is a deployment diagram that I suggest for each BP. Each BP provides two types of nodes, some node communication with other BP's nodes through VPN(WireGuard), some use public networks to connect directly to other BP nodes， The details are decided by BP himself ![[email protected]](https://cdn.steemitimages.com/DQmZ7pWUzP2jJzuZbtbda4yAtkniTVZTHaEbTfKxytZXrwD/[email protected])
json metadata	{"tags":["eos"],"image":["https://cdn.steemitimages.com/DQmZ7pWUzP2jJzuZbtbda4yAtkniTVZTHaEbTfKxytZXrwD/[email protected]"],"app":"steemit/0.1"}
Transaction Info	Block #22842443/Trx 8e51c8e79844087cabba1a7c9f159058376dad32

View Raw JSON Data

{
  "trx_id": "8e51c8e79844087cabba1a7c9f159058376dad32",
  "block": 22842443,
  "trx_in_block": 36,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-29T02:28:42",
  "op": [
    "comment",
    {
      "parent_author": "eostribe",
      "parent_permlink": "eos-bp-security-statement",
      "author": "eos.store",
      "permlink": "re-eostribe-eos-bp-security-statement-20180529t022842664z",
      "title": "",
      "body": "This is a good article with a lot of good security advice, but I suggest that the Ghostbuster team and the Canada team and other core teams can communicate deeply, make up for each other's shortcomings, and finally reach the same starting point, such as reaching a compatible solution that will not cause the community to split up, only in this way can we start a main network in the whole world.\n\nThe following figure is a deployment diagram that I suggest for each BP. Each BP provides two types of nodes, some node communication with other BP's nodes through VPN(WireGuard), some use public networks to connect directly to other BP nodes， The details are decided by BP himself\n![[email protected]](https://cdn.steemitimages.com/DQmZ7pWUzP2jJzuZbtbda4yAtkniTVZTHaEbTfKxytZXrwD/[email protected])",
      "json_metadata": "{\"tags\":[\"eos\"],\"image\":[\"https://cdn.steemitimages.com/DQmZ7pWUzP2jJzuZbtbda4yAtkniTVZTHaEbTfKxytZXrwD/[email protected]\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

eos.storepublished a new post: the-best-deployment-practice-of-eos-bp-nodes

2018/05/27 17:40:42 UTC

22,803,087|c32a5f6

parent author
parent permlink	eos
author	eos.store
permlink	the-best-deployment-practice-of-eos-bp-nodes
title	The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）
body	@@ -78,16 +78,14 @@ is -the best +a good pra @@ -254,12 +254,13 @@ %E8%83%BD%E6%83%B3%E5%88%B0%E7%9A%84 -%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5 +%E5%BE%88%E5%A5%BD%E7%9A%84%E6%96%B9%E6%A1%88 %EF%BC%8C%E5%8F%AF%E4%BB%A5%E6%9C%89 @@ -461,18 +461,17 @@ /%3E%3C/p%3E%0A%3C -h3 +p %3EFigure- @@ -477,10 +477,9 @@ -2%3C/ -h3 +p %3E%0A%3Cp @@ -1929,16 +1929,24 @@ tantly, +%3Cstrong%3E BP node @@ -2035,16 +2035,25 @@ c net IP +%3C/strong%3E , all BP @@ -4199,15 +4199,85 @@ %E5%85%B3%E7%B3%BB%E3%80%82%3C/p%3E%0A +%3Cp%3ESupported by %3Ca href=%22www.eos.store%22%3EEOS Store%3C/a%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A %3C/html%3E
json metadata	{"tags":["eos","bp","deployment","best","practice"],"image":["https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png","https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png"],"app":"steemit/0.1","format":"html","links":["www.eos.store"]}
Transaction Info	Block #22803087/Trx c32a5f67ee9e00a8a1187a092fb573b5a0f00ca8

View Raw JSON Data

{
  "trx_id": "c32a5f67ee9e00a8a1187a092fb573b5a0f00ca8",
  "block": 22803087,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-27T17:40:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "eos.store",
      "permlink": "the-best-deployment-practice-of-eos-bp-nodes",
      "title": "The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）",
      "body": "@@ -78,16 +78,14 @@\n  is \n-the best\n+a good\n  pra\n@@ -254,12 +254,13 @@\n %E8%83%BD%E6%83%B3%E5%88%B0%E7%9A%84\n-%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5\n+%E5%BE%88%E5%A5%BD%E7%9A%84%E6%96%B9%E6%A1%88\n %EF%BC%8C%E5%8F%AF%E4%BB%A5%E6%9C%89\n@@ -461,18 +461,17 @@\n /%3E%3C/p%3E%0A%3C\n-h3\n+p\n %3EFigure-\n@@ -477,10 +477,9 @@\n -2%3C/\n-h3\n+p\n %3E%0A%3Cp\n@@ -1929,16 +1929,24 @@\n tantly, \n+%3Cstrong%3E\n BP node \n@@ -2035,16 +2035,25 @@\n c net IP\n+%3C/strong%3E\n , all BP\n@@ -4199,15 +4199,85 @@\n %E5%85%B3%E7%B3%BB%E3%80%82%3C/p%3E%0A\n+%3Cp%3ESupported by %3Ca href=%22www.eos.store%22%3EEOS Store%3C/a%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A\n %3C/html%3E\n",
      "json_metadata": "{\"tags\":[\"eos\",\"bp\",\"deployment\",\"best\",\"practice\"],\"image\":[\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png\",\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png\"],\"app\":\"steemit/0.1\",\"format\":\"html\",\"links\":[\"www.eos.store\"]}"
    }
  ]
}

eos.storepublished a new post: the-best-deployment-practice-of-eos-bp-nodes

2018/05/27 17:36:00 UTC

22,802,993|96c61f7

parent author
parent permlink	eos
author	eos.store
permlink	the-best-deployment-practice-of-eos-bp-nodes
title	The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）
body	@@ -112,16 +112,61 @@ hink of, + which can effectively avoid the DDoS attack, if you @@ -235,10 +235,8 @@ p%3E%E4%BB%8A%E5%A4%A9 -%E6%88%91%E6%83%B3 %E5%92%8C%E5%A4%A7%E5%AE%B6%E5%88%86 @@ -257,16 +257,30 @@ %E6%83%B3%E5%88%B0%E7%9A%84%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5%EF%BC%8C +%E5%8F%AF%E4%BB%A5%E6%9C%89%E6%95%88%E7%9A%84%E9%81%BF%E5%BC%80DDoS%E6%94%BB%E5%87%BB%EF%BC%8C %E5%A6%82%E6%9E%9C%E6%82%A8%E6%9C%89%E6%9B%B4%E5%A5%BD%E7%9A%84%E6%83%B3 @@ -638,28 +638,16 @@ %3C/p%3E%0A%3Cp%3E -   As shown @@ -995,24 +995,32 @@    +%3C/p%3E%0A%3Cp%3E The IP of th @@ -1383,24 +1383,32 @@    +%3C/p%3E%0A%3Cp%3E The full nod @@ -1906,16 +1906,24 @@ p;  +%3C/p%3E%0A%3Cp%3E Most imp @@ -2284,24 +2284,32 @@    +%3C/p%3E%0A%3Cp%3E  You ca @@ -2495,24 +2495,32 @@    +%3C/p%3E%0A%3Cp%3E  The P2 @@ -2705,16 +2705,24 @@ p;  +%3C/p%3E%0A%3Cp%3E A revers @@ -2822,29 +2822,30 @@ l nodes. -   -  +%3C/p%3E%0A%3Cp%3E In addit
json metadata	{"tags":["eos","bp","deployment","best","practice"],"image":["https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png","https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22802993/Trx 96c61f7aeba90b0d972e1deae74bd89b700cb6c2

View Raw JSON Data

{
  "trx_id": "96c61f7aeba90b0d972e1deae74bd89b700cb6c2",
  "block": 22802993,
  "trx_in_block": 80,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-27T17:36:00",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "eos.store",
      "permlink": "the-best-deployment-practice-of-eos-bp-nodes",
      "title": "The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）",
      "body": "@@ -112,16 +112,61 @@\n hink of,\n+ which can effectively avoid the DDoS attack,\n  if you \n@@ -235,10 +235,8 @@\n p%3E%E4%BB%8A%E5%A4%A9\n-%E6%88%91%E6%83%B3\n %E5%92%8C%E5%A4%A7%E5%AE%B6%E5%88%86\n@@ -257,16 +257,30 @@\n %E6%83%B3%E5%88%B0%E7%9A%84%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5%EF%BC%8C\n+%E5%8F%AF%E4%BB%A5%E6%9C%89%E6%95%88%E7%9A%84%E9%81%BF%E5%BC%80DDoS%E6%94%BB%E5%87%BB%EF%BC%8C\n %E5%A6%82%E6%9E%9C%E6%82%A8%E6%9C%89%E6%9B%B4%E5%A5%BD%E7%9A%84%E6%83%B3\n@@ -638,28 +638,16 @@\n %3C/p%3E%0A%3Cp%3E\n-&nbsp;&nbsp;\n As shown\n@@ -995,24 +995,32 @@\n &nbsp;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n The IP of th\n@@ -1383,24 +1383,32 @@\n &nbsp;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n The full nod\n@@ -1906,16 +1906,24 @@\n p;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n Most imp\n@@ -2284,24 +2284,32 @@\n &nbsp;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n &nbsp;You ca\n@@ -2495,24 +2495,32 @@\n &nbsp;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n &nbsp;The P2\n@@ -2705,16 +2705,24 @@\n p;&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n A revers\n@@ -2822,29 +2822,30 @@\n l nodes.\n- \n &nbsp;\n-&nbsp;\n+%3C/p%3E%0A%3Cp%3E\n In addit\n",
      "json_metadata": "{\"tags\":[\"eos\",\"bp\",\"deployment\",\"best\",\"practice\"],\"image\":[\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png\",\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storepublished a new post: the-best-deployment-practice-of-eos-bp-nodes

2018/05/27 17:31:09 UTC

22,802,896|fd42fab

parent author
parent permlink	eos
author	eos.store
permlink	the-best-deployment-practice-of-eos-bp-nodes
title	The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）
body	<html> <p>Today I want to share with you the bp node cluster deployment. This is the best practice that I can think of, if you have a better idea, please leave a message below.  </p> <p>今天我想和大家分享超级节点集群部署。这是我能想到的最佳实践，如果您有更好的想法，欢迎在下面留言。 </p> <p>Figure-1</p> <p><img src="https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png" width="2310" height="1198"/></p> <h3>Figure-2</h3> <p><img src="https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png" width="2280" height="552"/></p> <p><br></p> <p>  As shown above, we have prepared a master BP node and two backup BP nodes. We (EOS Store) actually choose AWS to deploy these nodes, the master BP node and the backup BP node 1 are located in Tokyo, Japan, and the master BP node and the backup BP node 1 are located in different failure areas in Tokyo, and backup BP node 2 is located in Singapore.   The IP of the green full node in the graph is needed to be exposed to other BP so that other BP can be connected, and the IP of these nodes is easily leaked to the hacker, so it is very easy to be attacked, but in this network structure, even if the green full node is attacked and down, it will not affect the normal operation of the BP node.       The full node and BP node configuration files (config.ini) should be added as many "p2p-peer-address = ip:port" as possible.   For example, achieve 20, and try to connect each node to a number of different IPs. In this way, four full nodes and two BP nodes share a total of about 120 (206) IPs, which is already a relatively large number of connections. Even if two green full nodes is attacked, the entire cluster will still maintain 80 (204) connections. This structure is very solid.   Most importantly, BP node (master BP node and backup BP nodes) and the blue nodes in the graph have no public net IP, all BP nodes and blue nodes communicate directly with the public network IP provided by other BP. I have tested that BP nodes can still produce block without public net IP, so that hackers can't attack BP nodes and blue full nodes.      You can also add or reduce the blue or green full node in the picture according to your situation. The simplest way is that you can have only one green full node and one BP node.     The P2P port of a green node can use 80 ports, or other well-known ports, not 9871 ports, hidden in well-known ports can make it difficult for hackers to find the IPs of the node.   A reverse proxy is added to the API node to limit the flow to ensure the security of the back end full nodes.   In addition, the configuration item of "p2p-peer-address =" in config.ini is not related to the configuration item "max-client = 25", the former is set by the node's active connection to other nodes, and the latter only restricts the number of connections from the external node. These two parameters are not related to each other.  </p> <p><br></p> <p>  如上图所示，我们准备了一个主BP节点和两个备用BP节点。我们（EOS Store）实际会选择AWS在日本和新加坡的云部署这些节点，主BP节点和备BP节点1位于日本东京，并且主BP节点和备BP节点1位于东京不同的失效区，备BP节点2位于新加坡。   图中绿色full node的ip是需要对其他BP公开的，好让其他BP进行p2p连接，这些节点的ip也很容易被泄漏给黑客，因此非常容易被攻击，但在这个网络结构里面，即使绿色的full node被攻击而宕机，也不会影响BP节点正常运行。   </p> <p>图中full node和BP node的配置文件（config.ini）中应添加尽可能多的“p2p-peer-address = ip:port”，比如达到20个，并且尽量让每个节点连接多个不同的ip。这样，四个full node 和两个BP node总共和外界约120（206）个ip保持连接，已经是比较大的连接数量。就算两个绿色的full node被攻击，整个集群依然保持80（204）个连接。这样的结构是非常稳固的。</p> <p>最最关键的是，<strong>任何BP节点（主BP和备BP节点）和图中的蓝色节点都没有公网ip</strong>，所有的BP节点和蓝色节点直接和其他BP提供的ip通信，我已经测试过，BP节点在没有公网ip的情况下依然可以正常出块，这样就让黑客无法攻击BP节点，也无法攻击蓝色节点。   也可以根据你的情况，增加或减少图中蓝色或绿色的full node。最简单的模式是，你可以只有一个绿色full node和一个BP node。   绿色节点的p2p端口可以使用80端口，或其他知名端口，而不是9871端口，隐蔽在常用的端口当中会让黑客很难发现节点的ip。   </p> <p>为api节点增加反向代理，进行限流，以保证后端节点的安全。</p> <p>另：在config.ini中“p2p-peer-address = ” 整个配置项和“max-client = 25”整个配置项是不相关的，前者设置的是本节点主动连接其他节点的连接数，后者仅仅限制的是外部节点主动连接本节点的连接数。这两个参数并没有关系。</p> </html>
json metadata	{"tags":["eos","bp","deployment","best","practice"],"image":["https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png","https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22802896/Trx fd42fab5888efbb52d69350e42a2b41b1b080247

View Raw JSON Data

{
  "trx_id": "fd42fab5888efbb52d69350e42a2b41b1b080247",
  "block": 22802896,
  "trx_in_block": 67,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-27T17:31:09",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "eos.store",
      "permlink": "the-best-deployment-practice-of-eos-bp-nodes",
      "title": "The Best Deployment Practice of EOS BP Nodes（超级节点部署最佳实践）",
      "body": "<html>\n<p>Today I want to share with you the bp node cluster deployment. This is the best practice that I can think of, if you have a better idea, please leave a message below. &nbsp;</p>\n<p>今天我想和大家分享超级节点集群部署。这是我能想到的最佳实践，如果您有更好的想法，欢迎在下面留言。&nbsp;</p>\n<p>Figure-1</p>\n<p><img src=\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png\" width=\"2310\" height=\"1198\"/></p>\n<h3>Figure-2</h3>\n<p><img src=\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png\" width=\"2280\" height=\"552\"/></p>\n<p><br></p>\n<p>&nbsp;&nbsp;As shown above, we have prepared a master BP node and two backup BP nodes. We (EOS Store) actually choose AWS to deploy these nodes, the master BP node and the backup BP node 1 are located in Tokyo, Japan, and the master BP node and the backup BP node 1 are located in different failure areas in Tokyo, and backup BP node 2 is located in Singapore. &nbsp;&nbsp;The IP of the green full node in the graph is needed to be exposed to other BP so that other BP can be connected, and the IP of these nodes is easily leaked to the hacker, so it is very easy to be attacked, but in this network structure, even if the green full node is attacked and down, it will not affect the normal operation of the BP node. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The full node and BP node configuration files (config.ini) should be added as many \"p2p-peer-address = ip:port\" as possible. &nbsp;&nbsp;For example, achieve 20, and try to connect each node to a number of different IPs. In this way, four full nodes and two BP nodes share a total of about 120 (20*6) IPs, which is already a relatively large number of connections. Even if two green full nodes is attacked, the entire cluster will still maintain 80 (20*4) connections. This structure is very solid. &nbsp;&nbsp;Most importantly, BP node (master BP node and backup BP nodes) and the blue nodes in the graph have no public net IP, all BP nodes and blue nodes communicate directly with the public network IP provided by other BP. I have tested that BP nodes can still produce block without public net IP, so that hackers can't attack BP nodes and blue full nodes. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;You can also add or reduce the blue or green full node in the picture according to your situation. The simplest way is that you can have only one green full node and one BP node. &nbsp;&nbsp;&nbsp;&nbsp;The P2P port of a green node can use 80 ports, or other well-known ports, not 9871 ports, hidden in well-known ports can make it difficult for hackers to find the IPs of the node. &nbsp;&nbsp;A reverse proxy is added to the API node to limit the flow to ensure the security of the back end full nodes. &nbsp;&nbsp;In addition, the configuration item of \"p2p-peer-address =\" in config.ini is not related to the configuration item \"max-client = 25\", the former is set by the node's active connection to other nodes, and the latter only restricts the number of connections from the external node. These two parameters are not related to each other. &nbsp;</p>\n<p><br></p>\n<p>&nbsp;&nbsp;如上图所示，我们准备了一个主BP节点和两个备用BP节点。我们（EOS Store）实际会选择AWS在日本和新加坡的云部署这些节点，主BP节点和备BP节点1位于日本东京，并且主BP节点和备BP节点1位于东京不同的失效区，备BP节点2位于新加坡。 &nbsp;&nbsp;图中绿色full node的ip是需要对其他BP公开的，好让其他BP进行p2p连接，这些节点的ip也很容易被泄漏给黑客，因此非常容易被攻击，但在这个网络结构里面，即使绿色的full node被攻击而宕机，也不会影响BP节点正常运行。 &nbsp;&nbsp;</p>\n<p>图中full node和BP node的配置文件（config.ini）中应添加尽可能多的“p2p-peer-address = ip:port”，比如达到20个，并且尽量让每个节点连接多个不同的ip。这样，四个full node 和两个BP node总共和外界约120（20*6）个ip保持连接，已经是比较大的连接数量。就算两个绿色的full node被攻击，整个集群依然保持80（20*4）个连接。这样的结构是非常稳固的。</p>\n<p>最最关键的是，<strong>任何BP节点（主BP和备BP节点）和图中的蓝色节点都没有公网ip</strong>，所有的BP节点和蓝色节点直接和其他BP提供的ip通信，我已经测试过，BP节点在没有公网ip的情况下依然可以正常出块，这样就让黑客无法攻击BP节点，也无法攻击蓝色节点。 &nbsp;&nbsp;也可以根据你的情况，增加或减少图中蓝色或绿色的full node。最简单的模式是，你可以只有一个绿色full node和一个BP node。 &nbsp;&nbsp;绿色节点的p2p端口可以使用80端口，或其他知名端口，而不是9871端口，隐蔽在常用的端口当中会让黑客很难发现节点的ip。 &nbsp;&nbsp;</p>\n<p>为api节点增加反向代理，进行限流，以保证后端节点的安全。</p>\n<p>另：在config.ini中“p2p-peer-address = ” 整个配置项和“max-client = 25”整个配置项是不相关的，前者设置的是本节点主动连接其他节点的连接数，后者仅仅限制的是外部节点主动连接本节点的连接数。这两个参数并没有关系。</p>\n</html>",
      "json_metadata": "{\"tags\":[\"eos\",\"bp\",\"deployment\",\"best\",\"practice\"],\"image\":[\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE1.png\",\"https://raw.githubusercontent.com/vchengsong/eos-env/master/pics/%E9%83%A8%E7%BD%B2%E5%9B%BE2.png\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storepublished a new post: statement-to-community

2018/05/25 15:17:12 UTC

22,742,630|4178304

parent author
parent permlink	statement
author	eos.store
permlink	statement-to-community
title	STATEMENT TO COMMUNITY
body	<html> <p>To The EOS Token Holder Community,As the launch of EOS nears, speculation within the community concerning competing EOS mainnet launches has increased. As one of many Block Producers across the world responsible for organizing and launching the EOS mainnet, we would like to put the community at ease and declare our intent for the following:We, EosStore, do hereby pledge to present to the community one chain which fully honours the EOS token distribution for their validation. We further agree that we will support calling this validated chain the EOS mainnet, exclusively and definitively.We publish this letter in concert with following Block Producer candidates from the global community:Sincerely,</p> <p><br> EosStore & The EOS Block Producer Community《一份致予社区的声明》致EOS持有人社区随着EOS发布时间的临近，社区内有关各团队竞相启动EOS主网上线的猜测日益升温。作为全球负责组织和启动EOS主网上线的众多节点中的一员，我们希望社区消除疑虑，并将团队意向声明如下：我们，EosStore，在此承诺将与其他团队共同合作，向社区提供唯一的一条EOS公链，充分尊重并遵循可供验证的EOS代币分配机制。同时，我们约定并明确支持将这条经过验证的公链命名为EOS主网。</p> <p>我们与如下来自全球社区的节点竞选团队联合发布此项申明：</p> <p>诚致，<br> EosStore 及 EOS节点社区</p> </html>
json metadata	{"tags":["statement","to","community"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22742630/Trx 41783041467f08037f8728160344dc0faa42b793

View Raw JSON Data

{
  "trx_id": "41783041467f08037f8728160344dc0faa42b793",
  "block": 22742630,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-25T15:17:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "statement",
      "author": "eos.store",
      "permlink": "statement-to-community",
      "title": "STATEMENT TO COMMUNITY",
      "body": "<html>\n<p>To The EOS Token Holder Community,As the launch of EOS nears, speculation within the community concerning competing EOS mainnet launches has increased. As one of many Block Producers across the world responsible for organizing and launching the EOS mainnet, we would like to put the community at ease and declare our intent for the following:We, EosStore, do hereby pledge to present to the community one chain which fully honours the EOS token distribution for their validation. We further agree that we will support calling this validated chain the EOS mainnet, exclusively and definitively.We publish this letter in concert with following Block Producer candidates from the global community:Sincerely,</p>\n<p><br>\nEosStore &amp; The EOS Block Producer Community《一份致予社区的声明》致EOS持有人社区随着EOS发布时间的临近，社区内有关各团队竞相启动EOS主网上线的猜测日益升温。作为全球负责组织和启动EOS主网上线的众多节点中的一员，我们希望社区消除疑虑，并将团队意向声明如下：我们，EosStore，在此承诺将与其他团队共同合作，向社区提供唯一的一条EOS公链，充分尊重并遵循可供验证的EOS代币分配机制。同时，我们约定并明确支持将这条经过验证的公链命名为EOS主网。</p>\n<p>我们与如下来自全球社区的节点竞选团队联合发布此项申明：</p>\n<p>诚致，<br>\nEosStore 及 EOS节点社区</p>\n</html>",
      "json_metadata": "{\"tags\":[\"statement\",\"to\",\"community\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

tstoupvoted (100.00%) @eos.store / the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners

2018/05/23 11:49:03 UTC

22,681,236|089aade

voter	tsto
author	eos.store
permlink	the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners
weight	10000 (100.00%)
Transaction Info	Block #22681236/Trx 089aadefea8a20474274bb5c264423b37cc2d19a

View Raw JSON Data

{
  "trx_id": "089aadefea8a20474274bb5c264423b37cc2d19a",
  "block": 22681236,
  "trx_in_block": 71,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-23T11:49:03",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners",
      "weight": 10000
    }
  ]
}

tstoupvoted (100.00%) @eos.store / eos-store-block-producer-report-vote-for-us

2018/05/23 11:23:36 UTC

22,680,728|2256348

voter	tsto
author	eos.store
permlink	eos-store-block-producer-report-vote-for-us
weight	10000 (100.00%)
Transaction Info	Block #22680728/Trx 225634815ffcd6b9775bb252aeac8cc5780975ee

View Raw JSON Data

{
  "trx_id": "225634815ffcd6b9775bb252aeac8cc5780975ee",
  "block": 22680728,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-23T11:23:36",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report-vote-for-us",
      "weight": 10000
    }
  ]
}

tstoupvoted (100.00%) @eos.store / eos-store-block-producer-report-roadmap-and-views-on-dividends

2018/05/23 11:23:30 UTC

22,680,726|f14b325

voter	tsto
author	eos.store
permlink	eos-store-block-producer-report-roadmap-and-views-on-dividends
weight	10000 (100.00%)
Transaction Info	Block #22680726/Trx f14b325ee6d905001d20ee080233ddbff3f88243

View Raw JSON Data

{
  "trx_id": "f14b325ee6d905001d20ee080233ddbff3f88243",
  "block": 22680726,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-23T11:23:30",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report-roadmap-and-views-on-dividends",
      "weight": 10000
    }
  ]
}

eos.storepublished a new post: the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners

2018/05/23 06:35:45 UTC

22,674,981|aad4560

parent author
parent permlink	eos
author	eos.store
permlink	the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners
title	The Second Half of EOS BP Election: A Real Competition Among All 8 Check-mark Winners
body	<html> <blockquote>https://steemit.com/eos/@eosgo/block-producer-candidate-report-9-may-16-2018</blockquote> <p><img src="https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmVzxVgPGboiGAsAUbSszkXchoLFyBG1zbySsLrNXJuM1C" width="850" height="300"/></p> <p>On May 16th (UTC Time), EOS GO published the Block Producer Candidates Report #9, showing 41 new block producer candidates, the totality of global BPCs, and test scores of all of them. Candidates who won 8 checkmarks all released this good news to show their competence.</p> <p>Only 10 days left before EOS MainNet launch means that this BP competition is turn to the second half and its ending is coming. At present, the situation of this BP election is just like the sea, calm on its surface while simmering in depth.</p> <p><img src="https://img.jinse.com/806767_image3.png" width="600" height="400"/></p> <p>Nowadays, hotspot topics about EOS are non-stop, with EOS Block Producer Show sponsored by Huobi Pool in early days and EOS Global BP Summit on May 19th in Shanghai. The Shanghai summit got many well-known BP candidates and famous people in digital currency field together, including BPCs as EOS Gravity, EOS Cannon, and EosStore and stars like Gongming and Li Xiaolai, which made EOS become hotly discussed again.</p> <p><br></p> <p><code>What does 8 checkmarks mean for the election?</code></p> <p><img src="https://images.eos.store/eos-go-1.jpg" width="2552" height="1152"/></p> <p>Seriously, as 8 criteria for EOS.IO to evaluate all BPCs, 8 checkmarks contain public presence, ID on Steemit, Tech plans, scaling, community, telegram+testnet, BP roadmap and position on dividend. A candidate passing all these criteria means it is quite well-prepared and accepted by EOS.IO.</p> <p>Comprehensively, there are nearly 100 candidates winning 8 checkmarks, while the number of BPs is only 21. BP election will be a fierce competition among these teams on all-round strength.</p> <p>What about competitions among these famous leading candidates in China？As EOS holders, how to follow up the development of  EOS? How to do with their votes? All these issues should be concerned by EOS holders, especially at the late stage of the election.</p> <p><br></p> <p><code>Who will win the second half competition?</code></p> <p><br></p> <p>EOS is a block chain operation system based on decentralized applications, the features of which determine that candidate team could select their roles from protector, developer and investor during the ecosystem construction process. A protector is set to guarantee the stable operation of the public chain; A developer plays a role in introducing development teams and incubating them; while investors mostly use their fund to support the sustainable development of the ecosystem and make it live and full of energy.</p> <p>OracleChain, highlighting technology, tends to be as a protector to support EOS ecosystem in hardware, sustaining the stable operation and competence of the public chain.</p> <p>Boasting about a community with over 30,000 members, HelloEOS is good at community operating and marketing. It is reported that HelloEOS, inclined to be as a developer and also a protector, has a professional team responsible for reviewing and incubating DApp development.</p> <p>As a community based candidate, EOS Cannon is the same with EOS Gravity on community scale and both of them incline to become investors.</p> <p>Huobi is an all-rounder who has a big plan. At block producer summit on May 19th, it declared to establish a platform gathering all BP candidates, making it easier for EOS holders to follow up dynamics of all BPCs.</p> <p>EosStore is a new comer. Although it announced to focus on the practical use of commercial scale applications, its 8-digit EOS incubation fund made it more like a investor. However, accompanied with various kinds of online and offline activities, EosStore has the tendency to become an all-rounder.</p> <p>Lu Haifeng, the founder of EosStore, expressed that EosStore’s announcement of running for BP election at the late stage was not an abrupt decision. The team has always been preparing at previous stages, including single node test, whole testnet and operation and development of DApps on testnet. EosStore would not announce its candidacy before it accumulated its technical storage and technology strength and built its whole testnet. EosStore’s operation mode based on EOS ecosystem has been clearly defined. A closed loop ecosystem with a fund, a community and a DApp store being three in one will be created.</p> <p>As for why the team chose EosStore as its name, Lu Haifeng mentioned that they understand and support BM’s original intention, which is focusing on the practical use of commercial scale applications and incubating, investing and serving developers in the whole ecosystem. For easier understanding, nowadays most people use products of Apple Inc. , while the first and foremost one for the whole Apple ecosystem is its APP Store. If we say “EOS ecosystem” will be same with the “Apple ecosystem”, then EosStore is expected to become “APP Store” in the future.</p> <p><img src="https://images.eos.store/eos-go-2.jpg" width="2544" height="1564"/></p> <p>It could be noted that EosStore also got 8 checkmarks in the Report and ranked top comprehensively. BlockData published a ranking table named as” Top 10 BP Candidates in China” several days before showing that EosStore took a leading role among all other competitors.</p> <p><img src="https://images.eos.store/eos-go-3.jpg" width="1284" height="1888"/></p> <p>As a black horse becoming a blockbuster in the final stage, EosStore kept a high profile on announcing its candidacy and its fund initially. Later, the team showed its solid technical reserve, its belief in EOS ecosystem and efforts to preserve its development. All theses things made the author review the meaning of EOS held in hand. From the perspective of a traditional investor, EosStore could be regarded as a perfect BP for its position on the initial intention of EOS ecosystem and its plan for future development, plus the Store as its blackout, a closed loop trinity developing mode and superior technical strength and capital.</p> <p>We could see this EOS BPCs competition from two aspects: on one hand, all candidates run for one of 21 BPs, which depends on candidate’s comprehensive strength, influence, initial desire and ultimate goal; on the other hand, the total strength of these 21 BPs will determine the direction of ecological development of EOS.</p> <p>Mostly, a person is born with a liking of profits, thus some BP candidates organized such activities as dividend and airdrops for this election. In author’s view, a BP without enough strength will undoubtedly lead to the collapse of whole EOS ecosystem. If that do happen, then the EOS will be valueless.</p> <p>In order to appreciate the value of your EOS, keep a somber mind, pay more attention to and vote for those candidates like EosStore who really concern about the EOS ecosystem.</p> <p><br></p> <p><img src="https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need"/><img src="https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400"/><img src="https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need"/></p> <p>Email: [email protected] </p> <p>Website: <a href="http://www.eos.store/">http://www.eos.store</a> </p> <p>Twitter: <a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a> </p> <p>Github: <a href="https://github.com/eosstore">https://github.com/eosstore</a> </p> <p>Eosgo: <a href="https://steemit.com/@eos.store">https://steemit.com/@eos.store</a></p> <p>Telegram: <a href="https://t.me/StoreEos">https://t.me/StoreEos</a></p> </html>
json metadata	{"tags":["eos","bp","election"],"image":["https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmVzxVgPGboiGAsAUbSszkXchoLFyBG1zbySsLrNXJuM1C","https://img.jinse.com/806767_image3.png","https://images.eos.store/eos-go-1.jpg","https://images.eos.store/eos-go-2.jpg","https://images.eos.store/eos-go-3.jpg","https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need","https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400"],"links":["https://steemit.com/eos/@eosgo/block-producer-candidate-report-9-may-16-2018","http://www.eos.store/","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22674981/Trx aad456013c8b04496c4acedee756fa4384e840b7

View Raw JSON Data

{
  "trx_id": "aad456013c8b04496c4acedee756fa4384e840b7",
  "block": 22674981,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-23T06:35:45",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "eos.store",
      "permlink": "the-second-half-of-eos-bp-election-a-real-competition-among-all-8-check-mark-winners",
      "title": "The Second Half of EOS BP Election: A Real Competition Among All 8 Check-mark Winners",
      "body": "<html>\n<blockquote>https://steemit.com/eos/@eosgo/block-producer-candidate-report-9-may-16-2018</blockquote>\n<p><img src=\"https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmVzxVgPGboiGAsAUbSszkXchoLFyBG1zbySsLrNXJuM1C\" width=\"850\" height=\"300\"/></p>\n<p>On May 16th (UTC Time), EOS GO published the Block Producer Candidates Report #9, showing 41 new block producer candidates, the totality of global BPCs, and test scores of all of them. Candidates who won 8 checkmarks all released this good news to show their competence.</p>\n<p>Only 10 days left before EOS MainNet launch means that this BP competition is turn to the second half and its ending is coming. At present, the situation of this BP election is just like the sea, calm on its surface while simmering in depth.</p>\n<p><img src=\"https://img.jinse.com/806767_image3.png\" width=\"600\" height=\"400\"/></p>\n<p>Nowadays, hotspot topics about EOS are non-stop, with EOS Block Producer Show sponsored by Huobi Pool in early days and EOS Global BP Summit on May 19th in Shanghai. The Shanghai summit got many well-known BP candidates and famous people in digital currency field together, including BPCs as EOS Gravity, EOS Cannon, and EosStore and stars like Gongming and Li Xiaolai, which made EOS become hotly discussed again.</p>\n<p><br></p>\n<p><code>What does 8 checkmarks mean for the election?</code></p>\n<p><img src=\"https://images.eos.store/eos-go-1.jpg\" width=\"2552\" height=\"1152\"/></p>\n<p>Seriously, as 8 criteria for EOS.IO to evaluate all BPCs, 8 checkmarks contain public presence, ID on Steemit, Tech plans, scaling, community, telegram+testnet, BP roadmap and position on dividend. A candidate passing all these criteria means it is quite well-prepared and accepted by EOS.IO.</p>\n<p>Comprehensively, there are nearly 100 candidates winning 8 checkmarks, while the number of BPs is only 21. BP election will be a fierce competition among these teams on all-round strength.</p>\n<p>What about competitions among these famous leading candidates in China？As EOS holders, how to follow up the development of &nbsp;EOS? How to do with their votes? All these issues should be concerned by EOS holders, especially at the late stage of the election.</p>\n<p><br></p>\n<p><code>Who will win the second half competition?</code></p>\n<p><br></p>\n<p>EOS is a block chain operation system based on decentralized applications, the features of which determine that candidate team could select their roles from protector, developer and investor during the ecosystem construction process. A protector is set to guarantee the stable operation of the public chain; A developer plays a role in introducing development teams and incubating them; while investors mostly use their fund to support the sustainable development of the ecosystem and make it live and full of energy.</p>\n<p>OracleChain, highlighting technology, tends to be as a protector to support EOS ecosystem in hardware, sustaining the stable operation and competence of the public chain.</p>\n<p>Boasting about a community with over 30,000 members, HelloEOS is good at community operating and marketing. It is reported that HelloEOS, inclined to be as a developer and also a protector, has a professional team responsible for reviewing and incubating DApp development.</p>\n<p>As a community based candidate, EOS Cannon is the same with EOS Gravity on community scale and both of them incline to become investors.</p>\n<p>Huobi is an all-rounder who has a big plan. At block producer summit on May 19th, it declared to establish a platform gathering all BP candidates, making it easier for EOS holders to follow up dynamics of all BPCs.</p>\n<p>EosStore is a new comer. Although it announced to focus on the practical use of commercial scale applications, its 8-digit EOS incubation fund made it more like a investor. However, accompanied with various kinds of online and offline activities, EosStore has the tendency to become an all-rounder.</p>\n<p>Lu Haifeng, the founder of EosStore, expressed that EosStore’s announcement of running for BP election at the late stage was not an abrupt decision. The team has always been preparing at previous stages, including single node test, whole testnet and operation and development of DApps on testnet. EosStore would not announce its candidacy before it accumulated its technical storage and technology strength and built its whole testnet. EosStore’s operation mode based on EOS ecosystem has been clearly defined. A closed loop ecosystem with a fund, a community and a DApp store being three in one will be created.</p>\n<p>As for why the team chose EosStore as its name, Lu Haifeng mentioned that they understand and support BM’s original intention, which is focusing on the practical use of commercial scale applications and incubating, investing and serving developers in the whole ecosystem. For easier understanding, nowadays most people use products of Apple Inc. , while the first and foremost one for the whole Apple ecosystem is its APP Store. If we say “EOS ecosystem” will be same with the “Apple ecosystem”, then EosStore is expected to become “APP Store” in the future.</p>\n<p><img src=\"https://images.eos.store/eos-go-2.jpg\" width=\"2544\" height=\"1564\"/></p>\n<p>It could be noted that EosStore also got 8 checkmarks in the Report and ranked top comprehensively. BlockData published a ranking table named as” Top 10 BP Candidates in China” several days before showing that EosStore took a leading role among all other competitors.</p>\n<p><img src=\"https://images.eos.store/eos-go-3.jpg\" width=\"1284\" height=\"1888\"/></p>\n<p>As a black horse becoming a blockbuster in the final stage, EosStore kept a high profile on announcing its candidacy and its fund initially. Later, the team showed its solid technical reserve, its belief in EOS ecosystem and efforts to preserve its development. All theses things made the author review the meaning of EOS held in hand. From the perspective of a traditional investor, EosStore could be regarded as a perfect BP for its position on the initial intention of EOS ecosystem and its plan for future development, plus the Store as its blackout, a closed loop trinity developing mode and superior technical strength and capital.</p>\n<p>We could see this EOS BPCs competition from two aspects: on one hand, all candidates run for one of 21 BPs, which depends on candidate’s comprehensive strength, influence, initial desire and ultimate goal; on the other hand, the total strength of these 21 BPs will determine the direction of ecological development of EOS.</p>\n<p>Mostly, a person is born with a liking of profits, thus some BP candidates organized such activities as dividend and airdrops for this election. In author’s view, a BP without enough strength will undoubtedly lead to the collapse of whole EOS ecosystem. If that do happen, then the EOS will be valueless.</p>\n<p>In order to appreciate the value of your EOS, keep a somber mind, pay more attention to and vote for those candidates like EosStore who really concern about the EOS ecosystem.</p>\n<p><br></p>\n<p><img src=\"https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need\"/><img src=\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\"/><img src=\"https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need\"/></p>\n<p>Email: [email protected]&nbsp;</p>\n<p>Website: <a href=\"http://www.eos.store/\">http://www.eos.store</a>&nbsp;</p>\n<p>Twitter: <a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a>&nbsp;</p>\n<p>Github: <a href=\"https://github.com/eosstore\">https://github.com/eosstore</a>&nbsp;</p>\n<p>Eosgo: <a href=\"https://steemit.com/@eos.store\">https://steemit.com/@eos.store</a></p>\n<p>Telegram: <a href=\"https://t.me/StoreEos\">https://t.me/StoreEos</a></p>\n</html>",
      "json_metadata": "{\"tags\":[\"eos\",\"bp\",\"election\"],\"image\":[\"https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmVzxVgPGboiGAsAUbSszkXchoLFyBG1zbySsLrNXJuM1C\",\"https://img.jinse.com/806767_image3.png\",\"https://images.eos.store/eos-go-1.jpg\",\"https://images.eos.store/eos-go-2.jpg\",\"https://images.eos.store/eos-go-3.jpg\",\"https://steemit.com/eosstore/@eos.store/in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need\",\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\"],\"links\":[\"https://steemit.com/eos/@eosgo/block-producer-candidate-report-9-may-16-2018\",\"http://www.eos.store/\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storereceived 0.097 SBD, 0.040 SP author reward for @eos.store / eos-store-block-producer-report-roadmap-and-views-on-dividends

2018/05/21 13:01:00 UTC

22,625,097|virtual

author	eos.store
permlink	eos-store-block-producer-report-roadmap-and-views-on-dividends
sbd payout	0.097 SBD
steem payout	0.000 STEEM
vesting payout	65.099412 VESTS
Transaction Info	Block #22625097/Virtual Operation #22

View Raw JSON Data

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 22625097,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 22,
  "timestamp": "2018-05-21T13:01:00",
  "op": [
    "author_reward",
    {
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report-roadmap-and-views-on-dividends",
      "sbd_payout": "0.097 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "65.099412 VESTS"
    }
  ]
}

leewilliamsonreplied to @eos.store / re-eosstore-in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need-20180521t065250016z

2018/05/21 06:52:48 UTC

22,617,736|0102d03

parent author	eos.store
parent permlink	in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need
author	leewilliamson
permlink	re-eosstore-in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need-20180521t065250016z
title	fossbot voter comment
body	@therealwolf 's created platform smartsteem scammed my post this morning (mothersday) that was supposed to be for an Abused Childrens Charity. Dude literally stole from abused children that don't have mothers ... on mothersday. https://steemit.com/steemit/@prometheusrisen/beware-of-smartsteem-scam And the reason why is because @therealwolf is disgusting slimy pedophile that enjoys abusing kids. Here's proof of him upvoting child porn on the steemit blockchain. bigbadwolf indeed. http://i.imgur.com/rWlqa1M.png And the reason why is because @therealwolf is disgusting slimy pedophile that enjoys abusing kids. Here's proof of him upvoting child porn on the steemit blockchain. bigbadwolf indeed. http://i.imgur.com/rWlqa1M.png
json metadata	{}
Transaction Info	Block #22617736/Trx 0102d031b8d26ab7aff4e34296c736849a3fa2e2

View Raw JSON Data

{
  "trx_id": "0102d031b8d26ab7aff4e34296c736849a3fa2e2",
  "block": 22617736,
  "trx_in_block": 45,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-21T06:52:48",
  "op": [
    "comment",
    {
      "parent_author": "eos.store",
      "parent_permlink": "in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need",
      "author": "leewilliamson",
      "permlink": "re-eosstore-in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need-20180521t065250016z",
      "title": "fossbot voter comment",
      "body": "@therealwolf 's created platform smartsteem scammed my post this morning (mothersday) that was supposed to be for an Abused Childrens Charity.  Dude literally stole from abused children that don't have mothers ... on mothersday.  \r\n\r\nhttps://steemit.com/steemit/@prometheusrisen/beware-of-smartsteem-scam\r\n\r\nAnd the reason why is because @therealwolf is disgusting slimy pedophile that enjoys abusing kids.  Here's proof of him upvoting child porn on the steemit blockchain.  bigbadwolf indeed.  http://i.imgur.com/rWlqa1M.png\r\n\r\nAnd the reason why is because @therealwolf is disgusting slimy pedophile that enjoys abusing kids.  Here's proof of him upvoting child porn on the steemit blockchain.  bigbadwolf indeed.  http://i.imgur.com/rWlqa1M.png",
      "json_metadata": "{}"
    }
  ]
}

eos.storepublished a new post: in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need

2018/05/21 06:44:06 UTC

22,617,562|d9eb03b

parent author
parent permlink	eosstore
author	eos.store
permlink	in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need
title	In the eyes of a block chain geek, what technology does EOS BP need?
body	<html> <blockquote>EosStore</blockquote> <p><img src="https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/e970a8fd388f65666de352c29feeb73f.png?x-oss-process=style/size_lg" width="1200" height="669"/></p> <p>On May 20th, a salon themed on “In the eyes of a block chain geek, what technology does EOS BP need?” was held by EosStore at Garage Café at Z-innoway, the Holy Land for many entrepreneurs. During this sharing, Vincent Luo, a partner of EOS Capital and marketing director of EosStore, made his speech on the core expectation of EosStore as realizing the practical use of commercial-scale Dapps. Simon Wang, responsible for the technology of EosStore, shared the technical preparations EosStore had done for this BP election.</p> <p>Now there are only less than half a month before launching EOS MainNet. Meanwhile, global teams kept a high profile on the participation of 21 BPs election. Accordingly, in early May, at least 44 BP candidates come from China or their core team members are ethnic Chinese, which accounts for a half of the number of qualified candidates. We are proud to say EosStore came out on top at all criteria among all EOS BP candidates.  </p> <p><img src="https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/745d5c5b7acd6d9bc72a2639d9ab3407.png?x-oss-process=style/size_lg" width="1200" height="572"/></p> <p><strong>Vincent Luo, Marketing director of EosStore and a Partner of Eos Capital</strong></p> <p>EosStore team is comprised of block chain technology enthusiasts and firm believers of EOS, as Vincent expressed, “to realize the practical use of commercial-scale DApps” is the core expectation of EosStore. The team is committed to building a decentralized community featuring freedom, openness, equality and mutual-trust. Meanwhile, as a candidate for BP, EosStore has made its plan for creating an ecology closed loop with a fund, a DApp store and a community being three in one. The fund aims to support EOS to incubate, invest and service for all developers in Mainland China. That means the qualified DApp developers will be selected and gain investment firstly after voted by all community members. Besides, development projects of DApp will be able to be presented and distributed at EosStore. The fund, DApp store and the community of EOS holders will benefit, support and promote growth mutually. </p> <p>As a partner of Garage Café previously, Vincent comparing its operating philosophy to that of EosStore,” Garage Café was the most influential community in entrepreneur fields in early years. Why? The reason is that there were many people helping others while asking for nothing and enjoying such happiness. That all people spare no effort to help others is the community spirit. It is this kind of community we are dedicated to creating.”</p> <p><img src="https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/3c3c2f4283cbfbd773f121eec53948bd.png?x-oss-process=style/size_lg" width="1200" height="634"/></p> <p><strong>Simon Wang, responsible for EosStore technology </strong></p> <p>Later, Simon, responsible for EosStore technically, shared his opinion on block chain and EOS technology and presented technology preparations of EosStore at present.  Simon has full participation in the R&D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Besides, he also has done more research on artificial intelligence and devotes himself into the block chain technology now.</p> <p>In Simon’s view, “the Impossible Trinity” is common in block chain technology, which means it is impossible to have efficiency, security and decentralization at same time. A centralized processing will bring about a high TPS, which means a high TPS must be accompanied with the loss of decentralization. Under this context, Simon demonstrated a “EOS Could Plan” put forward by EosStore technology team. The Plan refers to separating the whole EOS service into numerous micro-services, which is the only way to achieve million-level TPS. Besides, Simon showed EosStore’s preparations for DDOS attack after launching EOS MainNet.</p> <p><img src="https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/560bc28dad7eca06f8a8413c77150ad2.png?x-oss-process=style/size_lg" width="1200" height="723"/></p> <p><strong>Simon communicating with attendees</strong></p> <p>During question time after Simon’s talking, attendees put forward various questions about EOS and all received thorough explanation given by Simon. The end of the activity could not stop the zest of attendees who continued surrounding and communicating with Simon. The crowd and their questions showed that block chain and EOS are still hotspots. Being late to success is common and what matter most is whether you have fully prepared! Block chain technology and EOS are now both at their beginning stages and EosStore is glad to embrace the new unknown era with you all!</p> <p><br></p> <p><br></p> <p><br></p> <p><img src="https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400" width="969" height="318"/></p> <p><br></p> <p>Email: [email protected] </p> <p>Website: http://www.eos.store </p> <p>Twitter: https://twitter.com/StoreEos </p> <p>Github: https://github.com/eosstore </p> <p>Eosgo: https://steemit.com/@eos.store</p> <p>Telegram: https://t.me/StoreEos</p> </html>
json metadata	{"tags":["eosstore","salon","eosbp"],"image":["https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/e970a8fd388f65666de352c29feeb73f.png?x-oss-process=style/size_lg","https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/745d5c5b7acd6d9bc72a2639d9ab3407.png?x-oss-process=style/size_lg","https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/3c3c2f4283cbfbd773f121eec53948bd.png?x-oss-process=style/size_lg","https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/560bc28dad7eca06f8a8413c77150ad2.png?x-oss-process=style/size_lg","https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400"],"links":["http://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22617562/Trx d9eb03b28a28f810b188d61fd71227dd26a9447b

View Raw JSON Data

{
  "trx_id": "d9eb03b28a28f810b188d61fd71227dd26a9447b",
  "block": 22617562,
  "trx_in_block": 34,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-21T06:44:06",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eosstore",
      "author": "eos.store",
      "permlink": "in-the-eyes-of-a-block-chain-geek-what-technology-does-eos-bp-need",
      "title": "In the eyes of a block chain geek, what technology does EOS BP need?",
      "body": "<html>\n<blockquote>EosStore</blockquote>\n<p><img src=\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/e970a8fd388f65666de352c29feeb73f.png?x-oss-process=style/size_lg\" width=\"1200\" height=\"669\"/></p>\n<p>On May 20th, a salon themed on “In the eyes of a block chain geek, what technology does EOS BP need?” was held by EosStore at Garage Café at Z-innoway, the Holy Land for many entrepreneurs. During this sharing, Vincent Luo, a partner of EOS Capital and marketing director of EosStore, made his speech on the core expectation of EosStore as realizing the practical use of commercial-scale Dapps. Simon Wang, responsible for the technology of EosStore, shared the technical preparations EosStore had done for this BP election.</p>\n<p>Now there are only less than half a month before launching EOS MainNet. Meanwhile, global teams kept a high profile on the participation of 21 BPs election. Accordingly, in early May, at least 44 BP candidates come from China or their core team members are ethnic Chinese, which accounts for a half of the number of qualified candidates. We are proud to say EosStore came out on top at all criteria among all EOS BP candidates. &nbsp;</p>\n<p><img src=\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/745d5c5b7acd6d9bc72a2639d9ab3407.png?x-oss-process=style/size_lg\" width=\"1200\" height=\"572\"/></p>\n<p><strong>Vincent Luo, Marketing director of EosStore and a Partner of Eos Capital</strong></p>\n<p>EosStore team is comprised of block chain technology enthusiasts and firm believers of EOS, as Vincent expressed, “to realize the practical use of commercial-scale DApps” is the core expectation of EosStore. The team is committed to building a decentralized community featuring freedom, openness, equality and mutual-trust. Meanwhile, as a candidate for BP, EosStore has made its plan for creating an ecology closed loop with a fund, a DApp store and a community being three in one. The fund aims to support EOS to incubate, invest and service for all developers in Mainland China. That means the qualified DApp developers will be selected and gain investment firstly after voted by all community members. Besides, development projects of DApp will be able to be presented and distributed at EosStore. The fund, DApp store and the community of EOS holders will benefit, support and promote growth mutually.&nbsp;</p>\n<p>As a partner of Garage Café previously, Vincent comparing its operating philosophy to that of EosStore,” Garage Café was the most influential community in entrepreneur fields in early years. Why? The reason is that there were many people helping others while asking for nothing and enjoying such happiness. That all people spare no effort to help others is the community spirit. It is this kind of community we are dedicated to creating.”</p>\n<p><img src=\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/3c3c2f4283cbfbd773f121eec53948bd.png?x-oss-process=style/size_lg\" width=\"1200\" height=\"634\"/></p>\n<p><strong>Simon Wang, responsible for EosStore technology&nbsp;</strong></p>\n<p>Later, Simon, responsible for EosStore technically, shared his opinion on block chain and EOS technology and presented technology preparations of EosStore at present. &nbsp;Simon has full participation in the R&amp;D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Besides, he also has done more research on artificial intelligence and devotes himself into the block chain technology now.</p>\n<p>In Simon’s view, “the Impossible Trinity” is common in block chain technology, which means it is impossible to have efficiency, security and decentralization at same time. A centralized processing will bring about a high TPS, which means a high TPS must be accompanied with the loss of decentralization. Under this context, Simon demonstrated a “EOS Could Plan” put forward by EosStore technology team. The Plan refers to separating the whole EOS service into numerous micro-services, which is the only way to achieve million-level TPS. Besides, Simon showed EosStore’s preparations for DDOS attack after launching EOS MainNet.</p>\n<p><img src=\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/560bc28dad7eca06f8a8413c77150ad2.png?x-oss-process=style/size_lg\" width=\"1200\" height=\"723\"/></p>\n<p><strong>Simon communicating with attendees</strong></p>\n<p>During question time after Simon’s talking, attendees put forward various questions about EOS and all received thorough explanation given by Simon. The end of the activity could not stop the zest of attendees who continued surrounding and communicating with Simon. The crowd and their questions showed that block chain and EOS are still hotspots. Being late to success is common and what matter most is whether you have fully prepared! Block chain technology and EOS are now both at their beginning stages and EosStore is glad to embrace the new unknown era with you all!</p>\n<p><br></p>\n<p><br></p>\n<p><br></p>\n<p><img src=\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\" width=\"969\" height=\"318\"/></p>\n<p><br></p>\n<p>Email: [email protected]&nbsp;</p>\n<p>Website: http://www.eos.store&nbsp;</p>\n<p>Twitter: https://twitter.com/StoreEos&nbsp;</p>\n<p>Github: https://github.com/eosstore&nbsp;</p>\n<p>Eosgo: https://steemit.com/@eos.store</p>\n<p>Telegram: https://t.me/StoreEos</p>\n</html>",
      "json_metadata": "{\"tags\":[\"eosstore\",\"salon\",\"eosbp\"],\"image\":[\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/e970a8fd388f65666de352c29feeb73f.png?x-oss-process=style/size_lg\",\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/745d5c5b7acd6d9bc72a2639d9ab3407.png?x-oss-process=style/size_lg\",\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/3c3c2f4283cbfbd773f121eec53948bd.png?x-oss-process=style/size_lg\",\"https://bihu2001.oss-cn-shanghai.aliyuncs.com/img/560bc28dad7eca06f8a8413c77150ad2.png?x-oss-process=style/size_lg\",\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\"],\"links\":[\"http://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storepublished a new post: block-producer-agreement-discussion-thread-thomasbcox

2018/05/21 06:31:39 UTC

22,617,313|3a110e8

parent author
parent permlink	thomasbcox
author	eos.store
permlink	block-producer-agreement-discussion-thread-thomasbcox
title	Block Producer Agreement Discussion Thread @thomasbcox
body	<html> <blockquote>原文链接：https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread</blockquote> <p><br></p> <p>Here's the text just published by @thomasbcox:</p> <p>这是 @thomasbcox刚刚出版的关于BP需要遵守的规则：</p> <p><br></p> <p>As a Block Producer (BP), I/we promise to:</p> <p>作为一个BP，我/我们承诺：</p> <p><br></p> <p>1.Produce exactly the authorized number of blocks faithfully, accurately, at the appointed time in the rotation</p> <p>1.在指定的时间内，轮流、如实、精准地生产出授权的块数。</p> <p><br></p> <p>2.Never produce and sign two or more blocks with the same block height or block interval</p> <p>2.从不在同一块高或出块间隔内生产并且签名两个或两个以上的块。</p> <p><br></p> <p>3.Never censor governance related transactions such as votes or Arbitration related transactions</p> <p>3.对交易相关的治理，如投票或交易相关的仲裁，绝不进行审查。</p> <p><br></p> <p>4.Only add "good" transactions from the transaction pool to the block</p> <p>4.只把交易池中“优质”的交易添加到块中。</p> <p><br></p> <p>5.Make a good faith effort to include as many "good" transactions as possible to the block without undue discrimination</p> <p>5.尽力将“优质”交易如实放到块中，不得有不必要的歧视。</p> <p><br></p> <p>6.Exclude "bad" transactions from the block, and publish why they were excluded</p> <p>6.把“劣质”的交易从块中剔除，并且公布剔除原因。</p> <p><br></p> <p>7.Show no favoritism among transactions, ordering them in a FIFO fashion or using some other ordering mechanism that is declared publicly in advance, including the default ordering provided by the unmodified software</p> <p>7.不偏袒任何交易，所有交易按FIFO排序，或按之前公开声明的其他一些排序机制，包括未经修改的软件所提供的默认顺序。</p> <p><br></p> <p>8.Refrain from using my/our superior information to "front run" transactions nor enabling anyone else to “front run”</p> <p>8.避免利用我/我们的信息优势来“预先运行”交易，也不要让任何人“预先运行”。</p> <p><br></p> <p>9.Accept as valid any Arbitrator’s order that’s</p> <p>9.接受仲裁人以下任何有效命令：</p> <p><br></p> <p>i. signed by an Arbitrator</p> <p>1）由仲裁人签名</p> <p><br></p> <p>ii. that the chain shows was assigned to a Case,</p> <p>2）链表被分配到一个实例中，</p> <p><br></p> <p>iii. such that the order affects only the Accounts named in that Case, and</p> <p>3）这样一来，该订单只影响到该实例中指定的账户，同时</p> <p><br></p> <p>iv. the Arbitrator is in good standing with their Arbitration Forum, and</p> <p>4）仲裁人遵守其所在仲裁庭的规章，并且</p> <p><br></p> <p>v. the original Transaction that gave rise to the Case names that Arbitration Forum as the venue for dispute resolution</p> <p>5）仲裁庭将原始交易引起的案例域名作为解决争议的场所</p> <p><br></p> <p>10.Only freeze accounts when authorized to do so by a valid Arbitrator’s order</p> <p>10.只有在仲裁人有效命令授权下才能冻结账户。</p> <p><br></p> <p>11.Always file a dispute against myself/ourselves after taking initiative to act on an emergency</p> <p>11.在对紧急情况采取初步行动后，要始终对我自己/我们自己提出异议。</p> <p><br></p> <p>12.Provide at least four (4) public endpoints running full nodes (the Minimum Configuration)</p> <p>12.至少提供4个公共端节点运行全节点（最低配置）</p> <p><br></p> <p>13.Not requesting my/our daily Vote Bonus pay on days when I/we don’t have the Minimum Configuration running, and repaying any Vote Bonus income collected while the Minimum Configuration wasn’t running</p> <p>13.在我/我们没有运行最低配置的日子里，不需要我/我们支付每天的投票奖金，同时在最低配置没有运行时，偿还收集到的一切投票奖金收入。</p> <p><br></p> <p>14.Disclosing all ownership of my/our organization greater than 10%</p> <p>14.公开占我的/我们的组织持有总量超10%的持有人。</p> <p><br></p> <p>15.Not sharing more than 10% ownership with another BP</p> <p>15.不要与其他bp共享超过自己10%的所有权</p> <p><br></p> <p><img src="https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400" width="969" height="318"/></p> <p><br></p> <p>Email: [email protected] </p> <p>Website: http://www.eos.store </p> <p>Twitter: https://twitter.com/StoreEos </p> <p>Github: https://github.com/eosstore </p> <p>Eosgo: https://steemit.com/@eos.store</p> <p>Telegram: https://t.me/StoreEos</p> </html>
json metadata	{"tags":["thomasbcox","block","producer"],"users":["thomasbcox"],"image":["https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400"],"links":["https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread","http://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22617313/Trx 3a110e8dab9bbd3f7eeda1a7a7ea8065ea3db9a9

View Raw JSON Data

{
  "trx_id": "3a110e8dab9bbd3f7eeda1a7a7ea8065ea3db9a9",
  "block": 22617313,
  "trx_in_block": 42,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-21T06:31:39",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "thomasbcox",
      "author": "eos.store",
      "permlink": "block-producer-agreement-discussion-thread-thomasbcox",
      "title": "Block Producer Agreement Discussion Thread  @thomasbcox",
      "body": "<html>\n<blockquote>原文链接：https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread</blockquote>\n<p><br></p>\n<p>Here's the text just published by&nbsp;@thomasbcox:</p>\n<p>这是&nbsp;@thomasbcox刚刚出版的关于BP需要遵守的规则：</p>\n<p><br></p>\n<p>As a Block Producer (BP), I/we promise to:</p>\n<p>作为一个BP，我/我们承诺：</p>\n<p><br></p>\n<p>1.Produce exactly the authorized number of blocks faithfully, accurately, at the appointed time in the rotation</p>\n<p>1.在指定的时间内，轮流、如实、精准地生产出授权的块数。</p>\n<p><br></p>\n<p>2.Never produce and sign two or more blocks with the same block height or block interval</p>\n<p>2.从不在同一块高或出块间隔内生产并且签名两个或两个以上的块。</p>\n<p><br></p>\n<p>3.Never censor governance related transactions such as votes or Arbitration related transactions</p>\n<p>3.对交易相关的治理，如投票或交易相关的仲裁，绝不进行审查。</p>\n<p><br></p>\n<p>4.Only add \"good\" transactions from the transaction pool to the block</p>\n<p>4.只把交易池中“优质”的交易添加到块中。</p>\n<p><br></p>\n<p>5.Make a good faith effort to include as many \"good\" transactions as possible to the block without undue discrimination</p>\n<p>5.尽力将“优质”交易如实放到块中，不得有不必要的歧视。</p>\n<p><br></p>\n<p>6.Exclude \"bad\" transactions from the block, and publish why they were excluded</p>\n<p>6.把“劣质”的交易从块中剔除，并且公布剔除原因。</p>\n<p><br></p>\n<p>7.Show no favoritism among transactions, ordering them in a FIFO fashion or using some other ordering mechanism that is declared publicly in advance, including the default ordering provided by the unmodified software</p>\n<p>7.不偏袒任何交易，所有交易按FIFO排序，或按之前公开声明的其他一些排序机制，包括未经修改的软件所提供的默认顺序。</p>\n<p><br></p>\n<p>8.Refrain from using my/our superior information to \"front run\" transactions nor enabling anyone else to “front run”</p>\n<p>8.避免利用我/我们的信息优势来“预先运行”交易，也不要让任何人“预先运行”。</p>\n<p><br></p>\n<p>9.Accept as valid any Arbitrator’s order that’s</p>\n<p>9.接受仲裁人以下任何有效命令：</p>\n<p><br></p>\n<p>i. signed by an Arbitrator</p>\n<p>1）由仲裁人签名</p>\n<p><br></p>\n<p>ii. that the chain shows was assigned to a Case,</p>\n<p>2）链表被分配到一个实例中，</p>\n<p><br></p>\n<p>iii. such that the order affects only the Accounts named in that Case, and</p>\n<p>3）这样一来，该订单只影响到该实例中指定的账户，同时</p>\n<p><br></p>\n<p>iv. the Arbitrator is in good standing with their Arbitration Forum, and</p>\n<p>4）仲裁人遵守其所在仲裁庭的规章，并且</p>\n<p><br></p>\n<p>v. the original Transaction that gave rise to the Case names that Arbitration Forum as the venue for dispute resolution</p>\n<p>5）仲裁庭将原始交易引起的案例域名作为解决争议的场所</p>\n<p><br></p>\n<p>10.Only freeze accounts when authorized to do so by a valid Arbitrator’s order</p>\n<p>10.只有在仲裁人有效命令授权下才能冻结账户。</p>\n<p><br></p>\n<p>11.Always file a dispute against myself/ourselves after taking initiative to act on an emergency</p>\n<p>11.在对紧急情况采取初步行动后，要始终对我自己/我们自己提出异议。</p>\n<p><br></p>\n<p>12.Provide at least four (4) public endpoints running full nodes (the Minimum Configuration)</p>\n<p>12.至少提供4个公共端节点运行全节点（最低配置）</p>\n<p><br></p>\n<p>13.Not requesting my/our daily Vote Bonus pay on days when I/we don’t have the Minimum Configuration running, and repaying any Vote Bonus income collected while the Minimum Configuration wasn’t running</p>\n<p>13.在我/我们没有运行最低配置的日子里，不需要我/我们支付每天的投票奖金，同时在最低配置没有运行时，偿还收集到的一切投票奖金收入。</p>\n<p><br></p>\n<p>14.Disclosing all ownership of my/our organization greater than 10%</p>\n<p>14.公开占我的/我们的组织持有总量超10%的持有人。</p>\n<p><br></p>\n<p>15.Not sharing more than 10% ownership with another BP</p>\n<p>15.不要与其他bp共享超过自己10%的所有权</p>\n<p><br></p>\n<p><img src=\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\" width=\"969\" height=\"318\"/></p>\n<p><br></p>\n<p>Email: [email protected]&nbsp;</p>\n<p>Website: http://www.eos.store&nbsp;</p>\n<p>Twitter: https://twitter.com/StoreEos&nbsp;</p>\n<p>Github: https://github.com/eosstore&nbsp;</p>\n<p>Eosgo: https://steemit.com/@eos.store</p>\n<p>Telegram: https://t.me/StoreEos</p>\n</html>",
      "json_metadata": "{\"tags\":[\"thomasbcox\",\"block\",\"producer\"],\"users\":[\"thomasbcox\"],\"image\":[\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\"],\"links\":[\"https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread\",\"http://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storepublished a new post: eos-store-block-producer-report-roadmap-and-views-on-dividends

2018/05/18 03:39:45 UTC

22,527,489|b6b3931

parent author
parent permlink	roadmap
author	eos.store
permlink	eos-store-block-producer-report-roadmap-and-views-on-dividends
title	EOS.STORE Block Producer Report --Roadmap and Views on Dividends
body	@@ -1494,25 +1494,17 @@ 3%3E%0A%3C -h3%3ELu Haifeng%3C/h3 +p%3E%3Cbr%3E%3C/p %3E%0A%3Cp @@ -1604,587 +1604,6110 @@ %3Ch3%3E -Cruze Guo%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EHu Xiangwei%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EWang Xiaoxuan%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ELiu Wenbin%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EWang Chengsong%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/ +Lu Haifeng    Project sponsor of EosStore and partner of EosStore Capital%3C/h3%3E%0A%3Cp%3EMr. Lu, graduating from School of Economics and Management of Tsinghua University with finance MBA as his major, invested EOS token in its early stages. He is one of the first entrepreneurs based in Garage Cafe, an enthusiast of block chain technology and EOS believer holding over 7-digit  EOS token.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ECruze Guo %3C/h3%3E%0A%3Cp%3EAn an untypical developer, Cruze graduated from College of Hydrology and Water Resources of Hohai University in Nanjing. He joined Rising, a forerunner of antivirus software company in China after moving to Beijing alone. 5 years of experience in Rising brought him a well-paid job in Tencent, in which he witnessed the %E2%80%9C3Q War%E2%80%9D, a well-known battle between Tencent and 360. He also worked for other Internet giants like Baidu. Mining 50 bitcoins was his first contact with block chain, but his unintentional behavior also made him miss his first pot of gold. %3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EHu Xiangwei%3C/h3%3E%0A%3Cp%3EGranted his master degree of Business Administration from Beihang University, Hu Xiangwei has 18 years of experience in software development and management, successively engaged in developing and managing of e-commerce, e-government, Internet, platform products, mobile Internet, and Internet financial products. He was a senior director at Naver China previously responsible for the development of platform products, including internal development framework, message queue, CUBRID database, middleware, PB-level big data analytic platform, performance testing tools and system monitoring tools. Besides, he was once responsible for developing, launching and operating of a financial product featuring 100 million data and high-concurrence. At present, he has an in-depth research in blockchain technology, leading a team to developing ICO platform and digital currency exchange. %3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EAlex%3C/h3%3E%0A%3Cp%3EAlex is a senior blockchain analyst in EosStore and an excellent translator at dockone community. Graduated from Beijing Institute of Technology majoring in communication engineering, Alex has been working in IT area for 15 years, engaged in the development of firewall first and then turn to 4A security products. He participated in designing some data backup products like netbackup puredisk velocity, when working for Symantec(Beijing) as senior R&D engineer. Alex, making a connection with container technology in 2015, is one of the first users and participators of cloud foundry and open shift. Besides, he worked as paas platform CTO for Grow Force.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ELiu Wenbin%3C/h3%3E%0A%3Cp%3EGranted a master degree of software engineer from Beihang University, Liu Wenbin has 7 years of experiences in Internet software development, skilled in such areas as digital payment and DevOps. He once worked as senior R&D engineer for Sony Mobile China first and then for Beijing Globallink Computer Technology. Besides leading R&D and implementation of an offline game platform (over ten thousands of participants) based on Android plus Java, he also built personal websites, microsite and WeChat official accounts. From cutting-edge technology like 3D space identity to R&D and implementation in traditional software industry, Liu Wenbin has explored both of them.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch2%3ESimon%3C/h2%3E%0A%3Cp%3ESimon has full participation in the R&D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Proficient in 5 more programming languages, Simon has built a micro e-commerce system by himself. Besides, he also has done more research on artificial intelligence.Now, Simon devotes himself into the blockchain technology and the subversive revolution it will bring about.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EJJ   Partner of Eos.Store Fund%3C/p%3E%0A%3Cp%3EAs an early supporter of EOS, JJ worked in investment & Internet areas for 5 years. She was the Chinese representative of a EB5 project responsible for the recruitment of its second phase in mainland China. As a senior marketing consultant of MLN Singapore, JJ once successfully helped dozens of entrepreneurs find perfect resource match. Besides, she also worked for Red Castle as its CMO, promoting the communication between China%E2%80%99s startup teams and startupers from such six countries as the UK, the US and Chile.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EJane Senior consultant of EosStore%3C/p%3E%0A%3Cp%3EJane has 3 years of experience in Internet area. She dedicated herself into the research of such fields as business model and brand consultancy and planning, taking advantage of being the project manager of Garage Cafe contacting with thousands of startup projects from various fields. Jane paid her attention to block chain since the second half of 2017.%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EAmy Senior consultant of EosStore%3C/p%3E%0A%3Cp%3EAmy has been working in Internet area for over 3 years with new media marketing as her focus, excelling at hotspot marketing, event marketing and WOM media marketing. She has successfully operated a top 50 new media account among all blockchain-related accounts, with only several months after her first contact with blockchain.%3C/p%3E%0A%3Cp%3E%3Cbr %3E%3C/p
json metadata	{"tags":["roadmap","views","and","dividends"],"users":["eosgo"],"image":["https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]","https://www.eos.store/static/img/person/[email protected]"],"links":["https://busy.org/@eosgo/announcement-grading-criteria-for-eos-block-producers-in-march-7-report","https://steemit.com/eos/@eosgo/two-new-criteria-for-eos-block-producer-candidates-in-report-9","https://www.eos.store ","https://github.com/eosstore ","https://t.me/StoreEos ","https://twitter.com/StoreEos","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22527489/Trx b6b393171996905a1777742698baaf142c376c86

View Raw JSON Data

{
  "trx_id": "b6b393171996905a1777742698baaf142c376c86",
  "block": 22527489,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-18T03:39:45",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "roadmap",
      "author": "eos.store",
      "permlink": "eos-store-block-producer-report-roadmap-and-views-on-dividends",
      "title": "EOS.STORE Block Producer Report --Roadmap and Views on Dividends",
      "body": "@@ -1494,25 +1494,17 @@\n 3%3E%0A%3C\n-h3%3ELu Haifeng%3C/h3\n+p%3E%3Cbr%3E%3C/p\n %3E%0A%3Cp\n@@ -1604,587 +1604,6110 @@\n %3Ch3%3E\n-Cruze Guo%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EHu Xiangwei%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EWang Xiaoxuan%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ELiu Wenbin%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EWang Chengsong%3C/h3%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/\n+Lu Haifeng &nbsp;&nbsp;&nbsp;Project sponsor of EosStore and partner of EosStore Capital%3C/h3%3E%0A%3Cp%3EMr. Lu, graduating from School of Economics and Management of Tsinghua University with finance MBA as his major, invested EOS token in its early stages. He is one of the first entrepreneurs based in Garage Cafe, an enthusiast of block chain technology and EOS believer holding over 7-digit &nbsp;EOS token.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ECruze Guo&nbsp;%3C/h3%3E%0A%3Cp%3EAn an untypical developer, Cruze graduated from College of Hydrology and Water Resources of Hohai University in Nanjing. He joined Rising, a forerunner of antivirus software company in China after moving to Beijing alone. 5 years of experience in Rising brought him a well-paid job in Tencent, in which he witnessed the %E2%80%9C3Q War%E2%80%9D, a well-known battle between Tencent and 360. He also worked for other Internet giants like Baidu. Mining 50 bitcoins was his first contact with block chain, but his unintentional behavior also made him miss his first pot of gold.&nbsp;%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EHu Xiangwei%3C/h3%3E%0A%3Cp%3EGranted his master degree of Business Administration from Beihang University, Hu Xiangwei has 18 years of experience in software development and management, successively engaged in developing and managing of e-commerce, e-government, Internet, platform products, mobile Internet, and Internet financial products. He was a senior director at Naver China previously responsible for the development of platform products, including internal development framework, message queue, CUBRID database, middleware, PB-level big data analytic platform, performance testing tools and system monitoring tools. Besides, he was once responsible for developing, launching and operating of a financial product featuring 100 million data and high-concurrence. At present, he has an in-depth research in blockchain technology, leading a team to developing ICO platform and digital currency exchange.&nbsp;%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3EAlex%3C/h3%3E%0A%3Cp%3EAlex is a senior blockchain analyst in EosStore and an excellent translator at dockone community. Graduated from Beijing Institute of Technology majoring in communication engineering, Alex has been working in IT area for 15 years, engaged in the development of firewall first and then turn to 4A security products. He participated in designing some data backup products like netbackup puredisk velocity, when working for Symantec(Beijing) as senior R&amp;D engineer. Alex, making a connection with container technology in 2015, is one of the first users and participators of cloud foundry and open shift. Besides, he worked as paas platform CTO for Grow Force.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch3%3ELiu Wenbin%3C/h3%3E%0A%3Cp%3EGranted a master degree of software engineer from Beihang University, Liu Wenbin has 7 years of experiences in Internet software development, skilled in such areas as digital payment and DevOps. He once worked as senior R&amp;D engineer for Sony Mobile China first and then for Beijing Globallink Computer Technology. Besides leading R&amp;D and implementation of an offline game platform (over ten thousands of participants) based on Android plus Java, he also built personal websites, microsite and WeChat official accounts. From cutting-edge technology like 3D space identity to R&amp;D and implementation in traditional software industry, Liu Wenbin has explored both of them.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22512%22 height=%22512%22/%3E%3C/p%3E%0A%3Ch2%3ESimon%3C/h2%3E%0A%3Cp%3ESimon has full participation in the R&amp;D and architecture of BP level storage systems, cloud computing platforms and e-commerce system during his 9 years of experience in Internet area. He has dedicated himself to micro service, container clusters and CI/CD for a long time. Proficient in 5 more programming languages, Simon has built a micro e-commerce system by himself. Besides, he also has done more research on artificial intelligence.Now, Simon devotes himself into the blockchain technology and the subversive revolution it will bring about.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EJJ &nbsp;&nbsp;Partner of Eos.Store Fund%3C/p%3E%0A%3Cp%3EAs an early supporter of EOS, JJ worked in investment &amp; Internet areas for 5 years. She was the Chinese representative of a EB5 project responsible for the recruitment of its second phase in mainland China. As a senior marketing consultant of MLN Singapore, JJ once successfully helped dozens of entrepreneurs find perfect resource match. Besides, she also worked for Red Castle as its CMO, promoting the communication between China%E2%80%99s startup teams and startupers from such six countries as the UK, the US and Chile.%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EJane Senior consultant of EosStore%3C/p%3E%0A%3Cp%3EJane has 3 years of experience in Internet area. She dedicated herself into the research of such fields as business model and brand consultancy and planning, taking advantage of being the project manager of Garage Cafe contacting with thousands of startup projects from various fields. Jane paid her attention to block chain since the second half of 2017.%3C/p%3E%0A%3Cp%3E%3Cimg src=%22https://www.eos.store/static/img/person/[email protected]%22 width=%22520%22 height=%22520%22/%3E%3C/p%3E%0A%3Cp%3EAmy Senior consultant of EosStore%3C/p%3E%0A%3Cp%3EAmy has been working in Internet area for over 3 years with new media marketing as her focus, excelling at hotspot marketing, event marketing and WOM media marketing. She has successfully operated a top 50 new media account among all blockchain-related accounts, with only several months after her first contact with blockchain.%3C/p%3E%0A%3Cp%3E%3Cbr\n %3E%3C/p\n",
      "json_metadata": "{\"tags\":[\"roadmap\",\"views\",\"and\",\"dividends\"],\"users\":[\"eosgo\"],\"image\":[\"https://steemit-production-imageproxy-upload.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\",\"https://www.eos.store/static/img/person/[email protected]\"],\"links\":[\"https://busy.org/@eosgo/announcement-grading-criteria-for-eos-block-producers-in-march-7-report\",\"https://steemit.com/eos/@eosgo/two-new-criteria-for-eos-block-producer-candidates-in-report-9\",\"https://www.eos.store \",\"https://github.com/eosstore \",\"https://t.me/StoreEos \",\"https://twitter.com/StoreEos\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

anomalyupvoted (1.00%) @eos.store / block-producer-agreement-discussion-thread-thomasbcox

2018/05/17 06:44:45 UTC

22,502,393|911597a

voter	anomaly
author	eos.store
permlink	block-producer-agreement-discussion-thread-thomasbcox
weight	100 (1.00%)
Transaction Info	Block #22502393/Trx 911597aaec9e04f13eefbc157a43dc23c26049ae

View Raw JSON Data

{
  "trx_id": "911597aaec9e04f13eefbc157a43dc23c26049ae",
  "block": 22502393,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-17T06:44:45",
  "op": [
    "vote",
    {
      "voter": "anomaly",
      "author": "eos.store",
      "permlink": "block-producer-agreement-discussion-thread-thomasbcox",
      "weight": 100
    }
  ]
}

eos.storepublished a new post: block-producer-agreement-discussion-thread-thomasbcox

2018/05/17 06:12:45 UTC

22,501,753|081d230

parent author
parent permlink	thomasbcox
author	eos.store
permlink	block-producer-agreement-discussion-thread-thomasbcox
title	Block Producer Agreement Discussion Thread @thomasbcox
body	<html> <blockquote>原文链接：https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread</blockquote> <p><br></p> <p>Here's the text just published by @thomasbcox:</p> <p>这是 @thomasbcox刚刚出版的关于BP需要遵守的规则：</p> <p><br></p> <p>As a Block Producer (BP), I/we promise to:</p> <p>作为一个BP，我/我们承诺：</p> <p><br></p> <p>1.Produce exactly the authorized number of blocks faithfully, accurately, at the appointed time in the rotation</p> <p>1.在指定的时间内，轮流、如实、精准地生产出授权的块数。</p> <p><br></p> <p>2.Never produce and sign two or more blocks with the same block height or block interval</p> <p>2.从不在同一块高或出块间隔内生产并且签名两个或两个以上的块。</p> <p><br></p> <p>3.Never censor governance related transactions such as votes or Arbitration related transactions</p> <p>3.对交易相关的治理，如投票或交易相关的仲裁，绝不进行审查。</p> <p><br></p> <p>4.Only add "good" transactions from the transaction pool to the block</p> <p>4.只把交易池中“优质”的交易添加到块中。</p> <p><br></p> <p>5.Make a good faith effort to include as many "good" transactions as possible to the block without undue discrimination</p> <p>5.尽力将“优质”交易如实放到块中，不得有不必要的歧视。</p> <p><br></p> <p>6.Exclude "bad" transactions from the block, and publish why they were excluded</p> <p>6.把“劣质”的交易从块中剔除，并且公布剔除原因。</p> <p><br></p> <p>7.Show no favoritism among transactions, ordering them in a FIFO fashion or using some other ordering mechanism that is declared publicly in advance, including the default ordering provided by the unmodified software</p> <p>7.不偏袒任何交易，所有交易按FIFO排序，或按之前公开声明的其他一些排序机制，包括未经修改的软件所提供的默认顺序。</p> <p><br></p> <p>8.Refrain from using my/our superior information to "front run" transactions nor enabling anyone else to “front run”</p> <p>8.避免利用我/我们的信息优势来“预先运行”交易，也不要让任何人“预先运行”。</p> <p><br></p> <p>9.Accept as valid any Arbitrator’s order that’s</p> <p>9.接受仲裁人以下任何有效命令：</p> <p><br></p> <p>i. signed by an Arbitrator</p> <p>1）由仲裁人签名</p> <p><br></p> <p>ii. that the chain shows was assigned to a Case,</p> <p>2）链表被分配到一个实例中，</p> <p><br></p> <p>iii. such that the order affects only the Accounts named in that Case, and</p> <p>3）这样一来，该订单只影响到该实例中指定的账户，同时</p> <p><br></p> <p>iv. the Arbitrator is in good standing with their Arbitration Forum, and</p> <p>4）仲裁人遵守其所在仲裁庭的规章，并且</p> <p><br></p> <p>v. the original Transaction that gave rise to the Case names that Arbitration Forum as the venue for dispute resolution</p> <p>5）仲裁庭将原始交易引起的案例域名作为解决争议的场所</p> <p><br></p> <p>10.Only freeze accounts when authorized to do so by a valid Arbitrator’s order</p> <p>10.只有在仲裁人有效命令授权下才能冻结账户。</p> <p><br></p> <p>11.Always file a dispute against myself/ourselves after taking initiative to act on an emergency</p> <p>11.在对紧急情况采取初步行动后，要始终对我自己/我们自己提出异议。</p> <p><br></p> <p>12.Provide at least four (4) public endpoints running full nodes (the Minimum Configuration)</p> <p>12.至少提供4个公共端节点运行全节点（最低配置）</p> <p><br></p> <p>13.Not requesting my/our daily Vote Bonus pay on days when I/we don’t have the Minimum Configuration running, and repaying any Vote Bonus income collected while the Minimum Configuration wasn’t running</p> <p>13.在我/我们没有运行最低配置的日子里，不需要我/我们支付每天的投票奖金，同时在最低配置没有运行时，偿还收集到的一切投票奖金收入。</p> <p><br></p> <p>14.Disclosing all ownership of my/our organization greater than 10%</p> <p>14.公开占我的/我们的组织持有总量超10%的持有人。</p> <p><br></p> <p>15.Not sharing more than 10% ownership with another BP</p> <p>15.不要与其他bp共享超过自己10%的所有权</p> <p><br></p> <p><img src="https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400" width="969" height="318"/></p> <p><br></p> <p>Email: [email protected] </p> <p>Website: http://www.eos.store </p> <p>Twitter: https://twitter.com/StoreEos </p> <p>Github: https://github.com/eosstore </p> <p>Eosgo: https://steemit.com/@eos.store</p> <p>Telegram: https://t.me/StoreEos</p> </html>
json metadata	{"tags":["thomasbcox","block","producer"],"users":["thomasbcox"],"image":["https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400"],"links":["https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread","http://www.eos.store","https://twitter.com/StoreEos","https://github.com/eosstore","https://steemit.com/@eos.store","https://t.me/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22501753/Trx 081d230abf3d6cb2edce4b9dd3a22336c9bccede

View Raw JSON Data

{
  "trx_id": "081d230abf3d6cb2edce4b9dd3a22336c9bccede",
  "block": 22501753,
  "trx_in_block": 48,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-17T06:12:45",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "thomasbcox",
      "author": "eos.store",
      "permlink": "block-producer-agreement-discussion-thread-thomasbcox",
      "title": "Block Producer Agreement Discussion Thread  @thomasbcox",
      "body": "<html>\n<blockquote>原文链接：https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread</blockquote>\n<p><br></p>\n<p>Here's the text just published by&nbsp;@thomasbcox:</p>\n<p>这是&nbsp;@thomasbcox刚刚出版的关于BP需要遵守的规则：</p>\n<p><br></p>\n<p>As a Block Producer (BP), I/we promise to:</p>\n<p>作为一个BP，我/我们承诺：</p>\n<p><br></p>\n<p>1.Produce exactly the authorized number of blocks faithfully, accurately, at the appointed time in the rotation</p>\n<p>1.在指定的时间内，轮流、如实、精准地生产出授权的块数。</p>\n<p><br></p>\n<p>2.Never produce and sign two or more blocks with the same block height or block interval</p>\n<p>2.从不在同一块高或出块间隔内生产并且签名两个或两个以上的块。</p>\n<p><br></p>\n<p>3.Never censor governance related transactions such as votes or Arbitration related transactions</p>\n<p>3.对交易相关的治理，如投票或交易相关的仲裁，绝不进行审查。</p>\n<p><br></p>\n<p>4.Only add \"good\" transactions from the transaction pool to the block</p>\n<p>4.只把交易池中“优质”的交易添加到块中。</p>\n<p><br></p>\n<p>5.Make a good faith effort to include as many \"good\" transactions as possible to the block without undue discrimination</p>\n<p>5.尽力将“优质”交易如实放到块中，不得有不必要的歧视。</p>\n<p><br></p>\n<p>6.Exclude \"bad\" transactions from the block, and publish why they were excluded</p>\n<p>6.把“劣质”的交易从块中剔除，并且公布剔除原因。</p>\n<p><br></p>\n<p>7.Show no favoritism among transactions, ordering them in a FIFO fashion or using some other ordering mechanism that is declared publicly in advance, including the default ordering provided by the unmodified software</p>\n<p>7.不偏袒任何交易，所有交易按FIFO排序，或按之前公开声明的其他一些排序机制，包括未经修改的软件所提供的默认顺序。</p>\n<p><br></p>\n<p>8.Refrain from using my/our superior information to \"front run\" transactions nor enabling anyone else to “front run”</p>\n<p>8.避免利用我/我们的信息优势来“预先运行”交易，也不要让任何人“预先运行”。</p>\n<p><br></p>\n<p>9.Accept as valid any Arbitrator’s order that’s</p>\n<p>9.接受仲裁人以下任何有效命令：</p>\n<p><br></p>\n<p>i. signed by an Arbitrator</p>\n<p>1）由仲裁人签名</p>\n<p><br></p>\n<p>ii. that the chain shows was assigned to a Case,</p>\n<p>2）链表被分配到一个实例中，</p>\n<p><br></p>\n<p>iii. such that the order affects only the Accounts named in that Case, and</p>\n<p>3）这样一来，该订单只影响到该实例中指定的账户，同时</p>\n<p><br></p>\n<p>iv. the Arbitrator is in good standing with their Arbitration Forum, and</p>\n<p>4）仲裁人遵守其所在仲裁庭的规章，并且</p>\n<p><br></p>\n<p>v. the original Transaction that gave rise to the Case names that Arbitration Forum as the venue for dispute resolution</p>\n<p>5）仲裁庭将原始交易引起的案例域名作为解决争议的场所</p>\n<p><br></p>\n<p>10.Only freeze accounts when authorized to do so by a valid Arbitrator’s order</p>\n<p>10.只有在仲裁人有效命令授权下才能冻结账户。</p>\n<p><br></p>\n<p>11.Always file a dispute against myself/ourselves after taking initiative to act on an emergency</p>\n<p>11.在对紧急情况采取初步行动后，要始终对我自己/我们自己提出异议。</p>\n<p><br></p>\n<p>12.Provide at least four (4) public endpoints running full nodes (the Minimum Configuration)</p>\n<p>12.至少提供4个公共端节点运行全节点（最低配置）</p>\n<p><br></p>\n<p>13.Not requesting my/our daily Vote Bonus pay on days when I/we don’t have the Minimum Configuration running, and repaying any Vote Bonus income collected while the Minimum Configuration wasn’t running</p>\n<p>13.在我/我们没有运行最低配置的日子里，不需要我/我们支付每天的投票奖金，同时在最低配置没有运行时，偿还收集到的一切投票奖金收入。</p>\n<p><br></p>\n<p>14.Disclosing all ownership of my/our organization greater than 10%</p>\n<p>14.公开占我的/我们的组织持有总量超10%的持有人。</p>\n<p><br></p>\n<p>15.Not sharing more than 10% ownership with another BP</p>\n<p>15.不要与其他bp共享超过自己10%的所有权</p>\n<p><br></p>\n<p><img src=\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\" width=\"969\" height=\"318\"/></p>\n<p><br></p>\n<p>Email: [email protected]&nbsp;</p>\n<p>Website: http://www.eos.store&nbsp;</p>\n<p>Twitter: https://twitter.com/StoreEos&nbsp;</p>\n<p>Github: https://github.com/eosstore&nbsp;</p>\n<p>Eosgo: https://steemit.com/@eos.store</p>\n<p>Telegram: https://t.me/StoreEos</p>\n</html>",
      "json_metadata": "{\"tags\":[\"thomasbcox\",\"block\",\"producer\"],\"users\":[\"thomasbcox\"],\"image\":[\"https://steemit-production-imageproxy-thumbnail.s3.amazonaws.com/DQmUw1RrVu6MYWvjtcrxh1dNbUtik37inF6hDqi1GgywnXv_1680x8400\"],\"links\":[\"https://forums.eosgo.io/discussion/922/block-producer-agreement-discussion-thread\",\"http://www.eos.store\",\"https://twitter.com/StoreEos\",\"https://github.com/eosstore\",\"https://steemit.com/@eos.store\",\"https://t.me/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

eos.storefollowed @eos-asia

2018/05/15 11:37:48 UTC

22,450,664|8fb19a6

required auths	[]
required posting auths	["eos.store"]
id	follow
json	["follow",{"follower":"eos.store","following":"eos-asia","what":["blog"]}]
Transaction Info	Block #22450664/Trx 8fb19a6db4954ffc57face98dfcbed54ca37bc52

View Raw JSON Data

{
  "trx_id": "8fb19a6db4954ffc57face98dfcbed54ca37bc52",
  "block": 22450664,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-15T11:37:48",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "eos.store"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"eos.store\",\"following\":\"eos-asia\",\"what\":[\"blog\"]}]"
    }
  ]
}

thevillanupvoted (1.00%) @eos.store / bp-eosio

2018/05/15 08:04:15 UTC

22,446,393|83655b0

voter	thevillan
author	eos.store
permlink	bp-eosio
weight	100 (1.00%)
Transaction Info	Block #22446393/Trx 83655b08f4dbed48c7194d4664a42391ee47be23

View Raw JSON Data

{
  "trx_id": "83655b08f4dbed48c7194d4664a42391ee47be23",
  "block": 22446393,
  "trx_in_block": 45,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-15T08:04:15",
  "op": [
    "vote",
    {
      "voter": "thevillan",
      "author": "eos.store",
      "permlink": "bp-eosio",
      "weight": 100
    }
  ]
}

eos.storepublished a new post: bp-eosio

2018/05/15 08:02:36 UTC

22,446,360|60c6347

parent author
parent permlink	thomas
author	eos.store
permlink	bp-eosio
title	BP怎么样获得eosio奖励
body	<html> <blockquote>Thomas 视频讲解的链接：https://www.youtube.com/watch?v=vqVOqq__De0&feature=youtu.be</blockquote> <p>每个生产者每6s出12个块，一轮有21个生产者，每一轮可以生产252个块；每一轮大概可以新产出195个token。这些tokens 被分成不均等的两份，第一份支付给所有的块生产花费，第二份用来放到工人建议基金中（这个大概是用于将来作为奖励发放给对社区做出贡献的账户，目前eosio并没有做过多的说明，或许以后会完善）。</p> <p>每年有5%的通货膨胀，每天大约有133000 新的tokens产生。其中1%（~27k tokens）用作bp的基金，剩余的4%（~107k tokens）保存刀工人建议基金中。</p> <p>在1%的bp基金中，每天大约产生26716 tokens，大约25%用于每个块的支付（~6679 tokens/day）每一个活跃的bp大概会有318 tokens/day，剩余的75% 给投票奖金池使用（~20037 tokens/day）</p> <p><img src="https://images.eos.store/bp2.jpg" width="794" height="546"/></p> <p>每一个活跃的BP会有2%的票，所以他每天获得新的token数为318+400 = 718 new tokens/day。</p> <p>每一个备用节点会有0.75%的票数，所以每天获得新的token数为 150 tokens。</p> <p><img src="https://images.eos.store/bp1.jpg" width="408" height="416"/></p> <p><br></p> <p><br></p> <blockquote><strong>Public website URL and at least one social media account</strong> </blockquote> <ul> <li>Official Website: <a href="https://www.eos.store/">https://www.eos.store </a></li> <li>Email: [email protected] </li> <li>Github: <a href="https://github.com/eosstore">https://github.com/eosstore </a></li> <li>Telegram: <a href="https://t.me/StoreEos">https://t.me/StoreEos </a></li> <li>Twitter: <a href="https://twitter.com/StoreEos">https://twitter.com/StoreEos</a></li> <li>Wechat official account：EosStore </li> </ul> <p><br></p> <p><br></p> </html>
json metadata	{"tags":["thomas","eosio","bp"],"image":["https://img.youtube.com/vi/vqVOqq__De0/0.jpg","https://images.eos.store/bp2.jpg","https://images.eos.store/bp1.jpg"],"links":["https://www.youtube.com/watch?v=vqVOqq__De0&feature=youtu.be","https://www.eos.store/","https://github.com/eosstore","https://t.me/StoreEos","https://twitter.com/StoreEos"],"app":"steemit/0.1","format":"html"}
Transaction Info	Block #22446360/Trx 60c63477da07157480f828a379ca22c985755db2

View Raw JSON Data

{
  "trx_id": "60c63477da07157480f828a379ca22c985755db2",
  "block": 22446360,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-15T08:02:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "thomas",
      "author": "eos.store",
      "permlink": "bp-eosio",
      "title": "BP怎么样获得eosio奖励",
      "body": "<html>\n<blockquote>Thomas 视频讲解的链接：https://www.youtube.com/watch?v=vqVOqq__De0&amp;feature=youtu.be</blockquote>\n<p>每个生产者每6s出12个块，一轮有21个生产者，每一轮可以生产252个块；每一轮大概可以新产出195个token。这些tokens 被分成不均等的两份，第一份支付给所有的块生产花费，第二份用来放到工人建议基金中（这个大概是用于将来作为奖励发放给对社区做出贡献的账户，目前eosio并没有做过多的说明，或许以后会完善）。</p>\n<p>每年有5%的通货膨胀，每天大约有133000 新的tokens产生。其中1%（~27k tokens）用作bp的基金，剩余的4%（~107k tokens）保存刀工人建议基金中。</p>\n<p>在1%的bp基金中，每天大约产生26716 tokens，大约25%用于每个块的支付（~6679 tokens/day）每一个活跃的bp大概会有318 tokens/day，剩余的75% 给投票奖金池使用（~20037 tokens/day）</p>\n<p><img src=\"https://images.eos.store/bp2.jpg\" width=\"794\" height=\"546\"/></p>\n<p>每一个活跃的BP会有2%的票，所以他每天获得新的token数为318+400 = 718 new tokens/day。</p>\n<p>每一个备用节点会有0.75%的票数，所以每天获得新的token数为 150 tokens。</p>\n<p><img src=\"https://images.eos.store/bp1.jpg\" width=\"408\" height=\"416\"/></p>\n<p><br></p>\n<p><br></p>\n<blockquote><strong>Public website URL and at least one social media account</strong>&nbsp;</blockquote>\n<ul>\n  <li>Official Website: <a href=\"https://www.eos.store/\">https://www.eos.store&nbsp;</a></li>\n  <li>Email: [email protected]&nbsp;</li>\n  <li>Github: <a href=\"https://github.com/eosstore\">https://github.com/eosstore&nbsp;</a></li>\n  <li>Telegram: <a href=\"https://t.me/StoreEos\">https://t.me/StoreEos&nbsp;</a></li>\n  <li>Twitter: <a href=\"https://twitter.com/StoreEos\">https://twitter.com/StoreEos</a></li>\n  <li>Wechat official account：EosStore&nbsp;</li>\n</ul>\n<p><br></p>\n<p><br></p>\n</html>",
      "json_metadata": "{\"tags\":[\"thomas\",\"eosio\",\"bp\"],\"image\":[\"https://img.youtube.com/vi/vqVOqq__De0/0.jpg\",\"https://images.eos.store/bp2.jpg\",\"https://images.eos.store/bp1.jpg\"],\"links\":[\"https://www.youtube.com/watch?v=vqVOqq__De0&feature=youtu.be\",\"https://www.eos.store/\",\"https://github.com/eosstore\",\"https://t.me/StoreEos\",\"https://twitter.com/StoreEos\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

Manabar

Voting Power100.00%

Downvote Power100.00%

Resource Credits100.00%

Reputation Progress24.69%

{
  "voting_manabar": {
    "current_mana": "6041573525",
    "last_update_time": 1539240765
  },
  "downvote_manabar": {
    "current_mana": 0,
    "last_update_time": 1523934507
  },
  "rc_account": {
    "account": "eos.store",
    "rc_manabar": {
      "current_mana": "7763821966",
      "last_update_time": 1541693028
    },
    "max_rc_creation_adjustment": {
      "amount": "2020748973",
      "precision": 6,
      "nai": "@@000000037"
    },
    "max_rc": "8185619917"
  }
}

Account Metadata

POSTING JSON METADATA
profile	{"name":"EosStore","website":"http://www.eos.store","profile_image":"https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg","cover_image":"https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg"}
JSON METADATA
profile	{"name":"EosStore","website":"http://www.eos.store","profile_image":"https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg","cover_image":"https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg"}

{
  "posting_json_metadata": {
    "profile": {
      "name": "EosStore",
      "website": "http://www.eos.store",
      "profile_image": "https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg",
      "cover_image": "https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg"
    }
  },
  "json_metadata": {
    "profile": {
      "name": "EosStore",
      "website": "http://www.eos.store",
      "profile_image": "https://steemitimages.com/DQmXRKefWwrTxZnSMEEZgTm7tgAWC1UV1tLpb98PTa7kzjj/%E6%9C%AA%E6%A0%87%E9%A2%98-1.jpg",
      "cover_image": "https://steemitimages.com/DQmWunMDca1av7jR92xmnBS8korwJByvVQjXegLMDDpf1xp/%E5%BE%AE%E5%8D%9A%E5%A4%B4%E5%9B%BE.jpg"
    }
  }
}

Auth Keys

Owner

Single Signature

Public Keys

STM8BYVSa8JugxbWUuq4VjiKpV9RCwTfHk2QqyM4V5eRv2QC6GB4q1/1

Active

Single Signature

Public Keys

STM6MEUkzUgimR2AvJbGTy1xFoVjMcJtJvww5b5eL92khAuQyLAXH1/1

Posting

Single Signature

Public Keys

STM5kGkRBYXfQPAMdtwA82uS5xGGP1An4YWsNqarWV9C5MM85LFz31/1

Memo

STM4uMqkUDVNDF5Pwpr1og3XNH9sbzDreQRDqoTrHjkiYZ3cn3rvm

{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM8BYVSa8JugxbWUuq4VjiKpV9RCwTfHk2QqyM4V5eRv2QC6GB4q",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6MEUkzUgimR2AvJbGTy1xFoVjMcJtJvww5b5eL92khAuQyLAXH",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5kGkRBYXfQPAMdtwA82uS5xGGP1An4YWsNqarWV9C5MM85LFz3",
        1
      ]
    ]
  },
  "memo": "STM4uMqkUDVNDF5Pwpr1og3XNH9sbzDreQRDqoTrHjkiYZ3cn3rvm"
}

Witness Votes

0 / 30

No active witness votes.

[]