create account

RE: Quick update on Hive-related activities at BlockTrades by vikisecrets

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @blocktrades/quick-update-on-hive-related-activities-at-blocktrades

· @vikisecrets ·
Great, please also audit the code for replay attacks between hive and steem.
properties (22)
authorvikisecrets
permlinkq85kp3
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2020-04-02 08:53:27
last_update2020-04-02 08:53:27
depth1
children1
last_payout2020-04-09 08:53:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length76
author_reputation1,183,592,428,206,519
root_title"Quick update on Hive-related activities at BlockTrades"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id96,677,660
net_rshares0
@blocktrades ·
$0.03
Replay attacks aren't possible, that's one thing we know already (because use of TAPOS, transactions-as-proof-of-stake). When you sign a transaction, your transaction includes a reference to a recent block in the blockchain you are signing for. So when you publish a transaction for hive, it will have a link to a hive block, so a steem node will determine that the transaction is invalid. And vice-versa.
👍  
properties (23)
authorblocktrades
permlinkq86skl
categoryhive
json_metadata{"app":"hiveblog/0.1"}
created2020-04-03 00:41:09
last_update2020-04-03 00:41:09
depth2
children0
last_payout2020-04-10 00:41:09
cashout_time1969-12-31 23:59:59
total_payout_value0.015 HBD
curator_payout_value0.015 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length405
author_reputation1,278,355,776,041,298
root_title"Quick update on Hive-related activities at BlockTrades"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id96,686,274
net_rshares149,271,448,218
author_curate_reward""
vote details (1)