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

@zkp2p/reclaim-witness-sdk

v0.0.2-rc5

Published

The witness server securely intermediates internet data exchange, using TLS and zero-knowledge proofs to verify and sign user claims with minimal information disclosure.

Downloads

95

Readme

Reclaim Attestor Core

Test status Deploy status

What is the Reclaim Protocol?

Reclaim enables you to bring user activity, reputation, and identity from external websites into your own platform.

For example,

  • Import the number of rides the user has taken on Uber to build a competing ride sharing platform
  • Import the users purchasing preferences using Amazon to provide discounts to the right users
  • Enable economics on a blockchain using users offchain activity data
  • Use national IDs to perform KYC

And many more...

Now what is this repository?

The attestor-core package is the core implementation of the Reclaim protocol.

TLDR: An "attestor" is a server that sits between the reclaim user & the internet. The client sends data to the internet via the attestor. All this data is exchanged securely via the TLS protocol.

We leverage some special properties of the TLS protocol along with zero-knowledge proofs to reveal only the necessary information to the attestor. The attestor then signs this data & sends it back to the client. The client can then use this signed data to prove the claim to anyone.

This package contains both the client & server side code for the Reclaim protocol.

Read a longer brief here.

This repository contains Typescript implementation of the attestor server & the SDK to interact with it. The SDK is compatible with the browser & NodeJS. However, to run the SDK on React Native/Mobile, refer to our React Native guide.

Note: if you're looking to build apps on Reclaim, we'd recommend you to use the Reclaim SDK instead. This repository is intended for developers looking to contribute to the core protocol.

Install

From GitHub: npm install git+https://github.com/reclaimprotocol/attestor-core

From NPM: npm install @reclaimprotocol/attestor-core

Note: if you plan on running the package on NodeJS or any non-browser environment, download the ZK files required to generate & verify ZK proofs:

npm run download:zk-files

Note: this approach is only advised for NodeJS projects or projects meant to run directly in a modern browser. For React Native or any solution running in a mobile app, refer to our doc here.

Note for devs: the "prepare" script which is run after npm install is configured to only build when there are files in the src directory. This is to prevent errors when building the Docker image.

Getting Started

We'd recommend you go through our documentation in the following order:

  1. Problem Statement: Understand the problem we're solving & whether this is the right solution for you.
  2. Getting Started: Understand how to get started with the attestor SDK & create your first claim.
  3. Browser RPC/React Native: How to setup the attestor client SDK for environments like React Native or any other mobile app.
  4. Provider: What is a provider in the Reclaim context, how to create one & details on the HTTP provider.
  5. Internals of Claim Creation: In-depth description of the full flow of creating a claim with a attestor.
  6. Working with the Codebase: Understand how to work with the codebase & how to deploy an attestor server.
  7. Run your own Attestor Server: Understand how to run your own attestor server locally or deploy it to the cloud.
  8. AVS: Understand how we use an Eigen AVS to decentralize the attestor server.

Contributing to Our Project

We're excited that you're interested in contributing to our project! Before you get started, please take a moment to review the following guidelines.

Code of Conduct

Please read and follow our Code of Conduct to ensure a positive and inclusive environment for all contributors.

Security

If you discover any security-related issues, please refer to our Security Policy for information on how to responsibly disclose vulnerabilities.

Contributor License Agreement

Before contributing to this project, please read and sign our Contributor License Agreement (CLA).

Indie Hackers

For Indie Hackers: Check out our guidelines and potential grant opportunities

License

This project is licensed under a AGPL v3. By contributing to this project, you agree that your contributions will be licensed under its terms.

Thank you for your contributions!