Hot answers tagged

3

What you are missing here is the chain ID of the network. Mainnet: aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906 Jungle Testnet: e70aaab8997e1dfce58fbfac80cbbb8fecec7b99cf982a9444273cbc64c41473 It has to be added in the " " field just after the key. Your request for Jungle Testnet should be: [{ "expiration": "2018-10-26T15:30:...


3

The api '/v1/wallet' is from the server keosd, not the nodeosd. You may change the port that keosd served.


2

Whoop, turns out it was "SIG_K1_" + base58check(65 bits of the signature) Getting the proper 65 bits is another headache for now, but yeah


2

There are several ECDSA according to what elliptic curve algorithm uses. Bitcoin, Ethereum and EOSIO support secp256k1 using Koblitz curve, and their ways to sign a transaction or recover public key from signature are fundamentally same. When a transaction is pushed to node, node tries recovering public keys from signatures (multi-sig is supported in EOSIO ...


1

ECDSA signature consists of two values, r and s. Recovery ID (v in Ethereum) is not mandatory, but due to characteristics of elliptic curve, multiple public keys are recovered from signature and verifier can determine what he should choose among them by recovery ID v. Or, verifier can check whether one of recovered key is same to known signer's public key. ...


1

Everytime you update the ABI file, a record is stored on chain. The action is eosio::setabi. Therefore it would be possible to say which version of the ABI file was current on the blockchain at the time of a transaction being signed.


1

You can sign everything you want using eosjs-ecc. See here Github eosjs-ecc ecc.Signature.signHash(sha256hash, private_key).toString() ecc.sign(Buffer.from(data, 'utf8'), private_key) But be aware, that the transaction always has to match with the ABI.


Only top voted, non community-wiki answers of a minimum length are eligible