Lighthouse
  • 👋Introduction
  • Quick Start
  • How To
    • 🔑Create an API Key
    • 🔼Upload Data
      • 📁File
      • 🔤Text/JSON
      • 🔀Buffer
    • 🔒Upload Encrypted Data
      • 📁File
      • 🔤Text/JSON
      • 🔐Encryption Authentication
        • 📝Method 1: Signed Message
        • ⚕️Method 2: JWT
        • 📲Method 3: Passkey
    • Encryption Features
      • 👯Share File
      • ❌Revoke Access
      • 🔑Check Access Conditions
      • 🚪Token Gating
      • Chains Supported
      • 📃Access Control Conditions
      • 🔓Decrypt File
        • 🌐Browser Decrypt File
        • 💻NodeJS Decrypt File
      • 🚪Access control with zkTLS
      • 👬Account Delegation Tutorial
    • 📂List Files
    • 💁File Info
    • 💰Get Balance
    • 🔁Retrieve File
    • 💾Check for Filecoin Deals
    • 🔄IPNS - Handle Mutable Data
    • 📦Migrate Files
    • 📌Pin CID
    • 💸Pay per use
    • Resize Image
    • 💻Use CLI Tools
  • zkTLS
  • 🤝Account Delegation
  • 💾Filecoin First
    • Usage
    • 💰Pay Per Deal
  • Tutorials
    • 💸Pay to View Application
    • Use Python SDK
    • 📝Update Content with Lighthouse IPNS
    • 📹Add Video Player in UI
    • ✅Document Verification with PoDSI
    • 🎨Minting NFTs on EVM Chains
    • 🪙Minting NFTs on Solana
    • 👩‍💻Programmable Storage with Lighthouse SDK and Filecoin
    • 🔐Secure File Sharing
    • Upload Encrypted Files
    • 📄Token Gating and Custom Contract
    • 🔑Token Gating NFTs
    • 🏖️Pushing File Metadata Onchain
    • Use Radix Wallet on Lighthouse Filesdapp
  • Concepts
    • Glossary
    • IPFS CID Transition to v1
  • Support
    • 📞Contact
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. How To
  2. Upload Encrypted Data
  3. Encryption Authentication

Method 1: Signed Message

Authentication via Signed Message

This endpoint allows for the retrieval of a message that users can sign to prove their ownership of a specific wallet address.


Endpoint:

https://encryption.lighthouse.storage/api/message/<walletAddress>

Method:

GET

URL Parameters:

  • wallet Address: The specific wallet address for which the user wants to prove ownership.


Success Response:

Code: 200 OK

Content:

[
  {
    "message": "<Message to sign>"
  }
]

Error Responses:

Code: 400 Bad Request

Content:

{
  "message": "Invalid address"
}

Notes & Usage:

  • The user should sign the provided message using their private key related to the wallet address in question. This signed message can then be used to verify the user's ownership of that specific wallet address.

  • The system might send multiple identical messages for redundancy and verification purposes.

  • Messages can be signed using both Ethereum-compatible wallets and Solana wallets.


Always handle the message securely and avoid exposing your private keys during the signing process.


PreviousEncryption AuthenticationNextMethod 2: JWT

Last updated 1 year ago

Was this helpful?

🔒
🔐
📝