ed25519 public key regeneration #7

vchong · 2024-05-28T17:27:27Z

Is it possible to shed light into the process of going from a bip39 mnemonic and the m/44'/607'/0'/0/0/0 bip44 derivation path to the 32B ed25519 public key returned in

ledger-app-ton/src/crypto.c

Lines 107 to 113 in 5ca0490

    
           // Convert to NaCL format 
        
           for (int i = 0; i < PUBKEY_LEN; i++) { 
        
               raw_public_key[i] = public_key.W[64 - i]; 
        
           } 
        
           if ((public_key.W[32] & 1) != 0) { 
        
               raw_public_key[31] |= 0x80; 
        
           }

? We're in dire need to do this without a ledger. Thank you very much in advance!

The text was updated successfully, but these errors were encountered:

kslamph · 2024-06-24T12:13:07Z

this is needed, as mytonwallet dosnt support ledger on dapps now. we need to do this without a ledger.

vchong · 2024-06-24T13:30:32Z

@kslamph Will https://tonhelloworld.com/01-wallet/ work for you? e.g.

import { mnemonicToWalletKey } from "@ton/crypto";
import { WalletContractV4 } from "@ton/ton";

async function main() {
  // open wallet v4 (notice the correct wallet version here)
  const mnemonic = "unfold sugar water ..."; // your 24 secret words (replace ... with the rest of the words)
  const key = await mnemonicToWalletKey(mnemonic.split(" "));
  const wallet = WalletContractV4.create({ publicKey: key.publicKey, workchain: 0 });

  // print wallet address
  console.log(wallet.address.toString({ testOnly: true }));

  // print wallet workchain
  console.log("workchain:", wallet.address.workChain);
}

main();

Our problem is that, if you program a ledger with the same mnemonic as the one used above (e.g. unfold sugar water ...), the wallet address generated when you connect this ledger to the tonkeeper wallet extension isn't the same as the one generated by the code above. Specifically, the publicKey isn't the same (and obviously the privateKey as well).

We would like the wallet address on both occasions to be the same, hence my original question above, how is the publicKey for the ledger-app-ton derived. If we can derive the same key value without a ledger, we can just plug it into the code above and generate the same wallet address as the one generated with the ledger plus tonkeeper wallet extension.

kslamph · 2024-06-25T01:16:34Z

@kslamph Will https://tonhelloworld.com/01-wallet/ work for you? e.g.
import { mnemonicToWalletKey } from "@ton/crypto";

import { WalletContractV4 } from "@ton/ton";



async function main() {

  // open wallet v4 (notice the correct wallet version here)

  const mnemonic = "unfold sugar water ..."; // your 24 secret words (replace ... with the rest of the words)

  const key = await mnemonicToWalletKey(mnemonic.split(" "));

  const wallet = WalletContractV4.create({ publicKey: key.publicKey, workchain: 0 });



  // print wallet address

  console.log(wallet.address.toString({ testOnly: true }));



  // print wallet workchain

  console.log("workchain:", wallet.address.workChain);

}



main();
Our problem is that, if you program a ledger with the same mnemonic as the one used above (e.g. unfold sugar water ...), the wallet address generated when you connect this ledger to the tonkeeper wallet extension isn't the same as the one generated by the code above. Specifically, the publicKey isn't the same (and obviously the privateKey as well).

We would like the wallet address on both occasions to be the same, hence my original question above, how is the publicKey for the ledger-app-ton derived. If we can derive the same key value without a ledger, we can just plug it into the code above and generate the same wallet address as the one generated with the ledger plus tonkeeper wallet extension.

thanks, but it dose not work for my case, i have the same requirments as you, need to generate the key same mytonwallet, besides, i have a passpharse added on the 24 words.

loupiote · 2024-10-22T08:00:09Z

Note that Ledger Live uses the derivation path m/44'/607'/0'/0'/0'/0' (not m/44'/607'/0'/0/0/0). No idea why Ledger Live uses this weird derivation path!

And yes, as @vchong said, it appears to be different from the derivation path used by Tonkeeper.

vchong · 2024-10-22T12:07:47Z

@loupiote i think that was the missing piece

@kslamph do you still need this? can you try below and see if it works?

import * as bip39 from 'bip39';
import * as ed25519 from 'ed25519-hd-key';
import { WalletContractV4, WalletContractV3R2 } from '@ton/ton';

function derivePublicKey(mnemonic, hdPath) {
    const seed = bip39.mnemonicToSeedSync(mnemonic);

    const { key: rawPrivateKey } = ed25519.derivePath(hdPath, seed.toString('hex'));
    console.log('rawPrivateKey:', rawPrivateKey.toString('hex'));

    const rawPublicKey = ed25519.getPublicKey(rawPrivateKey);
    console.log('rawPublicKey:', rawPublicKey.toString('hex'));

    // Get public key and slice off the '00' prefix before converting to hex
    const rawPublicKey2 = ed25519.getPublicKey(rawPrivateKey).slice(1);
    console.log('rawPublicKey2:', rawPublicKey2.toString('hex'));

    return {
        privateKey: rawPrivateKey,
        publicKey: rawPublicKey2
    }
}

// Example usage
const mnemonic = '<insert mnemonic here>';
const hdPath = "m/44'/607'/0'/0'/0'/0'"; // account index 0
// const hdPath = "m/44'/607'/0'/0'/1'/0'"; // account index 1
const keyPair = derivePublicKey(mnemonic, hdPath);
console.log('Private Key:', keyPair.privateKey.toString('hex'));
console.log('Public Key:', keyPair.publicKey.toString('hex'));

const contract = WalletContractV4.create({
    workchain: 0,
    publicKey: keyPair.publicKey
});

const friendlyAddress = contract.address.toString({urlSafe: true, bounceable: true, testOnly: false}); // set this to `true` if testnet
const friendlyAddressNonBounceable = contract.address.toString({urlSafe: true, bounceable: false, testOnly: false});

// these addresses should match those from a ledger
console.log(`
    v4R2 Wallet:
    Bounceable address: ${friendlyAddress}
    Non-bounceable address: ${friendlyAddressNonBounceable}
        `);

mikey-cool · 2024-10-23T02:03:07Z

@loupiote我认为这是缺失的部分

@kslamph你还需要这个吗？你可以尝试下面看看它是否有效吗？

import * as bip39 from 'bip39';
import * as ed25519 from 'ed25519-hd-key';
import { WalletContractV4, WalletContractV3R2 } from '@ton/ton';

function derivePublicKey(mnemonic, hdPath) {
    const seed = bip39.mnemonicToSeedSync(mnemonic);

    const { key: rawPrivateKey } = ed25519.derivePath(hdPath, seed.toString('hex'));
    console.log('rawPrivateKey:', rawPrivateKey.toString('hex'));

    const rawPublicKey = ed25519.getPublicKey(rawPrivateKey);
    console.log('rawPublicKey:', rawPublicKey.toString('hex'));

    // Get public key and slice off the '00' prefix before converting to hex
    const rawPublicKey2 = ed25519.getPublicKey(rawPrivateKey).slice(1);
    console.log('rawPublicKey2:', rawPublicKey2.toString('hex'));

    return {
        privateKey: rawPrivateKey,
        publicKey: rawPublicKey2
    }
}

// Example usage
const mnemonic = '<insert mnemonic here>';
const hdPath = "m/44'/607'/0'/0'/0'/0'"; // account index 0
// const hdPath = "m/44'/607'/0'/0'/1'/0'"; // account index 1
const keyPair = derivePublicKey(mnemonic, hdPath);
console.log('Private Key:', keyPair.privateKey.toString('hex'));
console.log('Public Key:', keyPair.publicKey.toString('hex'));

const contract = WalletContractV4.create({
    workchain: 0,
    publicKey: keyPair.publicKey
});

const friendlyAddress = contract.address.toString({urlSafe: true, bounceable: true, testOnly: false}); // set this to `true` if testnet
const friendlyAddressNonBounceable = contract.address.toString({urlSafe: true, bounceable: false, testOnly: false});

// these addresses should match those from a ledger
console.log(`
    v4R2 Wallet:
    Bounceable address: ${friendlyAddress}
    Non-bounceable address: ${friendlyAddressNonBounceable}
        `);

This still does not match the address generated by ledger live

mikey-cool · 2024-10-23T02:21:33Z

@loupiote我认为这是缺失的部分

@kslamph你还需要这个吗？你可以尝试下面看看它是否有效吗？

import * as bip39 from 'bip39';
import * as ed25519 from 'ed25519-hd-key';
import { WalletContractV4, WalletContractV3R2 } from '@ton/ton';

function derivePublicKey(mnemonic, hdPath) {
    const seed = bip39.mnemonicToSeedSync(mnemonic);

    const { key: rawPrivateKey } = ed25519.derivePath(hdPath, seed.toString('hex'));
    console.log('rawPrivateKey:', rawPrivateKey.toString('hex'));

    const rawPublicKey = ed25519.getPublicKey(rawPrivateKey);
    console.log('rawPublicKey:', rawPublicKey.toString('hex'));

    // Get public key and slice off the '00' prefix before converting to hex
    const rawPublicKey2 = ed25519.getPublicKey(rawPrivateKey).slice(1);
    console.log('rawPublicKey2:', rawPublicKey2.toString('hex'));

    return {
        privateKey: rawPrivateKey,
        publicKey: rawPublicKey2
    }
}

// Example usage
const mnemonic = '<insert mnemonic here>';
const hdPath = "m/44'/607'/0'/0'/0'/0'"; // account index 0
// const hdPath = "m/44'/607'/0'/0'/1'/0'"; // account index 1
const keyPair = derivePublicKey(mnemonic, hdPath);
console.log('Private Key:', keyPair.privateKey.toString('hex'));
console.log('Public Key:', keyPair.publicKey.toString('hex'));

const contract = WalletContractV4.create({
    workchain: 0,
    publicKey: keyPair.publicKey
});

const friendlyAddress = contract.address.toString({urlSafe: true, bounceable: true, testOnly: false}); // set this to `true` if testnet
const friendlyAddressNonBounceable = contract.address.toString({urlSafe: true, bounceable: false, testOnly: false});

// these addresses should match those from a ledger
console.log(`
    v4R2 Wallet:
    Bounceable address: ${friendlyAddress}
    Non-bounceable address: ${friendlyAddressNonBounceable}
        `);

Mnemonic word:perfect valley spy embark stadium hint ocean pen conduct prevent skull plug empower obscure night inside violin weasel brief barrel crucial choice brisk husband
ledger live address:UQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhITim
TonKeeper address:UQBLP6SOA1FhMb6UfNnGmVUgcl7KVpLoMTzdoZ4BV1HzKrWe
this code generate address: UQCR97S0JjEutMBft4FMIa_HVDdqREi1P1o_CEjOAqr3GEKV

vchong · 2024-10-23T05:59:22Z

Did you do this?

const mnemonic = '<insert your "perfect valley .." mnemonic here>';

I was able to get UQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhITim with the code, which matches the ledger live address.

rawPrivateKey: ...
rawPublicKey: ...
rawPublicKey2: 042727f75e5505bca999ea862c6fb4d7dfbd34ef4567fdc9e7e3b24d62b882d8
Private Key: ...
Public Key: 042727f75e5505bca999ea862c6fb4d7dfbd34ef4567fdc9e7e3b24d62b882d8

    v4R2 Wallet:
    Bounceable address: EQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhIWVj
    Non-bounceable address: UQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhITim

Importing the mnemonic directly into Tonkeeper will not give the same address as it does its derivation different than the ledger.

mikey-cool · 2024-10-23T06:07:29Z

你做过这个吗？
const mnemonic = '<insert your "perfect valley .." mnemonic here>';
我能够获得UQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhITim与分类帐实时地址相匹配的代码。
rawPrivateKey: ...
rawPublicKey: ...
rawPublicKey2: 042727f75e5505bca999ea862c6fb4d7dfbd34ef4567fdc9e7e3b24d62b882d8
Private Key: ...
Public Key: 042727f75e5505bca999ea862c6fb4d7dfbd34ef4567fdc9e7e3b24d62b882d8

    v4R2 Wallet:
    Bounceable address: EQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhIWVj
    Non-bounceable address: UQDNElOhL-KgNzU9I-j6HZLbvNsCaE5Jqs23lf-xYUkhITim
将助记词直接导入 Tonkeeper 不会给出相同的地址，因为它的派生方式与分类账不同。

Can you give me the package used for your package.json? I wonder if we have different bags

vchong · 2024-10-23T06:10:27Z

It's not a "clean" copy, but here you go.

{
  "dependencies": {
    "@ton/crypto": "^3.3.0",
    "@ton/ton": "^13.11.2",
    "bip32": "^4.0.0",
    "bip39": "^3.1.0",
    "ed25519": "^0.0.5",
    "ed25519-hd-key": "^1.3.0",
    "elliptic": "^6.5.5",
    "ethereumjs-util": "^7.1.5",
    "hdkey": "^2.1.0",
    "tiny-secp256k1": "^2.2.3",
    "tweetnacl": "^1.0.3"
  }
}

Only bip39, ed25519-hd-key and @ton/ton should be required.
It's not good though if the output depends on the library versions.

mikey-cool · 2024-10-23T06:19:16Z

这不是一个“干净”的副本，但是你可以看一下。
{
  "dependencies": {
    "@ton/crypto": "^3.3.0",
    "@ton/ton": "^13.11.2",
    "bip32": "^4.0.0",
    "bip39": "^3.1.0",
    "ed25519": "^0.0.5",
    "ed25519-hd-key": "^1.3.0",
    "elliptic": "^6.5.5",
    "ethereumjs-util": "^7.1.5",
    "hdkey": "^2.1.0",
    "tiny-secp256k1": "^2.2.3",
    "tweetnacl": "^1.0.3"
  }
}
只有bip39、ed25519-hd-key和@ton/ton应该是必需的。但如果输出依赖于库版本，那就不好了。

It really is the version of the problem, my "@ton/ton": "^15.0.0", replaced by your version will be the same, thank you

vchong · 2024-10-23T06:54:45Z

I used 15.0.0 and was able to get the same address as well. 🤔

mikey-cool · 2024-10-23T07:10:43Z

我使用了 15.0.0 并且也能够获得相同的地址。🤔

It was a ledger bug, I had an account with ton, but after I reset it I imported the mnemonic from before and now he gets a different account.

loupiote · 2024-10-23T08:09:46Z

It was a ledger bug, I had an account with ton, but after I reset it I

imported the mnemonic from before and now he gets a different account. If true, this is not good!

…

On Wed, Oct 23, 2024, 00:11 mikey-cool ***@***.***> wrote: 我使用了 15.0.0 并且也能够获得相同的地址。🤔 It was a ledger bug, I had an account with ton, but after I reset it I imported the mnemonic from before and now he gets a different account. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJTVMJYGAWWAY7CZXNHPZWDZ45DYTAVCNFSM6AAAAABINLZDVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZRGEYDMNJSGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

kslamph mentioned this issue Jul 4, 2024

Interact with contract #8

Open

vchong mentioned this issue Oct 23, 2024

ed25519 public key regeneration ton-blockchain/mytonctrl#320

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ed25519 public key regeneration #7

ed25519 public key regeneration #7

vchong commented May 28, 2024

kslamph commented Jun 24, 2024

vchong commented Jun 24, 2024

kslamph commented Jun 25, 2024

loupiote commented Oct 22, 2024 •

edited

Loading

vchong commented Oct 22, 2024

mikey-cool commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024 •

edited

Loading

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

loupiote commented Oct 23, 2024 via email

ed25519 public key regeneration #7

ed25519 public key regeneration #7

Comments

vchong commented May 28, 2024

kslamph commented Jun 24, 2024

vchong commented Jun 24, 2024

kslamph commented Jun 25, 2024

loupiote commented Oct 22, 2024 • edited Loading

vchong commented Oct 22, 2024

mikey-cool commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024 • edited Loading

mikey-cool commented Oct 23, 2024

vchong commented Oct 23, 2024

mikey-cool commented Oct 23, 2024

loupiote commented Oct 23, 2024 via email

loupiote commented Oct 22, 2024 •

edited

Loading

vchong commented Oct 23, 2024 •

edited

Loading