A quick update on my position as this thread has evolved. My initial concern was around systemic security risk, which the scope revision from runtime dependency to vendored harness meaningfully addressed.
My second concern was team accountability, specifically whether the named members were identifiable and verifiable beyond a single GitHub account. I did some due diligence on my own, including reaching out to several team members directly, and I’m comfortable with where that sits now.
What I’m still not convinced on is return on investment, and @Curia has been asking the right question in a couple of posts now. Is Relay integration actually a bottleneck builders are hitting in practice, or is demand being inferred? The proposal still carries no LOIs, no survey data, and no specific team that has said they’re blocked today. At $9,660 for the build plus $1,800 for six months of maintenance, this is a meaningful slice of treasury that would need to displace other projects competing for the same pool.
@DappsoverApps, before this goes back to a vote, can the team share any concrete signals from Rootstock builders that Relay setup and CI is a real friction point worth solving now? Conversations with two or three teams that would commit to using the kit would be important.