To address the other technical part of the question then (how to make Cardano tokens non-transferable), there were a few discussions (also mentioned here ) that came up in the meantime. These have been mostly disagreeable to managing token ownership & the latter of these proposals (listed here most recent first) was even deprecated at publication time by its own author:
cardano-foundation:master ← imikushin:cip-1775
opened 12:25AM - 24 Nov 22 UTC
Allow users to delegate authorized spending of outputs in their wallets to smart… contracts or other users, without sending said outputs out of their wallets.
This brings benefits to Cardano users when interacting with existing dapps and opens up new use cases, like noncustodial asset management, concurrent use of dapps and seamless integration with sidechains.
cardano-foundation:master ← zoeldevapps:cps/smart-tokens
opened 10:39AM - 20 Nov 22 UTC
The CPS standard is coming from this proposal: https://github.com/cardano-founda… tion/CIPs/tree/master/CIP-9999
The topic of smart tokens at this stage is not ready for a CIP, so I deemed a CPS to be a better fit for discussions. Since the CPS standard is not set yet and also this topic would require proper discussions potentially elsewhere, I also made this as a DRAFT.
The need to extend the functionality around tokens and their utility was raised in the Interoperability working group - https://github.com/input-output-hk/Interoperability-working-group/issues/16
Disclaimer:
I don't think I'm a good fit to define the full requirements for what smart-tokens should fulfill, neither have I the overview of the development direction of Cardano. I also don't have the connections to push this forward. I think experts in regulations, compliance definitely should have a strong say, with dapps and wallets defining how they would work from the UX perspective. My aim here is simply to raise the topic.
---
([rendered proposal in branch](https://github.com/zoeldevapps/cardano-CIPs/tree/cps/smart-tokens/CPS-%3F%3F%3F%3F))
cardano-foundation:master ← michaelpj:mpj/spending-policies
opened 01:04PM - 26 Sep 22 UTC
This adds a rejected CIP recording a possible design that has been discussed in … the past for "spending policies". I wanted to have somewhere to point when it comes up, and also to publicly record the reasons why designs like this are difficult.
---
[see rendered Markdown](https://github.com/michaelpj/CIPs/blob/mpj/spending-policies/CIP-0070/README.md)
3 Likes