Why does the decode function of the segwit bech32 encoder/decoder take a hrp (human readable part) as input?
Looking at the code referenced in bip-0173, specifically for example here:
https://github.com/sipa/bech32/blob/master/ref/javascript/segwit_addr.js
function decode (hrp, addr) {
var dec = bech32.decode(addr);
if (dec === null || dec.hrp !== hrp || dec.data.length < 1 || dec.data[0] > 16) {
return null;
}
...
I understand that this is an error checking statement, but why check a (user?) inputted hrp vs the decoded hrp from bech32.decode?
Also I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
segregated-witness bech32-address
asked 2 hours ago
kawthuldrokkawthuldrok
467
add a comment |
Looking at the code referenced in bip-0173, specifically for example here:
https://github.com/sipa/bech32/blob/master/ref/javascript/segwit_addr.js
function decode (hrp, addr) {
var dec = bech32.decode(addr);
if (dec === null || dec.hrp !== hrp || dec.data.length < 1 || dec.data[0] > 16) {
return null;
}
...
I understand that this is an error checking statement, but why check a (user?) inputted hrp vs the decoded hrp from bech32.decode?
Also I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
segregated-witness bech32-address
asked 2 hours ago
kawthuldrokkawthuldrok
467
add a comment |
Looking at the code referenced in bip-0173, specifically for example here:
https://github.com/sipa/bech32/blob/master/ref/javascript/segwit_addr.js
function decode (hrp, addr) {
var dec = bech32.decode(addr);
if (dec === null || dec.hrp !== hrp || dec.data.length < 1 || dec.data[0] > 16) {
return null;
}
...
I understand that this is an error checking statement, but why check a (user?) inputted hrp vs the decoded hrp from bech32.decode?
Also I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
segregated-witness bech32-address
asked 2 hours ago
kawthuldrokkawthuldrok
467
Looking at the code referenced in bip-0173, specifically for example here:
https://github.com/sipa/bech32/blob/master/ref/javascript/segwit_addr.js
function decode (hrp, addr) {
var dec = bech32.decode(addr);
if (dec === null || dec.hrp !== hrp || dec.data.length < 1 || dec.data[0] > 16) {
return null;
}
...
I understand that this is an error checking statement, but why check a (user?) inputted hrp vs the decoded hrp from bech32.decode?
Also I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
segregated-witness bech32-address
segregated-witness bech32-address
asked 2 hours ago
kawthuldrokkawthuldrok
467
asked 2 hours ago
kawthuldrokkawthuldrok
467
asked 2 hours ago
kawthuldrokkawthuldrok
467
asked 2 hours ago
kawthuldrokkawthuldrok
467
asked 2 hours ago
kawthuldrokkawthuldrok
467
467
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The HRP is part of the bech32 encoded string, and in the bech32 decoding API, it is returned along with the payload by the decoder, after checking the checksum.
We still want to compare it with the expected HRP in BIP173, which encodes the chain the software is operating on.
Otherwise you could have a testnet node that accepts mainnet BIP173 addresses or the other way around.
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
add a comment |
I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
No, it's because only versions 0 - 16 are specified. Other versions might behave entirely differently. (As an aside, if it were a comparison for the sake of clamping to the range of a single hex character the test would be >15 not >16).
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "308"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f83454%2fwhy-does-the-decode-function-of-the-segwit-bech32-encoder-decoder-take-a-hrp-hu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The HRP is part of the bech32 encoded string, and in the bech32 decoding API, it is returned along with the payload by the decoder, after checking the checksum.
We still want to compare it with the expected HRP in BIP173, which encodes the chain the software is operating on.
Otherwise you could have a testnet node that accepts mainnet BIP173 addresses or the other way around.
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
add a comment |
The HRP is part of the bech32 encoded string, and in the bech32 decoding API, it is returned along with the payload by the decoder, after checking the checksum.
We still want to compare it with the expected HRP in BIP173, which encodes the chain the software is operating on.
Otherwise you could have a testnet node that accepts mainnet BIP173 addresses or the other way around.
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
add a comment |
The HRP is part of the bech32 encoded string, and in the bech32 decoding API, it is returned along with the payload by the decoder, after checking the checksum.
We still want to compare it with the expected HRP in BIP173, which encodes the chain the software is operating on.
Otherwise you could have a testnet node that accepts mainnet BIP173 addresses or the other way around.
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
The HRP is part of the bech32 encoded string, and in the bech32 decoding API, it is returned along with the payload by the decoder, after checking the checksum.
We still want to compare it with the expected HRP in BIP173, which encodes the chain the software is operating on.
Otherwise you could have a testnet node that accepts mainnet BIP173 addresses or the other way around.
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
answered 2 hours ago
Pieter WuillePieter Wuille
45.6k393154
45.6k393154
add a comment |
add a comment |
I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
No, it's because only versions 0 - 16 are specified. Other versions might behave entirely differently. (As an aside, if it were a comparison for the sake of clamping to the range of a single hex character the test would be >15 not >16).
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
add a comment |
I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
No, it's because only versions 0 - 16 are specified. Other versions might behave entirely differently. (As an aside, if it were a comparison for the sake of clamping to the range of a single hex character the test would be >15 not >16).
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
add a comment |
I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
No, it's because only versions 0 - 16 are specified. Other versions might behave entirely differently. (As an aside, if it were a comparison for the sake of clamping to the range of a single hex character the test would be >15 not >16).
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
I'm assuming that the "dec.data[0] > 16" check is to make sure that the byte at index zero doesn't exceed a value of 16, which would be invalid hex. Is this correct?
No, it's because only versions 0 - 16 are specified. Other versions might behave entirely differently. (As an aside, if it were a comparison for the sake of clamping to the range of a single hex character the test would be >15 not >16).
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
answered 1 hour ago
G. MaxwellG. Maxwell
3,3821630
3,3821630
add a comment |
add a comment |
Thanks for contributing an answer to Bitcoin Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f83454%2fwhy-does-the-decode-function-of-the-segwit-bech32-encoder-decoder-take-a-hrp-hu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
