/autosnipe

The /autosnipe add command enables AutoSniper on the associated subscription, while /autosnipe delete will disable it. Auto-snipes include a miner tip and bot tip as gas costs are covered by AutoSniper. Said tips are automatically calculated, so no need to whip out those old TI-89s from high school. Users can choose between three aggression levels for any given subscription, which in case of a sought after listing, maximizes their chances at a successful snipe.

Please note that only subscriptions with a max_price are accepted by /autosnipe add.

/autosnipe delete accepts batching via commas (1, 7, 8) and via ranges (1-5).

For Flooring Protocol auto-snipes, there will be a total of 400 attempts (200 times for 2 blocks). If the snipe has failed and users still want to snipe, the /snipe command will have to be used.

/autosnipe add example for subscription #375 with a persistence of 5 snipes and aggressive gas
  • subscription-numbers

The subscription number of the chosen subscription(s) to delete/attach AutoSniper to, simply separate by a comma to add multiple.

  • persistence

Users can configure the AutoSniper's persistence level based on their preferences. The [AGGRESSIVENESS] and [PERSISTENCE] tags will automatically be removed after successfully sniping the specified number of NFTs, while the listing subscription will remain.

Auto-snipe example for 10KTF listings under Ξ0.05 with aggressive gas and a persistency of 3 successful snipes
  • aggression

Users can choose between 3 aggression levels: - normal: Submits the snipe with a validator tip of 0.005 Ether. - aggressive: Calculates the validator tip based on the difference between the listing price and max_price, the larger the difference the more aggressive the validator tip. - hyper-aggressive: Automatically fills the delta between listing price and max_price regardless of the listing price.

No matter what aggression level was chosen, snipers will never pay more than the set maximum price for a snipe.

Last updated