What is the output of the following commands?:

Code: [Select]

blockchain_get_block 601
blockchain_get_block 613
blockchain_get_block 756


(wallet closed) >>> blockchain_get_block 601
{
  "previous": "5afb6fd74d3bfd8268537e2dac0aea58ea44b387",
  "block_num": 601,
  "timestamp": "2015-05-18T06:14:30",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4a
d6164f0f0",
  "next_secret_hash": "e8fb9325d5ac58a65cc5ee0abe92236117ce08e0",
  "previous_secret": "bf5ce1cb5366e47b61ccab6cc4e28cad2d5a3b65",
  "delegate_signature": "1f1c291cca114fa8296368975a39efd627bc593fd26a97bc2ab5076
642789bcc010ed5eb68688a5c0b55e734879ef23bbab9d9e0d160026303c5d43b682545b6df",
  "user_transaction_ids": [
    "fbc3e30c1ed74cbda1956c6ea2647645e8d18c61"
  ],
  "id": "614faad84074a19c5105efcc271e7203a6ff5560",
  "block_size": 311,
  "latency": 0,
  "signee_shares_issued": 0,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 0,
  "random_seed": "0000000000000000000000000000000000000000",
  "processing_time": 0
}

(wallet closed) >>> blockchain_get_block 613
{
  "previous": "9c53938dea4ed219efd36df20423f16bcdb976e5",
  "block_num": 613,
  "timestamp": "2015-05-18T06:16:40",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4a
d6164f0f0",
  "next_secret_hash": "8fe2b5620c6081690bc1d1e04cf378184ca30db2",
  "previous_secret": "bde6608e3204a905f4ee2dec76711caa009483d7",
  "delegate_signature": "1f6eef98d60a1e710105637f035a6199b2306f7076c1ad319ca2638
379f5653757329bdf5a27c1320346a5719c403025f0499760989be072a8d28e625cfc61dbe3",
  "user_transaction_ids": [
    "fbc3e30c1ed74cbda1956c6ea2647645e8d18c61"
  ],
  "id": "0a4a953235e3e49d4255f040f43ed9c698a5f9bc",
  "block_size": 311,
  "latency": 0,
  "signee_shares_issued": 0,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 0,
  "random_seed": "0000000000000000000000000000000000000000",
  "processing_time": 0
}

(wallet closed) >>> blockchain_get_block 756
{
  "previous": "b20fdd3a3b4e95f4e515d0d152d8832614b2d330",
  "block_num": 756,
  "timestamp": "2015-05-18T06:43:10",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4a
d6164f0f0",
  "next_secret_hash": "5b756145e536d6c17a5e4e47974c8dc6544c03ff",
  "previous_secret": "6a654bbb1e11c18b96870e5738d019076937ca77",
  "delegate_signature": "2007e6541e3ba1b494c0935f19238be9fb6416ebdc4781de498dcad
529cfaa83d7222221613a7313a2664f7d4ad6bd07e340db46d586895290d09c06e2efe09515",
  "user_transaction_ids": [
    "fbc3e30c1ed74cbda1956c6ea2647645e8d18c61"
  ],
  "id": "85068bb246d03b3df3eb5f7a6c52c6ac5fd7228a",
  "block_size": 311,
  "latency": 0,
  "signee_shares_issued": 0,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 0,
  "random_seed": "0000000000000000000000000000000000000000",
  "processing_time": 0
}

Which version did you use to build that test network? The develop branch, or master or something completely different?

I use the source code Apr.3,2015

     I build 10 node to test the bitshares sourcecode.But I met a problem yestarday.
     I found the block chain have some Duplicate transaction .
     I Confused that why the NO.601 block have the TRX with "block_num": 756,
 
Did anyone met before？Or who knows the reason？

For example：
blockchain_get_block_transactions 601
[[
    "fbc3e30c1ed74cbda1956c6ea2647645e8d18c61",{
      "trx": {
        "expiration": "2015-05-18T07:14:20",
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "TTSPznLYup2rKYNRDQiTuRd58auWn9WojRth",
              "amount": 10050000,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 10000000,
              "condition": {
                "asset_id": 0,
                "slate_id": 0,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "TTSDyxeokoeGhKg39HEMpsBn6r2Hw7iURZ9k"
                }
              }
            }
          }
        ],
        "signatures": [
          "2017ba81858acf26d315b7fe0b2be0e2837fa0991db429961a3e46fa789d3c6a903fbb3f8d13452fc89855f1aeb379cce8e043df825a51a819db7a32c6756ad122"
        ]
      },
      "signed_keys": [],
      "deposits": [[
          0,
          10000000
        ]
      ],
      "withdraws": [[
          0,
          10050000
        ]
      ],
      "yield": [],
      "deltas": [[
          0,[[
              0,
              -10050000
            ]
          ]
        ],[
          1,[[
              0,
              10000000
            ]
          ]
        ]
      ],
      "required_fees": {
        "amount": 0,
        "asset_id": 0
      },
      "alt_fees_paid": {
        "amount": 0,
        "asset_id": 0
      },
      "balance": [[
          0,
          50000
        ]
      ],
      "delegate_vote_deltas": [],
      "chain_location": {
        "block_num": 756,
        "trx_num": 0
      }
    }
  ]
]

blockchain_get_block_transactions 613
[[
    "fbc3e30c1ed74cbda1956c6ea2647645e8d18c61",{
      "trx": {
        "expiration": "2015-05-18T07:14:20",
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "TTSPznLYup2rKYNRDQiTuRd58auWn9WojRth",
              "amount": 10050000,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 10000000,
              "condition": {
                "asset_id": 0,
                "slate_id": 0,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "TTSDyxeokoeGhKg39HEMpsBn6r2Hw7iURZ9k"
                }
              }
            }
          }
        ],
        "signatures": [
          "2017ba81858acf26d315b7fe0b2be0e2837fa0991db429961a3e46fa789d3c6a903fbb3f8d13452fc89855f1aeb379cce8e043df825a51a819db7a32c6756ad122"
        ]
      },
      "signed_keys": [],
      "deposits": [[
          0,
          10000000
        ]
      ],
      "withdraws": [[
          0,
          10050000
        ]
      ],
      "yield": [],
      "deltas": [[
          0,[[
              0,
              -10050000
            ]
          ]
        ],[
          1,[[
              0,
              10000000
            ]
          ]
        ]
      ],
      "required_fees": {
        "amount": 0,
        "asset_id": 0
      },
      "alt_fees_paid": {
        "amount": 0,
        "asset_id": 0
      },
      "balance": [[
          0,
          50000
        ]
      ],
      "delegate_vote_deltas": [],
      "chain_location": {
        "block_num": 756,
        "trx_num": 0
      }
    }
  ]
]

Quote from: xiaorui.dong on May 13, 2015, 06:49:44 am

     FC_ASSERT( fc::ripemd160::hash( header.previous_secret ) == *prev_secret_hash );
   Why the header.previous_secret should Equal the prev_secret_hash?

Actually it states that the HASH of the secret published in the previous block should equal the "previous secret hash".
This is for the random number generation in BitShares .. The delegates publish a HASH(secret) and reveal
the secret in the block they sign next. Thus you get verifiable secret hashes on the blockchain from the delegates

Quote

   And what situation can cause the exception of FC_ASSERT( fc::ripemd160::hash( header.previous_secret ) == *prev_secret_hash )?

Where do you see this exception? On a delegate machine or a client? In what context?

On a delegate machine

Quote from: xiaorui.dong on May 13, 2015, 05:50:16 am

Quote from: BTSdac on May 13, 2015, 02:48:23 am

Quote from: xiaorui.dong on May 12, 2015, 06:53:51 am

   求助，我在本地搭建代理节点想测试代理出块的流程。可是总有几个代理不出块，查看代码
   在void wallet::sign_block( signed_block_header& header )函数里面的如下断言出出错。
   FC_ASSERT( fc::ripemd160::hash( header.previous_secret ) == *prev_secret_hash );

   求大神能告诉下，哪些情况会导致这两个hash不相等呢，从而导致校验不过呢？
   PS：最好能解释下这里的header.previous_secret和prev_secret_hash的含义和作用。原谅小白对这个签块模块机制不太明白。可以解释下最好

previous_secret :每个代理出块时候都需要发布一个随机种子, 每轮用所有101个随机种子组合成随机数, 来洗牌下轮代表顺序. 但为了防止代表知道其他人的随机数后,自己生成一个对自己有利的随机种子,所以代表都先提前一轮公布随机种子的HASH, 这样就算知道其他代表的随机种子后,也不能更改自己的随机种子.
所以这个随机种子也叫秘密随机种子.

prev_secret_hash: 秘密随机种子的HASH ,

那什么样的情况下会导致我发布的这个prev_secret_hash 跟head里面存的header.previous_secret算出来的hash不一样呢？

[/quote]
程序不诚实 ? 
[/quote]
就是不清楚什么情况下会导致这两者不一致~~~
不太理解这个校验的意义~~

求大神解决

   求助，我在本地搭建代理节点想测试代理出块的流程。可是总有几个代理不出块，查看代码
   在void wallet::sign_block( signed_block_header& header )函数里面的如下断言出出错。
   FC_ASSERT( fc::ripemd160::hash( header.previous_secret ) == *prev_secret_hash );

   求大神能告诉下，哪些情况会导致这两个hash不相等呢，从而导致校验不过呢？
   PS：最好能解释下这里的header.previous_secret和prev_secret_hash的含义和作用。原谅小白对这个签块模块机制不太明白。可以解释下最好