hyperliquid 1.9.2 → 2.0.0

metadata

@@ -1,14 +1,28 @@
 --- !ruby/object:Gem::Specification
 name: hyperliquid
 version: !ruby/object:Gem::Version
-  version: 1.9.2
+  version: 2.0.0
 platform: ruby
 authors:
 - carter2099
-bindir: exe
+bindir: bin
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
+- !ruby/object:Gem::Dependency
+  name: bigdecimal
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.1'
 - !ruby/object:Gem::Dependency
   name: eth
   requirement: !ruby/object:Gem::Requirement
@@ -87,15 +101,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".rspec"
-- ".rubocop.yml"
-- ".ruby-version"
 - CHANGELOG.md
-- CLAUDE.md
-- CODE_OF_CONDUCT.md
 - LICENSE.txt
 - README.md
-- Rakefile
 - SECURITY.md
 - docs/API.md
 - docs/CONFIGURATION.md
@@ -103,7 +111,6 @@ files:
 - docs/ERRORS.md
 - docs/EXAMPLES.md
 - docs/WS.md
-- example.rb
 - lib/hyperliquid.rb
 - lib/hyperliquid/client.rb
 - lib/hyperliquid/cloid.rb
@@ -116,31 +123,6 @@ files:
 - lib/hyperliquid/signing/signer.rb
 - lib/hyperliquid/version.rb
 - lib/hyperliquid/ws/client.rb
-- scripts/test_01_spot_market_roundtrip.rb
-- scripts/test_02_spot_limit_order.rb
-- scripts/test_03_perp_market_roundtrip.rb
-- scripts/test_04_perp_limit_order.rb
-- scripts/test_05_update_leverage.rb
-- scripts/test_06_modify_order.rb
-- scripts/test_07_market_close.rb
-- scripts/test_08_usd_class_transfer.rb
-- scripts/test_09_sub_account_lifecycle.rb
-- scripts/test_10_vault.rb
-- scripts/test_11_builder_fee.rb
-- scripts/test_12_staking.rb
-- scripts/test_13_ws_l2_book.rb
-- scripts/test_14_ws_candle.rb
-- scripts/test_15_explorer.rb
-- scripts/test_16_send_to_evm_with_data.rb
-- scripts/test_17_create_vault.rb
-- scripts/test_18_user_portfolio_margin.rb
-- scripts/test_19_spot_user.rb
-- scripts/test_20_explorer_ws.rb
-- scripts/test_all.rb
-- scripts/test_automated.rb
-- scripts/test_helpers.rb
-- sig/hyperliquid.rbs
-- test_integration.rb
 homepage: https://github.com/carter2099/hyperliquid
 licenses:
 - MIT

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---require spec_helper

data/.rubocop.yml

@@ -1,49 +0,0 @@
-AllCops:
-  NewCops: enable
-  TargetRubyVersion: 3.3
-  SuggestExtensions: false
-  Exclude:
-    - 'test_*.rb'  # Exclude ad-hoc integration test scripts
-    - 'scripts/**/*'  # Exclude integration test scripts
-    - 'local/**/*'  # Exclude local test scripts
-    - 'vendor/**/*'  # Exclude vendored gems (CI bundles here)
-
-# Allow longer methods for complex logic
-Metrics/MethodLength:
-  Max: 50
-
-# Allow higher complexity for response handling
-Metrics/AbcSize:
-  Max: 25
-
-# Disable class length checks so rubocop doesn't complain that we implement all of Hyperliquid's endpoints
-Metrics/ClassLength:
-  Enabled: false
-
-# Allow longer blocks in specs and gemspec - this is normal for tests and gem configs
-Metrics/BlockLength:
-  Exclude:
-    - 'spec/**/*'
-    - '*.gemspec'
-
-# Exchange API methods (and multi-sig co-signer helpers that pass through to them) require many parameters
-Metrics/ParameterLists:
-  Exclude:
-    - 'lib/hyperliquid/exchange.rb'
-    - 'lib/hyperliquid/signing/multi_sig.rb'
-
-# Allow higher complexity for order type conversion logic and WS message handling
-Metrics/CyclomaticComplexity:
-  Exclude:
-    - 'lib/hyperliquid/exchange.rb'
-    - 'lib/hyperliquid/ws/client.rb'
-
-Metrics/PerceivedComplexity:
-  Exclude:
-    - 'lib/hyperliquid/exchange.rb'
-    - 'lib/hyperliquid/ws/client.rb'
-
-# Empty blocks are intentional in specs (no-op callbacks for subscription tests)
-Lint/EmptyBlock:
-  Exclude:
-    - 'spec/**/*'

data/.ruby-version

@@ -1 +0,0 @@
-3.4.10

data/CLAUDE.md

@@ -1,108 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to AI coding agents working with this repository. It is the canonical source of truth — keep it in sync as the SDK evolves.
-
-## Overview
-
-Ruby SDK for the Hyperliquid decentralized exchange API. Three API surfaces: **Info** (read-only market data), **Exchange** (authenticated trading), and **WebSocket** (real-time streaming). Built on Faraday for HTTP, the `eth` gem for EIP-712 signing, `msgpack` for action serialization, and `ws_lite` for WebSocket connections.
-
-Version is the single source of truth in `lib/hyperliquid/version.rb`; required Ruby version is in the gemspec.
-
-## Commands
-
-```bash
-bin/setup                  # install dependencies
-rake                       # run tests + linting (CI default)
-rake spec                  # tests only
-rake rubocop               # linting only
-bundle exec rspec spec/hyperliquid/cloid_spec.rb       # single file
-bundle exec rspec spec/hyperliquid/cloid_spec.rb:62    # single test by line
-bin/console                # IRB with SDK loaded
-ruby example.rb            # example usage script
-```
-
-### Integration Tests (Testnet)
-
-Integration scripts live in `scripts/` as standalone files (`test_NN_<name>.rb`). They require a real testnet private key and hit the live testnet API.
-
-```bash
-HYPERLIQUID_PRIVATE_KEY=0x... ruby scripts/test_all.rb              # all 20
-HYPERLIQUID_PRIVATE_KEY=0x... ruby scripts/test_automated.rb        # CI-friendly subset (14)
-HYPERLIQUID_PRIVATE_KEY=0x... ruby scripts/test_08_usd_class_transfer.rb  # single
-```
-
-`test_automated.rb` is the unattended runner — same as `test_all.rb` but excludes scripts that require manual testnet preconditions (e.g. `test_09_sub_account_lifecycle` needs $100k traded volume; `test_12_staking` needs HYPE balance). Some included tests (e.g. `test_08`, `test_11`) are also coded to skip-with-warning when known testnet preconditions aren't met, so the suite stays green on a stable wallet.
-
-`test_integration.rb` at the project root is a thin convenience wrapper.
-
-## Architecture
-
-### Request Flow
-
-All three API surfaces are reached through `Hyperliquid::SDK` (`lib/hyperliquid.rb`):
-
-```
-Hyperliquid.new(...)
-  ├── sdk.info     → Info       → Client → POST /info     (always available)
-  ├── sdk.exchange → Exchange   → Client → POST /exchange  (requires private_key)
-  └── sdk.ws       → WS::Client → WSS /ws                 (real-time streaming)
-```
-
-- **Info path**: method builds `{ type: 'someType', ... }` body → `Client` POSTs to `/info` → parsed JSON returned.
-- **Exchange path**: method builds action payload → `Signer` generates EIP-712 signature over msgpack-encoded action → `Client` POSTs signed payload to `/exchange` → parsed JSON returned.
-- **Explorer RPC path** (`tx_details`, `user_details`): a separate base URL (`rpc.hyperliquid.xyz` / `rpc.hyperliquid-testnet.xyz`) with endpoint `/explorer`. `Client` holds a second Faraday connection for this, built lazily on first use; methods opt in via `client.post(EXPLORER_ENDPOINT, body, target: :explorer)`. The SDK wires this up automatically based on `testnet:`. Calling `target: :explorer` on a `Client` constructed without `explorer_base_url:` raises `ConfigurationError`. Don't add a public connection accessor — `target:` is the contract.
-- **WebSocket path**: `WS::Client` manages two independent WebSocket connections:
-  - **Main API WS** (`wss://api.hyperliquid.xyz/ws`): subscribes to market data channels (`l2Book`, `trades`, `candle`, etc.). Messages arrive as `{channel, data}` envelopes; `compute_identifier` extracts routing keys (e.g. `l2Book:eth`, `candle:btc:1h`). Callbacks are dispatched via a bounded queue (1024, drops on overflow) on a dedicated thread.
-  - **Explorer WS** (`wss://rpc.hyperliquid.xyz/ws`): subscribes to block/transaction streams (`explorerBlock`, `explorerTxs`). Messages arrive as **bare arrays** (no envelope), so `identify_explorer_array` duck-types by field presence (`blockTime`/`height` for blocks, `action`/`hash` for txs). Uses a separate queue, dispatch thread, and subscription ID namespace to avoid cross-contamination with main-API WS. Both connections share the same 50s ping keepalive, automatic reconnection (exp backoff, 30s cap), and lifecycle hooks (`on(:open)`, `on(:close)`, `on(:error)`).
-
-### Signing (Python SDK Parity)
-
-The signing chain in `lib/hyperliquid/signing/` must exactly match the official Python SDK:
-
-1. **Action hash**: `keccak256(msgpack(action) + nonce(8B big-endian) + vault_flag + [vault_addr] + [expires_flag + expires_after])`
-2. **Phantom agent**: `{ source: 'a'|'b', connectionId: action_hash }` (`a`=mainnet, `b`=testnet)
-3. **EIP-712 signature** over phantom agent with Exchange domain (chain ID 1337)
-
-Any change to signing must maintain parity with the Python SDK or transactions will be rejected by the exchange.
-
-User-signed actions (`usd_send`, `withdraw_from_bridge`, `send_to_evm_with_data`, etc.) use direct EIP-712 typed-data signing with the `HyperliquidSignTransaction` domain (chain ID 421614) — not the phantom-agent flow. Each has a typed-data spec in `Signing::EIP712`. The `eth` gem's typed-data signer handles primitive types (`string`, `uint*`, `address`, `bool`) and dynamic `bytes` correctly — `send_to_evm_with_data` was the first to use `bytes`, and its spec includes a fixture-based signature parity test against `eth_account` to lock that in. When adding new user-signed actions with non-string types, add a similar fixture to catch eth-gem regressions.
-
-Multi-sig actions (`Exchange#multi_sig`) wrap any inner action with N co-signer signatures. The submitter's outer signature uses `MULTI_SIG_TYPES` over `{hyperliquidChain, multiSigActionHash, nonce}`; the `multiSigActionHash` is `Signer.compute_action_hash` of the multi-sig envelope (with `:type` stripped). Co-signer signing is exposed via `Signing::MultiSig.sign_as_co_signer_l1` (for L1 inner actions — signs `[multi_sig_user, outer_signer, action]` via phantom-agent) and `Signing::MultiSig.sign_as_co_signer_user_signed` (enriches the inner action's typed-data spec with `payloadMultiSigUser`+`outerSigner` address fields). Both mirror the Python SDK byte-for-byte; specs include fixture-based parity tests captured against `eth_account`+`msgpack`. Co-signature *collection* is the caller's responsibility — the SDK does not coordinate signing rooms.
-
-### Numeric Conversion
-
-- **`float_to_wire`** (in Exchange): converts to string with 8-decimal precision, validates rounding tolerance (`1e-12`), normalizes trailing zeros. No scientific notation.
-- **Market order pricing** (`_slippage_price`): apply slippage (default 5%) to mid price → round to 5 significant figures → round to `(6 for perp, 8 for spot) - szDecimals` decimal places.
-- **Spot vs perp**: assets with index `>= 10_000` are spot (`SPOT_ASSET_THRESHOLD` in Exchange). This affects decimal place calculations.
-
-### HIP-3 (Builder-Deployed Perps)
-
-Many Info methods accept a `dex:` kwarg (e.g. `meta(dex: 'foo')`, `user_state(user, dex: 'foo')`) to query a builder-deployed perp dex rather than the canonical perp market. `Info#perp_dexs` enumerates available dexes; `Info#perp_dex_limits(dex)` returns per-dex risk parameters.
-
-### Testing
-
-- **Unit tests** (`spec/`): RSpec + WebMock. WebMock resets between tests. Monkey-patching disabled. Test files mirror `lib/` structure. No live HTTP calls in unit tests. The WS client spec (`spec/hyperliquid/ws/client_spec.rb`) includes comprehensive isolation tests verifying that explorer WS messages never route to main-API callbacks and vice versa — this is critical because the two transports share the same `WS::Client` class.
-- **Integration tests** (`scripts/`): run against testnet with a real private key. Each script is self-contained. Helpers (separators, status dumping, retry-on-oracle-bounce) live in `scripts/test_helpers.rb`. `test_20_explorer_ws.rb` subscribes to `explorerBlock` on testnet and collects 3 block events (60s timeout) to verify the explorer WS transport works end-to-end.
-- **`dump_status` / `check_result` helpers** in `test_helpers.rb` must guard against `result['response']` *itself* being a String for transfer-style actions (`usdClassTransfer`, `approveBuilderFee`) — not just `result['response']['data']`. This was a real bug fixed in 1.1.0; preserve the guards if refactoring those helpers.
-
-### Code Style
-
-RuboCop targets Ruby 3.3. Key relaxations: methods up to 50 lines, no class length limit (Info/Exchange are large by design), no block length limit in specs, no parameter list limit in Exchange, empty blocks allowed in specs (intentional no-op callbacks). `scripts/`, `test_*.rb`, `local/`, and `vendor/` are excluded from linting. The WS client's `initialize` method was refactored to extract `init_main_ws_state` and `init_explorer_ws_state` helpers to reduce ABC size (33 assignments across two transports).
-
-Predicate methods follow Ruby style (`vip?`, `connected?`, `testnet?`) — not `is_vip` / `is_connected`. RuboCop's `Naming/PredicateName` enforces this.
-
-### CI
-
-GitHub Actions (`.github/workflows/main.yml`): runs `bundle exec rake` (tests + lint) on the Ruby matrix defined in that workflow, for pushes to `main` and on all PRs. The release workflow creates GitHub releases from `CHANGELOG.md` on version tags. Dependabot checks Bundler and GitHub Actions dependencies weekly with a 14-day default cooldown; Bundler major updates use a 30-day cooldown.
-
-### rbsecp256k1 git source
-
-The `Gemfile` pins `rbsecp256k1` to Carter's fork (`carter2099/rbsecp256k1`, full-SHA `ref:`, version 6.1.0) because rubygems only has 6.0.0, which requires `rubyzip ~> 2.3` (GHSA-47m2-wp7j-p9vc); the fork requires `rubyzip >= 3.4, < 4` and builds libsecp256k1 0.8.0. This affects only the dev/CI lockfile — a gemspec cannot declare git sources, so consumers of the published gem still resolve rubygems rbsecp256k1 6.0.0 via `eth ~> 0.5`. Dependabot is not expected to bump a SHA-pinned git ref; a Dependabot PR touching rbsecp256k1's source/ref or moving rubyzip below 3.4 must not be applied without Carter. Never `bundle update` it or drop the declaration; moving the ref is a deliberate, reviewed change (re-run the signature-parity specs in `spec/hyperliquid/signing/`). Remove the git source once an upstream rbsecp256k1 release on rubygems allows rubyzip 3.
-
-## Release Flow
-
-Releases happen from `main`. Day-to-day work lands on `dev`, then `dev` is merged into `main` and the version commit is pushed. `CHANGELOG.md` follows Keep-a-Changelog conventions; `lib/hyperliquid/version.rb` is the single source of version truth (gemspec reads it). Releases are atomic: only after the `Ruby` workflow is green on main and the gem is built is the RubyGems OTP requested; `gem push` goes first and the `vX.Y.Z` tag is pushed only after it succeeds. The tag push triggers the GitHub release workflow, so a failed gem push leaves no tag and no GitHub Release.
-
-## Additional Docs
-
-Detailed API reference, examples, WebSocket guide, configuration, and error handling in `docs/` (`API.md`, `EXAMPLES.md`, `WS.md`, `CONFIGURATION.md`, `ERRORS.md`, `DEVELOPMENT.md`).

data/CODE_OF_CONDUCT.md

@@ -1,132 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[INSERT CONTACT METHOD].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

data/Rakefile

@@ -1,12 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-require 'rubocop/rake_task'
-
-RuboCop::RakeTask.new
-
-task default: %i[spec rubocop]

data/example.rb

@@ -1,161 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require_relative 'lib/hyperliquid'
-
-# Example usage of the Hyperliquid Ruby SDK
-
-puts 'Hyperliquid Ruby SDK v0.4.0 - API Examples'
-puts '=' * 50
-
-# =============================================================================
-# INFO API (Read-only, no authentication required)
-# =============================================================================
-
-# Create a new SDK instance (defaults to mainnet)
-sdk = Hyperliquid.new
-
-puts "\n--- INFO API EXAMPLES ---\n"
-
-# Example 1: Get all market mid prices
-begin
-  puts '1. Getting all market mid prices...'
-  mids = sdk.info.all_mids
-  puts "   Found #{mids.length} markets" if mids.is_a?(Hash)
-  puts "   BTC mid: #{mids['BTC']}" if mids['BTC']
-rescue Hyperliquid::Error => e
-  puts "   Error: #{e.message}"
-end
-
-# Example 2: Get metadata for all perpetual assets
-begin
-  puts "\n2. Getting perpetual asset metadata..."
-  meta = sdk.info.meta
-  universe = meta['universe'] || []
-  puts "   Found #{universe.length} perpetual assets"
-  puts "   First asset: #{universe.first['name']}" if universe.any?
-rescue Hyperliquid::Error => e
-  puts "   Error: #{e.message}"
-end
-
-# Example 3: Get L2 order book
-begin
-  puts "\n3. Getting L2 order book for BTC..."
-  book = sdk.info.l2_book('BTC')
-  levels = book['levels'] || []
-  puts "   Bid levels: #{levels[0]&.length || 0}, Ask levels: #{levels[1]&.length || 0}"
-rescue Hyperliquid::Error => e
-  puts "   Error: #{e.message}"
-end
-
-# Example 4: Get spot metadata
-begin
-  puts "\n4. Getting spot asset metadata..."
-  spot_meta = sdk.info.spot_meta
-  tokens = spot_meta['tokens'] || []
-  puts "   Found #{tokens.length} spot tokens"
-rescue Hyperliquid::Error => e
-  puts "   Error: #{e.message}"
-end
-
-# Example 5: Use testnet
-puts "\n5. Creating testnet SDK..."
-testnet_sdk = Hyperliquid.new(testnet: true)
-puts "   Testnet base URL: #{testnet_sdk.base_url}"
-
-# Example 6: User-specific endpoints (requires valid wallet address)
-wallet_address = "0x#{'0' * 40}" # Placeholder address
-
-begin
-  puts "\n6. Getting user state for #{wallet_address[0..13]}..."
-  state = sdk.info.user_state(wallet_address)
-  puts "   Account value: #{state.dig('marginSummary', 'accountValue') || 'N/A'}"
-rescue Hyperliquid::Error => e
-  puts "   Error: #{e.message}"
-end
-
-# =============================================================================
-# EXCHANGE API (Authenticated, requires private key)
-# =============================================================================
-
-puts "\n--- EXCHANGE API EXAMPLES ---\n"
-puts "(These examples are commented out to prevent accidental execution)\n"
-
-# To use the Exchange API, create an SDK with your private key:
-#
-#   sdk = Hyperliquid.new(
-#     testnet: true,  # Use testnet for testing!
-#     private_key: ENV['HYPERLIQUID_PRIVATE_KEY']
-#   )
-#
-# Your wallet address:
-#   puts sdk.exchange.address
-#
-# Place a limit order:
-#   result = sdk.exchange.order(
-#     coin: 'BTC',
-#     is_buy: true,
-#     size: 0.001,
-#     limit_px: 50000.0,
-#     order_type: { limit: { tif: 'Gtc' } },
-#     reduce_only: false
-#   )
-#
-# Place a market order (uses slippage):
-#   result = sdk.exchange.market_order(
-#     coin: 'BTC',
-#     is_buy: true,
-#     size: 0.001,
-#     slippage: 0.01  # 1% slippage
-#   )
-#
-# Place a stop loss order:
-#   result = sdk.exchange.order(
-#     coin: 'BTC',
-#     is_buy: false,
-#     size: 0.001,
-#     limit_px: 48000.0,
-#     order_type: {
-#       trigger: {
-#         trigger_px: 49000.0,
-#         is_market: false,
-#         tpsl: 'sl'
-#       }
-#     },
-#     reduce_only: true
-#   )
-#
-# Cancel an order by OID:
-#   result = sdk.exchange.cancel(coin: 'BTC', oid: 123456789)
-#
-# Cancel an order by client order ID:
-#   result = sdk.exchange.cancel_by_cloid(coin: 'BTC', cloid: '0x...')
-#
-# Bulk cancel multiple orders:
-#   result = sdk.exchange.bulk_cancel([
-#     { coin: 'BTC', oid: 123 },
-#     { coin: 'ETH', oid: 456 }
-#   ])
-#
-# Use client order IDs for tracking:
-#   cloid = Hyperliquid::Cloid.random
-#   result = sdk.exchange.order(
-#     coin: 'BTC',
-#     is_buy: true,
-#     size: 0.001,
-#     limit_px: 50000.0,
-#     cloid: cloid
-#   )
-#   puts "Order placed with cloid: #{cloid}"
-#
-# Trade on behalf of a vault:
-#   result = sdk.exchange.order(
-#     coin: 'BTC',
-#     is_buy: true,
-#     size: 0.001,
-#     limit_px: 50000.0,
-#     vault_address: '0x...'
-#   )
-
-puts 'See commented code above for Exchange API usage patterns.'
-puts "\nSDK examples completed!"

data/scripts/test_01_spot_market_roundtrip.rb

@@ -1,48 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# Test 1: Spot Market Roundtrip (PURR/USDC)
-# Buy and sell PURR at market price.
-
-require_relative 'test_helpers'
-
-sdk = build_sdk
-separator('TEST 1: Spot Market Roundtrip (PURR/USDC)')
-
-spot_coin = 'PURR/USDC'
-spot_size = 5
-
-mids = sdk.info.all_mids
-spot_price = mids[spot_coin]&.to_f
-
-if spot_price&.positive?
-  puts "#{spot_coin} mid: $#{spot_price}"
-  puts "Size: #{spot_size} PURR (~$#{(spot_size * spot_price).round(2)})"
-  puts "Slippage: #{(SPOT_SLIPPAGE * 100).to_i}%"
-  puts
-
-  puts 'Placing market BUY...'
-  result = sdk.exchange.market_order(
-    coin: spot_coin,
-    is_buy: true,
-    size: spot_size,
-    slippage: SPOT_SLIPPAGE
-  )
-  check_result(result, 'Buy')
-
-  wait_with_countdown(WAIT_SECONDS, 'Waiting before sell...')
-
-  puts 'Placing market SELL...'
-  result = sdk.exchange.market_order(
-    coin: spot_coin,
-    is_buy: false,
-    size: spot_size,
-    slippage: SPOT_SLIPPAGE
-  )
-  check_result(result, 'Sell')
-else
-  puts red("SKIPPED: Could not get #{spot_coin} price")
-end
-
-test_passed('Test 1 Spot Market Roundtrip')
-

data/scripts/test_02_spot_limit_order.rb

@@ -1,48 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-# Test 2: Spot Limit Order (Place and Cancel)
-# Place a limit buy well below market, then cancel it.
-
-require_relative 'test_helpers'
-
-sdk = build_sdk
-separator('TEST 2: Spot Limit Order (Place and Cancel)')
-
-spot_coin = 'PURR/USDC'
-spot_size = 5
-
-mids = sdk.info.all_mids
-spot_price = mids[spot_coin]&.to_f
-
-if spot_price&.positive?
-  limit_price = (spot_price * 0.50).round(2)
-  puts "#{spot_coin} mid: $#{spot_price}"
-  puts "Limit price: $#{limit_price} (50% below mid - won't fill)"
-  puts "Size: #{spot_size} PURR"
-  puts
-
-  puts 'Placing limit BUY order...'
-  result = sdk.exchange.order(
-    coin: spot_coin,
-    is_buy: true,
-    size: spot_size,
-    limit_px: limit_price,
-    order_type: { limit: { tif: 'Gtc' } },
-    reduce_only: false
-  )
-  oid = check_result(result, 'Limit order')
-
-  if oid.is_a?(Integer)
-    wait_with_countdown(WAIT_SECONDS, 'Order resting. Waiting before cancel...')
-
-    puts "Canceling order #{oid}..."
-    result = sdk.exchange.cancel(coin: spot_coin, oid: oid)
-    check_result(result, 'Cancel')
-  end
-else
-  puts red("SKIPPED: Could not get #{spot_coin} price")
-end
-
-test_passed('Test 2 Spot Limit Order')
-