Google Drive Document Integrity and Certification System for Secure Proposals
We propose the integration of a certification system that ensures the authenticity and immutability of proposal documents. This system would function by verifying that documents remain unchanged from their original state and would provide an alert system that tracks any modifications, indicating when and what content was altered. This solution would guarantee the initial conditions of the approved proposals and offer an additional layer of transparency. By implementing this system, we can secure the sovereignty of the proposal process within the treasury, ensuring that all parties involved can trust that the documents reflect the agreed terms without unauthorized tampering.
To read full proposal click here
Comments (4)
Confirmation Period
3
of 3Decision Period
28 / 28 days
Confirmation Period
0 / 2 days
Summary
0%
Aye
0%
Nay
Aye (18)0.0 DOT
Support0.0 DOT
Nay (64)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
Hi @Open 4 Blockchain,
I agree that it's necessary that the proposers include the PDF files and their hashes in the proposal, but it is basically free to do it on IPFS, and both myself and some others have already been applying this practice in our proposals. You are proposing to charge the treasury for interfacing with free services, and on top of that you're planning to charge the community further for the use of the services:
Totally unnecessary. Any proposer can already do it for free. It's just a matter of enforcement by the community. If we want to include it in the workflows of Subsquare or Polkassembly, then those teams should be funded to implement this feature.
Nay.
Best,
kukabi | Helikon
PolkaWorld votes NAY on this proposal.
From Polkadot’s perspective, this is not an urgent or high-priority need. Additionally, PolkaWorld would like to strongly recommend that all proposers publish the full content of their proposals on-chain in the future. We also suggest that Polkassembly and Opensquare develop a tagging feature to categorize proposals. This would greatly support treasury fund classification and help establish a clearer prioritization framework.
The Budgets section of this proposal is overly simplistic and lacks necessary detail. A proper and transparent budget should include: milestones, development functions and descriptions, involved personnel (by role), estimated time per role, and respective hourly rates.