You are viewing a single comment's thread from:

RE: Bitfinex, Blockchain Hacks, and Replay Attacks Oh My - All Things that Steem’s Technology is designed to prevent.

in #steem8 years ago (edited)

//Update: I was wrong. It's working fine. For details please check https://github.com/steemit/steem/issues/244 .

--- Original Post ---
I noticed that with current client implementation the ref_block_num in transactions are usually far away from where it should be "recent", so usually little effect to prevent from replay attacks. for example

 get_block 3815965
...
"transactions": [
{"ref_block_num": 14875,...},
{"ref_block_num": 14876,...},
{"ref_block_num": 14875,...},
{"ref_block_num": 14693,...},
{"ref_block_num": 14864,...},
{"ref_block_num": 14874,...},
{"ref_block_num": 14874,...},
{"ref_block_num": 14876,...},
{"ref_block_num": 14875,...},
{"ref_block_num": 14874,...},
{"ref_block_num": 14472,...},
{"ref_block_num": 14876,...},
{"ref_block_num": 14876,...}
...

Will fire an issue to github.