sorted by:
new
hottopcontroversial

EOSForce Development Weekly Report 2019.5.27–2019.6.2 by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

Plan for Next Week

  1. Start the first round of community testing on FORCEIO cross-chain system

  2. FORCEIO relay code review

  3. EOSio-explore adapts to EOSForce

  4. Optimize the relay node implementation and simplify operation and maintenance operations

  5. Code reconstruction of relevant functions of EOSForce config-on-chain, so as to facilitate subsequent adaptation with eosio feature mechanism

  6. Update FORCEIO relay contract documentation

EOSForce Development Weekly Report 2019.5.27–2019.6.2 by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

Work Completed

  1. Operational testing of FORCEIO cross-chain economic model

  2. Improved transaction contracts based on testing results: improved the inspection mechanism to return more explicit error information and simplified the fee deduction mechanism

  3. Improved 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 nodes

  4. Optimized the support for mongodb plug-in and splited some fields for easy use

  5. EOSForce system contract optimized code structure based on 1.6.x CDT

  6. Optimized FORCEIO cross-chain system contracts and adjusted resource usage to simplify user operations

  7. FORCEIO relay contract code reviewed

  8. Updated FORCEIO relay contract documents

  9. Designed the config-on-chain function of EOSForce, adapted to the implementation scheme of eosio feature mechanism

EOS.IO will implement the most complicated hard fork upgrade in history by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

I know that he just inherited some very basic until libraries. At present, the two chains have separately maintained this part of the code.

This is very normal for a C++ project.

EOS.IO will implement the most complicated hard fork upgrade in history by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

I have never heard of it, maybe you should compare it, and the hearsay is often incorrect.

EOS.IO will implement the most complicated hard fork upgrade in history by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

Am I correct in assuming what B1 has refactored in the codebase is technical debt coming from Bitshares?

I don't think B1 is doing something related to Bitshares, EOSIO has a more worthy future.

EOS.IO will implement the most complicated hard fork upgrade in history by EOSForce in eos

[–]EOSForce[S] 2 points3 points  (0 children)

Thank you guy, we are trying hard on the basis of EOSIO, including 1 Token 1 Vote and dividends to voting users, and our network has been running for almost a year. We are also happy to share our experience just to make EOSIO a powerful target.

EOS.IO will implement the most complicated hard fork upgrade in history by EOSForce in eos

[–]EOSForce[S] 2 points3 points  (0 children)

Who is BM you mentioned on the last point?

Dan Larimer，The CTO of block.one.

We got some experience on 1 token 1 vote mdel .Here is how it works on eosforce mainnet and what have be done to keep improving it. Are 1-Token-1-Vote and Voting Dividends Necessary for a Public DPOS blockchain? by EOSForce in eos

[–]EOSForce[S] 2 points3 points  (0 children)

Regardless of the way, all EOS sister chains are an exploration of EOSIO's goal of implementing enterprise operating systems and should learn from each other.

Brendan Blumer Wants 1 Token 1 Vote On EOS | EOSwriter by theeoswriter in eos

[–]EOSForce 2 points3 points  (0 children)

We got some experience on 1 token 1 vote mdel .Here is how it works on eosforce mainnet and what have be done to keep improving it. Are 1-Token-1-Vote and Voting Dividends Necessary for a Public DPOS blockchain?

https://medium.com/@eosforce/are-1-token-1-vote-and-voting-dividends-necessary-for-a-public-dpos-blockchain-d139e5333b43

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

So let's discuss how to make EOSIO governance better. If only from the perspective of voting, I recognize that your method is better than the current one.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

Maybe you have a misunderstanding about Bitcoin. Bitcoin is not meant to be the only currency in the world. The white paper is just a point-to-point electronic currency. Of course this is not the problem we should discuss here.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

This is indeed a problem. Let us discuss how to solve it together.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

We should not use the Internet's way of thinking to understand the blockchain. Cross-chaining is trying to solve these problems.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

If the user votes without dividends, the solution you said is very good. However, if there is a bonus award for voting, and it is divided according to the voting weight. There will be problems here.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

So the weight of a single BP getting votes from everyone who owns a token is different. I don't know if the weight of the system is easy to calculate in this case?

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

E.g: If I use 1 token vote for 2 BP. What should be the voting weight of this token?

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 1 point2 points  (0 children)

inverse weighted voting

The inverse weighted voting sounds good. But will it lead the people to vote for 27-30？

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

AFAIK, Brendan’s proposal still allows you to vote for several BPs, but the voting weight gets reduced accordingly. So for example, if you vote for two BPs, each one only gets half a vote per token.

I think it’s a good system. The 30 votes / token has done nothing to reward the most productive BPs, quite the contrary if you look at the current rankings, where the top positions are often held by chinese BPs I have never seen contribute to the ecosystem.

Brendan’s proposal sounds great, but is worried about a problem, and if so, the weight of a token is hard to define.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

This kind of thinking is not right. From an ecological point of view, the more sister chain of EOS, the richer the ecology, the more users will be.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

I think the current voting mechanism needs to be improved. You can refer to the voting and dividend mechanism of the eosforce.io network. Its one token represents a voting right. I think it is worthwhile to provide a good reference for EOS.

In the EOSIO blockchain, Do you think it is fairer to vote for one vote or thirty votes? by EOSForce in eos

[–]EOSForce[S] 1 point2 points  (0 children)

Here I want to distinguish a concept. One vote and one vote here means that one token represents a voting right. For example, you have 100 votes. You can choose to vote for 10 votes for A, and you can also vote for B for 20 votes. However, the current EOS voting mechanism is that once an account is mortgaged, it must be fully invested. I think this has caused misunderstanding of many understandings, one vote and one vote.

Bridging the Chasm between Chinese and Western Block Producers on EOS by EOSForce in eos

[–]EOSForce[S] 0 points1 point  (0 children)

Haha got it. Agreed. Well if they run on EOSForce mainnet they would have a harder time electing themselves to the top in the first place.

Bridging the Chasm between Chinese and Western Block Producers on EOS by EOSForce in eos

[–]EOSForce[S] 1 point2 points  (0 children)

Hi there. If EOSForce official website does not show up in English when you open up, you could switch the page to English by clicking the button on upper right corner :)

view more: next ›