Investigate why txnNumber in encrypted commands is an int32

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.12.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None

      The txnNumber should be an int64, and is int64 before we encrypt. Does not cause any visible issues and we convert it back to int64, but this odd behavior that we should investigate.

            Assignee:
            Emily Giurleo (Inactive)
            Reporter:
            Emily Giurleo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: