Test peep!

I wonder if this is something that @peepeth is considering already in their business strategy. Monetising the contract itself (perhaps a fee for certain function execs), rather than the full stack, would be one way to actually turn this "piggybacking" into a biz advantage

This "piggybacking" could be a pretty big threat to a dapp's business model - but is also a boon for users, as they can find the blend of uncensorability, auxiliary features, and UX that works best for them.

However, this also means that competitors can build their own Filters to monitor stateless smart contracts - this lets them "piggyback" off of another project's platform, but perhaps censor content more or less frequently, or provide different auxiliary data, or a better UX.

Projects then use Filters on their back end that monitor the calls to the contract function, and store them in a centralised manner for later display. This lets the project perhaps add add their own auxiliary data to the content, or censor content.

Read up on stateless smart contracts after my convo w/ @ligi last night. Very cool stuff. As I understand it, the idea is to record info for a dapp immutably in the TX history of calls to a contract's function - rather than in a field array in the contract itself.

gotcha. i agree its the right step for now - full trustlessness is nice, but useless if no one is gonna use it. Keep up the great work!! I work in blockchain as well and peepeth has always been an inspiration for me.

Can someone explain to me the logistics of how Peepeth lets users peep for free? I understand that the crowdfund gave ETH to cover gas costs of users, but what are the actual mechanics of supplying each user with gas for a tx? wouldn't the tx still need to originate from the user

hello peepeth!