FEATURES
A complete overview of what Nexash does, how each feature works, and what is coming next.
WALLET
When you send /start to the Nexash bot for the first time, a wallet is created for you automatically. It is tied to your Telegram identity — no signup, no email, no seed phrase to write down.
In production, Nexash wallets will be non-custodial embedded wallets via Privy, giving users full control of their keys through the web dashboard. In the current demo, wallets are generated server-side and tied to Telegram identity.
What you can do with it
/wallet)/faucet)/pay)/kyc, /attest)Commands
/start — creates wallet on first use /wallet — shows address, HSK balance, USDC balance /faucet — funds wallet with testnet USDC
KYC AND COMPLIANCE
Nexash is a registered trusted compliance issuer on the HashKey Settlement Protocol. When a user completes KYC verification, Nexash issues a signed attests:kyc:v1 attestation and anchors it permanently on HashKey Chain mainnet via the AttestationRegistry smart contract.
This is not advisory compliance. The contract enforces it.
Commands
/kyc — issues KYC attestation for your wallet /attest 0x... — checks KYC status for any address on-chain
The attestation contains
0xf6520f2a...)Demo vs Production
HSP COMPLIANT PAYMENTS
Every payment through Nexash is a fully compliant HashKey Settlement Protocol (HSP) v1 mandate. Here is exactly what happens when you send /pay.
Command
/pay [amount] [address]
Example: /pay 10 0x1234...5678
Two independent compliance rails
Rail 1 — HSP: mandate + attestation → Coordinator verifies cryptographically → ACCEPT
Rail 2 — Contract: PayrollTreasury reads AttestationRegistry → transfer or revert
Neither rail trusts the other. Both must pass.
Step by step
Backend checks AttestationRegistry — is the payer KYC-attested? If not, payment is blocked.
Nexash issues a fresh attests:kyc:v1[level=full] attestation signed by our registered issuer key.
An HSP v1 mandate is built and signed by the payer key.
Mandate and attestation are submitted together to the HSP Coordinator.
The payer's wallet executes the on-chain ERC-20 transfer on HashKey testnet.
The Coordinator observes the settlement and verifies the attestation independently.
Nexash runs its own independent verifier and confirms ACCEPT.
The bot returns the paymentId, txHash, Blockscout link, and HSP Explorer link.
AI PAYROLL AGENT
The Nexash AI payroll agent (powered by Venice AI / GLM-5.2) understands natural language payment instructions and converts them into structured, reviewable proposals.
After parsing, the anomaly review agent checks each proposed payment against historical patterns and flags anything unusual — first-time payees, unusually large amounts, pattern deviations.
Example
Input:
Send alice 500 USDC and hold bob's 300 until his KYC renews
Output:
• alice — 500 USDC — immediate
• bob — 300 USDC — on hold (KYC renewal required)
API endpoints
POST /institutions/payroll/parse POST /institutions/payroll/review POST /institutions/payees GET /institutions/payees GET /institutions/payees/:id/history
MARKET INTELLIGENCE
Every market data point in Nexash comes directly from HashKey Exchange's public API. Indicators are computed in real-time from live OHLCV candle data.
Command
/market [pair]
Example: /market BTCUSDT
/market ETHUSDT
/market SOLUSDT
Indicators per timeframe (15m / 1h / 4h)
The AI trading agent
Applies a structured analysis — 4h for macro trend, 1h for confirmation, 15m for timing. Requires 2-of-3 timeframe confluence before proposing any position. Returns reasoning, confidence rating (low/medium/high), and a specific suggested action.
PAPER TRADING
Paper trading in Nexash uses live HashKey Exchange prices. Your portfolio persists in the database — it survives restarts and is tied to your user identity.
Commands
/trade buy [pair] [amount in USD] /trade sell [pair] [amount in USD] /portfolio Example: /trade buy BTCUSDT 100 /trade sell SOLUSDT 50
Portfolio shows
DASHBOARD
The Nexash dashboard (app.nexash.xyz) will provide a full web interface for everything the Telegram bot does, plus more. The backend API is fully built and ready. All 20 endpoints are implemented and tested. The frontend is in development.
What is coming