Dafny automates verification using an SMT solver. While this works well for many use cases, this automation is one source of proof brittleness. We informally call a proof brittle when it verifies on one version of Dafny but stops verifying when we make non-logical changes such as updating software versions or making changes to unrelated locations in the code. In this abstract we define a mode of use of Dafny called Dafny64 that dramatically reduces the resources needed for Dafny verification. We predict that Dafny64 will remove brittleness entirely from our projects.