Author Topic: Proposal: Keep delegates' task simple - signing blocks.  (Read 7177 times)

0 Members and 1 Guest are viewing this topic.

Offline matt608

  • Hero Member
  • *****
  • Posts: 878
    • View Profile
We cannot have more than 101 elected positions, it simply doesn't scale.

It should end up in a state where in normal circumstances we don't even have to see which delegates are being voted. Their task is simple, publish blocks on time and they will be auto ranked and voted.

The employees on the other hand would be voted by us in a more hands on approach.

Could block signers be ranked by an algorithm measuring their reliability, frequence of feed updates, frequency of version update, number of active feeds and average latency (all the fields in http://www.bitsharesblocks.com/delegates), to make it easier for voters to make their choices? 

Edit: I realise this may silly as they are ranked by their approval, but what if there was an option to 'rank by quality'?

Speaking of which, how does a voter find out if a delegate is dishonestly signing blocks?  What attacks can a block signer do to the network and what does it look like?

« Last Edit: November 04, 2014, 06:05:02 pm by matt608 »

Offline bytemaster

A block signer can be appointed and paid by a delegate and can be fired/reassigned at any time by a delegate. 

Thats just unnecessary distraction for the delegate, who may not be the best in choosing the correct block signer. If the delegate has a skill set which would be useful, let him just do that, no need to make him seek out an able block signer and outsource.

Another advantage for separation would be that there won't be a limit of the pay or the number of employees, giving better flexibility. It also will allow for short bounty style payments, which would case quite a upheaval in the  current model as a delegate comes and leaves for a short period.

What part of we cannot have shares vote for more than 101 *THINGS* because it does not scale.  So saying that there won't be a limit on employees or pay is wrong.  We need to limit pay to prevent unbounded dilution and we need to limit funded positions because of transaction processing time and size.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

sumantso

  • Guest
We cannot have more than 101 elected positions, it simply doesn't scale.

It should end up in a state where in normal circumstances we don't even have to see which delegates are being voted. Their task is simple, publish blocks on time and they will be auto ranked and voted.

The employees on the other hand would be voted by us in a more hands on approach.

sumantso

  • Guest
A block signer can be appointed and paid by a delegate and can be fired/reassigned at any time by a delegate. 

Thats just unnecessary distraction for the delegate, who may not be the best in choosing the correct block signer. If the delegate has a skill set which would be useful, let him just do that, no need to make him seek out an able block signer and outsource.

Another advantage for separation would be that there won't be a limit of the pay or the number of employees, giving better flexibility. It also will allow for short bounty style payments, which would case quite a upheaval in the  current model as a delegate comes and leaves for a short period.
« Last Edit: November 04, 2014, 05:34:36 pm by sumantso »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
A block signer can be appointed and paid by a delegate and can be fired/reassigned at any time by a delegate. 
That would be so +5%

Offline btswildpig

  • Hero Member
  • *****
  • Posts: 1424
    • View Profile
We are in favor of separating block signers from delegate accounts.

A block signer can be appointed and paid by a delegate and can be fired/reassigned at any time by a delegate. 

We cannot have more than 101 elected positions, it simply doesn't scale.

so marketer delegates don't have to know about server/vps...etc and still can be paid by a network ? That would be nice ...
这个是私人账号,表达的一切言论均不代表任何团队和任何人。This is my personal account , anything I said with this account will be my opinion alone and has nothing to do with any group.

Offline bytemaster

We are in favor of separating block signers from delegate accounts.

A block signer can be appointed and paid by a delegate and can be fired/reassigned at any time by a delegate. 

We cannot have more than 101 elected positions, it simply doesn't scale.

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline biophil

  • Hero Member
  • *****
  • Posts: 880
  • Professor of Computer Science
    • View Profile
    • My Academic Website
  • BitShares: biophil
I think the end compromise that will be made is that delegates can outsource their block signing to someone else. The block signer cannot control or change the reward and it is sent directly to the real delegate, but he can get paid a fixed rate for his services automatically.

It would help, but stakeholders whould have still no (direct) control over who is signing blocks for the delegate, correct?
Therefore I would still be in favour of a complete separation of roles.

I've been thinking this too.

Sent from my SCH-S720C using Tapatalk 2

Support our research efforts to improve BitAsset price-pegging! Vote for worker 1.14.204 "201907-uccs-research-project."

Offline Frodo

  • Sr. Member
  • ****
  • Posts: 351
    • View Profile
  • BitShares: frodo
I think the end compromise that will be made is that delegates can outsource their block signing to someone else. The block signer cannot control or change the reward and it is sent directly to the real delegate, but he can get paid a fixed rate for his services automatically.

It would help, but stakeholders whould have still no (direct) control over who is signing blocks for the delegate, correct?
Therefore I would still be in favour of a complete separation of roles.

Offline joele

  • Sr. Member
  • ****
  • Posts: 467
    • View Profile
I think the end compromise that will be made is that delegates can outsource their block signing to someone else. The block signer cannot control or change the reward and it is sent directly to the real delegate, but he can get paid a fixed rate for his services automatically.
+5

Offline Rune

  • Hero Member
  • *****
  • Posts: 1120
    • View Profile
I think the end compromise that will be made is that delegates can outsource their block signing to someone else. The block signer cannot control or change the reward and it is sent directly to the real delegate, but he can get paid a fixed rate for his services automatically.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani


sumantso

  • Guest
In the current model any kind of employee who wants to contribute and gets paid will have to take the hassle of running a delegate. They may lack the technical skills, which would make them hire somebody, or they may decide to do themself and not be very good at it. At the end, how will they be judged - their block production reliability or their task (marketing, developing etc)?

I feel the tasks should be separated. Delegates should stay exactly as now, getting a small pay and creating blocks, publishing feeds etc. We will also have employees (or whatever term sounds better) who will set a payrate as percentage of the total dilution pool. This will not only let them focus on their task and not get distracted, it will also allow the payrate to go above 100% from the current model if necessary. For example if a 2nd BM turns up, we would be certainly wise to break the bank (so to speak) and in the current model it would be difficult as ideally we would want a 1 person=1 delegate scheme.

Block production is a fundamental part of the network being maintained, so I think it should be kept simple and separate with a low barrier of entry. It would be useful in case the network has some form of crisis.

Named it proposal as that seems to be the rage these days :P