-
Notifications
You must be signed in to change notification settings - Fork 334
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-0056? | Treasury donations #269
Conversation
I love this idea, but I think it there are some preceding dependencies that need to be defined first. We have a 721 standard for digital assets, but I think businesses operating as DAOs deserve their own metadata standard along with some standardized smart contracts which would be important here. I've done a lot of preliminary research on that, but I still wouldn't be ready to pull the trigger on a draft CIP. (Or should I just post the idea with some supporting arguments at this point?) Also playing into that, what trustless mechanism would be in place for a stake-holder in a revenue generating organization And then on a different note, what mechanisms would be in place for quality control so the treasury doesn't get polluted? |
Probably out of scope but food for fought: In this initial stage, where tooling and scaling solutions are critical, It could make sense to allocate a % of the treasury funds too a more centralized funding mechanism but a more efficient one - we currently have ~ 500M in the treasury with teams willing to build if properly funded. This while the other % of the treasury is allocated to the current process of Project Catalyst so we can really build the infrastructure to have a truly decentralized governance system. This would create a hybrid funding mechanism where teams with critical value prepositions could be funded fast and the project catalyst could evolve to create the foundations to the Voltaire era. The question is, which team could be responsible for this more centralized but more efficient process of funding? Probably the CF, IOG? I know @KtorZ is moving to CF with Dirk Hohndel, so probably he can enlighten us if there is any plans to use the Cardano treasury for future developments? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a brilliant plan 🤠
The upgradeability of the contract should make it easy to keep this system compatible with existing plans for the Cardano treasury. For clarity, I will detail some of the treasury plans and how this proposal is compatible with them: | ||
|
||
1. **Allowing Catalyst rounds in non-ADA tokens** (ex: COTI rewards for COTI proposals which has happened in the past). This proposal is compatible with this idea because projects could send their tokens to the treasury address. Additionally, it makes itt easier for this to happen because we could allow projects to put in 10K ADA (arbitrary number) as a fee to mint a project ID to the treasury address which can be redeemable once to add the project to Catalyst using the funds for that token present in the address. The fee of this mint would be used to both fund the main ADA treasury balance and to cover the cost of distributing rewards for the Catalyst challenge of the project. | ||
2. **DCF**. DCF is a more complicated version of Catalyst meant for higher amounts with higher auditability on spending. DCF plans to have its own Plutus scripts, so there may be an overlap in the approach, but these DCF scripts could receive their initial funding from the treasury address so there should not be a compatibility issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The best source I could find on DCF was the video from last year's Cardano Summit. If there's anything written on the subject it would help to link it here, so people can see how the ideas are compatible without having to go through the video. 😎
This is what the DCF is to a certain extent
The goal of this CIP is to start with a very simple script that is upgradeable. If we add too many features, we'll never end up with a v1 that everybody agrees on
This isn't really required because of the way the UTXO model works. If the treasury thinks a certain UTXO entry is spam, it never needs to spend it. This applies both to spam and to funds received from questionable source. |
Co-authored-by: Robert Phair <rphair@cosd.com>
Perhaps this could be solved by obfuscating the Catalyst treasury's wallet addresses, and taking donations through a script address with appropriate T&C/disclaimers, which then forwards the funds on to appropriate addresses. |
Yes, this is the standard solution in accounting-style chains. I don't see why this would be required for a UTXO chain since you could just decide not to spend a specific UTXO until some condition is met like they signed T&C |
More considerate to the people making the donation, rather than leaving their funds in limbo they are explicitly being allocated. It could also be beneficial in that they could actually earmark it for specific catalyst initiatives/categories. |
Probably this is best handled via the project mint mechanism specified in the "Allowing Catalyst rounds in non-ADA tokens" because the changes to support this feature would be the same we need for this functionality. |
Putting this back to draft as, per CIP-0084, changes proposed to the ledger must come with accompanying ledger rules modifications and formal specifications. This CIP is still well-articulated but lacks the necessary level of details that would make it a valid candidate. |
Donating to the treasury is already possible, to do it
The result will be that the deposit of Source: Ledger specs and https://iohk.zendesk.com/hc/en-us/articles/900001951926-Retiring-a-stake-pool |
re: the last comment:
|
|
thanks @perturbing I appreciate your thoughts... I'd never thought of "treasury donation" in that way before, so this is a learning experience for me. It would be good to know that so much bureaucratic work & ledger load... not to mention processes of pool analytics services carefully stabilised on a long term set size of 3000+ pools... might not be necessary for a large Treasury donation. 🤓 |
@rphair, I was wrong in my statement that 500 Ada is the minimum, the registration has to be exactly 500 Ada. I tested the behavior in the key registration case, you will get a value not conserved error if you try to deposit something apart from 2 Ada. That said, one can easily register multiple pools in one transaction to donate more than 500 Ada. Though this is bound by the maximum transaction size. One has to check how many of those minimal registration one can fit in a transaction, not an ideal solution, but it works :) |
Hey @perturbing @rphair, In the Conway Ledger era such Ada donations are going to be introduced via a transaction field, see draft Conway specification. |
@rphair @Ryun1 is this CIP still necessary given that there has been no movement or changes on it in several years and this has been implemented (at least for pure-ADA) in the Conway era? Thoughts @SebastienGllmt @KtorZ ? |
Happy to close this one out for now, |
I'm also OK with closing this, especially if the original proponents don't respond after a couple of business days (it's Sunday now). I can also see an argument that swapping native tokens for ADA before donation to the Treasury (supported in Conway) would protect against volatility and possible conflicts of interest (i.e. Treasury governance being obligated to favour a certain token). |
Cardano's treasury is currently denominated purely in ADA and has no source of revenue other than the existing reward splitting mechanism implemented at the protocol level. This CIP intends to diversity the treasury holdings and increase protocol revenue to the treasury by allowing Catalyst-funded private ventures to both diversity and increase Cardano's treasury balance.
Not handled in this CIP is the legal implications of accepting donations:
(rendered proposal from branch)