Bind a passkey session to the contract and network it may commit to

[karagozemin]

Goal

Let a passkey commit a bid only to the contract id and network stored when the passkey session was created.

Why this is High

The passkey panel, the web config, and the SDK client can each be pointed at a different contract. A session opened against testnet must not sign a mainnet commit. The binding has to be checked at submit time.

Requirements

• Record contract id, network passphrase, and account when the passkey session starts.
• Refuse a commit when any of those differ from the current SDK client.
• Surface a typed error in the panel instead of submitting.
• Keep the secret seed out of the error and out of the demo trace.

Acceptance criteria

• A matching session can commit in the fixture test.
• A swapped contract id does not submit.
• A swapped passphrase does not submit.
• The error text does not contain the fixture seed.

Pointers

• apps/web/src/components/PasskeyPanel.tsx
• apps/web/src/passkey-config.ts
• apps/web/src/lib/config.ts
• packages/sdk/src/client.ts
• packages/sdk/src/network.ts

Validation

• Web config tests and an SDK network mismatch test

Drips

• Drips Complexity: High
• Expected Drips Points: 200
• Add this issue from the Drips maintainer dashboard and set complexity to High.
• Do not apply the Stellar Wave label on GitHub. That path defaults the issue to Trivial (100 points).

[nazteeemba]

@nazteeemba has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Please assign me to this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nazteeemba to this issue.

[salem-byt]

@salem-byt has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, I can fix this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @salem-byt to this issue.

[Viccodes11]

@Viccodes11 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi maintainer, I can work on this. I've gone through it, I can get it resolved

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Viccodes11 to this issue.

[drips-wave]

Congratulations, @nazteeemba! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @nazteeemba: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@nazteeemba's PR #454 was approved and merged by @karagozemin.

🏆 @nazteeemba: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (751 total points). Track your full progress on GrantFox.

👏 Great work, @nazteeemba! Keep contributing to Sub-Rosa-Issue.