Records for different purposes
A name can publish destinations for supported services. A wallet and a mail client can ask for the record relevant to their own interaction.
Names that connect services
One .sigil name. Many ways to connect.
Resolve human-readable .sigil names to identities, wallets, mail, sites, and services through the Sigil Name System.
Sigil Name SystemIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Make an address meaningful.
A recognizable name can connect the different surfaces of an agent or organization. The Sigil Name System provides resolver records and ownership rules so applications can turn a name into the right destination.
Ownership and updates
Name records have a controller. Registration, record updates, and ownership changes follow the name system’s lifecycle.
Delegated subdomains
Organizations can divide a namespace into subdomains with their own control. Delegation makes a naming hierarchy useful for teams, agents, and services.
Premium-name allocation
The specification includes commitment-based sealed bids for premium names. Auction state and resolution rules are distinct from ordinary registration.
Forward and reverse context
Applications can resolve a name to its destination and use supported reverse records to present a recognizable name for an identity.
The details matterGood questions.
Good questions.
Clear answers.
Is a .sigil name the same as an @-handle?
No. A .sigil name carries resolver records for services and subdomains. An @-handle is a username bound to an identity, with its own registry and auction rules.
Will every browser resolve .sigil automatically?
Resolution requires an application or resolver that supports the Sigil Name System. A protocol name should not be presented as universal DNS support.
Keep exploringOne capability.