​
August 21, 2025
v1.0.5
  • Added:
    • Optional API Key Configuration: Added support for defaultApiKey and domainApiKeys during client initialization
    • No-Parameter Client Creation: Support for creating clients without parameters (defaults to mainnet)
  • Enhanced:
    • Improved Developer Experience: Better inline API key setup workflow
    • Documentation Updates: Updated documentation and examples to reflect new features
​
August 20, 2025
v1.0.4
  • Fixed:
    • Coin Type Corrections:
      • Fixed Sui coin type from 101 to 784 (correct SLIP-44 identifier)
      • Fixed Starknet coin type from 234567891 to 9004 (correct SLIP-44 identifier)
      • Updated test script to include Sui address validation testing
  • Testing:
    • Enhanced Test Coverage:
      • Added Sui address record testing in manual test suite
      • Improved validation for blockchain-specific coin types
​
August 19, 2025
v1.0.3
  • Added:
    • New Blockchain Support: Added support for 7 new blockchain networks:
      • Unichain
      • Berachain
      • WorldChain
      • Zora
      • Celo
      • Aptos
      • Algorand
  • Enhanced:
    • Improved Address Validation:
      • Enhanced Starknet address validation to support variable-length hex addresses (1-64 characters)
      • Improved Bitcoin address validation to support Legacy (P2PKH), Script (P2SH), Bech32 (P2WPKH/P2WSH), and Taproot (P2TR) formats
      • Updated Cosmos address validation to use proper bech32 format with ‘cosmos1’ prefix
      • Enhanced NEAR address validation to support both implicit accounts (64 hex chars) and named accounts (.near)
      • Improved Sui address validation to support variable-length hex addresses (1-64 characters)
      • Added Aptos address validation with variable-length hex support
      • Added Algorand address validation using Base32 format (58 characters)
  • Testing:
    • Comprehensive Test Coverage:
      • Added validation tests for all new blockchain chains
      • Enhanced Bitcoin address validation tests with multiple format support
      • Added Starknet address validation tests for both full and shortened addresses
      • Added Cosmos, NEAR, Sui, Aptos, and Algorand address validation tests
      • Added EVM-compatible chain address validation tests
​
August 5, 2025
v1.0.2
  • Enhanced README.md:
    • Added Supported Chains section with a quick reference of available blockchain networks.
    • Added Error Handling section with try/catch examples and specific error classes.
​
August 5, 2025
v1.0.1
  • Adopted Keep a Changelog format and Semantic Versioning.
  • Initialized CHANGELOG documentation for the @thenamespace/offchain-manager package.
​
August 5, 2025
v1.0.0
  • Changed:
    • BREAKING: Package renamed from @namespacesdk/offchain-manager to @thenamespace/offchain-manager. This is the canonical package going forward.
    • Enhanced package description for better discoverability.
    • Updated repository information and added homepage.
    • Added comprehensive keywords (ens, ethereum, subnames, domains, web3, sdk, etc.).
    • Added engines specification requiring Node.js >=16.0.0.
    • Added publishConfig for public access.
  • Documentation:
    • Enhanced README.md:
      • Added comprehensive API key types documentation (Address-based vs Domain-based).
      • Updated all code examples with the new package name.
      • Improved environment setup instructions.
      • Added mixed usage examples for API keys.
      • Updated Namespace Dev Portal section with API key type explanations.
    • Improved TESTING.md:
      • Updated title and package references.
      • Fixed environment configuration examples.
      • Updated CI/CD workflow examples.
      • Improved code formatting and consistency.
  • Package improvements:
    • Repository field with proper GitHub organization link.
    • Homepage field pointing to https://namespace.ninja.
    • Bugs field for issue tracking.
    • PublishConfig for NPM organization publishing.
    • Enhanced metadata for better package discovery.
  • Fixed:
    • All import statements updated to use the new package name.
    • Documentation consistency across all files.
    • package.json validation and best practices compliance.