title: TRC-60:Precompiled contract function for multi-signature verification
author: Sh11thead <firstname.lastname@example.org>
discussions to: https://github.com/tronprotocol/TIPs/issues/60
This doc describes a native TVM function which is used to validate multi-signature for a provided account.
TRON provided multiple signature functions allowing for permission grading, and each permission can correspond to multiple private keys. But in TVM, currently we only have ecrecover() function to verify single-signed message.But multiple-signed message can not be verified in TVM ,to solve this case, we need a new function to support multiple-sign verification .
Developer hope to validate multi-sign for account with specific permission in smart contracts.
Add a new function named validatemultisign in solidity compiler .
This function could takes 4 parameters:
address accountAddress, // account address
uint256 permissionId, //permissionId for account
bytes32 content, //content for verifying
bytes signatures//signatures to be verified
Pay special attention to the parameter signatures,
The specific signature method is implemented in java code as follows:
//parameters address，permissionId ，hash
byte address = address
int permissionId = permissionId ;
byte hash= originData;
byte merged = ByteUtil.merge(address,ByteArray.fromInt(permissionId),data);
//get the content to sign
byte toSign = Sha256Hash.hash(merged);
List<Object> signs = new ArrayList<>();
This function will call to a specific address (for example,0x000000000000000000000000000000000000000a) which will executed precompiledContracts in TVM to validate multi-sign.Since in TRON, one transaction allow max up to 5 different account to sign,the parameter signatures is allow max up to 5.
In TVM , we could reuse ECKey.ECDSASignature.fromComponents(r, s, v)method,which is already used by ecrecover() to recover address for signature.
energy charge for the execution cost 1500 per signature
This function allows validating multi-sign in TVM could improve smart contract access to TRON blockchain which is good for both DApp developer and users.
Adding a new precompiledContract cause no backwards compatibility concerns.
1.Verifying both correct and incorrect signatures in smart contract.
2.Verifying duplicate signatures.
3.Verifying more than 5 signatures.
The text was updated successfully, but these errors were encountered: