Due to the relatively low self-bond, you should go for a higher number of desired candidates to ensure enough value is staked. I would aim for 32-64. However, I recommend you increase the count gradually and perhaps manually assign the collator spots. Due to the low candidacy bond there is a danger that multiple slots are taken by a single entity which would be a bad start.
To conclude, at today's market prices (low barrier) and given the lack of collation incentives, I would err to a more censored approach. Looking forward to joining your collator set!
Ioannis | StakeBaby
Another alternative is to use the illiquid stake-to-vote (vKINT) currency as implemented in this PR: https://github.com/interlay/interbtc/pull/688
hi,
I think what Ioannis wrote seems quite reasonable. I would add an emphasis on inclusion of whitelisted collator selection from trusted collators that took part in the testnet.
I think Ioannis's analysis is thorough and thoughtful and I support their recommendations.
@Curu
I like the concept of whitelist, I would extend the range to vault operators older than 3 months (3 as example)
Marvel
I tend to agree with what Ioannis described. The way I see it is there are basically three ways of rewarding collators sustainably
I am not sure how inflation rewards would fit into your tokenomics model so let's leave out this one. As was already mentioned, tx number in the network is rather low and it's hard to imagine it will change in the near future (unfortunately I believe this bear market will last for some time).
So this leaves us with the treasury option which is actually the most flexible one as well. It allows you to whitelist candidates and openly discuss their rewards in a form of spending proposals for your treasury to cover at least some of their infrastructure costs. I wonder what do you think about this? @gregdhill
Regarding the size of the bond, I think there are two points of view that are worth mentioning.
For 1), I think the fair amount is around 1-2k USD.
It is important to note that the
CandidacyBond
should not be set too low to avoid potential Denial of Service (DoS) attacks since the defaultCollatorSelection
implementation does not slash misbehavior. If the deposit is cheap enough, malicious actors could repeatedly re-register and not produce blocks within theKickThreshold
.