> ## Documentation Index
> Fetch the complete documentation index at: https://developers.stellar.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Signers

> Reference documentation for the Account Signers table in Hubble's Bronze data dictionary.

## Table Metadata

| Property | Configuration |
| - | - |
| Natural Key(s) | account\_id, signer, closed\_at |
| Partition Field(s) | batch\_run\_date (MONTH partition) |
| Clustered Field(s) | account\_id, signer, last\_modified\_ledger |
| Documentation | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.account_signers) |

## Column Details

| Name | Description | Data Type | Domain Values | Required? | Notes |
| - | - | - | - | - | - |
| account\_id | The unique identifier of the account. | string | | Yes | |
| signer | The address of the account that is allowed to authorize (sign) transactions for another account. This process is called multi-sig. | string | | Yes | |
| weight | The numeric weight of the signer. All weights on a transaction are added up and used to determine if a transaction meets the threshold requirements to complete the transaction. | float | | Yes | |
| sponsor | The account address of the sponsor who is paying the reserves for this ledger entry. | string | | No | |
| last\_modified\_ledger | The ledger sequence number when the ledger entry (this unique signer for the account) was modified. Deletions do not count as a modification and will report the prior modification sequence number | integer | | Yes | |
| ledger\_entry\_change | Code that describes the ledger entry change type that was applied to the ledger entry. | integer | | Yes | |
| deleted | Indicates whether the ledger entry (balance id) has been deleted or not. Once an entry is deleted, it cannot be recovered. | boolean | | Yes | |
| 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 | |
| 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 | |