Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(init): correct web3 standard attribution and add missing ethereum provider in config.toml template

Closed Beginner friendly
  • Is something wrong?
#7,324 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@7ttp is already working on this.

Since Oct 26, 2026.

  • #7334 by @7ttp — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli, documentation

Research direction

Read the template in apps/cli/src/shared/init/project-init.templates.ts and compare it with apps/cli-go/pkg/config/templates/config.toml and the test fixture. Update the Solana attribution, add the Ethereum example, and correct “rows returns” to “rows returned” in each required copy. Done when the templates and fixture agree and the generated config shows the corrected comments and Ethereum section.

Written by the indexing model from the issue text.

Description

📘 Docs supabase/cli
Documentation link

https://github.com/supabase/cli/blob/develop/apps/cli/src/shared/init/project-init.templates.ts

Issue type

Incorrect documentation

Problem
  1. Solana Web3 Standard Misattribution:
    In apps/cli/src/shared/init/project-init.templates.ts:L342, the template generated by supabase init reads:
# Allow Solana wallet holders to sign in to your project via the Sign in with Solana (SIWS, EIP-4361) standard.
# You can configure "web3" rate limit in the [auth.rate_limit] section and set up [auth.captcha] if self-hosting.
[auth.web3.solana]
enabled = false

EIP-4361 is specifically the Ethereum Improvement Proposal for "Sign-In with Ethereum" (SIWE). Solana uses SIWS / CAIP-122, not an Ethereum EIP. Citing (SIWS, EIP-4361) for Solana is inaccurate.

Missing Ethereum Web3 Provider in Init Template: The CLI configuration schema (packages/config/src/auth/web3.ts and registry-auth.ts) supports both solana and ethereum. The container runtime also supports GOTRUE_EXTERNAL_WEB3_ETHEREUM_ENABLED, but [auth.web3.ethereum] is omitted from the config.toml init template.

Minor Grammar Typo: Line 19 of the template reads: # The maximum number of rows returns from a view, table, or stored procedure. ("returns" instead of "returned")

Suggested improvement
  1. Update the Solana comment in project-init.templates.ts to reference SIWS without EIP-4361:
# Allow Solana wallet holders to sign in to your project via the Sign in with Solana (SIWS) standard.
# You can configure "web3" rate limit in the [auth.rate_limit] section and set up [auth.captcha] if self-hosting.
[auth.web3.solana]
enabled = false
  1. Add the commented-out [auth.web3.ethereum] example:
# Allow Ethereum wallet holders to sign in to your project via the Sign-In with Ethereum (SIWE, EIP-4361) standard.
# [auth.web3.ethereum]
# enabled = false

  1. Fix the grammar typo on line 19 (rows returned from).

  2. Keep parity across project-init.templates.ts, apps/cli-go/pkg/config/templates/config.toml, and the test fixture.

Additional context

I would be happy to submit a PR for this once triaged and labeled with open-for-contribution.

Dominant language
TypeScript
Stars
2.4k
Forks
537
Avg merge
18h 2m
Merged PRs (30d)
387

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/cli

All issues in supabase/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.