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

@waves/provider-keeper

v2.0.9

Published

ProviderKeeper for Signer

Downloads

399

Readme

ProviderKeeper

npm "" "" "" ""

Overview

ProviderKeeper implements a Signature Provider for Signer protocol library.

Getting Started

Library installation

Install using npm:

npm install @waves/signer @waves/provider-keeper

or yarn

yarn add @waves/signer @waves/provider-keeper

Library initialization

Add library initialization to your app.

  • For Testnet:

    import { Signer } from '@waves/signer';
    import { ProviderKeeper } from '@waves/provider-keeper';
    
    const signer = new Signer({
      // Specify URL of the node on Testnet
      NODE_URL: 'https://nodes-testnet.wavesnodes.com',
    });
    const keeper = new ProviderKeeper();
    signer.setProvider(keeper);
  • For Mainnet:

    import { Signer } from '@waves/signer';
    import { ProviderKeeper } from '@waves/provider-keeper';
    
    const signer = new Signer();
    const keeper = new ProviderKeeper();
    signer.setProvider(keeper);

You can also check if the Keeper Wallet is installed.

import { isKeeperInstalled } from '@waves/provider-keeper';

const isInstalled = await isKeeperInstalled();

if (!isInstalled) {
  // Some logic in case KeeperWallet is not installed
}

Basic example

Now your application is ready to work with Waves Platform. Let's test it by implementing basic functionality.

For example, we could try to authenticate user and transfer funds:

const user = await signer.login();
const [transfer] = await signer
  .transfer({
    recipient: '3Myqjf1D44wR8Vko4Tr5CwSzRNo2Vg9S7u7',
    amount: 100000, // equals to 0.001 WAVES
    assetId: null, // equals to WAVES
  })
  .broadcast();

Or invoke some dApp:

const [invoke] = await signer
  .invoke({
    dApp: '3Fb641A9hWy63K18KsBJwns64McmdEATgJd',
    fee: 1000000,
    payment: [
      {
        assetId: '73pu8pHFNpj9tmWuYjqnZ962tXzJvLGX86dxjZxGYhoK',
        amount: 7,
      },
    ],
    call: {
      function: 'foo',
      args: [
        { type: 'integer', value: 1 },
        { type: 'binary', value: 'base64:AAA=' },
        { type: 'string', value: 'foo' },
      ],
    },
  })
  .broadcast();

For more examples see Signer documentation.