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

post parser #11

Open
3 of 4 tasks
sponnet opened this issue Aug 24, 2018 · 2 comments
Open
3 of 4 tasks

post parser #11

sponnet opened this issue Aug 24, 2018 · 2 comments

Comments

@sponnet
Copy link
Owner

sponnet commented Aug 24, 2018

  • create basic parser
  • create JSON schema for validating input
  • add transaction data to JSON payload ( from address + TXhash )
  • save peep in local cache for easy lookup ( key = timestamp + txhash )
@sponnet
Copy link
Owner Author

sponnet commented Aug 28, 2018

I suggest to save the peep in a metadata again on IPFS in a format as follows:

{
          event: event,
          transaction: transaction,
          function: decodedData,
          ipfsHash: <hash>,
          ipfsData: <data of above hash>,
}

And save it as such in the levelDB - so we have all the data available for further data slicing.

@sponnet
Copy link
Owner Author

sponnet commented Aug 28, 2018

This could also be a generic format for all events coming out of the peepeth contract btw.

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

1 participant