Search results

You're halfway there then making assumptions about the rest, why would it be better if it occurred during v21 activation? This entire PR and all those commits are to do with BLS serialization, the bug was an edge case in the serialization, in the masternodelist, which involves protxs and...

We expect sporadic chainlocks soon (within 12-24h) and full chainlocks/instantsend within 40-50h. Note these are only estimated though

We don't see anything in the modqueue on Dashpay Reddit, did you delete your posts?

That's probably automatic rather than manual, I'll ping a few people

I also have some code from before I joined DCG: https://github.com/ktechmidas/garlictipsbot Mostly for Reddit, did include Dash support (but only for conversion) but maybe you can use it :)

I see! We've gone ahead and added a link at the top of the documentation at docs.dash.org that should link to the forum in future, thanks for the feedback :)

I will pass that on internally as well, which docs were you reading? We're always looking to improve them

It's on the list of things to be done, yes.

Window -> Console Which docs are you reading? They likely need to be updated

Note: We're shuffling some categories around, so things may look a little different than you're used to! Don't panic :) (Also there's a new archived section right at the bottom now)

Hey, I've forwarded it on internally cheers!

Just for everyone else (and yourself) encrypting a wallet will not help with unauthorized transactions, an unauthorized transaction means your private keys have been leaked. No matter what you do on your own machine if someone has the public and private part of a key, they have control of a...

I'm confused by the address here, an address starting with an X is a real, mainnet, actual value address, not a sandbox. Anyway... I would back the dash.conf up somewhere safe and start with a new one, since your wallet isn't included with the dash.conf it should load no issue (may complain...

At this point it's up to you, you can stash the changes as I mentioned earlier or simply reset to the HEAD (ie 1.7.1) which will delete your local changes with git reset --hard HEAD Then run a git pull to get to 1.7.3

Interesting, in that same dir run this to get the version grep -ir sentinel_version ./lib/config.py

It means something changed in that file locally for you, run git diff HEAD and if it's not important you can run git stash example to stash the change then run a git pull If you want the change back afterwards you can then run git stash apply

It shouldn't, here was the 1.7.3 release: https://github.com/dashpay/sentinel/commit/fa6c05175f864cb50145bf50c8cf0c9969fcd3a2

Sentinel updates will be needed to 1.7.3 before the HF activation

No worries! I was online at the time and scanning through recents to ban spammers and saw you ;)

There is a pre-proposals area over here: https://www.dash.org/forum/index.php?forums/new-budget-proposal-discussions.93/ You can try it :)