Author Topic: What is the average block size of Graphene practically?  (Read 2053 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

Here is what an empty block looks like.
Code: [Select]
{
  "previous": "00000ea55488ce365e62fb550da3b456dce9fe1a",
  "timestamp": "2015-07-09T21:14:15",
  "witness": "1.6.8",
  "next_secret_hash": "de22e2fbc90e45f20c7c6613fffa683e7e6189f2e3235006658d90d7",
  "previous_secret": "2e47ec8824c831a6fb07fa1bee7e7282d26aa6cb54402b7a295703e4",
  "transaction_merkle_root": "0000000000000000000000000000000000000000",
  "extensions": [],
  "witness_signature": "205081acc613cba45c23ca6e910ca0846cb6a2b9a722062fcc800c956d9764fac33759f42bbf99b37f9beafc9493feacac34dd30af32b32f0f6f84e1c5a8501731",
  "transactions": []
}

The only way we could shrink this down would be to reduce the size of the secret hashes.. which upon reviewing the code it looks like they are larger than necessary.  I will be reducing them down to 160bit saving a total of 16 bytes in the block header.


Here is what a create account transaction looks like:
Code: [Select]
{
      "ref_block_num": 3857,
      "ref_block_prefix": 2816863367,
      "relative_expiration": 3,
      "operations": [[
          4,{
            "fee": {
              "amount": 100000,
              "asset_id": "1.3.0"
            },
            "registrar": "1.2.89459",
            "referrer": "1.2.89459",
            "referrer_percent": 0,
            "name": "covenant-2141",
            "owner": {
              "weight_threshold": 1,
              "account_auths": [],
              "key_auths": [[
                  "GPH5PzktfJkT1DEEFqdZ4ZkNdEnn4U2X3oQ6CYEtnRcguVUB5sBnQ",
                  1
                ]
              ],
              "address_auths": []
            },
            "active": {
              "weight_threshold": 1,
              "account_auths": [],
              "key_auths": [[
                  "GPH6svYxFqh2EhCohFfesWp8DM6W4XfXSZ11rTbcwJS3ZV5dcrRkt",
                  1
                ]
              ],
              "address_auths": []
            },
            "options": {
              "memo_key": "GPH51CFFgo99kG5bC8LiY3DhB2r1fNsmiL9CyWiXsZQLXqyjhRUUj",
              "voting_account": "1.2.0",
              "num_witness": 0,
              "num_committee": 0,
              "votes": []
            }
          }
        ]
      ],
      "signatures": [
        "1f1b2cfff6fa5fb216e0b5c2f0554472284c5584ad4de54410fddcef308e59c13f02a70abf7bcb54e918662e479dbc08c1937baba059e599b0661fd0917fb6688d"
      ],
      "operation_results": [[
          1,
          "1.2.98842"
        ]
      ]
    }

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline bytemaster

fc::raw::pack_size(signed_block()): 168
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
I tested with flood_network command (1000 txs) and found the difference in blockchain is about 200KB. IIRC 2.0 argues for 100 byte average block size, but my result is about 200 byte. Why such difference happens?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop