Hi all,
Great to see the work around the wallet overview in WP4. Super useful to have this visible within the consortium.
One thing we’re noticing across the ecosystem: multiple initiatives (including LSPs like WE BUILD Consortium) are creating their own wallet lists. Logical in context, but it does make wallets harder to discover outside a specific project.
Within the FIDES Community, we’re building an open Wallet Catalog (https://fides.community/ecosystem-explorer/personal-wallets/ and https://fides.community/ecosystem-explorer/organizational-wallets/) that aims to bring these things together in one place. Still self-declared, still maintained by the providers themselves, but easier to find and reuse across initiatives.
We’re also planning to include the "WE BUILD profile" as an interop profile in that context.
(https://fides.community/community-tools/interop-profiles/)
Would it make sense to connect the WP4 list to that broader catalog?
Not to replace anything, just to avoid duplication and improve discoverability. For example:
- wallets listed here could also be referenced or synced
- we can add a simple “WE BUILD” filter/tag
- and include any LSP-specific data points (e.g. conformance)
Happy to explore a lightweight way to do this together!
Curious how you see this.
Victor
FIDES Community
https://fides.community
Hi all,
Great to see the work around the wallet overview in WP4. Super useful to have this visible within the consortium.
One thing we’re noticing across the ecosystem: multiple initiatives (including LSPs like WE BUILD Consortium) are creating their own wallet lists. Logical in context, but it does make wallets harder to discover outside a specific project.
Within the FIDES Community, we’re building an open Wallet Catalog (https://fides.community/ecosystem-explorer/personal-wallets/ and https://fides.community/ecosystem-explorer/organizational-wallets/) that aims to bring these things together in one place. Still self-declared, still maintained by the providers themselves, but easier to find and reuse across initiatives.
We’re also planning to include the "WE BUILD profile" as an interop profile in that context.
(https://fides.community/community-tools/interop-profiles/)
Would it make sense to connect the WP4 list to that broader catalog?
Not to replace anything, just to avoid duplication and improve discoverability. For example:
Happy to explore a lightweight way to do this together!
Curious how you see this.
Victor
FIDES Community
https://fides.community