RE: Compromised accounts in the STEEM blockchain // A new defender @crokkon 69 over 4 years ago (Edited) You are viewing a single comment's thread: View full context View direct parent . 0 0 0.000 4 comments @marcocasario 61 over 4 years ago (Edited) @crokkon Yes, I found out that someone already had my exact idea a few days ago. Its owner though recently said on Discord that he turned it off so I’m happy to take his place 0 0 0.000 Reply @crokkon 69 over 4 years ago (Edited) . 0 0 0.000 Reply @marcocasario 61 over 4 years ago (Edited) At the moment it takes about 25ms to detect a key after being published in a block. And I poll for new blocks every 20ms. I plan on having at least 2 instances running in order to be as fast as possible. Thx =} 0 0 0.000 Reply @reazuliqbal 68 over 4 years ago Yes, I have switched off noblebot. It wasn't very useful at saving keys anymore. 0 0 0.000 Reply
@marcocasario 61 over 4 years ago (Edited) @crokkon Yes, I found out that someone already had my exact idea a few days ago. Its owner though recently said on Discord that he turned it off so I’m happy to take his place 0 0 0.000 Reply @crokkon 69 over 4 years ago (Edited) . 0 0 0.000 Reply @marcocasario 61 over 4 years ago (Edited) At the moment it takes about 25ms to detect a key after being published in a block. And I poll for new blocks every 20ms. I plan on having at least 2 instances running in order to be as fast as possible. Thx =} 0 0 0.000 Reply @reazuliqbal 68 over 4 years ago Yes, I have switched off noblebot. It wasn't very useful at saving keys anymore. 0 0 0.000 Reply
@crokkon 69 over 4 years ago (Edited) . 0 0 0.000 Reply @marcocasario 61 over 4 years ago (Edited) At the moment it takes about 25ms to detect a key after being published in a block. And I poll for new blocks every 20ms. I plan on having at least 2 instances running in order to be as fast as possible. Thx =} 0 0 0.000 Reply
@marcocasario 61 over 4 years ago (Edited) At the moment it takes about 25ms to detect a key after being published in a block. And I poll for new blocks every 20ms. I plan on having at least 2 instances running in order to be as fast as possible. Thx =} 0 0 0.000 Reply
@reazuliqbal 68 over 4 years ago Yes, I have switched off noblebot. It wasn't very useful at saving keys anymore. 0 0 0.000 Reply
@crokkon Yes, I found out that someone already had my exact idea a few days ago.
Its owner though recently said on Discord that he turned it off so I’m happy to take his place
.
At the moment it takes about 25ms to detect a key after being published in a block. And I poll for new blocks every 20ms.
I plan on having at least 2 instances running in order to be as fast as possible.
Thx =}
Yes, I have switched off noblebot. It wasn't very useful at saving keys anymore.