From 3b84534b6ab11a765c9158ffda94d126d5eb3776 Mon Sep 17 00:00:00 2001 From: AlexanderBuzz Date: Mon, 30 Jan 2023 13:06:27 +0100 Subject: [PATCH] - Changed link in xrpl.org/serialization.html from ripple-binary-codec to the code from this PR --- content/references/protocol-reference/serialization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/references/protocol-reference/serialization.md b/content/references/protocol-reference/serialization.md index ac401204f6..8841d00050 100644 --- a/content/references/protocol-reference/serialization.md +++ b/content/references/protocol-reference/serialization.md @@ -59,7 +59,7 @@ Both signed and unsigned transactions can be represented in both JSON and binary The serialization processes described here are implemented in multiple places and programming languages: - In C++ [in the `rippled` code base](https://github.com/ripple/rippled/blob/develop/src/ripple/protocol/impl/STObject.cpp). -- In JavaScript in the [`ripple-binary-codec`](https://github.com/XRPLF/xrpl.js/tree/main/packages/ripple-binary-codec) package. +- In JavaScript in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/). - In Python 3 in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/). Additionally, many [client libraries](client-libraries.html) provide serialization support under permissive open-source licenses, so you can import, use, or adapt the code for your needs.