EOSFORCE

EOS side chain

home link https://eosforce.io/index.html

reference material

Community

Exchanges that listed the coin
2
Symbol
EOSC
Dapp
To be released
Project introduction

EOSFORCE is committed to exploring more open-minded cryptographic infrastructure. Multi-Chain Architecture The ongoing development of the block-chaining protocol meets the multiple consensus demands of the cryptographic economy and facilitates the application of block-chain technology in a variety of areas. The most active parallel mainnet in the EOSIO ecosystem, EOSForce.io, provides users with a more favorable resource model, provides developers with more abundant block-chain foundation support, and provides a more even administrative mechanism for the community. Users can activate the EOSForce.io mainnet asset using the mapped EOSIO's private key offline signature.

Executives and partners
There is no executive team information at this time
Please leave a message of support for the team

DUSHU FOUNDATION

Bit Forex

Latest News

There is no news posted at the moment
Please leave a message of support for the team

go to leave a message

Medium

Happy 2-Year Anniversary to...

On June 22, 2018, EOSC Mainnet was officially launched. Afterwards, 126 nodes such as CindyDaily, Jeepool and EOSAwake joined EOSC community in succession, and started the journey of EOSC community governance together with all community partners.With the goal of evolving towards the decentralized high-performance smart contract platform,EOSC Community and EOSForce Development Team have rebuilt the codes several times under the joint construction and continuous promotion in the past two years, which has gradually improved the performance of EOSC and provided a smooth environment for the high-speed operation of smart contracts.In early 2019, faced with the problem raised by the community developers that the hard fork upgrade for the mainnet is not conducive to long-term development, EOSForce Team developed a smooth update mechanism based on Effective Block to ensure that the EOSC mainnet can be efficiently iterated through smooth upgrades without compatibility; it’s original heartbeat mechanism has effectively promoted the EOSC main network to be more stable, ensuring the smooth operation of the entire main network around the clock.In March 2020, EOSForce Development Team launched the first solution to high-performance blockchain light nodes-EOS ArcLight, which provides low-cost and real-time reliable block data for various blockchain applications and lays the foundation of the implementation of high-performance cross-chain services.In the aspect of technology ecological construction, EOSForce Development Team, Awake Team and other community developers have jointly developed a series of development tools in the past two years, greatly reducing the threshold of blockchain development and effectively improving developers’ development efficiency. For example, FORCE.IO, a high-performance blockchain development framework, helps developers to launch a chain with “one click”, and build applications on the chain without considering the underlying implementation. What’s more, tools such as EOSFORCE.CDT, EOSC development tool set, EOSC contract development online compiler, EOSC historical data query plug-in, etc., also empower developers to directly start technology development from the contract level to the chain level.In the process of exploring decentralized governance, EOSC community put forward lots of discussions, and successfully implemented a number of improvement proposals such as Node Reward&Punishment Mechanism, Decentralized Budget System, the Foundation, etc., making significant contributions to the sustainable development of EOSC mainnet.On the occasion of EOSC Mainnet 2-Year Anniversary, EOSC Mainnet Foundation teamed up with the EOSForce Development Team, EOSC Mainnet Secretariat, Math Wallet and EOSC mainnet nodes to launch EOSC Mainnet 2-year anniversary celebration event.How To Participate1.Follow EOSC official Twitter account @EOSForce2.Retweet the activity post:3.Tag 3 friends4.Fill in form: bit.ly/30X88IyActivity Period2020/06/22 12:00 pm (UTC+8) — 2020/06/24 12:00 pm (UTC+8)RewardsFirst Prize:1NFT (15 winners)Second Price:622 EOSC (20 winners)RemarksNFT Benefits Explanation:After June 22, 2020, each EOSC x Math NFT can be redeemed for 2000 EOSC, and 10% added value will be given annually. No calculation in less than one year, and it is valid for 5 years.Each EOSC x Math NFT can also be redeemed for a piece of peripheral product for any EOSC community event in the later period.2. Winners will be announced on June 28, 2020 on Twitter.3. EOSC Mainnet Foundation reserves the right for the final explanation.Hosts: EOSC Mainnet Foundation, EOSForce Development TeamSupporters: EOSC Mainnet Secretariat, Math Wallet, Bepal, CCBC, Nodeasy.com, Cindy Daily, KuCoin, Lichang

EOSFORCE

20. 06. 22

EOSC 2 Year Anniversary Cel...

Dear friends, EOSC Mainnet has been ongoing for around two years, during which many significant achievements were made. From EOSC Decentralized Budget System to EOS ArcLight Solution, every step of EOSC mainnet’s development is inseparable from the construction and contribution of EOSC community partners.To thank all your support and companionship to EOSC community in the past two years, EOSC Foundation will coordinate with Math Wallet to airdrop NFT (Non — Fungible Token). Each EOSC x Math NFT can be redeemed for 2000 EOSC, 10% added value will be given annually(e.g., when EOSC is 3 years old, each EOSC x Math NFT can be redeemed for 2200 EOSC).Only 66 EOSC x Math NFTs available, be lucky to come and get it firstly!Activity Period2020/06/22 12:00 pm (UTC+8) — 2020/06/24 12:00 pm (UTC+8)Redeem EOSC x Math NFTAfter June 22, 2020, each EOSC x Math NFT can be redeemed for 2000 EOSC, and 10% added value will be given annually. No calculation in less than one year, and it is valid for 5 years.Each EOSC x Math NFT can also be redeemed for a piece of peripheral product for any EOSC community event in the later period.EOSC Mainnet Foundation reserves the right for the final explanation.How To ParticipateTo win limited EOSC x Math NFT, please follow EOSC official Twitter page @EOSForce in advance, and check the activity post during the activity period.The NFT will be issued based on the ERC-1155 token standard, more activity details will be able to referred at the activity post.MathWallet NFT Guide:http://blog.mathwallet.org/?p=1314Terms and ConditionsEach Twitter account can only correspond to one ETH address and win at most one NFT.Winners will be randomly selected among those eligible users.If you do not use an ERC-1155 compatible wallet, you will be unable to receive the NFT. We recommend using Math Wallet to receive your NFT and do not use exchange ETH addresses to receive NFT.You will only be eligible after sharing the activity post on Twitter.The limited EOSC NFTs will be sent to the eligible addresses.The celebration activity of EOSC mainnet 2 year anniversary will be launched on 2020/06/22, please stay tuned!

EOSFORCE

20. 06. 19

EOSC Referral Program

1.Newcomer RewardNew users recommended by the referrer can receive EOSC reward by creating user name through the public key. The screenshots of your EOSC account, Twitter account and KuCoin account are required to be provided (The mobile phone number of the registered KuCoin account must be the same as the Telegram mobile phone number. The exchange accounts registered between 06/15/2020 and 07/01/2020 will be the best).The first 20 new users will receive 500 EOSC rewards, 21–50 new users will receive 200 EOSC rewards, 51–100 new users will receive 100 EOSC rewards, and new users after 100 will receive 50 EOSC rewards.Remark: The EOSC reward will be applied from EOSC Budget System and approved by EOSC Foundation. In addition, star.eosc sponsors 20,000 EOSC.2. Newcomer Voting RewardNew users recommended by the referrer, after buying EOSC in the exchange, and participating the fixed voting(any period) in the wallet, will receive 10% of the EOSC you purchased according to the screenshot (the maximum is no more than 1000 EOSC).3.Referral RewardThe referrers shall help new users to download wallet (Math Wallet, Awake Wallet, etc.), and create username (one Telegram account with only one EOSC account)Every time a new user’s wallet is created, the introducer gets a reward of 100 EOSC, which is monthly settled, that is, the settlement is based on the number of new referrals in the month.( In order to avoid cheating, the recommender shall ensure that the recommended new users have at least 10 EOSC to vote for a two-year fixed period)If you have completed more than 10 referrals, starting from the 11th, you can enjoy 1.5 times the reward for each new referral, which is 150 EOSC.If you have completed more than 50 referrals, starting from the 51st, you can enjoy 3 times the reward for each new referral, which is 300 EOSC.If you have completed more than 100 referrals, starting from the 101st, you can enjoy 5 times the reward for each new referral, which is 500 EOSC.4.Best Referrer RewardIn addition, the top 3 referrers on the referral ranking list, will win additional EOSC rewards (with more than 10 referrals). The tentative rewards are: Top 1 will win no less than 30,000 EOSC and KuCoin peripheral products, Top 2 will win 20,000 EOSC and KuCoin peripheral products, and Top 3 will win 5,000 EOSC and KuCoin peripheral products.The top 3 referrers for the quarterly and yearly referral ranking list will win additional EOSC rewards. The specific amount is to be determined.5. Referrer Voting RewardAfter the new user has completed his first voting (ie, Newcomer Voting Reward) under the guidance of the referrer, the referrer will win a Referrer Voting Reward. After buying EOSC in the exchange, and participating the fixed voting in the wallet, the qualified referrer will receive 20% of purchased EOSC by providing the screenshot proof (the maximum is no more than 2,000 EOSC).6. Remarks(1) The short-term trial operation shall be subject to the above values. The incentive value of the long-term plan can be modified according to the actual situation.(2) All the above rewards shall be subject to the correspondence of one EOSC account, one KuCoin account and one Telegram account. If there is a force majeure or evil behavior, EOSC Foundation has the right to EOSC Foundation reserves all the rights for final explanation.(3) This referral program is going on trial from 06/16/2020 to 07/01/2020 for half a month.(4) All rewards will be distributed by a new account “eosccx”, which can be reviewed on the explorer to guarantee the fairness.

EOSFORCE

20. 06. 15

Meeting Minutes-The 16th EO...

Time: At 15:00 on April 15th, 2020 (UTC+8)Link: https://zoom.com.cn/j/999549267Attendee: Representatives from the BPs, community members and all members of the SecretariatHost: Guo YingInterpreter: LilySubjectsDiscuss & Vote on Proposal for Introducing An Entrusted Foundation to Participate in The Governance of Budget System V2.0Release Work Regulation for EOSC Mainnet SecretariatAgenda1. Discuss & Vote on Proposal for Introducing An Entrusted Foundation to Participate in The Governance of Budget System V2.0Introduction of the proposalSome opinions on the proposal from Su Boming, one of the community membersInterpretations of the proposal from Captain ForceVoting on the proposalVoting results: Among the 23 BPs, there were 18 “yes” votes, 0 “no” vote, 5 abstentions. The proposal was approved and officially took effect.The community commissioned the secretariat to implement the proposal.2. Release Work Regulation for EOSC Mainnet Secretariat 1.0Captain Force introduced the background of this regulation.Introduction of “Work Regulation for EOSC Mainnet Secretariat 1.0”.Mechanism SpecificationProcess SpecificationThe guiding significance and expectation of “Work Regulation for EOSC Mainnet Secretariat 1.0” on the work of the Secretariat.The iteration and improvement route of “Work Regulation for EOSC Mainnet Secretariat 1.0”.Publish the release channels and participation methods of this regulation.Attached:Email for BP Proposals:BPproposal@eosforce.ioMeeting Recording:https://youtu.be/06AKU9Nck4sENDSRecorder: Jack

EOSFORCE

20. 04. 23

EOSIO Weekly Roundup

04/13–04/19EOSC Foundation Will Take Over EOSC Budget SystemAt the 16th EOSC Mainnet BP Meeting, BPs voted Proposal for Introducing An Entrusted Foundation to Participate in The Governance of Budget System V2.0 FIP#18 through. EOSC Budget System will be formally handed over to the Foundation for management after the current term of the Budget Committee ends.BB: EOS WPS Is Powerful When Utilizing Democratized ConsensusBlock.one CEO Brendan Blumer, also known as BB, tweeted to state that an EOS WPS can be powerful and practical when leveraging democratized consensus to identify opportunity and cement accountability. Without involving the public, value is lost, he highlighted.“B1 PBE is actively working on these concepts and looks forward to collaborating with the community,” added he.Nearly 2.5 Mln EOS MovedMonitored by Whale Alert, 2,497,083 EOS ($6,819,001 USD) were transferred from the address “zbeoschangel” to another address “huobidevice3” at 00:15:46 UTC on April 19.The transaction hash is b3017b3f8efd7f92f48cfff4c4f01063372ccd594c0ce3d4ea97ea0c44a02a82.China’s BSN To Support EOS Nodes In JulyLed by the State Information Center, the Blockchain Service Network (BSN) stated that it will support EOS nodes outside China in late July. Besides, Ethereum nodes and other public chain nodes will then be progressively supported by BSN.PeckShield: Some Voice Phishing Accounts Have Illegally Profited 9044 EOSRecently, PeckShield has detected that there is a large number of inductive memo transaction information on the EOS mainnet, which has been verified as phishing scam websites posing as the Voice official account. Multiple accounts such as voiceechange and airdropvoice have gained altogether 9,044 EOS. PeckShield recommends that users should be aware of the false information of voice token collection, and can tell the true or false by checking the funds’ transfer status of the phishing account. For now, 73,874 EOS accounts have been attacked by these phishing accounts.

EOSFORCE

20. 04. 21

Work Regulation for EOSC Ma...

1.IntroductionSince June 22, 2018, the Secretariat has started exploring the decentralized community governance upon launch. As the first distributed autonomous organization, the Secretariat of EOSC Mainnet BP Meeting has experienced 5 terms. During the 5 terms, we have not only continuously promoted the construction of the mainnet based on community proposals, but also improved the governance mechanism of the Secretariat itself. We believe that the development of the community lies in both the continuous improvement and open source of codes, and the continuous improvement of the community governance mechanism.Based on the above cognition, we edited Work Regulation for EOSC Mainnet Secretariat. On the one hand, it can set a better working reference for the new secretariat. On the other hand, it can promotes the discussions on the experience of distributed organization governance with other blockchain communities.2.Routine Work2.1 Work DivisionThe Secretariat shall be elected by BPs. At the first regular meeting, the Secretariat will divide up the work. Generally, there shall be 1 seat for the Secretary-General, 3 seats for the Deputy Secretary-General. The specific work divisions are as follows:Meeting Host: Responsible for hosting regular meetings and BP meetings.Meeting Recorder&Media Synchronization: Responsible for recording meeting minutes and media synchronization of regular meetings and BP meetings.Meeting Organizer: Responsible for organizing meetings.Meeting Notice Editor&Person in charge of communication with development team: Responsible for writing meeting notices and communicating with the development teamRemarks:1. The meeting notice shall be reviewed by all the members of the Secretariat after editing. After it is confirmed correct, the notice shall be sent to BPs by the Secretary-General.2. The notice of the meeting shall be publicized in time on the community forums and media platforms.3. Meeting notice and meeting minutes shall be publicized both in Chinese and English communities.2.2 Regular Meetings of the SecretariatThe secretariat shall hold a regular meeting once a week, and the specific meeting time shall be determined at the first regular meeting of the new Secretariat.The host of the secretariat’s regular meetings is responsible for hosting the meeting.The editor of meeting notice is also responsible for the meeting minutes. After the meetings, the meeting mibutes shall be synchronized on forums, communities and Github.2.3 Organize Discussions on Community ProposalsOrganizing discuussions on community proposals is one of the main tasks of the Secretariat. The specific process is as follows:2.3.1 Collect ProposalsThe primary approaches for the Secretariat to collect proposals is through the Secretariat’s mailbox BPproposal@eosforce.io, the official forum and the community daily discussions. The Secretariat shall collect the latest proposals based on the key issues of community’s concern.2.3.2 Standardize ProposalsFor the proposals submitted by the community, the secretariat shall communicate with the proposer to ensure the correct format and logical specifications of the proposals. Specifically refer to EOSFORCE Mainnet Proposal Example.2.3.3 Organize Community Discussions on ProposalsFor proposals of community governance type, the Secretariat shall organize the community to discuss the proposal before the BP meeting.2.3.4 Organize Voting for ProposalsThis process can refer to the work content of Chapter 4.2.4 Organize BP/Community MeetingsThe workflow for organizing EOSC Mainnet BP Meetings and community meetings is as follows:2.4.1 Write Meeting Notice The notice shall be written by editor in charge. For the format, please refer to EOSC Mainnet BP Meeting Notice Example. Before writing the meeting notice, it shall be confirmed that whether the development team will attend the meeting to synchronize the development progress with the community. If necessary, the meeting agenda shall includes: Representative from the ndevelopment team synchronizes the development progress with the community.2.4.2 Publish Meeting Notice The Secretary-General shall be responsible for it. The meeting notice shall be notified to the person in charge of each BP at least three days in advance, and ensure that the person in charge of the node receives the notice.On the day of the meeting, the Secretariat shall notify the person in charge of the BP again and confirm whether to attend the meeting on time and make a note. The Secretariat shall make sure that at least two thirds of the BPs attend the meeting (including proxy voting by the Secretariat).Remarks: 1. The process of meeting notice should be rigorous and reasonable. 2. The notice of the meeting can only be officially released after all members of the Secretariat have ensured it is correct.2.4.3 Host Meeting The meeting host is responsible for hosting the meeting. For the meeting process, please refer to EOSC Mainnet BP Meeting Process Example. 2.4.4 Synchronize Meeting Minutes The meeting recorder & the person in charge of the media synchronization is responsible for meeting minutes synchronization. Please refer to EOSC Mainnet BP Meeting Minutes Example. The meeting minutes shall be edited in Markdown format and output both in Markdown format and PDF format. Markdown format shall be synchronized in the official forum and Github-DAO-FIPS directory, PDF format shall be synchronzied to the community. 2.4.5 Exceptional Case If the BP is not able to attend the meeting, the Secretariat shall confirm whether a proxy voting is needed. If necessary, the Secretariat shall ask the node to vote for, against, or abstain from the meeting proposal. Then, a person from the Secretariat will be specifically assigned for the proxy voting. If not necessary, and the BP does not attend the meeting, it will be recorded as Absent in the meeting minutes. For BP meetings, the Secretariat shall make sure that at least two thirds of the BPs attend the meeting (including proxy voting by the Secretariat).2.5 Organize Node Multi-SignatureFor the cases that approved proposals are required to take effect by BPs’ multi-signature, the Secretariat shall lead the mainnet multi-signature upgrade. The specific workflow is as follows:2.5.1 Preparation Work The Person in charge of communication with development team shall communicate the code development matters and ask for feedback, including development cycle, multi-sigature commands and related documentations. 2.5.2 Write NoticeBefore the official multi-signature, the meeting editor shall edit the multi-sig notice, including multi-sign time, multi-sig commands and remarks. Please refer to EOSC Mainnet Node Multi-Signature Notice Example. 2.5.3 Publish NoticeThe Secretary-General is responsible for publishing the formal multi-signature notice. 2.5.4 Follow Up ProgressThe secretariat shall follow up on the progress of multi-signature and promptly reminds nodes to complete multi-signature commands. 2.5.5 Complete Multi-Signature, Publish to the CommunityAfter the completion of the multi-signature, an news flash shall be issued to the community. Please refer to EOSC Mainnet Multi-Signature Completion Announcement. 2.5.6 Publish on Media PlatformThe news flash shall be synchronized in both Chinese and English communities.2.6 Offline Nodes RecoveryThe status of the offline nodes is mainly in the charge of the communicator with the coordination of other members of the secretariat. In the event of node failure or disconnection, the Secretariat shall start an emergency mechanism to cooperate with community nodes to restore the block status as soon as possible.2.6.1 Notify Offline Node to Locate FaultAfter the node goes offline, the Secretariat shall notify the node operator as soon as possible, and confirm whether the node can recover by itself. If not, locate the fault and provide a screenshot of the error report.2.6.2 Coordinate with Development Team or Other Node Operator to Provide SupportWhen the node cannot recover by itself, the Secretariat should contact the development team or other nodes in the community to provide technical support to assist the node to recover the block status as soon as possible.2.6.3 Announce the Community with Node RepairAfter the node restores its status, the Secretariat shall announce that the community node has recovered.3. Community Operation3.1 BP Community OperationThe Secretariat is responsible for the operation of the BP WeChat community. After the first regular meeting of the new secretariat, the authority of the supernode community administrator will be transferred to the new members. Members shall modify the remark name in the BP community (for example: Secretary-General & star.eosc_Guo Ying) to facilitate the publishment of notices by the Secretariat. The Telegram community of overseas communities is the same as above.3.2 Daily Community Article OperationThe members of the Secretariat shall synchronize the community with the development team’s daily output articles at the first time. At the same time, they need to organize community discussions or development team sharing on the development content and updates.4. Work ReportGenerally, the meeting minutes shall be edited and organized by the meeting recorder and reported by the Secretary-General.5.Term Changing of the SecretariatThe term changing of the Secretariat shall be in the charge of the Secretary-General. The specific process is as follows:5.1 Publish Registration NoticeThe term changing notice shall be published at least half a month in advance with the Github address for registration.5.2 Confirm Registration InformationConfirm whether the registration personnel and number meet the requirements before the formal meeting.5.3 Election SpeechThe Secretariat shall notice the candidates to prepare the election speech in advance, including both Chinese and English versions.5.4 Participant ConfirmationThe Secretariat shall synchronize the term changing meeting information to the candidates confirm the participation on time.5.5 Official ElectionPlease refer to EOSC Mainnet BP Meeting Procedure Example.6.SalaryThe salary of the Secretariat shall paid by the decentralized budget system, and the Secretary-General is responsible for applying the salary.7. Authorities7.1 Administrative Authority of Github-DAO BoardThe Secretariat possesses the Administrative Authority of Github-DAO Board. The person in charge of communication shall coordinates the authorization from the development team.7.2 Administrative Authority of Community ForumsThe Secretariat possesses the Administrative Authority of Community Forums. The person in charge of communication shall coordinates the authorization from the development team.8. OtherThis regulation is written based on the experience of the first five terms of the EOSC Mainnet Secretariat as a daily work reference. It is hoped that the follow-up terms of the secretariat will continue to improve in the process of community governance.9.IndexEOSFORCE Mainnet Proposal ExampleEOSC Mainnet BP Meeting Notice ExampleEOSC Mainnet BP Meeting Hosting Procedure ExampleEOSC Mainnet BP Multi-Sig Notice ExampleEOSC Mainnet Multi-Sig Completion Announcement ExampleEOSC Mainnet Secretariat Work Report ExampleEOSC Mainnet BP Meeting Minutes Example

EOSFORCE

20. 04. 19

Meeting Minutes-EOSC Commun...

1. Arrangements:Time: April 2nd, 2020, 20:00 ~ 21:30 (UTC + 8 )Place: https://zoom.com.cn/j/999549267 (ZOOM)Host: Guo Ying — the SecretariatRecorder: Jack— the SecretariatInterpreter: Lily2. SubjectDiscussions on Proposal to Introduce An Entrusted Foundation to Participate in The Governance of Budget System3. Agenda3.1 The requirements for the Foundation (the 3rd part of the proposal)Original Proposal: The Foundation shall lead and promote the development and construction of the mainnet and community, and complete the work of project planning, budget evaluation, development implementation, and continuous follow-up.Discussion Results: The Budget Foundation should be committed to community development and construction. The direction of community development is still dominated by BPs, the development team, and community members.3.2 The tenure of the Foundation (the 4th part of the proposal)Original Proposal: After the 6-month tenure has run out, if BPs do not actively renew the contract on the chain, the foundation account will lose the control of the budget system and a new Foundation will elected.Discussion Results: The term of the Budget Foundation expires by default on closing of the tenure. For the reappointment, BPs’ authorization is required.3.3 The funds of the Foundation (the 6th part of the proposal).Original Proposal: A budget shall be proposed for the expenditure of the Foundation and community proposals from the budget system. It will enter a 7-day publicity period after being approved by the Foundation. If there is no objection, EOSC will be automatically transferred to proposer’s account on closing of the publicity period.Discussion Results: The work of the Budget fFoundation includes two aspects, one is similar to the administrative approval proposal, the other is to actively expand external resources, both of which require the Foundation to exercise the power of approval. And the 7-day publicity period is the time for community supervision. If the community disagrees with the budget proposal that more than two-thirds of the BPs vote against, the proposal will be rejected.3.4 The incentives of the Foundation (the 7th part of the proposal).Original Proposal: 30% of the Foundation’s expenditure budget is the incentive compensation, which shall be claimed by the Foundation from the account. (30% is the reference value).Discussion Results: The proportion of budget foundation incentives shall be set according to the specific work content, and after the meeting, the proposer will re-enact this rule.Attached:Email for BP Proposal: BPproposal@eosforce.ioMeeting Recording: https://youtu.be/Cl0UKlwXJx4Recorder:Jack

EOSFORCE

20. 04. 14

Proposal for Introducing An...

Proposal for Introducing An Entrusted Foundation to Participate in The Governance of Budget System V2.0Proposers: The 1st Budgeting Committee, EOSC Development TeamIntroductionThe Budget System of EOSC mainnet has been running for six months with the management of the Budgeting Committee elected by the community. Based on the exploration experience for half a year, we found that distributed and collaborative non-fund management professionals cannot fully utilize the vitality of the organization and promote the ecological development of the budget system. In order to better explore the governance model of the budget system on the blockchain, based on the EOSC mainnet consensus mechanism, it is proposed to introduce an entrusted foundation governance solution, hereinafter referred to as the Foundation.1. ResponsibilityAccording to the requirement for development of the community, effectively utilize the budget system to promote ecological sustainable development.2. ElectionAnyone of the community members and BPs can participate in the election of the foundation. Candidates shall clarify the responsibilities of the foundation and make plans for community development during the term of office. At the election, candidates shall present their plans in turn. BPs will vote and the person with the highest votes will serve for the Foundation.3. Requirements3.1 The Foundation shall lead and promote the development and construction of the community, and complete the work of project planning, budget evaluation, development implementation, and continuous follow-up. At the same time, the Foundation is required to make a timely publicity of the recent work plan, the latest progress, and the whereabouts of each budget expenditure to the community.3.2 The Foundation shall approve and monitor the progress and implementation of community proposals and make them public in a timely manner.4. TenureThe tenure of the Foundation shall be 6 months. After it has run out, if BPs do not actively renew the contract on the chain, the foundation account will lose the control of the budget system and the Foundation will also be re-elected.5. SupervisionBPs are responsible for supervising the Foundation. If the Foundation does not operate properly and fails to achieve the expected goals, the account control of the budget system can be modified when more than 2/3 BPs approve.6. FundsA budget shall be proposed for the expenditure of the Foundation and community proposals from the budget system. It will enter a 7-day publicity period after being approved by the Foundation. If there is no objection during the publicity period, a withdrawal proposal can be proposed, and EOSC will be automatically transferred to proposer’s account when the withdrawal proposal is approved. If more than 1/3 BPs vote against the budget proposal during the publicity period, the proposal will be rejected.7. IncentivesThe incentive part of the Foundation is determined by the candidate according to the specific planning and goals.The elected candidate shall claim the budget from eos.budget account.April 9th, 2020

EOSFORCE

20. 04. 13

EOSIO Weekly Roundup

03/30–04/05Block.one Invests $150M In Its Social Media AppAccording to The Block, Voice, the social media App launched by Block.one, has received $150 million from its parent company.The funding is said to kickstart Voice’s independent operations.The beta version of Voice’s tech was built on a special-purpose blockchain based on the EOSIO protocol.All Active Block Producers Enabled EOS VMEOS Nation posted a Twitter thread, “Active Block Producers have now enabled EOS VM on all producing nodes! The fatest blockchain network in the world just go faster!”On June 1st 2019, Block.one announced EOSIO 2.0, which included several new features. One of these features called the EOS Virtual Machine (EOS VM) is a new Web Assembly (WASM) smart-contract engine. This upgrade to EOSIO brings efficiency improvements of 12x when compared to the first version of EOSIO released in June 2018. Block producers have been hard at work optimizing both software and hardware over the last few months in order to enable a smooth activation of EOS VM.Europechain launches a COVID-19 monitoring app based on EOSIOEuropechain announced the integration of a monitoring service for COVID-19 into their FACT application. Europechain is a consortium of blockchain experts using the EOSIO protocol within their public blockchain. What will their COVID-19 tracker be useful for?Their FACT application is already being used by organisations to increase visibility and ensure compliance & accountability. Through the COVID-19 tracker, governments and healthcare professionals will be able to monitor virus trends and try to increase the efficiency of medical resources.Through FACT it is possible to create templates to share with the people indicated, which could be the employees of an organization, for track potential outbreaks. All the data collected will be safe within their EOSIO chain, ensuring a high level of security and privacy.WAX Staking and Some Free AccountsThe Wax Guild Maltablock introduced a new method to create a WAX Account via Telegram and provided enough funds to give out 1000 accounts free of charge. The @waxmeetupbot lives in telegram and is based on the signupwaxwax smart contract, which the team presented in January. In the next phase, this bot will have interactive abilities such as answering frequently asked questions.

EOSFORCE

20. 04. 08

EOSIO Weekly Roundup

03/23–03/29Proposal for Introducing An Entrusted Foundation to Participate in The Governance of EOSC Budget System LaunchedAccording to the exploration experience for half a year, it is found that distributed and collaborative non-fund management professionals cannot fully utilize the vitality of the organization and promote the ecological development of the budget system. In order to better explore the governance model of the budget system on the blockchain, based on the EOSC mainnet consensus mechanism, the 1st EOSC Budgeting Committee anf EOSC Development Team proposed to introduce an entrusted foundation governance solution.Block.one CEO Regards EOS Worker Proposal System As ‘Very High Risk, Very High Reward Direction’Brendan Blumer, CEO of Block.one, opines that the proposed EOS Worker Proposal System is a “very high risk, very high reward direction.”In a March 26’s tweet, Blumer said that if the community decides to go ahead with it, they must get it right.“We need [to] learn from mistakes and double down on success. I’m up for whatever challenge lays ahead,” he said.This, however, is not the first time Blumer showed his worries.As reported by CoinNess.com on March 15, the Block.one CEO said he personally concerned of the effects the recently proposed EOS Worker Proposal System might have on the network, adding “even if the amount is nominal, socially authorising the BP’s to direct token-holder funds into projects without a clear or measurable return of value is risky, and may open the door to corruption and external scrutiny.”Details of the proposal were released by EOS Nation on March 11. In nature, the proposal is a funding mechanism for the EOS Public Network modeled closely after the DASH Budget Proposal System. It enables developers and other value creators to seek funding from the EOS blockchain for their projects outside of EOS block rewards.Block.one Recruits Block Producer (BP) EOS New YorkBlock.one announced that former EOS New York founders Rick Schlesinger, Kevin Rose and their team would be joining Block.one to help the company deepen its engagement with public blockchain communities, promote ideas to foster open, organized, and decentralized public network operation, and represent its interests as a token holder of several public digital assets.Block.one CEO Elaborates On Future Of Bitcoin, BlockchainBrendan Blumer, CEO of Block.one, expressed his opinions in a series of tweets about the future of Bitcoin (BTC) and blockchain.Per the CEO, if Bitcoin continues to grow exponentially, single transactions will move to private chains, institutions will make BTC management easy for the masses, and inter-company settlements will dominate the limited bandwidth of the main chain.Meanwhile, Bitcoin and crypto will be offering people a transparent store of value with provable supply integrity and self-empowering custody options.“Blockchain isn’t going to give us every freedom we want, nor is it going to end governments, or their ability to track and influence our actions, but it will increase the efficiency and mutual accountability of the governing process,” he said.

EOSFORCE

20. 03. 31

EOS ArcLight: The First Sol...

EOSIO has led the development of blockchain technology from the laboratory to a mass commercial implementation. With the emergence of more high-performance blockchain protocols, the prototype of the trust economy has formed. New problems are brought by the large-scale deployment of high-performance blockchain, such as the high O&M cost of full nodes, the inefficiency in the synchronization of application data, and the infeasibility of sharing data across multiple chains. A solution for lightweight nodes is urgently need in high-performance blockchains to eliminate the final obstacle for the further development of the trust economy.EOS ArcLightEOS ArcLight, the first high-performance blockchain light node solution, was launched by EOSForce Development Team recently. This solution is developed based on Golang, and introduces lightweight node solutions for high-performance blockchain protocols such as EOSIO. Unlike the full nodes which are started based on nodeos, EOS ArcLight only need to verify block headers without implementing Action in block.New Challenges in High-Performance Blockchain1. High O&M CostEOSIO’s block header structure supports lightweight nodes, but there is no reliable light node implemented in EOSIO community.In Bitcoin Whitepaper, Satoshi Nakamoto mentioned that it is possible to verify payments without running a full network node. The old block can only retain block headers and the transaction data that nodes pay attention to. Even in 2008 when the white paper was released, all block header data could be stored in the memory of the common microcomputer.In the subsequent discussion, Satoshi Nakamoto believed that there would eventually be only about 100,000 full nodes that can produce blocks in the Bitcoin network. Meanwhile there would be millions of lightweight clients that can send and receive transactions. Although those clients cannot produce blocks, they can still verify the payment for themselves without relying on other nodes.EOSIO’s blockchain structure also supports lightweight nodes, and it also requires a large number of lightweight nodes in its network and applications.In EOSIO network, a full node has high requirements for machine performance, network, and operation and maintenance. At present, there are few full nodes available in EOSIO network, which means that the current EOSIO network structure is not decentralized that has a great impact on the network stability and also increases the difficulty of developing and deploying applications on the chain.Take the EOS network (chainID: aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906) as an example (mid-January 2020), the total RAM is 174G, and the allocated memory is about 74G. Although the actual data used is little, there must be at least 64G of memory configured on a full node, otherwise transaction execution failure will occur due to memory read and write misses.On the other hand, the current EOSIO block data is very large, which brings great challenges to the maintenance and storage of nodes. At the same time, it takes too long to replay blocks. On some mainstream performance servers, the complete replay takes nearly one month.2. High Development Difficulty & CostAlthough EOSIO’s plug-in architecture allows nodes to expand functions, nodes have higher requirements for machine performance. Meanwhile, the entry for developing plugins based on C++ is high, so there are few developer tools in EOSIO, indirectly increasing the difficulty of developing DAPP.Many early query and index services of DAPP relied on EOSIO’s history plugin and mongoDB plugin. However, with the increase of block data, a big performance problem occurred with such history nodes or mongoDB database. Although the community has also proposed some solutions, the cost is quite high because they rely on full nodes, which brings a lot of additional costs to the development and operation of DAPP.Satoshi Nakamoto’s prediction of Bitcoin network structure is also applicable to other blockchain networks. In addition to full nodes, EOSIO network also needs a large number of lightweight nodes that conform to the cost game.3. Unable to Meet Cross-Chain NeedsThe support of cross-chain function significantly oriented the development of public chains, and EOSIO will support adding sidechains based on IBC. Currently it requires to start IBC based on the full node to enable users to obtain the proof data based on Merkle Tree. However, due to the high cost of building a full node, it is very difficult for even a few validators and phishers to start full nodes, which will make some theoretical support schemes fail economically. If the cross-chain operation depends only on the services provided by a small number of full nodes, the entire system will be very vulnerable.To sum up the above problems, we need an implementation of the sufficiently lightweight EOSIO node. The light node should be easily expanded and secondarily developed while ensuring the verification of the block.Technical Principals of EOS ArcLightEOS ArcLight will not process every transaction, only verify the validity of the block and block header, and confirm that its block is irreversible.One of the main reasons for EOSIO’s high demand for nodes is its RAM state. The state is very large and has not been verified in the block, so any node that wants to obtain any state needs to completely replay the EOSIO block. Although the node can be restored through the snapshot function, even for nodes that are kept in sync, the recovery time is relatively long in the event of a failure. Due to the busy transactions on the EOSIO chain, the peak value can reach about 4,000 TPS, so the synchronization of real-time EOSIO block will also have higher requirements for the machine.Not processing every transaction means that most of the work of the light nodes can be completed in parallel, and synchronization can also be started from any block height. In the current prototype implementation, light nodes need only take up very little computing resources to complete verification.Although not processing each transaction allows light nodes to occupy few resources, it also makes light nodes unable to provide RAM state. In EOSIO, almost all states are stored in RAM. Some actions also need to be triggered by executing transactions. In order to solve this problem, some assertion mechanism is required to ensure that the node can obtain the EOSIO state based on the block data only, which can be achieved through the EOSIO State Assertion Contract and the State Static Assertion Contract.According to the different roles of EOSIO light nodes, we divide EOSIO light nodes into block nodes and block header nodes. The former includes all or part of EOSIO blocks, and the latter includes only EOSIO block header data.Considering that EOSIO is under the continuous development, light nodes also need to follow it to iterate, so the design of light nodes should be as homogeneous as possible with EOSIO, and their APIs and actions should be as unified as possible with nodeos.Use Cases of EOS ArcLight1. The Real Decentralized WalletAt present, EOSIO wallets are usually based on the unverified data provided by third parties, which are different from Bitcoin wallets. These EOSIO wallets will not work properly without services provided by third parties. And in these wallets, users cannot get accurate transaction execution feedback. If you want to confirm whether the transaction is completed or not, you can only rely on other services, such as the block explorer to confirm the transaction completion, which actually has a great security risk.Based on EOS ArcLight, we can embed light nodes into the wallet, so that each wallet is a light node. At this time, the wallet can independently verify the success of the transaction, and it can be used safely even in an insecure network environment.2. Credible Realtime Block Data ServiceMany DAPPs need real-time on-chain data, especially applications with short response and security-oriented applications such as decentralized exchanges. They need to be able to securely and reliably obtain real-time status on the chain, especially EOSIO’s irreversible block determination. Because the current consensus algorithm is still in the initial completion stage, the time interval between the blocks entering the irreversible state is long, which means that many applications need to accept the irreversible blocks that are not entered first, and avoid inconsistent state verification after the fact. This logic requires writing node plugins and deploying full nodes, which will increase the DAPP development and operation costs.Based on EOS ArcLight, light nodes can be incorporated into existing data services in the form of libraries. Light nodes are developed based on Golang, which are friendly to back-end development and there is no threshold. At the same time, light nodes fully implement consensus algorithms. Therefore, it is very convenient to implement a reliable real-time block data service.3. High-Performance Cross-Chain ServiceIf cross-chain interaction between the EOSIO chain and other chains is required, it is often necessary to implement light nodes on both chains. EOS Arclight can be easily embedded in other services or nodes, and can independently verify the nodes to well support such applications.In fact, the original motivation of EOS ArcLight was being a link in cross-chain services. For example, for many chains that are developed based on the Cosmos SDK, a very common architecture is to use the Cosmos SDK-based chain as the settlement chain and the EOSIO-based chain as the calculation chain. The implementation of Cosmos IBC protocol is used to complete the settlement of cross-chain calculation results. In this system, we only need to integrate EOS ArcLight in the nodes of the settlement chain, so that each node of the settlement chain is a light node of the computing chain. Through the consensus mechanism of the original settlement chain, the calculation chain block data held by each settlement chain node (only the ID of the irreversible block needs to be considered) reaches a consensus. In this way, the data of the calculation chain can be traced back to the settlement chain.EOS ArcLight Technology RoadmapEOS ArcLight was developed by EOSForce, the development team of EOSC community. At present, the development work is mainly divided into three directions: node implementation, compatibility with full node API, and optimization of computing performance. EOSForce team has implemented a preliminary version that can complete the synchronization and verification of block data, and a technology roadmap has been released:2020 Q1: Implement the decision algorithm of irreversible blocks, improve block storage implementation, achieve the compatibility of nodeos’ block db.2020 Q2: Support other nodes to synchronize blocks and transactions from light nodes, improve API interface to be as compatible as possible with nodeos.2020 Q3: Optimize concurrent computing capabilities, speed up the synchronization process, and support EOS-VM to implement the execution of some ActionsEOS Arclight is fully open-source, view it on Github:https://github.com/eosforce/eos-light-node

EOSFORCE

20. 03. 27

Proposal for Introducing An...

Proposers: The 1st Budgeting Committee, EOSC Development TeamIntroductionThe Budget System of EOSC mainnet has been running for six months with the management of the Budgeting Committee elected by the community. Based on the exploration experience for half a year, we found that distributed and collaborative non-fund management professionals cannot fully utilize the vitality of the organization and promote the ecological development of the budget system. In order to better explore the governance model of the budget system on the blockchain, based on the EOSC mainnet consensus mechanism, it is proposed to introduce an entrusted foundation governance solution, hereinafter referred to as the Foundation.1. ResponsibilityAccording to the requirement for development of the community, effectively utilize the budget system to promote ecological sustainable development.2. ElectionAnyone of the community members and BPs can participate in the election of the foundation. Candidates shall clarify the responsibilities of the foundation and make plans for community development during the term of office. At the election, candidates shall present their plans in turn. BPs will vote and the person with the highest votes will serve for the Foundation.3. RequirementThe Foundation shall lead and promote the development and construction of the mainnet and community, and complete the work of project planning, budget evaluation, development implementation, and continuous follow-up. At the same time, the Foundation is required to make a timely publicity of the recent work plan, the latest progress, and the whereabouts of each budget expenditure to the community.The Foundation shall approve and monitor the progress and implementation of community proposals and make them public in a timely manner.4. TenureThe tenure of the Foundation shall be 6 months. After it has run out, if BPs do not actively renew the contract on the chain, the foundation account will lose the control of the budget system and the Foundation will also be re-elected.5. SupervisionBPs are responsible for supervising the Foundation. If the Foundation does not operate properly and fails to achieve the expected goals, BPs can modify the account control of the budget system at any time.6. FundsA budget shall be proposed for the expenditure of the Foundation and community proposals from the budget system. It will enter a 7-day publicity period after being approved by the Foundation. If there is no objection, EOSC will be automatically transferred to proposer’s account on closing of the publicity period.7. Incentives30% of the Foundation’s expenditure budget is the incentive compensation, which shall be claimed by the Foundation from the account. (30% is the reference value).March 24, 2020

EOSFORCE

20. 03. 26

EOSIO Weekly Roundup(03.16–...

03/16–03/22Block.one CEO: B1 Focuses On Building Best Technology, Designing For High Performance, Horizontal Scalability, etcYves La Rose, CEO of EOS Nation, took to Twitter to announce that EOS is now processing more than 100M unique operations every 24 hours. While one Twitter user raised questions about it, saying “The market cap (EOS) is too low and security is too low to run any high cap stablecoins like USDC. EOS is a baby, minnow, teenyweeny, or fruitfuly in the blockchain space. Security and trust have been its problem since day one.”As to such query, Brendan Blumer, co-founder and CEO of Block.one, replied: “By that logic, nobody can ever enter the market again, which we all know isn’t true. EOS has a flawless material security record, EOSIO is unrivaled in performance, and I’m confident EOS developers’ talent and numbers will keep outpacing other ecosystems.”“The truth is, showtime hasn’t started for any blockchain ecosystem yet, and B1 isn’t focused on smoke and mirrors, were focused on building the best technology, designing for high performance, horizontal scalability, parallel processing, and easy integration,” he stressed later.Several projects have the potential to demonstrate EOSIO capability at an unprecedented scale, and when the demand escalates for swapping out traditional database architecture for blockchain, they’re focused on making sure EOSIO is the only plausible choice, according to Brendan Blumer.EOS LaoMao: BTC Will Be A Kind Of Asset; New Economic Status Will Emerge If Bridgewater Gets Into TroubleEOS LaoMao tweeted to say that: “BTC will sure to be a genuine asset because it will not crash without the interference of the government. If Bridgewater gets into trouble, we can infer that the traditional hedge fund model reaches the end of the rope and the new economic status will appear soon.”OKEx To Adjust Face Value Of EOSUSDT Perpetual ContractAccording to the official Weibo news of OKEx, on March 17 from 08:00 to 08:30 UTC, OKEx will adjust the face value of EOSUSDT perpetual contract from 0.1 EOS to 10 EOS. During the upgrade process, the USDT perpetual contract of the corresponding crypto will be suspended from trading. Users can not place orders, cancel orders and add margin, etc., but the fund transfer will not be affected. In order to reduce the impact on transactions, users are requested to carry out risk control in advance by canceling orders, reducing positions or adding margin.

EOSFORCE

20. 03. 24

EOSC AMA Recap

On March 16th, the AMA began with Cyborg, the founder of EOSC. Thanks everyone for joining this event. Here are some highlights from the founder’s responses to the EOSC community:Q1. For what reason did you made EOSC?A1: We carried out in-depth research on the EOSIO protocol very early, and made some conclusions. First of all, we believed that EOSIO is a good protocol that can well meet everyone’s needs for blockchain performance at that time. The DPOS consensus algorithm allows the blockchain to achieve a better balance between decentralization and high performance. However, we did not agree with many governance designs of the EOSIO protocol. We believed that there are problems with the election mechanism of EOSIO, and these problems should also be resolved by some people. So EOSC community optimized the election mechanism of EOSIO and launched the EOSC mainnet at the genesis block height of one. Through persistently upgrading EOSC mainnet that makes EOSC Network evolve toward the decentralized high-performance smart contract platform.Q2. #EOSCFORCE’s team consists of experienced and brilliant individuals. What made you to unite together and work in unison for the fulfillment of it?A2:Our vision is to explore a more open cryptoeconomic infrastructure in practice. We believed that when the blockchain technology has advanced from a social experiment to a mass commercial implementation, cryptoeconomics will lead a new economic trend in the world, bringing epoch-making value and a better life to people around the world.Q3. EOSforce have chosen a development route that is not compatible with the B1 code. What is the consideration? After all, this leads to EOSforce needing a completely different set of development tools. Will this make it more difficult for developers to enter?In fact, EOSC is compatible with EOSIO. If you are familiar with the EOSIO codes, then you can easily participate in the development of EOSC. In the development planning of EOSC, we have always been as compatible with EOSIO as possible, not only EOS, but also other blockchains started based on EOSIO, such as Telos. We try to keep mutual adaptation as much as possible, which can be maintained at the same ecosystem.Q4. How is EOSForce any better than EOS for DApp developing? Should we expect improvement in aspects like speed and security? Also has been stated that with EOSC users wont deal with resources management? If true, how transaction fees will be implemented.Unlike EOS’s resource mortgage model, EOSC uses a fee model similar to ETH. At the same time, in order to provide users with a comfortable experience, EOSC has set a fixed fee for routine operations such as transfers, but it is compatible with the network carrying capacity. This allows EOSC users to use EOSC smoothly worrying about the complex fee logic.For DAPP developers, they do not need to care about the purchase and use of resources such as RAM and CPU. They only need to set the corresponding fee (set_fee) for each action in the smart contract according to the resource consumption. This allows DAPP developers to focus on the business logic development itself without having to spend extra attention elsewhere.Q5.When do we get our frozen tokens back?I think you can communicate and discuss this issue with the community nodes. EOSC community voted for FIP # 11 in October 2019. If you have different opinions and ideas on this proposal, you can discuss it in the community or communicate with the EOSC BPs.You can check FIP#11 via this link: https://github.com/eosforce/FIPs/blob/master/FIP%20%2311.mdQ6. What is the next step for EOS to be traded on decentralized platforms against other major cryptocurrencies?Trading is a voluntary behavior of the community. As one of the core development teams of the EOSC mainnet, EOSForce Development Team focuses on the technical development of the chain level. On the one hand, we continue to evolve the technology on the EOSC mainnet according to our development roadmap. On the other hand, we will provide technical development support based on proposals approved by the community.Q7.When EOSC on Newdex? Is there any possibility that EOSC will be integrated into the lynx wallet? When will eosforce be added in token pocket?EOSC is a blockchain governed by the community. Many participants in the EOSC community have jointly promoted the development of EOSC.If you have any good ideas or suggestions, you can initiate the community to act together.EOSC mainnet has launched a decentralized budget system. Everyone’s contribution to EOSC mainnet can be correspondingly rewarded through the budget system. We also encourage everyone to initiate budget proposals via the budget system and jointly build the EOSC mainnet.Q8. What is the utility use of your token?There are two uses. On the one hand, for any blockchain, the resources on the chain such as CPU, RAM, NET are limited, and no one can use them unlimitedly. In this case, the on-chain token is equivalent to the use of resources, and the more EOSC you have, the more resources you can use on the chain.On the other hand, EOSC tokens can be used to vote for staking and participate in the election of BPs. With the continuous improvement of the on-chain ecology, holders of EOSC tokens will also get more valuable services through EOSC tokens.

EOSFORCE

20. 03. 24

EOSIO Weekly Roundup

03/09–03/15Daniel Larimer Of EOS: DPOS Built On Top Of Different Technical Consensus VariationsDaniel Larimer, CTO of the Block.one team behind the EOS.IO (EOS) blockchain, tweeted, “every blockchain has two consensus algorithms: automated/objective /technical and manual/subjective/governance. DPOS is a number of different subjective governance models built on top of a number of different technical consensus variations — some that go undistinguished/unnamed.”Decentralized Identity System Based On EOSIO Adopted By South Korean ArmyOn January 21, 2020, the South Korean Military Manpower Administration, MMA, launched its decentralized identity system on its own blockchain based on EOSIO. This is the first attempt to use a DID system based on a blockchain adopted by a public institution, according to EOS GO.The system was developed by the South Korean government’s blockchain public pilot project in collaboration with Raon Secure, a Korean authentication and security company, which provided “Omni One”, the EOSIO-based DID platform.The MMA blockchain reached over 50,000 usage records during the first month of its release.Brendan Blumer Praises Binance As True Representative Of Users’ InterestIn a recent tweet, Brendan Blumer speaks highly of Binance, saying it represents token holders’ interest. He said, “Remember when you stake your EOS on an exchange, you are allowing the exchange to vote on your behalf. Binance’s focus on returning rewards back to EOS holders demonstrates their efforts to represent token holder interest. This is EOS governance maturing. Nice job@cz_binance.”Details Of EOS WPS Proposal ReleasedEOS Nation has released details of the EOS Worker Proposal System (WPS) proposal, which is a funding mechanism for the EOS Public Network, enabling developers and other value creators to seek funding from the EOS blockchain for their projects outside of EOS block rewards.The WPS is modeled closely after the DASH Budget Proposal System, which has been successfully funding projects benefiting the DASH ecosystem for over five years.Learn more about the WPS.BB: EOS’s Governance Is Simple And Relentlessly Marches Towards Interest Of Its HoldersBlock.one CEO Brendan Blumer, also known as BB, posted a tweet, saying, “With multiple options of 80%+ voter rebates freely available to EOS token-holders, that leaves effective inflation at less than 2%, making it unrivaled in cost to performance output. EOS’s governance is simple; it relentlessly marches towards the interest of its holders.”Block.one CEO Worried About EOS Nation’s Worker Proposal SystemWhile Brendan Blumer claimed that he greatly appreciates and applauds the work and thoughts that EOS Nation put into ways of potentially advancing the EOS ecosystem, he personally concerned of the effects the recently proposed EOS Worker Proposal System might have on the network.“Even if the amount is nominal, socially authorizing the BP’s to direct token-holder funds into projects without a clear or measurable return of value is risky, and may open the door to corruption and external scrutiny. Further, the WPS system may alienate EOS from some others in the blockchain community and media, and therefore potentially stake its future largely on the success of the WPS system itself. I am concerned about the risk profile and odds of this bet,” he tweeted.

EOSFORCE

20. 03. 16

EOSIO Weekly Roundup

03/02–03/08The Publicity Period of EOSC Budget System Was Adjusted to 7 DaysOn March 3rd, 2020(UTC+8), A Proposal to Adjust The Publicity Period of Budget System proposed by the 1st Budgeting Committee was approved by the multi-sig of EOSC BPs, and the publicity period of the decentralized budget system was shortened from 14 days to 7 day.Block.one Does Not Hold A Potentially Controlling Stake Of EOS, CEO SaysBrendan Blumer, CEO at Block.one, claimed on Twitter that Block.one does not hold a potentially controlling stake of EOS tokens.“B1 own less than 9.7% of EOS tokens and all top 21 producers have over 30% of tokens voting for them. B1 couldn’t change a single BP. Please consider a correction if truth is your intention,” he wrote.https://twitter.com/BrendanBlumer/status/1234662984057647111?s=20Daniel Larimer Of EOS: DPOS Is Based On Simple Principles And Facilities Community Decision MakingDaniel Larimer, CTO of the Block.one team behind the EOS.IO (EOS) blockchain, tweeted, “DPOS is based on simple principles and facilities community decision making. Other ‘decentralized’ systems lack any formal decision-making processes yet they still ‘make forking decisions’ by undefined processes largely governed by people other than the token holders.”https://twitter.com/bytemaster7/status/1236429108571242498?s=20Justin Sun Responds To Cointelegraph: We Have No Intention To Take Over Any BlockchainJustin Sun posted a tweet in which he once again clarified his team’s stance on the ‘takeover’ of Steem blockchain. According to him, “I believe the point here is about sanctity of private property. We have no intention to take over any blockchain. But we won’t allow anyone to freeze innocent people hard earned money even by “consensus”. Anyone’s assets including exchanges assets should be safe!” In a recent article released by Cointelegraph, Justin Sun was accused of “hostile takeover” of Steem blockchain. Also involved in this wave is Binance CEO ZHAO Changpeng, who was suspected to have transferred users’ money for voting.Binance CEO Apologizes For Binance’s Participating In Steem VoteBinance CEO ZHAO Changpeng tweeted to apologize on the Steem vote, “STEEM thread. I was hoping not to be involved, but alas, it doesn’t seem to be possible. I did approve the vote from Binance, thinking (wrongly) it was a regular upgrade/fork. For that, I apologize. Guess it is only fair that I get involved until the issue is resolved.”

EOSFORCE

20. 03. 11

The 15th EOSForce Mainnet B...

Subject:The 15th EOSC Mainnet BP MeetingTime: February 26, 2020, 15:00–16:00 (UTC+8)Place:https://zoom.com.cn/j/544801531 (ZOOM会议)Host: Tokenview-ManjiubuRecorder: eosou-Su BomingInterpreter: LilyStatistician: Captain Force1. Election of the 5th term of SecretariatCandidates:jack, titanforce-Li Jianyong, star.eosc-Guo YingResults:Voting results: 17 yes-votes, 0 no-vote and 6 abstension vote. The 5th term of the Secretariat was established.2. Voting on A Proposal for Adjustment of the Secretariat’s Salary proposed by the SecretariatIn order to unify the budgetary expenditures of community governance and attract community members to take a more active part EOSC mainnet community governance, it is proposed that instead of being paid from the developer account, the salary of the Secretariat is changed to be applied from the decentralized budget system. Voting results are as follows:Results:Voting results: 17 yes-votes, 0 no-vote and 6 abstention vote. The proposal was approved.3. A Community Governance Proposal by the Budgeting CommitteeAfter a full discussion, the representatives of BPs discussed A Proposal to Adjust The Publicity Period of Budget System proposed by the 1st EOSC Budgeting Committee. This proposal will be initiated by the proposer in a multi-signature manner on the chain, and the fifth secretariat will be responsible.4. Development process synchronization from the development team1.The community mainnet has been upgraded to Force-V1.8.3. The development of Force-2.0.1 has been completed, which is being tested. The next step is the upgrade of v2.0.1, which will double the efficiency. With EOSVM, new functions and new features, performance will be greatly improved.2.SDK development in Java and Android environment; The wallet developer experience improved.3.Released Light Node solution-EOS ArcLight with roadmap released and development continued. At the same time, the team will develop peripheral tools for light nodes to unify the light node technology implementation of EOS, EOSFORCE, and codex.February 26, 2020, 15:00–16:00 (UTC+8)Meeting Minutes by Su Boming from The SecretariatAttached:E-mail for BP proposals:BPproposal@eosforce.io

EOSFORCE

20. 02. 28

EOSC Weekly Report #79

02/10–02/16Work Completed1. Tested EOSC v2.0.1 and its stability.2. Improved EOSC/Codex.io node log and state operation&maintenance plan.3. Tested android environment adaptation of Codex.io java support library, improved development document.4. EVM simulator implemented the preliminary version of create action, withdraw action, and raw action.5. Introduced RLP parsing algorithm implementation in the contract environment6. Updated EOSC upgrade document and coordinated with some nodes to upgrade to v1.8.3.Plan for Next Week1. Update some online EOSC nodes to v2.0.1.2. Merge the latest updates of EOSC / Codex.io js support library to improve the development documentation.3. The EVM simulator implements the genesis action to declare constants such as ChainID.4. Analyze ETH transaction in the contract environment to implement the basic transaction processed by ETH in the contract environment.Community News1. EOSC Mainnet upgraded to v1.8.3. As of Feb 14th(UTC+9), more than two-thirds of the nodes have completed the version upgrade.2. EOSC Staking Campaign was launched on KuCoin, which supports EOSC users to participate in lock-up purchases from 20:00 on Feb 17th to Feb 18th(UTC+8).3. The 4th session of Secretariat of EOSC mainnet released an announcement of registration for the 5th session of the Secretariat, inviting community members to actively register to make contributions to the community.4. EOS ArcLight, the solution for EOSC light nodes customized for EOSIO is officially launched, which has good scalability and greatly reduces the difficulty of EOSIO development.

EOSFORCE

20. 02. 18

EOSC Weekly Report #78

02/03–02/09Work Completed1. Merged EOSIO v2.0.1 to EOSC, test block synchronization.2. Researched EOSC/Codex.io node log and state operation&maintenance plan based on ELK.3. Codex.io transplanted eosio-java support library to test android environment adaptation.4. Started the development of EVM runtime simulator project based on EOSIO contract environment and planned the project.5. EVM simulator built a project framework and implemented ETH address support. It introduced Keccak-256 Hash algorithm to implement the basic Account-related tables and actions.Plan for Next Week1. Test EOSC v2.0.1. Update some online nodes to v2.0.1 to test the block producing and stability.2. Improve EOSC/Codex.io node log and state operation&maintenance plan.3. Test android environment adaptation of Codex.io java support library, improve development document.4. Merge EOSC/Codex.io js support library with the latest update, improve development document.5. EVM simulator implements the preliminary version of create action, withdraw action, and raw action.6. EVM simulator implements genesis action to declare constants such as ChainID.7. Introduce RLP parsing algorithm implementation in the contract environment to parse ETH transaction.Community News1. The Secretariat of EOSC mainnet is planning a new BP meeting to change the term of the Secretariat.2. EOSC development team will participate in EOSIO Smart Contracts Challenge to jointly improve EOS ecology.3. Eosgod node announced its resignation from the BP list and appealed to voters to transfer votes to other nodes.

EOSFORCE

20. 02. 10

2019 in Review: Work Report...

As 2019 drew to a close, the Secretariat of EOSC Mainnet is moving into a new decade with the development of EOSC community. For EOSC community, 2019 is a big year with major reform. In the past year, the Secretariat has gone through 3 general elections, organized 6 BP meetings, and 12 proposals have been passed to promote community development.In the new year, the Secretariat of EOSC community will continue to contribute to the development of the EOSC mainnet and jointly promote the development of the EOSC mainnet towards a decentralized, high-performance smart contract platform.Here is the 2019 work report from the Secretariat of EOSC community.January 7, 2019● Organized the 9th EOSC Mainnet BP Meeting. BPs voted JiqiX’s EOSForce Mainnet Token Production Adjustment Proposal through, which got 16 fors, 1 nays, 6 abstains, reaching passage at a 2/3 overmajority. The proposal was passed.January 15, 2019● Organized the muti-sig to implement FIP#4 A Proposal to Reduct EOSForce Mainnet Block Reward.January 24, 2019● Organized EOSC Community Governance Discussion. Nodes at home and abroad and community members discuss community governance together.February 28, 2019● Organized the 10th BP Meeting of EOSForce Mainnet. The Secretariat summarized and reported the work of the 2nd session of the Secretariat, and BPs discussed and voted on the FIP#6 Secretariat Salary Proposal and No Redemption Period for Changing Vote Proposal.April 10, 2019● Sky.eosc Node initiated the discussion on the Proposal to Destroy Tokens in Unactivated EOSForce Genesis Accounts.April 22, 2019● The 3rd session of the Secretariat of EOSForce Mainnet held a community governance discussion on new governance proposals.July 1, 2019● Organized the nodes to upgrade the EOSC mainnet system contract and expanded the mainnet resource model.July 10, 2019● Jeepool BP, Jiuzhou Capital and the Development Team jointly initiated EOSFORCE Mainnet Improvement Proposal V1.0, which involves inflation rate adjustment, voting weight adjustment, block-producing reward, punishment mechanism, decentralized budget system and referendum system.July 18, 2019● At the 11th EOSForce Mainnet BP Meeting, BPs have voted to pass the EOSForce Mainnet Improvement Proposal jointly proposed by Jeepool Node, Jiuzhou Capital and Core Team. The proposal involves inflation adjustment, voting weight adjustment, block-producing reward and punishment mechanism. The proposal was reaching passage at a 2/3 overmajority and passed.August 3, 2019● JiqiX Node initiated A Proposal to Adjust The Upper Limit of EOSC Mainnet Contract Deployment.August 10, 2019● EOSC Mainnet Contract Size Adjustment Proposal proposed by JiqiX has been approved by the multisig of more than 2/3 of the BPs.August 13, 2019● Sky.eosc Node and Awake Node initiated A Proposal to Destroy the Unactivated Genesis Accounts and Tokens. It is proposed to destroy 80% locked genesis accounts and their tokens, 20% unactivated genesis accounts and tokens of Unactivated Genesis Account LockupPlan Proposal FIP#3.August 21, 2019● The 12th EOSC Mainnet BP Meeting was held successfully. BPs voted to pass A Proposal to Destroy the Unactivated Genesis Accounts and Tokens and A Proposal to Adjust the Allocation Plan of B1 Account Tokens.● The term of EOSC Mainnet BP Meeting Secretariat has been changed successfully. Tokenview, sky.eosc, eosou.io and Captain Force will serve as members of the 4th Secretariat.August 29, 2019● EOSC Mainnet held the 13th BP Meeting to discuss the problems on the development of FIP#9 Destruction Proposal and the new proposal.September 2, 2019● The 4th session of the Secretariat issued a notice of amendments to FIP # 9.September 19, 2019● The upgrade of EOSC mainnet v1.7.1 has been completed, and all the functions in FIP#7 Mainnet Improvement Proposal have been launched, including inflation rate adjustment, fixed voting, block reward, punishment mechanism and decentralized budget system.September 27, 2019● EOSC mainnet nodes have completed the multi-sig for the Proposal to Adjust RAM Rental Price proposed by eosawake and sky.eosc, which has officially taken effective on September 26, 2019 (UTC+8). The current price of RAM on EOSC mainnet is to deposit 2 EOSC to get 1KB of RAM.October 10, 2019● The freezing execution of unactivated account balance has been completed. The unactivated account balance is not able to vote or transfer. FIP#11 officially takes effect.October 11, 2019● Organized the 14th EOSC Mainnet BP Meeting. Membership of the 1st session of Management Committee of Budget System was elected. BPs voted to pass FIP#13 A Proposal to Complete Node Information and Adjust Node Punishment Rule and FIP#14 A Proposal to Adjust Block Missing Fault Tolerance Value.November 26, 2019● The fifth phase of EOSC community theme sharing event was successfully held. The community member Jichanglulu made a sharing of “EOSC Empowers the Real Economy”.December 2, 2019● The Secretariat of EOSC Maine BP Meeting released Statute of The Secretariat of EOSC Maine BP Meeting to coordinate opinions on community governance, promote the effectiveness of the governance proposals on the chain, and maintain the consensus of EOSFORCE mainnet.

EOSFORCE

20. 01. 26

2019 in Review: A Brief His...

The day has flown by, and EOSC Community has ushered into a new decade. Look back over the past year, many EOSC community users have participated in the governance of the EOSC mainnet, proposed and discussed a number of improvement proposals, and made suggestions for the development of the EOSC mainnet. BPs have voted on proposals for Mainnet Inflation Rate Adjustment, Increasing the Maximum Size of EOSC Mainnet Contract, Increasing Voting Weight, which fully embodies that EOSC Mainnet is governed by the community. New functions such as BP Reward&Penalty Mechanism and Decentralized Budget System have been launched on the mainnet, while further improving the stability of the mainnet, also provide sufficient power for the sustainable development of the EOSC mainnet.With regard to overseas communities, overseas nodes of the EOSC mainnet and community users have held community activities for many times. The English and Korean communities have attracted thousands of users in total. A number of well-known overseas YouTubers spontaneously produced introductions and interview video albums on EOSC, providing a new window for overseas community users to understand the EOSC mainnet.Looking ahead to the new year of 2020, EOSC Community will continue to contribute to the development of the EOSC mainnet and jointly promote the development of the EOSC mainnet towards a decentralized, high-performance smart contract platform.Here is a look back at the brief history of EOSC Community in 2019.January 7, 2019● BPs voted JiqiX’s EOSForce Mainnet Token Production Adjustment Proposal through, which got 16 fors, 1 nays, 6 abstains, reaching passage at a 2/3 overmajority. The proposal was passed.January 16, 2019● The service of one key to start public chain has been officially launched. In this service, the startup team can choose the resource model of the public chain, such as the resource model of EOSForce.io, the mortgage lease model of EOSEMG, or a free resource model similar to the alliance chain. In addition, the startup team can also choose different community governance models such as 1-token-1-vote, 1-token-multi-votes, and voting dividends.February 6, 2019● EOSForce was invited to attend the discussion forum held by EOS Israel on February 6, 2019, to discuss the future development of the EOS sister chains and how to promote the prosperity of the EOSIO ecosystem with the community leaders of the global EOS sister chains.February 28, 2019● At the 10th BP Meeting of EOSForce Mainnet, the Secretariat summarizes and reports the work of the 2nd session of the Secretariat, and BPs discuss and vote on the Secretariat Salary Proposal and No Redemption Period for Changing Vote Proposal.April 10, 2019● Sky.eosc Node initiated the discussion on the Proposal to Destroy Tokens in Unactivated EOSForce Genesis Accounts.April 22, 2019● The 3rd Secretariat of EOSForce Mainnet held a community governance discussion on Sky Node’s Proposal to Destroy Tokens in Unactivated EOSForce Genesis Accounts, Blockpro Node’s Proposal to Freeze and Destroy B1 Accounts and the Secretariat’s Secretariat Reform Proposal.April, 2019● Tokenview had joined EOSForce Mainnet as block producer, will develop new block explorer for EOSC, wallet support, EOSC DApp portal and related incentive plans.May 16, 2019● Xiwu, co-founder of EOSForce, was invited to attend 2019 Global Blockchain (Hangzhou) Summit Forum on May 16, 2019, to discuss the future development of blockchain with blockchain experts and practitioners at home and abroad.May, 2019● Block.one released EOSIO 1.8.0. EOSForce Development Team immediately interpreted the new version of EOSIO 1.8.0 and pointed out that EOSIO 1.8.0 will set the tone for EOS.IO’s rapid iteration through hard fork upgrades in the future. It will also make the entire blockchain industry re-examine the importance of hard fork upgrades.May 30, 2019● EOSForce Development Team released suggestions for improvements to the EOSForce mainnet and potential solutions, and community members participated in the discussion.June 5, 2019● EOSForce Community started a community governance opinion collection activity on June 5th, and those who provided opinions and were accepted could get lipstick gift rewards. This event will run until June 10.July 10, 2019● Jeepool BP, Jiuzhou Capital and the Development Team jointly initiated EOSFORCE Mainnet Improvement Proposal V1.0, which involves inflation rate adjustment, voting weight adjustment, block-producing reward, punishment mechanism, decentralized budget system and referendum system.July 11, 2019● Cyborg, founder of EOSForce, was invited to attend the AMA event of Great Chinese Public Chains held by FIND(区分) to share EOSForce Mainnet governance mechanism and cross-chain exploration.July 18, 2019● EOSForce Mainnet has completed upgrading to V1.6.0, supporting 2 resource models.● At the 11th EOSForce Mainnet BP Meeting, BPs have voted to pass the EOSForce Mainnet Improvement Proposal jointly proposed by Jeepool Node, Jiuzhou Capital and Core Team. The proposal involves inflation adjustment, voting weight adjustment, block-producing reward and punishment mechanism. The proposal was reaching passage at a 2/3 overmajority and passed.July 26, 2019● The airdrop activity of “Talk is cheap,show me the code” was held in EOSC communily.July, 2019● EOSForce Founder Cyborg was invited to attend Blockchain Technology Empowerment Industry Seminar co-hosted by Deep Chain, Ningbo Government and cyzone in Ningbo.August 2, 2019● EOSForce Founder Cyborg was invited to KuCoin China Tour and delivered an internal speech on “Governance Goals of Cryptocurrency Community”.August 3, 2019● JiqiX Node initiated A Proposal to Adjust The Upper Limit of EOSC Mainnet Contract Deployment.August 7, 2019● Cyborg was invited to visit eosou.io community, analyzing and discussing on the evolution of EOSC economy model in depth.August 10, 2019● EOSC Mainnet Contract Size Adjustment Proposal proposed by JiqiX has been approved by the multisig of more than 2/3 of the BPs.August 13, 2019● Sky.eosc Node and Awake Node initiated A Proposal to Destroy the Unactivated Genesis Accounts and Tokens. It is proposed to destroy 80% locked genesis accounts and their tokens, 20% unactivated genesis accounts and tokens of Unactivated Genesis Account LockupPlan Proposal FIP#3.August 14, 2019● Cyborg was invited to attend HyperDAO Open Class to discuss the community governance mechanism and the new development of Staking economy.August, 2019● Hexlant and Koreos, two major EOSIO communities in South Korea, launched EOSC airdrops to strengthen the EOSC community.August 19, 2019● World-renowned comprehensive blockchain services provider BEPAL has officially become a Node of EOSForce mainnet. It will participate in the construction of EOSForce mainnet ecology together with EOSForce community, aiming to provide a more convenient and excellent blockchain service to EOSForce community.August 21, 2019● The 12th EOSC Mainnet BP Meeting was held successfully. BPs voted to pass A Proposal to Destroy the Unactivated Genesis Accounts and Tokens and A Proposal to Adjust the Allocation Plan of B1 Account Tokens.August, 2019● The term of EOSC Mainnet BP Meeting Secretariat has been changed successfully. Tokenview, sky.eosc, eosou.io and Captain Force will serve as members of the 4th Secretariat.● The upgrade of EOSC mainnet v1.7.0 has been completed, and the fixed voting function and punishment mechanism have been launched.August 29, 2019● EOSC Mainnet held the 13th BP Meeting to discuss the problems on the development of FIP#9 Destruction Proposal and the new proposal.September, 2019● One-Stop Digital Asset Service Platform CoinAll has successfully run for EOSC mainnet BP.● EOSwriter original video production series Heidi Asks invited EOSForce founder Crborg and core developer Fan Yang to discuss everything EOSForce.September 19, 2019● The upgrade of EOSC mainnet v1.7.1 has been completed, and all the functions in FIP#7 Mainnet Improvement Proposal have been launched, including inflation rate adjustment, fixed voting, block reward, punishment mechanism and decentralized budget system.September 20, 2019● The Secretariat of EOSC community open the registration for Management Committee Election, and any individual or organization can participate in the election of Management Committee members. 5% of all approved proposal fees automatically goes to the Management Committee’s salary account as a salary for the Management Committee members.September 27, 2019● EOSC mainnet nodes have completed the multi-sig for the Proposal to Adjust RAM Rental Price proposed by eosawake and sky.eosc, which has officially taken effective on September 26, 2019 (UTC+8). The current price of RAM on EOSC mainnet is to deposit 2 EOSC to get 1KB of RAM.October 10, 2019● The freezing execution of unactivated account balance has been completed. The unactivated account balance is not able to vote or transfer. FIP#11 officially takes effect.October, 2019● EOSC Founder Cyborg was interviewed by Chain Teahouse to explain the significance of the existence of high-performance low-latency computing public chain.● The 1st EOSC Management Committee was established. The members are: Shede-eosawake, Damao-Jeepool, Wang Wei, Yibao-Bepal, Yi Chuanqi-EOSC Developent Team.October 12, 2019● The 1st Meeting of The 1st EOSC Budgeting Committee (EDBS-1) was held.October, 2019● The English community successfully held a community promotion campaign, attracted thousands of users to participate in the campaign, and the number of the community members doubled.● The famous blockchain Youtuber in the Arab region made an introduction video of EOSC.October 29, 2019● The EOSC develop team announced to join the CoinEx Chain pre-election node process, and will conduct a series of in-depth cooperations with CoinEx in cross-chain technology, blockchain virtual machines and privacy computing.November, 2019● EOSForce BP Management DAPP Platform, the first budget application of EOSC Decentralized Budget System initiated by Awake Node has been issued to the applicant’s account at the block height of 14401927.December, 2019● The Secretariat of EOSC Maine BP Meeting released Statute of The Secretariat of EOSC Maine BP Meeting to coordinate opinions on community governance, promote the effectiveness of the governance proposals on the chain, and maintain the consensus of EOSFORCE mainnet.● EOSC Founder Cyborg took an interview by EOS Summit to discuss the operation of the decentralized budget organization and talk about the development vision of the blockchain in 2020.● The Secretariat of EOSC Maine BP Meeting released Statute of The Secretariat of EOSC Maine BP Meeting to coordinate opinions on community governance, promote the effectiveness of the governance proposals on the chain, and maintain the consensus of EOSFORCE mainnet.

EOSFORCE

20. 01. 19

2019 in Review: A Brief His...

Time never lives, time never flows. As 2019 came to a close, bringing a brand new year. In 2019, as the core development team of EOSC Mainnet, EOSForce Development Team fully abided by the governance rules and the popular will in EOSC community, provided the technical implementation for FIP4–FIP15 approved by BPs and implemented the technical development and test on projects of half nodes, light nodes, EOSC development toolsets and CODEX.IO. Besides, some code refactoring has been done and some support for related libraries has been improved.With a continuous iterative evolution over the past year, the EOSC mainnet has achieved significant improvements in terms of throughput performance, security, and stability, and its comprehensive performance has reached a new level. At the same time, the emergence of EOSForce.CDT, EOSC Web IDE and other tools has also supplemented the developer tools of the EOSC mainnet.Looking ahead to the new year of 2020, EOSForce development team will continue to focus on the research and development of the underlying technology of the blockchain, and work with the EOSC community to promote the EOSC mainnet towards a decentralized high-performance smart contract platform.Here is a look back at EOSC’s technical development in 2019.12/23–12/29Weekly Report #74Reconstructed the eos-p2p support library, improved log interface and processing.Implemented the block storer interface of eos-p2p library to realize an interface based on bbolt for the test, and added a irreversible decision function to the storer interface.Added a sending transaction interface to the light node.Codex.io supported in the light node.Merged the update of EOSIO v1.8.7 with EOSC.12/16–12/22Weekly Report #73Reconstructed the eos-p2p support library, improved the support for messages’ integrity, improved the exit processing, designed the block storer interface of eos-p2p library.Designed the light node block DB to support for confirming block irreversibility.Merged the performance optimization commit of EOSIO debug branch to test the compatibility.Researched the progress of filecoin project, set up filecoin test network node.12/09–12/15Weekly Report #72Tested the branch of Codex.io v2.0.x, and fixed the synchronization problem.Tested the branch of EOSC v2.0.x.Reconstructed the light node, improved the exit support.Reconstructed the eos-p2p support library to improve the integrity of message processing.Researched the performance optimization commit of the recent EOSIO debug branch.Researched the progress of filecoin project, evaluated the compatibility of filecoin bridge tool with EOSIO ecology.Participated in and completed the process of filecoin trusted setup Perpetual Powers of Tau.12/02–12/08Weekly Report #71Merged the update of EOSIO v1.8.6 with EOSC and Codex.io.Tested the compatibility of EOSIO v2.0.x branch with EOSC and Codex.io.Collated the P2P protocol changes of the EOSIO v2.0.x branch.Reconstructed the light node to better adapt Codex.io and EOSIO.Improved the support for the interactive development of Codex.io and EOSC.Improved Codex.io’s support for Kafka.11/25–12/01Weekly Report #70Improved the support for the interactive development of Codex.io and EOSC.Designed the support plan for Codex.fc supporting multiple hash algorithms.Researched the chain-running solution of Codex.io running based on Golang.Implemented the static declaration feature of the contractual account on Codex.io, and researched the adaptation of EOSC to it.Improved Codex.io unit test.Improved the support for EOSC wallet, fixed the bug.11/18–11/24Weekly Report #69Fixed the problems with Codex.io merged with eosio 2.0.x, tested the applicability of new features in Codex.io 2.0.x.Improved the unit test of EOSC and Codex.io.Researched the development plan of Codex.fc supporting different encryption algorithms.Researched EOSC data index query scheme.Redesigned the chain startup proces of Codex.io, removed the dependency of the genesis contract.Added a declaration feature of the contractual account on Codex.io.11/11–11/17Weekly Report #68Merged eosin 2.0 rc with Codex.io.Researched the extent to which new features are applicable in EOSC.Improved support for EOSC unit test, added test cases corresponding to the EOSC function.Developed EOSC half-node.Transplanted history_tools to adapt EOSC.Researched the progress of the filecoin project.11/04–11/10Weekly Report #67Tested EOSC Token Exchange contract, and optimize the contract based on community feedback.Improved support for EOSC unit test, added test cases corresponding to the EOSC function.Collated EOSC document, added document related to new features.Developed EOSC half-node framework, completed the design of chain framework.Improved the EOSC goeosforce library, add new feature support.Investigated the adaptation of history_tools to EOSC.Investigated the progress of the filecoin project.10/28–11/03Weekly Report #66Completed EOSC Token Exchange contract, coordinate with the community to start the test.Completed EOSC Token Exchange data query plugin.Improved support for EOSC unit test, added test cases corresponding to the EOSC function.Collated EOSC document, added document related to new features.Complete the technical document of EOSC’s first sub-chain plan, designed cross-consensus prove mechanism.Built EOSC half-node framework, tested the performance of EOSC half-node.10/21–10/27Weekly Report #65Merged the update of EOSIO v1.8.5 to EOSC.Improved support for EOSC unit test, new features and support for EOSC on-chain config.Improved eosc_api_plugin to integrate EOSC-specific API.Completed the technical document of EOSC’s first sub-chain plan, developed light node demo, and tested synchronization performance.Developed EOSC Token Exchange contract.Investigated EOSIO Web IDE, collated and released the introduction document.10/14–10/20Weekly Report #64Tested EOSC v1.8.3.Improved support for EOSC unit test framework, tester supported EOSC test environment.Added eosc_api_plugin to integrate EOSC-specific API.Collated EOSC document, add the modifications as of v1.8.3.Added updateconfig function to EOSForce contract to facilitate adjustment of chain parameters.Designed EOSC sub-chain architecture solution, organize EOSC heterogeneous cross-chain framework.Developed EOSC Token Exchange contract.10/07–10/14Weekly Report #63Coordinated with the community to implement FIP#11.Merged the update of EOSIO v1.8.1 with EOSC.Reconstructed the code structure of EOSC Transaction fee to reduce the difference with EOSIO.Organized EOSC Http RPC API design, integrated the EOSC-specific API, and maintained compatibility with EOS.Collated EOSC state_history_plugin support plan , designed history_tool transplantation plan.Fixed some EOSC Bug, completed key notes.Designed EOSC voting incentive performance optimization plan.Investigated EOSC sub-chain architecture solution and designed EOSC heterogeneous cross-chain framework.Improve the support for EOSC Decentralized Budget System page.09/23–09/29Weekly Report #62Coordinated with the community to plan EOSC v1.8.2 upgrade process and program.Coordinated with the community to test the account freezing procedure and other functions on the test network.Merged EOSIO v1.8.2 with Codex.io.Merged EOSIO v1.8.2 with Codex.relay.Optimized Codex fee mechanism based on the change of EOS v1.8.x structure.Designed the support plan for Codex.io cross-chain verification.Improved Codex.relay economy model requirements.Designed EOSC voting incentive performance optimization plan.09/16–09/22Weekly Report #61Coordinated with the community to complete the upgrade of v1.7.1.Merged EOSIO v1.8.3 with EOSC.Tested EOSC v1.8.x branch, and released EOSC v1.8.2.Coordinated with the community to test the account freezing procedure and other functions on the test network.Improved the Docker support for EOSC v1.8.2.Improved the front-end support of the decentralized budget system.Communicated with the community about EOSC new technology roadmap.09/09–09/15Weekly Report #60Tested the activation process of new functions of EOSC v1.8.0.Completed the accounts freeze function passed by FIP #11, refined the process document.Tested the support for EOSC snapshot.Cooperated with the community to test the decentralized budget system and other functions on the test network.Cooperated with the community to improve EOSC mainnet node network topology and strengthen the stability of EOSC mainnet.09/02–09/08Weekly Report #59Tested the compatibility of sync blocks on EOSC v1.8.0, fixed the appeared problems.Improved the support for EOSC snapshot.Optimized the Node Punishment Mechanism, fixed the design that affects performance.Reconstructed EOSC node heartbeat plugin.Integrated the on-chain configuration and feature-related functions of EOSC.Transplanted a new EOSJS library for EOSC, collated JS development document.Cooperated with the community to launch EOSC test network, and made preparations for the update of new functions.Improved the front-end support of the decentralized budget system.08/26–09/01Weekly Report #58Merged EOSC with v1.8.0, tested the compatibility of sync blocks.Improved EOSC Budget System Contract.Fixed the problem about EOSC Docker mirror.Fixed the problem about Node Punishment Mechanism.Collated the implementation of Codex.io and Codex.Relay for the preparation of merging with EOSIO v1.8.0.Collated new EOSC Docker mirror operation document.08/19–09/25Weekly Report #57Cooperated with the community to update EOSC system contract and complete the upgrade of v1.7.0.Collated the design plan of Codex.Relay new economy model.Fixed voting supported in EOSC wallet.Merge EOSC with eosio v1.8.0.Reconstruct the codes of Codex.relay system contract according to the new cdt.Reconstructed EOSC docker support according to the community feedback.08/12–08/18Weekly Report #56Tested EOSForce new system contract, and prepared for the update of v1.7.0.Tested the merged version of Codex.relay, and fixed the compilation problem.According to the community feedback, added Action of revoting based on the unredeemed vote to the fix-time voting and current voting system contract.Added a temporary extension interval to support the system contract update.Collated the design plan of Codex.Relay new economy model , and updated Codex.Relay system contract accordingly.Tested the compilation of the upgraded EOSForce compiler version to merge with EOSIO v1.8.0 conveniently.Collated the new EOSForce system contract document.Reconstructed the codes of Codex.relay system contract according to the new cdt.Improved the support for the new feature of the wallet.08/05–08/11Weekly Report #55Released EOSForce mainnet v1.7.0 with a series of APIs added to simplify the development of chain-related applications.Implemented the punishment mechanism for block missing.Implemented EOSForce decentralized budget system.Refined EOSForce Docker support according to the community practice.Collated the new EOSForce system contract document.Reconstructed the codes of Codex.relay system contract according to the new cdt.Confirmed the plan of extending and improving the voting-related Action to enhance user experience.The wallet supported fix-time voting.07/29–08/04Weekly Report #54Planned the upgrade of EOSForce mainnet v1.7.x.Recomposed EOSForce system contract document, refined the mechanism description, and added the new functional description.EOSForce chain API added the interfaceof get_vote_reward to obtain the account voting reward value.Improved EOSForce heartbeat mechanism, simplified the heartbeat-related configurations.Implemented the punishment mechanism of block missing.Designed the plan of on-chain account system of EOSForce decentralized budget system.Designed the plan of block extension information compatible with EOSIO v1.8.x and subsequent versions.Designed the plan of on-chain account system of Codex decentralized budget system.Refined the testing of Codex.relay transaction contract unit.07/22–07/28Weekly Report #53Designed a stability mechanism of EOSForce BPs with the implementation of counting statistical block-missing data and historical block-missing data.Implemented fix-time voting function of EOSForce.Added the API for getting chain setting information to EOSForce.Added the API for getting Action Fee information to EOSForce.Implemented the common Margin Contract of EOSForce.Refined the startup script of EOSForce test net based on the recent modification.Refined the new EOSForce system contract file.Implemented the optimization of integrating Codex.IO and Codex.relay with EOSForce.Refined the testing of Codex.relay transaction contract unit.Refined the layout of Codex.relay Depositing & Rewarding Model and some related formulas.07/15–07/21Weekly Report #52Transplanted the new EOSForce system contract of eosio.lock and eosio.msig.Implemented the common assetage mechanism and unicode.Added global voting state to display voting data and efficiency of optimization and execution.Improved Ricardian Contract of EOSForce system contract.Reconstructed the code of EOSForce system contract, adjusted the code structure.Updated EOSForce system contract based on the new EOSForce economic model schemeCooperated with the community to update EOSForce mainnet to force-v1.6.0, preparing for the subsequent updates.Cooperated with the community to test Codex cross-chain system.Fixed the Codex.Relay problem reported in the testing.Planned the development of EOSForce system contract according to FIP#7 proposal.Designed the scheme of EOSForce fix-time voting, planned the update of compatibility mechanism.07/08–07/14Weekly Report #51EOSForce.cdt improved the support for EOSForce API and fixed abi generation problems.EOSForce system contract modified for cdt compatibility.Tested the new EOSForce system contract based on EOSForce.cdt.EOSForce merged EOSIO 1.7.4 updates.Planned the implementation plan and update steps of EOSForce new economic model.Cooperated with the community to test Codex cross-chain system.Fixed the Codex.relay issues found in the test.Codex.relay contract code reviewed and conducted Codex.relay performance testing.EOSForce Transaction version data compatibility tested.Planned the modification scheme of EOSForce Transaction compatibility with EOSIO HTTP API plug-in.Designed wallet modification scheme based on EOSForce new economic model scheme.Optimized the implementation of configuration contracts on EOSForce chain to simplify the following update steps.07/01–07/07Weekly Report #50Cooperated with the community to upgrade EOSForce mainnet.Cooperated with the community to test Codex cross-chain system.Improved the new EOSForce economic model scheme and delivered the final scheme document.Improve the new Codex economic model scheme.Fixed the Codex.relay transaction contract issues.Codex.relay contract code reviewed and the code style optimized.Added transaction data’s version into EOSForce transaction extension data to be compatible with EOSIO transaction structure.Provide technical solutions to scatter issues.06/24–06/30Weekly Report #49A new EOSForce governance mechanism scheme discussedPrepared EOSForce mainnet upgrade and reviewed the code implementation of resource model extensionOptimized the code of EOSForce system contract, referred to the Codex implementation for improvement and optimized the performance of onblockAccording to the results of Codex.Relay contract code review, reconstructed part of the contract implementation, optimized the code structure of contract and improved execution performanceCooperated with the community to test Codex cross-chain systemPlaned a solution to improve the compatibility of EOSForce, and solved a complex migration problem caused by different transaction structures06/17–06/23Weekly Report #48Cooperated with the community to test Codex cross-chain systemFixed the problems of Codex.Relay transaction contract found via testingOrganized and translated Codex related documentsCompleted the public test account and test Token receiving pageCompleted automatic configuration scripts for Trunk nodesTrunk supported configuring multiple RPC urls to accommodate EOS network jitterGet_currency_balance API supported relay.Token contractReviewed the EOSForce system contract code and planned some improvements of Codex system contract to be merged into the EOSForce06/10–06/16Weekly Report #47Cooperated with the community to test Codex cross-chain systemImproved Codex.relay API according to the testing resultsImproved the issues templates of Codex and EOSForceDesigned an automatic configuration tool for TrunkEOSForce cleos tools supported the newly extended resource model functionImproved the Codex document system and translated the documents into English versionPerfected the support for codex.cdt and completed its adaptation to codex.relay.contractsCodex.relay.contracts supported enuImproved codex-js, the javascript support library of Codex06/03–06/09Weekly Report #46Prepared for the first round of community testing of Codex cross-chain systemSubmitted Codex related projects and improved project’s introductionMongo_db plug-in supported Token contract parsingOptimized the implementation of Codex Trunk to simplified the configuration informationImproved PR template for EOSForce projectCodex.relay’s code reviewedBuilt Codex document system and improved content of the documents05/27–06/02Weekly Report #45Operational testing of FORCEIO cross-chain economic modelImproved transaction contracts based on testing results: improved the inspection mechanism to return more explicit error information and simplified the fee deduction mechanismImproved relay node based on testing results: improved error handling mechanism to adapt to network fluctuations of different blockchains and improved information on the blockchain to simplify the use of relay nodesOptimized the support for mongodb plug-in and splited some fields for easy useEOSForce system contract optimized code structure based on 1.6.x CDTOptimized FORCEIO cross-chain system contracts and adjusted resource usage to simplify user operationsFORCEIO relay contract code reviewedUpdated FORCEIO relay contract documentsDesigned the config-on-chain function of EOSForce, adapted to the implementation scheme of eosio feature mechanism05/20–05/26Weekly Report #44FORCEIO relay chain linked to EOSIO and EOSForce mainnetFORCEIO relay contract code reviewedUpdated FORCEIO relay contract documentsEvaluated EOSIO 1.8.x updates and planned EOSForce and FORCEIO update schemePorted the public beta version of the FORCEIO relay contract to support testing based on test TokenAdded the order action in the transaction contract, and informing mongo_db plug-in to insert into orderbookOptimized transaction contract execution actionImproved mongo_db plug-in, updated orderbook and transaction record tableEvaluated the eosio-explore port scheme05/13–05/19Weekly Report #43FORCEIO cross-chain economic model operation testedFORCEIO relay contract code reviewed and implementation optimized partlyFORCEIO relay contract documents updatedFORCEIO contracts adapted to cdt updatesFORCEIO relay contract voting and mining logic optimizedEOSForce Token contract supported the function of renting and recycling Token information memory05/06–05/12Weekly Report #42The relay chain’s transaction contract supported opening transaction pairs by mortgaging TokenThe relay chain’s transaction contract supported accounting function for users’ custody fund and the function of deducting handling fee with tokensThe relay chain’s inflation model modifiedImproved the fault BP punishment scheme of relay chainFORCEIO merged EOSIO 1.7.x updatesEOSForce tested the version merged with EOSIO 1.7.xForce-go reconstruction, p2p modules compatible with EOSIO, FORCEIO, EOSForce and other EOSIO isomorphic blockchainsFORCEIO relay nodes supported multiple EOSIO isomorphic chainsEOSForce, FORCEIO integrated development tool and eosio.cdt updatesFORCEIO.contracts adapted to cdt updatesFORCEIO modified the block extension data format to increase compatibility between chains04/22–04/28Weekly Report #40FORCEIO cross-chain transaction contract matching logic optimizationFixed FORCEIO issues found in cross-chain function testingFORCEIO relay chain supported modifying accuracy of transaction pairsFORCEIO system contract migrationFORCEIO wallet functionality improvedEOSForce merged with FORCEIO golang library and improved the implementation of p2p libraryRelay nodes supported quick confirm mode04/15–04/21Weekly Report #39FORCEIO cross-chain economic model implementation testedFORCEIO IBC related operations testedEOSForce system contract upgraded and EOSForce. CDT API prefectedFORCEIO wallet functionality improvedFORCEIO IBC relay contract refactored and fixed issues found by testingFORCEIO documents organizedInvestigated EOSForce REX adaptability04/08–04/14Weekly Report #38FORCEIO cross-chain wallet developmentImplementation of FORCEIO cross-chain economic model testedFORCEIO IBC related operations testedFORCEIO multi-chain projects organizedFORCEIO IBC solution documentation organizedFORCEIO command-line tools supported IBC related operationsEOSForce extending CPU resource model demo testedBus plug-ins adapted EOSIO and EOSForce04/01–04/07Weekly Report #37FORCEIO cross-chain economic model tested and the test data organizedFORCEIO.cdt added the function of configuring blockchain’s genesis informationFORCEIO IBC solution side-chain relay contracts added channel exception handling mechanismFORCEIO extended the CPU resource model to support coinage-based paymentEOSForce adds a demo of extending CPU resource model for testingPorted FORCEIO cross-chain system contract to FORCEIO.CDT implementationPlanned the development plan of EOSForce.cdt implementation, which would greatly reduce the threshold for developers to migrate03/25–03/31Weekly Report #36Initial release of FORCEIO cross-chain economic model completedReconstruction scheme of EOSForce fee model designedReconstructed the side-chain relay contract of FORCEIO IBC solution to be independent on specific blockchainFORCEIO IBC solution side-chain relay contract supported for EOSIO and FORCEIOEconomic model related functions of FORCEIO relay-chain client wallet completedFORCEIO cross-chain solution improved support for nodes operation, and the testnet built03/18–03/24Weekly Report #35FORCEIO relay chain economic model implementation scheme design and the preliminary framework completedFORCEIO IBC EOSForce sidechain relay contract implementedEOSForce contract development toolset refactored, transferred to https://github.com/eosforce/eosforce.cdtFORCEIO Checker node improved support for DockerFORCEIO relay chain client wallet developedFORCEIO relay chain transaction data storage function implementedEOSForce system contract update completed with the communityFORCEIO relay chain transaction contract documentation updated03/11–03/17Weekly Report #34EOSForce mainnet update completed with the communityFORCEIO Checker node relay function completedFORCEIO IBC solution improved transaciton contracts based on requirementsEOSForce merged the latest ELMG EOS updatesFORCEIO IBC solution economic model improvedFORCEIO ported CDT development toolsetFORCEIO golang library improvedFORCEIO client command line tools supported transaciton contractsEOSForce client adds the function of switching voting with no freezing period03/04–03/10Weekly Report #33FORCEIO IBC solution transaction contract completedFORCEIO IBC solution node realized the support for Docker-imageFORCEIO IBC solution relay contract added the confirm functionEOSForce new version testing finished and some issues fixed02/25–03/03Weekly Report #32FORCEIO IBC solution transaction contract refactoredFORCEIO IBC solution transfer node realized the block-transferring functionFORCEIO improved support for Docker and added Docker image for testnetFORCEIO IBC solution economic model improvedFORCEIO relay chain testing02/18–02/24Weekly Report #31FORCEIO IBC solution relay chain project v0.1.0 completedEOSForce prepared for version update and merged the previous proposalsFORCEIO cleared up the dependencies and removed GRPC submodulesEOSForce BP fault handling mechanism completedFORCEIO transaction contract improvedFORCEIO IBC economic model design02/11–02/17Weekly Report #30The FORCEIO IBC program completes the first phase of developmentEosforce design bp fault handling mechanism02/04–02/10Weekly Report #29FORCEIO developed basic cross chain mapping functionFORCEIO transplanted eos-go library, and merged the latest update to forcec and goeosforce libraryFORCEIO supported in forcec client tool.EOSForce supported transaction expansion data and context-free actionsEOSForce fee optimized, fee limit parameters addedEOSForce maximum transaction size supported on-chain multisigEOSForce cleos tool refactored code structure, fee-related parameter supported01/28–02/03Weekly Report #28FORCEIO IBC relay chain solution BP mode relay contract developmentFORCEIO IBC relay chain solution implemented Token swap contractFORCEIO golang client chain library implemented for the development of related toolsFORCEIO performance testing tool implemented01/21–01/27Weekly Report #27FORCE IBC completed the basic contract framework of relay contract development of relay chain BP modeFORCEIO added bus pluginFORCE IBC implemented the Mapping Token contract on the relay chainFORCE IBC designed token swap contract implementation plan.FORCEIO refactored account name implementation, customized account name format supportedFORCEIO refactored system contract initialization implementationFORCEIO supported in goeosforce libraryFORCEIOFORCEIO improved support for wallet01/14–01/20Weekly Report #26FORCEIO supports customizing resource model and voting mode by compiler options.FORCEIO supports one-token-multi-votes.3. FORCEIO supports blacklist mechanism on blockchain.FORCEIO supports customizing system contract accounts by compiler options.Release the highly customizable blockchain FORCEIO 0.1.0.Cooperate with the community to update EOSForce mainnet to version 1.4.1.Refine the English support documents of EOSForce.EOSIO 1.5.4 update merged into EOSForce.01/07–01/13Weekly Report #25FORCEIO supported in the EMLG EOS resource modelEORCEIO supported in the free resource modelRefactored the FORCEIO Voting Mode: Split voting process and mortgage processCompleted the plugin and contract for candidate BP node online status verification to EOSForceOrganized the documentation of FORCEIO customizationOptimize the function to use wallet to modify the account key12/31, 2018–01/06, 2019Weekly Report #24FORCEIO added native layer contract supportSplited the system contract function to improve the robustness of FORCEIO system.EOSForce multisig update contract function supportedFORCEIO fee implementation refactoredFORCEIO BP dividend mechanism implementation refactoredFORCEIO BP status heartbeat synchronization scheme designed

EOSFORCE

20. 01. 12

Shuyu Unveils Achievements ...

Shuyu’s Achievements in Blockchain Traceability Technology: From Beijing to Africa were unveiled on Dec 16th at a demonstration conference jointly held by the Embassy of the Republic of Sierra Leone, Beijing Association of Quality Inspection Certificate, Beijing Law Association of Technology Inspection, Beijing Social Enterprise Quality Association and IIAB Credibility&Brand Blockchain Research Institute.More than 40 entrepreneurs and representatives from various industries in the capital participated in this demonstration, which aims to promote the combination of Shuyu’s new achievements in blockchain traceability technology and with traditional industries, and help enterprises to realize the full-chain anti-counterfeiting traceability with higher efficiency and lower cost through Shuyu Blockchain Traceability Coordinated Middle-End.Shuyu Blockchain Traceability Collaborative Middle-End creates a fair and credible supply chain collaborative ecology based on blockchain technology system. Using smart contract technology, a value flow platform of trust and service is built.Data isolation technology is used to ensure the privacy of multiple parties.Digital signatures, blockchain immutability and Internet of Things technologies are used to trace the entire product life cycle of the product’s logistics, capital flow and information flow to the minimum, helping retailers, brands, manufacturers, logistics and warehousing to efficiently collaborate to transform to new retail.Rogers, Deputy Ambassador of the Embassy of the Republic of Sierra Leone to China, Minister Kamara, Zhouyi, Senior Commercial Counselor, also the President of China-Africa International and Editor-in -Chief of IIAB, Lingzhiyi, President of Beijing Association of Quality Inspection Certificate, Liu Tianfeng, Vice President of Beijing Community and Business Association of Quality, Wang Ruihua, Secretary General of Beijing Technical Supervision Law Association, and Dai Lin,President of llAB Guangdong Branch attended this conference. Chang Qing, the Guest Commentator, hosed the conference with the entrustment of Ye Huiya, Editor-in-Chief of IIAB.Rogers (front right), Deputy Ambassador of the Embassy of the Republic of Sierra LeoneRogers, Deputy Ambassador of the Embassy of the Republic of Sierra Leone to China (front right) delivered a speech representingGovernment of the Republic of Sierra Leone and all Diplomats in the Embassy. He expressed his delightedness of holding this demonstration conference of the latest blockchain technological achievements, and the hope that China’s blockchain technology can enter Sierra Leone and the whole of Africa, and play a leading role in science and technology in the construction of the Belt and Road Initiatives to bring a continuous development to Sierra Leone and Africa.Kamara(front right), Minister of the Republic of Sierra LeoneKamara, Minister of the Republic of Sierra Leone, delivered a welcome speech representing all Diplomats in the Embassy. He welcomed Chinese friends and entrepreneurs with a opening of “China Hooray!”. He also hoped to promote the latest achievements of the blockchain into Sierra Leone and the whole of Africa, and welcomed Chinese outstanding entrepreneurs to come to Sierra Leone for investment and development.Ling Zhiyi, President of Beijing Association of CertificateAt the speech by Ling Zhiyi, President of Beijing Association of Certificate, it was mentioned that he had paid special attention to new blockchain technology. As an old leader who has been engaged in quality inspection and certification for many years, he knew that the problem of counterfeiting is serious and it is not easy to crack down on counterfeiting. Although many companies have put in a lot of effort for this, the results are not very satisfactory. Can blockchain really solve the problem of traceability and anti-counterfeiting? The government and enterprises are very concerned. And he hoped that the blockchain technology can be recognized by the government and enterprises and contribute to China’s economic construction and quality power strategy.Shi Jingyao, President of IIAB [Credibility&Brand] Blockchain Research Institute, the founder of Shuyu Technology Co.LtdShi Jingyao, President of IIAB [Credibility&Brand] Blockchain Research Institute, also the founder of Shuyu Technology Co.Ltd, made a presentation of Shuyu’s achievements in Blockchain Traceability Technology. At the presentation, this youth blockchain expert introduced that “Blockchain traceability is just an instrumentality. The ultimate goal is to collect the data to a collaborative middle-end on the premise of ensuring the security of data privacy.Then it will serve enterprises and products to realize the transformation of production relations, promote the transformation of the business ecosystem from production-driven to demand-driven, and further solve the inventory problems of enterprises and retailers.”Then he gave an example. The original inventory plan was formulated based on the data reported from the upper layers of the channel. This is prone to problems of data amplification and information distortion, which makes it easy for channel dealers to accumulate a large amount of inventory, bringing huge losses to consumers and channel dealers. If the goods can be traced from the source to the retailer through Shuyu Blockchain Trace Middle-End, the channel dealer can obtain big data from the countless sales ends of the front end, then backward infer how many goods need to be produced this year, and which stars and internet celebrities can be launched to reach the target consumers to achieve precise demand-driven guidance.Shi frankly said that he didn’t like applying for patents, and he hoped to share his strength for the blockchain industry through open source. He has contributed hundreds of thousands of lines of code to the blockchain industry and developed a set of blockchain service platform to help developers quickly start the blockchain. He believed that blockchain is not a vent, industry, or technology, but a brand new era. Blockchain technology can remove the trust intermediary, reduce everyone’s trust cost, and ultimately reshape the entire trust ecosystem.Dai Lin, President of llAB Guangdong BranchAs a pioneer and advocator of blockchain technology, Dai Lin, President of llAB Guangdong Branch, expressed her interest in blockchain. She mentioned that for enterprises, if they use blockchain technology to trace the source, trust in the enterprises can be built while consumers are purchasing their products. Because blockchain traceability proves that there are no fakes in the market. From a business perspective, blockchain traceability technology can generate considerable benefits because this technology effectively helps companies reduce costs and increase efficiency.Lin Wenbin, Vice President of IIAB [Credibility&Brand] Blockchain Research Institute, is one of the main collaborators of this technical team. He said that Shuyu Blockchain Traceability Middle-End is a blockchain application with few benign profit models currently on the market. In the early stage, it will focus on the traceability of the supply chain of beauty products. He also mentioned that Shuyu Technology has rich experience in blockchain application development.Significant results have been achieved in the development of the equity trading platform for a domestic well-known fund through blockchain certificate and smart contract technology, as well as the order and checkout system for urban service providers of large domestic automobile groups by utilizing the immutability and transparency of blockchain.During the conference, a PPT made by Jiang Zhe, Deputy Secretary of IIAB [Credibility&Brand] Blockchain Research Institute, briefly introduced the development of [Credibility&Brand] (llAB) in recent years. [Credibility&Brand] (llAB) was first published in Hong Kong, China in April 2016. During the past 4 years, it has set branches in Beijing, Hong Kong(China), Jiangsu, Shenzhen, Guangzhou, the United States, the United Kingdom, Switzerland, France, Italy, Germany, Singapore, Africa, Malaysia( and other countries and regions. Many celebrities such as world-class politicians, Ambassador s to China and entrepreneurs have been on the magazine cover, including Former French Prime Minister Raffarin, Ambassadors to China of Switzerland, Chile, Botswana, Benin, France, Benin, Italy, Sierra Leone and many other countries, the renowned pianist Lang Lang, etc.Mr. Cui Shunli(right), Chairman of Long Way Lihua (Tianjin) Culture Development Co., Ltd.Representatives fromwell-known companies, academia and media had also been invited to attend this demonstration of Shuyu’s Achievements in Blockchain Traceability Technology, which met with much applause from the guests. Mr. Cui Shunli, Chairman of Long Way Lihua (Tianjin) Culture Development Co., Ltd. expressed his great interest in Shuyu’s new achievements in blockchain traceability. He hoped to have an in-depth discussion with Mr. Shi Jingyao on the traceability of wine brands under his company, and hoped that through the blockchain traceability technology, the market trust problem of high-quality wines can be solved, and consumers can be provided with more adequate authenticity.Guests took a group photo after the meeting.Guests took a group photo after the meeting. From left to right: Lawyer Tu Shaohua, Director of Beijing Haoting Law Firm; Mr. Cui Shunli, Chairman of Long Way Lihua (Tianjin) Culture Development Co., Ltd.; Zhou Chunlai, Director of Beijing Educational Supervision and Education Center; Zhou Yi, Senior Commercial Counselor, also the President of China-Africa International; Ling Zhiyi, President of Beijing Association of Quality Inspection Certificate; Chang Qing, Editor-in -Chief of IIAB, Guest Commentator; Shi Jingyao, Director of IIAB [Credibility&Brand] Blockchain Research Institute; DaI Lin, President of llAB Guangdong Branch; Lin Wenbin, Vice President of IIAB [Credibility&Brand] Blockchain Research Institute.Group photo of all guests

EOSFORCE

19. 12. 27

EOSC Weekly Report #72

12/09–12/15, 2019Work Completed1. Tested the branch of Codex.io v2.0.x, and fixed the synchronization problem.2. Tested the branch of EOSC v2.0.x.3. Reconstructed the light node, improved the exit support.4. Reconstructed the eos-p2p support library to improve the integrity of message processing.5. Researched the performance optimization commit of the recent EOSIO debug branch.6. Researched the progress of filecoin project, evaluated the compatibility of filecoin bridge tool with EOSIO ecology.7. Participated in and completed the process of filecoin trusted setup Perpetual Powers of Tau.Plan for Next Week1. Reconstruct the light node and eos-p2p support library, improve the support for messages’ integrity, support confirmed block message processing.2. Design the light node block DB to support for confirming block irreversibility.3. Merge the performance optimization commit of EOSIO debug branch to test the compatibility.4. Research the progress of filecoin project, set up filecoin test network node.Community News1. The 8th Meeting of The 1st EOSC Budgeting Management Committee (EDBS-1) was successfully held, and all proposals and data will be collated.2. GoBlock Game Development Team made a sharing of DAPP Game Ecology Development, and announced the schedule of development based on EOSC.3. Cyborg, the founder of EOSForce, commented on the latest CCID’s global public chain ranking that he didn’t think EOS is inferior to Ethereum in terms of innovation and application.

EOSFORCE

19. 12. 17

Statute of The Secretariat ...

Chapter I NameThe Secretariat of EOSC Mainnet BP Meeting is a decentralized autonomous organization composed of the Secretariat, the Management Committee and the Development Team, referred to as the Secretariat.Chapter II AimThe aim of the Secretariat is to coordinate community governance proposals, promote the proposals to take effect and maintain the consensus of EOSFORCE mainnet.Chapter III MembershipNumber of members: The Secretariat is composed of BPs, the development team and community members.The number of members is tentatively set at 4, including 1 from development team and 3 from BPs.Membership and Election Rules: Anyone is eligible to apply for the membership of the Secretariat, which requires 2/3 of BPs to approve.Salary: Members of the Secretariat are entitled to a 10,000 EOSC/month salary subsidy, which can be subsequently revised according to community proposals.Chapter IV DutyPositions and Duties: The Secretariat has 1 secretary-general and 3 deputy secretary-generals. 4 positions for meeting hosting, meeting organization, technical communication, and community communication have been set up. The specific job division shall be determined at the first meeting of the current Secretariat. The members must fulfill the rules and guidelines of this Statute and Eosforce Mainnet BP Meeting System.Duties of the Secretary-General: Coordinate and manage the daily work of the Secretariat; Organize and coordinate matters such as community governance, technical communication, and conference organization.Duties of Deputy Secretary-General: Responsible for their own work content; Organize meetings, collect community governance proposals, organize community discussions, coordinate the technical team development and organize nodes to complete the mainnet upgrade under the guidance of this Regulations.Application Process and Election Time: The application for the positions of the Secretariat shall begin in the first half month of the change of the current Secretariat. Anyone can apply for membership with the current Secretariat. The current Secretariat will submit the registration information to the BP meeting, and BPs will vote to elect the membership of next Secretariat.Term of Office: The Secretariat rotates for 3 months, with a maximum term of no more than 2 terms. Anyone can propose to remove the members of the Secretariat, which needs to be approved by 2/3 BPs voting at the BP Meeting.Restriction: For the facility of the community governance of proposals and the feasibility of communication on the chain, the Secretariat tentatively sets a quota for the development team, and subsequently adjusts or withdraws based on the community governance.Chapter V MeetingRegular Meeting: The Secretariat shall hold weekly meetings to determine the work content and specific division of labor for this week. The specific meeting time is determined by the first regular meeting of the current secretariat according to the members.Monthly Meeting: The Secretariat shall hold regular monthly meetings to mainly summarize the work of last week and the work plan for the next month. The specific meeting time is determined by the first regular meeting of the current secretariat according to the members.Unscheduled Meeting: Members of the Secretariat have the authority to initiate an unscheduled meeting of the Secretariat and a BP meeting of EOSFORCE mainnet. The purpose of EOSFORCE Mainnet BP Meeting must be clarified in the announcement. The announcement and specific arrangements shall be published at least three days in advance to notify BPs and community members.Quorum: The provisional quorum of the Secretariat is 4, which is subsequently adjusted according to community governance.Chapter VI Rules of ProcedureThe Secretariat adopted the latest version of “Statute of The Secretariat of EOSC Mainnet BP Meeting” as the standard of the rules of procedure. Under the premise of not conflicting with the “Eosforce Mainnet BP Conference System”, the “Eosforce Mainnet BP Meeting System” is preferentially used to guide the operation of the Secretariat.Chapter VII Amendments of the RegulationsThe regulations can be amended at any EOSFORCE Mainnet BP Meeting. The amendments follow the rules of “two-thirds node voting” and must be submitted in writing before the meeting.

EOSFORCE

19. 12. 12

EOSC Weekly Report #71

12/02–12/08, 2019Work Completed1. Merged the update of EOSIO v1.8.6 with EOSC and Codex.io.2. Tested the compatibility of EOSIO v2.0.x branch with EOSC and Codex.io.3. Collated the P2P protocol changes of the EOSIO v2.0.x branch.4. Reconstructed the light node to better adapt Codex.io and EOSIO.5. Improved the support for the interactive development of Codex.io and EOSC.6. Improved Codex.io’s support for Kafka.Plan for Next Week1. Test the branch of Codex.io v2.0.x, and fix the synchronization problem.2. Test the branch of EOSC v2.0.x.3. Add block synchronization mode and transaction synchronization mode to the light node’s support for EOSIO 2.0.x.4. Research the performance optimization commit of the recent EOSIO debug branch.5. Research the progress of filecoin project, evaluate the compatibility of filecoin bridge tool with EOSIO ecology.Community News1. The Secretariat of EOSC Maine BP Meeting released Statute of The Secretariat of EOSC Maine BP Meeting to coordinate opinions on community governance, promote the effectiveness of the governance proposals on the chain, and maintain the consensus of EOSFORCE mainnet.2. The 8th meeting of The 1st EOSC Budgeting Management Committee (EDBS-1) was successfully held, and the budget system will be upgraded.3. The founder of EOSForce Cyborg took an exclusive interview with Mars Finance, emphasizing that the main problem solved by blockchain is trust.4. The co-founder of EOSForce Xiwu was invited to attend 2019 T-EDGE Conference and made an application sharing of “Blockchain Reshaping Enterprise Ecology-Blockchain Traceability”.

EOSFORCE

19. 12. 09

EOSC Weekly Report #70

11/25–12/01, 2019Work Completed1. Improved the support for the interactive development of Codex.io and EOSC.2. Designed the support plan for Codex.fc supporting multiple hash algorithms.3. Researched the chain-running solution of Codex.io running based on Golang.4. Implemented the static declaration feature of the contractual account on Codex.io, and researched the adaptation of EOSC to it.5. Improved Codex.io unit test.6. Improved the support for EOSC wallet, fixed the bug.Plan for Next Week1. Merge the update of EOSIO with EOSC and Codex.io.2. Test the compatibility of EOSIO v2.0.x branch with EOSC and Codex.io.3. Collate the P2P protocol changes of the EOSIO v2.0.x branch, and fix the light node synchronization problem.4. Improve the support for the interactive development of Codex.io5. Improved the unit test of Codex.io.Community News1. The fifth phase of EOSC community theme sharing event was successfully held. The community member Jichanglulu made a sharing of “EOSC Empowers the Real Economy”, sparking positive discussions in the community.2. The founder of EOSC Cyborg was invited to participate in the theme sharing of “Development and Application of Blockchain Technology” hosted by DappOS.3. Statute of Decentralized Budgeting Committee has been released, which will improve the operational efficiency of the committee and promote a more efficient governance of the EOSC community.4. The EOSC Ecological Game Go Black developed by the DappBrids team has entered the development stage and proposed a budget proposal in the budget system.5. The founder of EOSC Cyborg took an interview by EOS Summit to discuss the operation of the decentralized budget organization and talk about the development vision of the blockchain in 2020.6. A Thanksgiving online event was held in EOSC English Community, evoking wild enthusiasm in the community.Code Submissions: 57Voting Users: 12,427Voting Rate: 55%

EOSFORCE

19. 12. 02

EOSC Weekly Report #69

2019.11.18–2019.11.24Work Completed1. Fixed the problems with Codex.io merged with eosio 2.0.x, tested the applicability of new features in Codex.io 2.0.x.2. Improved the unit test of EOSC and Codex.io.3. Researched the development plan of Codex.fc supporting different encryption algorithms.4. Researched EOSC data index query scheme.5. Redesigned the chain startup proces of Codex.io, removed the dependency of the genesis contract.6. Added a declaration feature of the contractual account on Codex.io.Plan for Next Week1. Improve the support for the interactive development of Codex.io and EOSC to realize API light node with chain interaction.2. Design the support plan for Codex.fc supporting multiple hash algorithms.3. Research the chain-running solution of Codex.io running based on Golang.4. Implement the static declaration feature of the contractual account on Codex.io, and research the adaptation of EOSC to it.5. Improve Codex.io unit test.Community News1. The first proposed budget of EOSC Maine Decentralized Budget System has been issued to the applicants account.2. EOSForce successfully ran for CoinEx verification node, ranking 16th.3. The 6th meeting of EOSC 1st Budgeting System (EDBS-1) was successfully held.4. The new official website of EOSC community launched, evolving towards the decentralized high-performance smart contract platform.5. The EOSForce technical team and SF Blockchain Research Center had an in-depth communication on commercializing blockchain applications, discussing about blockchain solutions on commodity origins, supplier finance, private computing, data access, and transparent payments.Code Submissions: 28Voting Users: 12,427Voting Rate: 55.2%

EOSFORCE

19. 11. 25

EOSC Weekly Report

EOSC Weekly Report #672019.11.4–2019.11.10Work Completed1. Tested EOSC Token Exchange contract, and optimize the contract based on community feedback.2. Improved support for EOSC unit test, added test cases corresponding to the EOSC function.3. Collated EOSC document, added document related to new features.4. Developed EOSC half-node framework, completed the design of chain framework.5. Improved the EOSC goeosforce library, add new feature support.6. Investigated the adaptation of history_tools to EOSC.7. Investigated the progress of the filecoin project.Plan for Next Week1. Merge eosio 2.0 rc to EOSC, investigate the extent to which new features are applicable in EOSC.2. Improve support for EOSC unit test, add test cases corresponding to the EOSC function.3. Collate EOSC document, add document related to new features.4. Develop EOSC half-node.5. Record the EOSC DAPP development course.Community News1. Cyborg was invited to attend the CoinEx Shanghai Meetup to discuss the construction of CET community and jointly promote the implementation of Blockchain DApps.2. Cyborg made a speech of The Aspiration Competition between Libra and DCEP at the Blockchain Kinetics Forum in the Era of Array Economy hosted by B-LABS.3. The EOSC community organized the first and third phases of the community theme sharing event, at which community members share and discuss current community hot topics.4. EOSC has reached a preliminary ecological and wallet cooperation consensus with EOS Tribe and StartEOS.5. The Awake Node developed an EOSC development tool for beginners, which facilitates developers to make contributions to open source community.6. The EOSC team participated in the filecoin verification and got an early test qualification.7. EOSC Founder Cyborg made a blockchain-themed speech at MXC’s Parallel Cities event.Code Submissions: 21Voting Users: 12,422Voting Rate: 56.2%

EOSFORCE

19. 11. 12

EOSC Weekly Report #66

2019.10.28–2019.11.3Work Completed1. Completed EOSC Token Exchange contract, coordinate with the community to start the test.2. Completed EOSC Token Exchange data query plugin.3. Improved support for EOSC unit test, added test cases corresponding to the EOSC function.4. Collated EOSC document, added document related to new features.5. Complete the technical document of EOSC’s first sub-chain plan, designed cross-consensus prove mechanism.6. Built EOSC half-node framework, tested the performance of EOSC half-node.Plan for Next Week1. Test EOSC Token Exchange contract, optimize according to the feedback from the community.2. Improve support for EOSC unit test, add test cases corresponding to the EOSC function.3. Collate EOSC document, add document related to new features.4. Develop EOSC half-node framework, complete Net plugin framework, and realize the preliminary block data storage.5. Improve the EOSC goeosforce library, add new feature support.Community News1. The EOSC community held the first sharing event on the community themes to share and discuss current hot topics in the community.2. The EOSC develop team announced to join the CoinEx Chain pre-election node process, and will conduct a series of in-depth cooperations with CoinEx in cross-chain technology, blockchain virtual machines and privacy computing.3. The EOSC English community held a Halloween event, and the overseas users took an active part in it with huge enthusiasm.Code Submissions: 33Voting Users: 12418Voting Rate: 56.1%

EOSFORCE

19. 11. 05

Community Publicity on Dece...

Project Name: Decentralized Budget SystemDescription:According to the content of the EOSFORCE Mainnet Improvement Proposal V1.0 FIP #7, the budget committee was started to manage and organize the ecological application development. To this end, the EOSFroce team organized and developed a decentralized budget system page. It has been developed and officially launched online, and at the same time add an entry on the official website, users can jump directly to the budget system website on the official website.Project functionsAll data in the budget system will be synchronized on the chain, and everyone can log in to apply for a proposal via scatter.Existing functions:1. Complete interface of pre-selected system2. Complete operation through the scatter contract3. Apply for layout design4. The design of each layout, including the approval, the public, the implementation, and the completion of the four stages.5. Subsequent version maintenance and updates.Project URLEOSForce(EOSC)Development cycleStage 1: Product demand (expected 5 staff days) 1、 demand finishing 2、 prototype design StageStage 2: UI design (expected 5 staff days) 1、UI designStage 3: Development and launch (expected 15 working days) 1. front-end development 2. back-end data docking 3. test and go onlineDevelopment costsWorking hours: 25 working days 500,000 eoscServer fee for one year: 30,000 eoscMaintenance cost for one year: 20,000 eoscTotal: 550,000 eosc

EOSFORCE

19. 10. 31

EOSC Cyborg: The Public Cha...

EOSC Cyborg: The Public Chain Needs Computing with High Performance and Low Latency Based on DPoS Consensus| Chain InterviewThe EOS public chain utilizes DPoS consensus mechanism, which supports computing with high performance and low latency. While DPoS mechanism itself is not decentralized enough. As the first forked chain of EOSC mainnet, EOSC has optimized the election mechanism of EOSIO and launched the EOSC mainnet at the genesis block height of one. Through persistently upgrading EOSC mainnet that makes EOSC Network evolve toward the decentralized high-performance smart contract platform.At this edition of Chain Interview, Chain Teahouse invited Cyborg, the founder of EOSC. Cyborg will tell the stories happened during the process of EOSC development and operation, and interpret the existence of the future computing public chain with high performance and low latency.Technology R&D Team Supported by Internal FundsKeep Optimizing DPoS ConsensusFounded in early 2018, EOSC team currently has about 20 members, and is based in Hangzhou. At first, the team felt that the industry competition lied on the protocol and the bottom public chain, and the entrepreneurial direction was based on the market, so there is no need to create a new consensus and ecology. At that time, EOSC chose the most advanced ecology EOS and is committed to the optimizations based on DPoS consensus.EOSC team has technical talents from famous Internet companies such as Huawei, Tencent, Baidu, etc. Cyborg also worked on Internet related work before. Currently, about 8 people in the team are responsible for technology development, mainly the upgrade and iteration of EOSC. The maintenance of EOSC mainnet is in the charge of the community. The technical team is mainly responsible for the following three directions of work: first, the improvements based on the community’s opinions; second, study the latest technologies, such as cross-chain, privacy computing, oracles and virtual machines; third, it will help peers with some blockchain development.At present, the EOSC team does not raise funds. It is entirely supported by its own internal funds. The revenue of the public chain business in the business model cannot cover the cost. Therefore, providing some other projects with some development help is also one of the sources of income.According to Cyborg, DPoS consensus is reasonable in its existence and development. Because the computing with high performance and low latency will be a must in the future blockchain industry, which can only be reached by public chains with DPoS consensus. In EOS, 6 blocks can be produced in every second, this concept is very advanced. Besides, the implementation of multi-threading technology EOS is exploring will bring a qualitative improvement for the high-performance computing in the blockchain industry.EOSC has encountered two difficulties on the its entrepreneurial path. The first is that EOSC was not recognized in the beginning. EOS is the beginning of the 3.0 era. People don’t understand that there are several blockchains in one ecology, so they naturally reject chains with fork tendency and think that fork is unjust. In 2017, BTC and ETH’s forked token ran away and left a lot of mess to the community, leading to a bad impression of the fork behavior. The EOSC team realized that in the blockchain world, actions speak louder than words. EOSC insisted developing for a year and a half, while ETH and BTC’s fork development did not take so long. Users in the EOSC community can feel that the team is hard-working by the upgrades and iterations of EOSC.Second is the shortage of team funds. EOSC cannot spend money on the ecology and marketing like other financing teams. In Cyborg’s view, the POW public chain can be financed, because holding POW tokens can only receive dividends, but DPOS sells both dividends and voting rights, and this network may not able to achieve the community governance. Profitable people took away dividends and voting rights, but they are not able to do these things. For example, EOS investors can’t participate in governance and voting, so EOSC will not raise funds for DPOS tokens, and maybe will raise funds for the company’s purposes in the future. EOSC token is not going to raise funds. The dividend is only the profit of the legal currency. These are two different things.EOSC Node Cost is 1% of EOSTPS is Adjusted According to Market DemandEOSC enables blocks to be produced every 0.5 seconds with 6 consecutive blocks, which is different from EOSIO’S model of producing blocks every 0.5 second with 6 consecutive blocks produced by 1 node. Even though consecutive block-producing can reduce the waiting time of unpacked trades, it may affect the chain stability because of the unsatisfactory network environment, resulting in a large number of microforks.In addition, Cyborg also believes that TPS is not a very rigid measure of the performance of the public chain. TPS in EOS currently reaches more than 5,000 and can support 432 million transactions per day. However, the daily order of Meituan APP is only of million level, and Taobao is only of ten million level, EOS’s TPS completely overflows the normal trading needs of users. The reason why EOSC reduces the speed of the block producing is that the market demand is not so big, and the node does not need to provide such a high configuration. EOS has a large number of microforks, and the synchronization cost is very high. When the market demand is high, all nodes just need to provide configuration to transform. Compared with the synchronization of 0.5 seconds and 3 seconds, the network cost is definitely low, so the EOSC node cost is one percent of EOS. If the network is very blocked, the nodes just need to improve the configuration, which means that the market demand for this chain has increased.Use Cross-Chain Technology to Make Up the Disadvantage that DPoS is Not Decentralized EnoughCyborg said that working on cross-chain is because the EOSC team feels that DPoS is not decentralized enough, but high performance requires DPoS, so it is impossible to give it up completely. How to realize the decentralization of the public chain that is not so decentralized, what needs to be done is to use another POS chain as the sub-chain of EOSC. At present, the team is working hard to develop in the test network.One important thing that both EOSC and EOS lack is Account Balance Status Verification, which is not on the mainnet. In EOS, there are two ways to alter the balance without the private key, the node private sign and the change of super privilege. Although the core users of the EOS ecosystem don’t care about this, everyone has different opinions on how to define the blockchain. The Bitcoin community believes that the user’s currency cannot be altered, EOS Ecology feels that if the private key of ETH and BTC is lost the asset will be 0. EOS sets node private sign and super privilege to better protect user asset security with a community consensus. But in extreme cases, if the node is controlled, there is a risk of changing the balance.The cross-chain of EOSC can solve this problem. It can verify the balance regularly, and then put the data into the block. Unless the transaction is rolled back, otherwise the asset can be truly protected. When developing cross-chain technology, EOSC found that when the market is talking about the importance of heterogeneous cross-chain, but everyone is doing isomorphic cross-chain. All chains in the isomorphic chain are developed based on the same protocol and can naturally be cross-chained.Cyborg believes that cross-chain changes the competition between public chains from the account book capacity to the accounting method. Excellent accounting methods can be used by everyone. There is a network effect, which is different from a single book. Before EOSC develops cross-chain, it investigated who can form a market effect in the market. At present, the team feels that COSMOS can. COSMOS has produced a good accounting method, ecologically chooses the GO language, and many traditional Internet developers familiar with the language. In addition, COSMOS sdk is very simple, developers can start in ten minutes. At present, there are hundreds of teams developing based on COSMOS. These hundreds of projects can be linked in the future, which is an ecology.1-Token-1-Vote Guarantees the FairnessBP Reward & Penalty Mechanism and Heartbeat Mechanism Guarantee the Block-Producing StabilityIn EOS, only elected nodes have profits, and the voting users have no income, so there is bribery. EOSC adopted “1 token 1 vote” that as long as you vote, you will gain dividends. But if the node does not produce blocks, the voting users cannot gain dividends. So the voting users will not vote randomly. They will choose the nodes that make contribution to the community and produce blocks stably.The main optimization direction of the EOSC’s election mechanism is to separate the voting rights and the dividend rights. This requires the user to vote for the node and ensure that the voting rate network is safe. As long as there are dividends, there will be bribes. This will be adjusted by the adjustment of voting rights. The longer you deposit, the more you will vote. The fairest thing about POW is computing power. EOSC believes that the fairest thing in POS consensus is time.But there are problems in practice. For example, a big holder directly locks his tokens for two years to gain more discourse power. In fact, big holders are also part of the community, and they are loyalty computing power. However, the gap between the rich and the poor exists in both POW and DPOS. In POW, computing power means the discourse power. In POS, the more tokens, the discourse power. The gap between the rich and the poor is inevitable. which is created by private ownership. And it is unrealistic to eliminate private ownership. The team is currently concerned about the unequal discourse power caused by the gap between the rich and the poor. Only by solving this problem will POS really break out. Cyborg believes that the blockchain is a new thing, we need to solve the problem first, and then improve it. The impact of the gap between the rich and the poor on the discourse power is a long-term issue.The nodes in EOSC can be divided into BPs and BP candidates. BPs just need to canvass and deposit a small amount of tokens. The work of BPs is to maintain the stability of block-producing. According to changes in market demand, the high market demand requires higher node configuration. The functions of mainnet can be updated and planned with more than 2/3 of BPs voting through. Users are voting in EOSC all the time. The eliminated BPs will be reduced to BP candidates, and the candidates need to prove that they have real ability to produce blocks. In the future, EOSC will also introduce light nodes that cross-chain needs, and they will verify whether the entire network is normally producing blocks or notEOSC has established two mechanisms to ensure the stability of the mainnet. First, BP Reward & Penalty Mechanism. The stable block-producing is the first goal of network security. For BPs which don’t produce blocks, EOSC will impose very severe penalties. The stable block-producing will gain more profits. The first task of the node is placed on network security. The BP has to pay the deposit. If the BP doesn’t work, it will not gain profits, and its deposit will be deducted. Anyone can initiate a proposal to punish the BP that doesn’t produce blocks. If the proposal is approved by the multi-sig, this part of the penalty will be distributed as reward to the proposer and the nodes that agree to the multi-sig.Second, the Node Heartbeat Mechanism for BP candidates. The high probability of BP candidate is that there is no outbound task. If it does not have a real server, but connects to someone else’s server, then you can get the benefit without paying the cost. EOSC requires that the BP candidates needs to have a real block-producing ability. When it is the turn for a BP candidate, it needs to be able to produce blocks. The Heartbeat Mechanism is to check whether the candidate has the ability to produce blocks online. If the candidate node is checked out not online, the heartbeat mechanism can make the BP candidate gain no profit.Single Public Chain Carrying Too Many DApps Does Not Conform to Development TrendEOSC is Committed to Provide More Public Chains with High-Performance ComputingEOSC is very compatible with EOSIO developers, and DApp can be migrated directly. Cyborg believes that DApp developers are currently facing three problems. First, from the physical bottleneck, a public chain can’t carry too many DApps. If a chain runs too many DApps, it will be blocked. In the future, the from will be multiple DApps on one public chain which cannot carry too much. It is not in line with the future trend to develop too many DApps in a single public chain.Second, it’s about the problem of development tools and development resources. Traditional game developers can invoke a different library to form a game, but the development tools for the public chain are few. This requires the community to do tolls and tutorials together.Third, the use of tokens. In the market, no more than 10 public chains have established the economy model. Few teams that are able to design an economy model. At present, no DApp can make continuous profit without the economy model, and developers don’t know how to get started. For the above points, EOSC will work on tutorials, application governance and economic models, and study without prejudice to the development progress of the mainnet.On EOSC mainnet, at present, there are nearly 600,000 registered addresses, more than 12,000 accounts participating in the vote, 23 BPs, and more than 30 active nodes including BP candidates. EOSC defines itself as a computing chain with high-performance and low-latency. Whether it is available to EOS or COSMOS ecosystem, EOSC will work with other public chains to provide high-performance computing protocols for other public chains. Moreover, the code will be open source in the future. The team plans to complete cross-chain R&D in half a year, and the high-performance computing provided in the second phase will be faster.Copied from Chain TeahouseAuthor: Shenneng

EOSFORCE

19. 10. 30

About the Budget Applicatio...

1. General Project InformationProject Name: EOSForce BP Management Platform Description and Goal Statement: The BP management platform will integrate BP’s daily operations, enhance BP’s ability to collaborate, and show the community the progress of BP’s work. Promote the ecological development of EOSC.Website: https://api.akdex.io/bpmsig2. Project TeamTeam Name: eosawake Nodes in the communityTeam Introduction: Eosawake community is one of the earliest nodes to participate in the governance of EOSC main network. In terms of EOSC ecology, there are the development of Akdex decentralized exchange and Awake decentralized wallet.Contact Information: https://t.me/eosawake,service@akdex.io3. Project Scope StatementProject Demand: Because BP’s daily work needs to use the private key of BP account, the current method can only be operated in the command line environment, which is very inconvenient. BP management platform can solve this demand, so that BP daily operation does not need a computer, and can be completed at any time anywhere on the mobile phone wallet related operations. And the results of the operation, the whole community users can see.Project Objectives:Display board for current node statusRelevant data display of block-producing nodes and standby nodes, such as produced blocks, voting weight, missed blocks, penalty, reward, etc.Relevant operations of nodes, such as block-missing record, increasing deposit, claiming reward, proposing penalty nodes, etc.Multi-sig module to display the current list for nodes to execute multi-sig and provide the operational button for multi-sig.Node information filling and modification module for nodes to use bpinfo contract conveniently.4. Project Milestones and Schedule2019–10–01 Project establishment2019–10–02 Project demand analysis2019–10–05 Project framework design2019–10–08 Project starts coding2019–10–12 Internal Test2019–10–15 Open Beta2019–10–20 Official Launch

EOSFORCE

19. 10. 29

EOSC Weekly Report #65

2019.10.21–2019.10.27Work Completed1. Merged the update of EOSIO v1.8.5 to EOSC.2. Improved support for EOSC unit test, new features and support for EOSC on-chain config.3. Improved eosc_api_plugin to integrate EOSC-specific API.4. Completed the technical document of EOSC’s first sub-chain plan, developed light node demo, and tested synchronization performance.5. Developed EOSC Token Exchange contract.6. Investigated EOSIO Web IDE, collated and released the introduction document.Plan for Next Week1. Coordinate with the community to update EOSC mainnet.2. Improve support for EOSC unit test, add test cases corresponding to the EOSC function.3. Collate EOSC document, add document related to new features.4. Complete the technical document of EOSC’s first sub-chain plan, build EOSC half-node framework.5. Develop EOSC Token Exchange contract.Community News1. EOSC Mainnet Decentralized Budgeting System officially launched, two proposals were received and approved in the first week.2. The development team applied to participate in the verification activity of the testing of Filecoin mainnet launch.3. The English community successfully held a community promotion campaign, attracted thousands of users to participate in the campaign, and the number of the community members doubled.4. The operation team communicated with CoinMarketCap (CMC), a well-known blockchain information platform, and updated the ranking of EOSC in CMC.5. The famous blockchain Youtuber in the Arab region made an introduction video of EOSC.Code Submissions: 30Voting Users: 12,417Voting Rate: 56.4%

EOSFORCE

19. 10. 28

Refer Friends to EOSForce T...

Refer Friends to EOSForce(EOSC) Telegram Reward CampaignAs a thank for all your contributions, we would like to hold a Referral Campaign to reward members of our EOSForce_EN Telegram community in this month. Both you and your friends will earn EOSC for participating in this campaign. These will then be distributed within 2 weeks after the campaign has ended.How To Get Your EOSCFor referrers:Send a message to EOSForce Bot (@EOSCbot) saying /myrefs to get a unique invite link2. Invite your contacts to our Telegram group by sharing your unique invite link3. Submit your Telegram user name and EOSC account name in the Google form https://forms.gle/MdwzWXkAgpKxdnc47For referees:1. Click the invite link you received2. Click “Start”3. Click “Accept Invite”4. Click “I’m not a robot👍” to pass the anti-bot check.5. Submit your Telegram user name and EOSC account name in the Google form https://forms.gle/MdwzWXkAgpKxdnc47Allocation1. Each successful referral will be rewarded 5 EOSC.2. Each referee who successfully joins the group will be rewarded 3 EOSC3. Rewards for referrers who have most referrals:Top 1: 500 EOSCTop 2–3: 250 EOSCTop 4–6: 100 EOSCTop 7–10: 50 EOSCHere Are The Rules!The Referral campaign will run from October 21, 2019 to October 31, 2019.· Referrals will be tracked via EOSForce Bot, so no need to worry! Your referrals are being logged.· For the referrer and referee to be allocated MPT, the individual referred must remain a part of EOSForce_EN Group for the length of the campaign.· SPAM, ABUSE, or failure to fully observe the rules lead to ban and disqualification!

EOSFORCE

19. 10. 20

EOSC Weekly Report #63

2019.10.7–2019.10.14Work Completed1. Coordinated with the community to implement FIP#11.2. Merged the update of EOSIO v1.8.1 with EOSC.3. Reconstructed the code structure of EOSC Transaction fee to reduce the difference with EOSIO.4. Organized EOSC Http RPC API design, integrated the EOSC-specific API, and maintained compatibility with EOS.5. Collated EOSC state_history_plugin support plan , designed history_tool transplantation plan.6. Fixed some EOSC Bug, completed key notes.7. Designed EOSC voting incentive performance optimization plan.8. Investigated EOSC sub-chain architecture solution and designed EOSC heterogeneous cross-chain framework.9. Improve the support for EOSC Decentralized Budget System page.Plan for Next Week1. Test EOSC v1.8.3, coordinate with the community for a pre-upgrade.2. Add eosc_api_plugin to integrate EOSC-specific API.3. Collate EOSC document, add the modifications as of v1.8.3.4. Improve the support for EOSC state_history_plugin.5. Design EOSC sub-chain architecture solution, organize EOSC heterogeneous cross-chain framework.6. Develop EOSC Token Exchange contract.Community News1. The freezing execution of unactivated account balance has completed and FIP#11 officially takes effect.2. Cyborg, the founder of EOSC, was interviewed by Chain Teahouse to explain the significance of the existence of high-performance low-latency computing public chain.3. The 14th EOSC Mainnet BP Meeting was held, the 1st EOSC Management Committee was elected.4. The 1st EOSC Management Committee was established. The members are: Shede-eosawake, Big Hair-Jeepool, Wang Wei, Yibao-Bepal, Yi Chuanqi-EOSC Developent Team.Code Submissions: 18Voting Users: 12,413Voting Rate: 56.6%

EOSFORCE

19. 10. 14

EOSC Weely Report #62

2019.9.23–2019.9.29Work Completed1. Coordinated with the community to plan EOSC v1.8.2 upgrade process and program.2. Coordinated with the community to test the account freezing procedure and other functions on the test network.3. Merged EOSIO v1.8.2 with Codex.io.4. Merged EOSIO v1.8.2 with Codex.relay.5. Optimized Codex fee mechanism based on the change of EOS v1.8.x structure.6. Designed the support plan for Codex.io cross-chain verification.7. Improved Codex.relay economy model requirements.8. Designed EOSC voting incentive performance optimization plan.Plan for Next Week1. Coordinate with the community to implement the upgrade of EOSC v1.8.2.2. Collate EOSC document, add the modification till v1.8.2.3. Collate EOSC Http RPC API design, integrate EOSC-specific API to be compatible with EOS.4. Improve EOSC state_history_plugin support, develop a history-tools migration plan.5. Improve Codex.relay economy model requirements, and improve Codex.relay underlying api support.6. Design EOSC voting incentive performance optimization plan.Community News1. Hotbit launched the EOSC/USDT trading pair.2. Cyborg, the founder of EOSForce, shared his opinions at an EOSC AMA event held by CoinEX.3. CoinEx launched the EOSC/USDT trading pair, and initiated “EOSC Discount and Rebate” event.4. The technical implementation of FIP#11 Freezing Proposal has been tested, and the list of frozen accounts began to be publicized.5. Nodes have completed multi-sig for FIP#12, and the Proposal to Adjust RAM Lease Price takes effect.

EOSFORCE

19. 09. 29

EOSC Weekly Report #61

2019.9.16–2019.9.22Work Completed1. Coordinated with the community to complete the upgrade of v1.7.1.2. Merged EOSIO v1.8.3 with EOSC.3. Tested EOSC v1.8.x branch, and released EOSC v1.8.2.4. Coordinated with the community to test the account freezing procedure and other functions on the test network.5. Improved the Docker support for EOSC v1.8.2.6. Improved the front-end support of the decentralized budget system.7. Communicated with the community about EOSC new technology roadmap.Plan for Next Week1. Coordinate with the community to plan EOSC v1.8.2 upgrade process and program.2. Coordinate with the community to test the account freezing procedure and other functions on the test network.3. Merge EOSIO v1.8.2 with Codex.io.4. Design the support plan for Codex.io cross-chain verification.5. Improve Codex.relay economy model requirements, and improve Codex.relay underlying api support.6. Design EOSC voting incentive performance optimization plan.Community News1. The upgrade of EOSC mainnet v1.7.1 has been completed, and all the functions in FIP#7 Mainnet Improvement Proposal have been launched.2. QB.com will list EOSC, holding Listing Campaign and Airdrop Campaign.3. The Secretariat of EOSC community open the registration for Management Committee Election, and any individual or organization can participate in the election of Management Committee members.4. Cyborg, the founder of EOSForce, was invited to attend 2019 Shanghai Staking Economy Roundtable held by Math Wallet.

EOSFORCE

19. 09. 22

The Detailed Explanation on...

Current Profit Calculation of Profitable NodeProfitable node: The registered nodes that can obtain the rewards of voting, including BP and BP candidates.The nodes that obtain more than 0.5% of the total weighted votes are the profitable nodes. The top 23 nodes are BPs, and the rest are BP candidates.EOSC mainnet will distribute rewards for profitable nodes according to their proportion of the total weighted votes with every block produced. And the rewards will be further distributed accordingly.For BPs:70% of profits goes to the reward pool, and the nodes can freely adjust the dividend ratio.15% of profits is distributed to nodes’ accounts as the basic salary.15% of profits goes to nodes’ accounts as block rewards.For BP candidates:70% of profits go to the reward pool, and the nodes can freely adjust the dividend ratio.15% of profits is distributed to nodes’ accounts as the basic salary.15% of profits goes to EOSForce foundation account.Remark: If the node does not produce blocks or pay the deposit, the node and the voters can not obtain any profits.Profit Calculation after FIP#7 Takes EffectTo lower the threshold of the node, EOSC mainnet passed EOSC Mainnet Improvement Proposal FIP#7, making some adjustments to the node rewards.After EOSC Mainnet Improvement Proposal FIP#7 takes effect, the block rewards of EOSC mainnet are distributed as follows:10% of block rewards is distributed by the block-generating nodes in proportion to the number of blocks.10% of block rewards is distributed by all profitable nodes’ rewards according to the proportion of voting weighted votes.For 50% of block rewards, the nodes can freely adjust the dividend ratio.30% of block rewards goes to decentralized budget system.Q & AQ1: Why do the backward BPs and BP candidates get few rewards?A: This is because a large number of weighted votes are concentrated in the top BPs, and there are big gaps between the number of votes of nodes. According to the profit distribution formula Node Profit = All the reward of profitable nodes * The proportion of the total weighted votes, the reward for the backward BPs and BP candidates are few.The problem that the node reward distribution gap is too large will be improved after EOSC Mainnet Improvement Proposal FIP#7 takes effect.After EOSC Mainnet Improvement Proposal FIP#7 takes effect, In addition to distributing the block rewards according to the proportion of voting weighted votes, BPs (Block Producers) will also distribute 10% of the block rewards according to proportion of the number of produced blocks.Q2: Why is there less profit when vote for a node than for other nodes?A: Because the amount of the reward pool of some nodes is relatively large, there are a lot of dividends to be claimed. If a large number of votes are suddenly cast to these nodes, according to the calculation formula of dividends (To-be-claimed dividends = The proportion of voting age * The amount of reward pool), it is known that the reward pool is larger, and our dividends will be more. The extra part is essentially diluting the dividends that the historical voters did not claim.This problem will also be solved at the next EOSC mainnet update.Q3: For voters, what factors will affect the voting rewards?After EOSC Mainnet Improvement Proposal FIP#7 takes effect, the rewards that voters can receive are affected by the following factors:Block-producing stability of the voted node.Whether the voted node pays the deposit.The dividend ratio set by the voted node.The rewards that voters can receive has nothing to do with the number of votes the node receives. Theoretically, if all the block producers have the same block-producing stability and dividend ratio, and all deposits have been paid. No matter which node a voter votes for, the dividends that can be obtained are the same.

EOSFORCE

19. 09. 17

EOSC Weekly Report #59

2019.9.2–2019.9.8Work Completed1.Tested the compatibility of sync blocks on EOSC v1.8.0, fixed the appeared problems.2.Improved the support for EOSC snapshot.3.Optimized the Node Punishment Mechanism, fixed the design that affects performance.4.Reconstructed EOSC node heartbeat plugin.5.Integrated the on-chain configuration and feature-related functions of EOSC.6.Transplanted a new EOSJS library for EOSC, collated JS development document.7.Cooperated with the community to launch EOSC test network, and made preparations for the update of new functions.8.Improved the front-end support of the decentralized budget system.Plan for Next Week1.Test the activation process of new functions of EOSC v1.8.0, collate the upgrade procedure document.2.Improve the related tools of EOSC testing nodes ram.3.Test the support for EOSC snapshot.4.Cooperate with the community to test the decentralized budget system and other functions on the test network.5.Merge the improvements of EOSC to Codex.io.Community News1.KuCoin has distributed all rewards of the Listing Campaign to the winners’ accounts. Winners can check their accounts by going to Assets>My Bonus, and check the Other Rewards.2.One-Stop Digital Asset Service Platform CoinAll has successfully run for EOSC mainnet BP.3.The Secretariat, the Awake Node and the jiqiX Node launched a fundraising campaign for EOSC listing on Bibox. If the target is reached, the Awake Node will promote EOSC listing on Bibox.4.EOSwriter original video production series Heidi Asks invited EOSForce founder Crborg and core developer Fan Yang to discuss everything EOSForce.5.The 4th Secretariat announced the Amendment Proposal on FIP#9 proposal, which will be tested on September 9, 2019 (UTC+8), and determined by the result of BP’s multi-signature on the chain.

EOSFORCE

19. 09. 08

A Fundraising Proposal for ...

With the rapid development of EOSC mainnet users, the community has gone from strength to strength. Since late August, major exchanges such as OKEx, ZB, Bigone, Bibox, etc. have activated and claimed the mapped EOSC tokens for their users. On behalf of the EOSC community, Awake Node has communicated with Bibox Exchange (Ranked Top 20 on Feixiaohao, Top 9 on mytoken. Please refer to the attachment for details ) and reached an agreement on the issues of distributing EOSC tokens held by Bibox Exchange to users and opening transactions of depositing, withdrawing and listing EOSC.In view of the fact that EOSC is one of the most promising active tokens in the market, Bibox Exchange will distribute the activated Tokens to its EOS genesis users in proportion as soon as possible, and open the business of withdrawing EOSC. For Bibox opening EOSC trading pairs, the special treatment of no listingfee can be adopted, but a promotion fee of 450,000 EOSC is required for Bibox to promote EOSC trading pairs, increasing user’s enthusiasm for EOSC tokens and the liquidity of EOSC.After the Awake Node has communicated with the EOSC mainnet BP Meeting Secretariat and the JiqiX Node (Members of the Secretariat include tokenview, eosou, SKY and Captain Force), the Secretariat and Awake Node take the lead to propose a fundraising of 450,000 EOSC from the community to promote EOSC listing on Bibox. Details are as follows:1) Total Amount of Fundraising: 450,000 EOSC2)Fundraising Account: donations (Note: This account is a multi-sig account owned by the 4 members of the Secretariat, jiqiX Node and Awake Node).3) Fundraising Time: Since this proposal is published until 10:00 am on September 9, 2019 (UTC+8).The Secretariat and Awake Node promise that:1) Once the total amount of fundraising reaches 450,000 EOSC, Awake Node will immediately promote EOSC listing on Bibox and complete it within one week.2) If there are excess tokens in the fundraising account, it is intended to reserve the tokens for the next fee or to refund the remaining tokens to the fundraiser account in proportion;3) If the total amount of 450,000 EOSC is still not reached by September 9, the fundraising activity will fail, and the fundraising tokens will be returned to the fundraiser account.EOSC is one of the most cohesive communities with a mainnet consensus being recognized and accepted by more and more users. The Awake Node and the Secretariat jointly propose the EOSC community to join this fundraising event to realize the listing of EOSC in Bibox and contribute to the development of EOSC!Proposer: The Secretariat, EOSAWAKE Node, jiqiX NodeSeptember 4, 2019Attachment:Introduction of Bibox ExchangeFeixiaohao Ranking: Top 20Mytoken Ranking: Top 9Bibox is the first AI-enhanced digital asset trading platform, ensuring the security, stability, and convenience for the crypto asset traders.As the world’s leading digital asset trading platform, since it was founded on November 2017, Bibox has received wide acclaim from both users and industry experts for its carefully-screening projects, smooth trading experience and excellent customer service. With a stable world top 10 trading volume, Bibox is recognized as a better digital asset trading platform. Within a span of one year, Bibox has also established a strong global presence, with operation centers in more than 10 countries and regions including Estonia, the US, Canada, Singapore, Switzerland, Japan, South Korea and Vietnam. In addition, Bibox established its Blockchain Research Center in Hainan China, aiming at promoting the development and applicability of blockchain technology. The current business of the platform covers transactions such as Exchange, Margin, Contract, and C2C. In May 2019, it announced the opening of Bibox Europe (the French currency exchange, which has received equity investment from a global top 10 bank).

EOSFORCE

19. 09. 05

EOSC Weekly Report #57

2019.8.19–2019.8.26Work Completed1. Cooperated with the community to update EOSC system contract and complete the upgrade of v1.7.0.2. Collated the design plan of Codex.Relay new economy model.3. Fixed voting supported in EOSC wallet.4. Merge EOSC with eosio v1.8.0.5. Reconstruct the codes of Codex.relay system contract according to the new cdt.6. Reconstructed EOSC docker support according to the community feedback.Plan for Next Week1. Merge EOSC with v1.8.0, test the compatibility of sync blocks.2. Update Codex.Relay system contract according to the design plan of Codex.Relay new economy model.3. Reconstruct transaction-related contract of Codex.relay.4. Improve EOSC Budget System Contract.5. Improve the support for the destruction of EOSC unactivated accounts and tokens.6. Collate new EOSC Docker mirror operation document.Community News1. World-renowned comprehensive blockchain services provider Bepal joined EOSC mainnet.2. The upgrade of EOSC mainnet v1.7.0 has been completed, and the fixed voting function and punishment mechanism have been launched.3. The 12th EOSC Mainnet BP Meeting was held successfully. BPs voted to pass A Proposal to Destroy the Unactivated Genesis Accounts and Tokens and A Proposal to Adjust the Allocation Plan of B1 Account Tokens.4. The term of EOSC Mainnet BP Meeting Secretariat has been changed successfully. Tokenview, sky.eosc, eosou.io and Captain Force will serve as members of the 4th Secretariat5. KuCoin launched a Listing Campaign to give away 750,000 EOSC and 1 BTC.6. EOSC Overseas Community launched an Airdrop Campaign, attracting more than 1,000 overseas users to participate in the event.

EOSFORCE

19. 08. 25

EOSForce (EOSC) Airdrop Cam...

DETAILS:EOS Force (ESOC) Airdrop Campaign is active for EOS Force Social Media. In order to qualify and get your airdrop tokens, you must comply with the instructions below. Hurry while tokens last!EOS Force (EOSC) is the world’s first EOS forked of the mainnet that based on the original EOS and made many optimization and improvements.Dates: Aug 20–24, 2019 (GMT +8)Total amount of airdropped tokens: 28,000 EOSCAirdropped tokens available per person: 70 EOSCINSTRUCTIONS:Twitter1) Follow EOSForce Official Twitter page: https://twitter.com/EOSForce2) Retweet the pinned post!3) Fill out the Google form: https://forms.gle/WNnGsJ2d44yUkQtj7 (make sure that all fields in the Google form complete and filled out correctly).4) Join EOSForce Official Telegram Group: t.me/eosforce_en, submit your EOSForce account information to the adminFacebook1) Like and share EOSForce Official Facebook page: https://www.facebook.com/eosforce.official/2) Like and share the pinned post3) Fill out the Google form: https://forms.gle/WNnGsJ2d44yUkQtj7 (make sure that all fields in the Google form complete and filled out correctly).4) Join EOSForce Official Telegram Group: t.me/eosforce_en, submit your EOSForce account information to the adminINS1) Follow EOSForce Official INS page: https://www.instagram.com/eosforce.official/2) Share the campaign post to your story3) Fill out the Google form: https://forms.gle/WNnGsJ2d44yUkQtj7 (make sure that all fields in the Google form complete and filled out correctly).4) Join EOSForce Official Telegram Group: t.me/eosforce_en, submit your EOSForce account information to the adminRemarks:1) Each EOSForce account can only receive airdrop ONCE.2) Only NEW members of telegram group are eligible for the airdrops.3) You cannot delete your completed tasks before the end of the airdrop campaign or if the team announces other conditions.4) SPAM, ABUSE, or failure to fully meet the instructions lead to ban and disqualification!EOSForce Official Group

EOSFORCE

19. 08. 20

EOSC Weekly Report #55

EOSC Weekly Report #562019.8.12–2019.8.18Work CompletedTested EOSForce new system contract, and prepared for the update of v1.7.0.Tested the merged version of Codex.relay, and fixed the compilation problem.According to the community feedback, added Action of revoting based on the unredeemed vote to the fix-time voting and current voting system contract.Added a temporary extension interval to support the system contract update.Collated the design plan of Codex.Relay new economy model , and updated Codex.Relay system contract accordingly.Tested the compilation of the upgraded EOSForce compiler version to merge with EOSIO v1.8.0 conveniently.Collated the new EOSForce system contract document.Reconstructed the codes of Codex.relay system contract according to the new cdt.Improved the support for the new feature of the wallet.Plan for Next WeekCooperate with the community to update EOSForce system contract.Collate the design plan of Codex.Relay new economy model , and update Codex.Relay system contract accordingly.Merge EOSForce with eosio v1.8.0.Reconstruct the codes of Codex.relay system contract according to the new cdt.Reconstruct transaction-related contract of Codex.relay.Community NewsThe BPs Sky.eosc and Awake jointly put forward A Proposal to Destroy the Unactivated Genesis Accounts and TokensCyborg was invited to attend HyperDAO Open Class to discuss the community governance mechanism and the new development of Staking economy.The EOSC community announced that the upgrade of the mainnet v1.7.0 version was postponed to August 20th (UTC+8). For the purpose of the smooth transition of the mainnet upgrade, the development team will develop the function of changing current voting to fix-time voting.Awake put forward A Proposal to Adjust the Allocation Plan of B1 Account Tokens, which proposes to adjust the B1 account token allocation from the fixed block rewards to the decentralized budget system application according to the contribution.

EOSFORCE

19. 08. 18

Arrangements of the 12th EO...

Dear nodes, we will hold the 12th EOSForce Mainnet BP Meeting on August 21, 2019 next Wednesday. The specific arrangements are as follows:Subject: The 12th EOSForce Mainnet BP MeetingTime: Aug 21, 2019 (next Wednesday) 20:00 ~ 21:30 (UTC + 8 )Link: https://zoom.us/j/888636173Host: Jia Huijie — Jiuzhou CapitalRecorder: Kallen-CCBCInterpreter: LilyStatistician: Captain ForceAgenda:1.Election of the 4th Secretariat1) Work report from the Third Session of Secretariat2) Election of the Fourth Session of Secretariat2. Discussion on A Proposal to Destroy The Unactivated Genesis Accounts And Tokens1) Interpretation of the proposal — sky, awake2) Questions about the proposal — the Community3) Vote on the proposal — BPs3. Discussion on A Proposal to Adjust The Allocation Plan of B1 Account Tokens1) Interpretation of the proposal — Awake2) Questions about the proposal — the Community3) Vote on the proposal — BPsRemarks:1. Please attend the meeting on time. We also hope BP candidates and community members can actively participate in the discussion on community governance proposals.2. This meeting involves the election of the Secretariat. To ensure the continuity of the community work, as for the nodes who are interested in serving as members of the next session of Secretariat, please communicate with @Captain Force before 18:00 on August 20th (UTC+8). We hope that everyone will take an active part in the community construction and make a positive contribution.SecretariatAug 16, 2019

EOSFORCE

19. 08. 16

A Proposal to Destroy The U...

EOSFORCE.IO is an EOSC mainnet based on EOSIO system, but launched in accordance with its own unique governance philosophy. At the beginning of mainnet launch, EOSC tokens was 1:1 mapped in accordance with EOSIO genesis accounts for community members with the same consensus to activate and claim for free, jointly building and prospering EOSC mainnet community and ecology. With more than a year of safe and stable operation, some EOSIO genesis users have actively activated the EOSC mainnet tokens and participated in the community and ecological construction. Through creating EOSC accounts, Some non-genesis users have purchased from the secondary market and participated in EOSC mainnet community governance and ecological construction. At present, the EOSC mainnet has been greatly improved in terms of the on-chain governance and underlying protocols, including improving the voting mechanism, adjusting the inflation rate, adjusting the secondary distribution, etc. EOSC has become another mature blockchain network of EOSIO system. And EOSC tokens officially got listed on the mainstream centralized exchange KuCoin, which is more convenient for buying and selling tokens in the secondary market.At present, the new EOSC tokens mainly come from the additional issue by each block and the activation of the genesis mapped accounts. Each of the block issuance has been clearly defined according to the governance model. The annual inflation rate is 20% with corresponding additional issue allocation mechanism, and the treatment of unactivated tokens of genesis accounts has always been the focus of community discussion. In October 2018, the community had been discussing the tokens of unactivated genesis accounts for more than a month. In view of the fact that the unactivated mapping accounts did not participate in community governance nor make any contribution, the community adopted Unactivated Genesis Account Lockup Plan ProposalFIP#3 proposed by Awake, jiqix, EOSOU, and Walian, locking 80% of EOSC tokens of unactivated genesis accounts, keeping the activating right of the remaining 20% EOSC tokens, to encourage non-genesis users to participate in the EOSC community construction as soon as possible.While after more than a year of operation, some genesis accounts still have not activated and claimed free EOSC. Correspondingly, some new members of the community recognize the EOSC consensus, actively purchase tokens from the secondary market and participate in community governance and ecological development. On the basis that the token mapping was only a token allocation model for EOSFORCE mainnet launch, the future community and ecological development will rely more on the consensus of existing members.In order to balance the fairness of community governance, the following plan is proposed for the community and BPs to discuss.1. Destroy Unactivated Genesis Account LockupPlan Proposal FIP#3, 80% locked genesis accounts and their tokens.2. Destroy Unactivated Genesis Account LockupPlan Proposal FIP#3, 20% unactivated genesis accounts and their tokens.3. Once the above-mentioned destruction takes effect, the mainnet will issue new tokens in the future, and the inflation will be calculated based on the total amount of tokens after destruction.The above plan is just a proposal, which is going to be determined by the voting at EOSFORCE Mainnet BP Meeting.August 13, 2019

EOSFORCE

19. 08. 13

EOSC Weekly Report #55

2019.8.5–2019.8.11Work Completed1. Released EOSForce mainnet v1.7.0 with a series of APIs added to simplify the development of chain-related applications.2. Implemented the punishment mechanism for block missing.3. Implemented EOSForce decentralized budget system.4. Refined EOSForce Docker support according to the community practice.5. Collated the new EOSForce system contract document.6. Reconstructed the codes of Codex.relay system contract according to the new cdt.7. Confirmed the plan of extending and improving the voting-related Action to enhance user experience.8. The wallet supported fix-time voting.Plan for Next Week1. Test EOSForce new system contract, and prepare for the update of v1.7.0.2. Cooperate with the community to update EOSForce system contract.3. Collate the design plan of Codex.Relay new economy model , and update Codex.Relay system contract accordingly.4. Collate EOSForce decentralized budget system document.5. Merge EOSForce with eosio v1.8.0.6. Collate the new EOSForce system contract document.7. Reconstruct the codes of Codex.relay system contract according to the new cdt.8. Reconstruct transaction-related contract of Codex.relay.Community News1. EOSC was selected as the first project for KuCoin Upstake Program and officially got listed at 18:00 on August 8, 2019 (UTC+8).2. BPs multisig to implement A Proposal to Adjust The Upper Limit of EOSC Mainnet Contract Deployment. If the proposal is passed through, EOSC mainnet will support the more complex contract deployment.3. KuCoin exchange airdropped EOSC to users who meet the generating snapshots conditions.4. Cyborg was invited to visit eosou.io community, analyzing and discussing on the evolution of EOSC economy model in depth.5. At Lucky 8 Carnival Red Envelopes Giveaway held by KuCoin, red envelopes containing 110,000 EOSC was given away in the community.

EOSFORCE

19. 08. 11

EOSFORCE Weekly Development...

EOSC Weekly Report #542019.7.29–2019.8.4Work Completed1. Planned the upgrade of EOSForce mainnet v1.7.x.2. Recomposed EOSForce system contract document, refined the mechanism description, and added the new functional description.3. EOSForce chain API added the interfaceof get_vote_reward to obtain the account voting reward value.4. Improved EOSForce heartbeat mechanism, simplified the heartbeat-related configurations.5. Implemented the punishment mechanism of block missing.6. Designed the plan of on-chain account system of EOSForce decentralized budget system.7. Designed the plan of block extension information compatible with EOSIO v1.8.x and subsequent versions.8. Designed the plan of on-chain account system of Codex decentralized budget system.9. Refined the testing of Codex.relay transaction contract unit.Plan for Next Week1. Release EOSForce mainnet v1.7.0 with a series of APIs added to simplify the development of chain-related applications.2. Implement the punishment mechanism of block missing.3. Implement EOSForce decentralized budget system.4. Improve the operational document of node deployment and upgrade, especially the operational introduction related to rerunning the block, to cooperate with the subsequent upgrade when merge with eosio v1.8.0.5. Collate the new EOSForce system contract document.6. Reconstruct the codes of Codex.relay system contract according to the new cdt.7. Reconstruct transaction-related contract of Codex.relay.8. Consult the community for the plan of extending and improving the voting-related Action to enhance user experience.9. Fix the Codex.relay problem reported in the testing.Community News1. KuCoin has launched UpStake program and selected EOSForce (EOSC) as the first project for this program. If the number of users and deposit amount meets the relevant requirements within a certain period, KuCoin will announce the trading opening date and time separately.2. Awake、eosou.io、JiqiX、Cindydaily and other BPs supported EOSC in the listing on KuCoin.3. Cyborg was invited to KuCoin China Tour and delivered an internal speech on “Governance Goals of Cryptocurrency Community.”

EOSFORCE

19. 08. 04

EOSFORCE Weekly Development...

EOSForce Weekly Development Report2019.7.22–2019.7.28Work Completed1. Designed a stability mechanism of EOSForce BPs with the implementation of counting statistical block-missing data and historical block-missing data.2. Implemented fix-time voting function of EOSForce.3. Added the API for getting chain setting information to EOSForce.4. Added the API for getting Action Fee information to EOSForce.5. Implemented the common Margin Contract of EOSForce.6. Refined the startup script of EOSForce test net based on the recent modification.7. Refined the new EOSForce system contract file.8. Implemented the optimization of integrating Codex.IO and Codex.relay with EOSForce.9. Refined the testing of Codex.relay transaction contract unit.10. Refined the layout of Codex.relay Depositing & Rewarding Model and some related formulas.Plan for Next Week1. Plan the update of EOSForce mainnet v1.7.x.2. Implemented the punishment mechanism of block missing.3. Design the scheme of EOSForce decentralized budget system.4. Collate the new EOSForce system contract file.5. Design the scheme of block extension information compatible with EOSIO v1.8.x.6. Design the implementation scheme of Codex Decentralized Budget System.7. Reconstruct the codes of Codex.relay system contract based on the new cdt.8. Cooperate with the community to test the Codex cross-chain system.9. Refine the testing of Codex.relay transaction contract unit.10. Fix the Codex.relay problem reported in the testing.Community News1. Awake published an article to interpret FIP#7 EOSC Mainnet Improvement Proposal, introducing the significant improvements that FIP#7 will bring to EOSC mainnet in details.2. Cyborg, the founder of EOSC Network, was invited to attend Blockchain Technology Empowerment Industry Seminar co-hosted by Deep Chain, Ningbo Government and cyzone in Ningbo.3.The airdrop activity of “Talk is cheap,show me the code” co-sponsored by EOSC community nodes, will airdrop 200,000 EOSC for developers.

EOSFORCE

19. 07. 29

EOSFORCE Development Weekly...

EOSFORCE Weekly Report 2019.7.15–2019.7.21Work Completed1. Transplanted the new EOSForce system contract of eosio.lock and eosio.msig.2. Implemented the common assetage mechanism and unicode.3. Added global voting state to display voting data and efficiency of optimization and execution.4. Improved Ricardian Contract of EOSForce system contract.5. Reconstructed the code of EOSForce system contract, adjusted the code structure.6. Updated EOSForce system contract based on the new EOSForce economic model scheme7. Cooperated with the community to update EOSForce mainnet to force-v1.6.0, preparing for the subsequent updates.8. Cooperated with the community to test Codex cross-chain system.9. Fixed the Codex.Relay problem reported in the testing.10. Planned the development of EOSForce system contract according to FIP#7 proposal.11. Designed the scheme of EOSForce fix-time voting, planned the update of compatibility mechanism.Plan for Next Week1. Design a stability mechanism for EOSForce BPs with the implementation of calculating the stability of BPs on the chain.2. Implement data statistics of block missing.3. Implement the function of EOSForce fix-time voting.4. Improve RPC configuration and contract API on the chain.5. Add update-friendly global state information.6. Refine EOSForce system contract file.7. Optimize the amalgamation of Codex.IO and EOSForce.8. Cooperate with the community to test Codex cross-chain system.9. Fix the Codex.Relay problem reported in the testing.10. Reconstruct the design of Codex.Relay contract based on the problem reported in the testing.Community News1. EOSForce Mainnet has completed upgrading to V1.6.0, which will support 2 resource models.2. The 11th EOSForce Mainnet BP Meeting was held successfully. BPs have voted to pass the EOSForce Mainnet Improvement Proposal FIP#7.

EOSFORCE

19. 07. 19

EOSFORCE Development Weekly...

EOSForce Weekly Report 2019.7.8–2019.7.14Work Completed1. EOSForce.cdt improved the support for EOSForce API and fixed abi generation problems.2. EOSForce system contract modified for cdt compatibility.3. Tested the new EOSForce system contract based on EOSForce.cdt.4. EOSForce merged EOSIO 1.7.4 updates.5. Planned the implementation plan and update steps of EOSForce new economic model.6. Cooperated with the community to test Codex cross-chain system.7. Fixed the Codex.relay issues found in the test.8. Codex.relay contract code reviewed and conducted Codex.relay performance testing.9. EOSForce Transaction version data compatibility tested.10. Planned the modification scheme of EOSForce Transaction compatibility with EOSIO HTTP API plug-in.11.Designed wallet modification scheme based on EOSForce new economic model scheme.12. Optimized the implementation of configuration contracts on EOSForce chain to simplify the following update steps.Plan for Next Week1. Update EOSForce system contract based on the EOSForce new economic model scheme.2. Cooperate with the community to update the EOSForce mainnet to force-v1.6.0 and prepare for the subsequent updates.3. Cooperate with the community to test Codex cross-chain system.4. Fix the Codex.relay issues found in the test.5. Reconstruct the Codex.relay contract design based on the issues found in the test.6. Enable EOSForce Transaction compatibility with EOSIO HTTP API plug-in development.Community News1. Tokenview wallet listed EOSC ‘daily profit’ current financial products with an expected annualized return of 26%.2. BP Jeepool, BP Jiuzhou capital and EOSForce development team have released the EOSForce mainnet improvement proposal V1.0, which is currently under discussion in the community.3. Cyborg, the founder of EOSForce, was invited to participate in the “Great Chinese public chain” hosted by Qufen to share the governance mechanism and cross-chain exploration practice of EOSForce mainnet.4.The EOSFORCE mainnet will be upgraded to v1.6.0.

EOSFORCE

19. 07. 12

EOSFORCE Mainnet Improvemen...

Proposer: Jeepool Jiuzhouziben Corce teamEOSFORCE.IO an EOSIO-based blockchain with different governance concepts, has been running stably for one year. EOSFORCE.IO’s governance has been gradually recognized by the community in practice. As the world’s first large-scale network of practice in Staking Economy, EOSFORCE.IO was the first to encounter some system models and community governance related issues. This proposal will propose improvements based on current network operations and community governance for community discussion and block producer’s parliament voting. Concept definition:BP: It indicates the block producer, or the super node. It’s one of the top 23 nodes based on the weighted votes ranking.Profitable node: A registered node that can obtain the rewards of voting.Current voting: There is no fixed period for users to participate in voting.Fix-time voting: Users choose to vote in different voting time periods.Weighted votes: The number of votes calculated according to different weights of the current voting and fix-time voting Remarks:Time periods presented in this proposal are the corresponding block heights on the chain. For ease of understanding, the time periods are used in this proposal. 1. Adjust the inflation rateIt is recommended to adjust the inflation rate. The additional issue amount is 20% of the total amount of the previous year’s token.2. Adjust the voting weightUsers participating in EOSFORCE mainnet voting can choose the current voting and the fix-time voting.Fix-time voting: users can select different voting periods to vote. The time periods are the block heights corresponding to 3 months, 6 months, 12 months and 24 months respectively. The tokens are locked during the fix-time voting period and automatically unlocked when it expires.Current voting: Users can vote without fixed period, and the voting tokens can be redeemed at any time. The redemption needs 3 days to unlock the block height.Weight of current voting: it is 0.2.Weight of fix-time voting: 3 months, 6 months, 12 months, 24 months correspond to different weights of 1, 2, 4 and 8 months respectively. Rewards of fix-time voting can be received at any time. The weight of the votes will be zero clearing after the votes expire. Remarks:1. Rewards of fix-time voting can be received and re-invested at any time, but the principal cannot be released before the end of the fix-time period.2. Fix-time voting and current voting can switch nodes at any time, just paying the fees of the system itself.3. The redemption of current and fix-time voting still requires a 72-hour block height redemption period.If this proposal is implemented, a transition period is required for the redemption of the vote. It is recommended it takes effect after the upgrade being implemented 3 days later.3. Reward and punishment mechanism of nodes’ block-generatingNode ranking is adjusted to be based on weighted votes.BP node needs to provide a deposit, and the minimum amount of deposit is 2 times of the node’s block-generating income at 2400 blocks height.The deposit will be deducted for the block missing of the block-generating node, and twice the deposit of the reward of the block will be deducted for each less produced block. More than 2 hours, it can propose to punish and offline the block height corresponding to the missing block and shorten the penalty time of missing block as time goes by.Remarks:The weight of votes will not be affected when the node changes.Propose that punishment to make node offline must meet the requirement that the voting agrees are more than disagrees by 10 votes. The penalty for missing blocks is split equally between the user who proposes the penalty and the profitable node who votes “yes” (50% for the proposers and 50% the nodes who votes yes). There is no reward for voting users when they are punished. After the penalty period, the nodes can make up the deposit to enter the normal election and get the income of voting.3.The development team needs to improve the basic tools of operation and maintenance.4. Node rewardsThe EOSFORCE mainnet nodes are divided into BP nodes and profitable nodes.10% of the total amount of inflation is distributed by the block-generating nodes in proportion to the number of blocks.10% of the total amount of inflation is distributed by all profitable nodes’ rewards according to the proportion of voting weighted votes.For 50% of the total amount of inflation, the nodes can freely adjust the dividend ratio. Remarks:1.Any node rewards can be received when the rewards are over 100 EOSCs.5. Establish a decentralized budget system**1. By establishing a decentralized budget system on the chain, anyone can initiate a budget proposal. 30% of the inflation issue goes into the budget system and does not impose a total amount limit. The decentralized budget system has separate account permissions, and account permissions are owned by the system. The approval authority is owned by the management committee.2. The sponsor needs to pledge 100 EOSC as deposit for the proposal to prevent bad proposals. The deposit will be returned after the proposal is passed.3. The proposer needs to specify the objectives of the proposal, the implementation details (cycle, cost, amount) and the return that the proposal will bring.4. After the proposal is approved by the management committee, there will be a 7-day publicity period. If more than one-third of the profitable nodes are opposed during the publicity period, the proposal can be rejected. If the proposal is not rejected during the publicity period, the system will automatically issue the award to the applicant’s account on a monthly basis after the publicity period. During the award payment period, the management committee and the profitable nodes are greater than one-third of the veto, and the proposal award can be suspended.5. After the proposal has passed the publicity period, the proposer will get the EOSC tokens applied for in the next block award to implement the proposal content.6. Establishing the EOSFORCE Mainnet Management Committee mechanismThe EOSFORCE network management committee is designed to manage and approve proposals for a decentralized budget system, monitor the implementation of the sponsors, and promote a more equitable distribution of the decentralized budget system. Hereinafter referred to as the management committee.The initial membership of the management committee shall be 7 seats, followed by 2 seats every six months with a maximum of no more than 100 members.Any individual or organization may run for membership of the management committee. The governing council is made up of the top seven members from the first 100 profitable nodes, and the yes vote is 10 more than the no vote.The management committee has the right to review and approve the decentralized budget system, but does not have the ownership. The ownership is owned by the system.Remarks:The initial three members of the management committee are elected by the development team and the other four members are elected by the community.The term of the development team is tentatively set at 2 years, and the personnel shall be designated by the development team; The term of office of community quota is six months, each person can at most serve two terms.For a smooth transition, it is recommended that the management committee be managed by the development team for the first 3 months. The transition begins after three months, with the withdrawal of one seat per month until three seats remain, and the community sets the selection criteria for the members of the management committee during the three-month trusteeship period.All proposals need the approval of more than two-thirds of the management committee to become effective.The management committee shall set up an impeachment mechanism. Anyone who initiates impeachment can initiate impeachment, and any member who passes the vote of more than 1/3 profitable node can be impeached.Election criteria for the management committee are set by the block producers.7. Establish a referendum systemEstablish a referendum system that has the ultimate power on the chain, and more than two-thirds of the votes can veto any resolution.The above is only a proposed scheme, and the final result is still to be determined by the EOSFORCE mainnet block producers parliamentary voting.

EOSFORCE

19. 07. 10

EOSForce Weekly Report 2019...

EOSEOSForce Weekly Report 2019.7.1–2019.7.7Work Completed1. Cooperated with the community to upgrade EOSForce mainnet.2. Cooperated with the community to test Codex cross-chain system.3. Improved the new EOSForce economic model scheme and delivered the final scheme document.4. Improve the new Codex economic model scheme.5. Fixed the Codex.relay transaction contract issues.6. Codex.relay contract code reviewed and the code style optimized.7. Added transaction data’s version into EOSForce transaction extension data to be compatible with EOSIO transaction structure.8. Provide technical solutions to scatter issues.Plan for Next Week1. Update the EOSForce system contract based on new EOSForce economic model scheme.2. Plan the update steps of the new EOSForce economic model scheme.3. Cooperate with the community to test Codex cross-chain system.4. Fix the Codex.relay problem found by testing.5. Improve the Codex. Relay synchronization node configuration tool.6. Review the Codex.relay contract code and conduct the performance testing of Codex.relay.7. Test the compatibility of EOSForce Transaction version data.Community News1. The EOSFORCE mainnet is upgraded to extend the resource model. This upgrade will significantly improve the contract performance of the mainnet system, making it seamlessly compatible with the EOSIO-based DAPPs.2. The community discussed the EOSFORCE mainnet improvement proposal v1.0, including lock-up tokens, inflation rate, user voting, node rewards, decentralized budget system.3.CODEX community set up an interim management committee, which aims to improve CODEX economic model, community governance and promote the launch of CODEX mainnet.

EOSFORCE

19. 07. 05

The Blockchain Industry Wil...

The Blockchain Industry Will Have the First Technical Standard Debate: EOS-VM Take the Lead in Virtual Machine RaceAuthor: Cyborg of EOSForceEOS-VM is an important cornerstone for EOS.IO to become a common blockchain protocol. At the same time, it surpasses EOSIO and will become the de facto blockchain virtual machine technology standard, and even stifles the virtual machine development of Ethereum and Polkadot in the cradle.0 PrefaceEOS.IO development team Block.One released the new EOS-VM on June 1, 2019. After large-scale testing, EOSForce team believes that EOS-VM will become the most commonly used VM and the de facto standard of VM in blockchain industry. As we mentioned in the article “EOS.IO will implement the most complicated hard fork upgrade in history”, several branches are under active development, and EOS-VM is just as important as the version 1.8.0. The branch began in July 2018. From the submission record, the early EOS-VM had no particularly compact development plan. However, since 2019, after a series of intensive developments, the EOS-VM project as we see it today was initially completed.If EOSIO version 1.8.0 makes Block.One’s determination clear on EOSIO, EOS-VM gives us a glimpse of Block.One’s ambitions in the blockchain industry.1 What is a VM?VM is called virtual machine, which can be understood as the running environment of smart contract in the context of blockchain. We can take smart contract as an analogy to HTML in the Internet, blockchain system as an operating system, VM as a browser, and various dapps based on smart contract as various websites in the Internet.Ethereum has completed the first smart contract function in blockchain system, and its EVM virtual machine is also the mainstream development environment for early smart contract developers. Meanwhile, many projects have borrowed Ethereum’s VM, such as TRX’s TVM.However, EVM has its limitations. The efficiency of virtual machine is extremely low compared with mature virtual machine systems, and it is difficult to support more complex applications and environments.Mature virtual machine system consists of a series of large projects, in current environment, it’s hard to achieve a complete mature virtual machine system from scratch and is also not necessary. Because for such a huge engineering project, starting from scratch means that developers and communities have to bear a lot of compatibility and learning costs. The best way is to develop virtual machine implementations for blockchain projects based on existing mature virtual machine standards.Therefore, most of the blockchain projects choose to use an existing mature virtual machine implementation, it can be said that WebAssembly is the most suitable virtual machine. In addition to EOSIO, Polkadot also chooses WebAssembly, and Ethereum is also developing webassembly-based ewasm project.WebAssembly has become a very important part of the blockchain world, whether it’s “The Lesser Evil” or not.As a high-performance decentralized smart contract platform, the virtual machine implementation used in EOSIO is a very important part of the entire project. When reading the early EOSIO implementation code, it will be found that when the virtual machine is revoked, the EOSIO implementation code did a very strict encapsulation to hide the details of the virtual machine implementation. It can be seen that the EOSIO project will make significant continuous improvements in the virtual machine.//A rare interface wrapper in EOSIO chain implementationClass Wasm_interface {Public :Enum Class Vm_type {Wavm ,Wabt};…Private :Unique_ptr < struct Wasm_interface_impl > My ;…};From the earliest use of ‘wavm’ virtual machine to the later support of ‘wabt’ virtual machine, Block.One has been improving the support of virtual machine and preparing for multi-virtual machine compatibility.Eventually, EOSIO took on a higher challenge and developed a new EOS-VM, to be used as EOSIO’s virtual machine implementation. If EVM is a blockchain virtual machine, EOS-VM will be the first virtual machine to be commercially available on a large scale.2 What is EOS-VM ?Let’s take a look at what EOS-VM is. EOS-VM is a wasm runtime dedicated to blockchain systems.In a blockchain system, contract code is compiled into bytecode, which cannot be run directly on the operating system. Instead, an executor is needed to execute these contracts. In a software system, the executor can be regarded as an abstract “machine”, and EOS-VM is such an executor.EOS-VM mainly does four things :First, EOS-VM is responsible for loading and parsing the compiled smart contract bytecode, known as wasm.Second, EOS-VM is responsible for allocating resources to the bytecode as it runs. Of course, for smart contracts, the available resources are memory.Third, EOS-VM is responsible for providing out-of-vm API calls to the bytecode of smart contracts.Finally, the EOS-VM is responsible for executing bytecode to compute the results of smart contract runs.As for EOS-VM, eosio:: VM ::backend class is the gateway for entire virtual machine system calls. In the tools directory, there are two testing tools that use the EOS-VM virtual machine. Those who want to understand the EOS-VM implementation in detail can read the EOS-VM code.Int Main ( int Argc , char** Argv ) {…/ / Set the watchdog , limit the running time to secondsWatchdog < std::chrono::nanoseconds > Wd ;. wd set_duration (std :: chrono :: seconds (3));Try {…/ / Load wasm bytecodeAuto Code = Backend_t::read_wasm ( argv [ 1 ] );/ / Create an execution environmentBackend_t Bkend ( code );Wd . set_callback ([ & ](){. bkend get_context () exit () .;});…// ExecuteBkend . execute_all ( & wd );} catch ( … ) {}Return 0 ;}Here is the main job of EOS-VM, but if that’s all, there is no difference from wavm and wabt. In addition to doing the basic necessary work, EOS-VM makes some important improvements and optimizations for the blockchain application scenario. Let’s take a look at some of the important improvements to EOS-VM in combination with the documentation and code implementation.3 Important improvements to EOS-VMEOS-VM has made a number of improvements according to the blockchain application scenario and it’s a great gift to smart contract developers.Let’s look at some of the improvements in the EOS-VM README documentation, and then look at how EOS-VM does it in the context of the existing EOS-VM code.In early EOS-VM README document, Block.One listed the following improvements:1) Satisfying the needs of a blockchain.2) Security built into the framework.3) Performance centric design.4) Light weight and easy to integrate solution.5) Effortless extendability.The current README has been changed to a more understandable description for non-developers:● Extremely Fast Execution (6x faster than WABT)● Extremely Fast Parsing/Loading (20x faster than WABT)● Efficient Time Bound Execution● Deterministic Execution (Soft Float & Hardware Floating Point options)● Standards Compliant● Designed for Parallel Execution● C++ / Header Only● Simple API for integrating Native CallsLet’s break it down one by one.3.1 Meet the needs of the blockchain scenarioFirstly, Block.One’s positioning of EOS-VM is “A VM for Blockchain”.It means that EOS-VM adds a lot of the specific functionality needed for the blockchain to WebAssembly. At present, there are mainly three aspects:First is the support of floating point numbers. Many developers are often one-sided that floating point arithmetic is inaccurate, and cannot be used for blockchain system. In fact, it is not the case. Just for some different hardware, because of some historical reasons, the floating-point arithmetic of the hardware has some difference. The best way to solve it is to use softfloat library and do not use the machine hardware floating-point numbers. So floating-point computation results of different hardware machine are the same. Of course Block.One also mentioned that if you don’t care about all platforms keep floating-point arithmetic, you can use hardware-based floating point arithmetic, which is much more efficient than using softfloat. And it is typically used when the hardware of node machines remains unified.Softfloat library is also integrated in EOSIO, but the previous implementation is embedded in the chain, native virtual machine itself does not support it. Now it is incorporated into the virtual machine implementation and can reduce the development cost of other blockchain using EOS-VM.The second is that EOS-VM adds a watchdog mechanism to ensure run time limits on bytecode. A watchdog mechanism that imposes resource usage restrictions on contracts at a fine-grained level.It is so important that a later section of the introduction document is needed to describe it.There are a lot of messy code in EOS in dealing with the problem of contract execution timeout. For a Turing Complete smart contract, the biggest difficulty is that if we don’t perform the contract again, we will not be able to know its execution cost. Therefore, in EOS, it is necessary to determine the consumption time while executing smart contract. VM is a black box in the environment of EOS blockchain, so it will be very difficult to determine the contract execution time outside of VM. If EOS-VM provides built-in support, the implementation is simple and avoids problems in this area.Finally, there are some virtual machine execution boundary restrictions. These boundary restrictions may appear to be some functional limitations at first glance, but in the blockchain application scenario, these restrictions do not bring the actual functional limitations, but based on these assertions, EOS-VM can be greatly optimized.3.2 Built-in security supportA blockchain system that supports smart contracts can be seen as a common computer, and common means that users must be restricted, which would pose a big security problem if users could run their own code without restriction. For the public chain, it is not acceptable.The security issue here is twofold: the security of code behavior and the boundedness of code consumption.First, EOS-VM guarantees type security through built-in types, and uses the system-provided mechanism for sandboxing through an optional allocator.In addition, the mechanism of watchdog mentioned above ensures the running time limit of running bytecode. For the public chain, if there is no effective mechanism, it will often cause some security problems. EOSIO has previously had the problem of blocking attacks based on delayed transactions, which is essentially the problem of not effectively and carefully defining the use of resources. Ethereum’s early hard fork was aimed at solving similar problems.Finally, EOS-VM does not trigger unlimited recursion or circulation at any time, strictly limiting the number of crashes or unlimited hang-ups that WASM can cause intentionally or unintentionally.The built-in security will greatly improve chain’s security while also providing a controllable security guarantee.3.3 Design for high performanceIn many cases, specialization is the best optimization. In fact, if WebAssembly is fully compatible, there is not much space for EOS-VM optimization. But for scenarios of blockchain requirements, many WebAssembly designs are not required. EOS-VM does a lot of specialization based on this, which means that the performance of EOS-VM is also greatly optimized.The performance of EOS-VM mainly benefits from the optimization of its built-in types. EOS-VM has built-in data types required by most contracts, which can be optimized by EOS-VM.In particular, ‘variant’ is not a native function. It may cause serious type securty problems if you directly use ‘union’.Although ‘variant’ can guarantee security and ease of use in the implementation, if it is not integrated into the virtual machine layer, its complex implementation will bring a lot of performance losses.‘vector’ is similar. If you read the current EOS system contract, you will find that vector is widely used. It is indeed very convenient to use vector for contract design.But many performance-sensitive developers may feel “uneasy” about this, and now the VM is directly integrated with vector, you can expect them to be “more comfortable” to use it.Today’s EOS contract development relies on a fairly small base library, which means that every contract using these base functions integrates their implementation code, bringing a lot of base library code into the wasm layer.With EOS-VM now embedding these base types in the implementation layer of virtual machines, the performance optimization space is naturally greatly improved.3.4 Lightweight and easily integrated architectureEOS-VM is in the form of pure header files, which means that EOS-VM can be embedded in almost any C++ project.At the same time, the design of EOS-VM makes it can be well adapted to multi-threaded environment. C++ multi-threaded programming was difficult and it was often necessary to avoid many problems to build a library that could run securely in the concurrent environment.EOS-VM does a lot of work on this issue to avoid repeating the “mistake” of STD ::string in a multi-threaded environment.There are more advantages of pure header files and EOS-VM has become much like the widely used LUA, which is also known for its lightweight runtime. It is foreseeable that more non-eos and even non-blockchain projects will use EOS-VM in the future.3.5 Highly scalableEOS-VM has a well-designed structure that is better than EOSIO’s code structure in some ways.The EOS-VM was designed with extensibility in mind, and there is little to expand or modify the backbone of a VM because its functions are just the four things mentioned above. However, for different application scenarios, its bytecode format and functions must be expanded and modified. EOS-VM has been designed in response. The visitor pattern is heavily applied, making it easy to add functionality to the entire VM without changing the class architecture.Many people think that there is no advantage for good architecture. After all, you can’t think of “well-architecting” as an “unprecedented” new feature.However, in the case of project development, a good architecture will determine the subsequent potential of the whole project.In general, reading current EOS-VM projects gives you a sense of ‘lua’ or ‘redis’ projects, which are small, compact, and clean. Although the heavy use of C++ features will confuse some beginners, it will not affect their understanding of functionality, and we believe that EOS-VM will play a bigger role in a wider range of areas in the future.4 The impact of EOS-VM on the EOSIO ecosystemEOSIO is an open source software. There are several blockchain networks launched by community with different functions and governance concepts based on EOSIO, such as EOS, EOS force, ENU, Telos, worbli, BOS and other networks, which have been developed with the technical support of Block.One. The innovation of EOS-VM will benefit all public chains based on EOSIO.From the perspective of existing implementation, EOS-VM will try to maintain compatibility with the current EOSIO virtual machine implementation, and if there are incompatibilities, it can also be differentiated based on version in abi. In the future, even if there are a lot of blockchains that have made a lot of improvement on the underlying EOSIO code like EOSForce, it can be easily compatible.In the future, developers of EOSIO-based public chains will be able to integrate EOS-VM into the chain, while maintaining the existing support for wasm.EOS-VM can bring many benefits and impacts to the chain:4.1 Saving user resource consumptionAs mentioned above, using EOS-VM can improve chain’s performance, and users can save a lot of resource consumption on chain by using smart contracts running on EOS-VM.In EOSIO-based public chain, there are usually three main resources: CPU, NET and RAM. CPU is mainly settled by the actual time consumed by contract operation. NET is mainly related to the size of transaction, while RAM is mainly determined by the memory size used by the state transformation brought by the contract.At this stage, EOS-VM will mainly save user CPU resources, which is now the main resource limitation of EOSIO network. For EOSIO network, NET resource consumption is often fixed, while RAM can stimulate node to upgrade through continuous additional issuance, so that the supply of RAM can be increased on the network. From the perspective of hardware, the RAM upgrade space supported by current server performance is enough.But for the CPU, the current limit is significant. As BM said in telegram, Intel hasn’t made 100 terahertz CPU. It is just a joke, but the current server’s CPU performance limit is relatively large. For server, it is mainly parallel computing ability enhancement in recent years. The performance of single core has been improved but is still insufficient.Adding parallel computing support for EOSIO is a relatively long process, even if EOSIO can support parallel computing, it will be limited by single-core computing performance. Because for the contract, its computing process is still a single-thread. Improving the efficiency of virtual machine is very useful for the chain based on EOSIO.4.2 Make the chain more extensibleBoth the code and the architecture of EOS-VM are fairly straightforward, and in order to keep it simple in the form of pure header files, Block.One did not even introduce its fc library.Most developers can easily read and understand the design and code of EOS-VM by simply understanding the definition documentation of wasm bytecode.In this way, developers can easily reuse EOS-VM, especially for chains based on EOSIO technology.Developers can simply add new types to meet the specific needs of a particular chain.4.3 Simpler development toolsEOS-VM is in the form of pure header files, which means that EOS-VM can be embedded in any C++ project, and with simple processing, EOS-VM can also be used in projects based on other languages.For example, interp in EOS-VM’s tools requires less than 100 lines of code to build the runtime environment of EOS-VM, which is useful for the tools for developing EOSIO contract.Many beginners of EOS contract development want to debug contract code, which is almost impossible in the past. Although a native lib is provided in the new CDT, it cannot perfectly simulate the running environment of the contract. While “Good code doesn’t come out by debugging”, the lack of a debugging environment can be inconvenient.On the other hand, we also have to consider the integration of contract runtimes with existing development tools, and EOS-VM is a good fit for this.Through EOS-VM, EOSIO development ecosystem and development efficiency will be greatly improved in the future.5 EOSIO is evolving towards a true protocolUnconsciously, EOSIO’s official slogan has changed from “the most powerful decentralized application platform” to “ Build on Change. Build on EOSIO”.Similarly, in the design of EOS-VM, the developers have no obvious sense of the existence of EOSIO and DPOS consensus mechanism. The design of EOS-VM is quite independent.If you have been looking at EOSIO development, you will find that the EOSIO contract layer is gradually de-eosio. From renditions such as’ eosio_assert ‘to’ check ‘to refactorings such as the complete removal of c API calls from CDT, developers will encounter fewer and fewer “EOS” in the current EOS contract development.A typical example is the contract migration between different EOSIO sister chains. The CDT based contracts have fewer differences between different projects nowWhile the early community was bothered by incompatibilities such as enu caused by a large number of unnecessary name changes, now developers can hardly feel the incompatibilities caused by enu name changes when using CDT tools.All this means that EOSIO is evolving towards a practical protocol.In the early days, the Block.One team was not eager to build abstract protocols and formalized yellow books like other projects, but carried out EOS development with a very pragmatic attitude, which also made EOSIO, the mainnet of the public chain, launch much earlier than other “third-generation” blockchain projects.We believe that the block. one team will not always “build cars with full head”, but adopt a bottom-up approach to continuously develop the EOSIO ecosystem. It will evolve into a true protocol, and eventually become a highly competitive DE facto standard of blockchain protocol.6 Block.One hits the first shot in the battle over the blockchain standardOne is the first shot in the battle over the blockchain standard.For a long time, any software subdivision has been seeking for the integration and unification of technical standards, which is not enforced by centralized organizations, but gradually recognized by the mainstream market through the software itself, and finally becomes the DE facto technical standard.And in the field of blockchain VM, the performance of old virtual machine such as EVM is poor and the single function of virtual machine cannot take complex smart contract. The virtual machines based on general design will become the essentials of future mainstream blockchain projects. Currently, the only option for such blockchain project is EOS-VM, which leads the industry for more than a year and will become the standard of the best smart contract operating environment. Its industry status will be similar to ARM’s in the mobile chip industry, and even ETH’s smart contract is expected to run on EOS-VM in the future.Even we can boldly assume that EOS-VM will not be limited to the blockchain industry, and will be used in traditional software development fields like game engines, databases, and web frameworks due to its excellent design and implementation.7 Encryption community’s open source policy and technical standards monopolyAs we know, Block.One always emphasizes that it is an open source organization when raising funds from the community, and all the money raised will be used to develop open source EOSIO software to feedback to the community, which also brings a lot of contributions to the cryptographic economy community.But EOS-VM is unlike any previous open source project of Block.One, which has made a rare reservation to the EOS-VM project. It means that the project is not just an open source library. Reserving rights deviates from the pure open source organization positioning at the time of funding and may even limit its usage scenarios through commercial licensing.Different from the traditional Internet industry, most of the encryption economy technology is open source, regardless of the expansion of the debate and governance philosophy are not involved in the level of technical standards. We will wait and see the impact of VM’s aiming at monopoly in open source encryption economy market.

EOSFORCE

19. 06. 25

EOSForce Improvement Sugges...

ForewordEOSIO is a software with great design. The continuous development of EOSIO by Block.One team has been widely recognized by the community in recent years, bringing the cryptoeconomics from concept to a new stage of large-scale commercial application.Based on different governance concepts, the EOSForce was born. And after a year, the EOSForce’s governance concept was gradually recognized by the community in practice.As the world’s first large-scale network of staking economy practices, we have also pioneered a number of problems. This article will describe the specific problems we encountered in the direction of community governance and the potential solutions. The problems EOSForce faced today will be encountered by other blockchain networks in the future. Hope that the community can take the initiative to think about and solve the problems in development, and set a better example for the latecomers.1. Who is EOSForce’s contributor?1.1 EOSForce BPs and VotersThe network of EOSForce is maintained by the BPs generating blocks in turns elected by the voters. Therefore, it is necessary to encourage voters to perform their duties of supervising and electing nodes, and encourage BPs to maintain network stability continuously.1.2 Block.One and its early donorsEOSIO exists in the form of open source code, so the donors of the codes are the genesis accounts when the mainnet launched. We launched EOSForce network based on EOSIO, so the donors of EOSIO source code need to be issued block rewards 1:1, and it should be the same with B1.1.3 Developers of EOSForceThe development of the public blockchain has moved from an era of decentralized community volunteer development to a formed development team, so how to continuously motivate developers and various tool developers is very important.1.4 Other individuals or organizations contributing to EOSForce2. What principles should incentive follow2.1 Blockchain security firstIn any case, the security of blockchain always comes first, which is why most of the incentives in most blockchain networks are given to nodes that maintain network security.2.2 Maintain fairnessThe Incentive of the network should be a unified rule for all. It cannot be a tool for the benefit of a minority interest groups. Therefore, we do not emphasize decentralization here. Decentralization is only a means, and our goal is fairness.POW is different from POS. The holders of POW networks are only equivalent to obtaining the dividend right of the network. The decision of network governance is in the hands of the nodes. And the holders of POS networks obtain the decision of network governance and network dividend rights. So fairness is particularly important. That’s why our development team chose to get token incentives from the system without adopting the traditional ICO approach.2.3 Keep openThe network needs to be open to ensure that anyone can freely join and leave the network at any time.2.4 Active development and evolution roadmapBlockchain is also a technology industry, and we need continuous development and evolution to adapt to the changing needs of our users.2.5 The soundness and evolution of the governance systemLiberalism is not anarchism or disorder. We hope that the governance of the entire network will proceed in a fair and continuously evolving order.3. We propose some potential solutions and hope to explore better solutions with the community3.1 High inflation rate + penalty for out of block-generating:High inflation rates and penalty for out of block-generating should come together.In the state of high inflation, participants in governance can fight inflation and indirectly increase turnout, so that the entire network is within the continued attention of its voters and cannot punish the node and its voting users. It will make the interests of voters and nodes who are concerned about their earnings consistent with the security interests of the entire network. We believe that a network first to achieve is an intrinsic value incentive of the positive cycle. As the value of the entire network increased with more developers and users, the token’s prices will produce a positive cycle.3.2 Release the 80% tokens locked by BPs to EOSIO donors 1:1, retain the continuous incentive of Block.OneEOSIO’s donors receive a one-time incentive. Whether they are willing to continue to participate in community building or choose to sell their own tokens to obtain income is a voluntary to deal with their own assets without excessive interference. As Block.One’s continuous improvement of the EOSIO underlying source code, it is desirable to continue to receive incentives.3.3 Minimum guarantee + handling fee model + mortgage resource modelWhen the mainnet launched, we saw some imperfections in the mortgage resource model, so we temporarily adopted the fee model, which is more friendly to users and guarantees the user’s operating experience. With the improvement of the mortgage model, we hope to restore a part of the mortgage model to make the user experience and developer experience friendly enough.4. A referendum system to correcting the issue of permissions in EOS practiceEOSEMLG’s practice on the referendum system is very encouraging. A good referendum system can make the entire network retain the will of the majority in an extreme situation. An online mobile referendum system can also make the governance of the entire network more fair.We found that the biggest problem with the EOSEMLG referendum system is the issue of permissions. It is critical that how the permissions of the referendum system and the BP’s permissions counterbalance each other.5. The need of a decentralization budget systemMost fair networks choose to reward 100% of blocks to nodes and voters, which can lead to reduced openness. We think that part of the block rewards should be awarded separately to other community contributors.The budget system should be generated from the block rewards, controlled by multiple signature of the nodes or by the executive team voted by the node. The actions that need to be rewarded include but are not limited to:Participate in the development of the public blockchainParticipating in the development of development toolsParticipating in the development of smart contractsParticipating in the maintenance of various public channels of the community and organizing various community activitiesEOSForce Development Team

EOSFORCE

19. 05. 31

EOS.IO will implement the m...

What does the popularity of hard forks mean?Author: Cyborg of EOSForceForewordEOS.IO development team Block.one released the EOSIO version of 1.8.0-rc2 on May 15, 2019. It is the most important releases of EOSIO since it became open source. This release will set the tone for EOSIO to rapidly iterate through hard fork upgrades in the future, and will allow the entire blockchain industry to revisit the importance of hard fork upgrades. Meanwhile, all users, wallets, exchanges and DAPP will be affected.In early 2019, some of the media started reporting a drop in the number of EOSIO code submissions, and we EOSForce team publicly responded that EOSIO has multiple developers submitting code every day in different branches, and needs to be tested before being merged into the main branch. 1.8.0-rc 2 is such a case, which has been under development since early 2019 or even earlier and its released on May 15, 2019.Next we will explain in details why this update is so important.Version: 1.8.0Github: https://github.com/EOSIO/eos/releases/tag/v1.8.0-rc21. The key improvements of 1.8.0-rc21.1 Scalability enhancement and code refactoring:In this release we see a large number of commits focusing on code refactoring and thread security.First, for code refactoring, many people often don’t care about these code changes that neither adding features nor improving performance, but from a development perspective, these actually constitutes an important foundation for the follow-up development. We can see that since the beginning of the year, the core developers of Block.one have been improving EOSIO ‘s code structure and gradually building an abstraction layer from the design level. The most obvious is the improvement of EOSIO.cdt, which makes up the framework of EOSIO. Unlike many teams that start with a large architecture, the EOSIO was developed with a pragmatic, bottom-up approach by the Block.one development team.In version 1.8.0, developers at Block.one split a lot of huge classes, stripping away some of the complex logic scattered around, such as the ’pending_block_state’ related state management has being stripped out from ‘block_header_state’. And the ‘transaction traces’ is also reorganized this time.Another aspect is about multi-thread, In the recent period, there are a lot of commits about thread security, in preparation for the next step of multi-thread related development, Block.One team attaches great importance to multi-threading in the development of 2019. This refactoring will make the multi-threading described in the EOSIO white paper even better, taking TPS to the next level.As is known to all, multi-thread development in medium or large scale C++ software has always been a “ tar pit “. In order to ensure the stability of EOSIO while introducing parallel computing, Block.one team is not eager to develop new features related to multi-threading. Instead, patiently troubleshoot thread-security issues in your code and improve infrastructure support. At the same time, the corresponding multi-threaded implementation is introduced in a specific independent module suitable for concurrency, such as chain API and P2P module.1.2 Improve chain securityIn this version, the Block.one team fixed some of the resource computation issues left over from the previous section. There are many resource-related logics in EOSIO, and they are extremely scattered. In order to improve chain performance and avoid unnecessary computation by nodes, a lot of resource-related specialization logic has been added to EOSIO. This also caused the ambiguity of user resource computation in many specific scenarios. For the EOSIO chain, this brings a lot of potential security issues. The blocking transaction problem exposed by the delayed transaction in the previous stage is largely the problem of incomplete resource inspection.In addition, the problem of resource computation in some scenarios will also lead to the loss of users’ rights and interests, so it is imperative to modify this aspect.1.3 Smart contract securityThe EOSIO community has been plagued by smart contract security for a long time. DAPP developers have found a number of issues in practice in the past year. The Block.one team has absorbed these issues and made significant improvements. This update is more friendly to smart contract developers.For DAPP developers, for example, the good news is the long-awaited ` GET_SENDER ` API is finally coming to EOSIO, DAPP developers can use this API to determine whether the current Action is triggered by the inline action, thus can avoid a lot of attacks that triggered by inline action from attacker’s contracts. This update can partially solve the problem of random numbers that have been plaguing the community for a long time. It should be noted that even though this API can block many CURRENT attack means and the attack cost will be greatly increased, it does not mean that DAPP developers can rest easy. For developers, security issues should always be noted, there is no silver bullet that is once and for all.1.4 Hard fork upgrade mechanismUpdates in this area can make future hard fork upgrades more efficient while making a hard fork upgrade process not affect the user experience.Recently, Block.one added a lot of new features, including the ones mentioned above. None of them have appeared in the past updates. A main reason is that developers must guarantee the compatibility of EOSIO. The node can choose not to upgrade the node version. Obviously this will greatly hinder the development of EOSIO. The biggest difference between this version of 1.8.0 and the previous one is that this version is not compatible with the previous version. Also known as the “hard fork”, before this version, EOSIO did not have a mechanism to deal with hard forks. The hard fork process can have a big impact on the user’s use. In order to make future updates not have the same impact as this one, a series of hard fork upgrade mechanisms have been added to this update. In the future, the hard fork update can be smoother and more secure.In the past updates of EOSForce, the EOSForce team also encountered the same problem. So the chain configuration function was introduced. By this mechanism, the features of opening block height and chain maintenance state were added to the chain to solve the transition problem in the hard fork. Block.one’s countermeasures are similar. By introducing the protocol feature to solve this problem, unlike the EOSForce’s simple and universal solutions, Block.one’s design hopes to solve the feature’s compatibility problem more specifically. The design can be found in #6831.Here you can judge that there will be more hard forks in the development process of Block.one than before. The progress of EOSIO in the future will be significantly faster than in the past.2. Effects of EOSIO hard forkEOSIO first used hard fork to upgrade, so the impact is huge.2.1 Node: Most nodes should not have experienced a hard fork upgrade. If you strictly follow the hard fork requirements, all nodes need to replay the block. According to the current node configuration, most nodes need at least several days. Of course, there is a lazy way to directly use of snapshots provided by other organizations, but the downside is that if too many core nodes especially BPs update in this way, it will affect the security of the entire blockchain.2.2 Users: All P2P nodes such as exchanges, wallets, block explorers, DAPPs, etc. will be suspended over a period of time, all other external access will be interrupted and user perception is very obvious.Of course, the blockchain itself does not suspend, just for the security reason to suspend the interaction between the external and the chain.2.3 DAPP developers: In theory, the hard fork of the chain does not affect the operation of the contract. But considering that many DAPPs have adopted a semi-centralized architecture and there is a lot of logic running outside the chain and interacting with the chain. So a hard fork will inevitably bring certain risks.3 Benefits and risks of hard fork3.1 Benefits:In the Internet age, product iterations are commonplace. Developers release new versions almost every week, and users are used to updating to enjoy more features and services.Previously, the hard fork upgrade was almost very rare in the blockchain industry, because most of the blockchain consisted of decentralized free developers, so the development progress was slow and the nodes were extremely scattered, and the hard fork upgrade was more troublesome. For example, an overflow vulnerability in 2010 led to the creation of a 184 billion BTC out of thin air. Satoshi Nakamoto first released a new version of the hard fork upgrade to avoid the Bitcoin crisis. Later, after Satoshi Nakamoto left the community, Bitcoin is taken over by the community, and it is difficult to reach a consensus on hard fork upgrades, so the hard fork upgrade is rarely used.The Block.one team is a professional development organization, and the development progress has been exponentially improved compared to the previous blockchain project, so the rapid iteration to adapt to user needs has become the mainstream. In view of the current technical architecture of most public chains, if a large-scale functional upgrade is to be implemented, the hard fork upgrade is inevitable.3.2 RiskIf the block producers have bad intentions during the fork, the fork process becomes very dangerous.If some nodes join together to reject the upgrade, then there are two EOSs with a high probability.Block.one did some precautions: Although Block.one had a lot of development in the first half of 2019, there were a lot of new features, but this update only includes some necessary features and security issues to fix. After the feature is online, the hard fork will get smoother.4. Note for this hard forkThis is the first hard fork update of EOSIO, and it is not performed under an effective upgrade mechanism, requiring more effort from nodes and community.The EOSForce team has conducted several large-scale hard fork upgrades since the mainnet launched to iterate new features. Here we share some of the experiences in the hard fork upgrade:First, the more you prepare, the smoother the update. Before the update, the node must do a backup job. The current EOSIO node data is very large. When backing up a node, the efficiency of restoring the backup data must be considered. The backup data and the node must be in the same intranet. Don’t rely on someone else’s backup. Otherwise, it will take a long time to transfer backup data when there is a problem. The best way is to directly create a backup node for the node.Secondly, you need to pay attention to control the interaction of the nodes. During the update process, the entire EOSIO network will be in a semi-compatible state for nodes. At this point, if someone submits a transaction that triggers incompatible logic to a BP that has already been updated, it will cause the updated BP to immediately fork. Although the hard-fork function itself is based on the feature to manage whether it is effective, and the transaction that performs the logic error is generally not transmitted in the p2p network. But it is difficult to sure all actions cannot cause fork from nodes. Therefore, nodes, especially block producers, should pay attention to control interaction during the update process. The first is to control the opening of http API. Several RPC nodes can be opened properly, but there must be no direct p2p connection between RPC nodes and block producer nodes, nor direct p2p connection between nodes and other external nodes. so that key nodes can be guaranteed to run when hard forks occur.Finally, the update order needs to be controlled. If nodes can orderly update, even if there is a hard fork, most nodes will not be affected. The nodes in EOSIO are often divided into data nodes, block producer nodes, RPC nodes and synchronization nodes. It is easy to establish a “green zone” for the block producer nodes by controlling the interaction of the nodes, shielding the external influence on the core block producer nodes. At this point, the block node can be upgraded. After this, gradually update the block producer node and the external synchronization nodes. At the same time, an update window period should be reserved for data nodes and other read-only nodes in the community. The nodes of the community and the developer can be similarly, first establish a green zone by establishing a shielded synchronization node, update the internal node, and finally update the synchronization node. Finally update the RPC nodes after most nodes and all core nodes are updated. Then complete the update of the entire network.In fact, the means and deployment specifications mentioned above have long been a commonplace, but the maintainers of many nodes do not strictly plan the deployment of nodes according to the specifications. It is foreseeable that if the node maintainers are still not perfect node deployment, then it will be a concentrated outbreak of many problems in this update.In general, the more preparation, the better. Many problems are unpredictable, so it should be do one or more walkthroughs of your EOSIO upgrade before you officially update it.5. What is the meaning of hard forksHard forks should be a common technical term, but hard forks for different purposes can produce different results, so the community has a very different understanding of the hard fork concept.From a technical point of view, hard forks can cause new rules to be incompatible with previous rules, and if you get the support of the community owner, the high probability will have no effect.From a community perspective, if there are different consensus and technical routes when hard forks, the high probability community will split into two public chains, each supporting different routes.In 2016, the EAO crisis occurred in Ethereum (ETH). The founder Vitalik decided to roll back the transactions. Some people in the community did not agree to roll back the transactions. They believed that the blockchain ledger could not be tampered with and refused to roll back. Therefore, ETC was born (Ethereum Classic).In 2017, the congestion of Bitcoin (BTC) made the big-block supporters eager to improve Bitcoin, but there were different opinions in the community, so Bitcoin cash (BCH) was born.In 2018, when the EOS mainnet was launched, the EOSForce team proposed different governance routes, and then the EOSForce (EOSC) was born.We can see that the Block.one team has done a lot of preparation.6. The importance of this hard forkThis hard fork is the most important version since the birth of EOSIO. All public chains based on EOSIO such as EOS, EOSC, ENU, Telos, BOS, Worbli, etc. need to be upgraded through hard forks.As one of the highest level development organizations in the industry, Block.one is very bold in its development. This time, the hard fork mechanism has been added, which means that there will be at least two or three hard forks in the second half of the year.In the past, blockchains were very afraid of hard forks. Only the BCH community maintained a hard-forward upgrade for half a year. EOSForce also carried out several hard fork upgrades. With the development of node and community awareness, ‘hard forks’ will no longer be a scary word, but it will become a way of making progress in the blockchain, even if there is a new branch.This hard fork upgrade will bring more functions and better user experience to EOSIO. It can be expected that if you want to adapt the public chain to the development of the times, the upgrade method of hard fork will become the mainstream in the future.7. Recent community rumors about BM’s leavingRumors that BM has developed new projects have triggered panic in the EOSIO community.From the perspective of EOSIO, Block.one has made great efforts on EOSIO after the mainnet was launched. Continuous and efficient development has made EOSIO the most powerful decentralized application software platform. At the same time, there are teams like EOSForce, EOS Canada, BOS Core that have been deeply involved in the development of the public chain. Even if BM leaves the community, it will not affect the development of EOSIO.EOSForce team tracked the development progress of most of the world’s mainstream public chains, whether the development speed or code quality, Block.one has better performance in EOSIO development than other mainstream public chain development teams. There are a lot of branches that are as important as 1.8.0-rc2, and we are waiting to see.

EOSFORCE

19. 05. 22

Inflation, Centralization, ...

24 APR 2019 BY GREYMASS IN EOSIn this post, we’d like to outline concerns around EOS inflation that we believe haven’t been addressed in-depth. Our goal with this post is to demonstrate that there may be tangible benefits to EOS inflation that does not flow directly to validators (consensus participants), and tangible downsides to inflation that flows only to these participants. We hope that this contributes to the community conversation around these issues, and we look forward to hearing voter feedback and discussing these issues further.Centralization Effects of CryptocurrenciesCryptocurrencies are simple to analyze, mathematical structures of mini-economies with differing properties, often pre-defined and deterministic. Bitcoin, for example, will issue only 21 Million “units” before ceasing all inflation. This makes analysis quite unique — we can analyze these closed-body economic systems exactly and with high fidelity, observing properties such as money velocity and distribution on a total scale as all information is public. In this post, we will seek to analyze the property of centralization over time.There are many contributing factors in which a cryptocurrency system can have centralization forces — beyond the ones we think of commonly, such as accumulation of wealth. In Bitcoin, for example, we already observe miner centralization to select, large pools. In Proof of Stake (and the delegated variant) we see a similar phenomena; with a small, technically capable pool of potential consensus participants, the ability to decentralize is constrained by the number of capable parties. This debate continues to be on-going with Bitcoin. Proponents of “small blocks” argue that large blocks will forever burden newcomers with too much data, while proponents of “large blocks” argue that technology is advancing and the “forever burden” decreases with time and technological progress. In reality, the correct trade-off is likely somewhere in-between. Startup costs and long-term costs certainly can increase the centralization of the system, as newcomers are unable to afford to validate the system and the pool of potential consensus participants shrinks. Yet finding a correct balance between a technological cost that does not burden newcomers, and a system usable enough that it doesn’t drive newcomers away in the first place, is a fine line to walk.In Proof of Work systems, present rewards do not affect future rewards, as the ability to achieve a PoW is an external factor. This is what makes PoW systems “permissionless” — their consensus mechanism is not a closed-body system, and external input (in the form of electricity and ‘work’) is required. With DPoS systems, we have an interesting reward structure that is quite different compared to Proof of Work. In many DPoS systems the supply is not fixed but rather inflationary. This means that present rewards can actually affect future rewards. If we award those responsible for consensus with rewards that give more influence over consensus, then the system’s decentralization can be affected in the long-run.Inflationary RewardsTo understand this problem, we need to take a step back and refresh our understanding of how exactly a property like inflation works in a closed-body system. As an example, suppose we have two people, Alice and Bob, each of whom have 100 units of currency. If Alice and Bob are both given 100 more units each, and each now has 200 units, has anything changed? In a closed body system, we have done absolutely nothing — Alice had 100/200 units (50% of the currency) and now has 200/400 units (still 50% of the currency). Inflation that is uniform has no effect other than accounting of units. In the “percentage of currency supply” reference domain, inflation can only move the percentages. If instead we give 100 units to Alice but do not give Bob any more, then Bob still has his original 100, but Alice has 200. We’ve “inflated away” Bob’s value — he has gone from owning 1/2 of the supply to owning just 1/3rd, and Alice has gone from owning 1/2 to owning 2/3rds.Of course, the unit count (the number itself) also has psychological effects — perhaps too complex to discuss simply here, and a topic for another time. The important takeaway here is that we must think about inflation as changing the percentage of ownership of the total supply. With inflation, for each win, there must be equal but opposite loss.So how does this actually affect blockchain systems? In DPoS, control of consensus is determined by votes from the supply. In a simplistic form, those with the most supply of the currency will de-facto control consensus. And yet we reward consensus participants with rewards that inflate away those not in control of consensus. Imagine that Alice, Bob, and Charlie each own 1 unit of currency, for a total supply of 3. If they elect Alice and she inflates the supply by 1 and awards that to herself, she now has two votes (compared to 1 each for Bob and Charlie). Alice voting for herself is now impossible to overrule. When consensus is controlled in a closed-body way, eventually the present control of system snowballs into future increased control.We can call this a form of “asymptotic convergence”, whereby the supply collected by a specific entity, as a percentage of total outstanding supply, increases asymptotically in a closed-body system (i.e., it slowly gets closer and closer). While we have only used inflation as an example, this effect would also occur with fixed or variable fees, as well as with variable inflation, though the math would change slightly.Asymptotic Consensus ConvergenceWhen the supply of tokens is responsible for consensus, and the inflation is given to those presently in charge of consensus, then inflation can lead to centralization in the system over time. This is this asymptotic consensus convergence, whereby the control of consensus itself asymptotically converges.Of course, real-world systems are far more complex than the simple examples we have given. The consensus rewards are not always hoarded in full. To understand the effect, let’s make an analogy to physics. Suppose we have a box in the middle of a warehouse. If a constant force is applied to a box in a single direction, the box will move in that direction. If the force is opposed, the box will not move. In this analogy, the asymptotic consensus convergence is a fixed force applied in the direction of centralization towards the current elected set of consensus participants. This force can be opposed, but it would need to be voluntary. If the consensus participants always sell all their rewards (externalizing their value), the force is opposed in full.However, if any of the consensus participants collect any of the reward, the box moves — just a little bit. The more that do, the more the box moves. The force can be defined in terms of the reward:As an example, this would yield a curve that looks like the following, if we suppose a reward (via inflation) of 1% per year:https://www.wolframalpha.com/input/?i=(1.01%5Ey+-1)%2F(1.01%5Ey)+for+y%3D0+to+100In the above, we see the percentage of control in the system (that is to say, the control of the newly generated supply compared to the new total supply) go from zero to just under 10% in 10 years, and about 60% after 100 years. What this means is that, in that amount of time, the maximum rate the box could move in our analogy is at worst that amount (just by this force). We use the analogy of a force for a very important reason: opposing the force as an impulse only delays the immediate outcome, and does not prevent future effects — in our example, consider opposing someone pushing a box constantly with a single kick: while it may delay them temporarily, it does not oppose their constant pushing.While this doesn’t sound like a problem today, the numbers should be concerning. In EOS, the top producer is presently elected by only about 12% of the supply. However, there is a multiplicative factor of 30 for votes in EOS: should a group of 30 agree, they can collectively amplify their votes (by vote trading) by that factor. In this case, a collective could achieve this dominance in, at worst, 5 months, entrenching themselves in a position only solvable by getting more of the supply to vote for a different group (and hoping that new group is more altruistic in their voluntary efforts of opposing the centralization force). This is not a ticking time-bomb with a sudden explosion; rather, this is a slow and painful drowning, struggling to breathe while the air slowly escapes.In reality, the math gets complex quite fast when taking into account competing groups vying for a single dominating control of consensus. However, with some effort it can be proven that the largest collective (specifically, the set receiving the most votes from the current dominant set) eventually will win. This leads to a bit of a prisoner’s dilemma for those not within the largest collective — if you elect to join the dominating group, you may get ‘rewarded.” If you refuse, and they are able to form with others, you will get nothing.Counterbalancing the Centralization ForceIf you’re concerned about centralized participants forming an entrenched position due to inflation, then this argument has succeeded. Yet, we should consider not just how this problem exists, but how it could be solvable.There are a few drastic measures that one could take. One example would be removing inflation to consensus participants altogether. This would indeed solve the problem, but it would remove the incentive for node operators to work for the network in the first place. As another attempt to solve the problem, a separation of token properties could be made: tokens that are voting capable (of fixed supply), and tokens that are utility tokens (of inflationary supply). In theory, the consensus participants are only paid out in minted utility tokens, and thus do not collect voting influence over time. However, this doesn’t actually work! We’ve just moved the problem to a different domain, so long as they can swap these tokens on the market.Removing the inflation of voting rights completely is not the only solution, however. In fact, if a secondary source of inflation were added that went to a different source — a force in an equal but opposite direction — the centralization force could be balanced (or even result in net decentralization)!In our equation above, the reward refers to the amount of the supply the consensus participants are receiving relative to the total supply. If we increase the total supply in another way that is specifically not going to the consensus participants, then their dominance over the system would not increase. Let’s go back to our previous example with Alice, Bob, and Charlie: Suppose each had 1 unit and Alice gained her extra unit just as before. But now, suppose Charlie also received 1 extra unit as well for a different reason — Alice would have her extra vote checked and balanced. This would be in the form of additional inflation, for a different purpose. As with all inflation, there are winners and losers: in this case Bob is the loser by being “inflated away” — but perhaps he was also the least engaged or otherwise not participating in the system itself.Figuring out good reasons for a secondary, balancing force of inflation is, however, a hard problem. As we recall with the original problem of inflation — in which, if we consider only the percentage of ownership rather than arbitrary unit counts — inflation is simply a tool to move the percentage in the direction of one entity at the expense of another. Thus, we need to pick a winner (a new reward to some who are specifically not part of the consensus participants), and we need to pick new losers. You might think of an obvious solution — we could just choose the winners to be everyone who is not a BP! But this would be an exact counterbalance and would be equivalent to not rewarding the BPs in the first place.If you’ve been following the logic, then you know exactly where this is going next: worker proposals. Indeed, a clear solution to this problem is a secondary source of inflation that is guided by token holders into the hands of non-block producing entities that increase the value of the ecosystem. This could include funding to apps and services, grants and scholarships, and other expenses that could be made in the goal of improving the value of the network as a whole. It would be important to strongly encourage that block producers do not double dip into this fund, for if they do, the point becomes moot. With this secondary source of inflation, the centralization force would be countered, and could in fact become a force for decentralization. If the inflation to the community is greater than the inflation towards only the consensus participants, then, while the consensus participants may still be well paid for their efforts, their position is no longer the most attractive source of revenue.There are many ways in which a worker proposal system could work, but consider a very simplistic approach: duplicate the block producer structure, but only assign pay by weight (vpay) and no pay for blocks (bpay). This secondary set of organizations would be elected separate from BPs, are not part of determining consensus, and gain their own inflation — voted in place by the token holders. This would fit well for organizations that do not have technical or governance expertise, and could then spend all their time focusing on what they are good at; be it community outreach, marketing, scholarships, or other EOS business ventures. In fact, with this structure (or one like it), the consensus participants become further beholden to the community decisions, as more voting power is transferred into the hands of the community over time.SummaryIn this post, we’ve highlighted three important points that need to be considered when using inflation in a closed-body consensus system (like DPOS).Inflation itself is simply a tool to generate winners and losers in terms of ownership of total supply.If we award those responsible for consensus with rewards that give more influence over consensus, we end up entrenching those presently in power with more power.Thinking about solutions that prevent power consolidation is important, and one of the best ways to avoid it is with a counter balance — ensuring that a single party or group is not the sole recipient of network rewards.As the EOS community continues to debate the pros and cons of different configurations of EOS inflation, it’s important to remember the long-term and second-order effects that changes to this system can have. While direct decreases to the amount of inflation can seem like a positive outcome for token value, they should only be done in a way that ensures that the long-term health of the network remains sound. We believe that short term actions can create market movements in price, but long-term thinking drives true value creation. In order to achieve that, we must carefully consider how changes to critical parameters can affect the network’s centralization.We look forward to engaging in further community debate around these topics in order to work together to diagnose and solve the hardest problems facing EOS.— -Clarification UpdateSince the first release of our post, there has been a lot of generated discussion and feedback, which we think is great! However, there are a few repeated comments on our post that often misunderstand either the terminology or the math. This brief update seeks to help clarify some of this.First, there is some confusion on the use of the term “closed body”, with many arguing that “EOS is not a closed body”. To be fair, those with this position would be correct if we used the term “isolated system”, however “closed body” has important distinctions. In physics, in an isolated system neither matter nor energy can escape or enter the system. However, in a closed body system, only matter is preserved (and extraneous energy is often only modeled). To make this analogous with our EOS system, the EOS tokens are like matter: tokens do not escape or enter the system from a non-observed point; we can track with perfect fidelity the location of tokens. However, the wealth of the system functions like energy, with external factors at play. As much as we all wish we could use simple levers to control wealth, the only tools we have are for controlling tokens. Thus, our investigation looks at the token distribution, not wealth or economic activity — which are external variables. To further clarify why inflation is still a centralization force regardless of wealth, perhaps consider the following: even if no one sold tokens to consensus participants, they could still eventually control the supply. This is why closed-body analysis is still useful; it can be done independent of external factors.From this misunderstanding, the argument typically drawn is that the consensus participants will sell some fraction of their tokens rather than keep them all. This position (despite being unrelated to the use of closed body analysis) does hold merit in regards to affecting the rate of centralization over time. Yet, as we have not seen anyone discuss the math yet, lets do just that. The equation for this effect would look as follows:With rp being the individual participants’ (of size P) reward, and ep being how much of that is expenses (and not withheld). As we can see, this confirms our previous statement that, if rp == ep ∀ p ∈ P, then the system is stable. However, when ep is less than rp, the effect remains: the asymptotic convergence approaches the ratio of (rp — ep)/rp rather than rpitself, like a damping factor. As an example, if all participants have a ratio of 1/2, the curve would instead look like this, with an asymptotic convergence towards 50% of the supply rather than 100%.Finally, the breakdown into individual participants is important here: although the asymptotic convergence ratio is towards the sum of all participants, the participants could eventually greedily choose individual/new participants that increase control. For example, suppose half the participants had a ratio of 1/2, but the other half had a ratio of 1 (holding everything). This example has a convergence ratio of 3/4 in total, but interestingly, the set that held more can eventually replace the set that held less. This is because the set that withholds more of the inflation can eventually outvote the set that held less. To summarize: consensus participants not withholding their rewards only delay the process, and further, hand control over to those willing to withhold more.Finally, there are some questions about how initial distribution can affect the results. Once again, lets expand our formula to include initial distribution as a factor (don’t worry, this change is simple):Here, we’ve introduced a constant term ip, a participants’ individual initial ownership (for the purpose of the formula, this would be represented as fraction of initial total supply). As can be immediately noted, this summed factor can only end positive, and can only work to accelerate the timeline of asymptotic convergence. Indeed, this matches our intuition; taking into account initial distribution can only worsen the situation, it does not make things better.Article from:https://blog.greymass.com/eos/@greymass/inflation-centralization-and-dpos

EOSFORCE

19. 05. 10

Latest FAQ | EOSForce Commu...

1 EOSForce Mainnet Introduction1.1 EOSForce IntroductionEOSForce is committed to exploring a more open crypto economy infrastructure in practice. Through the continuous development of multi-chain architecture blockchain protocol, it meets the diversified consensus requirements of the crypto economy and promotes the application of blockchain technology in various fields.EOSForce.io, the most active parallel mainnet in EOSIO ecosystem, has been completed and launched, providing more user-friendly resource model, richer underlying support for developers and fairer governance mechanism for the community. The EOSForce.io mainnet asset can be activated by offline signing with the mapped EOSIO private key.1.2 What is EOSC? Is EOSC an airdrop token?EOSC is the token of an EOS mainnet launched by EOSForce community. It represents the assets on the EOSForce main chain and can be used for voting rewards, block generating, transferring and trading on exchanges.EOSC is not an airdrop token. Users can activate the EOSC account assets by offline signing with the EOSIO private key mapped before June 3, 2018 Beijing time.1.3 The difference between EOSC and EOSEOSC is the token of the EOS mainnet launched by EOSForce. EOS is the token of the EOS mainnet launched by EMLG. These two assets are different. Currently, AKdex.io Exchange has listed the EOS and EOSC trading pairs.1.4 Total amount of EOSC (Including the lock-up plan, and allocation of the rest part)The initial circulation of EOSC is 1 billion, and 94.6 million EOSC are issued annually to reward 23 BPs. The BlockOne team will be awarded a prize of 100 million EOSC unlocked every 10 years. And it will continue to do so without interruption.According to the proposal of EOSForce mainnet unactivated genesis account lockup plan, on December 20, the unactivated EOSIO genesis account will be locked with 80% of EOSC tokens, and replaced for the same amount of lock tokens. The remaining 20% can be freely used. Token increased annually will be adjusted appropriately according to the existing total amount of EOSC tokens in the mainnet.At present, the number of EOSC locked is 672,390,243, and the remaining is 327,609,757.1.5 Difference between EOSForce mainnet and EMLG mainnetThere is more than one EOS mainnet. Currently, the EOS community has launched several mainnets. The mainnet launched by EOSForce community is called EOSForce mainnet and is parallel to the mainnet launched by EMLG.When debugging EOS software, we found many unstable factors and there are certain asset security risks. Since EOS itself is a set of open source software, the official does not guarantee security and reliability of the blockchain launched by EOS software. This requires dedicated team for targeted development and testing to maintain the entire blockchain. Therefore, our team carried out strict tests on each function of EOSIO, upgraded and optimized the official codes, prioritized the security and reliability of the whole blockchain, and officially launched the EOSForce mainnet on June 22, 2018.EOSForce mainnet added the innovation of voting rewards incentive mechanism, improved the decentralization of one-token-one-vote, charged transaction fees to prevent DDOS attack, optimized the community governance of 23 BPs and introduced the new resource models.1.6 Why does EOSForce mainnet change 1-token-30-votes to 1-token-1-vote?1-token-30-votes will cause the block producers to form alliances and vote each other, which will seriously affect the decentralization of the blockchain. Such monopoly will bring great harm to the EOS community, while 1-token-1-vote of the EOSForce mainnet can effectively avoid this situation and prevent the mainnet from falling into the centralized governance of the Qatar alliance.Block One CEO Brendan Blumer also suggested that EOSIO changes to one-token-one-vote in a telegram group on January 2019.1.7 Is this EOSC EOSClassic?The full name of EOSC is EOS COIN, which is short for the mainnet token of EOSForce, not EOSClassic.2 EOSForce accounts creating and transaction making2.1 How to create an EOSForce account?2.1.1 EOS Genesis users: using the following wallets by importing the EOS private key of mapping can get the EOSForce account.EOSForce official wallet (PC version) — EOSForce.ioInternational well-known wallet — ScatterInternational well-known wallet — Math WalletFamous wallet in EOS ecosystem — Awake Wallet2.1.2 EOS non-genesis users: can create an EOSForce account in the following walletEOSForce official wallet (PC version) — EOSForce.ioInternational well-known wallet — Math WalletFamous wallet in EOS ecosystem — Awake Wallet2.2 Which wallets support EOSC?Tutorial for activating EOSC using Scatter wallet:https://bbs.eosforce.io/?thread-329.htmScatter wallet download address:https://get-scatter.com/EOSForce Wallet tutorial:https://mp.weixin.qq.com/s/jbRRAmhoCKgHlga2V7xsDwEOSForce Wallet download address:https://www.eosforce.io/Math Wallet tutorial:https://mp.weixin.qq.com/s/QV0gQYfWV6xVIXpmtxpDOgMath Wallet download address:http://www.mathwallet.orgAwake Wallet tutorial:https://mp.weixin.qq.com/s/VC4uwNO99Cttj3k_5lEOggAwake Wallet download address:https://www.eosawake.io/EOSOU Wallet download address:https://bbs.eosforce.io/?thread-333.htm2.3 Which exchanges support EOSC?Centralized Exchange: Bitforex https://bitforex.comDecentralized Exchange: Akdex https://akdex.io (Math wallet and Awake wallet have built-in Akdex Exchange)OTC Exchange: EOSOU Wallet https://bbs.eosforce.io/?thread-333.htm3 About voting rewards sharing3.1 How to get voting rewards?https://mp.weixin.qq.com/s/6fdXZNGc2_CgdPpWj5GHwA3.2 How do the coins of the voting rewards sharing come out?The EOSForce mainnet generates one block every 3s, each block produces 3 EOSC, and it produces about 31.53 million EOSC every year. 70% of the total output goes into the nodes rewards pool based on the voting weights. The nodes distribute the rewards to users according to the rewards ratio they set and the users’ voting weight.For example, the rewards ratio set by node mathwalletbp is 99.99%, which means that mathwalletbp pays 99.99% of its rewards pool to the users as voting rewards sharing, and the remaining 0.01% enters its node account.Voting annualized returns = (profitable node annual rewards *70% * Percentage of votes * dividend ratio) / number of total votes of the node * 100%3.3 How to participate in voting to obtain rewards and get votes redeemed?Click “vote” on the right side of the tab of nodes to participate in voting and get rewards. Click “redemption” to modify and withdraw the votes.Each time you vote and redeem, you need to pay 0.05EOSC as a handling fee. There is a 3-days lock-up period for redemption, and shall be unlocked and claimed manually 3 days later.Click “Dividends to be claimed” on the tab of “My Votes” to receive rewards. Each time you claim the rewards, you need to pay a fee of 0.03 EOSC. A sufficient balance must be set aside as a handling charge before voting.4 About nodes4.1 How to become an EOSForce Block Producer?EOSForce mainnet block producer deployment tutorialCN : https://eosforce.github.io/Documentation/#/en/eosforce_bpEN: https://eosforce.github.io/Documentation/#/en-us/eosforce_bp4.2 How many block producers in EOSForce community?There are more than 100 nodes in EOSForce community, among which the top 23 nodes with votes generate blocks and are called block producers. A node that receives more than 0.5% of the total votes of the current network is a profitable node.4.3 The income source of the block producers?The initial circulation of EOSC is 1 billionOne block generated per 3s and 3 EOSC in one block.Daily rewards of profitable node = 3 * 20 * 60 * 24 = 86,400 EOSCAnnual rewards of profitable node = BP daily rewards * 365 = 31,536,000 EOSCThe reward distribution is as follows:The nodes whose votes obtained are more than 0.5% of the total votes of current network are profitable nodes. Among these profitable nodes, there are BPs and BP candidates. The first 23 are BPs and the rest are BP candidates.For the BPs, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to its account as block-generating reward. And the remaining 70% of the income will go into its account and rewards pool according to the allocation proportion set by the node.For the BP candidates, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to EOSForce Foundation account Devfund (This account belongs to the community and is used to support the developers. The transaction requires a multi-sign of more than two-thirds nodes) .The remaining 70% of the income will go into its account and rewards pool according to the allocation proportion set by the node.4.4 Is voting rewards the same for different nodes?Vote for nodes with different annualized interest rates, the voting rewards will be different.Users can vote for different nodes according to the annual interest rate and the contribution made by the node.5. Lockup plan5.1 Why is there less EOSC in the account than at the time of mapping?According to the proposal of EOSForce mainnet unactivated genesis account locking plan, on December 20, the unactivated EOSIO genesis accounts are locked with 80% of EOSC tokens, and replaced for the same amount of lock tokens. The remaining 20% can be freely used.5.2 Why lock up 80% EOSC of the account?Early builders of EOSForce community believe that a large number of unactivated EOSC are not conducive to the future development and construction of the EOSForce mainnet. If these unactivated EOSC are activated after the EOSForce mainnet matures, it is unfair to community builders who have invested time and effort early. In response to this topic, there was a long and repeated discussion in the community, and on November 29, 2018, voted by the block producers and finally approved by 20 votes, 2 votes against, 1 abstention, passed the lock-up proposal jointly proposed by Awake, jiqix, eosou.io and walianwang. On December 20, 2018, EOSForce officially executed the unactivated account EOSC token lock-up contract.5.3 Is it possible to unfreeze the locked EOSC in the future?There is no suitable solution in the community for how to deal with locked EOSC currently. Members of the community can present their opinions and suggestions to the community and nodes.6 The EOSForce DAPP ecosystem6.1 Are there any DAPP on EOSForce mainnet currently?At present, there are Millionaire, Finger Guess, EOSForce Pixel, Super Card, Big Color Quiz, Smoke and Ashes and Waiting for you. It involves DAPP of public benefit, art, social and finance. In the future, we will develop more DAPPs and build a complete EOS ecological community.6.2 How can I participate in DAPP?At present, you can participate in voting rewards sharing and various DAPP projects of the EOSForce mainnet via Math Wallet or Awake Wallet.7 EOSForce resource model7.1 The Difference of resource model between EOSFORCE and EOS EMLGCPU and NET resources are allocated based on fees, and RAM resources are allocated based on leases7.2 Why does the transfer charge a fee? What resources are you paying for?In EOSForce mainnet, each operation needs to consume certain network resources. Because the total network resources are limited, in order to allocate resources fairly and reasonably, and avoid excessive abuse, the EOSForce mainnet has innovatively established a set of model for allocating CPU and NET resources based on handling fee. Under this model, users need to pay a certain fee for each operation to obtain CPU and NET resources. For example, the following operations:Transferring: 0.01EOSCUser Creation: 0.1EOSCVoting: 0.05EOSCRedemption: 0.05EOSCMemory renting: 0.05EOSCRewards Claiming: 0.03EOSC7.3 What is the RAM resources of EOSForce mainnet used for? How to obtain RAM resources of EOSForce mainnet? Can RAM resources be bought and sold?RAM resources provide users and developers with a memory space for nodes to store data for contract’s reading and writing. The RAM resources in EOSForce mainnet can only be obtained by means of leasing. The upper limit of the RAM can be used by the account is set according to the rent paid by the account. It can only be rented and cannot be bought or sold. In order to facilitate the user’s operation, the EOSForce mainnet set an 8kb rent-free quota for each account at this stage, so most ordinary users do not need to care about RAM. Usually, developers need to pay rent for the RAM used by their DApp, including the RAM occupied by the contract and the RAM data generated in the execution.7.4 What to do with the handling fee and RAM resources rent?Handling fee: The handling fee currently incurred for each transaction will be destroyed.Rent: EOSForce mainnet has implemented the function of paying rent for RAM resources by voting rewards. The user votes with a certain amount of EOSC to get the corresponding amount of RAM resources, and pays the rent of the RAM resources with the voting rewards. Currently 1KB RAM resources can be obtained by voting with 10EOSC. The rent will be returned to the rewards pool of the block producers in proportion to the dividend, and will finally return to the voting users.

EOSFORCE

19. 03. 25

1 EOSForce Mainnet Introduc...

Latest FAQ | EOSForce Community Q&A1 EOSForce Mainnet Introduction1 EOSForce IntroductionEOSForce is committed to exploring a more open crypto economy infrastructure in practice. Through the continuous development of multi-chain architecture blockchain protocol, it meets the diversified consensus requirements of the crypto economy and promotes the application of blockchain technology in various fields.EOSForce.io, the most active parallel mainnet in EOSIO ecosystem, has been completed and launched, providing more user-friendly resource model, richer underlying support for developers and fairer governance mechanism for the community. The EOSForce.io mainnet asset can be activated by offline signing with the mapped EOSIO private key.1.2 What is EOSC? Is EOSC an airdrop token?EOSC is the token of an EOS mainnet launched by EOSForce community. It represents the assets on the EOSForce main chain and can be used for voting rewards, block generating, transferring and trading on exchanges.EOSC is not an airdrop token. Users can activate the EOSC account assets by offline signing with the EOSIO private key mapped before June 3, 2018 Beijing time.1.3 The difference between EOSC and EOSEOSC is the token of the EOS mainnet launched by EOSForce. EOS is the token of the EOS mainnet launched by EMLG. These two assets are different. Currently, AKdex.io Exchange has listed the EOS and EOSC trading pairs.1.4 Total amount of EOSC (Including the lock-up plan, and allocation of the rest part)The initial circulation of EOSC is 1 billion, and 94.6 million EOSC are issued annually to reward 23 BPs. The BlockOne team will be awarded a prize of 100 million EOSC unlocked every 10 years. And it will continue to do so without interruption.According to the proposal of EOSForce mainnet unactivated genesis account lockup plan, on December 20, the unactivated EOSIO genesis account will be locked with 80% of EOSC tokens, and replaced for the same amount of lock tokens. The remaining 20% can be freely used. Token increased annually will be adjusted appropriately according to the existing total amount of EOSC tokens in the mainnet.At present, the number of EOSC locked is 672,390,243, and the remaining is 327,609,757.1.5 Difference between EOSForce mainnet and EMLG mainnetThere is more than one EOS mainnet. Currently, the EOS community has launched several mainnets. The mainnet launched by EOSForce community is called EOSForce mainnet and is parallel to the mainnet launched by EMLG.When debugging EOS software, we found many unstable factors and there are certain asset security risks. Since EOS itself is a set of open source software, the official does not guarantee security and reliability of the blockchain launched by EOS software. This requires dedicated team for targeted development and testing to maintain the entire blockchain. Therefore, our team carried out strict tests on each function of EOSIO, upgraded and optimized the official codes, prioritized the security and reliability of the whole blockchain, and officially launched the EOSForce mainnet on June 22, 2018.EOSForce mainnet added the innovation of voting rewards incentive mechanism, improved the decentralization of one-token-one-vote, charged transaction fees to prevent DDOS attack, optimized the community governance of 23 BPs and introduced the new resource models.1.6 Why does EOSForce mainnet change 1-token-30-votes to 1-token-1-vote?1-token-30-votes will cause the block producers to form alliances and vote each other, which will seriously affect the decentralization of the blockchain. Such monopoly will bring great harm to the EOS community, while 1-token-1-vote of the EOSForce mainnet can effectively avoid this situation and prevent the mainnet from falling into the centralized governance of the Qatar alliance.Block One CEO Brendan Blumer also suggested that EOSIO changes to one-token-one-vote in a telegram group on January 2019.1.7 Is this EOSC EOSClassic?The full name of EOSC is EOS COIN, which is short for the mainnet token of EOSForce, not EOSClassic.2 EOSForce accounts creating and transaction making2.1 How to create an EOSForce account?2.1.1 EOS Genesis users: using the following wallets by importing the EOS private key of mapping can get the EOSForce account.EOSForce official wallet (PC version) — EOSForce.ioInternational well-known wallet — ScatterInternational well-known wallet — Math WalletFamous wallet in EOS ecosystem — Awake Wallet2.1.2 EOS non-genesis users: can create an EOSForce account in the following walletEOSForce official wallet (PC version) — EOSForce.ioInternational well-known wallet — Math WalletFamous wallet in EOS ecosystem — Awake Wallet2.2 Which wallets support EOSC?Tutorial for activating EOSC using Scatter wallet:https://bbs.eosforce.io/?thread-329.htmScatter wallet download address:https://get-scatter.com/EOSForce Wallet tutorial:https://mp.weixin.qq.com/s/jbRRAmhoCKgHlga2V7xsDwEOSForce Wallet download address:https://www.eosforce.io/Math Wallet tutorial:https://mp.weixin.qq.com/s/QV0gQYfWV6xVIXpmtxpDOgMath Wallet download address:http://www.mathwallet.orgAwake Wallet tutorial:https://mp.weixin.qq.com/s/VC4uwNO99Cttj3k_5lEOggAwake Wallet download address:https://www.eosawake.io/EOSOU Wallet download address:https://bbs.eosforce.io/?thread-333.htm2.3 Which exchanges support EOSC?Centralized Exchange: Bitforex https://bitforex.comDecentralized Exchange: Akdex https://akdex.io (Math wallet and Awake wallet have built-in Akdex Exchange)OTC Exchange: EOSOU Wallet https://bbs.eosforce.io/?thread-333.htm3 About voting rewards sharing3.1 How to get voting rewards?https://mp.weixin.qq.com/s/6fdXZNGc2_CgdPpWj5GHwA3.2 How do the coins of the voting rewards sharing come out?The EOSForce mainnet generates one block every 3s, each block produces 3 EOSC, and it produces about 31.53 million EOSC every year. 70% of the total output goes into the nodes rewards pool based on the voting weights. The nodes distribute the rewards to users according to the rewards ratio they set and the users’ voting weight.For example, the rewards ratio set by node mathwalletbp is 99.99%, which means that mathwalletbp pays 99.99% of its rewards pool to the users as voting rewards sharing, and the remaining 0.01% enters its node account.Voting annualized returns = (profitable node annual rewards *70% * Percentage of votes * dividend ratio) / number of total votes of the node * 100%3.3 How to participate in voting to obtain rewards and get votes redeemed?Click “vote” on the right side of the tab of nodes to participate in voting and get rewards. Click “redemption” to modify and withdraw the votes.Each time you vote and redeem, you need to pay 0.05EOSC as a handling fee. There is a 3-days lock-up period for redemption, and shall be unlocked and claimed manually 3 days later.Click “Dividends to be claimed” on the tab of “My Votes” to receive rewards. Each time you claim the rewards, you need to pay a fee of 0.03 EOSC. A sufficient balance must be set aside as a handling charge before voting.4 About nodes4.1 How to become an EOSForce Block Producer?EOSForce mainnet block producer deployment tutorialCN : https://eosforce.github.io/Documentation/#/en/eosforce_bpEN: https://eosforce.github.io/Documentation/#/en-us/eosforce_bp4.2 How many block producers in EOSForce community?There are more than 100 nodes in EOSForce community, among which the top 23 nodes with votes generate blocks and are called block producers. A node that receives more than 0.5% of the total votes of the current network is a profitable node.4.3 The income source of the block producers?The initial circulation of EOSC is 1 billionOne block generated per 3s and 3 EOSC in one block.Daily rewards of profitable node = 3 * 20 * 60 * 24 = 86,400 EOSCAnnual rewards of profitable node = BP daily rewards * 365 = 31,536,000 EOSCThe reward distribution is as follows:The nodes whose votes obtained are more than 0.5% of the total votes of current network are profitable nodes. Among these profitable nodes, there are BPs and BP candidates. The first 23 are BPs and the rest are BP candidates.For the BPs, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to its account as block-generating reward. And the remaining 70% of the income will go into its account and rewards pool according to the allocation proportion set by the node.For the BP candidates, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to EOSForce Foundation account Devfund (This account belongs to the community and is used to support the developers. The transaction requires a multi-sign of more than two-thirds nodes) .The remaining 70% of the income will go into its account and rewards pool according to the allocation proportion set by the node.4.4 Is voting rewards the same for different nodes?Vote for nodes with different annualized interest rates, the voting rewards will be different.Users can vote for different nodes according to the annual interest rate and the contribution made by the node.5. Lockup plan5.1 Why is there less EOSC in the account than at the time of mapping?According to the proposal of EOSForce mainnet unactivated genesis account locking plan, on December 20, the unactivated EOSIO genesis accounts are locked with 80% of EOSC tokens, and replaced for the same amount of lock tokens. The remaining 20% can be freely used.5.2 Why lock up 80% EOSC of the account?Early builders of EOSForce community believe that a large number of unactivated EOSC are not conducive to the future development and construction of the EOSForce mainnet. If these unactivated EOSC are activated after the EOSForce mainnet matures, it is unfair to community builders who have invested time and effort early. In response to this topic, there was a long and repeated discussion in the community, and on November 29, 2018, voted by the block producers and finally approved by 20 votes, 2 votes against, 1 abstention, passed the lock-up proposal jointly proposed by Awake, jiqix, eosou.io and walianwang. On December 20, 2018, EOSForce officially executed the unactivated account EOSC token lock-up contract.5.3 Is it possible to unfreeze the locked EOSC in the future?There is no suitable solution in the community for how to deal with locked EOSC currently. Members of the community can present their opinions and suggestions to the community and nodes.6 The EOSForce DAPP ecosystem6.1 Are there any DAPP on EOSForce mainnet currently?At present, there are Millionaire, Finger Guess, EOSForce Pixel, Super Card, Big Color Quiz, Smoke and Ashes and Waiting for you. It involves DAPP of public benefit, art, social and finance. In the future, we will develop more DAPPs and build a complete EOS ecological community.6.2 How can I participate in DAPP?At present, you can participate in voting rewards sharing and various DAPP projects of the EOSForce mainnet via Math Wallet or Awake Wallet.7 EOSForce resource model7.1 The Difference of resource model between EOSFORCE and EOS EMLGCPU and NET resources are allocated based on fees, and RAM resources are allocated based on leases7.2 Why does the transfer charge a fee? What resources are you paying for?In EOSForce mainnet, each operation needs to consume certain network resources. Because the total network resources are limited, in order to allocate resources fairly and reasonably, and avoid excessive abuse, the EOSForce mainnet has innovatively established a set of model for allocating CPU and NET resources based on handling fee. Under this model, users need to pay a certain fee for each operation to obtain CPU and NET resources. For example, the following operations:Transferring: 0.01EOSCUser Creation: 0.1EOSCVoting: 0.05EOSCRedemption: 0.05EOSCMemory renting: 0.05EOSCRewards Claiming: 0.03EOSC7.3 What is the RAM resources of EOSForce mainnet used for? How to obtain RAM resources of EOSForce mainnet? Can RAM resources be bought and sold?RAM resources provide users and developers with a memory space for nodes to store data for contract’s reading and writing. The RAM resources in EOSForce mainnet can only be obtained by means of leasing. The upper limit of the RAM can be used by the account is set according to the rent paid by the account. It can only be rented and cannot be bought or sold. In order to facilitate the user’s operation, the EOSForce mainnet set an 8kb rent-free quota for each account at this stage, so most ordinary users do not need to care about RAM. Usually, developers need to pay rent for the RAM used by their DApp, including the RAM occupied by the contract and the RAM data generated in the execution.7.4 What to do with the handling fee and RAM resources rent?Handling fee: The handling fee currently incurred for each transaction will be destroyed.Rent: EOSForce mainnet has implemented the function of paying rent for RAM resources by voting rewards. The user votes with a certain amount of EOSC to get the corresponding amount of RAM resources, and pays the rent of the RAM resources with the voting rewards. Currently 1KB RAM resources can be obtained by voting with 10EOSC. The rent will be returned to the rewards pool of the block producers in proportion to the dividend, and will finally return to the voting users.

EOSFORCE

19. 03. 25

EOSForce Mar 2019 Week 2 De...

Work completed1. EOSForce mainnet update completed with the community2. FORCEIO Checker node relay function completed3. FORCEIO IBC solution improved transaciton contracts based on requirements4. EOSForce merged the latest ELMG EOS updates5. FORCEIO IBC solution economic model improved6. FORCEIO ported CDT development toolset7. FORCEIO golang library improved8. FORCEIO client command line tools supported transaciton contracts9. EOSForce client adds the function of switching voting with no freezing periodNext week’s plan1. FORCEIO relay chain economic model implementation design2. Improve FORCEIO Checker node implementation3. Implement FORCEIO IBC solution sidechain relay contract4. FORCEIO Checker node improves support for Docker5. Develope FORCEIO relay chain client wallet한국어이번 주1. 커뮤니티와 협력하여 EOSForce 메인넷 업그레이드 완료2. FORCEIO 검사 노드 릴레이 기능 완성3. FORCEIO IBC 솔루션 수요에 따라 거래 컨트랙트 개선4. EOSForce의 ELMG EOS 최근 업데이트 버전 합병5. FORCEIO IBC 솔루션 이코노믹 모댈 개선6. FORCEIO cdt 개발 도구 모음 이식7. FORCEIO golang 라이브러리 보완8. FORCEIO 클라이언트 명령행 도구 거래 컨트랙트 지원9. EOSForce 클라이언트 언스테이킹 없이 투표 변경 기능 추가다음 주 계획1. FORCEIO 릴레이 체인 이코노믹 모델 실현 방안 설계2. FORCEIO 검사 노드 실현 개선3. FORCEIO IBC 솔루션 사이드 체인 릴레이 컨트랙트 실현4. FORCEIO 검사 노드 개선 및 Docker 지원 개선5. FORCEIO 릴레이 체인 클라이언트 지갑 개발

EOSFORCE

19. 03. 25

EOSForce BP Open-House Meeting

EOSForce BP Open-House Meeting | 02.25.2019Topic: EOSForce Community Governance Meeting (10th)Time: Feb 28, 2018, 20:00–21:30 UTC+8Location: Zoom@ https://zoom.us/j/725946471Host: Wang Wei (BP: Walianwang)Proceedings:1. Super Node Community Secretary rotation2nd Community Secretary work reportElection of the 3rd Community Secretary member2. Community Secretary proposal voting3. Non-delay vote token redemption proposal votingProposalsCommunity Secretary Compensation ProposalTo improve community governance efficiency and to attract more network BPs to community governance, it is proposed:Each member of the Community Secretary receives 10,000 EOSC as salary compensation each monthImplementation starts at the election of the 3rd Community SecretaryThe token compensation comes from the Developer Fund accountNotes:According to “EOSForce Mainnet Super Node Meeting Rules”, Community Secretary consists of 1 Chief Secretary, 2 Deputy Secretaries, and 1 Host in rotation.Compensations are calculated based off the token. Low price encourages the staff effectiveness and high price attracts more people to apply for the positionNon-Delay Vote Token Redemption Proposal VotingTo improve community governance efficiency and to attract more network BPs to community governance, it is proposed:The votes in the vote pool in mainnet voting will have no time delay when switched to vote for other BP nodesRedemption from the vote pool will still have the 3-day delay when redeemed for balance.Notes:Voting age will start from 0 when vote is cast for another candidate.The proposal aims to increase inter-BP competition and voter participation, as well as encouraging new BPs entering the competition.Notes:1. The meeting is open to all members and nodes of the EOSForce ecosystem.2. The Super Node secretary welcomes all community members to build the ecosystem together.Secretary Office of EOSForce Super Nodes2019.2.25 (CN) 2019.2.25 (EN)

EOSFORCE

19. 02. 25

EOSForce Community Governan...

ForewordThe Mandate to Govern in CommunityIn public blockchains, community governance makes up a large part of the integrity and the growth of the network. Traditional open-source projects only involve the developer community, but in public blockchains, network changes involve nodes, stake holders and users. Through economic incentive, public blockchains improve by involving more than one group of participants.Daniel Larimer took decentralized governance a step further with the design of Delegated-Proof-of-Stake (DPOS). Features including the on-going Block Producer election and the Referendum system add to the innovation and effectiveness of blockchain governance.The EOSForce governance community adds to the field of blockchain governance with their 1-Token-1-Vote and the Voter-Dividend model. Through economic incentives, EOSForce has been able to achieve voter turnouts as high as 90%. The high community participation continues to add new features to the network to adapt to new needs.Nodes, stake-holders and users can participate in community governance by directly drafting proposals or voting for Block Producers. The EOSForce Mainnet has 23 active Block Producer Super Nodes. Proposals which receive votes from more than 2/3 of the Super Nodes pass and get to be executed by the governance body and the EOSForce Core Team.It is also to be noted that this is a guide manual proposed by EOSForce Core Team and any EOSForce community member or Block Producer has the right to suggest changes.How to Participate in Community GovernanceVoting and Block Producer ElectionVoting is the most direct way for EOSC holders to participate in the EOSForce Mainnet governance. EOSForce (EOSC), born out of EOSIO, is the world’s first DPOS network with 1-Token-1-Vote. This model effectively eliminates governance manipulation of institutional investors and block producer alliance. It also encourages voters to vote for those Block Producers that serve in the interest of the community.Super Node Responsibilities to the CommunityAfter a node is successfully elected, it is required to fulfill the duties of packaging network transactions, blockchain generation, mainnet upgrades and so on. It is also required to vote on the proposals from the EOSForce communities on behalf of its electorates. Super Nodes must express its stance on each proposal clearly and interact with the community and each proposal voting will be clearly documented and presented to the EOSForce voter community.How to VoteThrough community wallets such as the MathWallet and EOSForce Desktop Wallet, any EOSC holder can vote and elect. EOSForce Core Team is developing a democratic voting infrastructure with better liquidity based on community proposals.Start Your Block Producer CampaignAny organization or individual can become a Block Producer through on-going EOSForce Mainnet elections.Initiating a governance proposal is the primary way in which EOSC holders can become deeply involved in community governance. As a unique feature of blockchain governance, EOSC token holders can present their opinions and solutions to problems and development of the EOSForce Mainnet through several ways. Several major decisions in the history of EOSForce have been made through rigorous community discussions, including:Voting dividend midificationInactive Token LockupInflation ReductionSpecific steps to initiate a proposal are as followed:Submit proposalEOSForce GithubBP proposal submission email: BPproposal@eosforce.ioEOSForce Global Community ForumInitiate proposal through BP support (list of BPs available at: explore.eosforce.io)2. Community Secretary organizes the community to initiate discussions and improve the proposal.Community Secretary is an open DAC composed of community and developement team, whose main responsibilities are to collect community proposals, initiate and host discussion meetings, record meeting contents, publish meeting contetns and so on. The Community Secretary rotates on a 3-month basis and is additionally compensated.Community Secretary regularly collects proposals and suggestions from the community on a weekly basis, organizes discussion of proposals by nodes and communities, and records views and opinions expressed by the community during the discussion.After the proposal has been fully discussed by the EOSForce community, the initiator needs to integrate the community opinions and further improve the proposal, then communicate with the EOSForce Core Team on the feasibility and priority of the update.3. Community Secretary organizes Block Producer meeting to voteAfter the proposal is completed, the Super Nodes and Block Producers will hold a meeting to vote on the proposal. If more than two-thirds of the block producers vote yes, the proposal is passed. If the proposal does not receive two-thirds of the votes, the proposal does not pass the vote. The proposal can be revised and submitted again. After the vote is completed, the Community Secretary will release detailed information about the meeting process and voting to the community.4. EOSForce Core Team execution & BPs test the code updateIf the proposal passes the Super Node vote, EOSForce Core Team will provide the corresponding technical support and technical solutions as well as the development cycle according to the requirements of the proposal, and then the nodes will jointly perform the test.5. Community Initiates Multi-Signed Contract & BP Implements Multi-SignatureIf the proposal passes the acceptance test, the community will initiate a multi-sign contract, and the block producer will execute the multi-sign proposal.After more than 2/3 of the block producers have signed, the new rules come into effect on the EOSC network. Any user can query through the public interface of EOSC (Chain ID :bd61ae3a031e8ef2f97ee3b0e62776d6d30d4833c8f7c1645c657b149151004b). The secretariat will also count the results of the execution and publish them in the public channels of EOSC.By now, the process of initiating, discussion, voting and executing has completed.Like government in the real world, no governance model is perfect. The EOSForce governance model is one of the more efficient models that have gone through an evolutionary process that leads to the current form. There are imperfections and the community is still exploring in practie. The community often conducts governance discussions on various public channels. Join these public channels and discuss a better solution with other community members.EOSForce is a multichain network built on EOSIO, enabling IBC and one-click blockchain launch for mass adoption, with an innovative governance modelWebsiteTwitterEnglish TelegramRedditGithubKorean TelegramMathWalletDesktop Wallet

EOSFORCE

19. 02. 25

EOSForce Community Q&A | Cy...

ForewordWhat are some of the hottest topics emerging in the crazy world of EOSIO in Jan 2019? BOS, market fluctuation, EOSForce 1-click blockchain, developer issues, resource/governance models? Surely there’s simply too much going on with EOSIO to keep up! No worries. EOSForce founder Cyborg has recently answered all of the above questions with a Q&A in the EOSForce community! If you are one of those who missed the community Q&A, you’re in the right place! In this article, we have organized his thoughts on all of the above topics! Let’s take a look.Note: credit of the original compilationgoes to eosou.io volunteer Boming Su.Translation provided by EOSForce Core Team JC ZhangStraight Words on BOSBOScore is supposedly led by a top Chinese-based top exchange. It has an interest group on the EOS Mainnet blockchain. So they launched this sidechain together. Some of the ideas of BOS are actually not bad, the Guaranteed Minimum Provision feature is actually a very good idea.However, the biggest risk of BOS is that it does away with the EOSIO’s concensus mechanism, in order to reduce the confirmation time to the Last Irreversible Block. EOS EMLG and EOSForce could both do this. The reason why we have not done so [at EOSForce] is that the visit traffic between nodes will climb up immediately and cause the cost of nodes to rise. So BOS’ concensus mechanism would actually cause the cost of nodes on their network to increase, even higher than EOS EMLG.At the same time, the issues of 1-token-30-vote model that plague the EOS community and the zero-voter incentive model carry huge risks for BOS as well. The codes of BOS give off an impression that they were in a rush, and many EOSIO codes were just copied and pasted line by line.As for their token distribution/ICO model, I personally agree with the arguments presented by the founder of EOS Laomao, Laomao himself, in his personal Wechat official account (for platform restrictions we are not posting its link directly in this article).Right now Brendan Bloomer is pushing 1-token-1-vote and voter incentive models, but the gaining support among communities is difficult. The current Block Producers have 3 categories: 1. exchanges that use idle tokens to vote for themselves; 2. BPs that are voted by the exchanges; 3. the last category is those that are elected purely through community voters. However, the 3rd category forms a very weak voice in the ecosystem. Without consent from one of these groups, Brendan Blumer would have a hard time pushing a change in the constitution. Moreover, I have talked with BPs from EOS, and they’ve told me that the current issue is not necessarily on the 1-token-30-vote or the voter dividend, but on the resource model.Where’s EOSIO Tech in the Overall Market?Many designs of EOSIO are laid out for the future development for multichain and crosschain. EOS development teams without long-term experience would have a hard time telling it, and every time we make changes we take a lot of caution.When it comes to 3rd generation blockchains, EOSIO is still better than other blockchains. But the 1-token-30-vote has spoiled the good vibe of the ecosystem and turned it into exchange BPs and whale BPs playground, and the resource models on EOSIO have been problematic too.Take REX and the Byzantine fault tolerance update for example. These updates go beyond the ability of regular teams. For EOSForce, they’d still take us a big chunk of a year to make such updates. So except for the Block.One team and our team, many developers now might resort to TRX. But actually experienced developers know that TRX’s resource model is even more unfriendly to develoepers, certainly worse than EOS. Seeing this challenge on the developer side, if the EOS DAPP development stories told on social media are true, EOS token price would have gone to the moon long ago. So that’s why we say that the current gambling and small game dapps on EOS are not solutions to the problem. Solutions exist outside the box.Once Again about Resource ModelsTheir (EOS) resource model needs to be changed, or many BPs will not be able to make it, mainly also if a lot of DAPP developers go away. EOSForce uses transaction fee and dividend rental to solve the issues of RAM and transactions. Still, from what public blockchain’s current performance, the future will definitely be multichain + crosschain. One single chain cannot possibly run that many dapps.The deterioarating state of gambling dappsThose gambling dapps actually need not be on EOSForce. As you can see, most of them merely have a life cycle of 2 weeks and have brought negative influence to the ecosystem. Many users have lost a lot of their assets they have earned just on gambling dapps. Probabilistically speaking, in the long run, you would always lose. When the winners liquidate their assets, the EOS token price is negatively affected as well.But actually, TRON’s resource model is the same as EOS. It’s in fact similar to EOS overall except for the virtual machine. But its resource model is inferior to EOS, and developer cost is high than on EOS. Its sole advantage is its intermittent price increases with whale pumping the price. This has led to rise of gambling dapp on TRON. The delusion this creates is that people think the ecosystem of TRON has gone up, and so TRX price has gone up. These two are actually not correlated.One more point on this, the platform loyalty of developers on TRON is actually very low. Developers on EOS for example, when the liquidity of their EOS DAPPs drops, they move to TRON. This kind of incentive is unsustainable. Developer teams themselves are not that wealthy, so after a pump and dump, they can only resort to high-liquidity areas. Ontology for example does exactly that — moving from chain to chain for short-term liquidity. For real application developers, if your blockchain does not have good experience, everything would not go long-term. Just like earlier RAM speculations. Do people still do speculation on RAM prices?Our view on building developer communityStatus quo of blockchain developersFull-time blockchain application developers are very small in numbers. The existing developers usually have a lacking understanding on blockchains.However, International developers from non-Chinese regions do not care about political correctness. They come for solving problems. The reason why our international communities have grown is that many users, developers, and BPs have noticed and join the EOSForce ecosystem.Our focus on the international communityFrom the perspective of EOSForce, our main focus now is to grow our international developer community. The Chinese gambling dapps developer teams only harm the ecosystem. If you have received mining dividend from dapps on EMLG Mainnet before, you know that the survivability of these dapps is usually 2 weeks. The process is usually early investors exploiting late-comers. They don’t have a mechanism to attract new users.A good quality of international developers is that they want to solve problems. They put long-term problem solving before short-term profitability. That’s why our main focus in on the international community. Just now I said that the Minimum Guarantee Provision of BOS is actually a good feature. I’m not sure if they have finished the coding, but we also have an equivalent provision on EOSForce. We give 8kb of RAM to each account. We see many of the advanced features that more and more mainnets on EOS have the same fundamental logic. Our advantage is we have finished coding this.In addition, Chinese EOS DAPP developer communities are no long that aggressive in many aspects. This is typical of Chinese-based groups even though the Chinese-based blockchain projects themselves are still leading in the industry. That’s why our international focus has brought activity to our global presence.About 1-Click Blockchain LaunchForceIO is launching very soon!In the weekly reports we published earlier, we have announced the development of ForceIO, and we have announced our multi crosschain network. Soon we will put forward that any DAPP developer team will be able to use the ForceIO program to launch a blockchain. It can be a public blockchain similar to EOSForce or EMLG, or an enterprise blockchain. The program is catered for all resource models and governance models.So from now on it will be easy to launch a blockchain for average users. Launching a public blockchains like BOS will no longer be an inhibiting threshold. People can launch a blockchian just like they launch an ERC-20 contract on Ethereum. Only when launching blockchains becomes accessible for developers will we see the significant applications being developed on blockchain.The logic behind this is: when launching public blockchains is 1 click away for everybody, speculations on public blockchains should go away, so what people do next is settle down and build useful applications. The future of the blockchain industry will be packed with new public blockchains.Early this year we said that we will support BCH. The reason we planned it was that some services work better with Proof-of-Work. So with our resources, we will aim for 1-click POW network launch service in Q2 or Q3 2019 too.Which blockchains does 1-Click Launch support?The 1-Click Blockchain Launch program supports EOSForce, with very fast transaction speed for homogeneous crosschains and sidechains. We will also support EOS EMLG, as well as public blockchains like Ethereum and Bitcoin.Interblockchain communications have several popular solutions. We have two stages of development. The first one is EOSForce-homogeneous blockchains. That is, the nodes in these blockchains install the same plugin and establish trust and security between them. This is suitable for homogeneous blockchains, but the disadvantage is installing the same plugin could encounter resistance.A Million Dollar SolutionThe other solution is to completely decentralize sidechains and crosschains. This is a cutting edge technical challenge in the industry at the moment. A lot of international teams have not made the breakthroughs on this. We are looking at 1 to 2 breakthoughts in Q1 and Q2 in 2019. That’s why we are looking at supporting heterogeneous blockchains as well.The simplest example application is when you play a dapp game, if you are playing an EOSForce mainnet game on EOS EMLG, you need to sell your EOS and buy EOSC and then play the game. You might make a lot of EOSC on the game, but if the EOSC price plummets, the EOS you exchange back might not cover what you made in the game. If we play the game through an interblockchain network with powered with crosschains, you stake your EOS on the relaychain to EOSC — this is equivalent to effect of staking it on EOS mainnet — you get the equivalent of 10 EOSC to play on the dapp. It uses the EOS you staked. When you exit the game, you can unstake your EOS and retrieve the EOS you earned in the game.Great User ExperienceThe advantage of this is that you only need to complete settlements on EOS while your contracts are run on the EOSC chain. For the users, the front-end interface has absolutely no signs of that. On the other hand, if you conduct transaction settlement on EOS chain as well computation of contracts, it gets congested.Relaychain 100% Community Mining — No 1:1 AirdropThe relaychains in the interblockchain network will have nodes i.e. BPs as well. The token distribution of these relaychains will be 100% community mining, rewarding only those who contribute to the network. No premine distribution will be reserved for the team either.Tokeneconomics in the IBC NetworkThe mechanism that incentives the EOSForce core team is: 1–5% of the mining reward each day goes to the core team account. One part of this will be paid as the salaries for the core team, and the other part will be for EOSForce mainnet airdrops for the community. This is under development and the distribution model is in design. However, it will be implemented through mining/blockc producing and no premine will be allowed.Why 1:1 airdrop premine is bad1:1 airdrop is flawed in its logic. Anyone without any proof of work can receive tokens in this model. The airdrop we call in the EOSForce community is from the 5% of what the core team makes and we give it to the community. But our bottom line is that you cannot get 1:1 for doing nothing. EOSForce Mainnet users have historically received that premined rewards. That actually has no more significance. Many launching mainnets nowawayds have 1:1 airdrops, but we see more and more so that do not.Where EOSForce Stands in the IBC Field?In the ForceIO multichain network, the latest technologies will be deployed on EOSForce Mainnet. Average developers will choose the EOSForce Mainnet for definite reasons. And they will launch a sidechain on EOSForce as EOSForce grows.Earlier I explained the token mapping process. It is launched on EOSForce Mainnet and settled on the sidechain. The EOSForce Mainnet blockchain is where the settlement takes place although developers can choose to run transaction settlements elsewhere. The rationale is to only run computation and smart contracts on the sidechain due to resource limits. The relaychain is the bridge between sidechains and the EOSForce Mainnet blockchain.The Historic Burden of EOSForceA lot of the prominent figures in the EOS ecosystem are good friends with me, but due to some arguments we had earlier, they have yet publicly supported EOSForce. But this is not the important point. What really makes a token valuable? Demand. The reason why EOSC and otehr cryptocurrency prices increase slowly is because of the low demand. That is, demand from the developers. Unlike older blockchains, EOSForce has been around for less than 1 year. EOS has been in existance for 2 years, Ethereum 3 years, Bitcoin a whole decade. So their community is really large. It is normal for these long-standing ecosystems to have large dynamics.The opposition to the EOSForce Mainnet early on was that people thought we would divert value from the EOS. Similar to ETC, even though they have done close to nothing, their price would rise. It’s diverted value from Ethereum and from Bitcoin. However, EOSForce started at a negative score, so all we are doing right now is to bring up the negative score.BOS vs EOSForceThe brand impression BOS goes for is different. By definition, they are a fork, but they claim to be a sidechain. They do not suffer much community resistance other than its ICO because they have a large group of communities around it. But what we need to remember is what makes a blockchain good is its developer experience. In this respect, EOSForce is better than other blockchains. EOSForce’s TPS is higher than any other blockchain with fast transaction speed. That’s why we are now focusing on developer experience.So we continue to upgrade. That’s why we do not spend as much resources on publicity. Publicity is for the useless gambing dapps. We want to focus on developer experience. We do not aim to attract enterprise dapp developer teams. We start with global medium-to-small developer communities.Next up we are focusing on developer tutorials in English and Chinese. Developers do not care much about meetups and publicity conferences. They develop much more interesting stuff on their own than the gambling dapps given the right resources. We will provide those resources.Comments on other developer teamsWith respect to development strength, some of the best teams in the world include Bitcoin core. They are relatively conservative in terms of development, and the overall community is rather conservative too. They do not want to make Bitcoin into a peer-to-peer digital cash but a digital gold. Another team with similar traits is the Copernicus team of BCH. They have in-depth research in POW and DPOS, but have not released their findings due to political reasons.Another team that’s very strong is BSC, the team behind Craig Wright. Their proposals are good and their development capability is find, and they ave POW miners support. Others include Cardano and Polkadot. They are strong in terms of development, but they are very slow. The rate at which they update their codes is inadequte to the amount of money they raised if this comparison makes sense.Demand for Enterprise BlockchainsAnother growing demand is enterprise blockchain. Transparency in assets in Business-to-Business needs enterprise blockchains to verify. This demand has huge potential with obvious advantages. I think if it uses stable coin to as a solution, the asset can solve the transparency issue completely in the contract.On Token PriceMany teams control the token price in consortium with whales, but everyone knows this is no long term solution. Although the EOSForce team did not do an ICO and is not that wealthy compared to others, but we can still pull that off based on the current EOSC price. But we understand the unsustainability of that deeply.From another perspective, the reason why people believe in Bitcoin is its decentralized nature. Even if the core team shuts down, the blockchain will still run. On the other hand, centralization would result in direct obliviation of the blockchain if the core team goes bankrupt.Decentralization on EOSForceFrom the 80% genesis lockup to the adjustment on the inflation rate, the decision-making is completely driven by the community on EOSForce Mainnet. The EOSForce core team has dedicated very minimal expenses on the governance level and the community takes full control. On the other hand, community of other blockchains have no say in the matter and can never make proposals.I think what our focus should be next is learning from the communties whose developer atmosphere is epecially great and what kind of applications they want to do and how we can attract these develoeprs. Then we make improvement on our blockchain. Even though EOSForce development force is in good shape, but issues on governance cannot be solved on our own. We need community effort.Blockchain growth & market conditionMany blockchains rely on speculative indicators for growth. They will artificially hype up the indicators that rating agencies use. If they look at the account number, they create accounts on their own. If they look at the transaction number, they spam transaction counts. I think the growth on EOSForce is actually the normal one. Our international community grows at a 10% rate weekly.Many speculators came in EOSForce at the times of market hype and bought the token at a very high price. I don’t think this is what a rational investor should do. With the current market condition, as more speculators leave, the community is starting to discuss things from an economic viewpoint and not for pure self interest.The current issues of the blockchain indsutry are not faced by EOSForce alone. BPs on EOS EMLG do not make a profit these days from the reward nor from developing dapps. The same goes for BCH. Good applications should not have to rely on token price to prosper. They rely on the performance and accessibility of the blockchain.For example, a question is if Bitcoin does not have 3Mb in its blockchain, could it grow? Is it still depending on the 3M/block? If it were not for the revolutionary fundamentals in the whitepaper, it would not have grown until today. Blockchains with centralized token price manipulation have died in masses. EOSForce will not repeat the same mistake. The current token price warm up is totally due to the community. If we were controlling the price, I would not be chatting with you guys here.What can EOSForce ecosystem members do?I think what all people should do in EOSForce ecosystem is to participate in the discussion of governance, not just as a token holder. Without discussions on governance and applications, blockchains die.Blockchain has not just been in existence for 1 or 2 years. It will be influential to industries for decades or even centuries to come. Currently if we only care about self-interest, we only hurt the existing users. We have a shortage of new users right now. Even the top three exchanges only have a fraction of the users they did. We must get rid of the short-term token holder speculative mindset.EOSForce, as the first fork or sidechain on EOS, price estimates would definitely be more promising than others. We will continuously iterate responding to new demands. We will also cooperate with the commuity and international BPs. We also thank our partner MathWallet and our Korean communities.I think that’s enough for today. Our plans for 2019 are way more dense and ambitious than the previous year. If you have any question, contact with us or with BPs, in Kaokao Talk or Telegram.Contact EOSForceTwitter | English Telegram | Reddit | Github |Korean TelegramEOSForce blockchain explorer: https://explorer.eosforce.io/#/enWalletshttps://github.com/eosforce/wallet-desktopEOSC token is distributed in accordance with the EOS genesis mapping. You can activate your EOSForce genesis account here.Scatter 10 has minor compatibility issues with EOSForce blockchain. Join the Telegram Channel here: https://t.me/Scatter. Visit the Scatter website at: https://get-scatter.com/ExchangesBitforex | Akdex.io

EOSFORCE

19. 02. 18

Meeting Minutes — 80% Genes...

Meeting Minutes — 80% Genesis Lockup Proposal DiscussionMeeting GeneralsTopic: EOSForce governance discussions — 80% genesis lockupMeeting time: 2019.01.25 13:00–14:30 UTCFormat: open-house ZOOM meetingHost: Wang Wei from WalianwangAttendees: EOSForce community members, super nodes and candidate nodes, EOSForce core team.ProceedingsLockup plan background introBP representative introduce lockup plan backgroundCommunity discussion on 3 unlock plans (discussion does not result in direct proposal passage)Open discussion on governance issuesAgendaAgenda 1 — Lockup Proposal Background IntroIntro by proposed BPsExchange of views on the proposalAgenda 2 — BP representative introduces lockup plan backgroundAwake introduces the passed lockup proposalAwake BP once proposed that portion of assets above 40,000 tokens of the unactivated accounts be deleted for the following reasons:There should not be an unlimited activation time.Whales do not participate in the community and treat EOSForce as airdrop candies, causing dumping pressure to the community.EOSForce did not have an ICO and has no strict obligation to the genesis accounts.Keep the accounts with less than 40,000 tokens can minimize the total number of affected accounts.2. Jiqix introduces lockup planJiqix proposes a lockup plan out of the concern to minimize the error probability of locking up and shares its views:Fairness is divided into procedural fairness and consequence fairness. In consequence, lockup is unfair to late-comers, but is procedurally fair. With no issue, any decision should be materilized by the current community.Lockup aims to protect EOSForce its own. If the EOSForce token price is unstable, no dapp will be willing to develop on EOSForce. If EOSForce then shuts down its services, the 20% of unactivated accounts is no different from 200% or 1000%. Existence is paramount in front ofthe pursuit of absolute fairness.Lockup is not the fairest nor the best solution, but is the best for the time being and is better than outright deletion. Lockup first and then other solutions minize the risk of errors. Whether or not unfreeze later, how to unfreez or total delete, it depends on community opinion. But that is not for now.New proposals about deleting portions above 40,000 tokens is not fair. Disagrees. Any other proposal concerning such should take into account the spirit of contract.Agenda 3 — Community discussion on 3 unlock plans (discussion does not result in direct proposal passage)The community reaches the concensus that a proposal should be listened to regarding changing the in-effect lockup plan. However, due to the absence of the community members who proposed the suggestions and disagreements among BPs, furhter discussions are not held.Agend 4 — Open Discussions on GovernanceCyborg:A lockup is helpful in preventing malicious whale exchange eactivities and EOSForce from being hijacked by them.Goal of EOSForce is to leave to the genesis investor a clean land of seeds for a different future.Anyone can submit proposals to be up for voting. Anyone should be able to know which BP supports their proposal and which does not, and which titles of the proposal needs amendment.Later proposals should shorten the voting time to channel the visions of the voters better.Swedencornet:Telos example could be borrowed to limit the token amount of an account to diversify EOSForce from EOS EMLG.A upper limit of 5000–40000 of token could replace the 80% genesis lockup plan.Upper limit can also ensure price stability and relieve market pressure.Everyone should have the problem-solving attitude of the community.EOSphere:The Chinese BPs are getting too stuck in the lockup issue. We should not forget the global picture in stimulating the EOSForce community.Overseas BPs did not join previous because they were not aware of its existence.During the passage of the 80% lockup plan, overseas users were not adequately informed.We should maintain a global picture and understand the international community users.We should have more ways to encourage participation from the EOSForce community since the existing measures are not enough.Nobody wants the token price to drop. But there are ways to encourage community participation while stabilizing the price. Some measure such as staking the tokens in some ecosystem activity could be a solution.ENDBP Proposals accepted: BPproposal@eosforce.io

EOSFORCE

19. 01. 29

Updated Guide to Activate E...

Special thanks to James from Scatter for his assistance on this update.Step ONE:Visit Scatter official website (https://get-scatter.com/) & download Scatter.Step TWO:Enter the Scatter application interfaceAfter you complete the wallet password and initial setup, you will be on the page below. Click “Add Keys”.Click “Create Keys”.Click on “Back” on the top left corner to get back to the Scatter main page.Step THREE: Set up the EOSForce Mainnet networkClick the settings icon on the top right corner.Click “Networks”. Enter the network setup after password verification.On the “Known Network” menu, drop down menue and chooseEOSForce Mainnet, and click Add to add it to your network.On the notification of “Network Saved”, new network setup is successful.Step FOUR: import EOSForce Mainnet private keyHead back to Scatter main page and click “Add keys”.Click “Import Key”.Click “Text”.Enter EOSForce Mainnet private key (unactivated account can enter the EOS genesis private key).The above page means that you have successfully set up EOSForce Mainnet on Scatter and you can access EOSForce through Scatter on the EOSC/EOSForce supported sites.Contact EOSForceTwitter | English Telegram | Reddit | Github |Korean TelegramEOSForce blockchain explorer: https://explorer.eosforce.io/#/enWalletshttps://github.com/eosforce/wallet-desktopEOSC token is distributed in accordance with the EOS genesis mapping. You can activate your EOSForce genesis account here.Scatter 10 has minor compatibility issues with EOSForce blockchain. Join the Telegram Channel here: https://t.me/Scatter. Visit the Scatter website at: https://get-scatter.com/ExchangesBitforex | Akdex.io

EOSFORCE

19. 01. 24

EOSForce Mainnet Weekly Upd...

Total Mainnet Transaction Count: 1,562,302 txMainnt Account Count: 578,194Mainnet Vote Count: 153,890,215 EOSC (93.8% of the total activated EOSC)Total Activated Genesis EOSC: 162,269,851 EOSCActivated Genesis Account Count: 3564EOSForce Jan 2019 Week 3 Development ReportThis weekFORCEIO supports custom resource model and voting model through compile options.FORCEIO supports one-token-multiple-votes voting models.FORCEIO supports onchain blacklist.FORCEIO supports custom system contract account through compiling parameters.Published FORCEIO highly constimizable blockchain version 0.1.0.Collaborated with community updating EOSForce Mainnet to version 1.4.1.Perfected EOSForce English support documentation.Integrated EOSForce with EOSIO 1.5.4 update.Next weekFORCE IBC solution relaychain BP model relay contract development.FORCEIO supports sync plugin development.FORCE IBC solution relaychain Token contract mapping realization.FORCE IBC solution relaychain design to corresponding resource models.EOSPhere Joins EOSForce MainnetEOSForce will be attending EOS Israel mainnets meetup in FebEOSIO.Sweden Joins EOSForce MainnetEOSForce Genesis Lockup BP Meeting Scheduled Jan 241-Token-1-Vote DiscussionsEOSForce founder Cyborg published an article offering his takes on the rise of 1-token-1-vote discussions in recent weeks. From Brendan Blumber to media channels, why is everyone studying EOSForce models? See here: https://medium.com/@eosforce/are-1-token-1-vote-and-voting-dividends-necessary-for-a-public-dpos-blockchain-d139e5333b43Contact EOSForceTwitter | English Telegram | Reddit | Github |Korean TelegramEOSForce blockchain explorer: https://explorer.eosforce.io/#/enWalletshttps://github.com/eosforce/wallet-desktopEOSC token is distributed in accordance with the EOS genesis mapping. You can activate your EOSForce genesis account here.Scatter 10 has minor compatibility issues with EOSForce blockchain. Join the Telegram Channel here: https://t.me/Scatter. Visit the Scatter website at: https://get-scatter.com/ExchangesBitforex | Akdex.io

EOSFORCE

19. 01. 19

Are 1-Token-1-Vote and Voti...

Community governance is the fundamental of the fundamentals.Table of contents:Foreword1. Why is voting-rewards-sharing a must for DPOS?2. Is one-token-one-vote a must?3. Thoughts on design of voting-rewards-sharing and one-token-one-vote mechanisms.4. What can Block One learn from the EOSForce’s resource models?5. What problems have been encountered in the development of blockchain applications?6. What is the bottleneck of the single-chain resource model?7. What is launching the public blockchain with just one click?8. What is the vision of EOSForce team?ForewordIn a rare series of history-breaking tweets and messages, CEO of Block.One, Brendan Blumer, has been making comments on voting-rewards-sharing and one-token-one-vote mechanisms in a variety of public channels, and even proposed to charge transfer fees.Experienced users of EOS community will find there are many similarities between BB’s new scheme and the one has been adopted by the running EOSForce mainnet. EOSForce mainnet has been running for more than six months with the one-token-one-vote, voting-rewards-sharing and charging-transfer-fee features. We’ve been suggesting that Block.One adopt the same economic model, and many blockchain media such as EOS Weekly also strongly advocate the community to refer to the economic model of EOSForce for improvements.So are one-token-one-vote and voting-rewards-sharing features necessary for a public DPOS blockchain? Can the resource model of charging transaction fee solve the congestion problem of current network? This paper mainly introduces the EOSForce community’s thoughts on the evolution of these three mechanisms since the EOSForce mainnet launched.1. Why is Voting Reward Sharing mechanism necessary for DPOS?1.1 Preventing double-spendingDouble-spending has not been taken seriously for a long time, until ETC suffered the double-spending attack recently.In DPOS consensus model, higher voter turnouts make the network more secure and the benefit of attacking networks lower. Voting-rewards-sharing mechanism can motivate more users to participate in community governance via voting, increase voter turnout, and reduce the benefit of attacking networks. Long-term observation results show that voting rewards and voter turnout are positively correlated. The turnout of EOSForce mainnet remains at 90% due to its voting-rewards-sharing feature. While the turnout of EMLG is around 40% because of the lack of rewards.1.2 Fighting inflation of the blockchainFor DPOS, the mainnet launches after the tokens have been issued (premine), so the incentive for nodes and BPs relies on the annual inflation rate. The EOSForce mainnet users can get rewards by voting, therefore, no matter how high the annual inflation rate is, the increase is returned to the voting users in the same proportion. The users who suffer losses are those who do not vote to participate in community governance.The increase part from EOSEMLG’s annual inflation of 5% are all given to the Block Producers (or BPs), the benefit users can get from the inflation is fee-free. But 90% of users will not pay more than 5% of their total tokens in a year. So if EOS does not adopt voting-rewards-sharing mechanism, the user assets will quickly depreciate.2. Is 1-Token-1-Vote a Must?One-token-30-votes needs to be corrected.There is a key point of one-token-one-vote is the super privilege.For a DPOS blockchain, whether there is a super privilege or not, two thirds of the nodes have the final say. So with the 1-token-30-votes and the super privilege, the chain directly changes from a public blockchain to a private blockchain controlled by the an interest alliance or “BP cartel”.How powerful is the super privilege? In a public test on May 17, the private key of the super-privilege account was accidentally acquired by someone who issued over 100 billion tokens and voted to his own node, which led to our emergency shutdown of the testnet. So we removed the super privilege in genesis block for the subsequent launch of mainnet. But later in the process of updating, we found that super privilege could make updating system contracts very efficient. And given that we have a one-token-one-vote mechanism, there is no possibility of conspiracy for BPs since the mainnet was launched, so we recovered the super-privilege feature, but it takes effect only when more than 2/3 BPs make multi-signing, not controlled by a single node.Monopoly brought by one-token-30-votes mechanism is the biggest harm to EOS community. The Chinese community such as EOS Cannon, EOS Gravity and HelloEOS, made a significant contribution to the community. Some centralized exchanges use users’ tokens to vote without authorization. In the logic of 1e-token-30-votes, the power of evil is magnified, so that nodes and BPs that have made great contributions to the community can be restrained by others to make their voices heard. The truth is very simple, becoming a BP requires the votes of the exchanges, if there is disagreement with the exchange, there is a risk that there will be no opportunity to participate in community governance. Of course, the only benefit of one-token-30-votes may be that it brought the community together to get mainnet launching and collectively repelled the EOSForce at that stage.3. Thoughts on Design of Voting-Rewards-Sharing and 1-Token-1-Vote MechanismsEOSForce also took a lot of detours on the design of voting-rewards-sharing at the beginning, but the good thing is that one-token-one-vote mechanism played a role.The first problem: At the beginning, we adopted another extreme which 100% opened the permission of BPs to pay rewards to voting users, resulting in competition between nodes becoming a competition of rewards. The community did not know how to exercise its rights, but only cared about which nodes pay higher voting rewards.The second problem: the 23 nodes split the block-generating rewards equally, so the node with the highest number of votes made more contributions, but its income and the voting users’ income are even less.The third problem: we wrongly underestimated the role of BP candidate. At the beginning, we thought that if more professional BPs could be offline after a DDOS attack, BP candidates might also be offline. So there was no need for BP candidates to get rewards. As a result, once a node falls out of the BPs sequence, all its votes will be revoked immediately. And the BPs will lose the competitive pressure from the BP candidates, leading to the stable ranking of the BPs within a period of time, and some BP candidates will then withdraw from the community.Taken together, these three problems turn the reward what should have been used as an incentive into an electoral bribery. After making so many stupid mistakes, the one-token-one-vote and voting-rewards-sharing played a role. And after a series of discussions and votes, eventually a proposal condense the crystallization of the wisdom of the community. It solved the three problems at once, adjust the reward back into a proper incentive. This proposal includes the BP candidates can get rewards, rewards shared according to the weight of votes, 30% of the rewards will be paid to the BPs’ account at once, the rest 70% of the rewards will pay to the community users and BPs themselves with an allocation scheme made by the BPs.The advantage is that the nodes have a fixed percentage of income, and they get rewards according to the proportion of votes obtained in the total votes. The more votes obtained, the higher rewards get. As for the voting users, they can vote for the nodes they support without worrying about the income loss due to nodes’ ranking out of the BPs list. As for BP candidates, they don’t need to worry about users withdrawing tickets due to low ranking, and can make contributions to the community reassuringly. However, it will strive to be a BP who is responsible for accounting of block generating, because the BP has 15% more reward than the BP candidate. The specific proposal was approved by more than 2/3 BPs’ votes, and the mainnet was upgraded according to it and keeps these features up to now:(1) The nodes whose votes obtained are more than 0.5% of the total votes of current network are profitable nodes. Among these profitable nodes, there are BPs and BP candidates. The first 23 are BPs and the rest are BP candidates.(2) All profitable nodes can obtain certain income, and all incomes are distributed according to the voting weight: (weight of each vote = the number of total votes of profitable nodes /the number of total votes of the whole network)1. The profitable nodes will get their income when each block is generated.2. Each profitable node gains income according to the voting weight (i.e. the proportion of votes obtained in the total votes of the current network).3. 70% of the income of each node will go into its reward pool, and the node can freely adjust the reward-sharing ratio to voters.4. For the BPs, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to its account as block-generating reward.5. For the BP candidates, 15% of the income will be credited to its account as basic salary, and 15% of the income will be credited to EOSForce Foundation account.6. The part less than 0.0001 EOSC is omitted from all single income. In particular, if the total amount of a single income is less than 0.0001 EOSC, it will not be issued. When the block-generating reward is calculated, if the sum of this part is greater than 0.0001 EOSC, it will be credited to EOSForce Foundation account.Note: For voters, only voting for the profitable node can get rewards.4. What Can Block.One Learn from EOSForce’s Resource model?4.1 Two serious problems that EOS EMLG’s current resource model encounters:- Network congestionThe free charge of mortgage has brought a large number of “econnoisseur” (i.e. click farming), which has brought a lot of junk transactions to the chain, resulting in a sharp rise in node costs and the network becomes extremely congested.- User operation threshold is too highThe few steps of a mortgage blocked 99 % of the beginners, which seriously affected the popularity of EOSIO.4.2 How does EOSForce’s resource model solve the above problems?In EOSForce, each transaction execution needs to be run in nodes of EOSForce network, which means it needs to be computed by the actual physical machine. The computing resources required are classified into three categories: CPU, NET and RAM. CPU is settled in terms of the time it takes the node to execute the transaction. NET is settled by the size of the transaction message. And RAM, meaning memory, is settled by the size of the data generated by the transaction. This data needs to be stored in the memory of the node for other contracts to read and write. Because the physical machine of the node has limited computing power and storage capacity, the resources available to users throughout the EOSForce network are also limited. In order to enable all users to use resources for transactions and prevent some users from abusing computing resources, a series of resource allocation rules need to be established, which is the resource model of EOSForce.4.2.1: Pay fees to use of CPU and NET resourcesIn EOSForce, we require users to pay a fee for each action they trigger, in a similar way to Ethereum. It will provide a CPU and NET resources limit for the action. For system native action such as transfer, creating users and privilege updating, it is fixed fee and resource restrictions mechanism, which is easy to use. For the user-customized action, the conversion rate is set by BP through multi-signing. By default, each transaction of 0.01 EOSC, the action will be given a CPU usage limitation of 200 us and NET usage limitation of 500 bytes. For user convenience, developers need to set the handling fee amount for the action in the contract submitted by themselves, so that users do not need to set it. At the same time, developers are encouraged to optimize the use efficiency of contract resources and provide users with a better experience.4.2.2 Each account has an 8kb free amount of RAM, and the voting rewards can be used to rent RAMUnlike CPU and NET, RAM uses the lease method and it set the upper limit of the RAM that can be used by the account according to the rent paid by the account. The rent is charged according to the time. In order to facilitate the user’s operation, we have set a rent free amount of 8kb for each account at this stage, so for most ordinary users they do not need to care about RAM. Usually, developers need to pay rent for the RAM used by their DAPP, including the RAM occupied by the contract and the RAM data generated during the execution.At present, we realize the function of paying the rent by voting rewards and the users can get rewards by voting in EOSForce, which forms a Token flow. And the RAM is also charged according to the time and amount of the rental. Paying rent through rewards, on the one hand, is convenient for users to operate and users do not need to pay rent and deposit frequently. On the other hand, it can improve the voter turnout and promote the healthy development of the blockchain ecosystem.EOSBet team, the super DAPP on EOS, has proposed three solutions in the community. The first solution is to recommend the use of EOSForce and Telos.5. What Problems Have Been Encountered in the Development of Blockchain Applications?Even if the above problems are solved and better underlying infrastructure is provided, the problems encountered by developers of blockchain applications are still unprecedented:First, developers still need to figure out what problem to solve. There is no living space if it cannot solve any problem, that is why the DAPP BETDICE is so short-lived and not helpful to EOS price. It’s hard to imagine an application scenario by sitting in an office, developers still need to know more about the historical solution of the problem to be solved. Is it necessary to use the blockchain technology?Second, developers should be familiar with the public chain and blockchain technology. In other words, they should be familiar with the powerful tool of blockchain. Simply writing a smart contract doesn’t make for a great application like bitcoin. Developers have insufficient understanding of the public chain, resulting in no way to maximize the role of blockchain.Moreover, many people regard decentralization as an end. But our goal is not decentralization. Decentralization is just our means. Through more or less decentralization to guarantee the fairness, security and cost reduction of the issues we have to solve. Decentralization is a means rather than an end.What also needs to be improved is the developer’s understanding of the economic model. If you look at the whole economic model of bitcoin, it’s really great and elaborate, and it’s very ambitious, but today a lot of developers just use the feature of token rewards.When we are developing blockchain applications today, there is a misconception that we follow the logic of the early rise of the Internet. We may think that the development of blockchain is the same as the Internet, from text to pictures to video, or from gambling and drugs. But what’s missing is that those are the problems that the centralized Internet is good at solving, not the problems that blockchain is good at solving. In the early days of the Internet, it did not prove much more efficient than traditional businesses. If Alibaba had challenged new retail directly in the first place, it would like throwing straws against the wind. Similarly, before the blockchain challenges the social and e-commerce business dominated by the Internet interest alliance, it should at least prove the security and trust-cost-reduction advantages brought by the blockchain in the field it is good at.6. What is the Bottleneck of the Single-Chain Resource Model?At present, there is no good parallel processing scheme in the entire blockchain field, and the average performance of the public chain depends on the performance of block-generating server with the lowest configuration. Limited by the physical characteristics of silicon, the computing power of a single server will not continue to increase as rapidly as it has in the past decade for a long time in the future (5–10 years). The current Internet computing is to expand the number of centralized servers to solve the problem of performance limitations.For blockchain, it is difficult to solve performance problems at an acceptable cost if only the computing and services of multiple applications are stacked on a single server.For EOSIO, there are three performance bottlenecks, CPU, NET and RAM. Even if the CPU can achieve dozens of performance improvements in parallel in the future, RAM will still be limited by a single server for a long time. The recent public-chain practices of Ethereum and EOSIO have shown that it is almost impossible to rely on a public chain to achieve high performance and high concurrency under the premise of guaranteeing decentralization in the short term.Although we can foresee a decade later, thanks to the continued breakthrough of technology and algorithm optimization of the chain, the bottleneck of single-chain will be solved. But in the recent 5–10 years, we will hardly see this breakthrough. In the future, we must propose an effective solution on the eve of the blockchain application outbreak.Based on the judgment of technology evolution in 5–10 years, a business scenario needs to be hosted by a single public chain, and even a business scenario needs to be solved by a multi-chain architecture. Our EOSForce multi-chain and cross-chain protocol is developed for these reasons.In the case of the ENU community, the ENU network was launched to achieve UBI. A decentralized organization promotes the basic income of the whole people. Launching the public chain network alone can minimize the resource cost and flexibly utilize the various characteristics of the public chain. And our continuous iterative DPOS protocol will have very good underlying support for ENU network, allowing the entire community to focus on UBI application development and popularization.7. What is Launching the Public Blockchain with Just One Click?Based on this judgment, we plan to provide developers with a one-click launching public blockchain service in Q1 2019. Based on the EOSForce multi-chain and cross-chain protocol, we can not only meet the needs of developers with multiple consensus models, but also meet the need for data structure differentiation and functional diversification on other chains.Two new resource models are supported in the latest version of the EOSForce multi-chain Protocol. One is EOSIO’s mortgage and leasing resource model and the other is a free resource model. When launching a public blockchain based on the EOSForce multi-chain protocol, developers can choose one from three models, the EOSForce fee model, the EMLG mortgage leasing model and a free resource model similar to the consortium blockchain. Many people of public blockchain community look down on the consortium blockchain, but the consortium blockchain is the fastest one to embrace the block chain technology, and also the fastest one to produce practical applications.Ethereum makes issuing tokens a kind of inclusive right, and the EOSForce will make it easier to launch a public blockchain of diversified consensus, while making it convenient for multiple chains to interoperate.8. What is the VISION of EOSForce Team?The vision of EOSForce development team is to explore a more open crypto economy infrastructure in practice. We continue to develop multi-chain and cross-chain protocols based on EOSForce.io to promote the application of blockchain in various industries.This means that whether it is POW or DPOS, or multiple resource model requirements in DPOS, we need to explore and develop. So we made a series of initiatives:Launched EOSForce, an EOS parallel mainnet, and assumed responsibility for network upgrade and iterationPublicly support the “competitor” ENUEOS EMLG is also supported in the smart contracts tutorialSupport BCH to develop a peer-to-peer electronic cash systemProvide the service of one-click to launch public blockchainFollow us on GitHub: https://github.com/eosforceContact EOSForceTwitter | English Telegram | Reddit | Github |Korean TelegramEOSForce blockchain explorer: https://explorer.eosforce.io/#/enWalletshttps://github.com/eosforce/wallet-desktopEOSC token is distributed in accordance with the EOS genesis mapping. You can activate your EOSForce genesis account here.Scatter 10 has minor compatibility issues with EOSForce blockchain. Join the Telegram Channel here: https://t.me/Scatter. Visit the Scatter website at: https://get-scatter.com/ExchangesBitforex | Akdex.io

EOSFORCE

19. 01. 15

The Rise of EOS Sisterchain...

The development of blockchain technology as an industry necessarily experiences the ups and downs of any rising industry. And any rise and fall of an industry resembles to that of a company, nation, individual, and any other entity that runs its course in history. When the power-center entity is weak, its subsidiary rises up. When the power-center dissatisfies, the vassel states demand changes. When the power-center does not suffice, developers fork the chain. This is JC from EOSForce Global Operations, and today, we will take a look at the innovation that has swept through the EOSIO ecosystem from EOS Sisterchains & EOSForce.EOSIO is the software developed by the Block.one company that raised 4 billion dollars from its ICOs. In June 2018, a group of international EOS enthusiast communities, which in my opinion are still the most participatory blockchain community there is, gathered together and launched their EOS mainnet. This group is called EOS Mainnet Launch Group, and hence their mainnet is sometimes referred to as EOS EMLG. They were firm believers in the EOSIO software and EOS governance system proposed by Block.one, and they launched the mainnet without making fundamental changes.In the months leading up to the launch of EOS software, a Chinese team called EOSForce, part of the EMLG group, saw some potential flaws in the EOS blockchain and potential changes that could be made. However, making changes on the fundamental level of blockchain codes required highly skilled engineering brainpower, so the team leader Cyborg founded a team of blockchain engineers and started to examine the code and see where how they could make the blockchain better. After 3 months of studying, the EOSForce team saw the changes they could make and decided to launch their own version of the software mainnet. This was not well-received by the EMLG community and the EOSForce chain was given cold faces by the prominent BP members of the EMLG group.The first fork chain of EOSIO software did not go well. Or was it?One open-minded feature of blockchain softwares is they are open-sourced. People can make changes and variation for a version of their own. The EOSIO software developed by Block.one was open to all interested members of the community. Still, the EOSForce Mainnet started off with bullets passing its shoulders.At the same time, the community development of EOSForce stood in the awkward position of domestic exclusion, where there is an already capped community growth in China, while international expansion efforts had barely taken off.The popularity of Telos and Worbli changed minds. When more sisterchains popped up in the EOSIO ecosystem, people’s minds started to shift — maybe actually there should be other mainnets too. However, the value these mainnets bring to the EOSIO blockchain advancement remained unclear.3 months after the launch of EOSIO by EMLG, the “Huobi BP vote collusion/buying” scandal took off in the EOS community. A series of document detailing the exact vote exchanges between the EOS BP Huobipool and numerous other top BPs on the EOS Mainnet was release into the EOS public. The news blast through the EOS community and voters from the West called for boycotting against Huobipoolbp, and some event suggested to remove Huobipoolbp as an EOS BP. Vote-buying and BP collusion, although always existing, had been brought under the spotlight in the EOSIO ecosystem.At the same time, the EOS referendum system was under development by a group of EOS BPs (thankfully these BPs did not appear in Huobi’s vote collusion document). The system aimed at addressing the constant conflicts between ECAF and the BPs, and also the lack of channels for voters to voice their opinions. The referendum system required a bare minimum of 15% votes to pass. This is a problem.If you recall, near the launch date of EOS EMLG, the group struggled to gagner the 15% bare minimum votes required to launch. The launch date was forced to be delayed. It was not after the help from the Chinese crypto billionaire Li Xiaolai that the EMLG had enough token votes to launch the EOSIO software. Standing in the shadow of the “launch delayed due to lack of voters” incident, the EOS referendum system took off.During this period, people were looking for governance solutions that could fundamentally improve the EOS Mainnet governance system. Calls for community actions were made, but mostly to no avail. Effective voter communication channels were still underdeveloped.EOSForce, while seeing all of this happened, with its updated governance features — 1-token-1-vote, voter dividend for high voter participation, and a new network resource model — started to ramp up its international community building efforts, with a clear conviction that new governance and communication model should be brought under spotlight right now if we ever want to make blockchain use popular.“Life clears out the old to make way for the new.”One of the most unique aspect of decentralized governance community that many fail to appreciate is the fantastic community initiate that happens all the time. While EOSForce kept pushing out contents and articles for discussion and education, these contents got noticed by a group of independent blockchain/EOS media, the likes of EOS Weekly, Everything EOS, Colin Talks Crypto, MaxDapp, CryptoTim and many others we should not ever overlook the importance of.When people saw the governance gridlock and the slow change process on EOS EMLG, they turned to other alternative solutions. Now many more people are discussing the important subjects of voter incentive. With Brendan Blumber’s Twitter bringing this subject under spotlight, the EOS community’s discussion sentiment is at its historic height.It is exactly the rise from EOSForce and sisterchains that propelled the community forward to discussing these important issues.By offering innovative and more organic community building and governance measures, EOSForce now has openned people’s minds to rethink exactly the relationship between the EOSIO software and individual chains built on it. By fundamentally shifting the framework of how people think, changes outside the box could then happen. In the past, people only take examples from EOS Mainnet, and now people see that other mainnets may offer better solutions than what’s available on the original luanch group. This is progress.Eventually, we must understand we are all striving for a common goal here — mass adoption for the blockchain technology. We are not striving for the individual interests of token holders, of developers, of whales/exchanges, or with investors. By putting the common goal first and thinking from this larger picture, the blockchain technology grows, and the hard work of token hodlers, developers, and investors will be paid off. Only putting one group’s interest first benefits no-one.Contact EOSForceTwitter | English Telegram | Reddit | Github |Korean TelegramEOSForce blockchain explorer: https://explorer.eosforce.io/#/enWalletshttps://github.com/eosforce/wallet-desktopEOSC token is distributed in accordance with the EOS genesis mapping. You can activate your EOSForce genesis account here.Scatter 10 has minor compatibility issues with EOSForce blockchain. Join the Telegram Channel here: https://t.me/Scatter. Visit the Scatter website at: https://get-scatter.com/ExchangesBitforex | Akdex.io

EOSFORCE

19. 01. 13

Transaction History
Transaction History Address
Kucoin Short cut
BitForex Short cut
Security verification

There is security verification of the project
Why security verification is necessary?

Read more

comment

* Written questions can not be edited.

* The questions will be answered directly by the token team.

  • 코인신 Sep 07. 2019

    요즘 초창기에 비해 너무 많은 코인이 나와서 어떤코인이 정말 스킴인지 분간이 가지 않아요. 정말 필요한 경쟁에서 이길수 있도록 노력

    바라겠습니다. 그리고 아무리 유망한 코인 이라도 마케딩이 중요하다 생각 됩니다. 지속적인 마케팅 계획과 메이져 거래소 상장 계획 궁금합니다.

  • 야스먄 Jan 03. 2019

    제네시스스냅샷이 머에요?

  • bubu Dec 17. 2018

    이것도 eos 보유시 받는거죠??
    일정은 아직 미정인가요

    EOSFORCE Person in charge Dec 17. 2018

    본 에어드랍은,
    기존에 제네시스 스냅샷을 토큰뱅크에서 참여하신 회원에 한하여 지급받을 수 있습니다.

  • Dkdjfjf Dec 17. 2018

    카톡방있나요?

  • Hkgom Dec 12. 2018

    제네시스 스냅샷도 토큰뱅크에 보유하는 것만으로 에어드랍 받을 수 있는건가요?

    EOSFORCE Person in charge Dec 12. 2018

    제네시스 스냅샷의 경우 ,
    기존에 제네시스 스냅샷을 토큰뱅크에서 참여하신 회원에 한하여 지급받을 수 있습니다.

  • 수퍼긍정 Dec 10. 2018

    헛 제네시스 스냅샷ㅋㅋㅋㅋ이거 사이드체인 아닌가요?

    EOSFORCE Person in charge Dec 10. 2018

    안녕하세요. 수퍼긍정님 사이드체인 에어드랍 또한 지원합니다.
    제네시스 스냅샷 기준으로 지급될 예정입니다.

Information
Platform EOSC
Accepting
Hard cap -
Audit -
Stage -
Location -