add brief Regtest description and link to setup #261
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#261
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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?
Thanks for opening this issue @binaryflesh. Definitely something we need to mention here/how it works/where to find setup instructions.
For review at https://github.com/lbryio/lbrycrd/tree/depends_build_all
merged.