You are viewing a single comment's thread from:

RE: SteemData Notify 代码学习二： Confirmation Worker / Code Study of SteemData Notify: Part two

in #cn • 7 years ago (edited)

The 24 character check is there for legacy reasons, and will be removed in the future. The 40 char size is the expected memo length, since 40 is the hexadecimal representation of sha1.

Bugs
Unfortunately, I don't understand Chinese, and Google Translate is not very helpful.

For all the bugs, please open the issues on Github.

7 years ago in #cn by
$4.89
  • Past Payouts $4.89, 0.00 TRX
  • - Author $4.53, 0.00 TRX
  • - Curators $0.36, 0.00 TRX
2 votes
Reply 1
Sort:  
  • Trending
    • [-]
     7 years ago 

    Hi @furion, Thank you very much for providing the SteemData Notify service.

    I had already explained the reasons for the different memo lengths in this article, Thank you again for the clarification.

    As for Bug,

        settings = db.settings.find_one({'_id': _id})
    if settings:
        db.settings.update_one(
            {'_id': _id, 'username': op['from']},
            {'$set': {'confirmed': True}}
        )

    I think it would be better to change above code to:

        settings = db.settings.find_one({'_id': _id, 'username': op['from']})
    if settings:
        db.settings.update_one(
            {'_id': _id, 'username': op['from']},
            {'$set': {'confirmed': True}}
        )

    Otherwise, It may cause minor problems in some extreme cases .
    I'll submit this issues on Github when I finished the study of your great code.

    $0.00
      Reply