npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@reclaimprotocol/reclaim-client-sdk

v0.0.12

Published

Reclaim client SDK

Downloads

47

Readme

Reclaim Client SDK

Introduction

Reclaim Client SDK enables you to request proofs for data owned by your user in the web2 world. Under the hood, it uses Reclaim Protocol to generate the proofs. For more details on the working of Reclaim Protocol, visit https://docs.reclaimprotocol.org

Getting started

  1. Install the SDK:

    npm i @reclaimprotocol/reclaim-client-sdk
  2. Import the SDK into your frontend code:

    import ReclaimSDK from '@reclaimprotocol/reclaim-client-sdk'
  3. Initialize the SDK with your Reclaim application ID:

    const reclaimSDK = new ReclaimSDK(<YOUR_RECLAIM_APP_ID>)

    Make sure to replace <YOUR_RECLAIM_APP_ID> with the actual application ID obtained from the Reclaim Developer Portal (https://dev.reclaimprotocol.org).

  4. Generate a session for a user to submit proofs:

    const userId = '<USER_ID>' // Replace with the user's ID
    const session = await reclaimSDK.generateSession(userId)

    The generateSession method returns an object with the following properties:

    • status: The status of the session generation, either "success" or "failed".
    • sessionId: The ID of the generated session. Store this value for later use.
    • link: The submission link that can be displayed to the user as a QR code or a clickable link.
    • onSubmission: A promise that resolves when the user submits the proofs.
  5. Handle the session and proof submission:

    // Display the verification link to the user, e.g., as a QR code
    if (session.link) {
        // Display the link or QR code
    }
    
    // Check if proof has been submitted
    try {
    	const submissionData = await session?.onSubmission
    	if(submissionData?.isProofSubmitted) {
    		// Handle successful proof submission
    	}
    } catch(e) {
        // Handle submission timeout or error
    }    

    The onSubmission promise polls the session status until the proofs are submitted or a timeout occurs (default timeout is 5 minutes).

  6. Retrieve proofs submitted for a session:

    const sessionId = '<SESSION_ID>'; // Replace with the session ID
    const proofs = await reclaimSDK.getProofs(sessionId);

    The getProofs method returns an object with the following properties:

    • status: The status of the proof retrieval, either "success" or "failed".
    • proofs: An array of proof objects submitted for the session.