Base Head

Yeah, you're right it's not an easy one to crack, there are multiple layers to ensure people (including @Meanwhile_cash itself) are not gaming it. I'm still polishing the solution, so some things will change in the whitepaper, but here's how it might look: Let's start with the assumption that campaigns are distributed correctly, that we have a solid risk engine, and that each impression is printed correctly. In the future, that risk engine will be made open source, and its signature will be known. Each impression will be signed by our worker via this engine, removing that assumption, but we could even push it further and run with AVS (e.g., @LayerOnEth) for total verifiability. The next question, how do we store each campaign and make sure that anyone (including agents) can have an audit trail that? Every certain amount of time (epoch) or per campaign (still need to think about it) we will post a digest of the leaves and update the root of a Merkle tree that lives on @solana. We will also add the revenue gross revenue in the same call to help us buyback $CASHBACK automatically (2 bird with 1 stone). Having the digest only is not enough, Each leaf is one accepted impression (campaign, user, install, amount, time AND risk engine signature) and the whole tree needs to be stored somewhere to be reconstructed. Currently exploring @FlareNetworks or @ArweaveEco (in terms of immutability guarantees but cost will play a big part in the decision, still need to look into it). Also worth nothing that this cost is predictable as each campaign has a known amount of impressions (which give more room to integrate $CASHBACK)! The "proofs" and everything needed to reconstruct the Merkle tree should be made easy for non technical users on a transparency page. The end goal is to have the whole loop verifiable by human agent alike! Ps: a questions you might have is: "But we have to trust you to input the right amount as some payments will be made in fiat via @stripe. I believe that all payments will be made on chain but in the Meanwhile we could a) Run the payment in a AVS b) Tust the 70/30 rate, which is a far smaller, auditable assumption (because payouts are a 100% on chain we can re construct the initial amount paid by the advertisers) Here's a paper I wrote back in the days where I had to solve a similar issue (in terms of the layering): reconciling a private ledger with a public chain to benefit from it's immutability, transparency, and verifiability while maintaining investors privacy using a Merkle tree app.pdf.net/edit/Q6LF62hlafE… Working on multiple things at the same time and will explain / polish everything in an upcoming whitepaper so hopefully this make sense!