Bitcoin Forum
June 30, 2024, 04:20:46 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 [221] 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 ... 463 »
4401  Bitcoin / Development & Technical Discussion / Re: Multisig with Time Lock? on: June 01, 2022, 12:57:11 PM
You can do this with 3-of-3 multi-sig, not 2-of-3. In the former, you need their approval to spend and so do they. In the latter, they can gain access to your coins and don't need your approval to spend, something you've said you don't want.

You also can time lock money to yourself, to avoid messing with intermediaries, but that's once and for all; you can't reverse it, in contrast with multi-sig wherein you can convince your friends to get the money.



An even better solution is to look after your emotions.
4402  Bitcoin / Development & Technical Discussion / Re: [Guide] How to run a Bitcoin Core full node for under 50 bucks! on: June 01, 2022, 10:31:50 AM
[...]
Your database is likely corrupted. Try wiping out the block index with bitcoin-qt -reindex. This will re-make the database by going all over the blk.dat files, re-validate them and rebuilding the chainstate. It'll take a lot of time.

Have you checked your debug.log for further info?
4403  Bitcoin / Development & Technical Discussion / Re: Thoughts on burner addresses on: June 01, 2022, 10:05:05 AM
The other coins that you get for the "burned" coins can't benefit in any way
But, they supposedly do benefit in some other way. That's why altcoins exist. They supposedly do something bitcoin can't do, and a mechanism to prevent double-spending is Proof-of-Burn.

It's similar to throwing a coin into an unreachable space, it's lost forever.
That's a bad analogy, because you can't prove you've burnt it, and burning bitcoin makes sense only if you're able to prove it.

Note that sending coins to perfectly valid addresses, such as 1Counterparty, doesn't necessarily mean they're removed from circulation. There are more than 79 octillion private keys, on average, that can unlock these outputs.

For provably burning, use OP_RETURN.

I can see the argument that you really want to burn the coins to make bitcoin more scarce but in my opinion the amounts are way to little for it to have an impact on the network.
1Counterparty currently has 2,130.96 BTC. That's 0.01% of the total circulation. It does have a little impact, and that's just from counter party.
4404  Bitcoin / Development & Technical Discussion / Re: Thoughts on burner addresses on: June 01, 2022, 09:18:47 AM
I researched it and I found out that it is used as a proof of burn address.
Where is it used as a Proof of Burn? I only know 1Counterparty[1][2] that does it.

In my opinion it does not make sense, since the value is destroyed and not transferred to the other project even if it might seem like it in the first place.
It does make sense. The value is destroyed from the Bitcoin network, but that's the condition for the other coin to create circulation. You can't have as much as you want, because you can't fake your bitcoin's burning, nor can you double-spend. It's a brand new coin that depends on bitcoin.

What doesn't make sense is to buy it.  Smiley

Also there could be an option built into the bitcoin network to burn coins, but actually insert them into blocks to be redistributed to the miners.
Transaction fees!  Wink



[1] https://counterparty.io/get-started/
[2] https://mempool.space/address/1CounterpartyXXXXXXXXXXXXXXXUWLpVr
4405  Bitcoin / Development & Technical Discussion / Re: Silent payments on: June 01, 2022, 08:50:51 AM
Yes! That was it.

but can't I just attack Alice by pre-generating billions of addresses using her server and tracking all incoming donations?
You can't track her donations, because the address you will generate won't be shown to anyone else. Once an address is shown, it's never used again. You can of course attack her by generating billions of addresses, but that will only increase her children, and, therefore, make her monitoring more difficult. It's a similar problem to DDoS.
4406  Bitcoin / Development & Technical Discussion / Re: Silent payments on: June 01, 2022, 08:09:25 AM
Try it, use a mixer for your bitcoins and sell them on some exchange. Lots of exchanges blacklist bitcoins from mixers.
Then don't do business with people who treat bitcoin as non-fungible.

What if you have billions of page loads?
You don't have to generate a new address for each page load. Just have a "Donation here!" link; whoever wants to donate will click it. Definitely not billions, not even hundreds of thousands.

I haven't seen any website that shows a new Bitcoin address on each reload, which confirms to me it's not feasible.
I've seen it once, and it was for donations specifically. Can't remember the github.io page. Doesn't BTCPay Server give you a new address each time? Why don't you use that?
4407  Bitcoin / Development & Technical Discussion / Re: Silent payments on: June 01, 2022, 07:22:28 AM
Anyone who has your extended public key can see all your transactions, anyone who has your silent public key sees literally nothing. That is the difference.
Sure, but you're supposed to hide it, just as you hide your private keys. And if you don't trust your web hosting service, which is normal, you can make it contact with your home's server. Such as Pi <--> Web hosting' server <--> Sender

Either way, you need to run your own node and scan for every transaction.

Previously, Alice had one address with many outputs created by different senders
No, I mean the idea with the master public key. No address reuse.

Let me show you.
Code:
 With master public key:


┌───────────┐ m/84'/0'/0'/0/0     ┌────────────┐  bc1q8g4...fjyjy       ┌────────────┐
│ Home node │◄───────────────────►│   Server   │◄──────────────────────►│ Visitor #1 │
└───────────┘                     └────────────┘                        └────────────┘



┌───────────┐ m/84'/0'/0'/0/1     ┌────────────┐  bc1qeud...ccr6f       ┌────────────┐
│ Home node │◄───────────────────►│   Server   │◄──────────────────────►│ Visitor #2 │
└───────────┘                     └────────────┘                        └────────────┘



┌───────────┐ m/84'/0'/0'/0/2     ┌────────────┐  bc1qwzx...2dxz7       ┌────────────┐
│ Home node │◄───────────────────►│   Server   │◄──────────────────────►│ Visitor #3 │
└───────────┘                     └────────────┘                        └────────────┘


 Et cetera.

Code:
                                                  ┌────────────┐   03aae...ccdf7       ┌───────────────────┐
                                          ┌──────►│ Visitor #3 ├──────────────────────►│ Construct Address │
    With silent payments:                 │       └────────────┘                       └───────────────────┘
                                          │
                                          │
     ┌────────┐    02efa...e4da1          │       ┌────────────┐   03da2...64a2d       ┌───────────────────┐
     │ Server ├───────────────────────────┼──────►│ Visitor #2 ├──────────────────────►│ Construct Address │
     └───┬────┘                           │       └────────────┘                       └───────────────────┘
         │                                │
         │                                │
         │                                │       ┌────────────┐   02d80...239e1       ┌───────────────────┐
         │                                └──────►│ Visitor #3 ├──────────────────────►│ Construct Address │
         │                                        └────────────┘                       └───────────────────┘
         │
┌────────┴─────────┐
│ Scans the chain  │
└──────────────────┘

The result is the same. Alice has received donations in several addresses, that have no connection.

Advantage of silent payment would be if Alice receives many payments and cannot reply to senders.
She doesn't have to reply to anybody. Address generation can happen automatically.

It would be more interesting to hide sender, not receiver. Maybe silent payments together with help of miners can break connection with senders.
Use a mixer then, end of story. No need to complicate it with miners and coinbase transactions.
4408  Bitcoin / Development & Technical Discussion / Re: Silent payments on: June 01, 2022, 06:00:31 AM
Quoting part of the OP:
Therefore, that allows user A to receive payments on completely delinked addresses using only one public address.
Isn't this already happening? Well, not exactly with one public address, but with one master public key. You can create nearly unlimited addresses which aren't linked and there's neither interaction from the sender.

I still don't understand how silent payments improve anonymity. Doesn't Alice still have lots of outputs in different addresses? Didn't she have the same problem before?
4409  Economy / Economics / Re: What is the golden rule of investment? on: June 01, 2022, 05:21:47 AM
he is an investor hold Luna and he has also lost quite a bit because of Luna.
"Quite a bit"? The shitcoin did a -100%, he's lost every cent he put.

Through this story I want everyone to know 1 golden rule in investing is: never give financial advice to anyone
Just because your friend told them to buy a worthless, centralized, opaque, game theory failing shitcoin, it didn't mean they should; and even if they were convinced, your friend shouldn't give advice, not because he might hurt someone, but he may have no idea what the hell he's bought.
4410  Bitcoin / Bitcoin Discussion / Re: Strike and HRF posted three challenges with 1 BTC reward each on: May 31, 2022, 07:18:11 PM
Is it just me, or is Challenge 2 vague and confusing?
That.

What's the benefit of pegging your Lightning balance to USD? And how exactly is this supposed to work? Like, creating 1 L-USD for each 3,000 Lightning sats? Doesn't make any sense. Bitcoin is free money; a currency on its own. And so is USD. Whoever wants to switch, utilize trading.

Challenge 3: E-Cash

1 BTC to a FOSS non-custodial wallet that gives their users the option to enter into a (likely) custodial arrangement where Bitcoin can be sent to other users of that wallet using Chaumian e-cash. The arrangement should be such that the wallet administrators cannot know the identity of their users, their balances, or transaction histories. One suspects this would be a federated system, but all submissions will be considered.
Reminds me of something. What can have possibly happened to that old soul, nullius, I wonder.
4411  Other / Beginners & Help / Re: My Four (4) Tips On How I Handle Criticism on Bitcointalk Forum on: May 31, 2022, 06:24:54 PM
The thing I like about bitcointalk is that it only has constructive criticism, from what I've seen two years now. If you don't understand all this bitcoin terminology, just make an account here, that's what I did; I nearly knew a thing before. Now I know that I know nothing.  Smiley

There are lots of helpful folks. Stackexchange is also useful, but that's a little much for techie stuff only.
4412  Bitcoin / Development & Technical Discussion / Re: Silent payments on: May 31, 2022, 05:30:51 PM
If an attacker can change public keys, he can steal funds instead of monitor the transaction. That's the same result as an attacker who changes the Bitcoin address.
Yes, but I guess what @oryhp says is that if you communicate without a secure connection you can't be sure there isn't someone spying on you without you knowing it. Sure, he can take the money, but what's more valuable? Depends on your threat model.  Tongue

I was thinking the same thing. Maybe because creating a new address for each visitor means they have generate and monitor millions of addresses.
You only need to derive millions of addresses from one master public key, and save those with a balance.
4413  Bitcoin / Bitcoin Discussion / Re: Could Bitcoin's transparency be its downfall? on: May 31, 2022, 02:11:21 PM
The problem, as you alluded to, is that we can evade all kinds of laws with software and technology, but in the end we live in a society that has rules, like not to launder money.
This wasn't my point. My point was that if an entity perpetually brainwashes everyone and tries to create a bad picture of bitcoin for their own benefit, you shouldn't bow your head and admit you're doing things wrong. For example, if few politicians state that bitcoin wastes too much energy and advise against its usage, don't try to change the code; the problem isn't into the code. We've spent hours on this debate, and we've debunked it.

Same goes for KYC. There's no study that reveals less criminal activity due to this undoubtedly extravagant requirements of personal info. Pretty much the opposite, it's extremely dangerous; it encourages identity theft, scams and helps scammers stay undetected. The reason the governments want it, and exchanges often intentionally add it, is control. It makes mass surveillance work more easily and effectively, it's moneymaking from the CEX's perspective, it's advantageous for chain analysis which brings even more money etc., all these entities cooperate for control.

So, when a CEX imposes KYC or some other arbitrary rule, such as "tainted coins", don't try to figure out a technical solution, such as improving privacy on a protocol level with cryptography. Just don't use the exchange.
4414  Bitcoin / Development & Technical Discussion / Re: Silent payments on: May 31, 2022, 01:43:13 PM
And what are the ways to bypass such attack when using silent payment?
If Alice and Bob communicate through a secure transfer protocol, such as with SSL certificates, then MITM attack becomes more difficult to execute. And they should, with or without silent payments. Otherwise, their internet provider and the server they use to communicate can de-anonymize them.

Let's say TPB accept Silent payments. Someone sends them a donation, which confirms on-chain. Nobody else can know TPB is the receiver, because they can't know which on-chain address belongs to their Silent payment.
So why they don't just generate a brand new address in each refresh, for each visitor?
4415  Bitcoin / Development & Technical Discussion / Re: How much text can you put in a bitcoin message? on: May 31, 2022, 07:15:06 AM
Does this actually work with 0 sats?
Yes, because it doesn't take space in the UTXO set. OP_RETURN outputs are simply ignored.
4416  Bitcoin / Hardware wallets / Re: SeedSigner: Review on: May 30, 2022, 06:18:51 PM
but you didn't say if you ordered that orange pill case from third party or you  3d printed it yourself?
I ordered it from gobrrr.

I have to say there are much better and smaller SeedSigner cases and I prefer them instead of this default option
Yep, but I thought the default would be a better option. Proved wrong.  Tongue

Most people would just use default entropy generation that is not really random nor secure, that is why they decided to go this direction.
Which thing isn't random nor secure exactly? Pi's RNG? urandom?

If you make any mistake during this process you can only blame yourself, not SeedSigner aka Rpi.
But, I don't blame them for my possibly less unpredictable entropy. Of course and it's my responsibility to ensure the dice is fair. But, you don't get to force me go with your way, just because you think it's right. This attitude is translated to a little disrespect, one might say, towards actual cryptographers who've studied more than you've done, and have concluded to using a CSPRNG.

Let me choose a "Use Pi's RNG" option, and if you don't recommend it, show a warning.
4417  Bitcoin / Bitcoin Discussion / Re: Could Bitcoin's transparency be its downfall? on: May 30, 2022, 05:52:47 PM
So, I think we know how to protect Bitcoin from censorship. My answer is just "we should write a better code".
Why do I have a feeling that this is the wrong path? I agree with all you've said, and bitcoin can, indeed, become more private overtime, but answering with "let's just write a better code" implies that what's causing this taint propaganda is the code.

I sort of agree with this:
Quote from: Unknown
You will not find a solution to political problems in cryptography.

Bitcoin solves no political problems, but only practical and technical. And we're seeing this everyday. I can move millions of dollars for a nickle (practical) or move money across the world anonymously (technical). But, there's no such mechanism that can give a solution to the abrupt rise of KYC. No, decentralized exchanges don't. They mitigate trust, same as with bitcoin, because things work more properly that way; because trust costs. But, both solutions are apolitical.

See monero. It's, supposedly, more private than bitcoin. What has happened? Most CEX's have blacklisted it, less and less merchants dare to accept it, people beyond the crypto space are constantly brainwashed etc. Is the problem in the code?
4418  Bitcoin / Hardware wallets / Re: SeedSigner: Review on: May 30, 2022, 04:29:37 PM
Since, most other hardware wallets don't offer this, you could potentially even argue that this is an additional expense that isn't really needed.
It's necessary. Without the camera you can't scan the PSBT from your computer's monitor.
4419  Bitcoin / Development & Technical Discussion / Re: How much text can you put in a bitcoin message? on: May 30, 2022, 03:25:36 PM
I would like to send BTC and put a message in it. Can someone guide me?
Which wallet do you use? In Electrum, enter OP_RETURN and, right after, your hexadecimally represented message. For example, this message:
Code:
The Times 30/May/2022 Football's night of shame
Hex: 5468652054696d65732033302f4d61792f3230323220466f6f7462616c6c2773206e69676874206f66207368616d65


Check the transaction, made in testnet, on a block explorer: d1cc92eb8af8e21f11177886a95ccda37c5236eafa170a446c031da6f8834a1d
4420  Bitcoin / Hardware wallets / SeedSigner: Review on: May 30, 2022, 01:50:15 PM
Prologue
So, a month ago, I was trying to find out which hardware wallet should I buy. My conditions were simple; it had to be open-source and I had to make the purchase in the most private way possible. My only option was to buy BitBox 1, but it happens to be old, deprecated and their developers aren't known for being privacy seekers, which really underwhelmed me.

My only choice was to purchase a hardware wallet outside my country using a poste restante, which I didn't want to do for personal reasons. But, then dkbit98 suggested something I hadn't thought of; do the job with a Pi.
I don't know if you want to use hardware wallet just for Bitcoin or for other shitcoins, but if it's only for good old BTC than you can buy Raspberry Pi zero locally and make your own SeedSigner signing device.

And so I did. I bought a RPi Zero, a camera, a little screen and a few other stuff, and built a SeedSigner; an air-gapped hardware wallet signing device, which takes security into the next level.  Wink

Disclaimer: There's no affiliation with SeedSigner and this thread isn't sponsored. I just bought it and share my thoughts.




Review


In summary:

Pros:

Cons:
  • Little hard setup
  • Experimental software; the project is, well from what I can judge, in an early stage
  • Works only with BlueWallet, Nunchuk, Sparrow, Specter Desktop
  • It's forcing you to generate the entropy yourself




Alright, let's begin.

SeedSigner aims to give a solution to one problem; the cost and complexity of multi-sig usage. However, at the same time, it can be used for single-sig setups, lowering the cost of your "hot" storage as well. There's nothing saved inside the SD card, besides your settings which is optional, therefore there's less danger for funds' loss. When you shut down SeedSigner, it erases the seeds; they're meant to be kept temporarily in memory and you have to import the seed on each startup. And that's basically one of the features that makes SeedSigner differentiate.

This has the following advantage: You can have the device on plain sight (don't, but you get the idea). As far as I understand, this is implemented to reduce the risk of money loss. For cold storage, create the QR code and find a good hiding spot. For daily transactions, you can just insert it into your drawer etc., without minding much.


For quick imports, use QR scanning:



Unfortunately, you can't create a new seed with an internal RNG. SeedSigner somewhat forces you to generate the entropy yourself. Either with a picture or dice rolls.


I get the spirit of "trust none!", but that's just wrong. It should allow you to generate random entropy, even with a warning. Furthermore, it gives a false sense of security. If you don't test the dice is decently fair, then you shouldn't generate a wallet. Period. Quoting a forum legendary is needed here:
Coders who make their own ad hoc randomness schemes are like kids playing with matches.

Hashing a picture can also be problematic, see thread: Turn photos into Bitcoin wallets. So, here's a feedback: Include /dev/urandom. Simple. Do it for those who want to avoid this fuss.

This is how they justify it:

One thing I also don't understand is how the rolls are 50/99 exactly. Doesn't each give 1.66 bits of entropy on average?  



These are the features:
Feature Highlights:
  • Calculate word 12/24 of a BIP39 seed phrase
  • Create a 24-word BIP39 seed phrase with 99 dice rolls
  • Create a 24-word BIP39 seed phrase by taking a digital photo
  • Temporarily store up to 3 seed phrases while device is powered
  • Guided interface to manually create a SeedQR for instant input (demo video here)
  • BIP39 passphrase / word 25 support
  • Native Segwit Multisig XPUB generation w/ QR display
  • Scan and parse transaction data from animated QR codes
  • Sign transactions & transfer XPUB data using animated QR codes (demo video here)
  • Live preview during photo-to-seed and QR scanning UX
  • Optimized seed word entry interface
  • Support for Bitcoin Mainnet & Testnet
  • Support for custom user-defined derivation paths
  • On-demand receive address verification
  • User-configurable QR code display density
  • Responsive, event-driven user interface

One thing I've forgotten to say is that, besides open-source, the code is also easy to read. It's 100% written in Python, and there aren't many files to check. It doesn't take more than an hour. The src/seedsigner/models is what's all about.



How to use it

These are the steps to spend money:
  • Create a seed.
  • Export the master public key with a QR code.
  • Import the master public key to a wallet software. (From the available, I prefer Sparrow*)
  • Create a transaction.
  • Export the PSBT in QR code from your computer's screen.
  • Scan the QR code from SeedSigner.
  • Sign the transaction from Seed Signer.
  • Export the signed transaction in QR code.
  • Scan the QR code from your computer.
  • Broadcast the signed transaction

Ta-da! Transaction signed in the air!  Shocked

*Sparrow is a wallet I'd never used, as I put Electrum above others, but I'll have to admit it's good. Perhaps even better than Electrum. The reason you can't use Electrum (at least not easily) is because it doesn't support animated QR codes, which is the way SeedSigner exports xpub keys and signs transactions. That's because the screen isn't big enough.





No, these cool, freshly 3D printed mined bitcoins in the images above aren't included in the SeedSigner Kit.  Tongue
Pages: « 1 ... 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 [221] 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 ... 463 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!