[SS] DOT #1557 - Google Drive Document Integrity and Certification System for Secure Proposals
active
Description

https://polkadot.subsquare.io/referenda/1557

A certification system is suggested to make sure proposal documents are real and cannot be changed. This system checks if the documents stay the same as when they were first made and tells us if any changes are made, showing when and what was changed. This helps to keep the proposal process safe and makes sure everyone can trust that the documents show the agreed terms without any changes made without permission.

Appendants
1
#1
5d ago

🟢 0 • 🔴 5 • ⚪️ 2
Required majority (more than 50%) of non-abstain votes not met.
Vote #1: NAY
10 available members.
No CoI reported. DV delegation exercised.
https://polkadot.subscan.io/extrinsic/26073110-2
https://polkadot.subsquare.io/referenda/1557#4

Cast your votesingle

Votes·10

15fT...yBzL
15fT...yBzL
15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL
Nay
# 2
Hard nay. Left my comments on the proposal: https://polkadot.subsquare.io/referenda/1557#1
1ZSP...vx6w
1ZSP...vx6w
1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w
Abstain
# 3
Thank you for proposing a solution that integrates blockchain and would be built on Polkadot. Interested to know how this would continue to run. What parties are needed and what cost would that entail? Who would do the hosting and how much would it cost? What would be the benefits over the potentially similar solutions that others have worked on?
12Hi...E9N3
12Hi...E9N3
12His7t3EJ38tjdBbivUzWQeaNCLKfMqtKp1Ed3xHMyCE9N3
Nay
# 2
From what I understand by both fellow DAO members as well as comments left by community members under the proposal, much of the functionality proposed is already available to proposers but isn't used. While I understand some streamlining is possible to make the proposal process smoother, I would assume most proposers have enough technical acumen to make use of the already available tools to secure the integrity of their proposal documents. Maybe a WFC is in order to enforce this?
1xzc...1bX6
1xzc...1bX6
1xzcLSwo7xBFkJYZiL4EHaqFpuPTkH641E3V43W4cuk1bX6
Nay
# 2
We share the same concerns as The Ionian Group.
13ED...KQbF
13ED...KQbF
13EDmaUe89xXocPppFmuoAZaCsckaJy3deAyVyiykk1zKQbF
Nay
# 2
14gM...deVb
14gM...deVb
14gMJV95zwxUsFEZDSC8mtBVifS6SypKJkfBKANkMsLZdeVb
Nay
# 2
I think this proposal try to solve a real problem in a wrong way.
167Y...TY9F
167Y...TY9F
167YoKNriVtP4Nxk9F9GRV7HTKu5VnxaRq1pKMANAnmmTY9F
Abstain
# 3
Out of my Depth slanting towards a Nay based on Forum and internal comments
12Kt...DCoJ
12Kt...DCoJ
12KtA8mtfsK1CyQb4utLiwG3ao22z77w2cM2GqnaL2RiDCoJ
Nay
# 2
The proposed strategy seems excessive imo. A lightweight, cost-effective solution that minimizes friction for proposers and voters should suffice. By reaching community consensus on the best approach (as discussed in ongoing forum threads), we can likely implement a solution faster and at lower cost than proposed. Leveraging existing platforms like SubSquare or PolkAssembly is preferable, as they are well-equipped to deliver such features quickly and efficiently.
14Gn...YLEh
14Gn...YLEh
14Gn7SEmCgMX7Ukuppnw5TRjA7pao2HFpuJo39frB42tYLEh
Nay
# 2
12s6...nE8h
12s6...nE8h
12s6UMSSfE2bNxtYrJc6eeuZ7UxQnRpUzaAh1gPQrGNFnE8h
Nay
# 2
The problem is valid, but this approach feels overengineered and redundant when simpler, existing tools already cover most of the functionality. Nay here.

Discussions·0

No current comments
Information
Snapshot
Timestamp
Created
May 09 2025 17:48
Start date
May 09 2025 00:00
End date
Jun 08 2025 00:00
Results
Voters
10
one-person-one-vote
Aye
0 VOTE
 
Nay
8 VOTE
 
Abstain
2 VOTE
 
© 2025 OpenSquare. All Rights Reserved.