Skip to content

docs: add SwapDK swidge community module#205

Open
Vali0x wants to merge 2 commits into
tetherto:mainfrom
Vali0x:docs/swapdk-swidge-community-module
Open

docs: add SwapDK swidge community module#205
Vali0x wants to merge 2 commits into
tetherto:mainfrom
Vali0x:docs/swapdk-swidge-community-module

Conversation

@Vali0x

@Vali0x Vali0x commented Jul 13, 2026

Copy link
Copy Markdown

Adds documentation for @swapdk/wdk-protocol-swidge-swapdk under content/docs/sdk/swidge-modules/swidge-swapdk.

Also adds one row to content/docs/sdk/community-modules/index.mdx pointing at the swidge-swapdk docs. Type = "Swidge Module", author = SwapDK.

Content highlights:

  • Multi-family source coverage: the swidge module ships a single class covering Bitcoin, EVM (Ethereum / Arbitrum / Base / BSC / Avalanche), Cosmos (THORChain / MAYAChain), Solana, and TRON as sources.

  • Server-side provider selection across THORChain / MAYAChain / Chainflip; live halt-filtered discovery via /chains and /tokens?shape=swidge.

  • Peer pin: @tetherto/wdk-wallet=1.0.0-beta.11 exact (upstream beta.12+ regressed the SwidgeProtocol re-export from /protocols/index.js).

  • Known limits in v1.0.0 (SwidgeProtocolConfig fee caps no-op, minAmountOut not forwarded, Solana SPL unsupported, getSupportedTokens fromToken filter passed through) documented in every page that mentions those APIs — no silent surprises for adopters.

  • Community disclaimer callout matches other swidge modules wording ("developed and maintained independently by a third-party contributor").

Content sourced from the module's README + CHANGELOG in the Swap-DK/wdk-protocol-bridges-swapdk repo (packages/swidge/); references throughout link back to the source on GitHub and to related WDK wallet-module pages for peer-wallet setup.

Vali0x added 2 commits July 13, 2026 13:38
Adds documentation for @swapdk/wdk-protocol-swidge-swapdk under
content/docs/sdk/swidge-modules/swidge-swapdk/ following the same
structure as swidge-rhinofi/ and swidge-orchestra/ (index /
configuration / usage / api-reference).

Also adds one row to content/docs/sdk/community-modules/index.mdx
pointing at the swidge-swapdk docs. Type = "Swidge Module", author =
SwapDK.

Content highlights:

- Multi-family source coverage: the swidge module ships a single
  class covering Bitcoin, EVM (Ethereum / Arbitrum / Base / BSC /
  Avalanche), Cosmos (THORChain / MAYAChain), Solana, and TRON as
  sources — larger scope than the existing rhinofi (EVM-only) and
  orchestra (BTC + stablecoins via Spark) community swidge modules.

- Server-side provider selection across THORChain / MAYAChain /
  Chainflip; live halt-filtered discovery via /chains and
  /tokens?shape=swidge.

- Legacy compatibility for free — because the base SwidgeProtocol
  class delegates bridge/quoteBridge/swap/quoteSwap to
  swidge/quoteSwidge, consumers still on the older IBridgeProtocol /
  ISwapProtocol API get compatibility without code changes.

- Peer pin: @tetherto/wdk-wallet=1.0.0-beta.11 exact (matches the
  rhinofi module's pin; upstream beta.12+ regressed the
  SwidgeProtocol re-export from /protocols/index.js).

- Known limits in v1.0.0-alpha (SwidgeProtocolConfig fee caps no-op,
  minAmountOut not forwarded, Solana SPL unsupported, getSupportedTokens
  fromToken filter passed through) documented in every page that
  mentions those APIs — no silent surprises for adopters.

- Community disclaimer callout matches swidge-orchestra/index.mdx
  wording ("developed and maintained independently by a third-party
  contributor").

Content sourced from the module's README + CHANGELOG in the
Swap-DK/wdk-protocol-bridges-swapdk repo (packages/swidge/); references
throughout link back to the source on GitHub and to related WDK
wallet-module pages for peer-wallet setup.
The @swapdk/wdk-protocol-swidge-swapdk package is now on 1.0.0 (was
1.0.0-alpha.0 when these docs were written). Same code — the alpha
window is closed and downstream can pin against the stable version.

Touched:

- index.mdx: "Currently on 1.0.0-alpha.0. … breaking changes are still
  possible before 1.0.0" callout reworded to signal stable ("Currently
  on 1.0.0 — stable API surface"). "Known Limits (v1.0.0-alpha)"
  heading loses the version qualifier — the limits remain but they're
  the current-release scope-of-first-release notes now, not alpha-
  window caveats.

- api-reference.mdx: `#known-limits-v100-alpha` anchor updated to
  `#known-limits` to match the renamed heading.
@Vali0x
Vali0x marked this pull request as ready for review July 14, 2026 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant