:ExternalAccount
leaf node

URI

Label

Externally Controlled Account

Description

One of the two main types of accounts on Ethereum, an external account is an account controlled by an external actor (as opposed to a contract account). The unique identifier of an external account is its address. It consists of the rightmost 160 bits of the keccak 256 hash of its public key (example: 0x1a1138875dAB9E0AC8b0fd4a37EEAC5eb26B870B). There is only one way external accounts can actively change the state of the blockchain. They can be used to send a valid transaction to the Ethereum blockchain. The transaction can be directed towards other external accounts or towards contract accounts. Since the private key is needed for sending, a valid transaction can only be created by the person or entity controlling the private key of the external account. Besides being target of transactions, external accounts can also be the target of contract messages, block beneficiary rewards, uncle beneficiary rewards or payouts of contract accounts that have self-destructed.

Relates an account to the Merkle Patricia tree that encodes its storage contents at a certain account state. This property is Functional because an account state can have only one instance of account storage and inverse functional because an account storage can have only one associated account state.

This is a general relation to express part of relationships. The classic study of parts and wholes, mereology, has three axioms: 1. the part-of relation is Transitive - "parts of parts are parts of the whole" - If A is part of B and B is part of C, then A is part of C Reflexive - "Everything is part of itself" - A is part of A Antisymmetric - "Nothing is a part of its parts" - if A is part of B and A != B then B is not part of A.

This property relates an EthOn class with a suggested string representation. It can be used to give the term a name, e.g. in program code.

owl:Thing

Implementation

@prefix:<http://ethon.consensys.net/>.@prefixdc:<http://purl.org/dc/elements/1.1/>.@prefixns:<http://www.w3.org/2003/06/sw-vocab-status/ns#>.@prefixowl:<http://www.w3.org/2002/07/owl#>.@prefixrdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#>.@prefixrdfs:<http://www.w3.org/2000/01/rdf-schema#>.@prefixsh:<http://www.w3.org/ns/shacl#>.@prefixskos:<http://www.w3.org/2004/02/skos/core#>.@prefixv0:<http://ethon.consensys.net/v0/>.@prefixvann:<http://purl.org/vocab/vann/>.@prefixvoid:<http://rdfs.org/ns/void#>.@prefixxml:<http://www.w3.org/XML/1998/namespace>.@prefixxsd:<http://www.w3.org/2001/XMLSchema#>.:ExternalAccountaowl:Class;rdfs:label"Externally Controlled Account"@en;:simpleDefinition"An Ethereum account usually controlled by a person. It is identified by an address (0x...) and a public/private key-pair.";:suggestedStringRepresentation"ExternalAccount"@en;rdfs:comment"One of the two main types of accounts on Ethereum, an external account is an account controlled by an external actor (as opposed to a contract account). The unique identifier of an external account is its address. It consists of the rightmost 160 bits of the keccak 256 hash of its public key (example: 0x1a1138875dAB9E0AC8b0fd4a37EEAC5eb26B870B). There is only one way external accounts can actively change the state of the blockchain. They can be used to send a valid transaction to the Ethereum blockchain. The transaction can be directed towards other external accounts or towards contract accounts. Since the private key is needed for sending, a valid transaction can only be created by the person or entity controlling the private key of the external account. Besides being target of transactions, external accounts can also be the target of contract messages, block beneficiary rewards, uncle beneficiary rewards or payouts of contract accounts that have self-destructed."@en;rdfs:subClassOf:Account;ns:term_status"unstable".

Documentation automatically generated on 22nd February 2019 with OntoDocs (v1.2.1)