Stellar assets are defined by who issued them, what they represent, and the terms and conditions for their use. These should all be defined and made public by the issuer in a [Stellar info file](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md). It’s crucial to provide clear information about what it represents. On Stellar, you do that by linking your issuing account to a home domain, publishing a Stellar info file on that domain, and making sure that file is complete and accurate. The most successful asset issuers give exchanges, wallets, and potential buyers lots of information about themselves in order to establish trust. Completing your Stellar info file is not a step you can skip. ## What is a Stellar info file? A Stellar info file is a common place where the Internet can find information about your organization’s Stellar integration. You write it in TOML, a simple and widely used configuration file format designed to be readable by both humans and machines, and publish it at `https://YOUR_DOMAIN/.well-known/stellar.toml`. That way, everyone knows where to find it, anyone can look it up, and it proves that the owner of the HTTPS domain hosting the `stellar.toml` claims responsibility for the accounts and assets listed in it. Using a `set_options` operation, you can link your Stellar account to the domain that hosts your Stellar info file, thereby creating a definitive on-chain connection between this information and that account. ## Completing your `stellar.toml` The first Stellar Ecosystem Proposal (SEP) is [SEP-1: Stellar Info File](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) and specifies everything you would ever need to include in your Stellar info file. This section will walk through the sections of SEP-1 that relate to asset issuers. Use this section in conjunction with the SEP to ensure you complete your `stellar.toml` correctly. The four sections we’ll cover are: 1. General Information 2. Organization Documentation 3. Point of Contact Documentation 4. Currency Documentation For each of those sections, we’ll let you know which fields are required, meaning all asset issuers must include them to be listed by exchanges and wallets, and which fields are suggested. Completing suggested fields is a good way to make your asset stand out. **Note:** it's a good idea to keep the sections in the order presented in SEP-1: Stellar Info File, which is also the order they're presented here. TOML requires arrays to be at the end, so if you scramble the order, you may cause errors for TOML parsers. ### 1. General Information Required field for all asset issuers: - `ACCOUNTS`: A list of public keys for all the Stellar accounts associated with your asset. Listing your public keys lets users confirm that you own them. For example, when [google.com](https://google.com) hosts a `stellar.toml` file, users can be sure that only the accounts listed on it belong to Google. If someone then says, "You need to pay your Google bill this month, send payment to address GIAMGOOGLEIPROMISE", but that key is not listed on Google's `stellar.toml`, then users know not to trust it. There are several fields where you list information about your Stellar integration to aid in discoverability. If you are an anchor service, and you have set up infrastructure to interoperate with wallets and allow for in-app deposit and withdrawal of assets, make sure to include the locations of your servers on your `stellar.toml` file so those wallets know where to find relevant endpoints to query. In particular, list these: #### Suggested fields for asset issuers: - `TRANSFER_SERVER` if you support [SEP-6: Deposit and Withdrawal API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) - `TRANSFER_SERVER_SEP0024` if you support [SEP-24: Interactive Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) - `KYC_SERVER` if you support [SEP-12: KYC API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md) - `WEB_AUTH_ENDPOINT` if you support [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) - `DIRECT_PAYMENT_SERVER` if you support [SEP-31: Cross-Border Payments API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md) If you support other Stellar Ecosystem Proposals — such as federation or delegated signing — or host a public Horizon instance that other people can use to query the ledger, you should also add the location of those resources to [General Information](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md#general-information) so they're discoverable. ### 2. Organization Documentation Basic information about your organization goes into a TOML table called [`DOCUMENTATION`]. Organization Documentation is your chance to inform exchanges and buyers about your business and to demonstrate that your business is legitimate and trustworthy. #### Required field for all asset issuers: - `ORG_NAME` The legal name of your organization, and if your business has one, its official ORG_DBA. - `ORG_URL` The HTTPS URL of your organization's official website. In order to prove the website is yours, you must host your `stellar.toml` on the same domain you list here. That way, exchanges and buyers can view the SSL certificate on your website and feel reasonably confident that you are who you say you are. - `ORG_LOGO` A URL to a company logo, which will show up next to your organization on exchanges. This image should be a square aspect ratio transparent PNG, ideally of size 128x128. If you fail to provide a logo, the icon next to your organization will appear blank on many exchanges. - `ORG_PHYSICAL_ADDRESS` The physical address of your organization. We understand you might want to keep your work address private. At the very least, you should put the city and country in which you operate. A street address is ideal and provides a higher level of trust and transparency to your potential asset holders. - `ORG_OFFICIAL_EMAIL` The best business email address for your organization. This should be hosted at the same domain as your official website. - `ORG_SUPPORT_EMAIL` The best email for support requests. #### Suggested fields for asset issuers: - `ORG_GITHUB` Your organization's official Github account. - `ORG_KEYBASE` Your organization's official Keybase account. Your Keybase account should contain proof of ownership of any public online accounts you list here, including your organization's domain. - `ORG_TWITTER` Your organization's official Twitter handle. - `ORG_DESCRIPTION` A description of your organization. This is fairly open-ended, and you can write as much as you want. It's a great place to distinguish yourself by describing what it is that you do. Issuers that list verified information including phone/address attestations and Keybase verifications are prioritized by Stellar clients. ### 3. Point of Contact Documentation Information about the primary point(s) of contact for your organization goes into a TOML [array of tables](https://github.com/toml-lang/toml#array-of-tables) called `[[PRINCIPALS]]`. You need to put contact information for at least one person in your organization. If you don't, exchanges can't verify your offering, and it is unlikely that buyers will be interested. Multiple principals can be added with additional `[[PRINCIPALS]]` entries. #### Required field for all asset issuers: - `name` The name of the primary contact. - `email` The primary contact's official email address. This should be hosted at the same domain as your organization's official website. #### Suggested fields for asset issuers: - `github` The personal Github account of the point of contact. - `twitter` The personal Twitter handle of the point of contact. - `keybase` The personal Keybase account for the point of contact. This account should contain proof of ownership of any public online accounts listed here and may contain proof of ownership of your organization's domain. ### 4. Currency Documentation Information about the asset(s) you issue goes into a TOML [array of tables](https://github.com/toml-lang/toml#array-of-tables) called `[[CURRENCIES]]`. If you issue multiple assets, you can include them all in one `stellar.toml`. Each asset should have its own `[[CURRENCIES]]` entry. (These entries are also used for assets you support but don’t issue, but as this section focuses on issuing assets the language will reflect that.) #### Required field for all asset issuers: - `code` The asset code. This is one of two key pieces of information that identify your token. Without it, your token cannot be listed anywhere. - `issuer` The Stellar public key of the issuing account. This is the second key piece of information that identifies your token. Without it, your token cannot be listed anywhere. - `is_asset_anchored` An indication of whether your token is anchored or native: true if your token can be redeemed for an asset outside the Stellar network, false if it can’t. Exchanges use this information to sort tokens by type in listings. If you fail to provide it, your token is unlikely to show up in filtered market views. If you're issuing anchored (tethered, stablecoin, asset-backed) tokens, there are several additional required fields: - `anchor_asset_type` The type of asset your token represents. The possible categories are fiat, crypto, stock, bond, commodity, realestate, and other. - `anchor_asset` The name of the asset that serves as the anchor for your token. - `redemption_instructions` Instructions to redeem your token for the underlying asset. - `attestation_of_reserve` A URL to attestation or other proof, evidence, or verification of reserves, such as third-party audits, which all issuers of stablecoins should offer to adhere to best practices. #### Suggested fields for asset issuers: - `desc` A description of your token and what it represents. This is a good place to clarify what your token does and why someone might want to own it. - `conditions` Any conditions you place on the redemption of your token. - `image` A URL to a PNG or GIF image with a transparent background representing your token. Without it, your token will appear blank on many exchanges. ## How to publish your Stellar info file After you've followed the steps above to complete your Stellar info file, post it at the following location: `https://YOUR_DOMAIN/.well-known/stellar.toml` Enable CORS so people can access this file from other sites, and set the following header for an HTTP response for a `/.well-known/stellar.toml` file request. `Access-Control-Allow-Origin:` \* Set a `text/plain` content type so that browsers render the contents rather than prompting for a download. `content-type: text/plain` You should also use the `set_options` operation to set the home domain on your issuing account. ```nginx title="Configure stellar.toml for nginx" server { server_name my.example.com; root /var/www/my.example.com; location = /.well-known/stellar.toml { types { } default_type "text/plain; charset=utf-8"; allow all; if ($request_method = 'OPTIONS') { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS'; add_header 'Content-Length' 0; return 204; } if ($request_method = 'GET') { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS'; add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range'; } } // CertBot SSL configuration // ... } ``` ## Sample code to set the home domain of your issuing account ## Sample `stellar.toml` [sep-0001]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md [sep-0020]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md [seps]: https://github.com/stellar/stellar-protocol/tree/master/ecosystem [twilio-guide]: https://support.twilio.com/hc/en-us/articles/223183008-Formatting-International-Phone-Numbers