Skip to content
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

Add reference field when Minting/Burning tokens #841

Closed
lkngtn opened this issue Jun 14, 2019 · 3 comments
Closed

Add reference field when Minting/Burning tokens #841

lkngtn opened this issue Jun 14, 2019 · 3 comments

Comments

@lkngtn
Copy link

lkngtn commented Jun 14, 2019

Note: this has been closed to be tracked in the "wishlist for future upgrades".


Is your feature request related to a problem? Please describe.
The token manager is commonly being used to manage group membership, so the action to mint a token or burn a token is equivalent to membership proposal. These proposals typically require approval via a voting app, but there is very little context provided to voters when evaluating a decision other that the tokens and address.

Describe the solution you'd like
It would be useful for users to provide a reference (like the finance app has) that would allow users to provide information to the voting app about the purpose/intention of the proposal and to include a link to an external source for discussion (like a github or forum post).

Describe alternatives you've considered
I know there is plans to add discussions to apps like voting which would be also very useful and perhaps a better long term solution. However, such a solution would be complementary to the reference approach, and so I don't see it as an either or type of decision.

Additional context
This functionality is a requirement for an upcoming dao launch, so there is some urgency to this request.

@john-light
Copy link
Contributor

I've been thinking about "proposal metadata" for a while since we've had to kind of hack our way around this for AGPs.

One solution I've thought of is that for any action that becomes a vote (or for any vote created directly in the Voting app) users are put into a flow to fill out metadata about the proposal before submitting the transaction to create the vote.

The flow would be like:

Action -> You can't do that directly, but you can create a vote -> Fill out metadata -> create vote

Then the user would have the option to fill out a few fields of metadata like:

  • Title
  • Description
  • URL
  • Attachments (insert IPFS hash)

The metadata itself doesn't need to be stored on-chain but could be put in a text file that is stored on IPFS and only the IPFS hash of the text file is stored in the vote transaction on chain.

@sohkai
Copy link
Contributor

sohkai commented Jul 2, 2019

@john-light A flow of this sort would be possible with #452, along with a bit of structured information from apps that describe what their forwarding inputs are.

@sohkai
Copy link
Contributor

sohkai commented Mar 18, 2020

Closing; we will evaluate this for new contract changes.

@sohkai sohkai closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants