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

Timestamp Serialization Format #1

Closed
scisci opened this issue Jul 31, 2015 · 1 comment
Closed

Timestamp Serialization Format #1

scisci opened this issue Jul 31, 2015 · 1 comment

Comments

@scisci
Copy link

scisci commented Jul 31, 2015

Based on the ots command line program, the Stamp command returns a timestamp formatted like this:

{
    'txid':b2lx(txid),
    'nonce':b2x(nonce),
    'addr':str(addr)
}

The Complete command takes that timestamp and if the block is complete, returns a timestamp that looks like this

[
    [merkle_path...],
    [timestamp header]
]

The disparity between the two formats should be reconciled. If we want to create a function to read a timestamp, it doesn't seem good to first check if it is an array or an object, etc. Maybe the timestamp returned by the Stamp command can match the array-style and just put the txid, addr, in the header area.

@petertodd
Copy link
Member

Closing - everything's been rewritten so the question isn't relevant anymore. :)

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

No branches or pull requests

2 participants