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.

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

Inconsistent seed handling #808

Open
jimfcarroll opened this issue Feb 22, 2025 · 0 comments
Open

Inconsistent seed handling #808

jimfcarroll opened this issue Feb 22, 2025 · 0 comments

Comments

@jimfcarroll
Copy link

jimfcarroll commented Feb 22, 2025

Using derive_keypair provides different results than every other XRP system. As an example, running:

from xrpl.core.keypairs import derive_keypair, derive_classic_address

# Your XRP seed (starting with 'shf')
seed = "shfMySeed"

# Derive private and public keys
private_key, public_key = derive_keypair(seed)

# Derive the XRP address from the public key
classic_address = derive_classic_address(public_key)

print("XRP Address:", classic_address)

Generates a different XRP Address than ripple-lib.js, Guarda, and bithomp, all of which, when I give it my 'shf...' seed (secp256k1), generate the same XRP Address.

I tried supplying it both algorithms and setting validator both ways and none of the resulting XRP Addresses matched the ones consistently generated by all the other options.

I'm not sure if this is a bug, I'm using it wrong, or my expectations are wrong. Any help would be appreciated. I'm trying to manage an existing wallet with a few funds in it already based on a stored key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@jimfcarroll and others