Not sure I understand this. If someone finds my 12 words but not my passphrase, he can see I have a smaller balance than the reality? I have 10 BTC, and without the password, someone sees I only have 0.1 BTC? You can use IanColeman.io to try it (of course only do this online to see how it works, not to create private keys you're going to use): 12 words: plunge snow gorilla wool help income mom kitten volcano warm top girl First address: 15Q9XKiYX4RZhNLdKYt894o1zguyhufoPZ Now add BIP39 Passphrase: \q?mpN[!\4`LA5w* First address: 19mYSjt1VaiGpTop31uEMWJFYbW76MCRJ3 Without the password, the same 12 words lead to different addresses.
|
|
|
Not sure how the BIP39 passphrase protected mnemonic code would not reveal your balance. Care to explain this? Thank you. You can set a password (for instance in Electrum) to extend the mnemonic. So with just 12 words, you'll find your daily spending money worth 2 pizzas. But if you add your own password to the 12 words, you'll get your hodlings worth 2 airplanes.
|
|
|
This is why you most probably need to destroy the private keys of wallet A right after you signed the transactions. This is terrible advice! Let's see what someone who knows a thing or two about Bitcoin said: You should never delete a wallet. This way, you only store private keys of wallet B (or simply use wallet B on a custodial exchange / wallet where you can login every time because you previously made the KYC) with 0 balance. With the custodial wallet, there is no risk of the exchange being hacked, because you don't store anything there, you will only use the wallet B if you'll ever need the backup. Best is to sign the same UTXO to more than one address and if you'll ever need the backup transaction just simply broadcast the one that you can surely access. So instead of "be your own bank" and "not your keys, not your coins", you want people to completely rely on third party services and give them the power to broadcast away your coins whenever they want.
|
|
|
Go to your http://addresses.loyce.club/css/all.css file You will find this: .xBlank { padding-top: calc(4rem + 74px); padding-bottom: 11rem; } Delete it, and add this: .xBlank { padding-top: calc(2rem + 74px); padding-bottom: 2rem;} This will fix the vertical white space. I don't think this changed anything, see this test version. About code tags, you just need to add <code> </code> where you want to look like code. ~ and add in your Css for different colors for balance and address, if you want: Thanks, that was easy. I don't need different colors, so I changed it to this: code { font-size: 87.5%; color: #888888; word-break: break-word; } Ideally, there should be a rectangle or something around the code tags. The forum makes code tags very obvious that way. If you want to get completely rid of vetrtical space, delete the "xBlank" class from this DIV, in the HTML: <!-- Just remove or copy the whole div/p/a/ tags from the (--start-- to --end--) --> <div class="xBlank bg-default"> I tried removing it, but that makes it too crowded. On the left side of this page, I've played around with this: <div class="card-body text-center"> That lead to too much vertical white space, so I've also changed this (it was 1.25rem;): .card-body { flex: 1 1 auto; padding: 0.50rem; } It feels like the 183 kB all.css is far too advanced for what I'm using it for.
|
|
|
I just realized why this fucked up year feels like it's never ending - it's 97 weeks according to the thread title. In 7 weeks, I hope to change the title to "first 🦊2 YEARS". Or even better: "first 🦊🦊 YEARS". And there's this: I was already wondering whether or not I should add another year to this domain: Update: domain isfoxpupstilla NSFWvixen.today is mine now At some point I wrote this: I'll probably let the domain expire after a year, I'm don't really want more domains to keep track of, just loyce.club is enough. Then again, when I created that one, I also expected to let it expire after a year. But maybe there's a bigger plan for a celebration domain that I am not aware of yet. Only 14 weeks left The 14 weeks just had it's halving into 7 weeks. Illuminati confirmed. Interesting logic! What happens next week? 98-52 = 46 46/52=
|
|
|
Ninety-seventh week paid. Thanks again for your flawless timing! I'm late, and as usual I'm blaming the kids They kept me busy all day so I'm catching up now.
|
|
|
I think one of the concerns regarding when we reach the total supply, miners will be less incentivized to mine Bitcoin, and probably quit because it is no longer profitable. A lower block reward means miners rely more on transaction fees. Every halving, miners are less incentivized to mine, but every halving, a new equilibrium is found. I don't expect this to be a problem when (decades from now) transaction fees are the main source of income for miners. I'm always amazed how well Satoshi's planning works out.
|
|
|
I've just doubled my allowed bandwidth (paid by Bitcoin Lightning Network) to 2 TB/month. However, the webhost hasn't processed the payment yet. If it processes it on time, you guys can continue downloading tomorrow. If not, it will reach it's 1 TB bandwidth limit tomorrow and get be suspended until the end of the month.
To be continued ........
Update: upgrade completed! I'm curious though: I'd love to know what this data is being used for. There must be more than a thousand downloads per month now.
|
|
|
So, if you lose access to your non custodial wallet (wallet A), simply login to backup service and run the previously signed raw transaction that will send all your funds to wallet B where you can access it. Why would they still have access to wallet B if they lose access to wallet A? If, for instance, you keep wallet B in a different location than wallet A, why don't you just keep a backup of wallet A on the same location?
|
|
|
created a new standard electrum wallet with seed after that i clicked "wallet" -> "sweep" -> pasted private-key funds are now in tx from paper wallet to standard electrum wallet. So the funds were still on the original paper wallet? Earlier you said the transaction was confirmed. None of this makes much sense, but at least the end result is good. Don't lose your coins again If your coins on your paper wallet were old enough, you may also own some Forkcoins.
|
|
|
It sounds like you have imported a single address from somewhere and then swept your paper wallet to it. You need to figure out where you copied that address from, as without doing that, you will not be able to access the coins. This is what I get from reading this (quite confusing) story. I then created an electrum wallet and saved the seed. Great! So far so good. I then created a new electrum wallet within the previous wallet, with key from paper wallet, a watch only address, then I swiped the paper wallet into this watch only address. Did you import the watch-only address, or the private key? This watch only wallet is a deterministic wallet " A deterministic wallet is a system of deriving keys from a single starting point known as a seed." I don't understand how you went from a paper wallet to a HD-wallet. I also don't understand how you sweeped the paper wallet onto the address you imported from the same paper wallet. Can you start explaining everything from the start again? Did you do all this recently, or did it happen years ago?
|
|
|
is it advisable to reduce the halving time from 4 to 2 years, from 210 000 to 105 000 blocks? No. Changes like that undermine the trust in Bitcoin. If this can change, halving can become a doubling too. Let's not go there.
|
|
|
So an unknown guy called him, told him he is a Ledger operator, and got probably the seed from him. He lost $27k but this was totally his fault. It sounds like they only got his phone number from the Ledger hack. Other than that, it's a "standard" phone scam where the victim gives away access to his money. Ledger just made it a lot easier by providing a list of Bitcoin users. For "standard" bank phishing calls (or fake tech support calls), most phone numbers can be a potential victim as most people have a bank account or a Windows computer. For crypto that percentage is a lot lower, and multiplied with the percentage of gullible people odds are even worse for the scammer. I can imagine a 1 in 100,000 successful phishing phone call isn't worth the effort, but if Ledger's data breach turned it into 1 in 100(0), it becomes (very) profitable. I'm just speculating on the numbers here of course.
|
|
|
Emphasis mine. Also the quote from your site: "How do I redeem my funds if I win?". I take major issue with this wording. You are not winning a prize which has been offered up willingly. It is not a competition, and the funds are not yours to redeem. It is stealing. When you put it like this, it sounds bad indeed. if you do stumble across a collision then you have somehow "won" and it is morally and ethically fine to just help yourself to the funds within. If anyone can find my private key, I assume they'll steal my funds. And even if they don't, someone else will do it when they find my keys. None of this matters as long as you keep your keys secure. Of course it's morally and ethically wrong, but so are many other things. That's why I lock my bicycle, because even if the first people who find it won't take it, someone will!
|
|
|
You can probably get the pre-validated files from somewhere on the internet but there isn't any guarantees about its authenticity or any possible problems arising with it. I made a topic about this in 2019: Bitcoin Core pruned blockchain: download it here! (DON'T DO THIS!), but stopped updating it. My latest pruned files are over 14 months old now. There was consensus on the title: yep, don't do this Yes, don't do this! Just in case it wasn't clear yet: It's NOT recommended to download the blockchain any other way than having Bitcoin Core download it on it's own. Don't do it! Seriously, don't! ~ On Reddit, theymos wrote this 3 years ago: This is massively insecure. Bitcoin Core trusts its block database files absolutely. /u/nullc has said that it is not particularly unlikely that a maliciously-modified block database could be used for arbitrary code execution. And even if that's not possible, all sorts of more obvious evil could be done, such as allowing the provider of the block database to create a special killswitch transaction which forks everyone who used his block database, or having everyone who used his block database think that he actually owns 22 million BTC. Nobody should ever receive block database files from untrusted sources. Also see: https://en.bitcoin.it/wiki/Data_directory#TransferabilitySo again: don't do it!
|
|
|
But the chances of finding, as on other similar sites, are almost zero. But there is a chance You're much more likely to guess credit card number. And if it doesn't have to be mine, it's much easier. With 2.8 billion credit cards in use and only 16 digits per number, you'll find on average 1 valid number for every 3,571,429 combinations you try. I made * you the first batch of 3,571,429 random 16 digit numbers * Give it 40 minutes to complete.
|
|
|
Sure, but I'm not sure what it is about bitcoin that makes otherwise honest people think it is OK to steal from people. Most people in the world if they found a set of car keys lying on the ground on a parking lot wouldn't pick them up, find the relevant vehicle, and drive it home. But it seems that there are a significant number of people on this forum who, if they found a private key collision, wouldn't think twice about stealing someone else's coins. The difference is of course anonymity: a car is registered, and the owner can be found. Bitcoin is more like cash, but on top of that is on the internet. I'm pretty sure more people would return the car keys than a pile of cash they find.
|
|
|
I automatically believed the accusers which is probably a little silly. I left them a neutral tag at first, but added a negative tag when they admitted to holding a user's funds hostage. That's just untrustworthy behaviour. Let's not extrapolate from a sample size of 1. Agreed. For instace selective scamming can leave a service with many satisfied customers who vouch for them, and only a few users who get scammed.
|
|
|
|