Smart contracts are what make TxID Support different from a generic chatbot. When you add your contracts, the AI can read live on-chain data, answering questions like 'is my token locked?', 'when does my vesting cliff end?', and 'what's my pending staking reward?' with real blockchain data rather than approximations.
What the AI can do with contracts
- Look up token lock amounts and expiry dates (Team Finance, Unicrypt, UNCX, custom lock contracts)
- Read vesting schedules and calculate what's currently claimable
- Check staking positions, reward rates, and pending rewards
- Query LP lock durations and unlock conditions
- Call any public read (view/pure) function defined in the contract ABI
Adding a contract
Go to Smart Contracts
Click Smart Contracts in the dashboard sidebar.
Enter the contract address
Paste the full checksum address (0x...) of the deployed contract.
Select the chain
Choose the chain this contract is deployed on. The AI only queries it on that specific chain.
Paste the ABI
Paste the contract ABI as JSON. The ABI tells the AI what functions are available and how to call them. You can usually find the ABI on Etherscan, BaseScan, or the contract's verified source code page.
Add a descriptive name
Label the contract clearly (e.g. 'Team Finance Lock Contract') so the AI understands its purpose when deciding whether to query it.
Common contract types
Token lock contracts
Team Finance, Unicrypt/UNCX, or custom lock contracts. The AI looks up lock amounts, expiry timestamps, and owner addresses.
Vesting contracts
Linear or cliff vesting. The AI reads each beneficiary's schedule, cliff date, and claimable amount.
Staking pools
Single-asset or LP staking. The AI reports staked balances, pending rewards, and any lock periods.
Token contracts
ERC-20 contracts. The AI can look up balances, allowances, and basic token info for a connected wallet.
Read-only
The AI only calls read (view/pure) functions. It never initiates write transactions or requests wallet signatures. No user funds can be moved by the widget under any circumstances.
Trim the ABI
You don't need to provide the full ABI if it's very large. A filtered ABI containing only the relevant read functions works equally well and keeps the AI's reasoning context cleaner.