pull down to refresh
0 sats \ 0 replies \ @senf 18 Feb \ parent \ on: Did we really land on the moon? AskSN
Governments lie a lot. I wouldn't say that it rises to "almost always." Taking something the government says as evidence that whatever they said is the only thing you know is not true is just as dumb as thinking they never lie.
You can test this yourself. Spin up 12 words and put them into a wallet, and note the first receive address. Put the same words in other software or hardware and note the receive address, it'll be the same. The mempool is pretty empty at the moment too, so you could do it with sats sitting in a UTXO without wasting too much money if you feel like that would be more meaningful.
You do also need the same derivation path, to be clear. That part is usually done in a standard way, but if your first wallet does something different you won't see the same info in other wallets without specifying your derivation path.
Every question has a meta question behind it, so every answer should have a meta answer behind it as well--ie, take a moment to think why they're asking you this question, and be sure your answer satisfies what they're looking for.
The "What's your biggest weakness" question isn't asked because they want to know that directly, they want to know about how self-aware you are about potential shortcomings and if you are taking steps to improve yourself, etc.
Structure answers to keep from rambling. I like to use STAR: Situation, Task, Action, Result. Clearly state what the situation was for context about everything else you'll say. What part did you play specifically in the plan? What individual actions did you do as your part (and be sure to say "I" as much as possible, saying "we" can make it sound like you were just along for the ride and didn't do anything yourself). Lastly, talk about the outcome and how your actions contributed to it being positive, and anything you've learned to use in the future.
What can go wrong? Sats can't just disappear or get hijacked, they exist at the source or the destination always. If you're on both ends then they're always yours. There's no additional risk* with a transaction sitting in the mempool waiting to get into a block. Nothing bad can happen.
*Technically with most common address types your transaction exposes your public key, which makes a future quantum computer attack more feasible. We are a very, very long time from that being a legit concern. Taproot addresses have bare public keys that are exposed from the moment they receive sats, as an example of why that isn't a thing to worry about at the moment.
Why would it matter if it takes months if you're sending to cold storage where it will stay for years or decades? There are definitely cases where a transaction would need to be faster, like if you're sending it to someone else.
If one single node in the entire world decided to use a different setting for purging old transactions, a valid transaction could be resubmitted to the mempool at any time and make it into a block.
My longest time to confirm was about two months.
I think xpub is technically for old legacy (1*) addresses, and zpub is native segwit (bc1*). People say xpub while meaning any of xpub, ypub, and zpub.
He's not related to the composer, no. The first book in the series is one of my absolute favorite books ever. The rest of the books are good, but I think they decline as you go through them.