FEIP3V4_CID(en-US)



  • FEIP3: CID
    Version: 4
    Language: en-US
    Author: C_armX, Deisler-JJ_Sboy,Free_Cash
    Status: draft
    Created date: 2021-02-5
    Last modified date:2021-03-06
    File hash: "0dcdf9e355f108ce47f7cdc4043ca6fc6e3ea51090f80622eeae55a0c15f2c9a"
    TXid: 
    

    FEIP3V4_CID(en-US)

    Contents

    Introduction

    General rules of FEIP type protocols

    Rules specific to this protocol

    Example of Registering a CID

    Example of Unregistering a CID

    Introduction

    
    Protocol type: FEIP
    Serial number: 3
    Protocol name: CID
    Version: 4
    Description : Register or unregister a human friendly identity for an address.
    Author: C_armX, Deisler-JJ_Sboy,Free_Cash
    Language: en-US
    Tags: FEIP, CID, identity, human friendly, basic protocol
    Previous version hash:"0dcdf9e355f108ce47f7cdc4043ca6fc6e3ea51090f80622eeae55a0c15f2c9a"
    
    

    General rules of FEIP type protocols

    1. Write important data in OP_RETURN for public witness under FEIP type protocols.

    2. The max size of OP_RETURN : 4096 bytes

    3. Format : compacted json

    4. Encoding : utf-8

    Rules specific to this protocol

    1. CID(Crypto Identity):“name"+"_"+suffix, e.g. CY_vpAv.

    2. Suffix:The last four letters of the address. If the new CID is the same as any CID that has been registered, increase the length of suffix until the new CID is unique, e.g. CY_kvpAv.

    3. When an address registers a new cid, its previous cid is automatically unregistered.

    4. Once a CID is registered by an address, it cannot be registered by other addresses, even if the CID has been unregistered.

    5. An address can re-register its unregistered CID.

    OP_RETURN

    The OP_RETURN of which contains the data as follows:

    field number field name type length<br>bytes content required
    1 type String 4 Fixed: "FEIP"<br>Case insensitive Y
    2 sn int 1 Serial number<br>Fixed: 3 Y
    3 ver int 1 Fixed: 4 Y
    4 name String 3 Fixed: "CID"<br>Case insensitive N
    5 hash hex 32 Sha256 value of this protocol file N
    6 data.op string 6-8 operation: "register" or "unregister" Y
    7 data.name string 1-32 Nick name given by the user Y when operation is register,<br>N when operation is unregister

    Example of Registering a CID

    
    Address: FPL44YJRwPdd2ipziFvqq6y2tw4VnVvpAv
    CID:CY_vpAv
    OP_RETURN content:
    
    {
        "type": "FEIP",
        "sn": 3,
        "ver": 4,
        "name": "CID",
        "hash": "0dcdf9e355f108ce47f7cdc4043ca6fc6e3ea51090f80622eeae55a0c15f2c9a",
        "data":{
            "op": "register",
            "name": "CY"
            }
    }
    
    

    Example of Unregistering a CID

    
    Address: FPL44YJRwPdd2ipziFvqq6y2tw4VnVvpAv
    
    OP_RETURN content:
    
    {
        "type": "FEIP",
        "sn": 3,
        "ver": 4,
        "name": "CID",
        "hash": "0dcdf9e355f108ce47f7cdc4043ca6fc6e3ea51090f80622eeae55a0c15f2c9a",
        "data":{
            "op": "unregister"
            }
    }
    
    


  • @昌用 协议里的json 格式不对,每个键名都应该用英文半角引号括起来,键值如果是字符串,也要用英文半角引号括起来。



  • @水雷_zzHe 好,修订一下



  • @昌用 更新内容:1)标准化为英文版本,2)数据格式改为Json。

    2月15日,《FEIP3V4_CID(en-US)》(密码身份协议)发布,这是自由共识生态协议标准化启动中的第二份重要协议,是自由共识的社会基础。在主网升级,即OP_RETURN扩容后,CID系统将全面转向新协议。https://github.com/freecashorg/FEIP/blob/master/FEIP3/FEIP3V4.md

    ————————


Log in to reply