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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@runonflux/aa-schnorr-multisig-sdk

v1.3.0

Published

Account Abstraction Schnorr Multi-Signatures SDK

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

thetrunkthetrunkbill2bill2

Keywords

Account AbstractionAAERC-4337SchnorrSignatureMultisig

Readme

Account Abstraction Schnorr Multi Signatures SDK

A typescript library for creating ERC-4337 Account Abstraction which utilizes Schnorr Signatures for multi signatures.

About

Current library provide utilities to sign/send User Operation's with Schnorr Signer. Alchemy Account Kit used to send User Operations. To better understand usage of library go to Examples section.

⚠️ Critical Information

Public Nonces

Never reuse public nonces. Reusing them will cryptographically expose your private keys and lead to a loss of funds. Implement robust nonce management in your application is crucial for security, make sure to delete nonce after usage and never use it again.

Salts

Construction of multisignature address uses salts. Ensure salts are deterministic and consistent to maintain cross-wallet compatibility. Usage of different salts will lead to different multisignature address. Use the following salts that are used by SSP Wallet:

  • accountSalt: aasalt
  • factorySalt: aafactorysalt

📦 Installation

Install via npm:

npm install @runonflux/aa-schnorr-multisig-sdk

Or clone the repository:

git clone https://github.com/RunOnFlux/account-abstraction.git
cd account-abstraction/aa-schnorr-multisig-sdk
npm i

🛠️ Usage

To get started, explore our examples and documentation. Ensure you have a .env file configured with the necessary environment variables as shown in .env.sample.

Examples

🐛 Reporting Issues

Found a bug? Please report it on our issue tracker.

📜 License

This project is licensed under the MIT License.

🌐 Associated Packages

SSP Wallet

SSP Wallet is a multi-signature multi-asset wallet that uses this AA Schnorr Multi-Signature SDK for EVM chains. Check out the SSP Wallet repository for more information and proper usage of the library

Inspiration, Credits & Acknowledgements

Security Audits

The smart contracts and SDK underwent a comprehensive security audit by Halborn finalised in February 2025.

Audit Reports

📄 Smart Contracts Audit

📄 SDK Audit

Findings & Notes

  • Smart Contracts: All findings were in unused code, which has been removed in the main branch. Contracts were redeployed, and the main branch is recommended for production while master branch is an archive where audits were assessed and perfectly safe to continue using. (Fix PR)
  • SDK: All important findigs were addressed in the main branch. Be noted that examples are using hard coded values, furthermore this library requires proper nonce management on the client side, and following a strict error-throwing approach. (Fix PR)