We will be redesigning the Nodes section of the Dashboard really soon so it's very likely that the "verified node" will be gone.
The reason we added a "verified node" badge was that we wanted to list both:
the companies we work with (like IBM)
nodes run by developers from our community (we often don't know outside our Slack).
By adding a special badge to ...
I am one of the devs at Stellarport. The verified status means (like you are alluding to) that the domain has verified that it has indeed issued this asset.
For example, any stellar account can issue a MOBI asset and add mobius.network as its home domain. How should you (the user) differentiate between the real MOBI and a fake MOBI?
Enter verification - ...
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:/...
You will need to verify the signature against the signing key (account ID). You can take a look at how the compliance server implements signature verification.
Copying over the code (Golang) here for convenience:
// VerifySignature verifies if signature is valid. It makes a network connection
// to sender server in order to obtain stellar.toml file and ...
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.
First and foremost check out this. Good explanation of how assets are verified.
Also, I have just setup my own coin to play around with this verification process.
The steps I took:
Add Stellar.TOML to my web domain
Add domain to my issuing account
Here is my asset on Stellarport: https://portal.stellarport.io/exchange/alphanum12/RobCoin/...
Yes, HTTPS is a must. The issuing account home domain should be specified in TLD format without protocol (your.domain.com, not the https://your.domain.com/).
If your stellar.toml has correct format and is served with CORS headers, you are good to go.
Beyond that, check Stellar Ecosystem Proposals, a set of recommended best practices for Stellar ecosystem. ...