DeFi Protocols

DeFi protocols use wallet-based authentication instead of API keys. Transactions are signed on-chain.

Hyperliquid

ID: hyperliquid | Markets: On-chain perpetuals DEX | Chain: L1

Hyperliquid is a fully on-chain order book for perpetual futures. Authentication uses an EVM private key for signing.

curl -X POST https://agents.systemr.ai/v1/broker/connect \
  -H "X-API-Key: sr_agent_..." \
  -H "Content-Type: application/json" \
  -d '{
    "broker_type": "hyperliquid",
    "connection_params": {
      "private_key": "0xYOUR_PRIVATE_KEY",
      "testnet": "false"
    }
  }'

Your private key is encrypted with per-agent AES-256 encryption and stored at rest. It is decrypted only at the moment of signing a transaction.

dYdX

ID: dydx | Markets: Decentralized perpetuals | Version: dYdX v4 (app chain)

dYdX v4 runs on its own Cosmos SDK app chain. Authentication requires an Ethereum address and STARK key pair.

curl -X POST https://agents.systemr.ai/v1/broker/connect \
  -H "X-API-Key: sr_agent_..." \
  -H "Content-Type: application/json" \
  -d '{
    "broker_type": "dydx",
    "connection_params": {
      "eth_address": "0xYOUR_ETH_ADDRESS",
      "api_key": "YOUR_API_KEY",
      "api_secret": "YOUR_API_SECRET",
      "api_passphrase": "YOUR_PASSPHRASE",
      "testnet": "false"
    }
  }'

Drift

ID: drift | Markets: Solana-native perpetuals | Chain: Solana

Drift Protocol is the leading perpetuals DEX on Solana. Uses Ed25519 wallet signing.

curl -X POST https://agents.systemr.ai/v1/broker/connect \
  -H "X-API-Key: sr_agent_..." \
  -H "Content-Type: application/json" \
  -d '{
    "broker_type": "drift",
    "connection_params": {
      "wallet_pubkey": "YOUR_SOLANA_PUBKEY",
      "private_key": "YOUR_SOLANA_PRIVATE_KEY"
    }
  }'

Your private key is encrypted with per-agent AES-256 encryption immediately upon connection. System R never stores plaintext keys at rest.

Security notes for DeFi connections

All DeFi broker credentials (private keys, secrets) are:

1. Encrypted in transit via HTTPS/TLS.
2. Encrypted at rest using per-agent AES-256 keys derived via PBKDF2.
3. Decrypted only at execution time when signing a transaction or placing an order.
4. Isolated per agent using unique encryption keys. One agent cannot access another's credentials.

For maximum security, use a dedicated trading wallet with only the funds you intend to trade. Do not use your primary cold storage wallet.