Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(docs): update bech32 conversion docs #4436

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

fix(docs): update bech32 conversion docs #4436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/content/developer/stardust/addresses.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ It's possible to convert a legacy Bech32 address back to hex format by doing the

1. Take the part after `iota1`. Using the address from the above paragraph as an example, iota1**qrhacyfwlcnzkvzteumekfkrrwks98mpdm37cj4xx3drvmjvnep6xqgyzyx**.
2. Base32 decode it.
3. Strip away the last 6 digits containing the checksum.

You are left with a 33-byte hex string. The first byte represents the address type (`0x00`) and can be stripped. The 32 bytes represent an address in hex format.

Expand All @@ -32,4 +31,4 @@ The `44` represents ed25519, and the `4218` represents the IOTA Coin Type. The f

You can derive a new key pair using the key derivation path with a 24-word BIP-39 mnemonic (the same as with Stardust).

Once a key pair has been derived, the public key can be BLAKE2b-256 hashed, leaving you with a 32-byte hex address. This retains full compatibility with existing keys and hex addresses from Stardust. For any other signing scheme, besides the default ed25519, a flag is appended before hashing the public key with BLAKE2b-256. You can find all the details in the [Signatures section](../cryptography/transaction-auth/signatures.mdx) of the documentation.
Once a key pair has been derived, the public key can be BLAKE2b-256 hashed, leaving you with a 32-byte hex address. This retains full compatibility with existing keys and hex addresses from Stardust. For any other signing scheme, besides the default ed25519, a flag is appended before hashing the public key with BLAKE2b-256. You can find all the details in the [Signatures section](../cryptography/transaction-auth/signatures.mdx) of the documentation.
Loading