Hi, currently the proposal generator tries to do too much and effectively doesn't work anyway once you put in the hash from the prepare statement. What the site tries to do is force the user to wait for 6 confs (after you paste the hash into the site) then I suppose it gives you final string to submit in the wallet. This is all awkward stuff and unnecessary stuffing about. All this proposal generator is good for is coming up with the gobject prepare .... statement based on the user's input and site's validation on the initial screen. Once it gives you the blob, the user will drop it in their core wallet console and the fee is paid hooking the proposal on chain, after that it only takes ONE conf to be valid and the next step the user should do is alter the original blob and replace the word prepare with submit and append the TX hash they got from the console and shove it back into the console.
It makes no sense to continue this flow in the proposal generator, instead the page which currently requests you input the TX hash should instead take that TX and immediately formulate the second command, eg gobject submit .....TX-hash and advise the user to paste it into the console when they have one confirmation on their previous TX, That's it ! There's nothing more to it. The proposal generator does not need to follow the chain and count 6 confs and validate the transaction hash, all of that is nonsense, the user just needs to be able to count 1 and wait a few minutes. Simplify this page, thus making it work better.
Hi, currently the proposal generator tries to do too much and effectively doesn't work anyway once you put in the hash from the
preparestatement. What the site tries to do is force the user to wait for 6 confs (after you paste the hash into the site) then I suppose it gives you final string to submit in the wallet. This is all awkward stuff and unnecessary stuffing about. All this proposal generator is good for is coming up with thegobject prepare ....statement based on the user's input and site's validation on the initial screen. Once it gives you the blob, the user will drop it in their core wallet console and the fee is paid hooking the proposal on chain, after that it only takes ONE conf to be valid and the next step the user should do is alter the original blob and replace the wordpreparewithsubmitand append the TX hash they got from the console and shove it back into the console.It makes no sense to continue this flow in the proposal generator, instead the page which currently requests you input the TX hash should instead take that TX and immediately formulate the second command, eg
gobject submit .....TX-hashand advise the user to paste it into the console when they have one confirmation on their previous TX, That's it ! There's nothing more to it. The proposal generator does not need to follow the chain and count 6 confs and validate the transaction hash, all of that is nonsense, the user just needs to be able to count 1 and wait a few minutes. Simplify this page, thus making it work better.