-
Notifications
You must be signed in to change notification settings - Fork 4
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
Store proposals on IPFS #90
Comments
Hey, @tupui |
also, the action JSON data, is it stored as another file in IPFS? |
Yes the proposal should always be For the JSON data, I will make a new link with everything to show. Let's call the file, |
in the outcome, should I display the XDR data or decoded data of it? |
We only display the decoded data. So json. We do t need to show the XDR itself there. What we will need is to add a link somewhere on the page to see the files on IPFS. This way people can verify for themselves everything if they want to. |
Here is the new link with outcomes: https://bafybeigstnjnededvbckmvlmodpw2m745i5lidmyttb4u7o6ouiudokbx4.ipfs.w3s.link |
then I'll add 'link' icon to the beside of the titles 'Proposal Description' and 'Proposal Outcome' https://bafybeigstnjnededvbckmvlmodpw2m745i5lidmyttb4u7o6ouiudokbx4.ipfs.w3s.link/proposal.md |
That works 👍 |
Relates to #83 (comment)
Send the proposal to IPFS with Storacha to the DID of the project (https://docs.storacha.network/how-to/upload/). The proposal is a markdown file and can have images.
Here is an example of proposal
https://bafybeidsfg2rfmpgtisfnmk6lur5dmy6j4kwjblh2rhme6nrsvjcaci4jq.ipfs.w3s.link
To store the possible actions in XDR form. I think the best would be to store a json file (I will make an example tomorrow and provide another IPFS link.) This JSON file need to be loaded and displayed at the bottom of the proposal.
The XDR field is optional.
See the laboratory for some XDR example. We are storing in the JSON files the XDR as a string. But in the UI we are only interested in displaying the JSON form. The XDR should be a collapsible and scrollable as it can be long.
The text was updated successfully, but these errors were encountered: