Skip to content

Drop internal iter-N references from user-facing docs #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pimfeltkamp merged 1 commit into from
Apr 28, 2026
+1 −1
Merged

Drop internal iter-N references from user-facing docs #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Getting-Started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ catch (CryptohopperException $e) {

**`cURL error 60: SSL certificate problem`** — corporate proxy or self-signed root CA in the chain. Don't disable verification globally; supply a custom Guzzle client with `verify` pointing at the right CA bundle (see "Bringing your own HTTP client" above).

**`cURL error 28: Operation timed out`** — your server's outbound connection to Cryptohopper is slow. The SDK now classifies this as `TIMEOUT` (was `NETWORK_ERROR` before iter-16). Retry with a longer `timeout:` if the slowness is legitimate, or check your firewall / outbound NAT.
**`cURL error 28: Operation timed out`** — your server's outbound connection to Cryptohopper is slow. The SDK classifies this as `TIMEOUT` (errno 28 specifically — non-timeout cURL errors stay as `NETWORK_ERROR`). Retry with a longer `timeout:` if the slowness is legitimate, or check your firewall / outbound NAT.

**Memory exhaustion on huge JSON responses** — the SDK reads the entire body into memory via `(string) $response->getBody()`. The Cryptohopper API doesn't return responses large enough to matter (no streaming endpoints), but if you hit a wall, supply a custom Guzzle client with stream-parsing middleware.

Expand Down