[BUIDL Audition Onchain] BE-003: Wallet Signature Verification

[jedstroke]

Endpoint: POST /api/auth/verify-wallet
Description
Ensure only legitimate wallet holders register or vote.

Tasks

• Accept message & signature from frontend.
• Recover wallet from signature.
• Match with walletAddress supplied by user.
• Return success/failure.

Payload

{
  "walletAddress": "0x...",
  "message": "Sign this message to authenticate",
  "signature": "0x..."
}

Acceptance Criteria

• Signature matches wallet.
• Reusable for both performer registration and voting.

Forum
https://t.me/MusicStrk_CJ/146

[4c1d-V]

Hi @jedstroke ,

I've reviewed the current authentication flow in routes/v1/auth.ts, including the /authenticate endpoint using ec.starkCurve.Signature and provider.verifyMessageInStarknet.

I'd like to take on Issue #44 by implementing a dedicated /verify-wallet endpoint that:

• Accepts walletAddress and signature
• Validates the signature using the same logic as /authenticate
• Returns a simple success/failure response
• Does not create a user or return a JWT
• Can be reused for voting, anonymous checks, or frontend validation before registration

This keeps /authenticate as the full login flow, and /verify-wallet as a lightweight validation utility.

ETA: I estimate delivery in 12–24 hours max.

Let me know if you’d like me to proceed with this!

[4c1d-V]

Working on this one, already! Will have the PR ready in 12 hours

[CollinsC1O]

hello @4c1d-V been patiently waiting on you to make a PR as you said you were going to make one in 12 hours and this was since 30th Apr.
Can you pls respond to this and relate what your progress has been or if you encountered any challenges. pls respond as soon as you see this. Thanks

[LaGodxy]

Hi,

I’d like to contribute to implementing the /api/auth/verify-wallet endpoint.

With experience working on Web3 authentication flows and integrating Ethereum-based wallet verification in NestJS and Node.js environments, I can:

Accept the wallet address, message, and signature from the frontend,

Recover the signer’s address using ethers.js or viem,

Verify that the recovered address matches the submitted walletAddress,

Return a success or failure response based on the match,

Ensure the solution is reusable for both performer registration and voting authentication.

I can deliver this in a modular and testable way, aligned with NestJS best practices.

Let me know if you'd like me to take this on.

[jedstroke]

Hi,

I’d like to contribute to implementing the /api/auth/verify-wallet endpoint.

With experience working on Web3 authentication flows and integrating Ethereum-based wallet verification in NestJS and Node.js environments, I can:

Accept the wallet address, message, and signature from the frontend,

Recover the signer’s address using ethers.js or viem,

Verify that the recovered address matches the submitted walletAddress,

Return a success or failure response based on the match,

Ensure the solution is reusable for both performer registration and voting authentication.

I can deliver this in a modular and testable way, aligned with NestJS best practices.

Let me know if you'd like me to take this on.

This has nothing to do with Ethereum?

[jedstroke]

@LaGodxy, you're not using Ethers.js or Viem; you're using Starknet.js. Do you understand what this problem is about?