-
Notifications
You must be signed in to change notification settings - Fork 27
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
proposalsURI for Snapshot DAOs #203
Comments
Sure Aman. I propose that we include members URI for Snapshot too. It's the same case with that too. |
I agree with Aman.
On Fri, Feb 2, 2024 at 9:29 PM Rashmi V Abbigeri ***@***.***> wrote:
Sure Aman. I propose that we include members URI for Snapshot too.
It's the same case with that too.
An example might be, ENS registration instance.
—
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHA5PBCG47SRTHFRUJATADYRWVJPAVCNFSM6AAAAABCXIBE7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGA2DANJXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
joshuatan.com/research
|
Moving this to High Prio |
Aman <> Rashmi (14.02.2023) Questions:
Wondering if we should also share the membersURI we created for Lodestar to Snapshot (@Rashmi-278 could submit a PR and ask them to review it ). |
This would the data included in the ContentURI for a Proposal
Snapshot Query
|
More Context on above: Me and Aman discussed the differences in the content returned by our API and Snapshot's API. According to EIP-4824, any content such as title and more info on proposals should be inside contentURI of a proposal, what additional content should we provide for a proposal through our API is what being discussed above. |
Referencing EIP-4824 Proposal URI JSON, created a PR to add more fields to Snapshots Proposals URI |
This issue has been worked and completed, Snapshot Merged our PR |
Check out the proposalsURI Snapshot publishes: https://hub.snapshot.org/api/eip4824/opcollective.eth/proposals
This is a sample proposalURI our Register service creates: https://services.daostar.org/api/v1/snapshot/proposals/opcollective.eth
The former returns more data. I feel like we can easily return more data (and we should) through our proposalsURI. See the proposalsURI JSON-LD schema suggested by the standard: https://daostar.one/EIP. In short, this issue was created to examine if the proposalsURI we create now needs to be fleshed out more.
@Rashmi-278, I'm assigning this to you but let's wait until @thelastjosh has a look to start working.
The text was updated successfully, but these errors were encountered: