Unable to send DGB from Exodus wallet to DGB Core Wallet using Taproot address

[jkr3373]

I am unable to send DGB from my Exodus wallet to the DGB core wallet using the Bech32m (Taproot) address.

I receive an error message on Exodus "Invalid DGB address. Please check it and try again."

_NOTE: I am able to send DGB from Exodus to DGB core wallet using Bech32 (SegWit)_

jkr3373

[JaredTate]

Yes, Exodus needs to upgrade to v8.26 to be able to send to Taproot addresses. This is their issue, not a DGB core issue. Please help reach out to them and request that they upgrade.

[jkr3373]

Thank you Jared for the quick response and feedback. Appreciate everything you and the DGB team are doing. I will reach out to Exodus and request that they upgrade.

…

On Thursday, October 30th, 2025 at 10:39 AM, Jared Tate ***@***.***> wrote: JaredTate left a comment [(DigiByte-Core/digibyte#339)](#339 (comment)) Yes, Exodus needs to upgrade to v8.26 to be able to send to Taproot addresses. This is their issue, not a DGB core issue. Please help reach out to them and request that they upgrade. — Reply to this email directly, [view it on GitHub](#339 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BY36CVKVXJYMTI52HWGQQS332IWMRAVCNFSM6AAAAACKS3NCGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRYGY2TMMZQGU). You are receiving this because you authored the thread.Message ID: ***@***.***>

[JaredTate]

Thanks for doing that! Could you send them to this link? We just dropped v8.26.1 formal release: https://github.com/DigiByte-Core/digibyte/releases/tag/v8.26.1

[jkr3373]

Will do. Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Thursday, 10/30/25 at 11:27 Jared Tate ***@***.***> wrote: JaredTate left a comment [(DigiByte-Core/digibyte#339)](#339 (comment)) Thanks for doing that! Could you send them to this link? We just dropped v8.26.1 formal release: https://github.com/DigiByte-Core/digibyte/releases/tag/v8.26.1 — Reply to this email directly, [view it on GitHub](#339 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BY36CVNGQM6IJIC3HOLWDAL32I37BAVCNFSM6AAAAACKS3NCGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRYHEYDANRXGE). You are receiving this because you authored the thread.Message ID: ***@***.***>

[jkr3373]

FYI, response from Exodus below: Hi there, Thank you for your kind words about Exodus! We're glad you're enjoying the platform. Regarding sending DigiByte (DGB) to Taproot (Bech32m) addresses: Our sources confirm that Exodus Desktop supports multiple addresses for DigiByte, but they don't specify which DGB address formats are currently supported for sending transactions.[How do I enable multiple addresses?](https://support.exodus.com/support/en/articles/10408929-how-do-i-enable-multiple-addresses) The error message you're receiving suggests that the destination Taproot address format may not be supported yet in our current version. While we appreciate you sharing the information about DGB v8.26, we don't have details in our documentation about upcoming updates or the specific address formats supported for sending DGB. To help our support team investigate this further and provide you with accurate information about DGB Taproot address support, you can reply to this email to get help from a real person. Please include: - A screenshot of the error message - The destination DGB address you're trying to send to (if you're comfortable sharing it)

…

On Thursday, October 30th, 2025 at 11:27 AM, Jared Tate ***@***.***> wrote: JaredTate left a comment [(DigiByte-Core/digibyte#339)](#339 (comment)) Thanks for doing that! Could you send them to this link? We just dropped v8.26.1 formal release: https://github.com/DigiByte-Core/digibyte/releases/tag/v8.26.1 — Reply to this email directly, [view it on GitHub](#339 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BY36CVNGQM6IJIC3HOLWDAL32I37BAVCNFSM6AAAAACKS3NCGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINRYHEYDANRXGE). You are receiving this because you authored the thread.Message ID: ***@***.***>