๐ŸŽฏCollection/Trait Bidding (CTO)

Collection Bidding Tasks

Collection Bidding Tasks are used to create automated offers on all tokens of a collection

  • Resource-friendly because 1 single offer is covering the whole collection

  • Low profit spans on most collections as it's very competitive

Available Markets & Blockchains

Trait Bidding Tasks

Collection Trait Bidding Tasks are used to create automated offers on all tokens of a specified collection trait.

  • Very profitable strategy

  • Research-intensive as profitable traits have to be identified first

  • Resource-friendly because 1 single offer is covering the whole collection

  • Low profit spans on most collections as it's very competitive

To start a Collection Trait Bidding task, you have to click on the very left icon "traits", which will open the trait overview.

Now you'll see each Trait of the collection as a dedicated box which can be used to creat Trait Bidding Tasks.

Check Token Bidding Tasks if you want to bid on collections with Trait Bidding disabled.

CTO Configuration

CTOs do have mostly the same configuration options as Token Bidding tasks. However there are some special notes below.

  • For collection tasks we recommend to always set Maximum active bids

  • Since a CTO is only processing 1 bid each time, the validity can be kept low between 10 - 15 minutes

  • Immediately start task will also play the CTO immediately after creation

  • We recommend to set the CTO interval to at least 1 - 5 min if you're running few (1-10) CTOs only

Running Tasks

After creating a Collection Trait Bidding Task, it will appear in the Collection Task menu in Butler:

  • Green border: means you're having the highest bid(s)

  • Yellow border: someone else is having the highest bid(s)

  • Red border: there's an error (shouldn't happen)

You will need to start the Collection Task Engine to start the bidding process.

It can be enabled on the Dashbord and the header of the page

It's recommended to add the NFTButler-prefix to your OpenSea Profile: see instructions.

Last updated