Skip to main content

Questions tagged [ecdsa]

The tag has no usage guidance.

Filter by
Sorted by
Tagged with
0 votes
1 answer

Create and sign transaction with offline signer and ECDSA signatures

I would like to understand how to sign a balances.transferKeepAlive transaction completely offline with an existing signing service with ECDSA signatures. This is what I have so far that is working: ...
ruby_newbie's user avatar
0 votes
1 answer

Invalid transaction:1010 Invalid: Transaction has a bad signature

I have changed my default multisignature to EthereumSignature. But whenever i'm doing any transaction on metamask then it is working fine and whenever i'm manually signing the transaction with a ...
Arunjot Singh's user avatar
3 votes
1 answer

What informations consist of a signature which is generated when siging a transaction payload offline?

From the wiki (, import { createSignedTx } from "@substrate/txwrapper-polkadot"; // Example code, replace `signWithAlice` ...
drhanlondon's user avatar
6 votes
0 answers

How to generate a Moonbeam Unified Account using Subkey?

In the Moonbeam Unified documentation here, it says that Moonbeam natively supports "Ethereum-style address (H160 format), which is 40+2 hex-characters long, in a Substrate based chain" and ...
Luke Schoen's user avatar
  • 2,346
1 vote
1 answer

Does polkadot.js extension expose a method for signing using ECDSA?

So far it looks like polkadot.js/api supports ECDSA signatures, but the polkadot.js extension doesn't expose a method to use ECDSA: How to sign a message using ECDSA key pairs in Polkadot.js so it ...
Bob's user avatar
  • 13
3 votes
2 answers

How to sign a payload using ECDSA in PolkadotJS?

I've followed the cookbook on signing a payload, however this uses sr25519. I would like to use ECDSA to sign the payload, how can this be done? I have looked into using the keyring and managed to get ...
goastler's user avatar
  • 579
1 vote
1 answer

Can I use ECDSA address which is compatible with Ethereum as the Native address in a substrate based blockchain?

For my project, I have to build a blockchain using ECDSA address in order to be compatible with Ethereum. But the native address is in sr25519 scheme in substrate. What should I do to implement this? ...
kugool's user avatar
  • 171
1 vote
1 answer

ink_env::ecdsa_recover is not returning the right public key

I am having an issue trying to verify ecdsa signature in ink! for my test. I am generating the signature this way const keyring = new Keyring({type: 'ecdsa'}); const pair = keyring.addFromUri('//...
dharjeezy's user avatar
  • 419
3 votes
1 answer

Adding support for p256 keys and signatures (secp256r1)

Is it possible to add support for other cryptographic algorithms, or are we only allowed to use the implemented ones? The implemented ones are sr25519, ed25519, ecdsa(secp256k1, not secp256r1). I ...
Juan Ignacio Rios's user avatar
5 votes
2 answers

How do ECDSA subkeys differ from Bitcoin/Ethereum keys?

As far as I understand, besides the ed25519 and sr25519 signatures, there is a compatibility mode for ECDSA keypairs that should use the secp256k1 curve. Both Bitcoin and Ethereum use the secp256k1 ...
q9f's user avatar
  • 307