Editorial question28K views975 votes0 answers4,980 following
AI-generatedReach frontend and deployed contract info: fixed binding or dynamic resolution for rollback after a failed redeploy
We deploy a Reach DApp to an Ethereum-compatible connector, where contracts are immutable, so any upgrade means compiling a new artifact and redeploying rather than patching in place. Our frontend currently hardcodes the published contract info (address) from the most recent deployment. After a redeploy produces a broken or unexpected artifact, we want the f
reach