Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CIP-???? | Cardano FUDS (Financial Updates & Disclosure Specification) #495

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

Crypto2099
Copy link
Collaborator

Initial framework for Cardano FUDS (Financial Updates & Disclosure Specification).

More details and conversation coming soon!

@Crypto2099
Copy link
Collaborator Author

Link to rendered version of this CIP.

@Ryun1 Ryun1 changed the title CIP-XXXX: Cardano FUDS (Financial Updates & Disclosure Specification) CIP-???? | Cardano FUDS (Financial Updates & Disclosure Specification) Apr 3, 2023
@Ryun1 Ryun1 added the Category: Tokens Proposals belonging to the 'Tokens' category. label Apr 3, 2023
Copy link
Collaborator

@rphair rphair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if implemented this would be a great improvement on what other blockchains are offering industry aggregators, and would be a newsworthy advance in the industry if Cardano's own aggregators were to support such auditing.

@Crypto2099 what's the next step in getting community review & endorsement?

  • What can we do to get Cardano token principals to review it?
  • Have you done one of your educational videos about it, or do you plan to?
  • Maybe someone at the Cardano Foundation (e.g. @gufmar @KtorZ) could provide developer relations support, given the significance of such a proposed standard?

Just touching up some format issues in the last commit so we can save reviewer's attention for commentary on the content itself. Well done & will do whatever I can do help move this along.


This CIP is licensed under [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).

## Footnotes
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we don't have a section like this (e.g. I had to eliminate it from my own CIP when standardising it: #429), and given this is hypertext after all, can you fold these footnote links into SEO anchors in the document itself so this section can be eliminated?

If this is not considered necessary then maybe @KtorZ will overrule this suggestion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm conflicted. I feel like re-introducing the full link and comment about "what it is" where these things are referenced in the context of the CIP distracts from the language of what we're attempting to explain in the CIP... This is why I opted for a Wiki-like "References" section.

@Crypto2099
Copy link
Collaborator Author

I think if implemented this would be a great improvement on what other blockchains are offering industry aggregators, and would be a newsworthy advance in the industry if Cardano's own aggregators were to support such auditing.

@Crypto2099 what's the next step in getting community review & endorsement?

  • What can we do to get Cardano token principals to review it?

I have spoken (of course) to the team at DripDropz about it, and have reached out to Xerberus, TapTools, and SCAT DAO in terms of community aggregators projects. CSWAP has also been part of the conversation as my impetus for creating the CIP was due to a Twitter engagement with their team about the lack of "verified" circulation information for Cardano Native Assets on CoinMarketCap and CoinGecko.

  • Have you done one of your educational videos about it, or do you plan to?

We had a great space with Xerberus yesterday to discuss it, I'm not sure how long these recordings last but it can be found here: https://twitter.com/Xerberus_io/status/1643629792065880072

  • Maybe someone at the Cardano Foundation (e.g. @gufmar @KtorZ) could provide developer relations support, given the significance of such a proposed standard?

I have had some DMs so far with John MacPherson about the CF helping particularly as it relates to "getting in the room" with the large 3rd party aggregator services once the standard is complete and ready for public consumption.

Just touching up some format issues in the last commit so we can save reviewer's attention for commentary on the content itself. Well done & will do whatever I can do help move this along.

@thaddeusdiamond
Copy link
Contributor

Again nicely done @Crypto2099. Really enjoying reading these. Just some general thoughts, though I think as a v1 this definitely passes the smell test.

  1. What do you think about the Digital Asset Market Structure (DAMS) proposal? I definitely don't want to make this too US-centric (I myself abide by US laws and regulations but understand jurisdictional variation). However, in it there are some really interesting concepts about the "Digital Asset Project Lifecycle". I might review that PDF and see if you can pull any concepts or information from there too match it up. That way, this disclosure specification (especially if it is stored on-chain or somehow linked to CIP-0088? | Token Policy Registration #467, would be a one-click copy/paste to anyone using Cardano and wanting to register in the US.
  2. How do you feel about extending the specification to non-fungible tokens? I think it could be a totally separate proposal, but to me, a lot of the concepts are the same. For example, there is no concept of "ownership" or "allocation" because you are selling art. However, policy IDs, asset IDs, airdrops, incentives, etc. all play some role in building a community. In the end, you may have to add concepts like project wallets, royalty addresses, etc. But it could be interesting to consider that as an extension to this spec.

@Liberty-Chris
Copy link

Well done, brother. I'm proud of you and really happy about what this will do for the entire ecosystem. Here's to the next chapter.

@rphair
Copy link
Collaborator

rphair commented Aug 20, 2024

@Crypto2099 how is this one going? I'm tagging it Waiting for Author and feel sure you can provide some update of what we are "waiting" for, since it's come up at the meeting once or twice as still being in progress. If waiting for any external factor please let's document here so it doesn't appear eligible for the Abandoned tag.

@rphair rphair added the State: Waiting for Author Proposal showing lack of documented progress by authors. label Aug 20, 2024
@rphair
Copy link
Collaborator

rphair commented Sep 24, 2024

@Crypto2099 this seems abandoned so please either confirm that some progress is being made with this or close this PR (with an explanatory message if you can, since I believe it was a good idea) if the concept or method has been invalidated somehow.

@rphair rphair added State: Likely Abandoned Close if confirmed abandoned (long waiting). and removed State: Waiting for Author Proposal showing lack of documented progress by authors. labels Sep 24, 2024
@rphair rphair closed this Oct 7, 2024
@Crypto2099
Copy link
Collaborator Author

Hey @rphair thanks for the nudge on this and apologies I did not get back sooner. This CIP had stalled somewhat while waiting for myself to get some work done on the CIP-88 implementation which was always a precursor to this CIP so that information could be verifiably stored on-chain.

To that end, more work is scheduled to begin towards this CIP towards the end of 2024 and in Q1 2025 we will hopefully have a working prototype for this CIP.

@Crypto2099 Crypto2099 reopened this Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Tokens Proposals belonging to the 'Tokens' category. State: Likely Abandoned Close if confirmed abandoned (long waiting).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants