# Grin uses the Nostr protocol to transport slatepack, which I believe is the future of grin

**URL:** <https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706>\
**Category:** Research\
**Created:** [August 25, 2023, 11:12pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706 "2023-08-25T23:12:04Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luneth](https://avatars.discourse-cdn.com/v4/letter/l/e19b73/32.png) [@Luneth](https://forum.grin.mw/u/Luneth)\
**Post date:** [August 25, 2023, 11:12pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/1 "2023-08-25T23:12:04Z")

</div>

Grin uses the Nostr protocol to transport slatepack, which I believe is the future of grin.

---

<div class="post-metadata">

**Author:** ![i2pZ7812HTZV69](https://avatars.discourse-cdn.com/v4/letter/i/839c29/32.png) [@i2pZ7812HTZV69](https://forum.grin.mw/u/i2pZ7812HTZV69)\
**Post date:** [October 2, 2023, 6:35pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/2 "2023-10-02T18:35:16Z")

</div>

Could be a good idea.  
Also don’t forget SimpleX Chat app too.

---

<div class="post-metadata">

**Author:** ![ardocrat](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/ardocrat/32/5164_2.png) [@ardocrat](https://forum.grin.mw/u/ardocrat)\
**Post date:** [October 4, 2023, 10:08pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/3 "2023-10-04T22:08:59Z")

</div>

For async version of interactive transactions possible, but we still need to use TOR, what can come to leak of privacy if 3-letter agencies will control major part of exit nodes or even will make TOR network unusable somehow… My dream is to replace TOR here by some Mixnet.

---

<div class="post-metadata">

**Author:** ![i2pZ7812HTZV69](https://avatars.discourse-cdn.com/v4/letter/i/839c29/32.png) [@i2pZ7812HTZV69](https://forum.grin.mw/u/i2pZ7812HTZV69)\
**Post date:** [October 4, 2023, 11:35pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/4 "2023-10-04T23:35:13Z")

</div>

@ardocrat how about i2p written in rust

---

<div class="post-metadata">

**Author:** ![ardocrat](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/ardocrat/32/5164_2.png) [@ardocrat](https://forum.grin.mw/u/ardocrat)\
**Post date:** [October 5, 2023, 12:01am UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/5 "2023-10-05T00:01:42Z")

</div>

Yes, I am researching if this crate can be useful to integrate [GitHub - cyphernet-dao/rust-cyphernet: Cyphernet is a set of libraries for privacy-preserving networking apps](https://github.com/cyphernet-dao/rust-cyphernet). It supports Tor, I2P, Nym and something else 🙂.

---

<div class="post-metadata">

**Author:** ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)\
**Post date:** [October 5, 2023, 8:49am UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/6 "2023-10-05T08:49:38Z")

</div>

> [@ardocrat](#):
>
> what can come to leak of privacy if 3-letter agencies will control major part of exit nodes or even will make TOR network unusable somehow… My dream is to replace TOR here by some Mixnet.

Is this not simple exchange one attack vector for another? I mean who says 3-letter agencies cannot control the majority of the Mixnet? Anything they see coming in in the first Mix node before aggregating can be de-aggregated. In any case, the more methods users use for interacting and optionally aggregating, the harder it will be to disentangle the transaction graph.

---

<div class="post-metadata">

**Author:** ![tromp](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/tromp/32/22_2.png) [@tromp](https://forum.grin.mw/u/tromp)\
**Post date:** [October 5, 2023, 11:00am UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/7 "2023-10-05T11:00:44Z")

</div>

> [@Anynomous](#):
>
> Anything they see coming in in the first Mix node before aggregating can be de-aggregated.

Wrong. The first Mix node itself cannot deaggregate (unless it’s a single node mixnet).

Even if n-1 mixnodes in an n node mixnet collude, they cannot deaggregate.

---

<div class="post-metadata">

**Author:** ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)\
**Post date:** [October 5, 2023, 1:48pm UTC](https://forum.grin.mw/t/grin-uses-the-nostr-protocol-to-transport-slatepack-which-i-believe-is-the-future-of-grin/10706/8 "2023-10-05T13:48:24Z")

</div>

> [@tromp](#):
>
> Wrong. The first Mix node itself cannot deaggregate (unless it’s a single node mixnet).

I guess it works less simplistic than I though. But it is good to know that it does not have any weakness. Or are there know attack vectors other than DDoS attacks that you can think of?
