user-interface

AI-Generated Content

This comprehensive explanation has been generated from 178 GitHub source documents. All source documents are searchable here.

Last updated: October 7, 2025

This content is meant to be consumed by AI agents via MCP. Click here to get the MCP configuration.
Note: In rare cases it may contain LLM hallucinations.
For authoritative documentation, please consult the official GLEIF vLEI trainings and the ToIP Glossary.

Short Definition

A user interface (UI) is the space where interactions between humans and machines occur, enabling users to control and receive feedback from software systems through visual, auditory, or tactile elements.

No related concepts available

Comprehensive Explanation

user-interface

Definition

A user interface (UI) is the interactive boundary between human users and computer systems, encompassing all elements through which users control software and receive feedback. In the context of digital identity and credential management systems, UIs serve as the primary mechanism through which users interact with cryptographic operations, identifier management, and credential presentations.

Context in KERI/ACDC

Within the KERI ecosystem, user interfaces play a critical role in making complex cryptographic operations accessible to end users:

Browser-Based Interfaces

The signify-browser-extension provides a browser-integrated UI that enables users to:

Manage AIDs (Autonomic Identifiers) directly within their browser
Approve cryptographic signing operations through visual consent workflows
Present verifiable credentials to web applications
Configure signing associations and authentication preferences

This extension architecture separates the trusted UI context (where sensitive operations occur) from untrusted web page contexts, maintaining security boundaries while providing seamless user experience.

Desktop and Mobile Applications

Keep serves as the primary desktop UI for KERI and ACDC systems, providing:

Implementation Notes

UI Architecture Patterns

Browser Extension Security Model

The signify-browser-extension implements a three-layer architecture:

Extension UI (Trusted Zone): Handles sensitive data and user interactions, prohibits external scripts
Background Script: Central message coordinator between extension UI, content scripts, and KERIA agent
Content Script (Untrusted Zone): Injected into web pages to facilitate communication without exposing sensitive operations

Agent Communication

UIs typically communicate with KERI agents through:

Admin Interface (default port 3901): Command and control operations
Boot Interface (default port 3903): Agent provisioning and initialization
Protocol Interface (default port 3902): KERI protocol message routing

User Consent Workflows

KERI UIs implement explicit consent patterns:

Users must approve each signing operation
Credential presentations require user selection and confirmation
Auto-signin features require prior user configuration
Passcode entry occurs within trusted UI contexts only

State Management

UIs must maintain:

Current AID selection state
Available credentials for presentation
Signing associations between AIDs and web applications
Keystore unlock status

Loading vLEI.wiki

user-interface

Short Definition

Comprehensive Explanation

user-interface

Definition

Context in KERI/ACDC

Browser-Based Interfaces

Desktop and Mobile Applications

Implementation Notes

UI Architecture Patterns

Browser Extension Security Model

Agent Communication

User Consent Workflows

State Management

Agent Communication

Security Considerations

Loading vLEI.wiki

Short Definition

Related Concepts

Comprehensive Explanation

user-interface

Definition

Context in KERI/ACDC

Browser-Based Interfaces

Desktop and Mobile Applications

Implementation Notes

UI Architecture Patterns

Browser Extension Security Model

Agent Communication

User Consent Workflows

State Management

Agent Communication

Security Considerations

Related Terms