Do not create transactions with incorrect claims #192
No reviewers
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#192
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "verify_claimid"
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?
Signed-off-by: Anthony Fieroni bvbfan@abv.bg
https://github.com/lbryio/lbrycrd/issues/116
@ -426,6 +426,10 @@ UniValue claimname(const UniValue& params, bool fHelp)
);
while it is unintuitive, an empty claim name is actually valid (you can make claim for empty names when you use double quotes: "" in the RPC claimname command) so this check is not needed
@ -849,2 +860,4 @@
string sName = params[0].get_str();
string sClaimId = params[1].get_str();
const size_t claimLength = 40;
same here
@ -849,2 +860,4 @@
string sName = params[0].get_str();
string sClaimId = params[1].get_str();
const size_t claimLength = 40;
There is actually a function created to check claimId here:
https://github.com/lbryio/lbrycrd/blob/master/src/rpc/claimtrie.cpp#L10
@ -536,1 +544,4 @@
{
if (op == OP_SUPPORT_CLAIM)
continue;
good catch.. I think this would have been problematic if the decoded claim script was a support...
rpc/claimtrie.cpp is a part of libbitcoin_server while rpcwallet of libbitcoin_wallet that's why i'm including only 2 checks from ParseClaimtrieId not compete one.
Please fix the travis issue.
"value must be hexadecimal" or something like that is a fine description (typos above: contains, hexdecimal, also omit the omit warning)
Same as above, just a wording difference/typo fix.
Reverse these (non-standard style otherwise)
Since 40 is not declared as a fixed constexpr, but used as a fixed constexpr, either declare it as something const (not constexpr since not C++11) and use that, or just change this to something like:
Fix addressed issues.
Mac build looks broken again.
Untested, but looks good to me, pending a travis build fix.
I'll leave this on 'request changes' instead of 'approve' until the travis issue is resolved.
Rebase off master again and the OSX build will be fixed.
Done