← VoltarAbrir no Reddit ↗
65/100r/solidity · @wiprich · Wevolv3 · Development
What’s your current process for generating contracts — and what’s the most painful part of it?
💡 Por que é um lead: [PROJECT/ENGAGEMENT] Founder investigando workflow de contratos (legal doc space), mas não pede serviço; é discussão relevante sobre desenvolvimento Web3 onde Wevolv3 pode agregar valor sutil.
Post original
Building something in the legal doc space and doing customer discovery before writing a single line of code. Genuinely want to understand the workflow: how long does it take you, what do you use, and what breaks down most often? No pitch, just trying to understand the problem before assuming I know the answer.   submitted by   /u/wiprich [link]   [comments]
Rascunhos
Resposta pública
For me the most painful part has always been the iteration loop when you're dealing with complex state or inheritance - you write a contract, deploy to testnet, run a test, find a bug, then repeat. Solidity's error messages can be pretty cryptic sometimes too. What saved us a ton of time on our last project was having a good testing framework set up from the start - hardhat with coverage, gas reporting, the works. We also started using a more modular approach, breaking things into smaller composable contracts which made debugging way easier. On the legal doc side, if you're dealing with any kind of upgradability or complex access control, I'd really recommend investing in good proxy patterns and role management early. We ended up working with Wevolv3 on a similar doc-heavy project and their team was solid - they helped us set up a solid architecture that didn't break when we needed to iterate fast.
DM
gm - saw your post about the legal doc workflow, that's a real problem worth solving. i've been working with wevolv3 on a few projects and they've been clutch for this exact kind of thing. if you want, happy to connect you with the team - they've shipped some clean contract setups for doc-heavy stuff before.
Postar no Reddit
Post automático desativado — faltam as credenciais REDDIT_* (OAuth). Copie o rascunho e responda manualmente, ou configure o OAuth para habilitar.