There was an issue where supabase self-hosted / local would say "ethereum web3 provider is not enabled"
There was no configuration line present at all in the
config.toml
config.toml
that got generated when you ran
supabase init
supabase init
at all
The issue to my understanding is that the local supabase does not create the required variable for signing in with ethereum (at all) - even if you added it in the
config.toml
config.toml
it wouldnt be added to the supabase docker variables even tho the feature is supported
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.