-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: "factom-cli transactions" shows incorrect MilliTimestamp #723
Comments
Moved to a standard format. |
It's still doing this. I just made a transaction at 1:46 PM CST and got: ~$ factom-cli transactions transaction01: Fee Due: 0.013332 Currently will pay: 1.0 Transaction (size 143): EntryCredit Outputs: 0000
RCD 1: 01 718b5edd2914acc2e4677f336c1a32736e5e9bde13663e6413894f57ec272e28 It should be 6:46pm (UTC) |
The time stamp is showing an extraneous "+0000" on the end. Do you want that? transaction01: Fee Due: 0.006666 Currently will pay: 0.0 WARNING: Currently your transaction fee may be too low Transaction (size 10): Inputs: 0000Outputs: 0000EntryCredit Outputs: 0000 |
The +0000 is a standard UTC timestamp indicator. The alternative is (UTC) On Fri, Sep 25, 2015 at 6:35 PM, drobertbaker notifications@github.com
|
OK |
Transaction occurred at 5:55 p.m. Central time.
The time shown was:
MilliTimestamp: 0000014f956bc2b3 Sep 3, 2015 at 10:55am (UTC)
The time shown SHOULD be 10:55PM (UTC)
The text was updated successfully, but these errors were encountered: