Skip to content
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

Closed
drobertbaker opened this issue Sep 3, 2015 · 5 comments
Closed

API: "factom-cli transactions" shows incorrect MilliTimestamp #723

drobertbaker opened this issue Sep 3, 2015 · 5 comments
Assignees
Milestone

Comments

@drobertbaker
Copy link

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)

@drobertbaker drobertbaker changed the title API: factom-cli transactions shows incorrect MilliTimestamp API: "factom-cli transactions" shows incorrect MilliTimestamp Sep 3, 2015
@PaulSnow PaulSnow added this to the Maintenance milestone Sep 18, 2015
@PaulSnow
Copy link
Contributor

Moved to a standard format.

@drobertbaker
Copy link
Author

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):
Version: 0000000000000002
MilliTimestamp: 0000014ff66143b9 Sep 22, 2015 at 6:46am (UTC)
# Inputs: 0001
# Outputs: 0000

EntryCredit Outputs: 0000

  input:            1.0        FA2jK2HcLnRdS94dEcU27rF3meoJfpUcZPSinpb7AwQvPRY6RL1Q
              0000000005f5e100 factoid-wallet-address-name01

RCD 1: 01 718b5edd2914acc2e4677f336c1a32736e5e9bde13663e6413894f57ec272e28
Signature Block:
signature: signature: ec4ca4c4f7f6c5121e9d3bb2f53b46f7637acd9af1d1e65611283913804292e1790bc14b6b2c4844894b249f4bb39fe3114b7817cfb83fcde5f792dfaa06e102

It should be 6:46pm (UTC)

@PaulSnow PaulSnow assigned drobertbaker and unassigned PaulSnow Sep 24, 2015
@drobertbaker
Copy link
Author

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):
Version: 0000000000000002
MilliTimestamp: 0000015006c8c470 Fri, 25 Sep 2015 23:13:52 +0000

Inputs: 0000

Outputs: 0000

EntryCredit Outputs: 0000

@PaulSnow
Copy link
Contributor

PaulSnow commented Sep 26, 2015

The +0000 is a standard UTC timestamp indicator. The alternative is (UTC)
which is just as many characters. When you get into other timezones with
daylight savings time, giving the hour offset works better than saying
(CST) or (CDT)...

On Fri, Sep 25, 2015 at 6:35 PM, drobertbaker notifications@github.com
wrote:

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):
Version: 0000000000000002
MilliTimestamp: 0000015006c8c470 Fri, 25 Sep 2015 23:13:52 +0000
Inputs: 0000 Outputs: 0000 EntryCredit Outputs: 0000


Reply to this email directly or view it on GitHub
#723 (comment)
.

@drobertbaker
Copy link
Author

OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants