Technical Activity Report
October 2025
October 2025 focused on Web Authenticator production readiness with 22 PRs implementing passkey/WebAuthn integration, Backup V2 system prototype, state architecture refactoring, and production polish. Development shifted from September’s foundational state refactoring to sophisticated feature completion (backup systems, modern authentication) and production-critical refinements. Supporting libraries received architectural improvements (mnemonic-seeds WASM removal), and smart contract work added account creation with dual key type support (R1/K1) for WebAuthn compatibility.
Key Achievements:
- Implemented passwordless authentication using passkeys enabling modern browser-based security without traditional private keys
- Prototyped Backup V2 system with secure 12-word recovery phrase protection through browser extension
- Added dual key type support (R1/K1) in account creation contracts enabling WebAuthn-based provisioning
- Improved account management with search, filtering, and scrolling for large account lists
- Integrated Wuchale for internationalization enabling multi-language support
- Simplified mnemonic-seeds library by removing WASM dependency improving portability
- Released WharfKit bundle package simplifying multi-library integration
Technical Significance: October marked critical production readiness milestone for Web Authenticator with sophisticated feature completion building on September’s architectural foundation. This work demonstrates the technology maturation described in the month-end blog post “What I see next for Vaulta/Antelope” (published Oct 29), which positions Web Authenticator as exemplifying the “fourth cycle”: infrastructure-building complete, ready for product deployment. Passkey/WebAuthn integration represents major UX advancement enabling mainstream adoption through familiar device authentication. Backup V2 system with 30-comment design discussion demonstrates careful approach to security-critical features. Coordinated smart contract work enabling R1 key support creates end-to-end WebAuthn account creation flow. State architecture evolution continuing September’s refactoring shows sustained commitment to code quality. Library simplifications (mnemonic-seeds WASM removal, WharfKit bundle) improve developer experience across ecosystem.
Table of Contents
- Cross-Repository Insights
- greymass/web-authenticator
- greymass/unicove
- greymass/web-authenticator-backups
- greymass/mnemonic-seeds
- aaroncox/vaulta-contracts
- New Repositories
- Development Patterns
Cross-Repository Insights
Coordinated WebAuthn Account Creation Infrastructure
Integration: Web Authenticator passkey implementation coordinated with vaulta-contracts account creation enabling end-to-end WebAuthn-based provisioning.
How It Works:
- Web Authenticator implemented passkey/WebAuthn authentication (PRs #183, #181) providing browser-native credential management
- vaulta-contracts added R1 (secp256r1) key support in account creation contract (PR #10) enabling WebAuthn public keys
- Coordinated implementation creates complete flow: Web Authenticator generates WebAuthn credentials → contract creates on-chain account with R1 key → passwordless authentication without traditional private key management
Technical Benefit: This coordination eliminates major adoption barrier by enabling mainstream authentication patterns (fingerprint, face recognition, device PIN) for blockchain accounts. Web Authenticator provides client-side credential generation; smart contract provides on-chain provisioning. Together they create seamless onboarding experience using familiar device security.
Strategic Impact: Addresses core challenge of native user experience and simplified onboarding. WebAuthn removes complexity of private key management while maintaining security, enabling product-focused development phase.
Backup System Integration Across Three Repositories
Integration: Web Authenticator Backup V2 system integrates mnemonic-seeds library and web-authenticator-backups extension creating secure recovery solution.
How It Works:
- mnemonic-seeds library simplified by removing WASM dependency (PR #2) enabling clean browser extension integration
- web-authenticator-backups extension integrated mnemonic-seeds package (PR #2) for secure mnemonic handling in isolated environment
- Web Authenticator implemented Backup V2 system (PRs #187, #190, #193) orchestrating recovery phrase generation and restoration
Technical Benefit: Three-repository architecture separates concerns: mnemonic-seeds provides cryptographic primitives, browser extension isolates sensitive operations, Web Authenticator provides user interface. WASM removal from mnemonic-seeds enabled extension integration by eliminating environment compatibility issues. Result is secure backup system with proper separation between UI, business logic, and sensitive operations.
Strategic Impact: Backup capability critical for production deployment. 30-comment design discussion (PR #187) demonstrates careful approach to security-critical feature. Architecture enables future backup method additions without core wallet changes.
greymass/web-authenticator
Repository: https://github.com/greymass/web-authenticator
Previous Context: See September 2025 for state management refactoring (26 PRs - state architecture improvements, UX simplification, Unicove integration, testnet development).
Activity This Month: 22 PRs merged
Changes This Month
October marked a major production readiness milestone for Web Authenticator following September’s state architecture work. With foundational architecture solidified in September, October focused on user-facing features required for production deployment. Development focused on three critical areas: (1) passkey/WebAuthn integration for passwordless authentication, (2) Backup V2 system completion enabling secure account recovery, and (3) continued state architecture improvements separating AccountsState into focused domain states. Month also included Wuchale internationalization integration, production polish, and configuration improvements. This work represents maturation from testnet architectural refinement to production-critical feature completion.
Pull Requests
Passkey and WebAuthn Integration (3 PRs)
#183 - Passkeys, Paraglide, and Credentials state
Merged: 2025-10-07
Description: Integrated passkey support, Paraglide internationalization framework, and credentials state management.
Technical Details:
- Passkey integration enables WebAuthn-based authentication
- Browser-native, phishing-resistant authentication without traditional password entry
- Paraglide internationalization framework enables multi-language support
- Credentials state provides foundation for managing WebAuthn credentials
Impact: Passkeys represent cutting-edge authentication UX - browser-native, secure, passwordless experience critical for mainstream adoption. Internationalization support enables global reach. Foundation for modern authentication flows that reduce onboarding friction compared to traditional private key management.
#181 - Passkey/webauthn refactor
Merged: 2025-10-05
Description: Refactored passkey and WebAuthn implementation following initial integration in PR #183.
Impact: Architectural improvements to WebAuthn integration patterns. Better code organization for credential management. Follow-up refinement demonstrating iterative approach to complex features.
#182 - Add pending request component
Merged: 2025-10-04
Description: Added Pending Request component showing active transaction requests. Changed switcher icon from right chevron to up/down chevron.
Impact: UX improvement giving users visibility into pending transactions. Better feedback for async operations. Icon change improves visual communication of switcher interaction model.
Backup System V2 (3 PRs)
#187 - Backups V2
Merged: 2025-10-11 | 30 comments
Description: Major backup system V2 implementation.
Discussion (30 comments): Most discussed PR in October, indicating extensive design discussion around backup system architecture, security considerations for mnemonic handling, integration approach with browser extension, state management patterns for backup flows, and recovery mechanisms.
Impact: Significant backup system overhaul enabling users to secure accounts through mnemonic-based recovery. 30 comments indicate high-complexity feature requiring careful review and iteration. Major milestone for production readiness - users need confidence in account recovery capability. V2 represents maturation of backup architecture after initial implementation.
Strategic Significance: Backup capability critical for non-custodial wallet adoption. This work removes major barrier to production deployment.
#190 - Dafuga backups v2 merge
Merged: 2025-10-08
Description: Merged backup system V2 work (related to PR #187).
Impact: Major backup system update integrating V2 architecture into main codebase.
#193 - Backup State Refactor
Merged: 2025-10-14
Description: Refactored backup state management following V2 merge.
Impact: Improved backup state architecture as follow-up to state splitting in PR #195. Better separation of backup concerns from account management.
State Architecture Refactoring (2 PRs)
#195 - Splitting Accounts into Accounts, Backup, and Wallets
Merged: 2025-10-17
Description: Major state architecture refactor splitting AccountsState into separate AccountState, AccountsState, WalletsState, and BackupState. Created reusable core state pattern with persistence. Reworked RequestState to use runed’s resource for async state. Removed unused ToasterState and CredentialsState.
Technical Changes:
- Created core states with reusable persistence patterns
- Reworked AccountState, AccountsState, SettingsState to inherit from core state
- Created WalletsState and BackupState removing that responsibility from AccountsState
- Reworked RequestState using runed’s resource for async state management
- Removed unused ToasterState components and CredentialsState (unused since discoverable credentials)
Impact: Significant architectural improvement separating concerns. AccountsState was handling too many responsibilities; splitting into focused states improves maintainability and testability. Core state pattern with built-in persistence enables code reuse across state classes. Async state management with runed’s resource provides better loading/error states. Removal of unused code reduces bundle size and complexity.
Continuation from September: Extends September’s state management refactoring (PRs #137, #126, #146, #171, #172) by further decomposing monolithic state into domain-specific states.
#175 - Connections and App State
Merged: 2025-10-04 | 2 comments
Description: Converted state management to app.svelte.ts with app state (menuTitle, pageTitle). Converted account selector from modal to page (/select route). Renamed Session Key names in localStorage. Fixed Session uniqueness issue allowing same account across multiple apps. Abstracted LoginPrompt component for reuse. Added pagination on /accounts page. Added error message for Ledger device without Contract Data enabled. Added Connections section to Settings.
Technical Changes:
- Converted
/lib/state/index.tsto/lib/state/app.svelte.tsfor app state - Added menuTitle and pageTitle state management
- Account selector moved from modal to dedicated page (/select route)
- Session Key localStorage naming updated
- Session uniqueness fix enabling same account across multiple dapps
- LoginPrompt component abstracted for reuse in Identity Requests and homepage
- Pagination on /accounts page for scalability
- Ledger Contract Data error message for hardware wallet UX
- Connections management in Settings providing transparency
Impact: Major state architecture evolution consolidating app-level state. Account selector as dedicated page improves UX and enables deep linking. Session management fix critical for multi-app use cases - users can now use same account across different dapps simultaneously. Component abstraction (LoginPrompt) improves code reuse. Pagination essential for accounts page scalability. Connections management gives users visibility and control over dapp permissions.
Strategic Significance: Session uniqueness fix enables core use case of single account across ecosystem. App state consolidation creates foundation for future features requiring global state coordination.
Wuchale Integration and Internationalization (2 PRs)
#199 - Initial wuchale implementation
Merged: 2025-10-17
Description: Initial implementation of Wuchale integration for internationalization.
Impact: Wuchale integration expanding Web Authenticator ecosystem connectivity and enabling multi-language support for global adoption.
#198 - Wuchale implementation and migration to new createContext helper
Merged: 2025-10-18 | 2 comments
Description: Completed Wuchale implementation and migrated codebase to new createContext helper pattern.
Technical Changes:
- Wuchale integration completion for internationalization
- Context helper migration improves code consistency across state management
- Architectural improvement for Svelte state patterns
Impact: Internationalization enablement through Wuchale. Context helper migration improves maintainability by standardizing state access patterns. Better architectural consistency following September’s context helper work (PRs #171, #172).
Account Creation and Validation (3 PRs)
#201 - Refactor account name creation for better ui ux
Merged: 2025-10-22 | 3 comments
Description: Refactored account name creation flow for improved user experience.
Impact: UX improvement simplifying critical onboarding step. Better account name creation flow reduces friction for new users during initial setup.
#197 - Use remote function to check account name availability
Merged: 2025-10-17
Description: Switched account name availability checking to remote function rather than local validation.
Impact: Real-time account name validation against blockchain state. More accurate than client-side validation. Improves user experience during account creation by preventing name conflicts earlier in flow rather than at submission time.
#189 - Refactor account name editing
Merged: 2025-10-11 | 3 comments
Description: Refactored account name editing component removing modal editing in favor of in-place editing. Used NameInput from unicove-components. Moved state and methods to creation state. Replaced deprecated createEventDispatcher with callback prop pattern.
Technical Changes:
- Removed modal editing pattern for in-place editing
- Used NameInput from unicove-components for consistency
- Moved state and methods to creation state for better organization
- Removed deprecated createEventDispatcher in favor of callback props
Impact: UX improvement with in-place editing reducing interaction friction. Leverages shared Unicove components for consistency across products. Modernizes Svelte patterns by removing deprecated API in favor of callback props. Better state organization.
Bug Fixes and Improvements (5 PRs)
#200 - Fixes
Merged: 2025-10-22 | 2 comments
Description: Multiple bug fixes and improvements including reworked balance state fetching using resources, added filter/search for accounts with 5+ accounts, generated copy of account creation contract, switched Vaulta to different account, changed public key format in smart contract creation from legacy to standard.
Technical Changes:
- Reworked balances state to fetch using resources instead of custom function
- Added filter/search box on account selector for 5+ accounts
- Generated copy of new account creation contract
- Switched Vaulta to use different account
- Changed public key string in smart contract creation (standard format not legacy)
Impact: Resource fetching improvement leveraging standard API patterns. Search/filter capability essential for users managing multiple accounts. Public key format standardization improves compatibility and follows best practices. Account creation contract integration supporting on-chain account provisioning.
#196 - Fixed some issues
Merged: 2025-10-17
Description: Various bug fixes.
Impact: Stability improvements addressing issues discovered during testing and usage.
#191 - ensure retry uses initial forceCreate from URL param
Merged: 2025-10-11
Description: Fixed account creation retry flow to preserve forceCreate URL parameter across retry attempts.
Impact: Bug fix ensuring URL parameters persist through retry flows. Improves reliability of account creation process when users need to retry after failures.
#188 - Scroll account select
Merged: 2025-10-11 | 10 comments
Description: Added scrolling capability to account selector.
Discussion (10 comments): Technical discussion around implementation approach for account selector scrolling, scroll behavior for large account lists, UI/UX considerations, performance implications, and alternative approaches.
Impact: UX improvement for users with many accounts. Enables navigation through large account lists. 10 comments suggests technical discussion around implementation complexity despite seemingly simple feature.
#204 - Truncate public key display to prevent UI overflow
Merged: 2025-10-22
Description: Truncated public key display strings to prevent UI overflow issues.
Impact: UI fix preventing layout breaks from long key strings. Improves visual consistency across different screen sizes.
UI and Design Polish (4 PRs)
#205 - Change style of backup banner
Merged: 2025-10-22
Description: Updated visual styling of backup reminder banner.
Impact: UI polish for backup feature visibility. Improves user awareness of backup functionality after Backup V2 launch.
#202 - Minor changes to menubar spacing
Merged: 2025-10-22
Description: Adjusted alignment and vertical spacing in menubar.
Impact: Visual polish improving menubar aesthetics and usability.
#208 - Environmental vars to enable/disable features
Merged: 2025-10-24
Description: Introduced environment variables for feature flags to control enabled backup plugins and other features.
Impact: Configuration-based feature control enables flexible deployment across environments. Allows selective feature enablement without code changes. Important for progressive rollout and A/B testing of new capabilities.
#207 - Wharf Code reorg
Merged: 2025-10-24
Description: Reorganized Wharf component structure by introducing new environment variables to control backup plugins and moving files out of utils directory into more appropriate locations.
Technical Changes: “Might look like a large PR, but it’s just moving files/imports around. Introducing new .env values to control enabled backup plugins. Reorganizing the Wharf components. A nice opportunity to pull a bunch of files out of utils and put them someplace more appropriate.”
Impact: Code organization improvement enhancing maintainability. Consolidates Wharf-specific components for better structure. Reduces technical debt by properly organizing utility functions. Foundation for cleaner codebase as project scales.
Technical Context
October’s 22 PRs focused on production readiness through sophisticated feature completion and architectural refinement:
Passkey/WebAuthn Integration (3 PRs): Modern passwordless authentication using browser-native WebAuthn. Phishing-resistant, secure credential management without traditional private keys. Paraglide internationalization framework integrated. Critical for mainstream adoption by reducing onboarding complexity.
Backup System V2 (3 PRs): Major backup system overhaul with 30-comment discussion indicating high complexity. Mnemonic-based recovery integrated with browser extension. Production-critical feature enabling user confidence in account recovery.
State Architecture Evolution (2 PRs): Continued September’s state refactoring by splitting AccountsState into domain-specific states (Accounts, Backup, Wallets). Session management fix enabling multi-app use cases. App-level state consolidation. Architectural maturation improving maintainability.
Wuchale Integration (2 PRs): Internationalization framework integrated with context helper migration. Enables global reach through multi-language support.
Account Creation (3 PRs): Remote validation, UX improvements, in-place editing patterns. Modern Svelte patterns replacing deprecated APIs. Improved onboarding flow.
Production Polish (9 PRs): Bug fixes, UI refinements, search/filter for multi-account management, feature flags, code organization. Production preparation through attention to detail.
Architectural Progression:
- September: State management refactoring, UX simplification, ecosystem integration (26 PRs)
- October: Production-critical features (passkeys, Backup V2), state architecture evolution, production polish (22 PRs)
Combined work demonstrates progression from architectural refinement to feature completion and production readiness.
greymass/unicove
Repository: https://github.com/greymass/unicove
Previous Context: See September 2025 for regular release cycles and reversible block support.
Activity This Month: 4 PRs merged
Changes This Month
October maintained regular Unicove release cycles with environment configuration updates for testnet connectivity.
Pull Requests
#541 - Updated URL again
Merged: 2025-10-22
Description: URL configuration update.
Impact: Configuration adjustment, likely environment-related for proper service connectivity.
#540 - Next release
Merged: 2025-10-22
Description: Release preparation merge gathering accumulated improvements.
Impact: Release consolidation PR preparing changes for deployment.
#537 - Update .env.jungle4
Merged: 2025-10-19
Description: Updated Jungle4 testnet environment configuration.
Impact: Testnet configuration maintenance ensuring proper Jungle4 connectivity and compatibility.
#536 - Next release
Merged: 2025-10-18
Description: Release preparation merge.
Impact: Regular release cycle maintaining product momentum.
greymass/web-authenticator-backups
Repository: https://github.com/greymass/web-authenticator-backups
Previous Context: See September 2025 for repository creation (browser extension for secure mnemonic backups).
Activity This Month: 2 PRs merged
Changes This Month
October integrated the mnemonic-seeds package following its WASM removal, improving extension architecture and eliminating code duplication.
Pull Requests
#1 - Refactor
Merged: 2025-10-03
Description: Code refactoring improving extension architecture.
Impact: Architecture or code quality improvements preparing for mnemonic-seeds integration.
#2 - Using mnemonic seeds package
Merged: 2025-10-04
Description: Integrated mnemonic-seeds package for mnemonic handling.
Impact: Leverages shared mnemonic-seeds library (PR #2) eliminating code duplication. Improves maintainability by using centralized mnemonic functionality. Related to mnemonic-seeds WASM removal enabling cleaner integration.
greymass/mnemonic-seeds
Repository: https://github.com/greymass/mnemonic-seeds
Previous Context: Library for mnemonic seed phrase generation and key derivation used by Web Authenticator backup systems.
Activity This Month: 1 PR merged
Changes This Month
October removed WASM dependency simplifying the library architecture and improving portability across environments.
Pull Requests
#2 - Removing wasm dependency
Merged: 2025-10-04
Description: Removed WASM dependency and added key generation helper functions.
Technical Changes:
- Eliminated WebAssembly dependency reducing complexity
- Added key generation helpers providing convenient API
- Pure JavaScript implementation improving portability
Impact: Eliminates WebAssembly dependency reducing complexity and bundle size. WASM can cause compatibility issues across environments (browser extensions, Node.js, edge workers); pure JavaScript implementation improves portability. Added key generation helpers provide convenient API for consumers. Performance tradeoff (WASM typically faster) likely acceptable given infrequent use case of mnemonic generation.
Strategic Significance: Simplifies integration for web-authenticator-backups extension (PR #2 integrated this package). Reduces attack surface by eliminating compiled code. Easier to audit and maintain pure JavaScript implementation compared to WASM binaries.
aaroncox/vaulta-contracts
Repository: https://github.com/aaroncox/vaulta-contracts
Branch: https://github.com/aaroncox/vaulta-contracts/tree/Sentiment
Previous Context: See September 2025 for sentiment voting contract enhancements (4 commits - multi-account balance queries, system token handling).
Activity This Month: 1 PR merged
Changes This Month
October implemented account creation functionality in smart contracts with support for both R1 (secp256r1/WebAuthn) and K1 (secp256k1/traditional) key types, enabling modern browser-based authentication flows.
Pull Requests
#10 - Account Creation
Merged: 2025-10-19
Description: Implemented account creation functionality in smart contracts with support for both R1 (secp256r1/WebAuthn) and K1 (secp256k1/traditional) key types. Split key type handling to enable different cryptographic approaches for account creation. Updated environment configuration.
Technical Changes:
- Account creation support enabling on-chain account provisioning
- R1 key support (secp256r1) for WebAuthn-based account creation
- K1 key support (secp256k1) for traditional key management
- Split implementation providing flexibility for different use cases
- Environment configuration updates
Impact: Account creation support in smart contracts enables on-chain account provisioning using different key types. R1 key support critical for WebAuthn-based account creation allowing browser-based authentication without traditional private keys. K1 support maintains compatibility with traditional Antelope key management. Split implementation provides flexibility: WebAuthn for new users seeking convenience, traditional keys for users wanting full control. Foundation for Web Authenticator and other wallet onboarding flows creating accounts directly on-chain.
Strategic Significance: This work directly supports modern authentication flows being built in Web Authenticator (PRs #183, #181 focused on passkeys/WebAuthn). Account creation infrastructure fundamental requirement for simplified onboarding. Multi-key-type support enables modern WebAuthn flows while maintaining backward compatibility, improving native user experience and onboarding.
New Repositories
wharfkit/bundle
Created: 2025-10-13
Repository: https://github.com/wharfkit/bundle
Visibility: Public
Technology Stack: TypeScript, WharfKit ecosystem packages, dual module format support (IIFE/ESM)
Purpose: Prepackaged bundle of common Wharf libraries for IIFE (CommonJS) or ESM (ES Module) usage patterns.
Description: Provides re-exported bundle of common WharfKit libraries for both IIFE and ESM usage patterns. Package.json and src/main.ts contain list of exported packages. Includes usage examples in public/bundle.html for IIFE and public/esm.html for ESM.
Strategic Significance: Bundle repository simplifies WharfKit adoption by providing single-import access to common libraries. Reduces complexity for developers who need multiple WharfKit packages by bundling them together. Supports both traditional script tags (IIFE) and modern ES modules enabling broader compatibility across different development environments. Important developer experience improvement making WharfKit more accessible for quick prototyping and integration into existing projects without complex build configurations.
Development Patterns
Security-Critical Feature Development
Pattern: Extensive design discussion and iterative refinement for security-sensitive features.
Example: Backup V2 system (PR #187) with 30 comments represents careful approach to account recovery. Discussion covered backup data structure, mnemonic handling security, browser extension integration, state management, and recovery flows.
Impact: High comment count demonstrates thorough review process for features handling sensitive user data. Backup capability critical for production deployment requires confidence in security model.
Architectural Simplification Through Dependency Removal
Pattern: Removing complex dependencies in favor of simpler implementations when performance tradeoffs are acceptable.
Example: mnemonic-seeds library removed WASM dependency (PR #2) in favor of pure JavaScript. WASM provided performance benefits but caused environment compatibility issues (browser extensions, Node.js, edge workers). Pure JavaScript implementation improved portability for infrequent mnemonic generation use case.
Impact: Simplification enabled clean browser extension integration, reduced bundle size, improved auditability, and eliminated WASM build toolchain maintenance.
Progressive State Architecture Refinement
Pattern: Continued architectural improvements through iterative refactoring across multiple PRs.
Example: September’s state management refactoring (5 PRs) continued in October with AccountsState decomposition (PR #195) splitting into domain-specific states (Accounts, Backup, Wallets). Demonstrates sustained commitment to architecture quality through incremental improvements.
Impact: Better separation of concerns, improved maintainability, reduced cognitive load, enhanced testability. Foundation for continued feature development without accumulating technical debt.
Dual Authentication Paradigm Support
Pattern: Building systems that support both modern convenience (passkeys/WebAuthn) and traditional control (private keys) enabling different user preferences.
Example: vaulta-contracts account creation (PR #10) implemented dual key type support with R1 (secp256r1) for WebAuthn-based authentication and K1 (secp256k1) for traditional private key management. Enables mainstream users to benefit from convenient passkey creation while experienced users maintain access to traditional approaches requiring full key control.
Impact: Accommodates spectrum of user sophistication and security preferences without forcing single authentication model. Modern WebAuthn flows reduce onboarding friction for new users while traditional key management preserves sovereignty for power users. Architecture supports both paradigms simultaneously rather than choosing one at the expense of the other.
Feature Flag Infrastructure for Production Deployment
Pattern: Environment-based feature control enabling flexible deployment and progressive rollout.
Example: Web Authenticator added environment variables for feature flags (PR #208) controlling backup plugins and other features. Enables selective enablement without code changes.
Impact: Configuration-based control supports A/B testing, staged rollouts, and environment-specific features. Important for production readiness and risk mitigation during new feature launches.
Developer Experience Improvements
Pattern: Creating simplified integration paths for library consumers.
Example: WharfKit bundle package (created October 13) provides pre-packaged bundle of common Wharf libraries supporting both IIFE and ESM usage patterns. Single-import access reduces complexity for developers needing multiple WharfKit packages.
Impact: Lowers adoption barrier for WharfKit by simplifying integration. Supports traditional script tags and modern ES modules enabling broader compatibility. Important for quick prototyping and integration into existing projects without complex build configurations.