I’m midway through moving a FlutterFlow app from Firebase Auth to Supabase. All user rows are already in the Supabase auth table, but every login fails with crypto/bcrypt: bcrypt hashes must start with '$', but hashedSecret started with 'F' Firebase stores SCRYPT hashes, so I need a quick, reliable bridge that lets existing users sign in on Supabase with their current passwords—no reset e-mails, no friction. Where things stand • Environment: this is strictly a Bug Fix phase, not a long-term feature sprint. • Password flow today: hashes travel straight from Firebase → Supabase; no proxy service sits in between. Your task 1. Patch the import so Supabase accepts the old hashes. 2. Add a just-in-time “rehash on first login” that silently verifies against Firebase Auth, then rewrites the hash in bcrypt for Supabase. 3. Prove that a user can log in through the existing FlutterFlow screens without code changes on the front end. 4. Hand over the working code (Node or Deno preferred) plus a short setup guide I can follow to replicate in staging and production. Budget would be 2500INR. Access I’ll provide • Supabase service + anon keys • Firebase service account • Full FlutterFlow project Acceptance criteria ✓ Existing Firebase user logs in via Supabase with no password reset. ✓ Supabase now stores a valid bcrypt hash. ✓ Subsequent logins authenticate solely against Supabase. ✓ Guide reproduces the flow in under 15 minutes. Timeline: 24 hours from hire.