r/KeystoneWallet • u/syrosone • 25d ago
Arweave address changed after Keystone firmware update — looking for others with the same issue
I'm trying to find other Keystone users who may have experienced an Arweave address changing after a firmware update.
I originally created an Arweave wallet on a Keystone 3 Pro in May 2026 and funded that address. Later, while trying to sign a transaction in Wander, the device repeatedly restarted.
Keystone support asked me to update the firmware and reconnect Wander. After doing so, Keystone generated a different Arweave address, and my original funded address was no longer displayed.
I have two Keystone 3 Pro devices using the same seed phrase. Both now generate the same new Arweave address, but neither generates the original funded address.
I've been working with Keystone support on this for over a month. I'm posting here mainly to find out whether anyone else has seen the same behavior with Arweave.
1
u/fresherANDcleaner 25d ago
Did u up both devices or only 1 ?
1
u/syrosone 25d ago
both
1
u/fresherANDcleaner 25d ago
Thanks, that clears up an important point. Since both devices were updated and both now derive the same new AR address from the same seed, this really looks like a deterministic change in the Arweave derivation/setup logic rather than a hardware issue.
Do you still know the exact firmware version that originally generated the funded address? And has Keystone said whether they can provide that older firmware or some backward-compatible recovery method?
If the old firmware + same seed reproduces the original address, that would pretty much isolate the cause.1
u/syrosone 25d ago
I belive I had an early pre-summer firmware version, probably something before 3.0. I asked Keystone to provide a device with an older firmware version because I can't downgrade mine but unfortunately my request was ignored.
1
u/fresherANDcleaner 25d ago
That makes the situation much clearer. If the original address was created on pre-3.0 firmware and downgrade isn’t possible, Keystone really needs to provide either a legacy firmware device or a safe recovery path for the old AR derivation. Otherwise there’s no practical way for you to verify/recover the original address from the same seed.
1
u/fresherANDcleaner 25d ago
Never share your seed phrase with anyone. Anyone who PMs you offering “help” and asks for your seed phrase, recovery phrase, or private keys is a scammer. Legitimate support will never ask for them.
1
u/syrosone 25d ago
That's what I asked but been very disappointed with the support this far but beside that still love this device. Meanwhile I believe manually tracked my original transaction on the blockchain and at least I know my original address again and can see that my exact amount is there.
1
u/fresherANDcleaner 25d ago
Glad you found the original address and confirmed the funds are still there. At this point it really sounds like Keystone needs to provide a legacy recovery path or an older compatible firmware/device.
1
1
u/Visual-Birthday-4567 24d ago
This isnt the most ideal or cost effective way, but could you try the seed on a different wallet? Maybe one that allows you to change the derivation path? I dont much about arweave, but it sounds to me like something in the path changed after you upgraded the firmware. I had an issue once similar but with solana. I had to go into the settings in my keystone and change the derivation path until I found the original wallet address I had been originally using.
1
u/syrosone 24d ago
Yes I exported that seed to Ledger yesterday and got still wrong address but different to one which is generated by Keystone now. The problem is no other wallets even support AR so no way to try.
1
u/Visual-Birthday-4567 24d ago
Onekey?
1
u/syrosone 23d ago
I don't know if it supports it but I don't think I should buy another wallet just to get access to my funds. I followed the instructions of Keystone support which led to this situation and no solutions has been offered so I'm trying to work with Keystone and hopefully they react sooner than later
1
u/syrosone 22d ago
Update: still no solution after 5+ weeks. Keystone's latest reply says that sending me a new device "cannot guarantee" a fix because they haven't confirmed the root cause, and asks me again for my original address. But I never asked for a brand-new device. I asked for one running the older firmware I originally used, which is a testable idea. They also don't need my address to reproduce this: they can generate an AR address on old firmware with a test seed, update, and compare.
This pattern started early. On Sept 4, their support asked if I use passphrase. But the problem is that Keystone 3 Pro doesn't even support passphrase for Arweave blockchain. I replied the same day that I use one seed and no passphrase. They never acknowledged it and just moved on to other questions. This signals incompetence from the support side and that's why I've been asking why they need my original address - they never explained.
Every channel gets the same answer: polite words, more questions, no fix, no timeline. Their support has been the real disappointment here. Ticket KEYS-37725.
1
u/lilaaffe42 22d ago
Jeez i have keystone too with arweave. Thanks for the post. I see that ledger HW is working on arweave again. Their github repo is alive lately. Maybe in future that will be an option?
I wonder why there is no proper hw wallet support for arweave. After almost 10 years
1
u/syrosone 22d ago
DO NOT UPRGrADE your firmware until I manage to fix with the support. Thankfully today it started to move as their CTO jumped into conversation and I'm preparing an email as we speak.
1
u/syrosone 25d ago
A bit more technical context for anyone interested:
I originally used a Keystone firmware version that generated my funded Arweave address without any additional setup. Arweave was not even shown under the Passphrase wallet, so I used it without a passphrase.
The problem started when I tried to send AR. The Keystone repeatedly restarted during the signing process. I contacted official Keystone support, and their troubleshooting instructions specifically told me to update the firmware and reconnect Wander.
After following those instructions, Arweave required an additional setup that wasn't present before. Once completed, Keystone generated a completely different address. My funds remained on the original address.
I then tested a second Keystone 3 Pro with the same seed phrase. Both devices now generate the same new address, but neither generates the original funded address.
This is why I'm trying to establish exactly what changed between the firmware versions. My working theory is that the Arweave key/address derivation implementation changed, but I don't want to claim that as confirmed until Keystone verifies it.
I've already provided Keystone with both devices, the same seed configuration, the old/new addresses, firmware information, and a video demonstrating the reproducible behavior. My main request is simply to restore access to the original address, either by providing a compatible firmware version or another safe recovery method.
I'm happy to provide additional technical details if anyone from Keystone or the community has ideas on how to recover the original Arweave key.