AN-5747 stellar gold (#3)

* first commit, added all docs but no transformations yet

* added all gold models, plus enhanced (EZ) operations and docs

* Silver incremental logic (#2)

* check in

* check in, gte in progress

* bronze & silver

* updated docs and gold models

* updated working gold models

* adding ez__operations as well

* SO, cluster, fix silver accounts

* updated ez config

* updated ez config formatting (minor)

* changed filenames and dir structure

* fixed and ran ez_operations, updated a line in the readme

---------

Co-authored-by: Mike Stepanovic <mike.stepanovic@flipsidecrypto.com>

README.md

@@ -23,14 +23,13 @@ stellar:
 ```
 
 ### Resources:
+- Learn more about Stellar's [Hubble dataset](https://developers.stellar.org/docs/data/hubble)
 - Learn more about dbt [in the docs](https://docs.getdbt.com/docs/introduction)
 - Check out [Discourse](https://discourse.getdbt.com/) for commonly asked questions and answers
 - Join the [chat](https://community.getdbt.com/) on Slack for live discussions and support
 - Find [dbt events](https://events.getdbt.com) near you
 - Check out [the blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices
 
-- Check out [the blog](https://blog.getdbt.com/) for the latest news on dbt's development and best practices
-
 ## Applying Model Tags
 
 ### Database / Schema level tags
@@ -63,12 +62,12 @@ To add/update a model's snowflake tags, add/modify the `meta` model property und
 By default, model tags are not pushed to snowflake on each load.  You can push a tag update for a model by specifying the `UPDATE_SNOWFLAKE_TAGS` project variable during a run.
 
 ```
-dbt run --var '{"UPDATE_SNOWFLAKE_TAGS":True}' -s models/core/core__fact_swaps.sql
+dbt run --var '{"UPDATE_SNOWFLAKE_TAGS":True}' -s models/core/core__fact_trades.sql
 ```
 
 ### Querying for existing tags on a model in snowflake
 
 ```
 select *
-from table(stellar.information_schema.tag_references('stellar.core.fact_blocks', 'table'));
+from table(stellar.information_schema.tag_references('stellar.core.fact_ledgers', 'table'));
 ```

models/descriptions/__overview__.md

@@ -0,0 +1,75 @@
+{% docs __overview__ %}
+
+# Welcome to the Flipside Crypto's Stellar Models Documentation
+
+## **What does this documentation cover?**
+The documentation included here details the design of Stellar tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/) For more information on how these models are built, please see [the github repository.](https://github.com/flipsideCrypto/stellar-models/)
+
+## **How do I use these docs?**
+The easiest way to navigate this documentation is to use the Quick Links below. These links will take you to the documentation for each table, which contains a description, a list of the columns, and other helpful information.
+
+If you are experienced with dbt docs, feel free to use the sidebar to navigate the documentation, as well as explore the relationships between tables and the logic building them.
+
+There is more information on how to use dbt docs in the last section of this document.
+
+## **Quick Links to Table Documentation**
+
+**Click on the links below to jump to the documentation for each schema.**
+
+### Core Tables (`stellar`.`CORE`.`<table_name>`)
+
+**Dimension Tables:**
+- [core.dim_assets](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.core__dim_assets)
+
+**Fact Tables:**
+- [core.fact_accounts](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.core__fact_accounts)
+- [core.fact_ledgers](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.core__fact_ledgers)
+- [core.fact_operations](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.core__fact_operations)
+- [core.fact_transactions](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.core__fact_transactions)
+
+### DeFi Tables (`stellar`.`DEFI`.`<table_name>`)
+
+**Fact Tables:**
+- [defi.fact_liquidity_pools](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.defi__fact_liquidity_pools)
+- [defi.fact_trades](https://flipsidecrypto.github.io/stellar-models/#!/model/model.stellar_models.defi__fact_trades)
+
+## **Data Model Overview**
+
+These Stellar models are built a few different ways, but the core fact tables are built using three layers of sql models: **bronze, silver, and gold (or core).**
+
+- Bronze: Data is loaded in from the source as a view
+- Silver: All necessary parsing, filtering, de-duping, and other transformations are done here
+- Gold (or core): Final views and tables that are available publicly
+
+The dimension tables are sourced from a variety of on-chain and off-chain sources.
+
+Convenience views (denoted ez_) are a combination of different fact and dimension tables. These views are built to make it easier to query the data.
+
+## **Using dbt docs**
+### Navigation
+
+You can use the ```Project``` and ```Database``` navigation tabs on the left side of the window to explore the models in the project.
+
+### Database Tab
+
+This view shows relations (tables and views) grouped into database schemas. Note that ephemeral models are *not* shown in this interface, as they do not exist in the database.
+
+### Graph Exploration
+
+You can click the blue icon on the bottom-right corner of the page to view the lineage graph of your models.
+
+On model pages, you'll see the immediate parents and children of the model you're exploring. By clicking the Expand button at the top-right of this lineage pane, you'll be able to see all of the models that are used to build, or are built from, the model you're exploring.
+
+Once expanded, you'll be able to use the ```--models``` and ```--exclude``` model selection syntax to filter the models in the graph. For more information on model selection, check out the [dbt docs](https://docs.getdbt.com/docs/model-selection-syntax).
+
+Note that you can also right-click on models to interactively filter and explore the graph.
+
+
+### **More information**
+- [Flipside](https://flipsidecrypto.xyz/)
+- [Velocity](https://app.flipsidecrypto.com/velocity?nav=Discover)
+- [Tutorials](https://docs.flipsidecrypto.com/our-data/tutorials)
+- [Github](https://github.com/FlipsideCrypto/stellar-models)
+- [What is dbt?](https://docs.getdbt.com/docs/introduction)
+
+{% enddocs %}

models/descriptions/account.md

@@ -0,0 +1,3 @@
+{% docs account %}
+The account involved in the operation.
+{% enddocs %}

models/descriptions/account_id.md

@@ -0,0 +1,3 @@
+{% docs account_id %}
+The address of the account. The address is the account's public key encoded in base32. All account addresses start with a 'G'.
+{% enddocs %}

models/descriptions/account_muxed.md

@@ -0,0 +1,3 @@
+{% docs account_muxed %}
+Muxed account identifier.
+{% enddocs %}

models/descriptions/account_sequence.md

@@ -0,0 +1,3 @@
+{% docs account_sequence %}
+Sequence number for the account.
+{% enddocs %}

models/descriptions/address.md

@@ -0,0 +1,3 @@
+{% docs address %}
+Address for Soroban contract creation.
+{% enddocs %}

models/descriptions/amount.md

@@ -0,0 +1,3 @@
+{% docs amount %}
+Float representation of the amount of an asset sent/offered/etc.
+{% enddocs %}

models/descriptions/asset_a_amount.md

@@ -0,0 +1,3 @@
+{% docs asset_a_amount %}
+The raw number of tokens locked in the pool for one of the two asset pairs in the liquidity pool.
+{% enddocs %}

models/descriptions/asset_b_amount.md

@@ -0,0 +1,3 @@
+{% docs asset_b_amount %}
+The raw number of tokens locked in the pool for one of the two asset pairs in the liquidity pool.
+{% enddocs %}

models/descriptions/asset_balance_changes.md

@@ -0,0 +1,3 @@
+{% docs asset_balance_changes %}
+Changes in asset balances.
+{% enddocs %}

models/descriptions/asset_code.md

@@ -0,0 +1,3 @@
+{% docs asset_code %}
+The 4 or 12 character code representation of the asset on the network.
+{% enddocs %}

models/descriptions/asset_id.md

@@ -0,0 +1,3 @@
+{% docs asset_id %}
+The Farm Hash encoding of Asset Code + Asset Issuer + Asset Type. This field is optimized for cross table joins since integer joins are less expensive than the original asset id components.
+{% enddocs %}

models/descriptions/asset_issuer.md

@@ -0,0 +1,3 @@
+{% docs asset_issuer %}
+The account address of the original asset issuer that created the asset.
+{% enddocs %}

models/descriptions/asset_type.md

@@ -0,0 +1,3 @@
+{% docs asset_type %}
+The identifier for type of asset code, can be an alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM.
+{% enddocs %}

models/descriptions/authorize.md

@@ -0,0 +1,3 @@
+{% docs authorize %}
+Indicates whether the trustline is authorized.
+{% enddocs %}

models/descriptions/authorize_to_maintain_liabilities.md

@@ -0,0 +1,3 @@
+{% docs authorize_to_maintain_liabilities %}
+Indicates whether the trustline is authorized for maintaining liabilities.
+{% enddocs %}

models/descriptions/balance.md

@@ -0,0 +1,3 @@
+{% docs balance %}
+The number of units of XLM held by the account.
+{% enddocs %}

models/descriptions/balance_id.md

@@ -0,0 +1,3 @@
+{% docs balance_id %}
+The balance id of the claimable balance.
+{% enddocs %}

models/descriptions/base_fee.md

@@ -0,0 +1,3 @@
+{% docs base_fee %}
+The fee (in stroops) the network charges per operation in a transaction for the given ledger. The minimum base fee is 100, with the ability to increase if transaction demand exceeds ledger capacity. When this occurs, the ledger enters surge pricing.
+{% enddocs %}

models/descriptions/base_reserve.md

@@ -0,0 +1,3 @@
+{% docs base_reserve %}
+The reserve (in stroops) the network requires an account to retain as a minimum balance in order to be a valid account on the network. The current minimum reserve is 10 XLM.
+{% enddocs %}

models/descriptions/batch_id.md

@@ -0,0 +1,3 @@
+{% docs 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.
+{% enddocs %}

models/descriptions/batch_insert_ts.md

@@ -0,0 +1,3 @@
+{% docs 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. The timestamp should not be used during ad hoc analysis and is useful for data engineering purposes.
+{% enddocs %}

models/descriptions/batch_run_date.md

@@ -0,0 +1,3 @@
+{% docs 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.
+{% enddocs %}

models/descriptions/begin_sponsor.md

@@ -0,0 +1,3 @@
+{% docs begin_sponsor %}
+The account address that initiated the sponsorship.
+{% enddocs %}

models/descriptions/bump_to.md

@@ -0,0 +1,3 @@
+{% docs bump_to %}
+The new desired value of the source account's sequence number.
+{% enddocs %}

models/descriptions/buying_account_address.md

@@ -0,0 +1,3 @@
+{% docs buying_account_address %}
+The account address of the buying party.
+{% enddocs %}

models/descriptions/buying_amount.md

@@ -0,0 +1,3 @@
+{% docs buying_amount %}
+The amount of purchased asset that was moved from the seller account into the buying account, reported in terms of the bought asset.
+{% enddocs %}

models/descriptions/buying_asset_code.md

@@ -0,0 +1,3 @@
+{% docs buying_asset_code %}
+The 4 or 12 character code representation of the asset being bought.
+{% enddocs %}

models/descriptions/buying_asset_id.md

@@ -0,0 +1,3 @@
+{% docs buying_asset_id %}
+The identifier of the asset being bought.
+{% enddocs %}

models/descriptions/buying_asset_issuer.md

@@ -0,0 +1,3 @@
+{% docs buying_asset_issuer %}
+The account address of the original asset issuer for the buying asset.
+{% enddocs %}

models/descriptions/buying_asset_type.md

@@ -0,0 +1,3 @@
+{% docs buying_asset_type %}
+The identifier for type of buying asset code.
+{% enddocs %}

models/descriptions/buying_liabilities.md

@@ -0,0 +1,3 @@
+{% docs buying_liabilities %}
+The sum of all buy offers owned by this account for XLM only.
+{% enddocs %}

models/descriptions/buying_offer_id.md

@@ -0,0 +1,3 @@
+{% docs buying_offer_id %}
+The offer ID in the orderbook of the buying offer. If this offer was immediately and fully consumed, this will be a synthetic ID.
+{% enddocs %}

models/descriptions/clawback_enabled.md

@@ -0,0 +1,3 @@
+{% docs clawback_enabled %}
+Indicates whether the asset can be clawed back by the issuer.
+{% enddocs %}

models/descriptions/clear_flags.md

@@ -0,0 +1,3 @@
+{% docs clear_flags %}
+Array of numeric values of flags cleared for a trustline.
+{% enddocs %}

models/descriptions/clear_flags_s.md

@@ -0,0 +1,3 @@
+{% docs clear_flags_s %}
+Array of string values of flags cleared for a trustline.
+{% enddocs %}

models/descriptions/closed_at.md

@@ -0,0 +1,3 @@
+{% docs closed_at %}
+Timestamp when the ledger was closed and committed to the network. Ledgers are expected to close ~every 5 seconds.
+{% enddocs %}

models/descriptions/contract_code_hash.md

@@ -0,0 +1,3 @@
+{% docs contract_code_hash %}
+Hash of Soroban contract code.
+{% enddocs %}

models/descriptions/contract_id.md

@@ -0,0 +1,3 @@
+{% docs contract_id %}
+Soroban contract identifier.
+{% enddocs %}

models/descriptions/core_accounts_id.md

@@ -0,0 +1,3 @@
+{% docs core_accounts_id %}
+Unique identifier for this record
+{% enddocs %}

models/descriptions/d.md

@@ -0,0 +1,3 @@
+{% docs d %}
+Denominator in price ratio calculations.
+{% enddocs %}

models/descriptions/deleted.md

@@ -0,0 +1,3 @@
+{% docs deleted %}
+Indicates whether the ledger entry (account, claimable balance, trust line, offer, liquidity pool) has been deleted or not. Once an entry is deleted, it cannot be recovered.
+{% enddocs %}

models/descriptions/destination_min.md

@@ -0,0 +1,3 @@
+{% docs destination_min %}
+The minimum amount to be received in destination asset.
+{% enddocs %}

models/descriptions/details_json.md

@@ -0,0 +1,3 @@
+{% docs details_json %}
+JSON record containing operation-specific details.
+{% enddocs %}

models/descriptions/extend_to.md

@@ -0,0 +1,3 @@
+{% docs extend_to %}
+Ledger extension target.
+{% enddocs %}

models/descriptions/extra_signers.md

@@ -0,0 +1,3 @@
+{% docs extra_signers %}
+Additional transaction signers.
+{% enddocs %}

models/descriptions/failed_transaction_count.md

@@ -0,0 +1,3 @@
+{% docs failed_transaction_count %}
+The number of failed transactions submitted to the network in this ledger. The transaction was still paid for but contained an error that prevented it from executing
+{% enddocs %}

models/descriptions/fee.md

@@ -0,0 +1,3 @@
+{% docs fee %}
+The number of basis points charged as a percentage of the trade in order to complete the transaction. The fees earned on all trades are divided amongst pool shareholders and distributed as an incentive to keep money in the pools.
+{% enddocs %}

models/descriptions/fee_account.md

@@ -0,0 +1,3 @@
+{% docs fee_account %}
+Account charged the fee.
+{% enddocs %}

models/descriptions/fee_account_muxed.md

@@ -0,0 +1,3 @@
+{% docs fee_account_muxed %}
+Muxed fee account identifier.
+{% enddocs %}

models/descriptions/fee_charged.md

@@ -0,0 +1,3 @@
+{% docs fee_charged %}
+Actual fee charged for the operation.
+{% enddocs %}

models/descriptions/fee_pool.md

@@ -0,0 +1,3 @@
+{% docs fee_pool %}
+The sum of all transaction fees
+{% enddocs %}

models/descriptions/flags.md

@@ -0,0 +1,3 @@
+{% docs flags %}
+Denotes the enabling and disabling of certain asset issuer privileges.
+{% enddocs %}

models/descriptions/from.md

@@ -0,0 +1,3 @@
+{% docs from %}
+The account address from which the payment/contract originates.
+{% enddocs %}

models/descriptions/function.md

@@ -0,0 +1,3 @@
+{% docs function %}
+Function type for invoke_host_function.
+{% enddocs %}

models/descriptions/funder.md

@@ -0,0 +1,3 @@
+{% docs funder %}
+The account address that funds a new account.
+{% enddocs %}

models/descriptions/history_operation_id.md

@@ -0,0 +1,3 @@
+{% docs history_operation_id %}
+The operation id associated with the executed trade. The total amount traded in an operation can be broken up into multiple smaller trades spread across multiple orders by multiple parties.
+{% enddocs %}

models/descriptions/home_domain.md

@@ -0,0 +1,3 @@
+{% docs home_domain %}
+The domain that hosts this account's stellar.toml file.
+{% enddocs %}

models/descriptions/id.md

@@ -0,0 +1,3 @@
+{% docs id %}
+Unique identifier for the ledger
+{% enddocs %}

models/descriptions/inclusion_fee_bid.md

@@ -0,0 +1,3 @@
+{% docs inclusion_fee_bid %}
+Bid for inclusion fee.
+{% enddocs %}

models/descriptions/inclusion_fee_charged.md

@@ -0,0 +1,3 @@
+{% docs inclusion_fee_charged %}
+Actual inclusion fee charged.
+{% enddocs %}

models/descriptions/inflation_destination.md

@@ -0,0 +1,3 @@
+{% docs inflation_destination %}
+Deprecated: The account address to receive an inflation payment when they are disbursed on the network.
+{% enddocs %}

models/descriptions/inner_transaction_hash.md

@@ -0,0 +1,3 @@
+{% docs inner_transaction_hash %}
+A transaction hash of a transaction wrapped with its signatures for fee-bump transactions
+{% enddocs %}

models/descriptions/inserted_timestamp.md

@@ -0,0 +1,3 @@
+{% docs inserted_timestamp %}
+Timestamp when this record was inserted.
+{% enddocs %}

models/descriptions/into.md

@@ -0,0 +1,3 @@
+{% docs into %}
+The account address receiving the deleted account's lumens.
+{% enddocs %}

models/descriptions/invocation_id.md

@@ -0,0 +1,3 @@
+{% docs invocation_id %}
+Unique identifier of the dbt job that inserted or modified this record.
+{% enddocs %}

models/descriptions/last_modified_ledger.md

@@ -0,0 +1,3 @@
+{% docs last_modified_ledger %}
+The ledger sequence number when the ledger entry was last modified. Deletions do not count as a modification and will report the prior modification sequence number.
+{% enddocs %}

models/descriptions/ledger_bounds.md

@@ -0,0 +1,3 @@
+{% docs ledger_bounds %}
+Bounds of the ledger.
+{% enddocs %}

models/descriptions/ledger_entry_change.md

@@ -0,0 +1,3 @@
+{% docs ledger_entry_change %}
+Code that describes the ledger entry change type that was applied to the ledger entry.
+{% enddocs %}

models/descriptions/ledger_hash.md

@@ -0,0 +1,3 @@
+{% docs ledger_hash %}
+The hex-encoded SHA-256 hash that represents the ledger's XDR-encoded form.
+{% enddocs %}

models/descriptions/ledger_header.md

@@ -0,0 +1,3 @@
+{% docs ledger_header %}
+A base64-encoded string of the raw LedgerHeader xdr struct for this ledger
+{% enddocs %}

models/descriptions/ledger_operation_count.md

@@ -0,0 +1,3 @@
+{% docs ledger_operation_count %}
+Number of operations in the ledger.
+{% enddocs %}

models/descriptions/ledger_sequence.md

@@ -0,0 +1,3 @@
+{% docs ledger_sequence %}
+The sequence number of the ledger.
+{% enddocs %}

models/descriptions/limit.md

@@ -0,0 +1,3 @@
+{% docs limit %}
+The upper bound amount of an asset that an account can hold.
+{% enddocs %}

models/descriptions/liquidity_pool_fee.md

@@ -0,0 +1,3 @@
+{% docs liquidity_pool_fee %}
+The percentage fee (in basis points) of the total fee collected by the liquidity pool for executing the trade.
+{% enddocs %}

models/descriptions/liquidity_pool_id.md

@@ -0,0 +1,3 @@
+{% docs liquidity_pool_id %}
+Unique identifier for a liquidity pool. There cannot be duplicate pools for the same asset pair. Once a pool has been created for the asset pair, another cannot be created.
+{% enddocs %}

models/descriptions/liquidity_pools_id.md

@@ -0,0 +1,3 @@
+{% docs liquidity_pools_id %}
+Unique identifier for the liquidity pool record.
+{% enddocs %}

models/descriptions/master_weight.md

@@ -0,0 +1,3 @@
+{% docs master_weight %}
+The weight of the master key, which is the private key for this account. If a master key is '0', the account is locked and cannot be used.
+{% enddocs %}

models/descriptions/max_fee.md

@@ -0,0 +1,3 @@
+{% docs max_fee %}
+Maximum fee for the transaction.
+{% enddocs %}

models/descriptions/max_price.md

@@ -0,0 +1,3 @@
+{% docs max_price %}
+Maximum exchange rate for deposit operation.
+{% enddocs %}

models/descriptions/max_price_r.md

@@ -0,0 +1,3 @@
+{% docs max_price_r %}
+A fractional representation of the prices of the two assets in a pool. The n is the numerator (value of asset a) and the d is the denominator (value of asset b).
+{% enddocs %}

models/descriptions/max_tx_set_size.md

@@ -0,0 +1,3 @@
+{% docs max_tx_set_size %}
+The maximum number of operations that Stellar validator nodes have agreed to process in a given ledger. Since Protocol 11, ledger capacity has been measured in operations rather than transactions.
+{% enddocs %}

models/descriptions/memo.md

@@ -0,0 +1,3 @@
+{% docs memo %}
+Memo content of the transaction.
+{% enddocs %}

models/descriptions/memo_type.md

@@ -0,0 +1,3 @@
+{% docs memo_type %}
+Type of memo attached to transaction.
+{% enddocs %}

models/descriptions/min_account_sequence.md

@@ -0,0 +1,3 @@
+{% docs min_account_sequence %}
+Minimum account sequence number.
+{% enddocs %}

models/descriptions/min_account_sequence_age.md

@@ -0,0 +1,3 @@
+{% docs min_account_sequence_age %}
+Minimum age of account sequence.
+{% enddocs %}

models/descriptions/min_account_sequence_ledger_gap.md

@@ -0,0 +1,3 @@
+{% docs min_account_sequence_ledger_gap %}
+Minimum gap in ledger sequences.
+{% enddocs %}

models/descriptions/min_price.md

@@ -0,0 +1,3 @@
+{% docs min_price %}
+Minimum exchange rate for deposit operation.
+{% enddocs %}

models/descriptions/min_price_r.md

@@ -0,0 +1,3 @@
+{% docs min_price_r %}
+A fractional representation of the prices of the two assets in a pool. The n is the numerator (value of asset a) and the d is the denominator (value of asset b).
+{% enddocs %}

models/descriptions/modified_timestamp.md

@@ -0,0 +1,3 @@
+{% docs modified_timestamp %}
+Timestamp when this record was last modified.
+{% enddocs %}

models/descriptions/n.md

@@ -0,0 +1,3 @@
+{% docs n %}
+Numerator in price ratio calculations.
+{% enddocs %}

models/descriptions/name.md

@@ -0,0 +1,3 @@
+{% docs name %}
+The key for a data entry in manage data operations.
+{% enddocs %}

models/descriptions/new_max_fee.md

@@ -0,0 +1,3 @@
+{% docs new_max_fee %}
+Updated maximum fee.
+{% enddocs %}

models/descriptions/node_id.md

@@ -0,0 +1,3 @@
+{% docs node_id %}
+The id of winning validator node which is allowed to write transaction set to the network. The winning validator is decided by the network.
+{% enddocs %}

models/descriptions/non_refundable_resource_fee_charged.md

@@ -0,0 +1,3 @@
+{% docs non_refundable_resource_fee_charged %}
+The amount of the resource fee charged for the transaction that is non-refundable.
+{% enddocs %}

models/descriptions/num_sponsored.md

@@ -0,0 +1,3 @@
+{% docs num_sponsored %}
+The number of reserves sponsored for this account (meaning another account is paying for the minimum balance). Sponsored entries do not incur any reserve requirement on the account that owns the entry.
+{% enddocs %}

models/descriptions/num_sponsoring.md

@@ -0,0 +1,3 @@
+{% docs num_sponsoring %}
+The number of reserves sponsored by this account. Entries sponsored by this account incur a reserve requirement.
+{% enddocs %}

models/descriptions/num_subentries.md

@@ -0,0 +1,3 @@
+{% docs num_subentries %}
+The total number of ledger entries connected to this account. Ledger entries include: trustlines, offers, signers, and data entries. (Claimable balances are counted under sponsoring entries, not subentries). Any newly created trustline, offer, signer or data entry will increase the number of subentries by 1. Accounts may have up to 1,000 subentries.
+{% enddocs %}

models/descriptions/offer_id.md

@@ -0,0 +1,3 @@
+{% docs offer_id %}
+The unique id for the offer.
+{% enddocs %}