Instant Counter Bidding
Last updated
Last updated
Instant Counter Bidding is available to all Lifetime Holders and Subscription Members.
It does only defend bids on OpenSea.
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
CTO bids do have priority in the ICB engine
To enable a task for instant counter bidding use the following option on the task config:
Important requirements for ICB:
ICB will only counter up to your max bid price per task
Token bidding tasks will only automatically react to other token bids. However once a token bid is triggered, it will also outbid trait and collection bids
Collection / Trait offer tasks (CTO) will only automatically react to other collection offers and trait offerts
NEW FEATURE (PRO Access only!): Auto-Scaling 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.
Instant Counter Bidding uses a queue similar to Token Bidding Tasks with a speed of 1000-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:
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.
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.
Dedicated ICB wallet: When you're using the PRO Version of Butler we strongly recommend to use a dedicated Wallet just for the ICB engine when scaling it to 2-3 Slots or using Auto Scaling. The reason is to avoid Wallet based Rate Limits of OpenSea. The ICB engine can send up to 4000 bids / hour and if it's running on the same wallet as your tasks you can hit OpenSea Rate Limits resulting in a degraded bidding speed.
Ignore max active bids on CTOs: No longer supported. ICB will now automatically cancel CTO Bids if "max active bids" settings are reached on a task.
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.
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 2000 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.
