OriginTrail / OT-RFC-repository

14 stars 3 forks source link

Discussion for OT-RFC-07 #2

Closed branarakic closed 1 year ago

branarakic commented 3 years ago

Hi Tracers,

This issue is dedicated for discussions on OT-RFC-07 - Multichain OriginTrail Decentralized Network - Starfleet stage

For convenience, the link to the latest version of the RFC is here

hottogo commented 3 years ago

It is a really good write up.

My main concern is the 13 initial validators, increasing to 37 at a later date.

My concerns are three fold:

  1. These 13 or 37 validators will be incentivized by fees which may not align with the wants of the community. The best incentive mechanism aligns the goals of the community with the incentivization. It will be difficult for the validators to self police themselves on a fair amount of fees - the community will want them to break-even and the validators will want to make a profit (which is not unreasonable). This also has the danger of splitting the community if node runners feel that validators are taking too big of a share of earnings. I understand the fees at first would be minimal, but I am looking further ahead at full adoption.

  2. At initially 13 and later 37 validators, the number is quite low and not necessarily an inclusive representation of the whole community. I imagine those close to the team and those that have contributed will be chosen - and rightly so, however this method of selecting validators will be criticized for centralization. One way around this would be to hold an election for the validator positions.

  3. If the fees to post a job are much much cheaper on Starfleet as opposed to Ethereum, the vast majority of job posters and node runners will switch to Starfleet. Despite the 'option' of running on Ethereum, the project will be seen as less decentralized because the security layer blockchain is controlled by a select minority which includes some industry players. It may deter usage and adoption by those that don't want to use the solution that their competitor part secures.

Overall I am happy with the proposal and think it is a great step forward for the ODN - heading towards its multichain future.

mucke12 commented 3 years ago

Do I also need to deposit StarTRAC on the SFC? and will we be able to payout current jobs on the SFC ?

ncerovac commented 3 years ago

Just finished reading pdf. I really like the concept. Looking at Ethereum roadmap we have a few more years before proper testing of scalability on proof of stake Ethereum network.

With that in mind, I do agree that the future of decentralization will be multiple protocols that all have pros and cons of usage. By deciding to go blockchain agnostic I think OT is being more open to testing and utilizing the best solutions.

I see you are already exploring Polkadot and that's great. I would add suggestions to also take a look at Near too. Some interesting concept that I found there is that part of the fee is going to smart contract deployer so maybe there are some interesting points for you to explore.

Anyhow, love where all of this is going.

Engage! ;)

branarakic commented 3 years ago

Thanks everyone for the feedback, those are all solid points.

@hottogo we've just uploaded an update (v1.2) that extends the RFC with additional information on validators so I'd encourage you to take a look

@mucke12 the details of the implementation are yet to be determined. An ODN node is required to stake a specific amount of TRAC in order to participate in a specific blockchain implementation market, so that will apply to Starfleet as well

@ncerovac thanks for the suggestions, those are always extremely welcome. Live long and prosper!

branarakic commented 3 years ago

LAST CALL

We are issuing the last call for the RFC-07, which means the Trace Alliance Starfleet Task Force will be collecting feedback by November 6th, which is the tentative date of RFC stage transitioning to ACCEPTED stage. Please provide all additional feedback and comments by then.

More information on the RFC lifecycle can be found here.

hottogo commented 3 years ago

@branarakic Thanks v1.2 addresses most of my concerns on validators.