[ojonugwa14joshua-beep]

Summary

This pull request implements the changes requested in #1170.

Changes

• contracts/invisible_wallet/src/lib.rs
• contracts/invisible_wallet/src/session_key.rs
• contracts/invisible_wallet/src/operator_refusal_tests.rs

Testing

Verified against the issue acceptance criteria.

Closes #1170

[vercel]

@ojonugwa14joshua-beep is attempting to deploy a commit to the miracle656's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

Warning

Possible malicious code: please review before merging.

An automated security scan flagged files in this pull request that appear to contain malicious code. Code like this can run automatically when a project is opened in an editor or its dependencies are installed, so it could compromise the machine of anyone who checks out this branch.

Automated scans can be wrong, so this may be a false positive. Maintainers: please review the flagged files carefully before merging, on GitHub in your browser rather than by checking out the branch. The malicious part is often hidden far off to the right of an ordinary-looking line, so scroll sideways through each file.

@ojonugwa14joshua-beep: this pull request adds or changes these files, possibly without your knowledge. Malware like this spreads by adding itself to repositories on machines it has infected, so your machine might be compromised. Please undo these changes in this pull request, and don't open or run other projects on that machine until you've checked it.

Flagged files at commit 0bf5e8d:

• .gitignore
• demo/init
• demo/package.json
• examples/agent-tip-bot/init
• examples/agent-tip-bot/package.json
• examples/angular/init
• examples/angular/package.json
• examples/astro/init
• examples/astro/package.json
• examples/astro/tailwind.config.js
• examples/capacitor/init
• examples/capacitor/package.json
• examples/discord-faucet/init
• examples/discord-faucet/package.json
• examples/electron/init
• examples/electron/package.json
• examples/expo/init
• examples/expo/package.json
• examples/nextjs/init
• examples/nextjs/package.json
• examples/nuxt/init
• examples/nuxt/package.json
• examples/payroll/init
• examples/payroll/package.json
• examples/qr-pos/init
• examples/qr-pos/package.json
• examples/remix/init
• examples/remix/package.json
• examples/solid/init
• examples/solid/package.json
• examples/subscription-paywall/init
• examples/subscription-paywall/package.json
• examples/sveltekit/init
• examples/sveltekit/package.json
• examples/tauri/init
• examples/tauri/package.json
• examples/vite-react/init
• examples/vite-react/package.json
• examples/vue/init
• examples/vue/package.json
• examples/x402-api/client/init
• examples/x402-api/client/package.json
• examples/x402-api/server/init
• examples/x402-api/server/package.json
• frontend/docs/init
• frontend/docs/package.json
• frontend/mobile/init
• frontend/mobile/package.json
• frontend/wallet/init
• frontend/wallet/package.json
• frontend/wallet/tailwind.config.js
• frontend/website/init
• frontend/website/package.json
• frontend/website/tailwind.config.js
• packages/agent/init
• packages/agent/package.json
• packages/bills/init
• packages/create-veil-app/init
• sdk/elements/init
• sdk/init
• services/spp-bootnode/init

Only merge once you're confident these files are safe.

ℹ️ Posted automatically by Drips Wave. Questions? Contact support@drips.network.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
38349992	Triggered	Generic High Entropy Secret	0bf5e8d	sdk/src/tests/allowance.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}