open-index/open-npm huggingface dataset:
npm package: @laborx/actions-tracking-artifacts
Description: Provides compiled smart contracts' artifacts of `@laborx/actions-tracking-contracts` contracts.
Latest version: 1.0.1

# Actions Tracking artifacts

Provides compiled smart contracts' artifacts of `@laborx/actions-tracking-contracts` contracts.

## Usage

They could be used to deploy\verify different smart contracts without need to compile them.

Use `@truffle-types/dep-contracts` package to fetch compiled artifacts into `build/contracts` directory.
npm package: @laborx/airdrop-artifacts
Description: Provides compiled smart contracts' artifacts of `@laborx/airdrop-contracts` contracts.
Latest version: 1.0.1

# Airdrop artifacts

Provides compiled smart contracts' artifacts of `@laborx/airdrop-contracts` contracts.

## Usage

They could be used to deploy\verify different smart contracts without need to compile them.

Use `@truffle-types/dep-contracts` package to fetch compiled artifacts into `build/contracts` directory.
npm package: @laborx/hunter-airdrop-addresses
Description: Contains addresses of deployed contracts in format of json file.
Latest version: 1.1.0

# Hunter airdrop addresses

Contains addresses of deployed contracts in format of json file.

## Structure

The next keys are the keys of deployed smart contracts:

- `HNTR` - Hunter Token
- `HunterTokenAirdrop` - Hunter Token airdrop contract
- `ScopedAirdropLib` - multi-airdrop library contract
- `ScopedAirdropBackendProvider` - multi-airdrop provider contract
- `DefaultScopedAirdrop` - default multi-airdrop contract

## More info

More about structure of `deployed-addresses.json` you could find in `@truffle-types/address-saver` package
npm package: @laborx/lx-core-addresses
Description: Provides addresses for deployed smart contracts in different networks and build environments.
Latest version: 2.0.0

# LaborX v2: deployed addresses

Provides addresses for deployed smart contracts in different networks and build environments.

## Install

```bash
npm install -D @laborx/lx-core-addresses
```

## Available addresses

There are 3 different build environments that are applicable for current deployed addresses:

- `dev` - `deployed-addresses-dev.json`, only development smart contracts, mostly deployed to testnets (like rinkeby, ropsten, kovan)
- `beta` -  `deployed-addresses-beta.json`, deployed smart contracts that are available for beta testers and could be placed in mainnet or testnet
- `production` - `deployed-addresses.json`, smart contracts that most likely was deployed to mainnet



## Usage

By default `production` smart contract addresses are exported, but you could also access others by specifying exact file path, for example for `beta`

```javascript
const deployedAddresses = require(`@laborx/lx-core-addresses/deployed-addresses-beta.json`)
```

## Additional info

See more in `@laborx/lx-core-migrations`. There are helper functions that could manage different build environment loading (`getDeployedArtifactsPath(buildEnv)`, `getDeployedArtifactsPathFromNodeEnv()`).
npm package: @laborx/sidechain-addresses
Description: Provides addresses for deployed smart contracts in different networks and build environments.
Latest version: 1.1.0

# LaborX Sidechain v2: deployed addresses

Provides addresses for deployed smart contracts in different networks and build environments.

## Install

```bash
npm install -D @laborx/sidechain-addresses
```

## Available addresses

There are 3 different build environments that are applicable for current deployed addresses:

- `dev` - `deployed-addresses-dev.json`, only development smart contracts, mostly deployed to testnets (like rinkeby, ropsten, kovan)
- `beta` - `deployed-addresses-beta.json`, deployed smart contracts that are available for beta testers and could be placed in mainnet or testnet
- `production` - `deployed-addresses.json`, smart contracts that most likely was deployed to mainnet

## Usage

By default `production` smart contract addresses are exported, but you could also access others by specifying exact file path, for example for `beta`

```javascript
const deployedAddresses = require(`@laborx/sidechain-addresses/deployed-addresses-beta.json`);
```

## Additional info

See more in `@laborx/sidechain-migrations`. There are helper functions that could manage different build environment loading (`getDeployedArtifactsPath(buildEnv)`, `getDeployedArtifactsPathFromNodeEnv()`).
npm package: @laborx/token-bridge-mainnet-addresses
Description: Provides addresses for deployed smart contracts in different networks and build environments.
Latest version: 0.1.1

# LaborX Token Bridge (Mainnet): deployed addresses

Provides addresses for deployed smart contracts in different networks and build environments.

## Install

```bash
npm install -D @laborx/token-bridge-mainnet-addresses
```

## Available addresses

There are 3 different build environments that are applicable for current deployed addresses:

- `dev` - `deployed-addresses-dev.json`, only development smart contracts, mostly deployed to testnets (like rinkeby, ropsten, kovan)
- `beta` - `deployed-addresses-beta.json`, deployed smart contracts that are available for beta testers and could be placed in mainnet or testnet
- `production` - `deployed-addresses.json`, smart contracts that most likely was deployed to mainnet

## Usage

By default `production` smart contract addresses are exported, but you could also access others by specifying exact file path, for example for `beta`

```javascript
const deployedAddresses = require(`@laborx/token-bridge-mainnet-addresses/deployed-addresses-beta.json`);
```

## Additional info

See more in `@laborx/token-bridge-mainnet-migrations`. There are helper functions that could manage different build environment loading (`getDeployedArtifactsPath(buildEnv)`, `getDeployedArtifactsPathFromNodeEnv()`).
npm package: @laborx/token-bridge-sidechain-addresses
Description: Provides addresses for deployed smart contracts in different networks and build environments.
Latest version: 0.1.1

# LaborX Token Bridge (Sidechain): deployed addresses

Provides addresses for deployed smart contracts in different networks and build environments.

## Install

```bash
npm install -D @laborx/token-bridge-sidechain-addresses
```

## Available addresses

There are 3 different build environments that are applicable for current deployed addresses:

- `dev` - `deployed-addresses-dev.json`, only development smart contracts, mostly deployed to testnets (like rinkeby, ropsten, kovan)
- `beta` - `deployed-addresses-beta.json`, deployed smart contracts that are available for beta testers and could be placed in mainnet or testnet
- `production` - `deployed-addresses.json`, smart contracts that most likely was deployed to mainnet

## Usage

By default `production` smart contract addresses are exported, but you could also access others by specifying exact file path, for example for `beta`

```javascript
const deployedAddresses = require(`@laborx/token-bridge-sidechain-addresses/deployed-addresses-beta.json`);
```

## Additional info

See more in `@laborx/token-bridge-sidechain-migrations`. There are helper functions that could manage different build environment loading (`getDeployedArtifactsPath(buildEnv)`, `getDeployedArtifactsPathFromNodeEnv()`).