You start with this not me!!!
i have just a Question post
The proposal is good for the ecosystem and Alif will be voting in favor regardless of how many/which validators are included from the start.
Just raising a valid concern for public validators who are not in the top 25 and operating a reliable validator.
Wow wow wow
Why you talk about gender, frence not attacking gender
I think this is just miss communication here, not need to be drama
I agree on this suggestion.
Baklava team can work on adding support to all validators.
We Aghanism host a reliable good uptime validator and follow the upgrade promptly without jail so I hope increasing the validator slot a little more can be a consideration
Guys,
Don’t forget to vote on proposal #40, which ends on August 8th, 2023.
After 4 days of voting, we reached 22.6% votes, all for YES, on proposal #40.
As a reminder, a quorum of 40% is required for proposal to go forward.
Please note that, even if your validator is inactive, you can vote for a proposal so that all staked tokens are accounted for. See at the end of this message if you encounter an issue.
Public validators which voted:
- Superbit123
World of FX Wizards 

FrenchメCore-1 

Fox 
- DAOVerse
- ClaudioメBarros
- FxWorld
- Alif
- 212th FX Battalion
- blocktempo
- paf_yyc_ca
- SmallFort
- ContributionDAO
- LeValidateurFX
- FX FriendsX (currently inactive)
Public validators which didn’t vote yet :
- Litecoin Foundation
- European University Cyprus
- Blindgotchi
- Asosiasi Blockchain Indonesia
- Blockchain Collaborative Consortium
- nexus
- Nammy

- NOBI
- LuckyFX
- Scale Moment Group
EA:robot:31337:chart_with_upwards_trend:- Cogni🧠

Moonbase- Dapp.com
- Janc
- Scissors
- Rock
- Aghanism (currently inactive)
- ByteX No longer active (currently inactive)
- AquillaX (currently inactive)
- dutchblue (currently inactive)
- Paper (currently inactive)
- fx-royv-validator (currently inactive)
- ByteX (currently inactive)
- Crypto Kid (currently inactive)
- fx-royv (currently inactive)
For inactive validators:
Unless your validator node is out of sync, or jailed, you should be able to vote.
If that ain’t working using the usual CLI commands, that might be because your validator is out-of-sync.
In such a case, you always have the option to add the following argument at the end of your command, either :
--node https://fx-json.functionx.io:26657, (FX foundation’s TM public node) or--node https://mainnet-tm-fx.frenchxcore.eu:26657(FrenchXCore TM public node)
You can also change the node value in your$HOME/.fxcore/config/client.toml file
Decentralization is also about this ![]()
![]()
Regards,
@FrenchXCore
thank you so much for your effort
[Updated 01/AUG/2023 11:00AM GMT+2]
Guys,
Don’t forget to vote on proposal #40, which ends on August 8th, 2023.
After 7 days of voting, we reached 29.7% votes, all for YES, on proposal #40.
As a reminder, a quorum of 40% is required for proposal to go forward.
Please note that, even if your validator is inactive, you can vote for a proposal so that all staked tokens are accounted for. See at the end of this message if you encounter an issue.
Public validators which voted (changes in bold):
- Superbit123
World of FX Wizards 

FrenchメCore-1 

*** Nammy
**
Fox 
- DAOVerse
- ClaudioメBarros
- FxWorld
- Alif
- 212th FX Battalion
- blocktempo
- paf_yyc_ca
- SmallFort
- ContributionDAO
- LeValidateurFX
- FX FriendsX (currently inactive)
- Scissors
- Aghanism (currently inactive)
EA
31337 
- Cogni🧠
- Janc
- ByteX (currently inactive)
- ByteX No longer active (currently inactive)
- Rock
Public validators which didn’t vote yet :
- Litecoin Foundation
- European University Cyprus
- Blindgotchi
- Asosiasi Blockchain Indonesia
- Blockchain Collaborative Consortium
- nexus
- NOBI
- LuckyFX
- Scale Moment Group

Moonbase- Dapp.com
- AquillaX (currently inactive)
- dutchblue (currently inactive)
- Paper (currently inactive)
- fx-royv-validator (currently inactive)
- Crypto Kid (currently inactive)
- fx-royv (currently inactive)
For inactive validators:
Unless your validator node is out of sync, or jailed, you should be able to vote.
If that ain’t working using the usual CLI commands, that might be because your validator is out-of-sync.
In such a case, you always have the option to add the following argument at the end of your command, either :
--node https://fx-json.functionx.io:26657, (FX foundation’s TM public node) or--node https://mainnet-tm-fx.frenchxcore.eu:26657(FrenchXCore TM public node)
You can also change the node value in your$HOME/.fxcore/config/client.toml file
This allows you to use your own Linux/Windows fxcored setup but with another node !!
Decentralization is also about this ![]()
![]()
Regards,
@FrenchXCore
If I vote via the command line, it works, but it doesn’t work that way in the fx-wallet.
[Updated 05/AUG/2023 11:30AM GMT+2]
Guys,
Don’t forget to vote on proposal #40, which ends on August 8th, 2023.
After 11 days of voting, we reached 33.1% votes, all for YES, on proposal #40.
As a reminder, a quorum of 40% is required for proposal to go forward.
Please note that, even if your validator is inactive, you can vote for a proposal so that all staked tokens are accounted for. See at the end of this message if you encounter an issue.
Public validators which voted (changes in bold):
- Superbit123
World of FX Wizards 

FrenchメCore-1 

*** Nammy
**
Fox 
- DAOVerse
- ClaudioメBarros
- FxWorld
- Alif
- 212th FX Battalion
- blocktempo
- paf_yyc_ca
- SmallFort
- ContributionDAO
- LeValidateurFX
- FX FriendsX (currently inactive)
- Scissors
- Aghanism (currently inactive)
EA
31337 
- Cogni🧠
- Janc
- ByteX (currently inactive)
- ByteX No longer active (currently inactive)
- Rock
- Scissors

Moonbase- LuckyFX
Public validators which didn’t vote yet (9.37% of voting power):
- BlindGotchi : 3% → @lancelai
- nexus : 2.1 % → @nexus
- NOBI : 1.95 % → @???
- Scale Moment Group : 1.5 % → @ScaleMoment
- DApp : 0.91 % → @???
@zaccheah , @DavidK ,
(cc: @indra )
Unless the following validators vote soon enough beofre voting ends, so as to trigger threshold, I suggest the foundation lowers their foundation delegated tokens and reallocates tokens accordingly towards voting validators.
Otherwise, we’ll have to go thru another governance crisis, which would be very sad for the project after matters which were discussed right after DAOVerse’s proposal rejection.
Thanks
Regards,
@FrenchXCore
Baklava Space’s proposal #40 passed quorum this morning with the latest votes of Miami and Delhi (team validators !!)
[07/08/2023 04:06]
Validator Delhi voted YES for proposal #40
Validator Miami voted YES for proposal #40
[07/08/2023 08:54]
Proposal #40 reached 41.9 % votes (100% Yes)
Hi @JohnB !
Thanks for this preview.
It’s working almost fine.
Some improvements maybe:
- When setting “Transfer Delegated FX” to true, we can choose amongst a 10-ish validators. But I was thinking we were choosing from which validators we were re-delegating FX from (case A), and in that case, the field should be autofilled only with validators having delegations from the selected account (>0). In the case it would mean “TO” which validator we want to delegate (case B), then we said that more validators should be proposed… Hence, there’s a need to explain what this field refers to…
- When adding FX to the vault, the percentage “Vault Filled” field doesn’t get updated.
- (Case B above) The validator field could be autofilled randomly to avoid everyone delegating to the same validator by laziness…
- Fees are a bit expensive (2,36 $FX for a 10 $FX transaction)… But that’s fine since I don’t think you can optimize that.
- You should remind somewhere that there is a 0.5% fee when depositing into the vault…
- FX balance in the wallet at the top-right part of the screen doesn’t update after the deposit is made.
- Remind users how to add stFX token into f(x)Wallet ? (token address)
Anyway, good work !!
Regards
@FrenchXCore
Baklava will really bring the ecosystem TvL up, so yes to this proposal.
Just feel post launch metrics is so important, eg distribution of grant based on TvL tiers, even though the proposal has already passed I hope we can implement this.
When TvL on defilama?
We have our TVL calculated on Defillama (for Avalanche’s vault).
For FX, we will update it to Defillama soon once it is live.
Hi FX community,
Good news, our beta version is live!
We have deployed our FX Delegation vault to mainnet and want to invite everyone to test it out. Your feedbacks are welcome.
The current maximum capacity is 100,000 $FX.
Link: https://baklava.space/vaults/fxdelegate/
Test flow:
- Connect your wallet (for example, Metamask and f(x)Wallet) to the website.
- Deposit $FX to the Vault.
After you delegate FX, you will receive certain amount of stFX as shown in “My position” vault shares. - For Withdrawal, it will be similar to the undelegation process and it will take 21 days to undelegate your FX. Please refer to the vesting schedule.
- For Harvest, the FX tokens will be received instantly.
- For Transfer Delegated FX, you are required to delegated to validator nodes and transfer it to Baklava Vaults. This feature is created to help users to relegate their delegated FX to Baklava vault to enjoy the auto-compound yield.
Fee details:
Withdrawal fees : 0.5% of the withdrawal amount ; will be redelegated back to the vault
Reward fees : 5% of the yield
Compounder fees : 1% of the yield; will be rewarded to the one who initiate the compound transaction.

