@6529-collections/allowlist-lib

v0.0.137

Published

3 days ago

Build reproducible NFT allowlists and distribution plans with the Janus operation DSL.

0High
0Medium
0Low

simo6529

gelatogenesis

allowlist nft ethereum distribution janus

Allowlist Lib

Build reproducible NFT allowlists and distribution plans using Janus operations. The library runs in Node.js and includes TypeScript declarations.

Install

npm install @6529-collections/allowlist-lib

Requires Node.js 18 or newer. Use a maintained Node.js LTS release for new applications. The package uses CommonJS, supports named imports from Node.js ES modules, and uses Node's filesystem APIs for its default storage.

Quick start

const {
  AllowlistCreator,
  AllowlistOperationCode,
} = require('@6529-collections/allowlist-lib');

async function main() {
  const creator = AllowlistCreator.getInstance({
    alchemyApiKey: process.env.ALCHEMY_API_KEY || 'offline-example',
    etherscanApiKey: process.env.ETHERSCAN_API_KEY || '',
    seizeApiPath: '',
  });

  const state = await creator.execute([
    {
      code: AllowlistOperationCode.CREATE_ALLOWLIST,
      params: {
        id: 'example-allowlist',
        name: 'Example allowlist',
        description: 'An empty distribution plan ready for more operations.',
      },
    },
  ]);

  console.log(state.allowlist);
}

main().catch(console.error);

This example creates an empty plan without making API requests. The factory requires an Alchemy key or SDK instance even for local operations, so this example supplies an offline placeholder. Use a real key for operations that fetch blockchain data. The default storage creates a transfers-data/ directory in the current working directory.

The package also includes the runnable example:

node node_modules/@6529-collections/allowlist-lib/examples/basic.cjs

For TypeScript or ES modules, use:

import {
  AllowlistCreator,
  AllowlistOperationCode,
  type AllowlistCreatorConfig,
  type AllowlistOperation,
  type AllowlistState,
} from '@6529-collections/allowlist-lib';

Existing subpath imports, such as @6529-collections/allowlist-lib/allowlist/allowlist-creator, remain available.

Configuration

| Option | Purpose | | --- | --- | | alchemyApiKey / alchemy | Supply an Alchemy API key or an AlchemyClient implementation, including an existing Alchemy SDK v2 instance. The default client uses Ethereum mainnet. | | etherscanApiKey | API key for operations that read Etherscan data; use an empty string for local-only operations. | | seizeApiPath | Seize API base URL for TDH, consolidation, delegation, and other Seize-backed operations. Use an empty string when those operations are not needed. | | seizeApiKey | Optional authentication key for the configured Seize API. | | storage | Implement StorageImplementations to supply transfer and token-pool storage, or use LocalFileSystemStorageImplementations to configure the transfer directory. | | loggerFactory | Optional LoggerFactory; defaults to console logging. | | onBeforeOperation / onAfterOperation | Optional synchronous or asynchronous callbacks around each operation. | | ofacCheckEnabled | Token-pool sanctions screening, enabled by default. |

API credentials belong in the consuming application's configuration. API availability and access requirements depend on the operations you execute. Operations execute in order and the first must be CREATE_ALLOWLIST.

The default client calls Alchemy's NFT API directly and uses ethers v6 for ENS lookups. It preserves the v2 NFT endpoint used for historical ownership snapshots. The library does not depend on the archived Alchemy SDK. Applications that inject their own SDK instance continue to own that instance's dependencies.

Historical owner token IDs accept decimal strings and explicitly 0x-prefixed hexadecimal strings. Both normalize to exact decimal uint256 IDs without using JavaScript numbers. Malformed or out-of-range IDs fail instead of being silently reinterpreted or truncated.

Development and release

npm ci
npm run audit
npm test -- --runInBand
npm run test:package

test:package builds and packs the library, checks the file list, installs the tarball into a temporary project, audits its runtime dependencies, runs the example, and checks CommonJS, ES module, TypeScript, and existing subpath imports. It needs network access to install public dependencies, but no blockchain API keys. The separate legacy E2E suite currently contains only skipped tests.

npm run build cleans dist/ and compiles runtime sources and declarations. npm pack and npm publish run that build automatically through prepack. Published files contain compiled JavaScript, declarations, this README, the MIT license, and the example. Tests, fixtures, source maps, and local files are excluded.

Releases use the manually triggered Publish to npm GitHub Actions workflow in .github/workflows/publish.yml. To release:

Merge the changes you want to release into main.
In GitHub, open Actions → Publish to npm → Run workflow and select main.
Choose patch (the default), minor, or major, and run the workflow.

The workflow starts from the selected main commit and updates package.json and package-lock.json automatically. From 0.0.135, patch produces 0.0.136, minor produces 0.1.0, and major produces 1.0.0. It installs dependencies, audits them, runs tests, and verifies the package. Only after those checks pass does it commit and push the version to main, then publish that version to npm. Releases are serialized. If main advances before preparation or during validation, the release stops before publishing instead of overwriting changes. Start a new workflow run to release the updated main.

If publishing fails after the version commit, use Re-run failed jobs on the same workflow run. The run ID recorded in the commit lets the retry reuse its version and source. A retry skips publishing if that version is already on npm, and refuses to publish an unpublished version superseded by a newer release. Starting a new workflow run requests a new version increment.

Authentication uses npm trusted publishing with GitHub OIDC. The package's npm trusted publisher must match organization 6529-Collections, repository allowlist-lib, and workflow filename publish.yml, with direct npm publish permission enabled and no environment restriction. The workflow uses a GitHub-hosted runner, Node 24, and npm 11. No npm token secret or interactive login is needed in CI. Its GITHUB_TOKEN needs contents: write and permission to push to main. GitHub does not start another push-triggered CI run for commits made with GITHUB_TOKEN, so the release workflow runs the checks itself. See GitHub's workflow trigger documentation and the npm trusted publishing documentation.

For a local release, sign into an npm account with access to the 6529-collections organization, choose and commit a new version yourself, and run sh publish.sh. The script runs the release checks but does not bump the version automatically.

Publishing the library does not update existing applications. Consumers moving from GitHub Packages must update their registry configuration and lockfile after the new version is available. In particular, a scope mapping such as @6529-collections:registry=https://npm.pkg.github.com/ still directs installs to GitHub Packages even when the default registry is npm.

License

MIT.

Operation reference

Introduction to Janus: The Embedded DSL for NFT Distribution Plans
- What is a DSL?
- Introducing Janus Operations
  - Why Operations?
  - Utilizing Janus Operations

Introduction to Janus: The Embedded DSL for NFT Distribution Plans

Welcome to the official documentation for Janus, an innovative embedded Domain Specific Language (DSL) designed exclusively for creating robust and versatile NFT (Non-Fungible Token) distribution plans. Embedded seamlessly within the JavaScript ecosystem, Janus provides developers intuitive approach to create distribution strategies.

What is a DSL?

A Domain Specific Language (DSL) is a specialized computer language crafted for a specific application domain. Unlike general-purpose languages, which are designed to solve a wide range of problems, DSLs are tailored to a particular set of tasks, offering optimized solutions for those specific scenarios. This focused nature of DSLs often results in more concise, readable, and expressive code for the given domain, making them a preferred choice for industries and sectors that require specialized computational tasks.

Introducing Janus Operations

In the vast landscape of NFT distribution, the dynamic capabilities of Janus come to life through its operations. These are the core constructs that enable developers to define, refine, and execute their distribution plans. But what exactly are Janus operations, and why are they paramount to the Janus experience?

Why Operations?

At the heart of any system, operations dictate how actions are carried out, how data flows, and how outcomes are produced. For NFT distribution, this means determining who gets what, when, and under which conditions. Without operations, we would merely have a static representation of data, devoid of any actionable insights or systematic procedures.

Utilizing Janus Operations

As we delve deeper into this documentation, you'll encounter a range of operations, each with its unique purpose and functionality. They become the building blocks, the nuts and bolts, of your distribution plan. By understanding and harnessing these operations, you are able to create any distribution plan

CREATE_ALLOWLIST Operation

Overview

The CREATE_ALLOWLIST operation serves as the foundational stone for curating allowlists within the Janus NFT distribution system. Similar to the main function in numerous programming languages, this operation not only kickstarts the allowlist creation but also ensures that a structured, identifiable, and descriptive scaffold is in place for subsequent operations.

Parameters

id (String):
- Description: A unique identifier for the allowlist.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system.
name (String):
- Description: A user-friendly name for the allowlist to provide an easily recognizable label.
- Requirements:
  - Must be a valid string.
description (String):
- Description: A detailed description providing context, use-case, or any pertinent information regarding the allowlist.
- Requirements:
  - Must be a valid string.

GET_COLLECTION_TRANSFERS Operation

Overview

The GET_COLLECTION_TRANSFERS operation is fetching a list of NFT transfers (transfer pool) associated with a specified contract. This operation downloads transfers up to a provided block number.

Parameters

id (String):
- Description: A unique identifier for the downloaded transfers.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system.
name (String):
- Description: A descriptive name for the transfers pool, aiding quick identification.
- Requirements:
  - Must be a valid string.
description (String):
- Description: A detailed description providing context, use-case, or any pertinent information regarding the transfer pool.
- Requirements:
  - Must be a valid string.
contract (String):
- Description: The specific contract's address whose NFT transfers you aim to fetch.
- Requirements:
  - Must be a valid ERC721/ERC1155 contract address
blockNo (Number):
- Description: The block number up to which the NFT transfers should be fetched.
- Requirements:
  - Must be a valid numerical value.
  - Represents the upper limit, ensuring that transfers are only retrieved up to this specific block.

TRANSFER_POOL_CONSOLIDATE_WALLETS Operation

Overview

The TRANSFER_POOL_CONSOLIDATE_WALLETS operation is employed for consolidating wallets by leveraging the delegation tool's consolidations as captured in a specified snapshot block.

Parameters

transferPoolId (String)
- Description: The unique identifier of the transfer pool that will undergo wallet consolidation.
- Requirements:
  - Must be a valid string, corresponding to an existing transfer pool in the Janus system.
consolidationBlockNumber (Number)
- Description: The block number that will serve as the snapshot for the consolidation process.
- Requirements:
  - Must be a positive integer.
  - Should reference a valid block number in the blockchain.

CREATE_TOKEN_POOL Operation

Overview

The CREATE_TOKEN_POOL operation offers a structured approach to curate a dedicated pool of NFT tokens. This tool provides the flexibility to consolidate wallet holdings, focus on specific token IDs, and define a specific blockchain depth, encapsulated by the block number.

Parameters

id (String)
- Description: A unique identifier for the token pool.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system.
name (String)
- Description: A user-friendly name for the token pool.
- Requirements:
  - Must be a valid string.
  - Offers a brief insight into the token pool's purpose or nature.
description (String)
- Description: Context or supplementary information about the token pool.
- Requirements:
  - Must be a valid string.
  - Encapsulates the essence of the token pool for enhanced clarity.
contract (String)
- Description: The contract address from which the NFT tokens are sourced.
- Requirements:
  - Must be a valid contract address.
  - Pertains to the NFTs in question.
blockNo (Number)
- Description: The block number serving as the upper limit for fetching data.
- Requirements:
  - Must be a valid number.
  - Defines the range of the blockchain data to be considered.
consolidateWallets (Boolean)
- Description: Determines whether to consolidate tokens from different wallets into a unified view.
- Requirements:
  - Must be true or false.
  - Streamlines the token pool by merging fragmented holdings.
tokenIds (String, Optional)
- Description: Specific token IDs to be considered for the pool.
- Requirements:
  - Comma-separated string of token IDs (example: 1,2,3,4-10,12)
  - If provided, only these specific tokens are curated into the pool.

TOKEN_POOL_CONSOLIDATE_WALLETS Operation

Overview

The TOKEN_POOL_CONSOLIDATE_WALLETS operation streamlines the wallets within a token pool using the advanced mechanisms of the delegation tool's consolidations, anchored at a specified snapshot block.

Parameters

tokenPoolId (String)
- Description: The unique identifier for the token pool slated for wallet consolidation.
- Requirements:
  - Must be a valid string, matching an existing token pool within the Janus system.
consolidationBlockNumber (Number)
- Description: The specific block number that will act as the reference snapshot during the consolidation process.
- Requirements:
  - Must be a positive integer.
  - Should correlate to a legitimate block number on the blockchain.

CREATE_CUSTOM_TOKEN_POOL Operation

Overview

The CREATE_CUSTOM_TOKEN_POOL operation empowers users to curate a personalized pool of NFT tokens based on specific input criteria. Unlike the standard token pool, this custom operation allows for a more granular approach, where the emphasis is on explicit token owners and optional token IDs. In the absence of provided IDs, Janus takes the initiative, sequentially assigning IDs in the order of their listing: 1, 2, 3, and so forth.

Parameters

id (String)
- Description: A unique identifier for the custom token pool.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system.
name (String)
- Description: A concise name representing the essence of the custom token pool.
- Requirements:
  - Must be a valid string.
  - Captures the purpose or nature of the custom token pool.
description (String)
- Description: Elaborate details or context about the custom token pool.
- Requirements:
  - Must be a valid string.
  - Should encapsulate the nuances of the token pool's creation or intent.
tokens (Array of Objects)
- Description: An array detailing each token's ownership and optional ID.
- Object Structure:
  - owner (String):
    - Description: The address representing the owner of a particular token.
    - Requirements:
      - Must be a valid wallet address.
  - id (String, Optional):
    - Description: A unique identifier for the token.
    - Requirements:
      - Must be a valid string if provided.
      - In the absence of an ID, Janus will automatically assign an ID based on the token's order: 1, 2, 3, etc.

CREATE_WALLET_POOL Operation

Overview

The CREATE_WALLET_POOL operation is designed to curate and consolidate a specific set of wallet addresses. By centralizing these addresses into a pool, users can conveniently manage and reference them for subsequent modifications or operations within the Janus ecosystem.

Parameters

id (String)
- Description: A unique identifier for the wallet pool.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system to ensure distinct identification of this pool.
name (String)
- Description: A descriptive name for the wallet pool that briefly captures its intent or content.
- Requirements:
  - Must be a valid string.
description (String)
- Description: Detailed context about the purpose, origin, or nuances of the wallet pool.
- Requirements:
  - Must be a valid string.
wallets (Array of Strings)
- Description: A collection of wallet addresses intended for inclusion in the pool.
- Requirements:
  - An array of valid wallet addresses.
  - Each wallet address should be unique within the array.

ADD_PHASE Operation

Overview

The ADD_PHASE operation introduces a structured phase or stage within distribution plan.

Parameters

id (String)
- Description: A unique identifier for the phase.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system to ensure distinct identification of this phase.
name (String)
- Description: A concise name representing the essence or primary focus of the phase.
- Requirements:
  - Must be a valid string.
description (String)
- Description: Detailed context providing insights, objectives, or nuances associated with the phase.
- Requirements:
  - Must be a valid string.

ADD_COMPONENT Operation

Overview

The ADD_COMPONENT operation allowing users to create distinct components, or snapshot groups, within a defined phase.

Parameters

id (String)
- Description: A unique identifier for the component.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system to ensure distinct identification of this component.
name (String)
- Description: A representative name that conveys the primary purpose or nature of the component.
- Requirements:
  - Must be a valid string.
description (String)
- Description: An elaborate narrative that offers insights into the objectives, nuances, or relevance of the component.
- Requirements:
  - Must be a valid string.
phaseId (String)
- Description: The unique identifier of the phase under which the component is to be nested.
- Requirements:
  - Must be a valid string, corresponding to an existing phase within the system.

ADD_ITEM Operation

Overview

The ADD_ITEM operation allows users to integrate specific snapshot or token pools directly into a designated component.

Parameters

id (String)
- Description: A unique identifier for the item.
- Requirements:
  - Must be a valid string.
  - Must be unique across the system to ensure distinct identification of this item.
name (String)
- Description: A title that succinctly captures the essence of the item.
- Requirements:
  - Must be a valid string.
description (String)
- Description: Detailed context shedding light on the importance, role, or specifics of the item.
- Requirements:
  - Must be a valid string.
componentId (String)
- Description: The unique identifier for the component where the item is intended to be nested.
- Requirements:
  - Must be a valid string, corresponding to an existing component within the system.
poolType (String)
- Description: Specifies the type of pool being added, allowing for distinction between standard and custom token pools.
- Accepted Values:
  - 'TOKEN_POOL'
  - 'CUSTOM_TOKEN_POOL'
poolId (String)
- Description: A unique identifier for the specific snapshot or token pool being integrated into the component.
- Requirements:
  - Must be a valid string, representing a pre-existing pool in the system.

Building Blocks of the Distribution Plan

The aforementioned operations serve as the foundational building blocks for crafting a precise and efficient NFT distribution plan. They allow for the definition and organization of pivotal snapshots and the overarching structure, encapsulated within distinct phases. By utilizing these operations, users can shape the blueprint of their distribution plan with accuracy and foresight.

Modifying the Distribution Plan State

While the initial operations provide structure and content, subsequent operations empower users to modify and fine-tune the state of their distribution plan.

ITEM_EXCLUDE_TOKEN_IDS Operation

Overview

The ITEM_EXCLUDE_TOKEN_IDS operation introduces a dynamic filtering mechanism within the Janus system. With this operation, users can selectively remove specific tokens from an item based on their token IDs. This becomes especially valuable when certain tokens within an item need to be excluded due to varied reasons, such as changes in strategy, exclusivity criteria, or data refinement.

Parameters

itemId (String)
- Description: The unique identifier of the item from which tokens are to be excluded.
- Requirements:
  - Must be a valid string, pointing to an existing item in the system.
tokenIds (String)
- Description: A delimited string indicating which token IDs should be excluded from the item.
- Format: Token IDs are represented as comma-separated values, with the ability to denote ranges using hyphens. E.g., "1,2,3,4-10,12" represents individual tokens with IDs 1, 2, 3, 12 and a range from 4 to 10.
- Requirements:
  - Must adhere to the defined format.

ITEM_SELECT_TOKEN_IDS Operation

Overview

The ITEM_SELECT_TOKEN_IDS operation provides an inverse functionality to its exclusion counterpart. By using this operation, users can explicitly specify which tokens they wish to retain within an item based on their token IDs. This allows for a targeted approach, ensuring that only the most relevant or desired tokens remain a part of the item, thereby streamlining the content to match strategic needs or criteria.

Parameters

itemId (String)
- Description: The unique identifier of the item where tokens are to be selectively retained.
- Requirements:
  - Must be a valid string, referencing an existing item in the system.
tokenIds (String)
- Description: A delimited string indicating which token IDs should be kept within the item.
- Format: Token IDs are expressed as comma-separated values, with ranges signified using hyphens. E.g., "1,2,3,4-10,12" denotes individual tokens with IDs 1, 2, 3, 12 and a range from 4 to 10.
- Requirements:
  - Must conform to the prescribed format.

ITEM_SORT_WALLETS_BY_TOTAL_TOKENS_COUNT Operation

Overview

The ITEM_SORT_WALLETS_BY_TOTAL_TOKENS_COUNT operation introduces a mechanism to organize tokens within an item based on the cumulative count of tokens associated with each owner or wallet. By doing so, it facilitates an ordered perspective, making it easier for users to identify and engage with wallets based on their token abundance within a specific item.

Parameters

itemId (String)
- Description: The unique identifier of the item whose tokens are to be sorted.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.

ITEM_SORT_WALLETS_BY_UNIQUE_TOKENS_COUNT Operation

Overview

The ITEM_SORT_WALLETS_BY_UNIQUE_TOKENS_COUNT operation is designed to arrange tokens within an item based on the unique count of tokens owned by each wallet. This sorting method emphasizes the diversity of token ownership, allowing users to prioritize and engage with wallets that possess a varied set of unique tokens within the specified item.

Parameters

itemId (String)
- Description: The unique identifier of the item to be sorted.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.

ITEM_SORT_WALLETS_BY_MEMES_TDH Operation

Overview

The ITEM_SORT_WALLETS_BY_MEMES_TDH operation streamlines tokens within an item based on the MEMES TDH (Total Days Held)* score of each wallet. By leveraging the TDH snapshot at a specified block number, this operation allows users to organize and prioritize wallets based on their TDH score within the MEMES ecosystem.

Parameters

itemId (String)
- Description: The unique identifier of the item that requires sorting.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
tdhBlockNumber (Number)
- Description: The specific block number indicating which TDH snapshot to utilize for sorting.
- Requirements:
  - Must be a valid block number.

* TDH (Total Days Held) is a custom metric used within The Memes project to identify long-term collectors of the Memes. TDH version 1.1 is currently being used by Janus. More info at https://seize.io/community-metrics

ITEM_REMOVE_FIRST_N_TOKENS Operation

Overview

The ITEM_REMOVE_FIRST_N_TOKENS operation provides users with a mechanism to remove a specified number of tokens from the beginning of an item's token list.

Parameters

itemId (String)
- Description: The unique identifier of the item from which tokens will be removed.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: Specifies the number of tokens to be removed from the beginning of the item.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of tokens in the specified item.

ITEM_REMOVE_LAST_N_TOKENS Operation

Overview

The ITEM_REMOVE_LAST_N_TOKENS operation offers a straightforward method for users to eliminate a defined number of tokens from the end of a specific item's token list.

Parameters

itemId (String)
- Description: The unique identifier of the item from which the tokens will be subtracted.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: Denotes the number of tokens to be purged from the end of the item.
- Requirements:
  - Must be a positive integer.
  - Should not surpass the total count of tokens present in the denoted item.

ITEM_SELECT_FIRST_N_TOKENS Operation

Overview

The ITEM_SELECT_FIRST_N_TOKENS operation allows users to refine an item's token list by retaining only the first "N" tokens and discarding the rest.

Parameters

itemId (String)
- Description: The unique identifier of the item to be refined.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: The number of tokens to be retained from the beginning of the item.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of tokens in the specified item.

ITEM_SELECT_LAST_N_TOKENS Operation

Overview

The ITEM_SELECT_LAST_N_TOKENS operation equips users with the ability to retain only the last "N" tokens from an item's list, discarding all preceding tokens.

Parameters

itemId (String)
- Description: The unique identifier of the item to be adjusted.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: The number of tokens to be retained from the end of the item.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of tokens in the chosen item.

ITEM_REMOVE_FIRST_N_WALLETS Operation

Overview

The ITEM_REMOVE_FIRST_N_WALLETS operation provides a way for users to trim their item's wallet list by removing the first "N" wallets.

Parameters

itemId (String)
- Description: The unique identifier of the item whose wallets are to be modified.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: The number of wallets to be removed from the beginning of the item.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of wallets in the specified item.

ITEM_SELECT_FIRST_N_WALLETS Operation

Overview

The ITEM_SELECT_FIRST_N_WALLETS operation empowers users to curate an item's wallet list by preserving only the first "N" wallets and discarding all that follow.

Parameters

itemId (String)
- Description: The unique identifier of the item to be curated.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
count (Number)
- Description: The number of wallets to be kept from the start of the item.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of wallets in the designated item.

ITEM_REMOVE_WALLETS_FROM_CERTAIN_COMPONENTS Operation

Overview

The ITEM_REMOVE_WALLETS_FROM_CERTAIN_COMPONENTS operation lets users refine an item's token list by excluding wallets that have already been given spots from specific components.

Parameters

itemId (String)
- Description: The unique identifier of the item that needs refinement.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
componentIds (String Array)
- Description: An array of component IDs which are used to identify wallets that have already been allocated spots.
- Requirements:
  - Each component ID in the array should be a valid string, referencing existing components within Janus.

ITEM_REMOVE_WALLETS_FROM_CERTAIN_TOKEN_POOLS Operation

Overview

The ITEM_REMOVE_WALLETS_FROM_CERTAIN_TOKEN_POOLS operation allows users to refine an item's token list by excluding wallets that are associated with the specified token pools.

Parameters

itemId (String)
- Description: The unique identifier of the item that needs refinement.
- Requirements:
  - Must be a valid string, referencing an existing item in the Janus system.
pools (Object Array)
- Description: An array of pools from which wallets will be removed. Each pool object contains:
  - poolType (String)
    - Description: Specifies the type of the pool.
    - Valid Values:
      - TOKEN_POOL
      - CUSTOM_TOKEN_POOL
      - WALLET_POOL
  - poolId (String)
    - Description: The unique identifier for the token or wallet pool.
    - Requirements:
      - Must be a valid string, referencing an existing pool within Janus.

COMPONENT_SELECT_RANDOM_WALLETS Operation

Overview

The COMPONENT_SELECT_RANDOM_WALLETS operation offers a method to diversify and inject an element of randomness into your NFT distribution plans. By targeting a specific component, users can select a random set of wallets from the combined pool of all wallets in the component's items. Only the selected wallets are retained, and all others are excluded, ensuring that a randomized subset of wallets is prioritized for distribution.

Parameters

componentId (String)
- Description: The unique identifier of the component that's the subject of random wallet selection.
- Requirements:
  - Must be a valid string, referencing an existing component in the Janus system.
count (Number)
- Description: The number of random wallets to be selected and retained from the component's aggregate wallet list.
- Requirements:
  - Must be a positive integer.
  - Should not exceed the total number of unique wallets across all items in the specified component.
seed (String)
- Description: A seed value to initialize the randomization process, ensuring consistent and replicable results across multiple runs.
- Requirements:
  - Must be a valid string.

COMPONENT_SELECT_RANDOM_PERCENTAGE_WALLETS Operation

Overview

The COMPONENT_SELECT_RANDOM_PERCENTAGE_WALLETS operation provides users with a method to select a random subset of wallets based on a percentage of the total wallets within a given component's items.

Parameters

componentId (String)
- Description: The unique identifier of the component undergoing random wallet selection.
- Requirements:
  - Must be a valid string, referencing an existing component in the Janus system.
percentage (Number)
- Description: Specifies the percentage of total wallets that should be randomly selected and retained.
- Requirements:
  - Must be a positive integer or floating-point number between 0 and 100 (inclusive).
  - Represents the desired percentage ratio of the total wallets to be selected.
seed (String)
- Description: A seed value utilized to initiate the randomization mechanism, assuring reproducible and consistent outcomes across multiple executions.
- Requirements:
  - Must be a valid string.

COMPONENT_ADD_SPOTS_TO_ALL_ITEM_WALLETS Operation

Overview

The COMPONENT_ADD_SPOTS_TO_ALL_ITEM_WALLETS operation enhances the adaptability of NFT distribution strategies by allowing users to allocate a specific number of spots to every wallet within a given component's items. This operation simplifies the process of ensuring each wallet receives a predetermined number of spots, thereby maintaining an even distribution mechanism within the component.

Parameters

componentId (String)
- Description: The unique identifier of the component where spots will be added to all item wallets.
- Requirements:
  - Must be a valid string, referencing an existing component in the Janus system.
spots (Number)
- Description: The number of spots to be assigned to each wallet across all items within the specified component.
- Requirements:
  - Must be a positive integer.

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

Allowlist Lib

Install

Quick start

Configuration

Development and release

License

Operation reference

Introduction to Janus: The Embedded DSL for NFT Distribution Plans

What is a DSL?

Introducing Janus Operations

Why Operations?

Utilizing Janus Operations

CREATE_ALLOWLIST Operation

Overview

Parameters

GET_COLLECTION_TRANSFERS Operation

Overview

Parameters

TRANSFER_POOL_CONSOLIDATE_WALLETS Operation

Overview

Parameters

CREATE_TOKEN_POOL Operation

Overview

Parameters

TOKEN_POOL_CONSOLIDATE_WALLETS Operation

Overview

Parameters

CREATE_CUSTOM_TOKEN_POOL Operation

Overview

Parameters

CREATE_WALLET_POOL Operation

Overview

Parameters

ADD_PHASE Operation

Overview

Parameters

ADD_COMPONENT Operation

Overview

Parameters

ADD_ITEM Operation

Overview

Parameters

Building Blocks of the Distribution Plan

Modifying the Distribution Plan State

ITEM_EXCLUDE_TOKEN_IDS Operation

Overview

Parameters

ITEM_SELECT_TOKEN_IDS Operation

Overview

Parameters

ITEM_SORT_WALLETS_BY_TOTAL_TOKENS_COUNT Operation

Overview

Parameters

ITEM_SORT_WALLETS_BY_UNIQUE_TOKENS_COUNT Operation

Overview

Parameters

ITEM_SORT_WALLETS_BY_MEMES_TDH Operation

Overview

Parameters

ITEM_REMOVE_FIRST_N_TOKENS Operation

Overview

Parameters

ITEM_REMOVE_LAST_N_TOKENS Operation

Overview

Parameters

ITEM_SELECT_FIRST_N_TOKENS Operation

Overview

Parameters

ITEM_SELECT_LAST_N_TOKENS Operation

Overview

Parameters

ITEM_REMOVE_FIRST_N_WALLETS Operation

Overview

Parameters