CaptAhab
Active member
I didn't enter any commands, just pasted outcomes from the wallet and proposal tool.
Proposal problem: Governance object is not valid
- Thread starter DanyDee
- Start date
handymannn
New member
CaptAhab
Active member
I didn't use Dash Treasury, because the admin on this site suggested I use https://proposal.dash.org/ as the official site.
dashdisciple
Active member
Lesson of the day: Be wary when someone calls something "official", especially when it interfaces with a public decentralized blockchain.
Thanks @CaptAhab , this is exactly what I need.
lesson of the day :
we wary when 3rd parties have a problem with an official trustless blockchain tool
abob54
Member
lesson of the day :
we wary when 3rd parties have a problem with an official trustless blockchain tool
It's these pages and pages of users who have a problem with your "official" tool, @tungfa. It's exceedingly complex. Perhaps you are in a position to either improve the tool, improve support for the tool, or at least provide better documentation for it. I'm not sure how many more users need to lose 5 Dash or run into panic/delays for this to become clear.
It's okay to defend your product vehemently, but it's irresponsible to do so when it's no longer the best option for users.
well
i did the 1st testrun with proposal@ , and tbh if i can do it , so can anybody (as i am not the tech pro here)
it seems the problems got worth as now people are between multiple pages and proposal generators
the team is looking into the latest issues posted + i will be working on a guide
i did the 1st testrun with proposal@ , and tbh if i can do it , so can anybody (as i am not the tech pro here)
it seems the problems got worth as now people are between multiple pages and proposal generators
the team is looking into the latest issues posted + i will be working on a guide
I am working on it now, but can't give you any guarantees. What's interesting is the timestamp you posted along with the command -- 1500040217. This is machine-speak for "2017-07-14 13:50:17 UTC". The funny thing is that your collateral transaction was included in a block on blockchain before that time happened.
Your collateral TX was included in this block:
http://insight.dash.org/insight/blo...436e786c748324efbda34dd57ac5be7f5222ed7a59d46
...which has a timestamp of 1499973860, or 2017-07-13 19:24:20 UTC.
I do have a few questions which might help me understand more about what happened.
Did you happen to refresh your browser when you created this proposal?
What browser were you using (e.g. Chrome, Firefox, etc.)?
Is your computer's system clock incorrect/off?
I'll note that all timestamps used are in UTC so time zone differences should not have affected anything.
CaptAhab
Active member
Hi @nmarley
Many thanks, something happened when I was first on the waiting for confirmations screen, after getting the txid. The web page jumped back to a blank proposal form, with no forward option on the browser (I did not refresh the browser).
I then stated again, and submitted with the previous TX id. I did this on a number of occasions trying to make it work. The info I sent was just from the most recent attempt.
I am using Chrome and the time on my PC is correct.
Best
Many thanks, something happened when I was first on the waiting for confirmations screen, after getting the txid. The web page jumped back to a blank proposal form, with no forward option on the browser (I did not refresh the browser).
I then stated again, and submitted with the previous TX id. I did this on a number of occasions trying to make it work. The info I sent was just from the most recent attempt.
I am using Chrome and the time on my PC is correct.
Best
Last edited:
Ahhh... ok, this answer a lot actually. When you do a "prepare", the proposal parameters and the timestamp are all hashed, and that hash is stored with the burned funds in OP_RETURN. So in order to submit the proposal, you have to submit it with all the parameters the same as when they were prepared.
That said, I believe it's just a matter of guessing the right timestamp AND the right start_time and end_time which are encoded within the proposal data. Since the gap between proposal start and end time are the same distance, I think that we'll only have to figure out the two variables, but it might take some time. I've written a tool to help and will try and run it this evening with several different input ranges to see if I can "guess" the hash needed to submit your proposal. I'll keep you informed, probably won't be 'til later this afternoon/evening.
@CaptAhab Oh, wanted to ask:
Did any of the proposal parameters change from the first time you issued the prepare command? Dash address, URL, proposal name?
If any of those things changed it might be extremely difficult to recover the proposal at this point.
The "gobject prepare" command might have that info if you still have your Dash-Qt client open and haven't closed it in the few days that have passed. Actaully, if you have that it would be best, but I understand it's not likely.
Did any of the proposal parameters change from the first time you issued the prepare command? Dash address, URL, proposal name?
If any of those things changed it might be extremely difficult to recover the proposal at this point.
The "gobject prepare" command might have that info if you still have your Dash-Qt client open and haven't closed it in the few days that have passed. Actaully, if you have that it would be best, but I understand it's not likely.
CaptAhab
Active member
I attempted to use the same proposal name, that's the only thing that may have changed!
Here is the earliest submission I have
gobject submit 0 1 1499978105 5b5b2270726f706f73616c222c7b22656e645f65706f6368223a2231353033303932303535222c226e616d65223a225375727665792d7768792d4d65726368616e74732d6e6f742d7573696e672d44617368222c227061796d656e745f61646472657373223a2258775565466955517a31714c75727a63707a4b4244555450766a31547a7833465973222c227061796d656e745f616d6f756e74223a2238322e3735222c2273746172745f65706f6368223a2231353030353136353735222c2274797065223a312c2275726c223a2268747470733a2f2f7777772e646173682e6f72672f666f72756d2f746872656164732f70726f6a6563742d70726f706f73616c2d756e6465727374616e64696e672d7468652d62617272696572732d746f2d61646f7074696f6e2d6f662d646173682d62792d756b2d627573696e65737365732d616e642d6d65726368616e74732e31353737302f227d5d5d a89d5da1466d1e7556c7c957f741992d5d795adafde8106edfa9df1f80ac1df3
On later ones I know I changed the proposal name.
Fingers crossed.
Thanks
Here is the earliest submission I have
gobject submit 0 1 1499978105 5b5b2270726f706f73616c222c7b22656e645f65706f6368223a2231353033303932303535222c226e616d65223a225375727665792d7768792d4d65726368616e74732d6e6f742d7573696e672d44617368222c227061796d656e745f61646472657373223a2258775565466955517a31714c75727a63707a4b4244555450766a31547a7833465973222c227061796d656e745f616d6f756e74223a2238322e3735222c2273746172745f65706f6368223a2231353030353136353735222c2274797065223a312c2275726c223a2268747470733a2f2f7777772e646173682e6f72672f666f72756d2f746872656164732f70726f6a6563742d70726f706f73616c2d756e6465727374616e64696e672d7468652d62617272696572732d746f2d61646f7074696f6e2d6f662d646173682d62792d756b2d627573696e65737365732d616e642d6d65726368616e74732e31353737302f227d5d5d a89d5da1466d1e7556c7c957f741992d5d795adafde8106edfa9df1f80ac1df3
On later ones I know I changed the proposal name.
Fingers crossed.
Thanks
I'm seeing different payment addresses as well in the two outputs you've provided me.
Will try with the earliest and see if I can get a match. If not, it's likely the proposal process will need to be re-done. If this is the case, you will only want to "prepare" once, then keep that Dash-QT console open. Grab a bite, watch a show, whatever you need to do. Come back after 6 confirmations and enter the exact same thing, only change "prepare" to "submit" and add the TXID of your "prepare" transaction at the end. Or you might use the tools at DashCentral or other sites if it's easier.
Code:
$ python bin/dehex.py 5b5b2270726f706f73616c222c7b22656e645f65706f6368223a2231353033303932303535222c226e616d65223a225375727665792d7768792d4d65726368616e74732d6e6f742d7573696e672d44617368222c227061796d656e745f61646472657373223a2258775565466955517a31714c75727a63707a4b4244555450766a31547a7833465973222c227061796d656e745f616d6f756e74223a2238322e3735222c2273746172745f65706f6368223a2231353030353136353735222c2274797065223a312c2275726c223a2268747470733a2f2f7777772e646173682e6f72672f666f72756d2f746872656164732f70726f6a6563742d70726f706f73616c2d756e6465727374616e64696e672d7468652d62617272696572732d746f2d61646f7074696f6e2d6f662d646173682d62792d756b2d627573696e65737365732d616e642d6d65726368616e74732e31353737302f227d5d5d
[["proposal",{"end_epoch":"1503092055","name":"Survey-why-Merchants-not-using-Dash","payment_address":"XwUeFiUQz1qLurzcpzKBDUTPvj1Tzx3FYs","payment_amount":"82.75","start_epoch":"1500516575","type":1,"url":"https://www.dash.org/forum/threads/project-proposal-understanding-the-barriers-to-adoption-of-dash-by-uk-businesses-and-merchants.15770/"}]]
$ python bin/dehex.py 5b5b2270726f706f73616c222c7b22656e645f65706f6368223a2231353033303933323532222c226e616d65223a225768792d6172652d4d65726368616e74732d6e6f742d7573696e672d44617368222c227061796d656e745f61646472657373223a22586f664e59384a59537341644b68314263774b4b6e435454517a456e485878587368222c227061796d656e745f616d6f756e74223a2238322e3735222c2273746172745f65706f6368223a2231353030353137373732222c2274797065223a312c2275726c223a2268747470733a2f2f7777772e646173682e6f72672f666f72756d2f746872656164732f70726f6a6563742d70726f706f73616c2d756e6465727374616e64696e672d7468652d62617272696572732d746f2d61646f7074696f6e2d6f662d646173682d62792d756b2d627573696e65737365732d616e642d6d65726368616e74732e31353737302f227d5d5d
[["proposal",{"end_epoch":"1503093252","name":"Why-are-Merchants-not-using-Dash","payment_address":"XofNY8JYSsAdKh1BcwKKnCTTQzEnHXxXsh","payment_amount":"82.75","start_epoch":"1500517772","type":1,"url":"https://www.dash.org/forum/threads/project-proposal-understanding-the-barriers-to-adoption-of-dash-by-uk-businesses-and-merchants.15770/"}]]Will try with the earliest and see if I can get a match. If not, it's likely the proposal process will need to be re-done. If this is the case, you will only want to "prepare" once, then keep that Dash-QT console open. Grab a bite, watch a show, whatever you need to do. Come back after 6 confirmations and enter the exact same thing, only change "prepare" to "submit" and add the TXID of your "prepare" transaction at the end. Or you might use the tools at DashCentral or other sites if it's easier.
Hey @CaptAhab ,
Wanted to let you know the results on this -- I wasn't able to figure out what the hash was.
Eventually I restored to compiling a range guesser into DashCore and trying to guess using that and a custom Python script to generate the proposal data using the time ranges which are within a few hours of when you prepared the TX as well as within around an hour of the estimated next block time, but no such luck. I believe there are too many variables that could have been different.
Branch of DashCore code for reference: https://github.com/dashpay/dash/compare/v0.12.1.x...nmarley:genhash-debug
Custom Python script: https://github.com/nmarley/prop-gen
I'm sorry about the loss of your 5 Dash, really wish there was a way to recover it. Without the original "prepare" command, it's almost impossible to know what's changed or guess the hash parameters.
In the future, I'd suggest leaving the Dash-Qt window open after you "prepare", and do not close it. Save the TXID that gets returned also. Your "gobject prepare" and the TXID that results are the only things needed to submit the proposal, but you cannot change any of the information once it's been prepared. By keeping the Dash-Qt console window open, you're able to simply cut-and-paste the command, change "prepare" to "submit", then add the TXID at the end.
Wanted to let you know the results on this -- I wasn't able to figure out what the hash was.
Eventually I restored to compiling a range guesser into DashCore and trying to guess using that and a custom Python script to generate the proposal data using the time ranges which are within a few hours of when you prepared the TX as well as within around an hour of the estimated next block time, but no such luck. I believe there are too many variables that could have been different.
Branch of DashCore code for reference: https://github.com/dashpay/dash/compare/v0.12.1.x...nmarley:genhash-debug
Custom Python script: https://github.com/nmarley/prop-gen
I'm sorry about the loss of your 5 Dash, really wish there was a way to recover it. Without the original "prepare" command, it's almost impossible to know what's changed or guess the hash parameters.
In the future, I'd suggest leaving the Dash-Qt window open after you "prepare", and do not close it. Save the TXID that gets returned also. Your "gobject prepare" and the TXID that results are the only things needed to submit the proposal, but you cannot change any of the information once it's been prepared. By keeping the Dash-Qt console window open, you're able to simply cut-and-paste the command, change "prepare" to "submit", then add the TXID at the end.
I would also advise to save prepare command somewhere in txt file BEFORE entering it into Dash Core console window.
abob54
Member
@CaptAhab Your proposal is posted to the blockchain now (+2.71%, good start!).
Was the process on Dash Treasury any easier or is there a way it could be simplified/improved from the viewpoint of a proposal owner like yourself?
Was the process on Dash Treasury any easier or is there a way it could be simplified/improved from the viewpoint of a proposal owner like yourself?