fix: backend Gnosis proposalsURI.

[crazyyuan]

No description provided.

[netlify]

✅ Deploy Preview for whimsical-cuchufli-3a5565 canceled.

Name	Link
🔨 Latest commit	867798b
🔍 Latest deploy log	https://app.netlify.com/sites/whimsical-cuchufli-3a5565/deploys/64d3b6299d126100089046ba

[thelastjosh]

Looks good / reasonable, would be helpful if you could give a quick example of the new version that's generated through this pointing out the additional stuff.

[crazyyuan]

https://services.daostar.org/api/v1/gnosis/proposals/1/0x48d1981a86bf62f3f005b03dd106789fd2d28104

[thelastjosh]

Okay, some comments on the link:

• first, DAO "name" should not be the contract address, it should be the actual name of the DAO, or empty.
• the "id" format does not follow the stated format for id in EIP-4824. I've copied the relevant section below.

In particular, any on-chain proposal MUST be associated to an id of the form CAIP10_ADDRESS + “?proposalId=” + PROPOSAL_COUNTER, where CAIP10_ADDRESS is an address following the CAIP-10 standard and PROPOSAL_COUNTER is an arbitrary identifier such as a uint256 counter or a hash that is locally unique per CAIP-10 address. Off-chain proposals MAY use a similar id format where CAIP10_ADDRESS is replaced with an appropriate URI or URL.

{
"@context": "http://www.daostar.org/schemas",
"type": "DAO",
"name": "",
"proposals": [
{
"type": "proposal",
"id": "",
"name": "",
"contentURI": "",
"status": "",
"calls": [
{
"type": "CallDataEVM",
"operation": "",
"from": "",
"to": "",
"value": "",
"data": ""
}
]
}
]
}

[crazyyuan]

Okay, some comments on the link:

• first, DAO "name" should not be the contract address, it should be the actual name of the DAO, or empty.
• the "id" format does not follow the stated format for id in EIP-4824. I've copied the relevant section below.

In particular, any on-chain proposal MUST be associated to an id of the form CAIP10_ADDRESS + “?proposalId=” + PROPOSAL_COUNTER, where CAIP10_ADDRESS is an address following the CAIP-10 standard and PROPOSAL_COUNTER is an arbitrary identifier such as a uint256 counter or a hash that is locally unique per CAIP-10 address. Off-chain proposals MAY use a similar id format where CAIP10_ADDRESS is replaced with an appropriate URI or URL.

{ "@context": "http://www.daostar.org/schemas", "type": "DAO", "name": "", "proposals": [ { "type": "proposal", "id": "", "name": "", "contentURI": "", "status": "", "calls": [ { "type": "CallDataEVM", "operation": "", "from": "", "to": "", "value": "", "data": "" } ] } ] }

Got it, I'll document this and create a new issue.