-
Notifications
You must be signed in to change notification settings - Fork 318
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-0030: API methods for Governance E.g. Checking DRep delegation. #923
Comments
cc @Ryun1 - I was also wondering if such methods will fit into CIP-0030 as opposed to one or two of the wallet APIs that might supersede it (e.g. the candidate CIP-0090 or future alternative referred to here: #462 (comment)) |
Hey @bakon11
Good question, in short probably not (feel free to propose a CIP30 extension to add this) Having wallets serve governance data was something I avoided intentionally did not do for the CIP-30 governance extension (CIP-95). In general I tend to feel that the DApp specific logic (be it governance in this case) should place the indexing burden upon the DApp, rather than the wallet. |
Agreed, I was more specifically speaking just about maybe being able to pull the DRep info, since most wallets already support dRep creation and delegation options anyways. and everything else exactly should be handled by the dApp, |
ahhh ok just looked through CIP-0095 makes sense now. |
Yes, thank you. |
With the ERA of on chain governance(CIP-1694) upon us. Many wallets are implementing governance tools For creating/delegating to dreps and casting votes.
Are there any plans on implementing API calls to check if connected wallet is associated/delegated to a DReps?
The text was updated successfully, but these errors were encountered: