1.6.0 • Published 2 years ago

massa-web3 v1.6.0

Weekly downloads
-
License
MIT
Repository
github
Last release
2 years ago

massa-web3

Web3 libraries for Massa (web3.js SDK)

Requirements

  • NodeJS 14+
  • npm / yarn (see package.json)

Package commands

  1. Run yarn install to install all deps
  2. Run yarn run build to build distribution content
  3. Run yarn run test to run integration and unit tests

Web3 Client initialization

To instantiate a web3 client, one needs to create a base account for signing and paying for transactions as well as a list of providers as shown below:

import { IAccount, IClientConfig, IProvider, ProviderType } from "massa_web3/interfaces";
import { Client } from "massa_web3/web3/Client";

const baseAccount = {
    publicKey: "2SPTTLK6Vgk5zmZEkokqC3wgpKgKpyV5Pu3uncEGawoGyd4yzC",
    privateKey: "5Jwx18K2JXacFoZcPmTWKFgdG1mSdkpBAUnwiyEqsVP9LKyNxR",
    address: "9mvJfA4761u1qT8QwSWcJ4gTDaFP5iSgjQzKMaqTbrWCFo1QM"
} as IAccount;

const providers: Array<IProvider> = [
    {
        url: "http://127.0.0.1:33035",
        type: ProviderType.PUBLIC
    } as IProvider,
    {
        url: "http://127.0.0.1:33034",
        type: ProviderType.PRIVATE
    } as IProvider
];

const web3ClientConfig = {
    providers,
    retryStrategyOn: true // activate the backoff retry strategy
    periodOffset: 3       // set an offset of a few periods (default = 5)
} as IClientConfig;

const web3Client: Client = new Client(web3ClientConfig, baseAccount);

Once there is an initialized client instance, it is straightforward to call methods on it:

import { IStatus, IAddressInfo } from "massa_web3/interfaces";

const nodeStatusResp: IStatus = await web3Client.getStatus();
const addressesResp: Array<IAddressInfo> = await web3Client
    .publicApi()
    .getAddresses(["some_address"]);

There are also convenience factories for a straightforward initialization of the client:

import {
    ClientFactory,
    Client,
    DefaultProviderUrls,
} from "massa_web3/web3/ClientFactory";

// a testnet client
const testnetClient: Client = ClientFactory.createDefaultClient(
    DefaultProviderUrls.TESTNET,
    baseAccount
);

// a custom client (see above)
const customClient: Client = ClientFactory.createCustomClient(
    providers,
    baseAccount
);

Client exposed APIs

The client exposes several APIs which could be used on its (also initialized as stand-alone) own if one needs to:

web3Client.publicApi()      -> sub-client for public api                    (interface: PublicApiClient)
web3Client.privateApi()     -> sub-client for private api                   (interface: PrivateApiClient)
web3Client.wallet()         -> sub-client for wallet-related operations     (interface: WalletClient)
web3Client.smartContracts() -> sub-client for smart contracts interaction   (interface: SmartContractsClient)

Client public API

Client public API operations are accessible under the public sub-client, which is accessible via the publicApi() method on the client.

Example:

// get block info
const blocks: Array<IBlockInfo> = await web3Client
    .publicApi()
    .getBlocks(["q2XVw4HrRfwtX8FGXak2VwtTNkBvYtLVW67s8pTCVPdEEeG6J"]);

Available methods are:

Client private API

Client private API operations are accessible under the private sub-client, which is accessible via the privateApi() method on the client.

Example:

// stop the node
await web3Client.privateApi().nodeStop();

Available methods are:

Wallet operations

Wallet operations are accessible under the wallet sub-client which is accessible via the wallet() method on the client.

Example:

// generate new wallet
const newWalletAccount = web3Client.wallet().walletGenerateNewAccount();

Available methods are:

  • walletGenerateNewAccount
    const newWalletAccount = await WalletClient.walletGenerateNewAccount();
  • walletSignMessage
    const sig = await WalletClient.walletSignMessage("hello", baseAccount);
  • addPrivateKeysToWallet
    await web3Client
        .wallet()
        .addPrivateKeysToWallet([
            "2SPTTLK6Vgk5zmZEkokqC3wgpKgKpyV5Pu3uncEGawoGyd4yzC",
        ]);
  • getWalletAccounts
    const walletAccounts = web3Client.wallet().getWalletAccounts();
  • getWalletAccountByAddress
    const walletAccount = web3Client
        .wallet()
        .getWalletAccountByAddress(
            "9mvJfA4761u1qT8QwSWcJ4gTDaFP5iSgjQzKMaqTbrWCFo1QM"
        );
  • addAccountsToWallet
    await web3Client.wallet().addAccountsToWallet([
        {
            privateKey: "2a4dobJSVb8CN7cQCEL4cfU6xsUNrtwGXQvUPqzUXhEedvzGjc",
            publicKey: "5tdoCo5TwvYZoRjnoqZHDsvff3Z9pXTP1gnEgN9FFS7WWbjjn2",
            address: "yKCRYgv5nVDVwqHmTTXXxqqZW7he3bgEDBQ5bPjBxPkuzAte2",
        },
    ]);
  • walletInfo
    const walletInfo: Array<IFullAddressInfo> = await web3Client
        .wallet()
        .walletInfo();
  • sendTransaction
    const sendTxIds = await web3Client.wallet().sendTransaction(
        {
            fee: 0, // int
            amount: "1", //MAS
            recipientAddress:
                "yKCRYgv5nVDVwqHmTTXXxqqZW7he3bgEDBQ5bPjBxPkuzAte2",
        } as ITransactionData,
        baseAccount
    );
  • buyRolls
    const buyRollsIds = await web3Client.wallet().buyRolls(
        {
            fee: 0, // int
            amount: 1, //ROLLS
        } as IRollsData,
        baseAccount
    );
  • sellRolls
    const sellRollsIds = await web3Client.wallet().sellRolls(
        {
            fee: 0, // int
            amount: 1, //ROLLS
        } as IRollsData,
        baseAccount
    );

Smart contract deployment

Once the smart contract WASM is available, it becomes quite straightforward to deploy a smart contract operation (a state changing operation):

// deploy smart contract
const opIds = await web3Client.smartContracts().deploySmartContract(
    {
        fee: 0,
        maxGas: 2000000,
        gasPrice: 0,
        coins: 0,
        contractDataBase64: compiledScFromSource.base64,
    } as IContractData,
    baseAccount
);

The compiledScFromSource is the base64 compiled smart contract code that could easily be obtained using massa's https://www.npmjs.com/package/massa-sc-utils

Smart contract event fetching

Smart contracts can emit events which the client could easily fetch via the code below. The second parameter in the call represents the refresh interval which we can set in order to poll the events

// poll smart contract events
const eventsFilter = {
    start: {
        period: 0,
        thread: 0,
    } as ISlot,
    end: {
        period: 0,
        thread: 0,
    } as ISlot,
    original_caller_address:
        "9mvJfA4761u1qT8QwSWcJ4gTDaFP5iSgjQzKMaqTbrWCFo1QM",
    original_operation_id: null,
    emitter_address: null,
} as IEventFilter;

const eventPoller = new EventPoller(
    eventsFilter,
    5000,
    web3Client.smartContracts()
);
eventPoller.startPolling();
eventPoller.on(ON_EVENT, (data: [IEvent]) =>
    console.log("EVENT(S) RECEIVED", data)
);

//...

// cleanup and finish
eventPoller.stopPolling();

Alternatively, one could make direct use of an async promise for doing the latter:

const events: Array<IEvent> = await EventPoller.getEventsAsync(
    eventsFilter,
    5000,
    web3Client.smartContracts()
);
console.log("Events", events);

The latter could easily be employed in smart contracts where we need to e.g. get the contract address. For example, this contract would emit the address at creation:

import { call, print, create_sc, generate_event } from "massa-sc-std";

export function main(_args: string): i32 {
    const sc_address = createContract();
    call(sc_address, "initialize", "", 0);
    print("Initialized, address:" + sc_address);
    generate_event(`Address:${sc_address}`); //emit an event with the address
    ...
}