Skip to content

Document SDK 0.2.0 release #4

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
mcc0x merged 1 commit into from
Oct 7, 2026
Merged

Document SDK 0.2.0 release #4

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/reference/developer-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Query arguments are optional. Use the Claire chat UUID from `telegram.chats.list

### Token identity

The next SDK contract adds `chainId`, `protocol`, `poolId`, and `pairedToken` inside `data.token`. These TypeScript fields are not in npm `0.1.0`; check the SDK release notes and hosted OpenAPI before relying on them. Ethereum availability is also rollout-gated.
SDK `0.2.0` adds typed `chainId`, `protocol`, `poolId`, and `pairedToken` fields inside `data.token`, matching the hosted API contract. Upgrade from `0.1.0` to use these TypeScript fields. Network availability still depends on the deployment; the SDK does not enable Ethereum transactions.

Identify a token by **chain ID and contract address together**: Ethereum is `1`, Robinhood Chain is `4663`, and `protocol` is `pons` or `stockereum`. The token object is `null` when none is linked.

Expand Down
Loading