A way for Stellar client software to resolve email-like addresses to a stellar address.
The Stellar federation protocol maps Stellar addresses to a unique name spaced string. It’s a way for Stellar client software to resolve email-like addresses such as
name*your_domain.com into account IDs like:
GCFFPIFOYY7Z...TK6T32V37KEJU. Stellar addresses provide an easy way for users to send and receive payments by using a syntax that interoperates across different domains and providers. When sending a payment, you contact a federation server first to determine what Stellar account ID to pay. Luckily, the bridge server does this for you.
To explain it simply, a Stellar Federation Server is a database with the following table structure which maps a Stellar address to a string(
| id | first_name | last_name | friendly_id | |----|------------|-----------|---------------------| | 1 | Tunde | Adebayo | tunde_adebayo | | 2 | Lightrains | Tech | lightrains |
Lightrains Stellar address would be
Stellar Federation Server architecture
Here, your front end app/website will be talking to a intermediate server called
bridge serverwhich will be talking directly to a federation server. Bridge server is responsible for querying the federation server and get corresponding address and send transaction or operation to a stellar core via stellar Horizon server.
Current federation workflow
Currently, in order to resolve a federation address, the client needs to do the following:
- fetch the
https://<domain>/.well-known/stellar.tomland read the
FEDERATION_SERVERentry from it
- fetch the response from the federation server using secure HTTP
GETand required parameters
- proceed with the payment