Search results

RC2 (https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc2) has just been released. Changes in RC2 only affect masternodes, so please upgrade masternodes. The most important change is a fix for the intra-quorum communication which skipped deterministic connections to nodes with the same IP...

@f8192 @xkcd as far as I know, this is the behavior we always had when receiving a TX while being offline. This is only different on SPV wallet which do a BIP35 mempool request on startup. Or did you verify that this behavior is different on other version of Dash, e.g. on 0.13.2?

Release candidate v0.14.0.0-rc5 is ready for testnet! :) Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5 Release notes are not ready yet and will be prepared in the next few days. Post will be updated. Gitian sigs can be found here...

As @UdjinM6 said, EC105D04 is my subkey which I currently use for signing. I have now added [email protected] to my primary key and updated the public key on keybase. You can import it with: curl https://keybase.io/codablock/pgp_keys.asc | gpg --import

RC11 has just been released: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc11 Only change is a new parameter for all protx commands. The parameter allows you to specify which address should be scanned for inputs usable as fees source. If not specified, it will try to use the...

RC10 has just been released: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc10 Please upgrade when you find time, it's however not that urgent this time. @qwizzie We are in feature freeze atm and only do fixes from now on. I think RC10 is pretty stable and might end up being the last...

UPDATE: The DIP3 BIP9 deployment has been activated, bringing us to stage 3./4./5./6. Please start upgrading your existing MNs to DIP3 (using the new protx commands)

Testnet was succesfully downgraded to v0.12.3.4 and reset to block 4000 (we're already at 6582 now). All MN features have been tested and all looks good so far. We have just published v0.13.0-RC9, which is also compatible to the new testnet. Please upgrade nodes to this RC and keep testing...

UPDATE: We've reset testnet to block 4000 and have already spinned up about 60 MNs on the new testnet. The old testnet is still there and mining continues for some time to give integration partners more time to switch to the new testnet. However, the old testnet doesn't have enough MNs anymore...

RC8 is pretty stable atm. RC9 is in preparation and mostly contains fixes for miners. RC9 will also include a reset of testnet to block 4000+, which will allow us to re-test everything. We're currently preparing everything for this and will properly announce this later today, together with...

RC8 has been published: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc8 It contains a few crash fixes. Please upgrade ASAP. If you don't upgrade, your nodes will crash when we upgrade our miners. It also contains changes to the "dummy DKG" which is used to test simple PoSe on testnet...

Release RC7 has just been published: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc7 Please update MNs when you find time. After this update, proposal voting should work again. There is also an incompatible change that will later result in non-upgraded nodes to fork off, but we'll try...

We've enabled spork15 and it got activated on block 277730. We've entered stage 8 now and are running in full deterministic mode now :) We already foud a few issue which we'll fix in RC7, but testing can generally continue (except for proposal testing...)

RC6 has just been released: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc6 Please upgrade all your nodes. This will be the version for which we're going to activate spork15 to move into the next phase.

Looks like a crash on initial-sync slipped into RC5: https://github.com/dashpay/dash/issues/2507 If anyone seens his node crash on initial sync, revert to rc4 and let it sync past block 264000. Then stop syncing and continue with rc5. tMNs which were already synced when they upgraded are not...

RC5 has just been published: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc5 Please update ASAP, and if possible before we reach block 274000. This release includes an incompatible upgrade (a fork) that happens at exactly this block. If you don't upgrade fast enough, you'll be stuck...

v0.13.0.0-rc4 is ready for testnet: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc4 Please update your nodes. Testnet is getting better compared to the last days and syncing should be successful in most cases, as long as you have enough good (v13) peers. This release includes a new...

v0.13.0.0-rc3 has just been released. Please upgrade. To see if you're on the correct chain, call "getblockhash 264978" and verify that it returns " 00000000100625f33be83bc1cebe4087ebf521c5ddd860c3304ea73967473e2c". If it doesn't, try "reconsiderblock...

Can we reduce discussion in this thread to v13/testnet related stuff? If you want answers for your questions, I'd suggest to ask in Discord or make a fresh forum post (ping me as I'm not watching new threads) Back to v13 :) @strophy and @thephez just finished the first version of the DIP3...

For your information, we reached stage 4. yesterday, which means we are in compatibility mode. There is already one DIP3 MN registered (I'm the first one, yeah :D) Testnet was in a pretty bad state yesterday as the BIP9 deployment activated earlier then we hoped. One large miner was still...