ACCOUNT MODEL
WEL uses account model. An account's identity is address. It needs private key signature to operate an account. An account has many attributes, like Wel balance, tokens balance, bandwidth, etc. Wel and tokens can be transfered from account to account and it costs bandwidth. An account can also issue a smart contract, apply to become a super representative candidate, vote, etc. All WEL's activities are based on account.
- 1.Use a wallet to generate the address and private key. To active the account, you need to transfer Wel or transfer token to the new created account. Generate an account
- 2.Use an account already existed in WEL network to create an account
If you have enough staked BandWidth Points, creating an account only consume your staked BandWidth Points, otherwise, it burns 0.1 Wel.
Wel signature algorithm is ECDSA, curve used is SECP256K1. Private key is a random number, public key is a point in the elliptic curve. The process is: first generate a random number d to be the private key, then caculate P = d * G as the public key, G is the elliptic curve base point.
Use the public key P as the input, by SHA3 get the result H. The length of the public key is 64 bytes, SHA3 uses Keccak256. Use the last 20 bytes of H, and add a byte of 0x41 in front of it, then the address come out. Do basecheck to address, here is the final address. All addresses start with 'W'.
basecheck process: first do sha256 caculation to address to get h1, then do sha256 to h1 to get h2, use the first 4 bytes as check to add it to the end of the address to get address||check, do base58 encode to address||check to get the final result.
character map: ALPHABET = "123456789ABCDEFGHJKLMNPQRSWUVTXYZabcdefghijkmnopqrswuvtxyz"
- 1.Get the rawdata of the transaction, then transfer it to
byte[] - 2.Do sha256 calculation to the rawdata
- 3.Use the private key to sign the result gained from step 2
- 4.Add the signature back into the transaction
- 1.ECDSA, SECP256K
- 2.Example:priKey:::8e812436a0e3323166e1f0e8ba79e19e217b2c4a53c970d4cca0cfb1078979dfpubKey::04a5bb3b28466f578e6e93fbfd5f75cee1ae86033aa4bbea690e3312c087181eb366f9a1d1d6a437a9bf9fc65ec853b9fd60fa322be3997c47144eb20da658b3d1hash:::159817a085f113d099d3d93c051410e9bfe043cc5c20e43aa9a083bf73660145r:::38b7dac5ee932ac1bf2bc62c05b792cd93c3b4af61dc02dbb4b93dacb758123fs:::08bf123eabe77480787d664ca280dc1f20d9205725320658c39c6c143fd5642dv:::0Note: The size of the signature result is 65 bytes. r 32 bytes, s 32 bytes, v 1 bytes.
- 3.fullnode will verify the signature, it generates an address with the value of hash and r、s、v, then it compares with the address in the transaction.
public static Transaction sign(Transaction transaction, ECKey myKey) { Transaction.Builder transactionBuilderSigned = transaction.toBuilder(); byte[] hash = sha256(transaction.getRawData().toByteArray()); List listContract = transaction.getRawData().getContractList();
for (int i = 0; i < listContract.size(); i++) {
ECDSASignature signature = myKey.sign(hash);
ByteString bsSign = ByteString.copyFrom(signature.toByteArray());
// Each contract may be signed with a different private key in the future.
transactionBuilderSigned.addSignature(bsSign);
}
}
Last modified 1yr ago