From 961e3db20314535e2206e10638f980f14798a4aa Mon Sep 17 00:00:00 2001 From: Toon Sevrin Date: Wed, 30 Aug 2017 14:24:10 +0200 Subject: [PATCH] Added skip-transaction-signatures requirement --- docs/group__eosc.html | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/group__eosc.html b/docs/group__eosc.html index 779330b98..58c86b998 100644 --- a/docs/group__eosc.html +++ b/docs/group__eosc.html @@ -75,6 +75,7 @@ Creating an Account

In order to create an account you will need two new keys: owener and active. You can ask eosc to create some keys for you:

This will be your owner key,

$ ./eosc create key
public: EOS4toFS3YXEQCkuuw1aqDLrtHim86Gz9u3hBdcBw5KNPZcursVHq
private: 5JKbLfCXgcafDQVwHMm3shHt6iRWgrr9adcmt6vX3FNjAEtJGaT

And this will be your active key,

$ ./eosc create key
public: EOS7d9A3uLe6As66jzN8j44TXJUqJSK3bFjjEEqR4oTvNAB3iM9SA
private: 5Hv22aPcjnENBv6X9o9nKGdkfrW44En6z4zJUt2PobAvbQXrT9z
Note
eosc does not save the generated private key.

Next we will create the account tester, but because all accounts need to be created by an existing account we will ask the inita account to create tester using the owner and active keys created above. inita was specified in the genesis file.

+

Right now this requires eosd to be ran with the --skip-transaction-signatures flag.

$ ./eosc create account inita tester EOS4toFS3YXEQCkuuw1aqDLrtHim86Gz9u3hBdcBw5KNPZcursVHq EOS7d9A3uLe6As66jzN8j44TXJUqJSK3bFjjEEqR4oTvNAB3iM9SA
{
"transaction_id": "6acd2ece68c4b86c1fa209c3989235063384020781f2c67bbb80bc8d540ca120",
"processed": {
"refBlockNum": "25217",
"refBlockPrefix": "2095475630",
"expiration": "2017-07-25T17:54:55",
"scope": [
"eos",
"inita"
],
"signatures": [],
"messages": [{
"code": "eos",
"type": "newaccount",
"authorization": [{
"account": "inita",
"permission": "active"
}
],
"data": "c9251a0000000000b44c5a2400000000010000000102bcca6347d828d4e1868b7dfa91692a16d5b20d0ee3d16a7ca2ddcc7f6dd03344010000010000000102bcca6347d828d4e1868b7dfa91692a16d5b20d0ee3d16a7ca2ddcc7f6dd03344010000010000000001c9251a000000000061d0640b000000000100010000000000000008454f5300000000"
}
],
"output": [{
"notify": [],
"sync_transactions": [],
"async_transactions": []
}
]
}
}

After creating the account we can view the current account status like so:

$ ./eosc get account tester
{
"name": "tester",
"eos_balance": 0,
"staked_balance": 1,
"unstaking_balance": 0,
"last_unstaking_time": "1969-12-31T23:59:59"
}

You will note that there is no balance because almost all genesis EOS tokens are currently allocated to the eos account.

$ ./eosc get account eos
{
"name": "eos",
"eos_balance": "8999999999998100",
"staked_balance": 0,
"unstaking_balance": 0,
"last_unstaking_time": "1969-12-31T23:59:59",
"abi": {
"types": [{
"newTypeName": "AccountName",
"type": "Name"
}
],
"structs": [{
"name": "transfer",
"base": "",
"fields": {
"from": "AccountName",
"to": "AccountName",
"amount": "UInt64"
}
}
],
"actions": [{
"action": "transfer",
"type": "transfer"
}
],
"tables": []
}
}
Note
The eos account happens to have an ABI (Application Binary Interface) defined which provides meta-data to tools that want to interface with the eos contract.
-- GitLab