I agree with this.
Maybe the team will agree to hold on the $FX to release them part by part.
Iāve also seen (testnet) the team is working on a proposal milestone delivery smart-contract which would be great for validators to vote on the release of fundsā¦
As for the rest, I expect you to be publishing recurrent information (every month) about the tool progress (FX-BAVA TVL, unique users, active users, etc.), as well as transaction hashes when you receive funds, etc.
I agree on this approach, i can provide the address to hold the fund, and we will release it once Baklava has reached the agreed TVL.
It will be great if you have some regular metric updates, as @FrenchXCore mentioned. It will be helpful for our community to keep updated on your project.
I donāt agree with this strategy. I represent public validator Alif & we are currently on spot # 33. We have always offered exceptional service since FX mainnet launch, always offered competitive commission rates (0% for the first 6 months, 1% up until Feb 2023) & were one of the first public validators to have sentry & backup servers for improved security & uptime. We have been active on forums, always participated in voting & never have been jailed. Even with doing everything right, we donāt have enough fx delegated to meet the top 25 cut.
This is a big deal because if we are not part of initial auto distribution, our gap to others will grow even further which will not be fair. I am sure there are other public validators, who are in the same boat as us.
To keep things fair, I recommend you make all reliable public validators part of your initial auto distribution & possibly not include company validators. Because the long term goal for company validators is to distribute tokens among public validators, this will slowly initiate the process.
Yes i think the same.
I still have my validator Function X StarScan inactive and I think that it will never become active with the suggestion. Iām always updating and I hope that Iāll get delegaters at some point. I think your system will rob all future validators of the chance to get up.
Best regards Sylvia ByteX
@ByteXSylvia :
Your 1st validator was tombstoned, meaning that 5% of all your delegators money went slashedā¦ (see below). Thatās what happen when a validator strongly misbehaves. Happily, you didnāt have many public delegations at that time. But 5% of teamās money got āslashesā.
Your 2nd validator is currently inactive since end of march 2023ā¦ because you have too few delegations.
What happens when a validator is slashed ?
The slashed tokens (0.1% of delegations in cas of jail [more than 19k blocks missed] or 5% in case of tombstone [single try to get a consensus around a bad block]) are distributed to other validators and delegators within the network. This redistribution is based on factors like the proportion of tokens staked or delegated to other validators. By doing so, the network incentivizes active participation and discourages malicious or unskilled actorsā activities.
whether the proposal is good for FunctionX ecosystem,
whether the proposal is good for your validator.
I know Iām in a bad seat to discuss that because our validator will be in the first list. However, thatās why I raised the point in a timely manner (before the proposal was submitted).
Moreover, this 25-1st validators list does not seem to me like a definitive issue, as it might evolve in the future.
There are thus 3 things that need to be discussed :
what are the main parameters taken into account by the team to increase public validatorās delegations from the FunctionX foundationās tokens in the future ?
what is being done to attract more public validators into the ecosystem ?
what are we doing (ourselves) to attract more delegations from public delegators ?
Nothing is locked there, he just has too few delegators. Please do not spread false information. The first validator became inactive due to the upgrade error, it was 99% my own FX that got lost.
My bad : Iāll edit my post. It was just unbonded.
Please note my intent is not to spread fake info, but I am also a human who makes slight mistakes sometimesā¦
15 minutes is a long time to damage my reputation. I would never damage someoneās reputation like that if I didnāt have 100% proof. Thatās because of the respect I have for every user or do you think Iām not smart enough as a woman to run a validator?
Wow ! That went bad too fast for me.
As I wrote to you in a DM over TG: 1) I wrote on the forum, not on Twitter. So, probably noone beside the two of us saw the post in between during this 15 minutes lapse. Thereās not enough users connected for that. And if you were to loose delegations in between, Iād delegate the difference myself to your validator node. 2) Iām never considering gender in any of my decisions. Because Iām trusting deeply into diversity in my decisions.
I wonāt reply any further as I already apologized and edited my post in a very timely manner, and this discussion is now completely off-topicā¦
As a lesson for the future, I will never comment out on another validator and will just keep on helping users who ask meā¦
Iāll leave it to delegators to judge by themselves for the rest.
You already know that itās a criminal act that puts people down without evidence. You harm me and my company with your statements. Please consider that something like this is punishable in Europe. First think than write!!!
I will really appreciate if we only discuss about Baklava Space (products, features, proposals, and updates) here. The forum will be helpful for us to improve our product.
All hell is breaking looseā¦
I gave you all information required to report me to the police if you feel like it.
But talking about ācriminal actsā is at least wrongā¦
What I did was a simple mistake, quickly corrected, apologized for, that could eventually be considered a civil defamation in E.U. if there were damages, which were not since your validator node didnāt loose or gain any delegator in the timeframe.
But putting this conversation publicly and going insane is not helping.
@JohnB : thank you for clarifying the situation towards public validators. If I can be of any technical help, donāt hesitate to ask in DM.