Thanks for your thoughtful response. FDD in its current form has some propriety knowledge because we don’t want to explicitly show the attackers how to beat the system.
That said, we had an internal goal to become “Kerckhoff compliant” by the end of this year. We aren’t there yet. We will be there for the beta launch of the protocol.
Here is an example of the current legos application.
To address the two posts you referenced:
The first is a post on Allocationism. It is a high level idea that I was sharing with the DAO. It wasn’t a specific call to action for FDD. (Though the post did have a specific call to action of one session exploring the DAO’s movement to community led which happened the following day.)
For the second reference, yes, this is something we would like to do, but this specific suggestion is not actioned at this time. We have built out dashboards for the Fantom & Unicef round exposing data. Next we will need to take this to the next step to combine with the open source lego packages.
We have made adjustments to our team to be able to quickly build out the legos while continually increasing the bar for quality. Our focus is on adjusting to the onchain future where we no longer have the account name as a primary key. Additionally, we need to make sure the passport scoring is sufficient for use cases outside of grants like Bankless NFT drop & Snapshot voting integrations.
You can evaluate our budget requests for the past 5 seasons and the milestone reports which accompany them. I’m not aware of many items that we have promised to execute and haven’t. I do understand that it can be confusing to see many ideas floating on the forum and not knowing which are actually on our roadmap.
I’d be happy to connect to discuss further if you would like. disruptionjoe#6464 on discord