last days before launching the liquidity pool I'm checking and wrapping up all technical stuff.
Today I finished runningHash.
What is it?
Well, @gmcoin works on @gelatonetwork. Each day web3function's workers run and search for "gm" tweets from registered smart-contract users. Verify them, and send the result to smart-contract, where we mint $GM.
It's all transparent. But the exact tweets that have been scanned are not exposed. Cauze on scale it can cost a lot. Yes, @base is cheap and fast, but anyway I don't like to design things that scale poorly.
So, how I solved it?
We save tweets on the AWS backend and calculate runningHash. (see img).
Then we upload to IPFS and store the final runningHash on smart-contract too
So, you can download IPFS file with the list of all processed tweet, and calculate final runningHash by yourself, and it will match the final runningHash on smart-contract.
That's how you can verify what tweets have been processed.
Full transparency, cauze we're in web3 development 🙌 0 reply
0 recast
1 reaction
0 reply
0 recast
0 reaction