Nostr is verifiable data.

Sign code into Nostr events, and you get Verifiable Code.

But here’s the problem: you still have to trust the environment running that Verifiable Code. If you rely on a third-party machine, how can you guarantee it’s executing your code as intended and not something entirely different?

Enter Verifiable Computations. Runners take verifiable data + verifiable code, execute them, and return the results + a cryptographic proof that nothing was changed.

Now, recipients can verify if the script ran exactly as intended, making runners trustless partners.

Welcome to verifiable, trustless DVMs on Nostr.

https://video.nostr.build/699106b3c505e8a953b1508a497ea5b4c8019ea2f321e53d6ddf707a144ccd03.mp4

Reply to this note

Please Login to reply.

Discussion

Please translate this for mere mortals ! .. all over my head .. and pay grade :-)

Imagine sending your timeline algorithm to Twitter and getting the results back with a proof that Twitter run your algorithm without any changes.

Ohhhh so that's the usecase!! How does it work??

Link?

Abdel why don't you post cool nostr stuff on NOSTR 😮‍💨

At least please give us on nostr more details about how this can be done and what are computational limitations? Generating Fibonacci sequence does not sound very advanced.

You are right I should post more often

Please do!

Holy smokes !!! YES !!! … I am so into this feature … count me in as an advocate & fan … I wanna build a feature with this function 100%

how can you do it when nostr is decentralized data tho? the odds of any two dvm providers running against the same dataset is practically non existent, unless the client is the one feeding the data to both.. 🤔

DVMs can sign provable structures of which event IDs they have access to and make that available (Bloom filters, hyperloglog, etc).

Clients can even send signed Bloom filters from other DVMs as input to tell your DVM which events should be included as part of the verifiable computation process.

Having a network of third-party proofs so that not everything needs to be verified by the phone in real time will make this possible.

DVM is really a misnomer. It’s not data, it’s operating on data.

It’s compute. You give your data and it offers compute, right? Or wait, it gets the data from relays, not you.

So you plug in the data location and you ask it to run compute on that data.

I like the idea of data, code and money with which to execute said code. I imagine a population of processors mining a data stream for embedded ecash bounties. Currently humans hold the purse strings but what if the data has money in it?

Basically, it’s what Ethereum was intended to be, but without the blockchain needed.

Ethereum is dead!

Long live nostr!