Manual Token ID Bidding
Last updated
Last updated
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
Multiple token ids can be specified when separating them with comma ,
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
It can be used to generate token ids for nummeric ENS tokens such as 0001.eth - 1000.eth:
ENS Token IDs can also be generated for strings such as 'casino.eth' and others (comma-separated):
There are two different ENS smart contracts:
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: Smart contract: 0x495f947276749ce646f68ac8c248420045cb7b5e Token ID: 42745998150656004690816543961586238000273307462307754421658803578179357246440
You can also use the in our Discord server to an entire collection and get a useful output of all token ids per traits or assets
Here you can also find some more info about the output and how to deal with it:
And if you would like to use the search engine you can simply new collections on the #community-bot too.
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 command.
Make sure to add the right contract to your task config to make sure it will find it's bidding target. The current implementation of our will let you choose if you want to generate token ids for the ERC721 contract or the ERC1155 Contract version.
