Setup a crowdfund to distribute NFTs representing fractionalized ownership of the goal being funded. Proceeds are able to be divided and distributed to yield vaults to assure direct delivery to the respective manufacturing / distribution / business partnerships.

Allows users to launch their own custom NFT projects.

Kernel address

A raw address (andr1....), a valid vfs path (~username/app/component), app component (./component) or ibc protocol path (ibc://cosmoshub-4/user/app/component)

Minter

Name

Owner

Symbol

Cw721

Provide the address or name of a specific Andromeda Digital Object (ADO) within an app.

Identifier Address

Input the wallet address responsible for minting tokens. Use your own wallet address if you will retain minting rights.

Minter Address

Module Details

Optionally attach Andromeda Modules such as rates or address-list to the contract.

Selected Modules

Enter the official name of the token or NFT. Use only letters for the name.

Token/NFT Name

Specify a unique symbol for the token or NFT. It should contain only letters and be 3 to 12 characters long.

Token/NFT Symbol

An ADO for initiating a token crowdfund, with a minting feature included.

Banner

Label

Tiers

Crowdfund

Enter the URL for the banner image of the campaign.

Campaign Banner URL

Enter the address of the CW20 token to be used for purchasing NFTs.

CW20 Token

Enter the native token to be used for purchasing NFTs.

Native Token

The type of funds accepted for buying NFTs.

Denom

Enter a short description about the campaign.

Campaign Description

The maximum amount of funding to be raised by the campaign.

Hard Cap (Optional)

The minimum amount of funding to be raised for the campaign to be considered successful.

Soft Cap (Optional)

Campaign Title

Enter the address of the CW721 contract whose NFTs will be sold in this campaign.

NFT Contract Address

Configure the details for your Crowdfund campaign.

Campaign Configuration

Enter the URL for the campaign's official website.

Campaign Website URL

Address

Enter an IBC address for fund recovery, if applicable.

IBC Recovery Address (Optional)

Include an optional message for the recipient.

Attached Message (Optional)

The address to receive the funds from the campaign proceeds.

Withdrawal Recipient

Tier Label

The tier level. For example, 1 for the highest tier, 2 for the second highest tier, and so on.

Tier Level

Specify a limit for the number of NFTs available for this tier.

Tier Limit (Optional)

Tier Price

Tier

Define the tiers for your campaign. For example, you could have a bronze, silver, and gold tier for your crowdfund, each having a specified price.

Create a new Crowdfund ADO to manage a token sale, allowing for multiple tiers of support.

An ADO used to split sent funds amongst two or more predefined addresses/wallets

Default recipient

Lock time

The vector of recipients for the contract. Anytime a `Send` execute message is sent the amount sent will be divided amongst these recipients depending on their assigned percentage.

Percent

Recipients

Splitter

(Optional) Recipients cannot be changed for this duration of time selected. Minimum is 1 day and Maximum is 1 year.

Lock Time

Module

A component that can be attached to ADOs (Ex. Rates)

Modules

This is ONLY ONE recipient. To add more, click '+Add Item' below.

Distribution Percentage

A list of recipients that can be changed as you build.

Crowdfund App

Publishing configurations to publish the ADO as an App

App Name

Publish as an App

The maximum amount of funding to be sold for the fundraising

The minimum amount of funding to be sold for the successful fundraising

Title of the campaign. Maximum length is 64.

An address that can be used within the Andromeda ecosystem. Inspired by the cosmwasm-std `Addr` type. https://github.com/CosmWasm/cosmwasm/blob/2a1c698520a1aacedfe3f4803b0d7d653892217a/packages/std/src/addresses.rs#L33

This address can be one of two things: 1. A valid human readable address e.g. `cosmos1...` 2. A valid Andromeda VFS path e.g. `/home/user/app/component`

VFS paths can be local in the case of an app and can be done by referencing `./component` they can also contain protocols for cross chain communication. A VFS path is usually structured as so:

`<protocol>://<chain (required if ibc used)>/<path>` or `ibc://cosmoshub-4/user/app/component`

A simple struct used for inter-contract communication. The struct can be used in two ways:

1. Simply just providing an `AndrAddr` which will treat the communication as a transfer of any related funds 2. Providing an `AndrAddr` and a `Binary` message which will be sent to the contract at the resolved address

The `Binary` message can be any message that the contract at the resolved address can handle.

Failing to meet the hard cap will result in refunds for the users.

Enter the address (e.g, andr1v...) or name of the specific ADO module (e.g, ./rates) you wish to attach.

Module Address

Indicate if the module can be modified post-deployment. Check the box for yes.

Module Mutability

Select the type of module to add. Currently compatible: 'rates','address-list'

Module Type

An optional name or tile for the module. Primarily for orginzational usage.