Start in 4 commands

Getting Started

Step 1 — Open the bot

Search @nexash_horizon_bot on Telegram or tap the link: t.me/nexash_horizon_bot

Step 2 — Create your wallet

Send /start. A wallet is created for you instantly.

/start

Step 3 — Get testnet funds

/faucet

Your wallet receives testnet USDC from the HSP faucet automatically.

Step 4 — Verify KYC

/kyc

A KYC attestation is issued and anchored on HashKey Chain mainnet. Required before sending any compliant payment.

Step 5 — Send a payment

/pay 10 0xRecipientAddress

That is it. Nexash handles the rest — compliance check, HSP mandate, on-chain transfer, and verification.

All commands

Command Reference

Command	Description
/start	Create your wallet and get started
/wallet	Show your address, HSK balance, and USDC balance
/faucet	Fund your wallet with testnet USDC
/kyc	Issue a KYC attestation on HashKey Chain mainnet
/pay [amount] [address]	Send a compliant HSP payment
/market [pair]	Live market data + AI multi-timeframe analysis
/trade buy [pair] [USD]	Paper trade — buy with real prices
/trade sell [pair] [USD]	Paper trade — sell with real prices
/portfolio	Your paper portfolio with live P&L
/attest [address]	Check KYC status for any address on-chain
/link	Connect your Telegram account to the web dashboard

Contract reference

Smart Contracts

AttestationRegistry

Address:  0x093393dB86DCFAe9565dbD9Fa03332D5CB3b6362
Network:  HashKey Chain Mainnet
chainId:  177
Explorer: hsk.blockscout.com/address/0x0933...

Key functions

isIssuer(address issuer) → bool
isValid(address subject, bytes32 capability) → bool
recordAttestation(address subject, bytes32 capability, ...) → void

PayrollTreasury

Address:  0x06D99B9232056034B218bCDe88753820bCdF6AC4
Network:  HashKey Chain Mainnet
chainId:  177
Explorer: hsk.blockscout.com/address/0x06D9...

Key functions

releasePayment(address payee, uint256 amount, address token) → void
addPayee(string identifier, address payeeAddress, Policy policy) → void

Registered Issuer

Address:     0xb625c4699784c6bEDabB6A83005981a7c14186D3
IssuerKeyId: 0xf6520f2a7b8e4e844f55cc8da9d56ab5745e853b...
HSP families: attests:kyc:v1, attests:sanctions:v1

How Nexash uses HSP

HSP Integration

Nexash is registered as a trusted compliance issuer on the HashKey Settlement Protocol sandbox. Here is how the integration works.

Capability IDs

attests:kyc:v1[level=full] role-wrapped (mandate):
0xe176eab87495d286f7e5298e98297365377824ec...

attests:kyc:v1[level=full] base (attestation):
0x232e9f37db21a178d9598188ea9294473f2f8897...

KYC schema ID:
0xedc9e4b795c2d81b19fe5080310f148e7f853b18...

HSP Coordinator (sandbox)

URL:   https://hsp-hackathon.hashkeymerchant.com
Chain: hashkey-testnet (chainId 133)
USDC:  0x8FE3cB719Ee4410E236Cd6b72ab1fCDC06eF53c6

Proven compliant payment

paymentId: 0xaddf28bcff42219b1dbaebfc1578aadc671b5ee4...
Verdict:   ACCEPT
Issuer:    Nexash (0xb625c469...)

Backend API

API Reference

Base URL: https://api.nexash.xyz (coming soon — currently on EC2)

Protected endpoints require header:

X-Nexash-Operator-Key: <operator key>

Attestations

POST /attestations/issue-kyc
Body: { subject, reportTxHash, taskId, templateId }
→ { hspAttestation, hspLevel, onChainTxHash }

GET  /attestations/:subject
→ { hasAttestation, attestation: { kycLevel, isValid, expiresAt } }

Payments

POST /payments/release
Body: { payeeIdentifier, token, amount, requiredCapabilities }
→ { paymentId, status, decision }

GET  /payments/:paymentId
→ { paymentId, status, mandate, receipts, lastDecision }

Payroll

POST /institutions/payroll/parse
Body: { instruction }
→ { proposedPayments, unresolvedReferences }

POST /institutions/payroll/review
Body: { proposedPayments }
→ { flags, summary, advisoryOnly: true }

Trading

POST /trading/ask
Body: { userId, question, pairs }
→ { reasoning, confidence, proposedAction, portfolio }

GET  /trading/:userId/portfolio
→ { portfolio, unrealizedPnl, totalPnl }

How it all fits together

Architecture

┌─────────────────────────────────────────┐
│           Telegram Bot                  │
│  /start /wallet /faucet /kyc /pay       │
│  /market /trade /portfolio /attest      │
└─────────────┬───────────────────────────┘
              │
              ▼
┌─────────────────────────────────────────┐
│         Nexash Backend                  │
│                                         │
│  ┌──────────┐  ┌──────────────────────┐ │
│  │Venice AI │  │  HSP Mandate Builder │ │
│  │(GLM-5.2) │  │  + Coordinator Client│ │
│  └──────────┘  └──────────────────────┘ │
│                                         │
│  ┌──────────┐  ┌──────────────────────┐ │
│  │HashKey   │  │  Nexash Issuer       │ │
│  │Exchange  │  │  (KYC attestations)  │ │
│  │  API     │  └──────────────────────┘ │
│  └──────────┘                           │
└──────┬──────────────────────┬───────────┘
       │                      │
       ▼                      ▼
┌─────────────┐    ┌──────────────────────┐
│  HSP        │    │  HashKey Chain       │
│  Coordinator│    │  Mainnet (177)       │
│  (testnet)  │    │                      │
│             │    │  AttestationRegistry │
│  ACCEPT /   │    │  PayrollTreasury     │
│  REJECT     │    └──────────────────────┘
└─────────────┘

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 for a compliant payment.

Components used

HashKey Ecosystem

Component	Role	Status
HashKey Chain mainnet (177)	Smart contract deployment, attestation storage	Live
HashKey Chain testnet (133)	HSP payment execution	Live
HashKey Settlement Protocol	Payment mandate + compliance verification	Registered Issuer
HashKey Exchange API	Market data, OHLCV, price feeds	Live
NexaID	zkTLS KYC evidence source	In Development