#

issuecomment

(13 articles)

Silent Payments Bitcoin   

Trechos do artigo do seth for Privacy COMO FUNCIONAM OS PAGAMENTOS SILENCIOSOS, SIMPLIFICADOS Antes de nos aprofundarmos no motivo pelo qual estou entusiasmado com os Pagamentos Silenciosos, é importante que você entenda em um nível muito simplista como os Pagamentos Silenciosos funcionam tanto para o remetente quanto para o destinatário. PARA O REMETENTE Quando alguém deseja enviar fundos para um endereço de pagamento silencioso, na prática, tudo o que precisa fazer é digitalizar ou copiar/colar o código de pagamento em sua carteira favorita (supondo que seja compatível) e enviar o pagamento normalmente. Mas o que exatamente está acontecendo nos bastidores? Quando o remetente insere o endereço de Pagamento Silencioso em sua carteira, sua carteira combina três chaves para criar um endereço único e único, do qual apenas o destinatário pretendido pode gastar. Esse endereço exclusivo é criado combinando a chave pública (ou “endereço”, em termos leigos) de uma das entradas que o remetente deseja passar para o destinatário, a chave pública do destinatário (contida no endereço de pagamento silencioso), e uma chave “segredo compartilhado” que o remetente gera e que apenas o remetente e o destinatário conhecem. Graças a algo conhecido como propriedade “comutativa” na criptografia, o remetente pode combinar essas chaves, mas não pode gastar do endereço resultante , pois não conhece a chave privada do destinatário (é claro). Quando o remetente combina essas três chaves, ele gera uma nova chave pública (ou endereço) e envia os fundos pretendidos para esse novo endereço que somente o destinatário controla. Na cadeia, esta transação se parece exatamente com qualquer outro gasto de tipo e script semelhantes, e não há nenhum fator distintivo que torne aparente para observadores externos que um Pagamento Silencioso foi usado, muito menos quem possui o endereço de Pagamento Silencioso. PARA O DESTINATÁRIO Assim que chegarmos ao destinatário, veremos onde entra a principal desvantagem dos pagamentos silenciosos. Se você se lembra de que o remetente usa a chave pública de uma entrada que está sendo gasta para gerar o endereço único e único, pode estar se perguntando: “Como o destinatário sabe que recebeu fundos e para qual endereço?” Esta questão está no centro da proposta de pagamentos silenciosos e significa que os destinatários precisam fazer uma varredura relativamente cara de todas as transações na blockchain do Bitcoin depois de criarem seu endereço de pagamento silencioso. Essa varredura permite que o destinatário veja se uma chave pública de entrada mais um segredo compartilhado gerado usando seu endereço de pagamento silencioso e uma chave pública de saída em qualquer transação corresponde adequadamente às suas chaves privadas e, se for o caso, adicioná-la à carteira. Essa varredura é bastante cara em comparação com a varredura de carteira Bitcoin padrão, pois você não pode simplesmente comparar uma lista de endereços derivados de sua carteira com uma lista de saídas de transações para obter o saldo de sua carteira. Em vez disso, você precisa passar por cada transação, calcular o segredo compartilhado para cada entrada e comparar com as saídas, algo que Somsen comparou a “verificar cada assinatura duas vezes, em vez de uma vez” em “Bitcoin Explained ” . Idealmente, essa varredura será feita durante o download do bloco inicial (a primeira vez que você sincronizar todo o blockchain do Bitcoin) ou um software autônomo que descarregue a varredura de sua carteira e nó Bitcoin. OTIMIZANDO O TEMPO DE DIGITALIZAÇÃO PARA O DESTINATÁRIO Embora essa varredura seja computacionalmente cara, ela pode se tornar mais eficiente sem sacrificar a privacidade ou a fungibilidade por meio de três otimizações principais: 1. Crie uma data de “aniversário” ao criar um endereço de pagamento silencioso e salve-o, para que, quando precisar restaurar, você possa começar a digitalizar apenas a partir desse bloco adiante na cadeia, em vez do bloco de gênese. 2. Verifique apenas as saídas Taproot, pois muito poucas saídas na cadeia são atualmente Pay-to-Taproot (“ P2TR ”), isso eliminará uma grande porcentagem de transações e reduzirá bastante o tempo de verificação. Idealmente, isso se tornará menos útil à medida que o Taproot for mais usado, mas provavelmente será uma otimização extremamente eficaz por algum tempo. 3.Verifique apenas o conjunto UTXO em vez de verificar todas as transações históricas, pois você está preocupado apenas com saídas novas, recebidas e não gastas destinadas ao seu endereço de pagamento silencioso. Isso tem a desvantagem de não fornecer histórico de transações e exigiria um banco de dados adicional sobre os métodos normais. Artigos sobre Silent Payments 🤫 https://bitcoinmagazine.com/technical/silent-payments-make-bitcoin-more-private https://bitcoinmagazine.com/technical/silent-payments-improve-privacy-without-bitcoin-data https://bitcoinmagazine.com/technical/bitcoin-silent-payments-secret-keys https://bitcoinmagazine.com/technical/improving-bitcoin-privacy-with-silent-payments https://foundationdevices.com/2023/02/making-sense-of-stealth-addresses/ Videos sobre Silent Payments 🤫 https://youtu.be/vOCWO_zX7X8 https://youtu.be/42PMLaz7Avk https://youtu.be/YCMaqS-LhLc Space sobre Silent Payments 🤫 https://twitter.com/bitcoinoptech/status/1668949342814609408?t=UY6nEc0ghPiPxgfydUzW6w&s=19 Recompensa pra carteira mobile suporte ao Silent Payments 🤫 https://twitter.com/gladstein/status/1684567103297445888?t=tY6WQ8fzPn3vNs_YrvXDmQ&s=19 BIP 352 Silent Payments 🤫 https://github.com/bitcoin/bips/pull/1458#issuecomment-1613507274

Issues opened for WalletScrutiny ...

At WalletScrutiny we open a lot of issues. And just recently, Danny, whom I cannot mention on Habla.news due to [this error](https://github.com/verbiricha/habla.news/issues/171) wrote a script to facilitate re-visiting issues we haven't re-visited in over half a year. Should we poke them all? 🤔 Issue | Comment | Issue -----------|------------|---------------------- 2019-12-14 | 2019-12-16 | [App cannot be verified](https://github.com/EdgeApp/airbitz-android-gui/issues/21) 2017-10-20 | 2020-04-11 | [Builds are not reproducible](https://github.com/lightninglabs/lightning-app/issues/67) 2019-12-14 | 2020-06-19 | [App from GooglePlay is not verifiable](https://github.com/BlueWallet/BlueWallet/issues/758) 2020-08-27 | 2020-09-02 | [Please provide full build instructions to reproduce the app on Google Play](https://github.com/OpenBazaar/haven/issues/3) 2020-12-05 | 2020-12-14 | [Provide build instructions to rebuild the app from Google Play](https://github.com/jdogresorg/freewallet-mobile/issues/34) 2020-12-16 | 2020-12-16 | [Where is the code of DApp Browser?](https://github.com/TP-Lab/tp-ios/issues/1) 2020-12-18 | 2021-01-02 | [Reproducible builds of com.crypto.multiwallet on Google Play?](https://github.com/guardaco/guarda-android-wallets/issues/42) 2021-03-06 | 2021-03-07 | [Change minSdkVersion from 16 to 19](https://github.com/coincasso/ccwallet/issues/1) 2017-12-20 | 2021-03-12 | [Build APK deterministically](https://github.com/Bitcoin-com/Wallet/issues/39) 2021-03-05 | 2021-04-03 | [Please update your build instruction and make sure the app on Google Play can be reproduced](https://github.com/bither/bither-android/issues/69) 2019-12-28 | 2021-04-03 | [Please update your build instructions such that reproducible builds are possible](https://github.com/hodlwallet/hodl-wallet-android/issues/50) 2021-04-09 | 2021-04-09 | [Please provide detailled instructions on how to reproduce the app on Google Play](https://github.com/HODLERTECH/HODLER-Open-Source-Multi-Asset-Wallet/issues/165) 2021-03-07 | 2021-04-20 | [Missing build instructions & build fail](https://github.com/blockchaingate/exchangily-mobile-app/issues/1) 2021-03-08 | 2021-04-22 | [Build fail with errors "Error: No named parameter with the name"](https://github.com/AniketSindhu/My_Paper_Crypto_Wallet/issues/1) 2021-04-23 | 2021-04-23 | [Where is the latest source-code for im.token.app?](https://github.com/consenlabs/token-core/issues/97) 2021-03-12 | 2021-05-02 | [Missing code for latest 2.1 version in google-play](https://github.com/Lunes-platform/Wallet-mobile/issues/9) 2021-04-01 | 2021-05-02 | [Publish source code for the app](https://github.com/neogeno/shango-lightning-wallet/issues/84) 2021-05-03 | 2021-05-04 | [Please provide build instructions for reproducing the apk from Google Play](https://github.com/bitcoin-dot-org/BitcoinWalletMobile/issues/7) 2020-04-07 | 2021-05-16 | [Please provide verifiability of released builds](https://github.com/COINiD/COINiDVault/issues/14) 2021-04-18 | 2021-05-19 | [Where is the latest code and build instructions](https://github.com/TP-Lab/tp-android/issues/15) 2021-05-27 | 2021-05-27 | [Missing code for latest release 3.2.7 on google-play](https://github.com/coinninjadev/dropbit-android/issues/2) 2020-01-29 | 2021-06-02 | [Please provide verifiable builds](https://github.com/COINiD/COINiDWallet/issues/24) 2019-12-22 | 2021-06-03 | [Failed to verify the build on GooglePlay](https://github.com/ACINQ/eclair-mobile/issues/232) 2021-05-27 | 2021-06-08 | [Android app is not reproducible, diffs in AndroidManifest.xml & 0.dist.js & dist.js & resources.arsc files](https://github.com/monya-wallet/monya/issues/130) 2020-06-01 | 2021-07-23 | [Please make the app reproducible](https://github.com/ValleZ/Paper-Wallet/issues/42) 2021-10-26 | 2021-12-02 | [Publish sources for android mobile appid=`io.divipay.divi`](https://github.com/DiviProject/Divi-Desktop-Public/issues/214) 2021-12-11 | 2021-12-11 | [Please provide latest source code and reproducible builds](https://github.com/hyperpayorg/hardwallet/issues/4) 2021-12-20 | 2021-12-20 | [Please share the source and build instructions for the QUANTUM HW firmware](https://github.com/SecurityArts/QuantumManager/issues/14) 2022-02-08 | 2022-02-08 | [Please add interpretation of transactions due to be signed](https://github.com/arcbtc/bowser-bitcoin-hardware-wallet/issues/13) 2021-10-17 | 2022-03-12 | [Please provide build instructions to reproduce the version on Google Play Store](https://github.com/bitriel/bitriel-wallet/issues/26) 2021-12-02 | 2022-03-14 | [Please provide instructions to reproduce your app found on Google Play](https://github.com/rsksmart/rwallet/issues/726) 2021-04-21 | 2022-03-27 | [Minimal Containers for Reproducible Builds testing for android app - WIP](https://github.com/hsjoberg/blixt-wallet/issues/318) 2019-11-23 | 2022-03-28 | [Build is not verifiable](https://github.com/hoanghiephui/Bitcoin-Wallet/issues/15) 2022-03-15 | 2022-04-10 | [Show hash of firmware prior to installation](https://github.com/prokey-io/prokey-optimum-firmware/issues/28) 2021-04-12 | 2022-04-12 | [Please provide build instructions to reproduce the app in Google Play Store](https://github.com/atomex-me/atomex.mobile/issues/24) 2020-04-27 | 2022-04-14 | [Please provide reproducible builds](https://github.com/melis-wallet/melis-cm-client/issues/1) 2022-04-08 | 2022-04-16 | [Why the wallet readme is not detailed and no updated description?](https://github.com/SalletOne/sallet-one-cold/issues/6) 2021-07-17 | 2022-07-22 | [Publish source-code of releases before uploading them to Google Play](https://github.com/blockchain/My-Wallet-V3-Android/issues/1294) 2021-12-01 | 2022-08-07 | [Reproducible build fails due to a missing dependency](https://github.com/shesek/spark-wallet/issues/192) 2021-02-14 | 2022-08-29 | [Build failed if --production or npm ci are used instead of development](https://github.com/ZeusLN/zeus/issues/416) 2022-03-01 | 2023-01-06 | [Publish source code for mobile apps](https://github.com/nunchuk-io/nunchuk-mobile-issues/issues/5) 2021-10-16 | 2023-04-13 | [Missing Code for latest versions on google-play](https://github.com/QuarkChain/QPocket-Android/issues/2) 2023-04-15 | 2023-04-15 | [Missing Git Tag & Github release for latest version 5.5.1 on Google Play](https://github.com/particl/copay/issues/58) 2022-08-04 | 2023-04-20 | [Add build instructions for all platforms & Containerfiles to compile app](https://github.com/coffee-software/coffee.wallet/issues/89) 2021-11-23 | 2023-04-22 | [Missing source code for latest version 4.18](https://github.com/breadwallet/brd-mobile/issues/13) 2021-03-12 | 2023-04-23 | [Build apk fail with "because bitorzo_wallet_flutter depends on intl ^0.16.0, version solving failed."](https://github.com/Bitorzo/Bitorzo/issues/2) 2019-12-14 | 2023-04-24 | [App on Google Play is not verifiable](https://github.com/CoinSpace/CoinSpace/issues/30) 2023-04-24 | 2023-04-24 | [Publish code for newer version 23 on google-play](https://github.com/inbitcoin/altana-android/issues/5) 2023-04-27 | 2023-04-28 | [Reproducibility problem on v0.32.0](https://github.com/horizontalsystems/unstoppable-wallet-android/issues/6071) 2022-07-12 | 2023-05-25 | [Missing code for version 1.3.11 on google-play](https://github.com/coingrig/coingrig-wallet/issues/22) 2023-05-27 | 2023-05-27 | [reproducible builds](https://github.com/OneKeyHQ/firmware/issues/404#issuecomment-1633287406) 2023-06-20 | 2023-06-21 | [Use `--output-hashing none` to prevent random names for built main.js](https://github.com/airgap-it/airgap-vault/issues/197) 2023-06-25 | 2023-06-25 | [The app is not reproducible](https://github.com/nunchuk-io/nunchuk-android/issues/23) 2023-02-21 | 2023-07-01 | [Could not find com.google.android.gms:play-services-tapandpay:18.2.0](https://github.com/bitpay/bitpay-app/issues/686) 2021-10-09 | 2023-07-08 | [Please fix build reproducibility](https://github.com/muun/apollo/issues/54) 2023-05-22 | 2023-07-13 | [v7.8.0 is not reproducible](https://github.com/keepkey/keepkey-firmware/issues/342) 2021-10-17 | 2023-07-31 | [Missing x86_64 folder in ./app/src/main/cpp/*/lib with lib*.a files & Instructions to reproduce binaries in lib folders](https://github.com/MixinNetwork/android-app/issues/2559) 2021-01-21 | 2023-08-16 | [How can I verify the app on Google Play was built from this source code?](https://github.com/bithyve/hexa/issues/2544) 2019-12-28 | 2023-09-30 | [Please provide verifiable builds](https://github.com/trustee-wallet/trusteeWallet/issues/1) 2019-12-14 | 2023-11-02 | [App on Google Play can't be verified](https://github.com/EdgeApp/edge-react-gui/issues/1748) 2019-12-30 | 2023-11-03 | [Support verifiable builds](https://github.com/breez/breezmobile/issues/247) 2021-02-21 | 2023-12-19 | [Has the BitLox project died?](https://github.com/BitLox/bitlox-firmware/issues/3)