Skip to main content

​
Overview

SEP-1 (Stellar Info File) allows wallets and other Stellar applications to discover information about your anchor service. By hosting a stellar.toml file at /.well-known/stellar.toml, you enable applications to automatically find:
  • Your organization’s information
  • Supported assets and currencies
  • Authentication endpoints (SEP-10)
  • SEP endpoints for SEP-6, SEP-24, SEP-31, SEP-38, SEP-45
For details, please refer to the SEP-1 specification.

​
Creating Your stellar.toml File

Create a stellar.toml file with your service information. Here’s a minimal example to get started:
For a complete list of all available stellar.toml attributes, see the SEP-1 specification. You’ll need to add additional sections like [[CURRENCIES]], TRANSFER_SERVER, TRANSFER_SERVER_SEP0024, WEB_AUTH_ENDPOINT, WEB_AUTH_FOR_CONTRACTS_ENDPOINT, DIRECT_PAYMENT_SERVER etc., as you configure the supported assets and other SEPs.
Production vs. Development: You’ll need separate stellar.toml files for testnet and mainnet:
  • Testnet: Use NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
  • Mainnet: Use NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
Make sure your production file includes your actual Mainnet distribution accounts, signing keys, and production service URLs.

​
Configuration

To enable SEP-1, you need to configure how the Anchor Platform should access your stellar.toml file. The platform supports three methods:

​
Environment Variables

Configure SEP-1 using the following environment variables:
  • SEP1_ENABLED: Set to true to enable SEP-1
  • SEP1_TOML_TYPE: One of file, string, or url
  • SEP1_TOML_VALUE: The value depends on the type (see examples below)
Best for: Production deployments where you manage the file on disk.
When using Docker, mount your stellar.toml file as a volume and reference the path inside the container. For example:
Then set SEP1_TOML_VALUE=/config/stellar.toml in your environment.

​
Method 2: String

Best for: Quick testing, development, or when managing config via environment variables.
When using the string type, ensure your TOML content is properly escaped for your environment file format. For complex configurations, the file type is easier to manage.

​
Method 3: URL

Best for: Dynamic content or when hosting the file externally.
When using the url type, the Anchor Platform will fetch the file on each request. Make sure the URL is accessible from your Anchor Platform server and returns valid TOML content.

​
Accessing Your stellar.toml File

Once configured and enabled, the Anchor Platform automatically serves your stellar.toml file at the standard SEP-1 endpoint:
  • /.well-known/stellar.toml - The primary endpoint (served with Content-Type: text/plain)
  • / - Redirects to /.well-known/stellar.toml when SEP-1 is enabled

​
Testing Your Configuration

After starting the Anchor Platform, verify your configuration:
You should see your stellar.toml content returned as plain text.

​
Alternative: External Hosting

You can also host your stellar.toml file using a static file server like nginx or a CDN. If you choose this approach:
  1. Host the file at https://your-domain.com/.well-known/stellar.toml
  2. Ensure it’s publicly accessible
  3. Make sure your stellar.toml file includes the correct URLs pointing to your Anchor Platform endpoints
The Anchor Platform’s SEP-1 service is optional if you’re hosting the file externally, but it provides a convenient way to manage everything in one place.