NFT Butler

Instant Counter Bidding

Beta has finished: Instant Counter Bidding is now available to Lifetime Holders and Subscription Members!
Core functionality NFT Butler defends the tokens you have already bid on (and/or have planned to bid on, e.g. scheduled token tasks) by putting counterbids. It is available for:
  • Token Bidding Tasks
  • Collection Bidding Tasks
  • Trait Bidding Tasks
Auto scaling
NEW FEATURE (PRO only): Auto-Scaling --> Instant Counter Bidding will automatically re-allocate bidding power from counter bidding to token bidding tasks if there's not much competition on the tasks where you have counter bidding activated.
The basic idea behind auto-scaling: if your queue is empty, power goes to token bidding tasks. If the queue fills up, power is allocated to counter bidding.
The thresholds can be adjusted in the settings page.
Speed & Resources Instant Counter Bidding uses a queue similar to Token Bidding Tasks with a speed of 800-1200 bids/h. It also uses the same resources as a Token Bidding Tasks. So if Instant Counter Bidding is activated, a slot will automatically be blocked for Token Bidding Tasks:
Monitoring & Taking Action ❗
The Instant Counter Bidding tab is kind of a 'Control Center' to monitor your counter bidding queues. This overview is necessary to take the right actions. In this chapter we'll show a few different examples.
Example 1: "Healthy State"
This example shows a healthy scenario. The graph on the right side always shows the most resource-intensive counterbidding tasks. In this case, there were plenty of jobs created to counterbid on the "Pixels - Farm Land" Task. But the queue seems to be recovering and getting smaller again. No action required.
What to do when Instant Counter Bidding Queue grows faster than it can be processed? Recommendations/Strategies:
  • deactivate Instant Counter Bidding for super competitive Token Bidding Tasks
  • increase the bidding steps (e.g. with Smart Bidding) - don't fall into the trap of trying to counterbid every token task with 0.001 ETH - this will just waste resources
  • add more power to Instant Counter Bidding (in development, soon you will be able to scale Instant Counter Bidding to the speed of 3 token bidding tasks)
Example 2: Queue overloading
In this example multiple token bidding tasks have counter bidding activated and there is heavy competition on it. If no action is taken, the queue will grow faster than it can be processed and will reach its cap of 1000 jobs. This scenario is undesired as we want to have our counterbids being instant and not queued somewhen far in the future. We must take action: reduce the number token bidding tasks with counter bidding enabled or counterbid in higher increments (e.g. smart bidding).
While you have to be careful activating Instant Counter Bidding for Token Bidding Tasks (this can get very resource-intensive), there's no such concern for CTOs.
Additional Settings
  • Ignore max active bids on CTOs: Does what the name says. If you have this flag enabled, your settings on the CTOs will be ignored. This makes sense if you want to be competitive, but be aware of the risk: it may happen that you end up with a lot of concurrent bids. That's normally not a problem, as the bids are in your defined range, but you're more exposed to the risk of rapidly falling floor prices.
  • Show all queued jobs Shows the queues for each counter bidding task, can be toggled off if you want to save resources on your computer.
  • Use counter bid event validity By activating this, the system will always be counter bidding with the same validity as competitive bidder, while never bidding longer than what is defined in task config.
CPU load
The Instant Counter Bidding engine needs to handle all bidding events that happen on a collection (and check if the bid event must trigger a counterbid) - for some collections with a lot of bidding events this can be taxing for the CPU. One butler instance can handle about 3000 events/minute (average CPU). Normally you would not care about this information, but in cases where you're CPU is completely used up, it's worth to investigate if the ICB engine is the source of the problem. In that case, you can mitigate the problem by reducing the amount of collections with a lot of bidding events.
Counterbidding Mechanism explained: