Thanks for engaging directly. A few of the answers landed, a few raised follow-ups I'd still like to see resolved.
On team turnover
You said most of those listed left "before I even joined or early when I joined." You were introduced in the previous proposal as a brand-new BD hire, so that timing places the departures either inside the previous funding cycle or before the proposal that listed them was even published. Both versions are concerning in different ways. Could you confirm: of the contributors named in the previous proposal, who was actively paid during that funding year, and roughly what percentage of the 420K HBD went to contributors who have since left? "Their work is on GitHub" is fair on the technical side, but the question is the financial one.
On the 560%
"That's just how good we got" plus "old Magi ran middle of the pack on DHF efficiency" is essentially agreeing the prior cycle was not optimal use of community funds. If you have done the cross-DHF benchmarking analysis, would you publish it? That would actually be useful input to the broader DHF discussion, not just for evaluating Magi.
On Altera
Saying old Altera "didn't have any functionality that could support crosschain functionality" opens a new question. The previous proposal explicitly committed to cross-chain features. So either the team knew v1 wouldn't fit that roadmap and built it anyway, or the requirements changed mid-cycle. Which was it, and was the community informed at the time?
On the rebrand
Fair enough, accepted as answered. The only follow-up worth a line is whether there were any direct costs (domain, design, marketing assets) tied to the rebrand. Not a sticking point for me otherwise.
On AI and security
The question was sidestepped. "Nothing goes live until tested" addresses something else. The question was: roughly what percentage of recent commits involved AI-assisted code, and what does the human review process look like scaled to that volume? 's audit found three real issues in EVM bridge code, which is exactly why a clear answer here matters, rather than a deflection of the concern.
Appreciate the engagement. The unresolved pieces are worth pinning down before votes close.
RE: Magi Network DHF Proposal 2026