15 November 2026

Account: @asofij
Issue: Comprehensive authority key mismatch preventing transactions

---

Summary

I'm writing to request assistance with recovering access to my Hive account @asofij. The account has been experiencing persistent issues with key authority validation for several months, and despite having the correct private keys, the network rejects them for transactions requiring active authority.

Key Details

Account Background

• Account created: April 13, 2025 (approximately 7 months ago based on current date of November 2026)

• Used primarily via Ecency and PeakD interfaces

• Posting key works for voting and content publication

• Active key fails for all transactions with error: "Missing Active Authority"

Key Discrepancies Detected

Owner (Master) Public Keys:

• Ecency blockchain: STM797yaPY4b7YBvYzfpUzidN9AXYvRZMYerPtoLTwoXvUA4XNByX

• My notes/records: STM8AUxF7j8GDewu31vojADUGg79JSEkazZHwDkVFyqs4PzZxvuGP

Active Public Keys (three different versions found):

• My iPhone notes: STM5SPpa52zcTMzVtY4TUQPgYLxJiMwjd1AwucwkLNbXSFkh9hh6q

• Ecency interface: STM6Z1Lh7FBeNR8bx9AqSFqa1ZMNosRB3ADH1QbQ8j8FsGSm4pLLL

• Cellphone Keychain: STM5RTg9k7jPuiY2ZdoHbKjXqV7Pmka5QaVhJutAboKcQ6xfVaQbC

Private Active Key (verified correct but incompatible): 5K1VZQ...myZSyeey

What I've Tried

• Importing keys into Hive Keychain (multiple times, across different browsers/devices)

• Direct connection in PeakD without Keychain

• Using Ecency for voting/publication (works for posting-only operations)

• Verifying keys against public keys (confirmed correct private keys but public key mismatches)

• Sending test transactions - all fail with "Missing required active authority"

The Problem

The core issue appears to be a complete disconnection between the stored key pairs and the authorities currently registered on the blockchain. The owner public keys themselves don't match between different sources, and the active key private doesn't correspond to any of the three active public keys found. This suggests either:

1. A hard fork or protocol change (hf26 mentioned in error logs) that changed key serialization

2. An incomplete key rotation that left the authorities in an inconsistent state

3. A blockchain-level issue requiring manual intervention

What I Need from Hive Support

Given the complexity and the number of key mismatches detected, I'm requesting direct assistance with one or more of the following:

1. Manual authority reset on the @asofij account using owner key validation

2. Verification and correction of the owner key registered on-chain

3. Guidance on proper key import procedure given the current state of authorities

4. Escalation to the technical team if this requires blockchain-level intervention

Additional Context

• I have full ownership and control of @asofij

• I've never intentionally changed the owner key

• The account has been used continuously since April 2025

• Other Hive accounts I own ( @aljif7, @alejandringggg , @corazoncito) work perfectly with similar key management procedures

• I'm willing to provide any additional key material, signatures, or verification steps required

  This is the Posting Active Sessions I can see in Ecency:

  

Preferred Contact

I can be reached through this Hive interface, and I'm available to provide:

• Cryptographic proof of key ownership

• Additional account history or transaction logs if needed

• Any other verification required to confirm account ownership

---

Thank you for your time and assistance. This account has significant personal and community value, and I'm motivated to resolve this technical blockage.

Sent from Hive-Ecency interface by verified account holder

#hive #peckd #ecencyhelp #leo.voter #keyissues #hivesupport #accountaccess #keyrecovery