{
  "op": [
    "comment",
    {
      "body": "Congratulations @cvb! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@cvb/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@cvb) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=cvb)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-cvb-20190719t055824000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 34790862,
  "trx_id": "afc1b4e7503e934092fdbcd0659122751f22223a",
  "op_in_trx": 0,
  "timestamp": "2019-07-19T05:58:27",
  "virtual_op": false,
  "trx_in_block": 10
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"reblog\",{\"account\":\"cvb\",\"author\":\"byteball.org\",\"permlink\":\"byteball-rebrand-the-next-step-to-real-world-adoption\"}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 29594555,
  "trx_id": "6d0f312e975d5e29f2ec841b994a42f482d96803",
  "op_in_trx": 0,
  "timestamp": "2019-01-19T14:34:51",
  "virtual_op": false,
  "trx_in_block": 24
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"cvb\",\"following\":\"xjenek\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 27257464,
  "trx_id": "223b8f0e1092ab5d010673c7b8f06e08b0b77dfd",
  "op_in_trx": 0,
  "timestamp": "2018-10-30T09:40:36",
  "virtual_op": false,
  "trx_in_block": 6
}

{
  "op": [
    "comment",
    {
      "body": "Congratulations @cvb! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/votes.png)](http://steemitboard.com/@cvb) Award for the number of upvotes\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-steem-power-followers-and-following-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-steem-power-followers-and-following-added\">SteemitBoard Ranking update - Steem Power, Followers and Following added</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-cvb-20181018t071805000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 26909264,
  "trx_id": "59e1a691efc211e16e3ca465206a53c24e2d43ea",
  "op_in_trx": 0,
  "timestamp": "2018-10-18T07:18:09",
  "virtual_op": false,
  "trx_in_block": 5
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "xjenek",
      "weight": 58,
      "rshares": 121600249,
      "permlink": "tutorial-for-developers-on-byteball-part-1",
      "pending_payout": "2.469 HBD",
      "total_vote_weight": 1332871
    }
  ],
  "block": 26859348,
  "trx_id": "9c8b8584e65f7588b65da0d5568063b161eaa569",
  "op_in_trx": 1,
  "timestamp": "2018-10-16T13:40:00",
  "virtual_op": true,
  "trx_in_block": 27
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "xjenek",
      "weight": 10000,
      "permlink": "tutorial-for-developers-on-byteball-part-1"
    }
  ],
  "block": 26859348,
  "trx_id": "9c8b8584e65f7588b65da0d5568063b161eaa569",
  "op_in_trx": 0,
  "timestamp": "2018-10-16T13:40:00",
  "virtual_op": false,
  "trx_in_block": 27
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "byteball.org",
      "weight": 29,
      "rshares": 121600249,
      "permlink": "steem-use-a-thon-by-byteball-winners-announcement",
      "pending_payout": "15.207 HBD",
      "total_vote_weight": 2858741
    }
  ],
  "block": 26614963,
  "trx_id": "cc34deee1712b3f4487ba87bf14e2534e2e199ca",
  "op_in_trx": 1,
  "timestamp": "2018-10-08T01:51:45",
  "virtual_op": true,
  "trx_in_block": 1
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "byteball.org",
      "weight": 10000,
      "permlink": "steem-use-a-thon-by-byteball-winners-announcement"
    }
  ],
  "block": 26614963,
  "trx_id": "cc34deee1712b3f4487ba87bf14e2534e2e199ca",
  "op_in_trx": 0,
  "timestamp": "2018-10-08T01:51:45",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "altcoinb",
      "weight": 58,
      "rshares": 121600249,
      "permlink": "byteball-use-a-thon-paid-surveys-polls",
      "pending_payout": "2.445 HBD",
      "total_vote_weight": 1360021
    }
  ],
  "block": 26427533,
  "trx_id": "1d96c5befab87b7a76fd5b69a910bbb71c048714",
  "op_in_trx": 1,
  "timestamp": "2018-10-01T13:34:24",
  "virtual_op": true,
  "trx_in_block": 4
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "altcoinb",
      "weight": 10000,
      "permlink": "byteball-use-a-thon-paid-surveys-polls"
    }
  ],
  "block": 26427533,
  "trx_id": "1d96c5befab87b7a76fd5b69a910bbb71c048714",
  "op_in_trx": 0,
  "timestamp": "2018-10-01T13:34:24",
  "virtual_op": false,
  "trx_in_block": 4
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "cryptories",
      "weight": 10000,
      "permlink": "cryptories-the-first-crypto-economical-game-on-byteball-platform"
    }
  ],
  "block": 26157418,
  "trx_id": "c33e4f47551585a240f41935c0b221dcae4b53b4",
  "op_in_trx": 0,
  "timestamp": "2018-09-22T04:08:54",
  "virtual_op": false,
  "trx_in_block": 14
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "cryptories",
      "weight": 655,
      "rshares": 171600248,
      "permlink": "dice-game-on-byteball-platform",
      "pending_payout": "0.019 HBD",
      "total_vote_weight": 131976
    }
  ],
  "block": 26157417,
  "trx_id": "d6d7639754d5ddd443a4daead7e3a250507d03a5",
  "op_in_trx": 1,
  "timestamp": "2018-09-22T04:08:51",
  "virtual_op": true,
  "trx_in_block": 19
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "cryptories",
      "weight": 10000,
      "permlink": "dice-game-on-byteball-platform"
    }
  ],
  "block": 26157417,
  "trx_id": "d6d7639754d5ddd443a4daead7e3a250507d03a5",
  "op_in_trx": 0,
  "timestamp": "2018-09-22T04:08:51",
  "virtual_op": false,
  "trx_in_block": 19
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"cvb\",\"following\":\"cryptories\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 25608142,
  "trx_id": "3f41e8e1c89b00fc084f4bd08ad95bf12c2a6735",
  "op_in_trx": 0,
  "timestamp": "2018-09-02T13:13:27",
  "virtual_op": false,
  "trx_in_block": 14
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "cvb",
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25509675,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 2,
  "timestamp": "2018-08-30T03:07:42",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "comment",
    {
      "body": "Don't hubs get 50% of the fee?  As 1st to see the transaction.",
      "title": "",
      "author": "lukie",
      "permlink": "re-cvb-byteball-s-current-problems-and-improvement-directions-20180826t000056446z",
      "json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25390801,
  "trx_id": "5ee300148bbf229a43d789ddc08e340030fcd307",
  "op_in_trx": 0,
  "timestamp": "2018-08-26T00:01:00",
  "virtual_op": false,
  "trx_in_block": 3
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "drsensor",
      "author": "cvb",
      "weight": 12269,
      "rshares": 3216146412,
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "pending_payout": "0.017 HBD",
      "total_vote_weight": 115442
    }
  ],
  "block": 25353094,
  "trx_id": "e8ce771c638c32a5849db7908fc8aaf3c9f00432",
  "op_in_trx": 1,
  "timestamp": "2018-08-24T16:34:09",
  "virtual_op": true,
  "trx_in_block": 24
}

{
  "op": [
    "vote",
    {
      "voter": "drsensor",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25353094,
  "trx_id": "e8ce771c638c32a5849db7908fc8aaf3c9f00432",
  "op_in_trx": 0,
  "timestamp": "2018-08-24T16:34:09",
  "virtual_op": false,
  "trx_in_block": 24
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"cvb\",\"following\":\"fabien\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 25336954,
  "trx_id": "8034872492d30ce75b59aa4d2f1016e1f9fccdb3",
  "op_in_trx": 0,
  "timestamp": "2018-08-24T03:06:36",
  "virtual_op": false,
  "trx_in_block": 23
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "angr",
      "author": "cvb",
      "weight": 71750,
      "rshares": 8880864810,
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "pending_payout": "0.013 HBD",
      "total_vote_weight": 103173
    }
  ],
  "block": 25317822,
  "trx_id": "185f404d7c99608f2fa95eb14d0cd633d9746c24",
  "op_in_trx": 1,
  "timestamp": "2018-08-23T11:09:09",
  "virtual_op": true,
  "trx_in_block": 4
}

{
  "op": [
    "vote",
    {
      "voter": "angr",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25317822,
  "trx_id": "185f404d7c99608f2fa95eb14d0cd633d9746c24",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T11:09:09",
  "virtual_op": false,
  "trx_in_block": 4
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "cvb",
      "weight": 2619,
      "rshares": 171600248,
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "pending_payout": "0.001 HBD",
      "total_vote_weight": 31423
    }
  ],
  "block": 25317064,
  "trx_id": "dae91a1e3a887a1528df0276f5d7e6e01f44ca89",
  "op_in_trx": 1,
  "timestamp": "2018-08-23T10:31:15",
  "virtual_op": true,
  "trx_in_block": 30
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25317064,
  "trx_id": "dae91a1e3a887a1528df0276f5d7e6e01f44ca89",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T10:31:15",
  "virtual_op": false,
  "trx_in_block": 30
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "flowering-cycas",
      "author": "cvb",
      "weight": 3152,
      "rshares": 206569767,
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "pending_payout": "0.001 HBD",
      "total_vote_weight": 28804
    }
  ],
  "block": 25309379,
  "trx_id": "ab99eae02db52e11041dafda6e667214069d8009",
  "op_in_trx": 1,
  "timestamp": "2018-08-23T04:06:51",
  "virtual_op": true,
  "trx_in_block": 21
}

{
  "op": [
    "vote",
    {
      "voter": "flowering-cycas",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25309379,
  "trx_id": "ab99eae02db52e11041dafda6e667214069d8009",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T04:06:51",
  "virtual_op": false,
  "trx_in_block": 21
}

{
  "op": [
    "comment",
    {
      "body": "Hi ~ I'm a robot of red2018.I just upvoted your post! \r\n Please come visit me here: https://steemit.com/@red2018 \r\n Thanks so much~!!",
      "title": "",
      "author": "red2018",
      "permlink": "re-byteball-s-current-problems-and-improvement-directions-20180823t040025",
      "json_metadata": "{\"app\": \"piston-lib/0.5.7\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25309252,
  "trx_id": "e3e5b4767fd4a496c0018af68cd17ed75cebfc0f",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T04:00:30",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "red2018",
      "author": "cvb",
      "weight": 25652,
      "rshares": 607445437,
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 25652
    }
  ],
  "block": 25309251,
  "trx_id": "a9d65d15b0b1f9d6bd4eeb3853cf27ea906e3993",
  "op_in_trx": 1,
  "timestamp": "2018-08-23T04:00:27",
  "virtual_op": true,
  "trx_in_block": 42
}

{
  "op": [
    "vote",
    {
      "voter": "red2018",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-s-current-problems-and-improvement-directions"
    }
  ],
  "block": 25309251,
  "trx_id": "a9d65d15b0b1f9d6bd4eeb3853cf27ea906e3993",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T04:00:27",
  "virtual_op": false,
  "trx_in_block": 42
}

{
  "op": [
    "account_update",
    {
      "account": "cvb",
      "memo_key": "STM6rqVTLBSV2KyRvDLxVddyur7VJ8eS1YfhsXPm7iLrj285d88MB",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmd3ELADCcLyJGiwhG9qtRb6q1CdyQATbehgfDJb9Bz6wx/timg.jpg\",\"cover_image\":\"https://cdn.steemitimages.com/DQmaf3JcS5FfeMteFtKZ8bMpVWMi3tanNH2Z7NrzLWpRU3u/timg%20(1).jpg\"}}"
    }
  ],
  "block": 25308698,
  "trx_id": "5d733eb6aeac1567512021c39bb6f4a78867775d",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:32:48",
  "virtual_op": false,
  "trx_in_block": 35
}

{
  "op": [
    "account_update",
    {
      "account": "cvb",
      "memo_key": "STM6rqVTLBSV2KyRvDLxVddyur7VJ8eS1YfhsXPm7iLrj285d88MB",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmd3ELADCcLyJGiwhG9qtRb6q1CdyQATbehgfDJb9Bz6wx/timg.jpg\",\"cover_image\":\"https://cdn.steemitimages.com/DQmd3ELADCcLyJGiwhG9qtRb6q1CdyQATbehgfDJb9Bz6wx/timg.jpg\"}}"
    }
  ],
  "block": 25308609,
  "trx_id": "f203c50351db495430364797ebc4b8d8f2f6c76a",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:28:21",
  "virtual_op": false,
  "trx_in_block": 22
}

{
  "op": [
    "account_update",
    {
      "account": "cvb",
      "memo_key": "STM6rqVTLBSV2KyRvDLxVddyur7VJ8eS1YfhsXPm7iLrj285d88MB",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmd3ELADCcLyJGiwhG9qtRb6q1CdyQATbehgfDJb9Bz6wx/timg.jpg\"}}"
    }
  ],
  "block": 25308529,
  "trx_id": "622159beef7445f52d8e80714f6758a2a1196ae3",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:24:21",
  "virtual_op": false,
  "trx_in_block": 18
}

{
  "op": [
    "comment",
    {
      "body": "Byteball is a new digital asset platform based on DAG technology. It not only supports P2P payment, but also supports smart contracts, oracles, privacy assets, ICO and other functions. Byteball's wallet is designed to be very powerful and user-friendly. However, through careful study of Byteball, it will be found that there are certain defects in the design and implementation. If these problems are solved well, Byteball will be among the mainstream digital asset platforms.\n\n**Network performance problem\nA recent test of the byteball main network gives three conclusions:\n\n(1) The transaction processing speed can only reach about 15 TPS;\n(2) The network is vulnerable to DOS attacks, and a large number of bursty malicious transactions block the network and reduce the transaction processing speed of the network;\n(3) As the number of transactions increases, the transaction confirmation time can be kept stable.\n\nThe DAG base chain, the stress test is quite disappointing, which obviously does not give full play to the advantages of DAG technology. Different from the traditional blockchain transaction processing speed is limited by the block size, the transaction processing speed of the Byteball network may be related to the code execution speed, network transmission delay, hardware processing capability and the like. Founder Tony acknowledged in the Slack channel that a large number of SQL operations in the byteball code implementation increased processing latency, which may be an important reason for the performance of the byteball processing.\n\n* So, can you optimize the database design and SQL operations of the byteball?\n\nDAG is the underlying data structure of Byteball, and its corresponding data should naturally be stored using the graph database. This requires redesigning the Byteball database and rewriting the underlying code of the Byteball. At the same time, you need a high-performance serverless embedded graph database, such as leveldb based on leveldb. One of the biggest benefits of using a graph database is that it can reduce a large number of SQL multi-table join queries and simplify multi-level backtracking operations when validating transactions, thereby improving its processing performance.\n\n**Hub node problem\nIn a Byteball network, a Hub node is a backbone node in the network, which forms a P2P network between them, and other nodes need to communicate with each other through them. Multiple Hubs can exist in the entire network, and users can freely choose the Hub they want to access. It should be noted here that the Relay node has similar functions as the Hub node, but does not provide an end-to-end information encryption service. In the following discussion, the Hub/Relay node is collectively referred to as a Hub node unless otherwise specified.\n\n![](https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png)\n\nFrom a technical point of view, the Hub node is based on a full-node wallet and provides some additional data forwarding capabilities. From a data storage perspective: the light wallet does not save the complete ledger data; the full-node wallet and the witness save the complete ledger data, but only for their own use; only the Hub node saves the complete ledger data, and with other The nodes are shared.\n\nImagine if the Hub node does evil, it can refuse to provide Byteball network access services for other nodes such as the wallet connected to it, and refuse to broadcast and share transaction data for them. There is also an extreme case where if all witness nodes are connected to the same Hub node, then it will become the overlord in the entire network. If other Hub nodes cannot obtain the service of the Hub node, all transactions broadcast by other Hub nodes cannot be confirmed by the network. This means that those Hub nodes are not working properly.\n\n![](https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png)\n\nThe Hub node plays an important role in the validity, reliability and security of the ledger data. However, under the current implementation of Byteball, the Hub node is completely free of revenue incentives, and at the same time bear the corresponding server expenses. In fact, the main use of the entire network is the official Hub node (wss://byteball.org/bb/).\n\n*So, should the Hub node playing such an important role be given economic incentives and limit some of its power?\n\nThe purpose of designing economic incentives is to make more people willing to run Hub nodes and provide fairer and more efficient services for the entire network. At the same time, in order to relatively restrict the power of the Hub node, it is recommended to enhance the status of the witness node and the whole node wallet in the network structure, that is, they can form a P2P network.\n\n** Witness's question\nWitnesses is used by Byteball to achieve a consensus across the network. Witnesses continue to send transactions to confirm transactions with other users. Byteball's request to witnesses is: a well-known user or institution in the real world to ensure that it has a good reputation. Once the witnesses commit evil acts, then he will be discredited. The requirements are so strict, but the witness can only get a small fee. Who would like to put their reputation on a digital asset platform like Byteball? The current reality is that most of the witness nodes are in the hands of founder Tony.\n\nOne of the basic ideas of Byteball's consensus mechanism is to select a main chain, all units can be ordered according to this main chain, thus solving the double flower problem. In terms of image, this main chain is similar to a highway, and other branches connected to the main chain are provincial roads. In this way, network processing efficiency can be greatly improved. Byteball chooses the main chain by means of witnesses, and the transactions on the main chain are recognized by most witnesses. Of course, there are other ways to choose the main chain, such as using the POW method. The most popular xdag adopts this idea.\n\n* So, can Byteball's consensus mechanism evolve into a POS-based witness mechanism?\n\nThis means that the list of witnesses is not fixed and is not manually selected by the user. The Witness List is generated by means of POS, generating a list of witnesses at regular intervals and building a consensus based on this. In POS, users with more assets are more inclined to maintain the normal operation of the network.\n\n** fee problem\nThe transaction fee in Byteball is divided into two parts, one for the witness and the other for the subunit.\n\nThe transaction fee assigned to the witness is called payload commission, which is proportional to the number of bytes occupied by the transaction storage content. However, in reality, the size of the transaction storage content is no different for the witness. What the witness needs to do is to continuously generate the transaction unit.\n\nThe transaction fee assigned to a subunit is called a header commission, which is basically a fixed value. It is designed to allow users to choose the newly created trading unit as much as possible so that the width of the DAG is not too large. In fact, it is very doubtful that ordinary users receive a small amount of handling fees. Although user behavior contributes to the confirmation of the transaction unit, it is usually an even issue. Nodes such as the Hub that carry the heavy responsibility of the network are not motivated. As for limiting the width of the DAG, it is entirely possible to give the newly generated node a higher weight when selecting the parent node.\n\n* So, is it possible to redesign the fee structure and assign it to nodes that maintain the normal operation of the network?\n\nAbove we discussed the incentives for the Hub node, the part of the fee that should be added to the Hub node; at the same time, the part assigned to the sub-unit is removed, and the better parent node selection algorithm is substituted.",
      "title": "Byteball's current problems and suggestions for improvement directions",
      "author": "cvb",
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "json_metadata": "{\"tags\":[\"byteball\",\"cryptocurrency\",\"crypto\",\"blockchain\",\"cn\"],\"image\":[\"https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png\",\"https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "byteball"
    }
  ],
  "block": 25308386,
  "trx_id": "b6d2ced455b3436fbea604708326ecd076c892ba",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:17:09",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "comment",
    {
      "body": "Byteball is a new digital asset platform based on DAG technology. It not only supports P2P payment, but also supports smart contracts, oracles, privacy assets, ICO and other functions. Byteball's wallet is designed to be very powerful and user-friendly. However, through careful study of Byteball, it will be found that there are certain defects in the design and implementation. If these problems are solved well, Byteball will be among the mainstream digital asset platforms.\n\n**Network performance problem\nA recent test of the byteball main network gives three conclusions:\n\n(1) The transaction processing speed can only reach about 15 TPS;\n(2) The network is vulnerable to DOS attacks, and a large number of bursty malicious transactions block the network and reduce the transaction processing speed of the network;\n(3) As the number of transactions increases, the transaction confirmation time can be kept stable.\n\nThe DAG base chain, the stress test is quite disappointing, which obviously does not give full play to the advantages of DAG technology. Different from the traditional blockchain transaction processing speed is limited by the block size, the transaction processing speed of the Byteball network may be related to the code execution speed, network transmission delay, hardware processing capability and the like. Founder Tony acknowledged in the Slack channel that a large number of SQL operations in the byteball code implementation increased processing latency, which may be an important reason for the performance of the byteball processing.\n\n* So, can you optimize the database design and SQL operations of the byteball?\n\nDAG is the underlying data structure of Byteball, and its corresponding data should naturally be stored using the graph database. This requires redesigning the Byteball database and rewriting the underlying code of the Byteball. At the same time, you need a high-performance serverless embedded graph database, such as leveldb based on leveldb. One of the biggest benefits of using a graph database is that it can reduce a large number of SQL multi-table join queries and simplify multi-level backtracking operations when validating transactions, thereby improving its processing performance.\n\n**Hub node problem\nIn a Byteball network, a Hub node is a backbone node in the network, which forms a P2P network between them, and other nodes need to communicate with each other through them. Multiple Hubs can exist in the entire network, and users can freely choose the Hub they want to access. It should be noted here that the Relay node has similar functions as the Hub node, but does not provide an end-to-end information encryption service. In the following discussion, the Hub/Relay node is collectively referred to as a Hub node unless otherwise specified.\n\n![](https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png)\n\nFrom a technical point of view, the Hub node is based on a full-node wallet and provides some additional data forwarding capabilities. From a data storage perspective: the light wallet does not save the complete ledger data; the full-node wallet and the witness save the complete ledger data, but only for their own use; only the Hub node saves the complete ledger data, and with other The nodes are shared.\n\nImagine if the Hub node does evil, it can refuse to provide Byteball network access services for other nodes such as the wallet connected to it, and refuse to broadcast and share transaction data for them. There is also an extreme case where if all witness nodes are connected to the same Hub node, then it will become the overlord in the entire network. If other Hub nodes cannot obtain the service of the Hub node, all transactions broadcast by other Hub nodes cannot be confirmed by the network. This means that those Hub nodes are not working properly.\n\n![](https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png)\n\nThe Hub node plays an important role in the validity, reliability and security of the ledger data. However, under the current implementation of Byteball, the Hub node is completely free of revenue incentives, and at the same time bear the corresponding server expenses. In fact, the main use of the entire network is the official Hub node (wss://byteball.org/bb/).\n\n*So, should the Hub node playing such an important role be given economic incentives and limit some of its power?\n\nThe purpose of designing economic incentives is to make more people willing to run Hub nodes and provide fairer and more efficient services for the entire network. At the same time, in order to relatively restrict the power of the Hub node, it is recommended to enhance the status of the witness node and the whole node wallet in the network structure, that is, they can form a P2P network.\n\n** Witness's question\nWitnesses is used by Byteball to achieve a consensus across the network. Witnesses continue to send transactions to confirm transactions with other users. Byteball's request to witnesses is: a well-known user or institution in the real world to ensure that it has a good reputation. Once the witnesses commit evil acts, then he will be discredited. The requirements are so strict, but the witness can only get a small fee. Who would like to put their reputation on a digital asset platform like Byteball? The current reality is that most of the witness nodes are in the hands of founder Tony.\n\nOne of the basic ideas of Byteball's consensus mechanism is to select a main chain, all units can be ordered according to this main chain, thus solving the double flower problem. In terms of image, this main chain is similar to a highway, and other branches connected to the main chain are provincial roads. In this way, network processing efficiency can be greatly improved. Byteball chooses the main chain by means of witnesses, and the transactions on the main chain are recognized by most witnesses. Of course, there are other ways to choose the main chain, such as using the POW method. The most popular xdag adopts this idea.\n\n* So, can Byteball's consensus mechanism evolve into a POS-based witness mechanism?\n\nThis means that the list of witnesses is not fixed and is not manually selected by the user. The Witness List is generated by means of POS, generating a list of witnesses at regular intervals and building a consensus based on this. In POS, users with more assets are more inclined to maintain the normal operation of the network.\n\n** fee problem\nThe transaction fee in Byteball is divided into two parts, one for the witness and the other for the subunit.\n\nThe transaction fee assigned to the witness is called payload commission, which is proportional to the number of bytes occupied by the transaction storage content. However, in reality, the size of the transaction storage content is no different for the witness. What the witness needs to do is to continuously generate the transaction unit.\n\nThe transaction fee assigned to a subunit is called a header commission, which is basically a fixed value. It is designed to allow users to choose the newly created trading unit as much as possible so that the width of the DAG is not too large. In fact, it is very doubtful that ordinary users receive a small amount of handling fees. Although user behavior contributes to the confirmation of the transaction unit, it is usually an even issue. Nodes such as the Hub that carry the heavy responsibility of the network are not motivated. As for limiting the width of the DAG, it is entirely possible to give the newly generated node a higher weight when selecting the parent node.\n\n* So, is it possible to redesign the fee structure and assign it to nodes that maintain the normal operation of the network?\n\nAbove we discussed the incentives for the Hub node, the part of the fee that should be added to the Hub node; at the same time, the part assigned to the sub-unit is removed, and the better parent node selection algorithm is substituted.",
      "title": "Byteball's current problems and suggestions for improvement directions",
      "author": "cvb",
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "json_metadata": "{\"tags\":[\"byteball\",\"cryptocurrency\",\"crypto\",\"blockchain\",\"steemit\"],\"image\":[\"https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png\",\"https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "byteball"
    }
  ],
  "block": 25308294,
  "trx_id": "b81ed780dba7c04796b9672844444cfe19a2adc4",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:12:33",
  "virtual_op": false,
  "trx_in_block": 23
}

{
  "op": [
    "comment",
    {
      "body": "Byteball is a new digital asset platform based on DAG technology. It not only supports P2P payment, but also supports smart contracts, oracles, privacy assets, ICO and other functions. Byteball's wallet is designed to be very powerful and user-friendly. However, through careful study of Byteball, it will be found that there are certain defects in the design and implementation. If these problems are solved well, Byteball will be among the mainstream digital asset platforms.\n\n**Network performance problem\nA recent test of the byteball main network gives three conclusions:\n\n(1) The transaction processing speed can only reach about 15 TPS;\n(2) The network is vulnerable to DOS attacks, and a large number of bursty malicious transactions block the network and reduce the transaction processing speed of the network;\n(3) As the number of transactions increases, the transaction confirmation time can be kept stable.\n\nThe DAG base chain, the stress test is quite disappointing, which obviously does not give full play to the advantages of DAG technology. Different from the traditional blockchain transaction processing speed is limited by the block size, the transaction processing speed of the Byteball network may be related to the code execution speed, network transmission delay, hardware processing capability and the like. Founder Tony acknowledged in the Slack channel that a large number of SQL operations in the byteball code implementation increased processing latency, which may be an important reason for the performance of the byteball processing.\n\n* So, can you optimize the database design and SQL operations of the byteball?\n\nDAG is the underlying data structure of Byteball, and its corresponding data should naturally be stored using the graph database. This requires redesigning the Byteball database and rewriting the underlying code of the Byteball. At the same time, you need a high-performance serverless embedded graph database, such as leveldb based on leveldb. One of the biggest benefits of using a graph database is that it can reduce a large number of SQL multi-table join queries and simplify multi-level backtracking operations when validating transactions, thereby improving its processing performance.\n\n**Hub node problem\nIn a Byteball network, a Hub node is a backbone node in the network, which forms a P2P network between them, and other nodes need to communicate with each other through them. Multiple Hubs can exist in the entire network, and users can freely choose the Hub they want to access. It should be noted here that the Relay node has similar functions as the Hub node, but does not provide an end-to-end information encryption service. In the following discussion, the Hub/Relay node is collectively referred to as a Hub node unless otherwise specified.\n\n![](https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png)\n\nFrom a technical point of view, the Hub node is based on a full-node wallet and provides some additional data forwarding capabilities. From a data storage perspective: the light wallet does not save the complete ledger data; the full-node wallet and the witness save the complete ledger data, but only for their own use; only the Hub node saves the complete ledger data, and with other The nodes are shared.\n\nImagine if the Hub node does evil, it can refuse to provide Byteball network access services for other nodes such as the wallet connected to it, and refuse to broadcast and share transaction data for them. There is also an extreme case where if all witness nodes are connected to the same Hub node, then it will become the overlord in the entire network. If other Hub nodes cannot obtain the service of the Hub node, all transactions broadcast by other Hub nodes cannot be confirmed by the network. This means that those Hub nodes are not working properly.\n\n![](https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png)\n\nThe Hub node plays an important role in the validity, reliability and security of the ledger data. However, under the current implementation of Byteball, the Hub node is completely free of revenue incentives, and at the same time bear the corresponding server expenses. In fact, the main use of the entire network is the official Hub node (wss://byteball.org/bb/).\n\n*So, should the Hub node playing such an important role be given economic incentives and limit some of its power?\n\nThe purpose of designing economic incentives is to make more people willing to run Hub nodes and provide fairer and more efficient services for the entire network. At the same time, in order to relatively restrict the power of the Hub node, it is recommended to enhance the status of the witness node and the whole node wallet in the network structure, that is, they can form a P2P network.\n\n** Witness's question\nWitnesses is used by Byteball to achieve a consensus across the network. Witnesses continue to send transactions to confirm transactions with other users. Byteball's request to witnesses is: a well-known user or institution in the real world to ensure that it has a good reputation. Once the witnesses commit evil acts, then he will be discredited. The requirements are so strict, but the witness can only get a small fee. Who would like to put their reputation on a digital asset platform like Byteball? The current reality is that most of the witness nodes are in the hands of founder Tony.\n\nOne of the basic ideas of Byteball's consensus mechanism is to select a main chain, all units can be ordered according to this main chain, thus solving the double flower problem. In terms of image, this main chain is similar to a highway, and other branches connected to the main chain are provincial roads. In this way, network processing efficiency can be greatly improved. Byteball chooses the main chain by means of witnesses, and the transactions on the main chain are recognized by most witnesses. Of course, there are other ways to choose the main chain, such as using the POW method. The most popular xdag adopts this idea.\n\n* So, can Byteball's consensus mechanism evolve into a POS-based witness mechanism?\n\nThis means that the list of witnesses is not fixed and is not manually selected by the user. The Witness List is generated by means of POS, generating a list of witnesses at regular intervals and building a consensus based on this. In POS, users with more assets are more inclined to maintain the normal operation of the network.\n\n** fee problem\nThe transaction fee in Byteball is divided into two parts, one for the witness and the other for the subunit.\n\nThe transaction fee assigned to the witness is called payload commission, which is proportional to the number of bytes occupied by the transaction storage content. However, in reality, the size of the transaction storage content is no different for the witness. What the witness needs to do is to continuously generate the transaction unit.\n\nThe transaction fee assigned to a subunit is called a header commission, which is basically a fixed value. It is designed to allow users to choose the newly created trading unit as much as possible so that the width of the DAG is not too large. In fact, it is very doubtful that ordinary users receive a small amount of handling fees. Although user behavior contributes to the confirmation of the transaction unit, it is usually an even issue. Nodes such as the Hub that carry the heavy responsibility of the network are not motivated. As for limiting the width of the DAG, it is entirely possible to give the newly generated node a higher weight when selecting the parent node.\n\n* So, is it possible to redesign the fee structure and assign it to nodes that maintain the normal operation of the network?\n\nAbove we discussed the incentives for the Hub node, the part of the fee that should be added to the Hub node; at the same time, the part assigned to the sub-unit is removed, and the better parent node selection algorithm is substituted.",
      "title": "Byteball's current problems and improvement directions",
      "author": "cvb",
      "permlink": "byteball-s-current-problems-and-improvement-directions",
      "json_metadata": "{\"tags\":[\"byteball\",\"cryptocurrency\",\"crypto\",\"blockchain\",\"steemit\"],\"image\":[\"https://cdn.steemitimages.com/DQmSQcZEgW6H7k3LRJT23eYhBo9cSpthPZhebLYXtuzBe8m/image.png\",\"https://cdn.steemitimages.com/DQmeCCMyGM2X26ECcV92r129qVBBoF7Ta46UiYNHJCXadnB/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "byteball"
    }
  ],
  "block": 25308198,
  "trx_id": "e241eede4bac885e4ce79d84193b7f5f33b4fb99",
  "op_in_trx": 0,
  "timestamp": "2018-08-23T03:07:45",
  "virtual_op": false,
  "trx_in_block": 5
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "lunaticpandora",
      "weight": 10000,
      "permlink": "capybara-exchange-enters-the-fray"
    }
  ],
  "block": 25048268,
  "trx_id": "a274edc6786929366e1ce5c8dd193127aadcb7ce",
  "op_in_trx": 0,
  "timestamp": "2018-08-14T02:27:18",
  "virtual_op": false,
  "trx_in_block": 3
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cvb",
      "author": "unknownheroes",
      "weight": 1310,
      "rshares": 171600248,
      "permlink": "greetings-unknown-heroes-foundation-results-update",
      "pending_payout": "0.012 HBD",
      "total_vote_weight": 94719
    }
  ],
  "block": 24934468,
  "trx_id": "b800ff3c9b0a1978d7562f7a5d4eac29d4c00a1e",
  "op_in_trx": 1,
  "timestamp": "2018-08-10T03:35:30",
  "virtual_op": true,
  "trx_in_block": 1
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "unknownheroes",
      "weight": 10000,
      "permlink": "greetings-unknown-heroes-foundation-results-update"
    }
  ],
  "block": 24934468,
  "trx_id": "b800ff3c9b0a1978d7562f7a5d4eac29d4c00a1e",
  "op_in_trx": 0,
  "timestamp": "2018-08-10T03:35:30",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "transfer_to_savings",
    {
      "to": "cvb",
      "from": "cvb",
      "memo": "",
      "amount": "1.613 HIVE"
    }
  ],
  "block": 24933893,
  "trx_id": "69f1e2f5549f2882c4ae17556c7315f16226b07c",
  "op_in_trx": 0,
  "timestamp": "2018-08-10T03:06:45",
  "virtual_op": false,
  "trx_in_block": 23
}

{
  "op": [
    "claim_reward_balance",
    {
      "account": "cvb",
      "reward_hbd": "0.665 HBD",
      "reward_hive": "0.763 HIVE",
      "reward_vests": "2495.685336 VESTS"
    }
  ],
  "block": 24761335,
  "trx_id": "1c4a417dcdb2875842760fdf4aecb3ecad963e3b",
  "op_in_trx": 0,
  "timestamp": "2018-08-04T03:15:21",
  "virtual_op": false,
  "trx_in_block": 11
}

{
  "op": [
    "comment",
    {
      "body": "Nice work! Great summary of Byteball networking. I like the network diagram with all the different roles and how they are connected. \nAlthough wallets have a primary hub, full wallets are actually connected to many. Hub addresses are sent around and each wallet connects to a bunch so if one goes down, another takes over. \nIn Byteball the hub/wallet/oracle/witness roles are a little fuzzy since they all base on the same core library, so for example a full wallet can act as a hub an oracle and a witness all in one.",
      "title": "",
      "author": "byteball.market",
      "permlink": "re-cvb-byteball-principle-analysis-4-network-structure-20180726t150450891z",
      "json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24516881,
  "trx_id": "d52861cdba958ebb612a75bef26e8f9c8fb7919c",
  "op_in_trx": 0,
  "timestamp": "2018-07-26T15:04:54",
  "virtual_op": false,
  "trx_in_block": 19
}

{
  "op": [
    "vote",
    {
      "voter": "byteball.market",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24516494,
  "trx_id": "4811f79b0def42938f29c589627497fc008c0698",
  "op_in_trx": 0,
  "timestamp": "2018-07-26T14:45:27",
  "virtual_op": false,
  "trx_in_block": 31
}

{
  "op": [
    "comment_payout_update",
    {
      "author": "cvb",
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24508116,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 16,
  "timestamp": "2018-07-26T07:45:27",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "comment_reward",
    {
      "author": "cvb",
      "payout": "4.639 HBD",
      "permlink": "byteball-principle-analysis-4-network-structure",
      "author_rewards": 2461,
      "total_payout_value": "3.506 HBD",
      "curator_payout_value": "1.132 HBD",
      "beneficiary_payout_value": "0.000 HBD"
    }
  ],
  "block": 24508116,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 15,
  "timestamp": "2018-07-26T07:45:27",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "author_reward",
    {
      "author": "cvb",
      "permlink": "byteball-principle-analysis-4-network-structure",
      "hbd_payout": "0.665 HBD",
      "hive_payout": "0.763 HIVE",
      "vesting_payout": "2495.685336 VESTS",
      "payout_must_be_claimed": true,
      "curators_vesting_payout": "1611.754543 VESTS"
    }
  ],
  "block": 24508116,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 14,
  "timestamp": "2018-07-26T07:45:27",
  "virtual_op": true,
  "trx_in_block": 4294967295
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"cvb\",\"following\":\"jacksonmil980\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 24476409,
  "trx_id": "3d3f53cd48edb1a3d8b7c55a076fce9a8729924e",
  "op_in_trx": 0,
  "timestamp": "2018-07-25T05:19:09",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "comment",
    {
      "body": "Quite an extensive and very well structured walkthrough of all the nuts and bolts of Byteball. There seem to be some weird formatting near the end, where the words \"sender\" and \"receiver\" gets added more or less randomly.\n\nOther than that, you've really done an amazing job at explaining the way the platform works.\n\nThank you for taking the time to do this.",
      "title": "",
      "author": "punqtured",
      "permlink": "re-cvb-byteball-principle-analysis-4-network-structure-20180721t193930950z",
      "json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24378498,
  "trx_id": "0e9474d61b5695ad0747765f03c742280762fff6",
  "op_in_trx": 0,
  "timestamp": "2018-07-21T19:39:36",
  "virtual_op": false,
  "trx_in_block": 19
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "punqtured",
      "author": "cvb",
      "weight": 3639,
      "rshares": 9990560346,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "4.929 HBD",
      "total_vote_weight": 1573989
    }
  ],
  "block": 24378446,
  "trx_id": "48e0c7465dfdaff8599672b55acd98c4f6ff6ae6",
  "op_in_trx": 1,
  "timestamp": "2018-07-21T19:37:00",
  "virtual_op": true,
  "trx_in_block": 34
}

{
  "op": [
    "vote",
    {
      "voter": "punqtured",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24378446,
  "trx_id": "48e0c7465dfdaff8599672b55acd98c4f6ff6ae6",
  "op_in_trx": 0,
  "timestamp": "2018-07-21T19:37:00",
  "virtual_op": false,
  "trx_in_block": 34
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "angr",
      "author": "cvb",
      "weight": 252,
      "rshares": 529121461,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "5.021 HBD",
      "total_vote_weight": 1570350
    }
  ],
  "block": 24367706,
  "trx_id": "84b68d1c65138511553c165f7ea5a0eac8e70f83",
  "op_in_trx": 1,
  "timestamp": "2018-07-21T10:39:45",
  "virtual_op": true,
  "trx_in_block": 1
}

{
  "op": [
    "vote",
    {
      "voter": "angr",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24367706,
  "trx_id": "84b68d1c65138511553c165f7ea5a0eac8e70f83",
  "op_in_trx": 0,
  "timestamp": "2018-07-21T10:39:45",
  "virtual_op": false,
  "trx_in_block": 1
}

{
  "op": [
    "comment",
    {
      "body": "Right thoughts you have @cvb, and set them cool",
      "title": "",
      "author": "surikowstepanuk",
      "permlink": "re-cvb-byteball-principle-analysis-4-network-structure-20180720t162517317z",
      "json_metadata": "{\"tags\":[\"byteball\"],\"users\":[\"cvb\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24345833,
  "trx_id": "76cca217736fab19cb61e5229bc2ba1bf635c6e9",
  "op_in_trx": 0,
  "timestamp": "2018-07-20T16:25:21",
  "virtual_op": false,
  "trx_in_block": 20
}

{
  "op": [
    "comment",
    {
      "body": "Byteball's network structure\nFrom the point of view of node function, Byteball network nodes can be divided into relay nodes, hub nodes, broadcast nodes (Oracle), witness nodes (Witness), and wallet nodes (Wallet):\n\n*Relay: Responsible for forwarding the unit to the node connected to it, storing the entire Byteball blockchain database, but it does not save any private key and does not send any unit;\n*Hub: Provides an end-to-end encrypted message transmission channel for devices connected to it, such as sending and receiving private assets, multi-signature transactions, chat messages, etc. Other functions are the same as relay nodes. The default Hub address is wss://byteball.org/bb;\n*Broadcast Node (Oracle): Responsible for continuously broadcasting data to the Byteball network, the data can be time, price, or even Bitcoin transactions;\n*Witness: responsible for sending a unit at a fixed address without interruption, and any node that satisfies this condition may become a witness;\n*Wallet node: responsible for interacting with users, sending and receiving transactions, messages, etc.\nThe following figure shows a schematic diagram of the Byteball network structure :\n![](https://cdn.steemitimages.com/DQmNhyq94Xq2HMe9oa4JtQqui1xnG5M5mw9LQyHrbwccNFf/image.png)\n\nLight node and its verification process\nFrom the perspective of whether or not the complete blockchain data is stored, the nodes can also be divided into full nodes and light nodes, and the entire node stores the complete blockchain data, while the light nodes do not. Users can choose whether to use a full node or a light node when installing the wallet. The light node only stores those units associated with its address, it needs to download the required data from the full node, the request condition includes the list of witnesses it trusts and the address it cares about.\n\nJump list: Suppose the MCI of the ball directly on the main chain is i i . If i mod 10 = 0 imod10=0 , then the ball has a jump list ( skiplist_balls), the value in the jump list points to the previous ball; for the i i mantissa each having a 0 0 , a skip list is a value corresponding MCI; skip list is maintained equal MCI mantissa 0 0 closest to the case of the same number of I I MCI, such as I = 3000 I = At 3000 o'clock, the corresponding jump list is [ 2990 , 2900 , 2000 ] [ 2990 , 2900 , 2000 ] .\n\nJump Distance: For the MCI value in the jump list, the difference between it and the MCI value of the current ball is called the jump distance.\n\nRecent ball: The ball closest to the current time known to the current node ( last_ball), each unit must contain its most recent known ball when it is sent.\n\nThe whole node receives the witness list and the attention address sent by the light node, and searches the database of its storage unit for the unit related to the light node attention address. At the same time, for each relevant unit, the whole node constructs a chain of evidence, and the construction method is as follows:\n\n*Backtracking along the main chain, when the light node has been collected for the majority of the witnesses in the given witness list ( this is the process of finding a witness ), the units on these main chains are recorded, recorded as a unit set C C ;\n*Selecting the unit with the earliest time in the unit set C C (which is also the smallest unit of MCI), and obtaining it last_ball;\n*From last_ballthis unit, backtracking along the main chain until the inclusion of the contained skiplist_ballsball stops, recording the balls on these main chains, recorded as the ball set B B ;\n*Use skiplist_ballsto continue backtracking along the main chain and jump to skiplist_ballsthe ball with the largest jump distance ( this is the process of continuously accelerating the jump );\n*Repeat step 4 to reduce the jump distance when the next jump exceeds the target unit ( this is the process of slowing down the jump. In the extreme case, no skiplist_ballsbacktracking is used , only the parent unit is used for backtracking ) until the target unit stops.\nFor light nodes, the chain of evidence given by the whole node is credible for two main reasons:\n\n*The units at the beginning of the chain of evidence contain units issued by witnesses trusted by the light node;\n*The connections in the chain of evidence use parent_units(find the witness process), last_ball, skiplist_balls, , parent_balls.\nTherefore, through the chain of evidence, the light node can determine whether a unit is valid.\n\nEnd-to-end encrypted channel\nThe hub node Hub is used to provide a reliable end-to-end encrypted data channel between different user devices, somewhat similar to a mail server. The Hub provides a store-and-forward service for user devices, and user devices can choose to connect to different Hubs. The user device connects to the Hub using websocket and uses TLS encryption. Once the Hub receives a message addressed to a device address, it will forward it immediately, and delete the message after successful forwarding.\n\nThe device address is used to identify the user device, and thus receives messages sent by other devices, similar to the email address. The device address is different from the wallet address and can use the same wallet address on different devices. Each device saves a permanent private key, and its corresponding public key is hashed and BASE32 encoded to obtain the device address. To distinguish it from the wallet address, the device address adds 0 as the identifier at its beginning (0 itself is not a BASE32 character). The full device address also includes the name of the hub, for example ([email protected]). When switching to a different Hub, @the address between them remains the same.\n\nAssume that the device that sent the message is recorded as the device senderreceiving the message receiver, and receiverthe connected Hub is hub. Then, when senderyou want receiverto communicate with it, it needs to do the following:\n\n*(sender)Modify its Hub address to (hub)be all connected by default wss://byteball.org/bb;\n*(sender)The (receiver)paired, two-dimensional code scan may be used, matching string, or use (byteball://)starting link.\nEnd-to-end encryption (ECDH+AES) and digital signature (ECDSA) are used for communication between all devices. As the only intermediary in the communication, the Hub cannot view or modify the message content. To improve the security of forwarding, the device generates a temporary private key and uploads the corresponding public key to the Hub connected to it. At the same time, the device can periodically change the temporary private key and public key.\n\nTherefore, (sender)when (receiver)sending a message, it needs to complete the following steps:\n\n*And (hub) connection;\n*Temporary public key (hub) obtained from (receiver);\n*Generate a one-time key pair;\n*(receiver) Generating an ECDH key based on the one-time private key and the temporary public key;\n*AES encryption of messages using ECDH keys;\n*Add a one-time public key;\n*Sign the entire message with the device private key;\n*Send a message to (hub);\nFor example (receiver), it first needs to verify the signature of the message, and then use senderthe one-time public key and the local temporary private key to decrypt the message to obtain the content of the message.\n\nThe Hub-based device end-to-end encrypted message channel can be used for communication between devices, and messages sent between devices are not stored in the Byteball database. Users can use this channel to send encrypted text messages, multi-signature transactions, privacy assets (such as blackbytes), and more.",
      "title": "ByteBall principle analysis--network structure",
      "author": "cvb",
      "permlink": "byteball-principle-analysis-4-network-structure",
      "json_metadata": "{\"tags\":[\"byteball\",\"cryptocurrency\",\"crypto\",\"blockchain\",\"cn\"],\"users\":[\"the\"],\"image\":[\"https://cdn.steemitimages.com/DQmNhyq94Xq2HMe9oa4JtQqui1xnG5M5mw9LQyHrbwccNFf/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "byteball"
    }
  ],
  "block": 24336380,
  "trx_id": "28dc74c98f54deb6613f77abb3535893efe2d1b5",
  "op_in_trx": 0,
  "timestamp": "2018-07-20T08:32:33",
  "virtual_op": false,
  "trx_in_block": 13
}

{
  "op": [
    "vote",
    {
      "voter": "cvb",
      "author": "punqtured",
      "weight": 10000,
      "permlink": "official-byteball-airdrop-to-steemians"
    }
  ],
  "block": 24336219,
  "trx_id": "ae0535b2c74fbdfa1e5e669faadcd6253a9ad40e",
  "op_in_trx": 0,
  "timestamp": "2018-07-20T08:24:30",
  "virtual_op": false,
  "trx_in_block": 27
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cicbar",
      "author": "cvb",
      "weight": 253255,
      "rshares": 531113916602,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "4.995 HBD",
      "total_vote_weight": 1570098
    }
  ],
  "block": 24318286,
  "trx_id": "ff2bb073171294f1ce054895cd4d6d41ba260c93",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T17:27:36",
  "virtual_op": true,
  "trx_in_block": 27
}

{
  "op": [
    "vote",
    {
      "voter": "cicbar",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24318286,
  "trx_id": "ff2bb073171294f1ce054895cd4d6d41ba260c93",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T17:27:36",
  "virtual_op": false,
  "trx_in_block": 27
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "eltairovy",
      "author": "cvb",
      "weight": 290,
      "rshares": 608759204,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "3.807 HBD",
      "total_vote_weight": 1316843
    }
  ],
  "block": 24313092,
  "trx_id": "e7c2fb2366c033ac0d4c41a8e85c21d4b25b32f2",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T13:07:42",
  "virtual_op": true,
  "trx_in_block": 34
}

{
  "op": [
    "vote",
    {
      "voter": "eltairovy",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24313092,
  "trx_id": "e7c2fb2366c033ac0d4c41a8e85c21d4b25b32f2",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T13:07:42",
  "virtual_op": false,
  "trx_in_block": 34
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "steemitboard",
      "author": "cvb",
      "weight": 206,
      "rshares": 432112890,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "3.806 HBD",
      "total_vote_weight": 1316553
    }
  ],
  "block": 24312725,
  "trx_id": "596ae67a1abf16632602d0a8a1f12e77de777c6f",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T12:49:21",
  "virtual_op": true,
  "trx_in_block": 8
}

{
  "op": [
    "vote",
    {
      "voter": "steemitboard",
      "author": "cvb",
      "weight": 100,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24312725,
  "trx_id": "596ae67a1abf16632602d0a8a1f12e77de777c6f",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T12:49:21",
  "virtual_op": false,
  "trx_in_block": 8
}

{
  "op": [
    "comment",
    {
      "body": "Congratulations @cvb! You have completed the following achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@cvb) You published your First Post\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstvote.png)](http://steemitboard.com/@cvb) You made your First Vote\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@cvb) You got a First Vote\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@cvb) Award for the number of upvotes received\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\nTo support your work, I also upvoted your post!\n\n\n**Do not miss the last post from @steemitboard:**\n[SteemitBoard World Cup Contest - The results, the winners and the prizes](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-the-results-and-prizes)\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-cvb-20180719t124917000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24312724,
  "trx_id": "68814ee1796adc5da70ad25d2ba8bc547a807e29",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T12:49:18",
  "virtual_op": false,
  "trx_in_block": 46
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "fabien",
      "author": "cvb",
      "weight": 1113813,
      "rshares": 1623601116633,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "3.659 HBD",
      "total_vote_weight": 1316347
    }
  ],
  "block": 24309006,
  "trx_id": "be32175f2ac1939bdc7e81e6a5b0a2d5dbd46122",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T09:43:18",
  "virtual_op": true,
  "trx_in_block": 76
}

{
  "op": [
    "vote",
    {
      "voter": "fabien",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24309006,
  "trx_id": "be32175f2ac1939bdc7e81e6a5b0a2d5dbd46122",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T09:43:18",
  "virtual_op": false,
  "trx_in_block": 76
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cryptkeeper",
      "author": "cvb",
      "weight": 52882,
      "rshares": 15416522380,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "0.080 HBD",
      "total_vote_weight": 202534
    }
  ],
  "block": 24308247,
  "trx_id": "f8b6167d3f794a5fba734046a84d61423f4f17cf",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T09:05:12",
  "virtual_op": true,
  "trx_in_block": 31
}

{
  "op": [
    "vote",
    {
      "voter": "cryptkeeper",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24308247,
  "trx_id": "f8b6167d3f794a5fba734046a84d61423f4f17cf",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T09:05:12",
  "virtual_op": false,
  "trx_in_block": 31
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "sensation",
      "author": "cvb",
      "weight": 963,
      "rshares": 252306781,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "0.047 HBD",
      "total_vote_weight": 149652
    }
  ],
  "block": 24307984,
  "trx_id": "36147a986558438fed43f9d0e7cce45acc30418f",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T08:52:03",
  "virtual_op": true,
  "trx_in_block": 39
}

{
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24307984,
  "trx_id": "36147a986558438fed43f9d0e7cce45acc30418f",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:52:03",
  "virtual_op": false,
  "trx_in_block": 39
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "moby-dick",
      "author": "cvb",
      "weight": 198,
      "rshares": 52058146,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "0.046 HBD",
      "total_vote_weight": 148689
    }
  ],
  "block": 24307808,
  "trx_id": "102ee9212f07d2a0da77243073767e7ff32b141e",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T08:43:12",
  "virtual_op": true,
  "trx_in_block": 2
}

{
  "op": [
    "vote",
    {
      "voter": "moby-dick",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24307808,
  "trx_id": "102ee9212f07d2a0da77243073767e7ff32b141e",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:43:12",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "comment",
    {
      "body": "This seems quite complex stuff. Glad that the wallet works super easy.",
      "title": "",
      "author": "wekkel",
      "permlink": "re-cvb-byteball-principle-analysis-4-network-structure-20180719t083910137z",
      "json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "cvb",
      "parent_permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24307728,
  "trx_id": "66ffa2ae754feb3b7e3d64acff499c56b63216e3",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:39:12",
  "virtual_op": false,
  "trx_in_block": 50
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "wekkel",
      "author": "cvb",
      "weight": 111404,
      "rshares": 20389357800,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "0.046 HBD",
      "total_vote_weight": 148491
    }
  ],
  "block": 24307716,
  "trx_id": "8417e24122b99e8dba21e015483054e978a205ba",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T08:38:36",
  "virtual_op": true,
  "trx_in_block": 2
}

{
  "op": [
    "vote",
    {
      "voter": "wekkel",
      "author": "cvb",
      "weight": 9500,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24307716,
  "trx_id": "8417e24122b99e8dba21e015483054e978a205ba",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:38:36",
  "virtual_op": false,
  "trx_in_block": 2
}

{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsonkomirchev",
      "author": "cvb",
      "weight": 1489,
      "rshares": 97558621,
      "permlink": "byteball-principle-analysis-4-network-structure",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 37087
    }
  ],
  "block": 24307555,
  "trx_id": "e2ea045b8438702f63819edb4a389eac056569da",
  "op_in_trx": 1,
  "timestamp": "2018-07-19T08:30:33",
  "virtual_op": true,
  "trx_in_block": 63
}

{
  "op": [
    "vote",
    {
      "voter": "tsonkomirchev",
      "author": "cvb",
      "weight": 10000,
      "permlink": "byteball-principle-analysis-4-network-structure"
    }
  ],
  "block": 24307555,
  "trx_id": "e2ea045b8438702f63819edb4a389eac056569da",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:30:33",
  "virtual_op": false,
  "trx_in_block": 63
}

{
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"cvb\",\"following\":\"punqtured\",\"what\":[\"blog\"]}]",
      "required_auths": [],
      "required_posting_auths": [
        "cvb"
      ]
    }
  ],
  "block": 24307397,
  "trx_id": "967a9d38565fd1f779e803cc66d8142affaddbb7",
  "op_in_trx": 0,
  "timestamp": "2018-07-19T08:22:36",
  "virtual_op": false,
  "trx_in_block": 7
}