<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC4949 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4949.xml">
]>
<rfc submissionType="IETF" docName="draft-nakajima-crypto-asset-terminology-07" category="info" ipr="trust200902">
	<!-- Generated by id2xml 1.5.0 on 2020-12-31T07:05:17Z -->
	<?rfc strict="yes"?>
	<?rfc compact="yes"?>
	<?rfc subcompact="no"?>
	<?rfc symrefs="yes"?>
	<?rfc sortrefs="yes"?>
	<?rfc text-list-symbols="o*+-"?>
	<?rfc toc="yes"?>
	<front>
	<title abbrev="Cryptoassets Terminology">Terminology for Cryptoassets</title>
	<author initials="H." surname="Nakajima" fullname="Hirotaka Nakajima">
	<organization abbrev="Mercari R4D">Mercari, Inc. R4D</organization>
	<address><postal><street>Roppongi Hills Mori Tower 21F</street>
	<street>6-10-1 Roppongi</street>
	<street>Minato, Tokyo  106-6125</street>
	<street>JAPAN</street>
	</postal>
	<email>nunnun@mercari.com</email>
	</address>
	</author>

	<author initials="M." surname="Kusunoki" fullname="Masanori Kusunoki">
	<organization abbrev="JDD">Japan Digital Design, Inc.</organization>
	<address><postal><street>Nihonbashi Talk Building</street>
	<street>3-3-5, Nihonbashi-Hongokucho</street>
	<street>103-0021</street>
	<street>JAPAN</street>
	</postal>
	<email>masanori.kusunoki@japan-d2.com</email>
	</address>
	</author>

	<author initials="K." surname="Hida" fullname="Keiichi Hida">
	<organization abbrev="JBA">Japan Blockchain Association</organization>
	<address><email>hida@jba-web.jp</email>
	</address>
	</author>

	<author initials="Y." surname="Suga" fullname="Yuji Suga">
	<organization abbrev="Advanced Security Div, IIJ">Advanced Security Division, Internet Initiative Japan Inc.</organization>
	<address><postal><street>Iidabashi Grand Bloom,</street>
	<street>2-10-2 Fujimi</street>
	<street>Chiyoda, Tokyo  102-0071</street>
	<street>JAPAN</street>
	</postal>
	<email>suga@iij.ad.jp</email>
	</address>
	</author>

	<author initials="T." surname="Hayashi" fullname="Tatsuya Hayashi">
	<organization abbrev="Lepidum">Lepidum Co. Ltd.</organization>
	<address>
	<email>hayashi@lepidum.co.jp</email>
	</address>
	</author>

	<date year="2022" month="January" day="05"/>
	<abstract><t>
   This document provides terminology used in cryptoassets.</t>

	</abstract>
	</front>

	<middle>
	<section title="Introduction" anchor="sect-1"><t>
   Our goal with this document is to improve our understanding on a set
   of terms which frequently used in documents which related to
   cryptoassets.  Mutual understanding about terminology may help to
   reach a consensus on issues we're trying to solve.</t>

	</section>

	<section title="Conventions and Definitions" anchor="sect-2"><t>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all
   capitals, as shown here.</t>

	</section>

	<section title="Terms and Definitions" anchor="sect-3"><t><list style="hanging" hangIndent="3"><t hangText="address:">
	An identifier to represent a public key in a blockchain network.
	</t>

	<t hangText="administrator:">
	It is a person who conducts operational maintenance of the system with the authority to change the system settings.
	From the viewpoint of mutual checking, there are administrators with different authorities depending on the subjects to be managed. See also: operator.
	</t>

	<t hangText="asymmetric cryptography:">
	Defined in <xref target="RFC4949"/> as "A modern branch of cryptography (popularly known as "public-key cryptography") in which the algorithms use a pair of keys (a public key and a private key) and use a different component of the pair for each of two counterpart cryptographic operations (e.g., encryption and decryption, or signature creation and signature verification). " 
	</t>

	<t hangText="block:">
	A basic unit of the blockchain.  A set of transactions on a blockchain which contains a cryptographic hash value of the previous block.
	</t>

	<t hangText="blockchain:">
	An ordered series of data chains constructed that attackers cannot alter by cryptographic algorithms. A type of distributed ledger.
	</t>

	<t hangText="confirmation:">
	Approval works defined by the consensus algorithm.
	A status that blocks and transactions in a certain block are approved by miners and users of the blockchain network.
	</t>

	<t hangText="consensus:">
	Agreements among nodes in the blockchain network.
	</t>

	<t hangText="cryptoasset:">
	A digital representation of values that can be exchanged or transferred digitally, realized by a distributed ledger such as blockchain utilizing cryptography or similar technology.
	</t>

	<t hangText="cryptoassets custody service:">
	Business to manage the kind of cryptoassets.
	</t>

	<t hangText="cryptoassets custodian:">
	The business entities that operate the cryptoasset custody business.
	</t>

	<t hangText="cryptoassets custody system:">
	The information system that responsible for the cryptoasset custody business.
	</t>

	<t hangText="cryptoassets exchange:">
	A function for exchanging fiat currencies and cryptoassets, and also exchanging cryptoassets with each other.
	</t>

	<t hangText="cryptoassets exchange service provider:">
	A business entity that operates a cryptoasset exchange.
	</t>

	<t hangText="deterministic wallet:">
	See: wallet
	</t>

	<t hangText="digital signature:">
	Defined in <xref target="RFC4949"/> as "A value computed with a cryptographic algorithm and associated with a data object in such a way that any recipient of the data can use the signature to verify the data's origin and integrity." 
	</t>

	<t hangText="distributed ledger:">
	A distributed database about cryptoassets with agreed processed.
	</t>

	<t hangText="double spending:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "result of successfully spending some money more than once." fiat currency:  Currency which has been established by the government or other authorities. 
	</t>

	<t hangText="fork:">
	A branch of a ledger.  Ledger branching may occur accidentally or by specification changes.
	</t>

	<t hangText="accidental fork:">
	A case where a block is accidentally mined at about the same time, and a plurality of chains coexist temporarily.  It occurs on a daily basis and converges to the longest chain by re-org.
	</t>

	<t hangText="soft fork:">
	A branch caused by specification change of blockchain. It does not affect wallet implementation.
	</t>

	<t hangText="hard fork:">
	A branch caused by a specification change without the forward compatibility of the blockchain, which may affect the wallet implementation in addition to the miner. 
	There is a case where a plurality of chains continue to coexist permanently because there is no consensus between developers regarding the case where the majority of nodes stay in the specification change by following the hard fork, we call it split. 
	Examples of typical splits include the division of Ethereum and Ethereum Classic in The DAO case of 2016, the division of Bitcoin and Bitcoin Cash in 2017, and so on.  The new coin born by division is called a fork coin.
	</t>

	<t hangText="genesis block:">
	An initial block on a blockchain.  Genesis block may differ to distinguish chains.
	</t>

	<t hangText="hash value:">
	Defined in <xref target="RFC4949"/> as "The output of a hash function."
	</t>

	<t hangText="hash rate:">
	Amount of a hash value which node is able to generate per unit of time (generally per second)
	</t>

	<t hangText="hierarchy deterministic wallet:">
	See: wallet
	</t>

	<t hangText="mining:">
	A process to append a received transaction to a block by validating a transaction with agreed consensus rules such as proof-of-work and proof-of-stake.
	</t>

	<t hangText="miner:">
	A network node which contributes its resources to mining.
	</t>

	<t hangText="multisignature:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "requiring more than one key to authorize a bitcoin transaction".  In this scope, the transaction is not limited to a bitcoin transaction.
	</t>

	<t hangText="node:">
	A device that connects to the blockchain network.Note that the node has a different meaning in the context of expression about the Merkle tree.
	</t>

	<t hangText="off-chain transaction:">
	The movement of value outside of the blockchain
	</t>

	<t hangText="on-chain transaction:">
	The movement of value on the blockchain
	</t>

	<t hangText="operator:">
	It is a person who performs routine tasks based on authority as a normal task.  See also: administrator.
	</t>

	<t hangText="orphan block:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "Blocks whose parent block has not been processed by the local node, so they can't be fully validated yet." </t>

	<t hangText="permissioned-chain:">
	A blockchain that only specified members can join the blockchain network.
	</t>

	<t hangText="permissionless-chain:">
	See: permissioned-chain
	</t>

	<t hangText="public-chain:">
	An open blockchain that anyone can retrieve all of blocks and transactions without special privileges.
	</t>

	<t hangText="public key:">
	Defined in <xref target="RFC4949"/> as "The publicly disclosable component of a pair of cryptographic keys used for asymmetric cryptography." 
	</t>

	<t hangText="private-chain:">
	In contrast with "public-chain", A closed blockchain that only qualified users can access blocks and make transactions.
	</t>

	<t hangText="private key:">
	Defined in <xref target="RFC4949"/> as "The secret component of a pair of cryptographic keys used for asymmetric cryptography." 	
	</t>

	<t hangText="proof-of-stake:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "method by which a cryptocurrency blockchain network aims to achieve distributed consensus." 
	</t>

	<t hangText="proof-of-work:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "A piece of data that requires significant computation to find."
	</t>

	<t hangText="reorganization:">
	The convergence into one chain based on a certain consensus from multiple chains that are temporarily branched.
	</t>

	<t hangText="reward:">
	Value by the blockchain network which assigned to a miner who successfully validates a transaction. Rules may differ among blockchains and consensus rules.
	</t>

	<t hangText="side-chain:">
	See off-chain
	</t>

	<t hangText="smart contract:">
	A guaranteed digital procedure that automatically enforced on a blockchain network.
	</t>

	<t hangText="soft fork:">
	See: fork
	</t>

	<t hangText="token:">
	1) Data that represents the amount of cryptoassets like ERC20 specification, 2) Data used in the API as one of the factors with the authentication process.
	</t>

	<t hangText="transaction:">
	Defined in <xref target="MasteringBitcoinOnline"/> as "More precisely, a transaction is a signed data structure expressing a transfer of value."
	</t>

	<t hangText="incoming transaction:">
	Transfer of cryptoassets from other addresses to one's own address.
	</t>

	<t hangText="outgoing transaction:">
	Transfer of cryptoassets from one's own address to other addresses.
	</t>

	<t hangText="validation:">
	Checking the accuracy and consistency of given transactions and blocks. Specifically, it is general to verify the integrity of data to be digital-signed and also the integrity of other transactions and blocks. By verifying a transaction repeatedly, it is possible to verify blocks in the transaction.
	</t>

	<t hangText="validated:">
	See: validation
	</t>

	<t hangText="validator:">
	See: validation
	</t>

	<t hangText="wallet:">
	A mechanism that handles a key pair of a public key and a secret key used for transmitting cryptoassets and such a key pair.
	</t>

	<t hangText="hot wallet:">
	A wallet that is online connected to the network, the key is activated, and operators can coin out the cryptoassets by automatic processing.
	</t>

	<t hangText="cold wallet:">
	A wallet that is disconnected from the network and the key is inactivated. It can not be coined out unless there is an explicit operation by the operator. 
	The frequency of outgoing coins is limited.
	Between hot wallet and cold wallet, there are various intermediate forms such as a wallet that is online, but requires manual operation at the time of signing a transaction, the wallet that is offline but the operation is automated, and warm wallet.
	</t>

	</list>
	</t>

	</section>

	<section title="Symbols and abbreviated terms" anchor="sect-4"><t><list style="hanging" hangIndent="1"><t hangText="AML">
	Anti-Money Laundering
	</t>

	<t hangText="API:">
	Application Programming Interface
	</t>

	<t hangText="CFT:">
	Counter Financing of Terrorism
	</t>

	<t hangText="DAO:">
	Distributed Autonomous Organization
	</t>

	<t hangText="DLT:">
	Distributed Ledger Technologies
	</t>

	<t hangText="HD:">
	Hierarchy Deterministic (wallet)
	</t>

	<t hangText="PKI:">
	Public Key Infrastructure
	</t>

	</list>
	</t>

	</section>

	<section title="Security Considerations" anchor="sect-5"><t>
   This document defines terminology for cryptoassets.  Therefore, there is no security considerations.
	</t>

	</section>

	<section title="IANA Considerations" anchor="sect-6"><t>
   None.</t>

	</section>

	</middle>

	<back>
	<references title="Normative References">
	&RFC2119;
	&RFC8174;
	</references>
	<references title="Informative References">
	<reference anchor="MasteringBitcoinOnline" target="https://github.com/bitcoinbook/bitcoinbook"><front>
	<title>Mastering Bitcoin</title>
	<author initials="A." surname="Antonopoulos" fullname="A. Antonopoulos">
	</author>

	<date month="March" year="2018"/>
	</front>

	</reference>
	&RFC4949;
	</references>
	<references title="URIs">
	<reference anchor="ref-1" target="https://cgtf.github.io/"><front>
	<title/>
	<author>
	</author>

	<date/>
	</front>

	</reference>
	</references>
	<section title="Acknowledgments" numbered="no" anchor="acknowledgments"><t>
   Thanks to members of the Cryptoassets Governance Task Force <xref target="ref-1"/> for
   help and feedback.</t>

	</section>

	</back>

	</rfc>
	
