Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/abdelstark/askeladd
Powering Verifiable Computation for Nostr Data Vending Machines.
https://github.com/abdelstark/askeladd
bitcoin circle-stark lightning-network nip-90 nostr nostr-dvm starknet stwo zero-knowledge-proofs
Last synced: 2 months ago
JSON representation
Powering Verifiable Computation for Nostr Data Vending Machines.
- Host: GitHub
- URL: https://github.com/abdelstark/askeladd
- Owner: AbdelStark
- License: mit
- Created: 2024-07-16T10:38:25.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2024-08-07T12:19:11.000Z (5 months ago)
- Last Synced: 2024-10-05T16:32:55.630Z (3 months ago)
- Topics: bitcoin, circle-stark, lightning-network, nip-90, nostr, nostr-dvm, starknet, stwo, zero-knowledge-proofs
- Language: Rust
- Homepage: https://askeladd.org
- Size: 12.8 MB
- Stars: 14
- Watchers: 1
- Forks: 3
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Censorship-resistant global proving network.
## About
Askeladd is a censorship-resistant global proving network, for anyone to be able to generate validity proofs, using [STWO](https://github.com/starkware-libs/stwo) prover, and verify them. It enables to submit proving request to the network and retrieve the generated proof for any given request.
Askeladd leverages [Nostr](https://github.com/nostr-protocol/nostr) for the communication layer, to gossip the proving requests and generated proofs, following the [NIP-90 - Data Vending Machine](https://nips.nostr.com/90) specification.
> **Disclaimer:** Askeladd is only a proof of concept and should not be used in a production environment. It's a work in progress as a showcase of the STWO prover and the Nostr protocol.
Check out this video demonstration of Askeladd in action:
[](https://asciinema.org/a/670103)
## Architecture
```mermaid
graph LR
Customer((DVM Customer))
SP[DVM Service Provider]
Nostr[Nostr Network]
STWO_P[STWO Prover]
STWO_V[STWO Verifier]
Customer -->|1. Submit Proving Request
Kind: 5600| Nostr
Nostr -->|2. Fetch Request| SP
SP -->|3. Generate Proof| STWO_P
SP -->|4. Publish Proof
Kind: 6600| Nostr
Nostr -->|5. Fetch Proof| Customer
Customer -->|6. Verify Proof| STWO_V
classDef customer fill:#f9d71c,stroke:#333,stroke-width:2px;
classDef provider fill:#66b3ff,stroke:#333,stroke-width:2px;
classDef network fill:#333,stroke:#333,stroke-width:2px,color:#fff;
classDef prover fill:#ff9999,stroke:#333,stroke-width:2px;
classDef verifier fill:#b19cd9,stroke:#333,stroke-width:2px;
class Customer customer;
class SP provider;
class Nostr network;
class STWO_P prover;
class STWO_V verifier;
```
Typical flow:
1. User submits a proving request to the network (DVM Job Kind `5600`)
2. A DVM Service Provider picks the request and generates a proof using the STWO prover.
3. The proof is published to the Nostr network (DVM Job Result Kind `6600`).
4. The DVM Customer can verify the proof using the STWO verifier.
## Running the demo
### Using docker-compose
```bash
./scripts/demo_docker_compose_local_relayer.sh
```
### Manually
Create a `.env` file, you can use the `.env.example` file as a reference.
```bash
cp .env.example .env
# Set the relay URL in the .env file
# Using a local relay
APP_SUBSCRIBED_RELAYS=ws://localhost:8080
# Or a public relay
APP_SUBSCRIBED_RELAYS=wss://relay.nostr.net
```
(Optional, if you want to run a local nostr relay) In a terminal, run the local nostr relay:
```bash
docker run -p 8080:8080 scsibug/nostr-rs-relay
```
In a terminal, run the prover agent:
```bash
cargo run --bin dvm_service_provider
```
In a terminal, run the user CLI:
```bash
cargo run --bin dvm_customer
```
The user CLI binary will submit a proving request to the Nostr network. The prover agent will generate a proof for the request and publish it to the Nostr network. The user CLI binary will be able to verify the proof.
## Askeladd DVM Marketplace
See the [Askeladd DVM Marketplace](https://github.com/AbdelStark/askeladd-dvm-marketplace) for more information.
This requires to build the STWO WASM bindings and to copy the generated artifacts.
Go to [crates/stwo_wasm](crates/stwo_wasm) and run `wasm-pack build --target web` to build the STWO WASM bindings.
Then copy the generated `pkg` directory to [askeladd-dvm-marketplace/src/](askeladd-dvm-marketplace/src/).
## 🤝 Contributing
We love contributions! If you have ideas for improvements or find any issues, please open an issue or submit a pull request.
## 📜 License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## 🙏 Acknowledgements
This demo is powered by the amazing [STWO Prover](https://github.com/starkware-libs/stwo) from StarkWare. A big thank you to the StarkWare team and all contributors!
## 📚 Resources
- [Nostr Rust relay](https://github.com/scsibug/nostr-rs-relay/)
- [Nostr web tooling](https://nostrtool.com/)
- [NIP-90 - Data Vending Machine](https://nips.nostr.com/90)
- [Vendata.io](https://vendata.io/dvms)
- [Data Vending Machines](https://www.data-vending-machines.org/)