8000 set error correction level to low for qr codes by antonilol · Pull Request #1952 · mempool/mempool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

set error correction level to low for qr codes #1952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 6, 2022
Merged

Conversation

antonilol
Copy link
Contributor

fixes #1807

i first thought that alphanumeric mode wasnt used/supported but the npm package supports it and segwit addresses are converted to uppercase (btw regtest addresses weren't, fixed that too)

error correction was set to high, which is causing the large qrcodes, in my opinion it is not needed as low is good enough and bech32 has error correction

qrcodes before were very pixely on my screen (because of scaling some qrcode pixels were larger than other)
with smaller qrcodes this will be smoother and less pixely

@katesalazar does this fix your issue?

@katesalazar
Copy link
katesalazar commented Jul 3, 2022 via email

@katesalazar
Copy link
katesalazar commented Jul 3, 2022 via email

@antonilol
Copy link
Contributor Author

what about lowering qr error correction but only for base32 keeping base58 with high qr error correction funds should be safu

oh i said bech32 has error correction, but base58 can still detect error (with sha256)
(both have error detection, only bech32 has correction)

qr code error detection is useful when printed on a piece of paper, where some ink can get vague, but in the mempool case it is a screen where the code gets displayed on, for possible dead pixels on screens low error correction is fine

@katesalazar
Copy link

I printed an address page and it looked kinda horrible
but was usable enough

somewhere someone will use it as a paper wallet,
surely they deserve high error correction

@antonilol
Copy link
Contributor Author

I printed an address page and it looked kinda horrible but was usable enough

lol

somewhere someone will use it as a paper wallet, surely they deserve high error correction

dont think so, there are website for that that give nice printable things that also have a private key

but a button (or clicking the qr) could be added to scale up the qr (for better scanning) and/or increase error correction level

@katesalazar
Copy link

users will commit mistake
resistance is futile

I think it's a good idea allowing different error correction triggered by user, yeah

Copy link
Member
@wiz wiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested ACK @ v2.4.1-dev [98db8b1b]

@wiz wiz merged commit 3424bb9 into mempool:master Jul 6, 2022
@antonilol antonilol deleted the qrcodes branch July 8, 2022 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

qr code optimization
3 participants
0