Open bakon11 opened 3 weeks ago
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: https://github.com/cardano-foundation/CIPs/pull/462#issuecomment-2305395806)
Hey @bakon11
Are there any plans on implementing API calls to check if connected wallet is associated/delegated to a DReps?
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). I did this because I wanted to seek maximum adoption for CIP95/governance for wallets, so I moved the burden of indexing governance data from wallets to dApps
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.
@Ryun1
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.
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?