Here is a step-by-step process of the basic asset verification:
Set home_domain field for your asset issuing account. Clients can look up a stellar.toml from this domain.
This should be in the format of a fully qualified domain name such as example.com, anchor.example.com etc.
DO NOT include scheme (i.e. http or https) and trailing relative path: https:/...
The stellar.toml spec lists the currency description as a string, with no mention of HTML. Clients rendering it will thus treat it as a plain string, so any HTML you include there will not be rendered as you intend.
Federation, which is what stellar.toml is usually used for, is a layer on top of Stellar, and nothing that Stellar itself "uses".
Client applications, typically, look at an account they are interested in, find the homedomain, and use it to build a URL, hopefully pointing to a valid stellar.toml.
If it does, this can be used for finding out meta data about ...
Instead of using the netlify.toml directly, try creating an _headers file in the root directory. Then add:
# the stellar.toml file route
As describe in the documentation, stellar.toml should be in the .well-known folder. So if your domain is DOMAIN, the complete url is
If your react app is served at https://DOMAIN/, then you should make a .well-known folder in the root and add the stellar.toml there.
Yes, you have to create this folder.
Stellar documentation explains it like this:
Here is a real world example that you can try out:
OrbitLens does a good walkthrough of the steps needed.
Ultimately, your asset isn't set as verified because you haven't added a homedomain to the issuing account.
A stellar.toml isn't any good if the network doesn't know how to find it.
The ledger is a collection of entries. Currently there are 4 types of ledger entries. They’re specified in src/xdr/Stellar-ledger-entries.x.
This entry represents an account. In Stellar, everything is built around accounts: transactions are performed by accounts, and ...
Nevermind, I've just realized my mistakes. They're right there: issuer identified twice, status use brackets, is_asset_anchor used brackets and fixed_number used brackets. Hope that helps future inquiries.
Per the documentation here: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
The home_domain is the domain that hosts the .toml file. Serve your toml from the correct domain.
If you don't need the full history, you can easily have it up and running within an hour. In this case you will have details on all accounts and account balances but no details about the whole transaction history prior to the first ledger (block) that was processed by that node.
If you want a COMPLETE_CATCHUP=true containing the whole history from ledger #1 ...
You can enter the docker container with docker exec -it stellar /bin/bash
Then enter supervisorctl
and then enter stop stellar-core. This will stop stellar-core.
Enter exit to exit supervisor.
Then edit the stellar-core.cfg file in the base directory of the docker container.
Type supervisorctl again and type start stellar-core
We have successfully customized our stellar-core configuration by following the documentation of https://hub.docker.com/r/stellar/quickstart/
To customize the configurations that both stellar-core and horizon use, you must use persistent mode. The default configurations will be copied into the data directory upon launching a persistent mode container for ...
We are using custom coins only so why should be activate account using XML?
The network need to lock base reserve and charge minimum transaction fees to prevent transactions spamming by bad actors. It's essential because all transactions end up in history archives and operational databases, resulting in significant blockchain size increase. Validators have ...