From 86564cd37ed132e06a6936d14fa67ad288bc7a2e Mon Sep 17 00:00:00 2001 From: "Ryan G. Young" Date: Thu, 8 Apr 2021 17:30:46 -0700 Subject: [PATCH] restore specific links --- .../references/rippled-api/api-conventions/serialization.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/references/rippled-api/api-conventions/serialization.md b/content/references/rippled-api/api-conventions/serialization.md index e69eab2310..3c361c816b 100644 --- a/content/references/rippled-api/api-conventions/serialization.md +++ b/content/references/rippled-api/api-conventions/serialization.md @@ -43,6 +43,12 @@ 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/ripple/ripple-binary-codec/) package. +- In Python 3 in [this repository's code samples section]({{target.github_forkurl}}/blob/{{target.github_branch}}/content/_code-samples/tx-serialization/serialize.py). + +Additionally, the following libraries also provide serialization support: + {% include '_snippets/libs-snippet.md' %} These implementations are all provided with permissive open-source licenses, so you can import, use, or adapt the code for your needs in addition to using it alongside these documents for learning purposes.