🕵️‍♂️Manuel Token ID Bidding

Feature Overview

• Support Magic Eden ETH & Ordinals Bidding Task

• Bidding by Token IDs on Base Chain

• Bidding by Token IDs on Blast Chain

• Bidding by Token IDs for ERC721 & ERC1155 Tokens

• Bidding on ENS Token IDs

• Excluding ownder addresses for ERC721 while bidding

• Supporting safety features like Floor Price caps & Asset Limits

Creating a Task

By clicking on the Create Manual Task Button on your token task list you'll be able to bid on any collection by copying the collection link / slug into Butler (no indexing required). You can also configure token ID ranges manually

Create a manual token bidding task

• Multiple token ids can be specified when separating them with comma ,

• The token id is always the last number on the Opensea link to an NFT. It's usually a number between 1 and 10'000 but can also be a very long number like this one: Link: https://opensea.io/assets/ethereum/0x495f947276749ce646f68ac8c248420045cb7b5e/42745998150656004690816543961586238000273307462307754421658803578179357246440 Smart contract: 0x495f947276749ce646f68ac8c248420045cb7b5e Token ID: 42745998150656004690816543961586238000273307462307754421658803578179357246440

• The "Smart contract addr" field is optional but can be used to bid on collections with shared contract address such as the OpenSea Storefront contract or Art Block collections

• Butler does also support ERC-1155 tokens for bidding

Creating a manual token bidding task for a specific ERC-1155 Token (The NFT Butler Lifetime license!)

• You can also use the #community-bot in our Discord server to /scan an entire collection and get a useful output of all token ids per traits or assets

/scan a collection

• Here you can also find some more info about the /scan output and how to deal with it: https://www.youtube.com/watch?v=CkkvwqkKelU

• And if you would like to use the search engine you can simply /add new collections on the #community-bot too.

Adding a new Collection to the Butler Search engine

ENS Token bidding

ENS Token bidding works the same as manual bidding. You'll basically have to define the token ids to bid on. However the #community-bot can help you to find those token ids with the /ens command.

• It can be used to generate token ids for nummeric ENS tokens such as 0001.eth - 1000.eth:

  

  generate ens token ids 0001.eth - 1000.eth
• ENS Token IDs can also be generated for strings such as 'casino.eth' and others (comma-separated):

generate ens Token IDs

There are two different ENS smart contracts:

    "contracts": [
        {
            "address": "0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85",
            "chain": "ethereum"
        },
        {
            "address": "0xd4416b13d2b3a9abae7acd5d6c2bbdbe25686401",
            "chain": "ethereum"
        }
    ],

• Make sure to add the right contract to your task config to make sure it will find it's bidding target. For example the 10k digit ENS club (0001.ens - 10000.ens) is hosted on 0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85

You can check the ENS Token ID by replacing the token id (and contract) on an OpenSea Link at the very end: https://opensea.io/assets/ethereum/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/<tokenid>

Example for 0001.ens below:

https://opensea.io/assets/ethereum/0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85/38764329101403256878217503524140705778209985981144907919668889447405219871633opensea.io