From 876ac2602cdf66032e9e0102028c1852a0ba9998 Mon Sep 17 00:00:00 2001
From: Bas van den Aakster <bvdaakster@gmail.com>
Date: Fri, 12 Dec 2025 21:00:11 +0100
Subject: [PATCH] Fix: Correct validateUsernameClaim function calls

The function expects 4 separate parameters, not an object.
This was causing 'Username must be a string' errors because
the entire object was being passed as the username parameter.
---
 src/rpc.ts | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/rpc.ts b/src/rpc.ts
index 805af70..b176914 100644
--- a/src/rpc.ts
+++ b/src/rpc.ts
@@ -67,12 +67,12 @@ async function verifyAuth(
     }
 
     // Validate username format before claiming
-    const validation = await validateUsernameClaim({
+    const validation = await validateUsernameClaim(
       username,
       publicKey,
       signature,
-      message,
-    });
+      message
+    );
 
     if (!validation.valid) {
       return {
@@ -159,12 +159,12 @@ const handlers: Record<string, RpcHandler> = {
     const { username, publicKey: paramPublicKey } = params;
 
     // Validate claim
-    const validation = await validateUsernameClaim({
+    const validation = await validateUsernameClaim(
       username,
-      publicKey: paramPublicKey,
+      paramPublicKey,
       signature,
-      message,
-    });
+      message
+    );
 
     if (!validation.valid) {
       throw new Error(validation.error || 'Invalid username claim');