Soneso · christian-rogobete · Apr 3, 2026 · Apr 3, 2026
diff --git a/.gitignore b/.gitignore
@@ -122,13 +122,8 @@ stellar-sdk/native-libs/libsodium-macos/
 # Backup files
 *.bak
 
-# Compatibility analysis (keep local for now)
-tools/sdk-analysis/
-
-# Compatibility analysis generated data (keep source code)
-compatibility/horizon/data/
-compatibility/rpc/data/
-compatibility/sep/data/
+# Matrix generator intermediate data
+tools/matrix-generator/data/
 
 # Node modules (web app dependencies)
 node_modules/

diff --git a/compatibility/horizon/HORIZON_COMPATIBILITY_MATRIX.md b/compatibility/horizon/HORIZON_COMPATIBILITY_MATRIX.md
diff --git a/compatibility/rpc/RPC_COMPATIBILITY_MATRIX.md b/compatibility/rpc/RPC_COMPATIBILITY_MATRIX.md
@@ -1,8 +1,9 @@
 # Soroban RPC vs KMP Stellar SDK Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:31
-
-**SDK Version:** 1.3.1
+**RPC Version:** v26.0.0 (released 2026-04-03)  
+**RPC Source:** [https://github.com/stellar/stellar-rpc/releases/tag/v26.0.0](https://github.com/stellar/stellar-rpc/releases/tag/v26.0.0)  
+**SDK Version:** 1.3.1  
+**Generated:** 2026-04-04 00:01:12
 
 ## Overall Coverage
 
@@ -14,18 +15,35 @@
 
 ## Method Comparison
 
-| RPC Method | Status | Kotlin Method | Required Params | Optional Params | Notes |
+| RPC Method | Status | Kotlin Method | Required Params | Response Fields | Notes |
 |------------|--------|---------------|-----------------|-----------------|-------|
-| `getEvents` | ✅ Fully Supported | `getEvents` | N/A | N/A | All parameters implemented |
-| `getFeeStats` | ✅ Fully Supported | `getFeeStats` | N/A | N/A | All parameters implemented |
-| `getHealth` | ✅ Fully Supported | `getHealth` | N/A | N/A | All parameters implemented |
-| `getLatestLedger` | ✅ Fully Supported | `getLatestLedger` | N/A | N/A | All parameters implemented |
-| `getLedgerEntries` | ✅ Fully Supported | `getLedgerEntries` | N/A | N/A | All parameters implemented |
-| `getLedgers` | ✅ Fully Supported | `getLedgers` | N/A | N/A | All parameters implemented |
-| `getNetwork` | ✅ Fully Supported | `getNetwork` | N/A | N/A | All parameters implemented |
-| `getTransaction` | ✅ Fully Supported | `getTransaction` | N/A | N/A | All parameters implemented |
-| `getTransactions` | ✅ Fully Supported | `getTransactions` | N/A | N/A | All parameters implemented |
-| `getVersionInfo` | ✅ Fully Supported | `getVersionInfo` | N/A | N/A | All parameters implemented |
-| `sendTransaction` | ✅ Fully Supported | `sendTransaction` | N/A | N/A | All parameters implemented |
-| `simulateTransaction` | ✅ Fully Supported | `simulateTransaction` | N/A | N/A | All parameters implemented |
+| `getEvents` | ✅ Fully Supported | `getEvents` | 1/1 | 6/6 | All parameters and response fields implemented |
+| `getFeeStats` | ✅ Fully Supported | `getFeeStats` | N/A | 3/3 | All parameters and response fields implemented |
+| `getHealth` | ✅ Fully Supported | `getHealth` | N/A | 4/4 | All parameters and response fields implemented |
+| `getLatestLedger` | ✅ Fully Supported | `getLatestLedger` | N/A | 6/6 | All parameters and response fields implemented |
+| `getLedgerEntries` | ✅ Fully Supported | `getLedgerEntries` | 1/1 | 2/2 | All parameters and response fields implemented |
+| `getLedgers` | ✅ Fully Supported | `getLedgers` | 1/1 | 6/6 | All parameters and response fields implemented |
+| `getNetwork` | ✅ Fully Supported | `getNetwork` | N/A | 3/3 | All parameters and response fields implemented |
+| `getTransaction` | ✅ Fully Supported | `getTransaction` | 1/1 | 5/5 | All parameters and response fields implemented |
+| `getTransactions` | ✅ Fully Supported | `getTransactions` | 1/1 | 6/6 | All parameters and response fields implemented |
+| `getVersionInfo` | ✅ Fully Supported | `getVersionInfo` | N/A | 5/5 | All parameters and response fields implemented |
+| `sendTransaction` | ✅ Fully Supported | `sendTransaction` | 1/1 | N/A | All parameters and response fields implemented |
+| `simulateTransaction` | ✅ Fully Supported | `simulateTransaction` | 1/1 | N/A | All parameters and response fields implemented |
+
+## Response Field Coverage
+
+Detailed breakdown of response field support per method.
+
+| RPC Method | RPC Fields | SDK Fields | Missing Fields |
+|------------|------------|------------|----------------|
+| `getEvents` | 6 | 6 | - |
+| `getFeeStats` | 3 | 3 | - |
+| `getHealth` | 4 | 4 | - |
+| `getLatestLedger` | 6 | 6 | - |
+| `getLedgerEntries` | 2 | 2 | - |
+| `getLedgers` | 6 | 6 | - |
+| `getNetwork` | 3 | 3 | - |
+| `getTransaction` | 5 | 5 | - |
+| `getTransactions` | 6 | 6 | - |
+| `getVersionInfo` | 5 | 5 | - |
 
diff --git a/compatibility/sep/SEP-0001_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0001_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0001 (Stellar Info File) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:13
 
-**SEP Version:** 2.7.0<br>
-**SEP Status:** Active<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** 2.7.0  
+**SEP Status:** Active  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ The `stellar.toml` file publishes information about an organization's Stellar in
 
 - ✅ **Implemented:** 71/71
 - ❌ **Not Implemented:** 0/71
-- **Required Fields:** 100.0% (3/3)
+
+**Required Fields:** 100.0% (3/3)
+
+**Optional Fields:** 100.0% (68/68)
 
 ## Implementation Status
 
@@ -160,11 +163,20 @@ The `stellar.toml` file publishes information about an organization's Stellar in
 | `HOST` |  | ✅ | `host` | The IP:port or domain:port peers can use to connect to the node |
 | `HISTORY` |  | ✅ | `history` | The location of the history archive published by this validator |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0001!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information

diff --git a/compatibility/sep/SEP-0002_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0002_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0002 (Federation protocol) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:13
 
-**SEP Version:** 1.1.0<br>
-**SEP Status:** Final<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** 1.1.0  
+**SEP Status:** Final  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ The federation protocol resolves human-readable addresses like `name*yourdomain.
 
 - ✅ **Implemented:** 10/10
 - ❌ **Not Implemented:** 0/10
-- **Required Fields:** 100.0% (6/6)
+
+**Required Fields:** 100.0% (6/6)
+
+**Optional Fields:** 100.0% (4/4)
 
 ## Implementation Status
 
@@ -84,11 +87,20 @@ The federation protocol resolves human-readable addresses like `name*yourdomain.
 | `memo_type` |  | ✅ | `memoType` | type of memo to attach to transaction, one of text, id or hash |
 | `memo` |  | ✅ | `memo` | value of memo to attach to transaction, for hash this should be base64-encoded |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0002!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information

diff --git a/compatibility/sep/SEP-0005_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0005_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0005 (Key Derivation Methods for Stellar Keys) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:14
 
-**SEP Version:** N/A<br>
-**SEP Status:** Final<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** N/A  
+**SEP Status:** Final  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ Defines methods for deriving Stellar keypairs from mnemonic phrases, making it e
 
 - ✅ **Implemented:** 31/31
 - ❌ **Not Implemented:** 0/31
-- **Required Fields:** 100.0% (22/22)
+
+**Required Fields:** 100.0% (22/22)
+
+**Optional Fields:** 100.0% (9/9)
 
 ## Implementation Status
 
@@ -134,11 +137,20 @@ Defines methods for deriving Stellar keypairs from mnemonic phrases, making it e
 | `test_vector_4_24words_passphrase` | ✓ | ✅ | `(verified in tests)` | 24-word mnemonic with passphrase test vector: 'cable spray genius state float twenty...' with pas... |
 | `test_vector_5_abandon_about` | ✓ | ✅ | `(verified in tests)` | Known test vector: 'abandon abandon abandon abandon abandon abandon abandon abandon abandon aband... |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0005!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information

diff --git a/compatibility/sep/SEP-0006_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0006_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0006 (Deposit and Withdrawal API) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:14
 
-**SEP Version:** 4.3.0<br>
-**SEP Status:** Active (Interactive components are deprecated in favor of SEP-24)<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** 4.3.0  
+**SEP Status:** Active (Interactive components are deprecated in favor of SEP-24)  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ A programmatic API for anchors and wallets to handle deposits and withdrawals wi
 
 - ✅ **Implemented:** 73/73
 - ❌ **Not Implemented:** 0/73
-- **Required Fields:** 100.0% (4/4)
+
+**Required Fields:** 100.0% (4/4)
+
+**Optional Fields:** 100.0% (69/69)
 
 ## Implementation Status
 
@@ -204,11 +207,20 @@ A programmatic API for anchors and wallets to handle deposits and withdrawals wi
 | `wallet_name` |  | ✅ | `walletName` | (**Deprecated**, optional) In communications / pages about the withdrawal, anchor should display ... |
 | `wallet_url` |  | ✅ | `walletUrl` | (**Deprecated**, optional) Anchor can show this to the user when referencing the wallet involved ... |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0006!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information

diff --git a/compatibility/sep/SEP-0008_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0008_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0008 (Regulated Assets) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:14
 
-**SEP Version:** 1.7.4<br>
-**SEP Status:** Active<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** 1.7.4  
+**SEP Status:** Active  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ Defines how assets that require per-transaction issuer approval are identified,
 
 - ✅ **Implemented:** 32/32
 - ❌ **Not Implemented:** 0/32
-- **Required Fields:** 100.0% (27/27)
+
+**Required Fields:** 100.0% (27/27)
+
+**Optional Fields:** 100.0% (5/5)
 
 ## Implementation Status
 
@@ -167,11 +170,20 @@ Defines how assets that require per-transaction issuer approval are identified,
 | `tx` | ✓ | ✅ | `tx` | Transaction envelope XDR, base64 encoded. This transaction will have both the original signature(... |
 | `message` |  | ✅ | `message` | A human readable string containing information to pass on to the user |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0008!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information

diff --git a/compatibility/sep/SEP-0009_COMPATIBILITY_MATRIX.md b/compatibility/sep/SEP-0009_COMPATIBILITY_MATRIX.md
@@ -1,10 +1,10 @@
 # SEP-0009 (Standard KYC Fields) Compatibility Matrix
 
-**Generated:** 2026-04-03 17:48:35
+**Generated:** 2026-04-04 00:01:15
 
-**SEP Version:** 1.17.0<br>
-**SEP Status:** Active<br>
-**SDK Version:** 1.3.1<br>
+**SEP Version:** 1.17.0  
+**SEP Status:** Active  
+**SDK Version:** 1.3.1  
 **SEP URL:** https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 
 ## SEP Summary
@@ -17,7 +17,10 @@ A standard list of KYC and financial account fields (names, addresses, ID docume
 
 - ✅ **Implemented:** 76/76
 - ❌ **Not Implemented:** 0/76
-- **Required Fields:** 100% (0/0)
+
+**Required Fields:** 100% (0/0)
+
+**Optional Fields:** 100.0% (76/76)
 
 ## Implementation Status
 
@@ -158,11 +161,20 @@ A standard list of KYC and financial account fields (names, addresses, ID docume
 | `organization.email` |  | ✅ | `email` | Organization contact email |
 | `organization.phone` |  | ✅ | `phone` | Organization contact phone |
 
+## Implementation Gaps
+
+No gaps found! All fields are implemented.
+
+## Recommendations
+
+The SDK has full compatibility with SEP-0009!
+
 ## Legend
 
 - ✅ **Implemented**: Field is fully supported in the SDK
 - ❌ **Not Implemented**: Field is not currently supported
 - ⚠️ **Partial**: Field is partially supported with limitations
+- **Server**: Server-side only feature (not applicable to client SDKs)
 - ✓ **Required**: Field is required by SEP specification
 
 ## Additional Information