# Steg

> Applied research and operations in proof verification, modular verifier design, and Ethereum-anchored trust models

## Docs

- [9. Edge Cases & Client Requirements](/specifications/evm-specification): **Educational Content**: This document presents hypothetical ENSIP-19 integration concepts for research purposes only.
- [Universal Resolver Matrix: Non-EVM Resolution and Architecture](/specifications/non-evm-specification): **Educational Content**: This document presents hypothetical cross-chain resolution concepts for research purposes only.
- [4. AuthResolverImpl](/spec/authresolver): AuthResolverImpl is the **verification orchestration layer** that composes ENSv2 storage and permission primitives into an Authority-tier surface for MARPs. It holds **credential**, **capability**, and **revocation** records under any ENS name and exposes `verifyAction` ([§5](/spec/verify-action)) as the convenience entry point that bundles credential lookup + scheme dispatch + revocation check.
- [9. Deferred beyond v1.0-draft.02](/spec/deferred)
- [Prototype Spec: Verifier + AuthResolverImpl](/spec): **Working copy:** [Google Doc](https://docs.google.com/document/d/1L5Kj7oxT4dzlkYdYh0Sne2jx76XomT7K04P7Bu9zR-w/edit?usp=sharing). The version on this site is the published cut.
- [1. Scope and Non-Goals](/spec): **Working copy:** [Google Doc](https://docs.google.com/document/d/1L5Kj7oxT4dzlkYdYh0Sne2jx76XomT7K04P7Bu9zR-w/edit?usp=sharing). The version on this site is the published cut.
- [2. Composite of Standards](/spec): **Working copy:** [Google Doc](https://docs.google.com/document/d/1L5Kj7oxT4dzlkYdYh0Sne2jx76XomT7K04P7Bu9zR-w/edit?usp=sharing). The version on this site is the published cut.
- [6. Record Schemas (non-normative shape; CBOR field layouts deferred)](/spec/record-schemas): The structs below describe the **conceptual shape** of each record. The CBOR field-level layout (map keys, type tags, ordering) is deferred to a later v1.0-draft revision. A conformant implementation MUST encode/decode these records in CBOR; the specific field encoding is not yet pinned by this revision.
- [10. References](/spec/references): Conformance with this spec depends on these documents. Implementers MUST consult them for the contracts the spec inherits, the role-keyword semantics, and the encoding/standard formats the spec uses.
- [8. Security Considerations](/spec/security): This section is intentionally narrow in this revision. Full threat-model treatment (replay, key-compromise, gateway-trust, governance-capture) is deferred to a later v1.0-draft revision in parallel with the signed-freshness specification.
- [7. End-to-End Verification Flow](/spec/verification-flow): The flow generalizes across all three v1 schemes. The dispatch step (P) varies by `schemeId` on the resolved credential; the rest of the orchestration is identical. The Verifier is a single shared contract; the AuthResolver is per-name.
- [3. Verifier](/spec/verifier): The Verifier is a single shared contract responsible for **signature verification and scheme dispatch only**. It has no records, no roles, no policy state, and no per-name configuration.
- [5. ](/spec/verify-action): A conformant AuthResolverImpl **MUST** expose `verifyAction` with the following signature:
- [DNSSEC Resolution Pattern](/patterns/dnssec-pattern): **DNSSEC Onchain Resolution** enables trustless mapping from DNS domains to ENS names through cryptographic proof validation on Ethereum. This breakthrough allows DNS zones to become first-class participants in the decentralized identity ecosystem, bridging traditional DNS infrastructure with blockchain-based name resolution.
- [EVM Resolution Pattern](/patterns/evm-pattern): **EVM Resolution** enables consistent primary name resolution across all Ethereum Virtual Machine (EVM) compatible blockchains through ENSIP-19. This pattern standardizes how users can set and resolve primary names across multiple EVM chains, creating a unified identity experience.
- [Non-EVM Resolution Pattern](/patterns/non-evm-pattern): **Non-EVM Resolution** extends ENSIP-19 to enable primary name resolution for non-Ethereum Virtual Machine (non-EVM) blockchains including Cosmos, Solana, and other ecosystems. This pattern enables bidirectional identity resolution (address ↔ name) across fundamentally different blockchain architectures.
- [WebAuthn Resolution Pattern](/patterns/webauthn-pattern): **WebAuthn Resolution** integrates Web Authentication (WebAuthn) passkeys with Ethereum Name Service (ENS) to enable hardware-backed identity management. This pattern allows users to control ENS names and authenticate transactions using biometric or hardware security keys instead of traditional private keys.