Search results

Old testenet was very fragmented (lots of masternodes we don't control which were running different 12.2 versions), so we abandoned the it and forked to a new one to start with clean 12.1 and test migration to 12.2 properly, from start to finish. Once we are done with that, we'll publish the...

Ok, you almost got it anyway, so I'm going to tell you the last bit of the picture that is missing - Evan is a reptiloid and he controls state agents via telepathy, so they don't even realize. Now you can go write a book and make millions selling it. Don't thank me :D

Thanks, included fi in PR. We are offtopic here for way too long already ;) let's move this to https://www.dash.org/forum/threads/12-2-translations.17122/

We are approaching final stages of testing 12.2, so vast majority of text strings is most likely not going to change a lot. Which means we can safely start translations without worrying about doing the same work twice, so I welcome all translators registered on transifex to jump in and bump...

@Bertrand256 ^^^

Took me longer than I expected exactly because of the reasons why I hate it - some packages for python scripts were missing and I broke my env trying to fix it.. Anyway, en source should be more or less up to date on transifex now :) Note/reminder to everyone translating strings: - please keep...

It's hard to tell. That fix would include protocol bump to get some idea of update progress which would mean that everyone would have to update and moreover, MNs would have to be restarted losing their place in the payment queue.. which is quite of a disincentive. Generally speaking, that would...

The roadmap was put together before IS issue was even discovered and it took a lot of time to find a proper way to fix it (initially we had another fix prepared btw). Anyway, all major tickets for 12.2 are closed now and everything (2mb blocks, lower fees, IS fix, and a whole bunch of internal...

There were 2 major fixes: https://github.com/dashpay/dash/pull/1592 https://github.com/dashpay/dash/pull/1620 and few smaller followups/cleanups later. Due to the nature of the vulnerability/fix we can't just apply it on the live network and we have to wait for 12.2 to activate it via...

Спасибо за тестирование в продакшене, конечно, но зачем? Релиз же еще не объявляли... Если не хотите майнить невалидные блоки, то я бы рекомендовал откатить до стабильной 0.12.1.5.

Yes we are aware. But as it was mentioned in the video, to prepare an attack like that one would require millions of $$ spent in fees, so it's more of a theoretical one. With this in mind, we do not plan to address this in initial 12.2 release as this would require backporting way too much of...

Look, I understand your frustration and I was letting you to express yourself in this thread for some time even though it was slightly offtopic. But @iBeLink_1 has a legit point as well, so pls stay on topic (tech issues) and keep this thread clean. You can either start a new thread if you want...

I have no idea, posted this in evo dapi channel, let's see. On a side note - there is no mentions of bitcoin in Payment API description but it mentions visa and mastercard as payment methods. Not sure why anyone would be so excited about it :)

Ooops, missed this thread earlier somehow. We are going to fix as much issues/bugs as possible as always but we are aiming to get consensus/protocol critical things right first and test/release 12.2 asap. Going to fix low priority issues as time allows in minor releases probably.

Most of the time errors like that are caused by some antivirus software which puts blockchain .dat files into quarantine. You should add dash datadir folder into exceptions/ignore list in antivirus settings to prevent this error from re-appearing in the future.

Site is up but stuck at 717522 ...

Yep, replies work :)

I got no alerts or anything. All checkboxes in "Alert settings" are on btw.

@newmz @aleix Try running wallet with `-resetguisettings` cmd-line flag