oSnipe
  • Overview
    • πŸ‘‹Introduction to oSnipe
      • About oSnipe
      • Sniper's Pass
      • Purveyor’s Pass
      • Observer's Pass
    • 🎯oSnipe Coverage
  • πŸ€–AutoSniper
    • Sniper Wallet Setup
  • πŸ“œcommands list
    • Sniper Commands
      • AutoSniper
        • /autosnipe
        • /snipe
        • /get-address
        • /set-address
      • oSnipe Notification Management
        • /subscribe
        • /list
        • /preferences
        • /edit
        • /delete
        • /ignore
        • /get-traits
    • Purveyor & Observer Commands
    • Full Command List
  • πŸ”—Official Links
Powered by GitBook
On this page
  1. commands list
  2. Sniper Commands
  3. AutoSniper

/snipe

The /snipe command allows users to snipe a desired NFT the instant they run it instead of waiting for a listing that fulfills the user's criteria. This uses the user's contract Ether balance and approved Wrapped Ether if available.

In the case of a Flooring Protocol listing, there will be 2000 attempts (1 attempt per block). Since failures don't cost gas, feel free to run the command again if needed.

  • contract-address

The contract address of the desired NFT.

  • token-id

The token ID of the desired NFT.

  • marketplace

The marketplace on which the NFT is listed, dropdown choice between OpenSea, LooksRare, Blur, X2Y2 and Flooring Protocol.

Please note that in the case of a Blur snipe, the fulfiller address (autosnipe.eth) must hold enough Ether to fulfill the snipe. We keep a reasonable amount of Ether in it but in case of very expensive snipes, these might fail.

  • aggression

Aggressiveness of the validator tip for the snipe.

  • max-price

The maximum price in Ether the user is willing to pay for for the snipe including gas.

  • listing-price

The price in Ether at which the desired NFT is listed at.

Eventually, it will be possible to auto-fill these parameters simply by reacting to an event in the user's private channel.

Previous/autosnipeNext/get-address

Last updated 1 year ago

πŸ“œ