{"data":{"proposalCid":"QmX5c2RTKWeyzpQu3CQehgKJ2jmMPga1jU6WNzN5VVvuKy","choices":["Nay"],"remark":"Nay for a few reasons. First, as I noted on multiple past referenda, a proposal should be submitted per milestone or period, so that the community can evaluate the work before committing to further payments. Nobody in the community has the time available to track the delivery for scheduled payments, and never have I seen a cancellation of a scheduled payment. Scheduled payments provide guarantees to the proposer and nobody else. Second, I'm still not convinced that there should be an over-arching BD or sales hub/guide for teams building on Polkadot. Polkadot is an enablement layer, it is infrastructure, it is NOT a company, and it is NOT a family of companies either. Builders should get creative, imagine completely new businesses and use cases and then DISRUPT existing business structures by offering unimaginably convenient and incomparably greater products than those exist right now. If we are not able to do this, we should simply QUIT. The litmus test is very easy for whether a product/use-case is sellable or not. Present it as it is to a potential client or user as it is, I'm presuming you are a user of the product yourself, and if they are not shocked by how much greater this thing is compared to what they currently have, and if the response is not \"STFU and take my money\", then we are simply just forcing things, we should just quit and reiterate in that case. I'm really having a hard time comprehending all these organization and templatization around what should be a completely novel and creative endeavor. I'm sure the team can deliver on their promises, but sorry, I find all this very futile.","voterNetwork":"polkadot","remarkType":"markdown","version":"4","timestamp":1753253681},"address":"15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL","signature":"0xfc05784c23857fe89c88e780abda9aa139916d9c681ee7fd8cb01bd751c8400068ed930f2b1b6e3ecfded9c3abba7ba2174bfae4b679278c761236dc161c1988","version":"2"}