# What options should I set for launching counterparty-lib?

**URL:** <https://forums.counterparty.io/t/what-options-should-i-set-for-launching-counterparty-lib/1375>\
**Category:** Counterparty\
**Created:** [August 3, 2015, 4:50am UTC](https://forums.counterparty.io/t/what-options-should-i-set-for-launching-counterparty-lib/1375 "2015-08-03T04:50:52Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [August 3, 2015, 4:35pm UTC](https://forums.counterparty.io/t/what-options-should-i-set-for-launching-counterparty-lib/1375/7 "2015-08-03T16:35:44Z")

</div>

Hi Zono,

- You can change the parameters as per Sqlite docs (stop counterparty-server, use Sqlite CLI to change config parameters)
- PRAGMA\_CHECK maybe can be replaced with PRAGMA\_QUICK\_CHECK ([https://www.sqlite.org/pragma.html#pragma\_quick\_check](https://www.sqlite.org/pragma.html#pragma_quick_check)), but it’s not something that we test. I think this check runs only rarely, for example when the DB is first deployed (if you use `counterparty-server bootstrap`, for example). I don’t find it time consuming (yes, sometimes it runs for 10+ mins, but if you normally shutdown counterparty-server (using CTRL+C), it takes only 1-2 mins at startup, in my experience). I use the top command to watch if counterparty-server is stuck or active - if it’s “working”, then I just wait. The longest check I’ve seen was around 30 mins, when the entire DB had to be checked on a slow PC.

Did you use [bootstrap/download the Counterparty DB](https://forums.counterparty.io/t/how-do-i-get-started-developing-on-counterparty/1198), or did you let it catch up naturally?

Normally for test/dev environments it’s better to use testnet because DB is smaller and the wait is shorter, then do final testing on mainnet. Or point your counterparty-client to public Counterparty server (e.g. CoinDaddy’s servers) while the DB is catching up / checking consistency (create a different config file and use `counterparty-client --config-file coindaddy.server.conf getinfo` - a detailed example of using CoinDaddy’s Counterparty server can be found [here](https://forums.counterparty.io/t/counterparty-client-testnet-on-raspbian/1321))

---

_[View the full topic](https://forums.counterparty.io/t/what-options-should-i-set-for-launching-counterparty-lib/1375)._