Stellar standards
How Solva relates to the Stellar Ecosystem Proposals that touch reserves, tokens, oracles, sign-in, addresses and signed messages.
Stellar standards are called Stellar Ecosystem Proposals, or SEPs, and are kept in the stellar-protocol repository. Solva uses some of them and relates to others. The summary table says which.
No SEP standardises reserve coverage today. SEP-1 has a field that links to evidence of reserves, but no SEP defines a coverage record, a status such as covered, short or stale, or a contract call that answers whether a token is covered.
Summary
| Standard | Subject | Solva today |
|---|---|---|
| SEP-1 | stellar.toml, the issuer's info file | Relates. An anchor can link its record from it. |
| SEP-41 | Soroban token interface | Relates. Shapes how token balances are read. |
| SEP-40 | Oracle consumer interface | Relates. is_covered Coming soon follows its read pattern. |
| SEP-10 | Web authentication for Stellar accounts | Relates. Not used for sign-in today. |
| SEP-45 | Web authentication for contract accounts | Relates. The passkey wallet does not use it today. |
| SEP-23 | Strkeys, the text form of keys and addresses | Uses. Every address Solva shows or accepts is a strkey. |
| SEP-53 | Sign and verify messages | Relates. Reserve signatures use a different scheme. |
SEP-1: stellar.toml
SEP-1 defines stellar.toml, the file an issuer publishes on its own domain to describe its organisation and its tokens. Wallets and exchanges read it before they list a token.
Two parts of it touch reserves:
attestation_of_reserveis a URL field for each token, defined as a link to an attestation or other evidence of reserves. It takes any URL and has no fixed format. An anchor sets it to the token's public record page Coming soon, so wallets and exchanges find the record where they already look.- The collateral fields
collateral_addresses,collateral_address_messagesandcollateral_address_signatureslist the accounts that hold the reserves for an anchored crypto token, with a signed statement from each. They prove control of those accounts and carry no balances. The read on chain reserve source reads the balance of Stellar reserve accounts today. Verification of these signatures Coming soon ties those accounts to the token on each cycle. See Where reserve figures come from.
SEP-41: Soroban token interface
SEP-41 is the standard interface for tokens on Soroban, which the Stellar Asset Contract also implements. It has a balance call for an account. It has no call for a token's total supply.
Solva relates to it. The read on chain reserve source reads XLM and issued assets, such as USDC, from Horizon. Through the Stellar Asset Contract those assets are also SEP-41 tokens, with the same balances. Amounts in SEP-41 are whole numbers in the token's smallest unit, which matches how Solva handles every amount.
SEP-40: Oracle consumer interface
SEP-40 defines how contracts read price feeds. It covers prices only and states that other oracle types are outside its scope.
Solva does not implement SEP-40. is_covered follows the same read pattern: a read-only call that any contract can make, with a time on every answer so the caller can judge freshness.
SEP-10 and SEP-45: Web authentication
SEP-10 lets a service confirm that a user controls a Stellar account, by having the user sign a challenge. SEP-45 does the same for contract accounts, such as smart wallets.
Solva relates to both and uses neither today. The passkey smart wallet that owns an institution's registry is a contract account, the kind SEP-45 covers. Today the console checks the passkey in the browser at sign-in, and the passkey approves each wallet action through Soroban authorization. Neither step uses a SEP-45 challenge.
SEP-23: Strkeys
SEP-23 defines the text form of Stellar keys and addresses: G... for accounts and C... for contracts. Solva uses it. Registry addresses, wallet addresses and account addresses throughout Solva and these docs are strkeys.
SEP-53: Sign and verify messages
SEP-53 defines how a Stellar key signs a plain message, so anyone can verify it. It uses ed25519, the signature scheme of Stellar accounts.
Solva relates to it. A custodian signs reserve balances today with ECDSA on the P-256 curve, not with a Stellar key, so SEP-53 does not apply. SEP-1 does not name a format for its collateral signatures, so SEP-53 fits when the reserve accounts are on Stellar.