Wiskers Documentation
  • Overview
  • System Architecture
    • Backend
    • Action System
    • TradingView Integration
    • Interaction with Gelato Network
    • Interaction with Moralis Streams
    • Trade Process
    • Security Measures
  • User Setup Guide
    • Precautions
    • 1. Connect your web3.0 wallet
    • 2. Select network and route
    • 3. Enter the assets being traded
    • 4. Click 'Generate'
    • 5. Copy your generated webhook
    • 6. Go to the alert set up for your trade, then click 'Notifications'
    • 7. Paste webhook in TradingView and create your alert
    • 8. View Your Created 'Action'
    • 9. Connect your telegram to receive notifications
  • Contract Triggers
    • Transfer
    • Swap
    • Ownership Transfer
    • Approval
    • Liquidity Burn
    • Mint Event
  • Continuous Actions
    • Enable this action to be 'Continuous'
    • Set Run Limit
  • Public SDK
    • SDK Implementation Guide
  • Referrals
    • Setting up your Referral Link
  • Tokenomics
    • Staking
    • Fees
    • Token Tax
    • Governance
    • Presale
  • Roadmap
  • Contract Addresses
  • Official Links
Powered by GitBook
On this page
  1. System Architecture

Action System

Each trade (or interaction) is called an action in the Wiskers ecosystem*. If desired by the user, Wiskers allows the creation of a unique webhook for every action.

When creating an action the user is required to sign the hash of the action payload, after which the signature is saved in the Wiskers database with the payload. Upon execution request, Wiskers bundles the signature together with the payload as well as the simulation results and executes it using Wiskers’ contracts.

*Currently, Wiskers is configured to execute actions solely based on TradingView alerts (more on this in the TradingView Integration section).

PreviousBackendNextTradingView Integration

Last updated 1 year ago