From: Angel Leon <gubatron@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] [QT] how to disable block verification for faster UI testing?
Date: Wed, 19 Mar 2014 13:27:08 -0400 [thread overview]
Message-ID: <CADZB0_aSpu7v0bVV6Po0RonobGVreWTLN7Mya687PbP2t_-oZg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
the command line options mention a -checklevel parameter.
I've been passing 0 assuming there'd be little to no verification, but it's
happened a few times that when I open the official binary (while not doing
development) there's some sort of database corruption and Bitcoin-Qt needs
to reindex blocks on disk, a process that can take probably a whole day.
how do you guys develop the UI and avoid these issues?
Cheers,
Angel
http://twitter.com/gubatron
[-- Attachment #2: Type: text/html, Size: 611 bytes --]
next reply other threads:[~2014-03-19 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 17:27 Angel Leon [this message]
2014-03-19 18:22 ` [Bitcoin-development] [QT] how to disable block verification for faster UI testing? Wladimir
2014-03-19 18:36 ` Angel Leon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADZB0_aSpu7v0bVV6Po0RonobGVreWTLN7Mya687PbP2t_-oZg@mail.gmail.com \
--to=gubatron@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox