Stefaan Ponnet

I suggest to save the peep in a metadata again on IPFS in a format as follows: ``` { event: event, transaction: transaction, function: decodedData, ipfsHash: , ipfsData: , }...

Example reply payload: ``` { "type": "peep", "content": "Yes. Yesssss. ", "pic": "", "untrustedAddress": "0x94b26d7a0145635ed3dad4b786f47b6be4f3945a", "untrustedTimestamp": 1521521622, "shareID": null, "parentID": "Qmf4TMhyrqhRH8YtwdnzvrPU28pYVGtDTiix6zVzh8kKY2" } ``` These payload are saved to IPFS and...

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

It's currently not very clear to me what the difference is between having a `parentID` and a `shareID` - they seem to be similar from a parser/indexer point of view....

sample ``` { "batchSaveJSON": [ { "peep": { "ipfs": "QmaZvkhSyb9DBwWjKPwMAACyQRAAGVUm2mPc8sPb1B4v5Y", "untrustedTimestamp": 1521247003 } } ], "untrustedTimestamp": 1521247022 } ```

Someone probably guessed the password of the wallet & removed the funds out of it.. Very useless action, but yeah. Since I don't find anyone willing to fund the wallet...

+1

+1

What did you switch to instead ?

Also seems to fail on safari browsers ( tested on v 8.0.8 )