← All intelligence

GitHub · November 11, 2026

SimplyStaking/pegaroute-sdk released v0.3.0

github.com · Read at source ↗

## Overview New SDK surface: - `userIp` on `quotes.get()` and `swaps.create()` - `destinationMemo` on `quotes.get()` and `swaps.create()` - `QuoteRoute.destinationMemoLabel` - `DESTINATION_MEMO_UNSUPPORTED` - `providerStatus` on `TransactionWebhookData.input` SDK `0.3.0` requires Pegaroute `v0.9.0` for destination memo and webhook provider-status fields. ### Upgrade guide: `0.2.0` → `0.3.0` Instal

SimplyStaking’s Pegaroute SDK v0.3.0 adds user-IP and destination-memo parameters for quotes and swaps, alongside provider-status information in transaction webhooks. The update retains compatibility with existing calls made using SDK v0.2.0.

Compatibility and installation

The release notes specify Pegaroute v0.9.0 as a requirement for the destination-memo and webhook provider-status fields.

Developers can install the SDK with:

```sh npm install @pegaroute/sdk@0.3.0 ```

The changes are additive: existing quote and swap calls remain valid. Catalog-specific SDK updates are unnecessary because chain and token identifiers already use string types.

The new SDK surface includes:

  • `userIp` and `destinationMemo` on both `quotes.get()` and `swaps.create()`.
  • `QuoteRoute.destinationMemoLabel`.
  • The `DESTINATION_MEMO_UNSUPPORTED` error code.
  • `providerStatus` on `TransactionWebhookData.input`.

Enabling SwapSpace routes

The upgrade guide instructs developers to supply the same end-user `userIp` when requesting a quote and creating a swap to enable SwapSpace routes.

Its example requests a swap amount of `"1"`, from chain `ETH` and token `ETH` to chain `CANTON` and token `CC`, using the illustrative IP address `203.0.113.7`. It selects a route whose provider is `swapspace`, falling back to the first returned route if none matches.

The swap request carries forward the quote’s `quoteId` and the selected route’s provider through `routeProvider`. The example uses `0x1111111111111111111111111111111111111111` as the sender address and `canton-address` as the destination.

Passing destination memos

For a destination memo, tag or payment ID, developers should include `destinationMemo` in both the quote and swap requests.

The memo example uses `"payment-id-1"` with the same chain, token, amount, IP and address values as the initial example. It reads `destinationMemoLabel` from the first returned route and uses that route’s provider when creating the swap.

The release notes direct interfaces to use `destinationMemoLabel` as the field label. This value comes from the live provider and may be `Memo`, `Tag` or `Payment ID`.

A destination memo must not be placed in `execution.memo`: it is distinct from a source-chain signing memo.

Errors and webhook status

The guide describes handling two error codes through `PegarouteError`:

  • `USER_IP_REQUIRED`: obtain a valid end-user IP address, then retry the quote.
  • `DESTINATION_MEMO_UNSUPPORTED`: omit `destinationMemo` or select a route that accepts it.

Webhook consumers can also inspect provider-status evidence when it is available. The example checks `event.data.input.providerStatus?.actionRequired` and, when action is required, passes the accompanying `message` to `showAction`.

Release record and downloads

GitHub lists `atharen`, identified as Tharen Abela, as the publisher, with a release time of 11 November at 09:55. The release points to commit `285c7ea`, and the page records four subsequent commits to `main`.

The commit carries a verified signature, recorded on 11 November 2026 at 03:43 AM, with SSH key fingerprint `4ELYPWEVaePi9oqz4wQifEOCJtvGk5FWgzORoCBTtaI`.

The page marks v0.3.0 as the latest release and provides two source-code archives, in ZIP and TAR.GZ formats. Both assets carry the timestamp `2026-11-11T08:40:40Z`.

TopicProduct
ProvenanceLive web scan, matched against the project registry
Scope
Canton Network

Sources & attribution

Published
Nov 11, 2026 · 9:55 AM UTC
Source
github.com
Publisher
github.com

Full attribution under the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512: this article is an original report by Canton Intelligence that summarizes the reporting of the publishers named above, links to their original work, and reproduces no protected expression beyond brief factual reference and in-line attribution (“according to github.com”). All rights in the underlying reporting remain with the publishers listed; nothing here implies endorsement by or affiliation with them. Rights holders may request correction, update or removal through the contact address published at infiniti.w3ai.io.