Polkassembly Logo

Head 1
Head 3
Head 4
Head 2
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Small Spender
Requested:35K USDT
Rejected

Google Drive Document Integrity and Certification System for Secure Proposals

inSmall Spender
3 months ago
BeneficiaryBeneficiary:

(35K USDT)

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)

3 months ago

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:

To access the API, users will be required to transfer DOT tokens to a smart contract, which will divide the transfer into two parts: one portion for the Polkadot network and another for the certification distributor to cover the service costs.

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

3 months ago

PolkaWorld votes NAY on this proposal.

  1. 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.

  2. 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.

Load more comments
PleaseLogin to comment

Confirmation Period

3

of 3

Decision Period

28 / 28 days

Confirmation Period

0 / 2 days

Summary

0%

Aye

AyeNay

0%

Nay

Aye (18)0.0 DOT

Support0.0 DOT

Nay (64)0.0 DOT

Voting Data

Approval%

Support%

Threshold0.00%

Threshold0.00%

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy