add brief Regtest description and link to setup #261

Closed
opened 2019-03-19 15:50:05 +01:00 by binaryflesh · 3 comments
binaryflesh commented 2019-03-19 15:50:05 +01:00 (Migrated from github.com)

As a new user coming from the infosec side of things, 'regtest' is usually an alias to fuzzing. While writing a binding to the API, I was under impression to use testnet with my code and I thought '-regtest' was mainly an internal feature for developers on lbrycrd. Could there be mention of ideal developer setup in the readme?

As a new user coming from the infosec side of things, 'regtest' is usually an alias to [fuzzing](https://en.wikipedia.org/wiki/Fuzzing). While writing a binding to the API, I was under impression to use testnet with my code and I thought '-regtest' was mainly an internal feature for developers on lbrycrd. Could there be mention of [ideal developer setup](https://lbry.tech/resources/regtest-setup) in the readme?
tzarebczan commented 2019-03-19 18:09:29 +01:00 (Migrated from github.com)

Thanks for opening this issue @binaryflesh. Definitely something we need to mention here/how it works/where to find setup instructions.

Thanks for opening this issue @binaryflesh. Definitely something we need to mention here/how it works/where to find setup instructions.
BrannonKing commented 2019-06-06 19:54:19 +02:00 (Migrated from github.com)
For review at https://github.com/lbryio/lbrycrd/tree/depends_build_all
BrannonKing commented 2019-06-17 23:51:57 +02:00 (Migrated from github.com)

merged.

merged.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#261
No description provided.