Refresh Hubble data dictionary against crypto-stellar

Reconcile the Hubble data catalog with the live crypto-stellar BigQuery
datasets and the current stellar-dbt-public models. BigQuery is treated as
authoritative for which columns exist and their types; the dbt docs blocks
are authoritative for descriptions.

Add six tables that were missing from the catalog:

- gold/account-balances-daily-agg (crypto_stellar_dbt.account_balances__daily_agg)
- gold/soroban-core-metrics (crypto_stellar_dbt.soroban_core_metrics)
- silver/config-settings-snapshot (crypto_stellar_dbt.config_settings_snapshot)
- silver/reflector-prices-data-{cex,fex,sdex}-snapshot (snapshots.*)

token_transfers is deliberately excluded: the model lives in
stellar-dbt-public but only materializes to hubble-261722.sdf_marts when the
internal project runs it as a package, so it is not public data.

Notable corrections:

- tvl_agg documented accounts_tvl_usd / total_tvl_usd as USD-denominated. The
  real columns are accounts_tvl / total_tvl in raw token amounts, and the
  asset dimensions and liquidity_pools_tvl were missing entirely. The page had
  no dbt docs link, which is why the drift went unnoticed.
- history-effects carried a duplicate 157-line column table outside the styled
  div, a leftover from the catalog reorg (#1785). The two copies disagreed on
  a column name.
- details.authorized_to_maintain_liabilites is spelled without the second "i"
  in the warehouse; the docs used the correct English spelling, which would
  break queries.
- config_settings had three stale pre-rename rows (min_temp_entry_ttl,
  min_persistent_entry_ttl, max_entries_to_ttl) whose current names were
  already documented. Adds 27 Protocol 23/26 columns.
- claimable_balances_current is disabled in stellar-dbt-public and has not
  been written since 2026-07-16; the page now says so.

Author: chowbao

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx

@@ -42,5 +42,6 @@ description: ""
 | batch_run_date | The start date for the batch interval. When taken with the date in the batch_id, the date represents the interval of ledgers processed. The batch run date can be seen as a proxy of closed_at for a ledger. | datetime |  | Yes | The table is partitioned on batch_run_date. It is recommended to always include the batch_run_date in the filter if possible to help reduce query cost. |
 | batch_insert_ts | The timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfill | timestamp |  | Yes |  |
 | asset_id | Unique identifier for asset_code, asset_issuer | integer |  | No |  |
+| balance_id_strkey | The StrKey (`B...`) representation of the claimable balance id. | string |  | No | Introduced alongside [CAP-38](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md) style StrKey encodings. Prefer this over the raw hex `balance_id` when joining to Horizon or RPC responses. |
 
 </div>

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx

@@ -51,12 +51,9 @@ description: ""
 | contract_data_key_size_bytes | Max size of contract data keys | integer |  | No |  |
 | contract_data_entry_size_bytes | Max size of contract data entries | integer |  | No |  |
 | max_entry_ttl | Max TTL that can be set for an entry (sequence created at + this) | integer |  | No |  |
-| min_temp_entry_ttl | Min temporary entry TTL (sequence created at + this) | integer |  | No |  |
-| min_persistent_entry_ttl | Min persistent entry TTL (sequence created at + this) | integer |  | No |  |
 | auto_bump_ledgers | Automatic bump ledgers amount | integer |  | No |  |
 | persistent_rent_rate_denominator | Persistent entry rent rate denominator | integer |  | No |  |
 | temp_rent_rate_denominator | Temporary entry rent rate denominator | integer |  | No |  |
-| max_entries_to_ttl | Max entries to TTL | integer |  | No |  |
 | bucket_list_size_window_sample_size | Bucket list size window sample size | integer |  | No |  |
 | eviction_scan_size | Eviction scan size | integer |  | No |  |
 | starting_eviction_scan_level | Starting eviction scan level | integer |  | No |  |
@@ -73,5 +70,32 @@ description: ""
 | batch_insert_ts | The timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfill | timestamp |  | Yes |  |
 | closed_at | Timestamp in UTC when this ledger closed and committed to the network. Ledgers are expected to close ~every 5 seconds | timestamp |  | Yes |  |
 | ledger_sequence | The sequence number of this ledger. It represents the order of the ledger within the Stellar blockchain. Each ledger has a unique sequence number that increments with every new ledger, ensuring that ledgers are processed in the correct order. | integer |  | Yes |  |
+| ledger_max_disk_read_entries | Maximum number of ledger entries a single ledger may read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `ledger_max_read_ledger_entries`, which now covers in-memory state only. |
+| ledger_max_disk_read_bytes | Maximum number of bytes a single ledger may read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `ledger_max_read_bytes`. |
+| tx_max_disk_read_entries | Maximum number of ledger entries a single transaction may read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `tx_max_read_ledger_entries`. |
+| tx_max_disk_read_bytes | Maximum number of bytes a single transaction may read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `tx_max_read_bytes`. |
+| fee_disk_read_ledger_entry | Fee in stroops charged per ledger entry read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `fee_read_ledger_entry`. |
+| fee_disk_read_1kb | Fee in stroops charged per 1KB read from disk. | integer |  | No | Protocol 23 (CAP-62/63) successor to `fee_read_1kb`. |
+| fee_write_1kb | Fee in stroops charged per 1KB written to the live Soroban state. | integer |  | No | Protocol 23 rename of the bucket-list write fee. |
+| soroban_state_target_size_bytes | Target size in bytes of the live Soroban state, used as the inflection point for rent fee growth. | integer |  | No | Protocol 23 successor to `bucket_list_target_size_bytes`. |
+| rent_fee_1kb_soroban_state_size_low | Rent fee in stroops per 1KB when the live Soroban state is below the target size. | integer |  | No | Protocol 23 successor to `write_fee_1kb_bucket_list_low`. |
+| rent_fee_1kb_soroban_state_size_high | Rent fee in stroops per 1KB when the live Soroban state is above the target size. | integer |  | No | Protocol 23 successor to `write_fee_1kb_bucket_list_high`. |
+| soroban_state_rent_fee_growth_factor | Multiplier applied to the rent fee once the live Soroban state exceeds the target size. | integer |  | No | Protocol 23 successor to `bucket_list_write_fee_growth_factor`. |
+| live_soroban_state_size_window_sample_size | Number of samples retained in the sliding window used to average the live Soroban state size. | integer |  | No | Protocol 23 successor to `bucket_list_size_window_sample_size`. |
+| live_soroban_state_size_window_sample_period | Number of ledgers between samples of the live Soroban state size. | integer |  | No |  |
+| live_soroban_state_size_window | The sliding window of sampled live Soroban state sizes used to compute rent fees. | array[integer] |  | No | Protocol 23 successor to `bucket_list_size_window`. Repeated field. |
+| ledger_max_dependent_tx_clusters | Maximum number of dependent transaction clusters per ledger. | integer |  | No | Protocol 23 parallel compute setting. |
+| tx_max_footprint_entries | Maximum number of footprint entries per transaction. | integer |  | No | Protocol 23 ledger cost extension. |
+| ledger_target_close_time_milliseconds | Target ledger close time in milliseconds. | integer |  | No | Protocol 23 SCP timing setting. |
+| nomination_timeout_initial_milliseconds | Initial SCP nomination timeout in milliseconds. | integer |  | No | Protocol 23 SCP timing setting. |
+| nomination_timeout_increment_milliseconds | SCP nomination timeout increment in milliseconds. | integer |  | No | Protocol 23 SCP timing setting. |
+| ballot_timeout_initial_milliseconds | Initial SCP ballot timeout in milliseconds. | integer |  | No | Protocol 23 SCP timing setting. |
+| ballot_timeout_increment_milliseconds | SCP ballot timeout increment in milliseconds. | integer |  | No | Protocol 23 SCP timing setting. |
+| frozen_ledger_keys | Array of base64-encoded ledger keys frozen by validator governance. | array[string] |  | No | Protocol 26 ([CAP-77](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0077.md)). Repeated field. |
+| frozen_ledger_keys_to_freeze | Array of base64-encoded ledger keys to freeze in this delta update. | array[string] |  | No | Protocol 26 (CAP-77). Repeated field. |
+| frozen_ledger_keys_to_unfreeze | Array of base64-encoded ledger keys to unfreeze in this delta update. | array[string] |  | No | Protocol 26 (CAP-77). Repeated field. |
+| freeze_bypass_txs | Array of hex-encoded transaction hashes that bypass frozen key restrictions. | array[string] |  | No | Protocol 26 (CAP-77). Repeated field. |
+| freeze_bypass_txs_to_add | Array of hex-encoded transaction hashes to add to the freeze bypass list. | array[string] |  | No | Protocol 26 (CAP-77). Repeated field. |
+| freeze_bypass_txs_to_remove | Array of hex-encoded transaction hashes to remove from the freeze bypass list. | array[string] |  | No | Protocol 26 (CAP-77). Repeated field. |
 
 </div>

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx

@@ -40,5 +40,6 @@ description: ""
 | n_imports | Number of imports in contract code | integer |  |  |  |
 | n_exports | Number of exports in contract code | integer |  |  |  |
 | n_data_segment_bytes | Number of data segment bytes in contract code | integer |  |  |  |
+| ledger_key_hash_base_64 | The base64-encoded representation of the ledger key hash for this contract code entry. | string |  | No | Same value as `ledger_key_hash`, encoded in base64 instead of hex. |
 
 </div>

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx

@@ -41,5 +41,6 @@ description: ""
 | val | The encoded value associated with the key in the contract data. The encoded val has two components (type and value) where type describes the data type and the value describes the encoded value of the data type for the contract data | json |  |  |  |
 | val_decoded | The human-readable or decoded version of the value. This provides a clear and understandable representation of the value, making it easier to interpret and use in analysis | json |  |  |  |
 | contract_data_xdr | The XDR (External Data Representation) encoding of the contract data. XDR is a standard format used to serialize and deserialize data, ensuring interoperability across different systems. This field contains the raw, serialized contract data in XDR format | string |  |  |  |
+| ledger_key_hash_base_64 | The base64-encoded representation of the ledger key hash for this contract data entry. | string |  | No | Same value as `ledger_key_hash`, encoded in base64 instead of hex. |
 
 </div>

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx

@@ -23,5 +23,6 @@ description: ""
 | is_evicted | If true, the ledger key hash has been evicted | boolean |  |
 | closed_at | The UNIX timestamp of the sequence number's age | timestamp |  | Yes |  |
 | ledger_sequence | The sequence number of this ledger. It represents the order of the ledger within the Stellar blockchain. Each ledger has a unique sequence number that increments with every new ledger, ensuring that ledgers are processed in the correct order. | integer |  | Yes |  |
+| is_evicted | Status flag indicating whether an entry is evicted or not. `false` signifies the key has been restored. | boolean |  | Yes |  |
 
 </div>

docs/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx

@@ -19,13 +19,14 @@ description: ""
 
 | Name | Description | Data Type | Domain Values | Required? | Notes |
 | --- | --- | --- | --- | --- | --- |
-| id | Unique identifier for the asset code, type and issuer combination. This is not a primary key on the table | float |  | Yes | Deprecated |
 | asset_id | Unique identifier for asset_code, asset_issuer | integer |  | No |  |
 | asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul> | Yes | XLM is the native asset to the network. XLM has no asset code or issuer representation and will instead be displayed with an asset type of 'native' |
 | asset_code | The 4 or 12 character code representation of the asset on the network | string |  | No | Asset codes have no guarantees of uniqueness. The combination of asset code, issuer and type represents a distinct asset |
 | asset_issuer | The account address of the original asset issuer that created the asset | string |  | No |  |
 | batch_id | String representation of the run id for a given DAG in Airflow. Takes the form of `scheduled__<batch_end_date>-<dag_alias>`. Batch ids are unique to the batch and help with monitoring and rerun capabilities | string |  | Yes |  |
 | batch_run_date | The start date for the batch interval. When taken with the date in the batch_id, the date represents the interval of ledgers processed. The batch run date can be seen as a proxy of closed_at for a ledger. | datetime |  | Yes | The table is partitioned on batch_run_date. It is recommended to always include the batch_run_date in the filter if possible to help reduce query cost. |
 | batch_insert_ts | The timestamp in UTC when a batch of records was inserted into the database. This field can help identify if a batch executed in real time or as part of a backfill | timestamp |  | Yes |  |
+| ledger_sequence | The sequence number of the ledger in which this asset was first seen. | integer |  | Yes |  |
+| closed_at | Timestamp in UTC when the ledger in which this asset was first seen closed and committed to the network. Ledgers are expected to close ~every 5 seconds. | timestamp |  | Yes |  |
 
 </div>