You could do it with a single Durable Object, and then proxy incoming messages from one to the other
You could do it with a single Durable Object, and then proxy incoming messages from one to the other
wrangler.toml to your repos? I mean, is it okay/secure to have those bindings ids there? Or is there a way we can set the binding ids from environment variables (could be better IMO)?wrangler secret put, or something like the secrets option with wrangler-action#2977253

its easiest to get on workers but also interestingly there was some conversation on some laravel thing about how its better than argon2 but I dont know anything about passwords to know whats better really 
To summarize, even some of the PHC judges acknowledge that, in order to achieve auth speeds in alignment with UX tolerance studies (500ms to 1 second of auth delay per user), both the Argon2 family and scrypt have to be tuned "downward" so much that they end up being less resistant to offline attack than bcrypt at equivalent auth speeds(!)
wrangler secret putsecretswrangler-action#2977253