You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some proposals (I am thinking of Smart Contract Execute proposals) may benefit from some kind of templating.
The way I imagine it is that anyone could create a template with
Smart Contract address
JSON Execute message
Within the JSON message, we could select some fields that would be mapped to some "template variables".
Then, when someone wants to create a proposal based on that template (e.g. "Swap USDC to NTRN on Astroport" template), they would just need to fill in some fields:
belief price
max spread
And it would automatically create the proposal, by filling the correct information in the JSON directly.
For a "swap USDC to NTRN on Astroport", we would have something like:
SC address: neutron18c8qejysp4hgcfuxdpj4wf29mevzwllz5yh8uayjxamwtrs0n9fshq9vtv
Execute Smart Contract Message:
Just for this specific case, we could also restrict the funds to be only one denom possible: USDC. Not sure if it should be made restricted in the UI, or if just a description on the template would work, something like "Please only provide Noble USDC as funds for this proposal".
For some cases, restricting may not make sense, so it may just be a nice-to-have feature for later (maybe would need a separate issue when / if this feature is developed).
The text was updated successfully, but these errors were encountered:
Some proposals (I am thinking of Smart Contract Execute proposals) may benefit from some kind of templating.
The way I imagine it is that anyone could create a template with
Within the JSON message, we could select some fields that would be mapped to some "template variables".
Then, when someone wants to create a proposal based on that template (e.g. "Swap USDC to NTRN on Astroport" template), they would just need to fill in some fields:
And it would automatically create the proposal, by filling the correct information in the JSON directly.
For a "swap USDC to NTRN on Astroport", we would have something like:
SC address: neutron18c8qejysp4hgcfuxdpj4wf29mevzwllz5yh8uayjxamwtrs0n9fshq9vtv
Execute Smart Contract Message:
Just for this specific case, we could also restrict the funds to be only one denom possible: USDC. Not sure if it should be made restricted in the UI, or if just a description on the template would work, something like "Please only provide Noble USDC as funds for this proposal".
For some cases, restricting may not make sense, so it may just be a nice-to-have feature for later (maybe would need a separate issue when / if this feature is developed).
The text was updated successfully, but these errors were encountered: