# Shielded actions - Subscription to a dVPN node on Sentinel

**URL:** <https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285>\
**Category:** Data Protection\
**Tags:** ibc, interoperability\
**Created:** [5 October 2023 16:17 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285 "2023-10-05T16:17:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/daniel/32/186_2.png) [@Daniel](https://forum.namada.net/u/Daniel)\
**Post date:** [5 October 2023 16:17 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285/1 "2023-10-05T16:17:45Z")

</div>

**Action to shield** : an on-chain subscription to a dVPN node on Sentinel.

**What’s the asset’s chain?** Sentinel blockchain. It’s based on Cosmos SDK.  
**Is it IBC enabled or has it a bridge?** It’s IBC enabled.

**Flow of the assets** :

I see three viable options to perform this action since there’s decent liquidity on both OSMO/DVPN and ATOM/DVPN pairs on Osmosis DEX.

1. by retrofitting privacy to ATOM from a Cosmos address and seeding with ATOM a new Cosmos address.

- Cosmos address ( **origin** ) → sends ATOM via IBC to → a Namada payment address within Namada’s MASP.
- Namada shielded address → sends ATOM via IBC to → a new Cosmos address.
- New Cosmos address → sends ATOM via IBC to → an Osmosis address.
- Swap ATOM to DVPN on Osmosis DEX.
- Osmosis address → sends DVPN via IBC to → a Sentinel address ( **destination** ).
- Sentinel address makes an on-chain subscription to a dVPN node.

1. by retrofitting privacy to OSMO from an Osmosis address and seeding with OSMO a new Osmosis address.

- Osmosis address ( **origin** ) → sends OSMO via IBC to → a Namada payment address within Namada’s MASP.
- Namada shielded address → sends OSMO via IBC to → a new Osmosis address.
- Swap OSMO to DVPN on Osmosis DEX.
- New Osmosis address → sends DVPN via IBC to → a Sentinel address ( **destination** ).
- Sentinel address makes an on-chain subscription to a dVPN node.

1. by retrofitting privacy to DVPN from a Sentinel address and seeding with DVPN a new Sentinel address.

- Sentinel address ( **origin** ) → sends DVPN via IBC to → a Namada payment address within Namada’s MASP.
- Namada shielded address → sends DVPN via IBC to → a new Sentinel address ( **destination** ).
- New Sentinel address makes an on-chain subscription to a dVPN node.

**Observations:**

- After the swap (on the first two options), an additional step could be added to send DVPN back to Namada’s MASP, to finally send them to a new Sentinel address and complete the action. Maybe it’s too much, so it’d be great to know what others think about it.
- On the 3rd option, a substantial amount of DVPN tokens would be needed to sit at Namada’s MASP in order to “obfuscate” in-outs.

This post has been made following the [Shielded actions - Template to organize potential ideas](https://forum.namada.net/t/shielded-actions-template-to-organize-potential-ideas/284).

---

<div class="post-metadata">

**Author:** ![Gavin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/gavin/32/16_2.png) [@Gavin](https://forum.namada.net/u/Gavin)\
**Post date:** [6 October 2023 13:50 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285/2 "2023-10-06T13:50:22Z")

</div>

great idea, Daniel!

are you embedded in the Sentinel community? i’m curious to know what they think of this idea

i particularly like that you’ve proposed a specific kind of shielded action AND a [proposed template for new shielded action proposals](https://forum.namada.net/t/shielded-actions-template-to-organize-potential-ideas/284)

i haven’t much experience with the MASP yet, and we just started doing IBC transactions  
i wonder what @bengtlofgren thinks–is there a good way to spec out something like this?

---

<div class="post-metadata">

**Author:** ![bengtlofgren](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/bengtlofgren/32/33_2.png) [@bengtlofgren](https://forum.namada.net/u/bengtlofgren)\
**Post date:** [8 October 2023 11:49 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285/3 "2023-10-08T11:49:31Z")

</div>

This is a great idea and definitely feasible. It’s definitely an important use case for people who want full-stack privacy when connected to the internet. I don’t know too much about the Sentinel implementation, but the idea sounds grand!

It shouldn’t need any additional implementation from the Namada side I believe

---

<div class="post-metadata">

**Author:** ![Daniel](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/daniel/32/186_2.png) [@Daniel](https://forum.namada.net/u/Daniel)\
**Post date:** [16 October 2023 15:58 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285/4 "2023-10-16T15:58:17Z")

</div>

Thank you, Gavin! I wanted to read some feedback on this from the Sentinel community before replying. As @bengtlofgren pointed out above, it doesn’t require any specific implementation on Namada.

I have been involved on Sentinel in various ways since its first testnets around 2018–2019. As a curiosity, Sentinel was one of the early projects that adopted the Cosmos SDK and migrated from Ethereum to fully develop its use case. As it’s a privacy-focused project as well, I’m really happy that I found out a potential way to add an extra privacy layer through Namada shielded actions. These act as a catalyst to enhance privacy on external domains, so this idea came naturally to my mind once I began to understand them few months ago.

In a nutshell, most members of the Sentinel community liked the concept of “Shielded Subscriptions”, while others didn’t fully understand how these would work, but are curious about - I have tried to make it clear for them answering doubts, and will continue to do so. Regarding its implementation on dVPN apps based on Sentinel, I think it could take some time, because it’s up to their respective developers to prioritize it over other ongoing developments.

I will definitely keep pushing for this.

---

<div class="post-metadata">

**Author:** ![Gavin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/gavin/32/16_2.png) [@Gavin](https://forum.namada.net/u/Gavin)\
**Post date:** [17 October 2023 17:08 UTC](https://forum.namada.net/t/shielded-actions-subscription-to-a-dvpn-node-on-sentinel/285/5 "2023-10-17T17:08:38Z")

</div>

neat! maybe we could try a proof of concept? i’m inclined to think that Option 3, seeding, is would be the simplest thing to try

maybe between a Namada testnet like Campfire 🏕 🔥 and the Sentinel testnet

do you know if there’s a Sentinel testnet? i looked around but couldn’t find relevant info about a testnet
