Thank you for the lovely summary and notes, and most of all for organizing the event, which I found personally very reinvigorating and which I’ve heard nothing but rave reviews of!
This is also a clear takeaway to me – my follow-up question would be: what structure and format would best address this need? I think an aspect that we still struggle with at the moment is that there’s a lot of design and engineering work in motion, and while most information is generally public (papers, code, forums, etc.), it isn’t organized in the right sort of way to provide more accessible onboarding.
An additional complexity is that we’re deploying Anoma in stages (e.g. first to Ethereum) and different applications (utilizing different parts of the “full Anoma design”) may depend on different deployment stages – e.g. something like Public Signal could be built on the protocol adapter, but something like TerraTwin (as I understand it) requires aspects such as the P2P system which are not finished yet.
I imagine that some combination of:
- A high-level roadmap of our planned deployment stages
- A clear introduction to “what is live right now” and what can/cannot be done with it
- A clearer support channel (for interested parties)
could be helpful? What do you think? We’re also very happy to do a Q&A but I suspect it will be most useful if we prepare some content first as there seems to be a bit of a “missing piece” here.