How coinbase/core-go works
core-go is a small reusable SDK runtime for REST calls, WebSocket connections, and shared value helpers. The main flow is an SDK caller invoking an HTTP verb helper, which serializes the request, applies optional headers, performs the request through the supplied client, then decodes the response or returns a structured error. A separate WebSocket flow dials and wraps a connection before callers can listen for messages. The README documents SDK integration and header/credential support; source excerpts show implementation details for HTTP and WebSockets, but not how consuming SDKs construct credentials.
Main entry points: http.go HTTP verbs · ws.go WebSocket dialer · ws_model.go WebSocket connection · client.go REST client
Components 15
HTTP requests
- HTTP verbs
http.go - REST client
client.go - Header hook
http.go - API response
http.go - API errors
http.go
WebSocket
- WebSocket dialer
ws.go - Dial configuration
ws_model.go - WebSocket connection
ws_model.go - Message listener
ws.go - WebSocket helpers
ws_utils.go
Shared utilities
- Value helpers
utils.go
Other components
- SDK caller
- HTTP transport
- Coinbase API
- WebSocket service
Connections 15
- SDK caller → HTTP verbs: invokes
README.md - HTTP verbs → REST client: uses client
http.go - HTTP verbs → Header hook: applies headers
http.go - REST client → HTTP transport: sends request
- HTTP transport → Coinbase API: HTTP request
- HTTP verbs → API response: decodes body
http.go - HTTP verbs → API errors: returns errors
http.go - SDK caller → WebSocket dialer: configures and dials
README.md - WebSocket dialer → Dial configuration: reads settings
ws.go - WebSocket dialer → WebSocket service: opens socket
- WebSocket dialer → WebSocket connection: wraps socket
ws.go - SDK caller → Message listener: listens through
- Message listener → WebSocket connection: reads messages
ws.go - WebSocket helpers → WebSocket connection: writes close
ws_utils.go - SDK caller → Value helpers: uses helpers