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.exchange/provider-cloud

v1.2.0

Published

ProviderCloud for Signer

Downloads

357

Readme

provider-cloud

Signer waves.exchange cloud auth provider ​

Overview

​ ProviderCloud developed by Waves.Exchange implements a Signature Provider for Signer protocol library. Signer enables easy deploy dApps based on Waves blockchain. User's private key and SEED phrase are encrypted and stored in Waves.Exchange, so your web app does not have access to them. ​

For now, signing is implemented for all types of transactions except exchange transactions. ​

Getting Started

1. Library installation

​ To install Signer and ProviderCloud libraries use ​

npm i @waves/signer @waves.exchange/provider-cloud

​ For Windows, use the following format:

npm i @waves/signer '@waves.exchange/provider-cloud'

​ ​

2. Library initialization

​ Add library initialization to your app. ​

  • For Testnet: ​
    import Signer from '@waves/signer';
    import { ProviderCloud } from '@waves.exchange/provider-cloud';
    
    const signer = new Signer({
      // Specify URL of the node on Testnet
      NODE_URL: 'https://nodes-testnet.wavesnodes.com'
    });
    signer.setProvider(new ProviderCloud('https://testnet.wx.network/signer-cloud'));

  • For Mainnet: ​
    import Signer from '@waves/signer';
    import { ProviderCloud } from '@waves.exchange/provider-cloud';
    
    const signer = new Signer();
    signer.setProvider(new ProviderCloud());

  • For tetsnetwxnetwork env: ​
    import { ProviderCloud } from '@waves.exchange/provider-cloud';
    
    const provider = new ProviderCloud('https://testnet.wx.network/signer-cloud?env=testnetwxnetwork');

3. 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, get his/her balances and transfer funds. ​

const user = await signer.login();
const balances = await signer.getBalance();
const [broadcastedTransfer] = await signer
  .transfer({amount: 100000000, recipient: 'alias:T:merry'}) // Transfer 1 WAVES to alias merry
  .broadcast(); // Promise will resolved after user sign and node response
​
const [signedTransfer] = await signer
  .transfer({amount: 100000000, recipient: 'alias:T:merry'}) // Transfer 1 WAVES to alias merry
  .sign(); // Promise will resolved after user sign