Nostr Wallet Connect Docs
  • Introduction
    • Welcome to NWC
    • Introduction to NWC
  • What to Build
  • FAQ
  • Bitcoin apps and websites
    • Benefits and Features
    • Getting Started
    • Code Examples
    • Connecting To The Wallet
      • Traditional Connection Flow
      • 1-Click Wallet Connections
    • SDKs and Tools
    • Best Practices
  • Bitcoin Lightning wallets
    • Benefits and Features
    • Getting Started
    • Code Examples
    • NWC Relay
    • References & SDKs
    • Best Practices
  • Reference API
    • Overview
      • get_info
      • get_balance
      • make_invoice
      • pay_invoice
      • multi_pay_invoice
      • pay_keysend
      • lookup_invoice
      • list_transactions
    • Error Codes
  • Contribute
    • Specification
    • Design Assets
Powered by GitBook
On this page
  • Set budgets
  • Unique Keys
  • Sub-wallets
  1. Bitcoin Lightning wallets

Best Practices

Follow this page to learn about best practices as a wallet service developer

PreviousReferences & SDKsNextOverview

Last updated 1 month ago

Configure permissions

Wallets should support the ability to configure connections directly from the wallet service (e.g. Alby Hub allows you to define permissions such read account balance and make payments)

Set budgets

Users are going to link their wallet account to apps to send and receive payments natively in apps. Enabling your users to set budgets creates an efficient safety measure to not overspend.

Unique Keys

Use unique wallet keys for each connection. This keeps your user's activity across different apps completely separate.

Sub-wallets

Sub-wallets allow your users to completely isolate their activity, so that apps can only see and access data and funds for that specific app.

Manage access permissions example from Alby Hub
Manage budgets example from Alby Hub