The last rounds winners though show us a different thing.They the people who have won the weekly lotteries do not have a huge balance nor they have bet huge amounts as to win like 1000-5000 lottery tickets you just need to have some like 10 WoF spin daily and you can get that amount within a week.
The reason we don't win is that out of 50 million users we need to be extremely lucky to be in the top 10 weekly lottery winners,chances in percentage as you can see in the lottery tab of the site is very but very low.
I really see no point in being excited by lottery results from years ago. It is like it was in the previous century. As swogerino mentioned, the times has changes, I do not know how it was in the past, but probably now the lottery is really a secondary thing. I think most of people here, on the forum, has disabled tickets from free rolls; if someone has huge amount of tickets then it is probably from referrals. |
|
|
|
Most probably he used the mobile version where you can add the homepage of Freebitco.in as some app.Every time I check right after the lottery has been drawn it shows the 60th round for me too.
Or again one of "cache" problems. I think they should rethink which URLs could be forced to be refreshed (for example using personal/time-updated parameter as a part of URL). For a very long time I had the same problem using my mobile when I wanted to convert RPs to WOF, the old price was displayed in pop-up. |
|
|
|
2 months away for me to get my maturity on the FUN I locked for a year. Didn't even realize how fast time flies, and in that time I kept calculations and have earned 30k satoshi just from WoF and freespins (not including wins but including interest).
Do you remember what was the average cost for your tokens? I guess you have disabled lottery tickets from freespins, haven't you? 40 hours left for BTC/ETH/FUN price betting. I did not expect BTC will go to 21-22 range again, and I have no idea what will happen in 10 days. Therefore I think I will skip betting this month, for me both ranges (20-22.5 & 22.5-25) are 50/50. And we even cannot exclude going below 20k, so no, no betting in August. I am not even sure if FUN will stay in the range. |
|
|
|
Webhards are the main platforms that the attackers targeting Korean users exploit to distribute malware. What was recently found was XMRig, famous Monero Miner. Anyway - if you do not download software from the official site, but from random sources, do not be surprised you get promo "2 in 1". More info: https://asec.ahnlab.com/en/37526/ |
|
|
|
Keep in mind that this method is only accurate when the missing characters are all at the end since the farther away they get from the end, the bigger the range is going to be compared to the actual range of missing characters.
I know, but I have prepared a version of Kangaroo which works with given stride - just to be able to solve WIFs, preferably with missing beginning. https://bitcointalk.org/index.php?topic=5315607.msg56298967#msg56298967 |
|
|
|
I do not understand what do you mean by "directory" - is it a file with addresses? Or directory on hdd where each file has name like an address? Then how you may have the same address twice? It's a directory with files. Each file has all Bitcoin addresses that were used that day, some of them more than once. Ok, I understand now. That way I may change program to process all the files from the given directory, not only the one file (daily snapshot). The question would be if you look for double hits per day/per file, or totally in any of files. If you change your mind, give it a try, maybe it will use less resources. I do not know how much memory will take 8.7mln addresses. |
|
|
|
|
The problem with your WIF is that stride collides with checksum and you may have improperly calculated private keys, tomorrow I will launch my calculator to see how to solve it, usually it may be solved by launching several works with a different starting points. Just confirm how many characters you know l, from the gap to the end.
|
|
|
|
|
No, that’s not correct. I mean, it is, technically, but it is not the best way to solve WIF problem. You know that you look for a private keys with a given stride, which is “58^number of known characters to the end”, in your case 58^15.
|
|
|
|
Question
I have a file (300 MB) with 8.9 million Bitcoin addresses. I also have a directory (67 GB) with all Bitcoin addresses. I want to know which address from the file is in the direcory more than once.
Hi, I do not understand what do you mean by "directory" - is it a file with addresses? Or directory on hdd where each file has name like an address? Then how you may have the same address twice? I have prepared a small program for you: https://github.com/PawelGorny/Loyce60787783It reads into memory list of addresses and then reads "directory" file with addresses - if address exists in memory, is marked, if the same address in hit for the second time, is removed from memory and saved to file. If you want to calculate how many times address was hit, the change is needed. |
|
|
|
5HpHagT65TZzG1P*********************EB3kEsreAnchuDf
it is not the best example, because you used WIF from private key=1. Normally you calculate range as follows: replace unknown characters by "1", decode, it will be your starting range. Then add 58^unknown characters (in your case 21?), if you add to starting range you will have the end range for search. - is there is some useful methods to try to recover my wallet instead of bitcrack ?
Yes, that's what we try to do with Kangaroo - if the bitcoin address contains 0.054 BTC , will it be a 54 bit 2^54 ? ( sorry if it's a dump question , but i have limited knowledge ) .
No, it has nothing in common. - can i split the range that i will be searching for into 2 parts , for example let's say that i will search for a specific range for 7 days , how can i split this search into 2 devices ?
doable. |
|
|
|
2. Secondly, there was a day I was asleep, my wife wanted to use my phone but didnt know my password, she didn't want to wake me up either, all she did was take my finger, place it on the biometric scanner on the phone and my phone unlocked.
When I woke up and found out, I though within myself, "what if it was someone else I don't know that took my phone that afternoon and did what my wife did for the purpose of gaining access to my private information.? My banking details, my crypto wallets etc.
Or even worst ;-) https://news.sky.com/story/flight-diverted-after-woman-unlocks-husbands-phone-and-discovers-affair-11117184We all know that 2FA is based on 2 thing from different groups: something you know and something you have. Apparently we cannot base generation (let's do not talk now about access to device where crypto wallet is already created) of crypto-keys on anything what we cannot control. Otherwise we are like people who holds their credit cards with PIN written on the card. |
|
|
|
Last 3 days left on the price betting events on bitcoin and ethereum. The tables have turned now because of the dump yesterday from $24k to $21k.
Volatility is high so may be it will be difficult to predict the prices this time. But the risk is worth it because of attractive returns on the price ranges.
What are you guys planning to bet on ?
I was thinking about the same today. Plan minimum is FUN ($0.007501 - $0.01), but odds are very low (as always), 1.15. ETH made a very good progress recently, but last days' dump moved it back to $1,501 - $1,750 range (odds 3.45). And if we believe it will stay there, it would be a good option. Similar situation is with BTC, but here the 2nd range ($20,001 - $22,500) has lower odds (2.76). I will wait 1-2 days more (this month I did not do any early bets) and if situation will be the same, I will bet on ETH. |
|
|
|
It may encourage more people to buy BTC if it is needed for betting. In general it might be seen as a good opportunity to buy and start betting. Otherwise, if you had BTC (or other coins) bought in the past, even if you have quite good results (profits), probably it would be still not enough to cover the price change.
I'm not quite sure about your opinion, I think it will encourage people to hold for long term, not for betting. Most people doesn't really care with the price change, they're calculate their profit based on Bitcoin equivalent, not in USD equivalent. They will confused to count how much they're already wagered and when they should stop, converting to stable coin every day also doesn't worth it. That's what I wanted to say - they will not sell their BTC to FIAT, even after significant win, because at the end the FIAT amount they get might be disappointing. So maybe it may have exactly the effect you mentioned - more people will hold BTC on their casino accounts. It might be different with stablecoins, but talking about "pure" crypto coins the current price does not encourage selling. |
|
|
|
Of course when Bitcoin gets dumped there will be a bad or other effect for a gambler. Because when a gambler bets with Bitcoin, his bets will definitely be affected by the Bitcoin market dumping. But when a gambler bets with stable coins, the dumping of bitcoins has no effect on his bets.
It may encourage more people to buy BTC if it is needed for betting. In general it might be seen as a good opportunity to buy and start betting. Otherwise, if you had BTC (or other coins) bought in the past, even if you have quite good results (profits), probably it would be still not enough to cover the price change. |
|
|
|
This is why I believe that we are not looking at a bad investment no matter where you bought it. We should also compare as well, if I bought bitcoin with the same money it just went down and will recover, but with fun tokens it went down just as bitcoin did, but also kept making me profits meanwhile instead of just waiting for it to recover.
Only if you are patient enough. No easy/fast money here. For me, the FUN prize and profits from trading are secondary, I bought them for premium membership benefits. The fact I may lock them for a really nice interest is good thing, but I made the decision thinking about something different. |
|
|
|
I think the confusion here is that it seems pbies is talking about taking any arbitrary string, passing it through SHA256 (or some other function) to create a (usually) valid private key in hex, and then encoding that as a WIF. In this case he is correct in saying that there are many different strings from outside the range given which when first SHA256ed will result in the same private key (although it is almost certainly impossible to find such a collision).
Have you ever heard about any brainwallet (or simply saying just a sha256 hashed phrase) which produces wrong private key? As upper boundary is not fff...fff, but a little less, do we know any example of sha256 result which "bigger" than allowed private key? |
|
|
|
New electrum version is released. It contains some minor fixes for Lightning network and UI # Release 4.3.1 - (August 17, 2022)
* build: we now also distribute a "source-only"
Linux-packager-friendly tarball (d0de44a7, #7594), in addition
to the current "normal" tarball. The "source-only" tarball excludes
compiled locale files, generated protobuf files, and does not
vendor our runtime python dependencies (the packages/ folder).
* fix os.chmod when running in tmpfs on Linux (#7681)
* (Qt GUI) some improvements for high-DPI monitors (38881129)
* bring kivy request dialog more in-line with Qt (#7929)
* rm support of "legacy" (without static_remotekey) LN channels.
Opening these channels were never supported in a release version,
only during development prior to the first lightning-capable
release. Wallets with such channels will have to close them.
(1f403d1c, 7b8e257e)
* Qt: fix duplication of some OS notifications on onchain txs (#7943)
* fix multiple recent regressions:
- handle NotEnoughFunds when trying to pay LN invoice (#7920)
- handle NotEnoughFunds when trying to open LN channel (#7921)
- labels of payment requests were not propagated to
history/addresses (#7919)
- better default labels of outgoing txs (#7942)
- kivy: dust-valued requests could not be created for LN (#7928)
- when closing LN channels, future (timelocked) txs were not
shown in history (#7930)
- kivy: fix deleting "local" tx from history (#7933)
- kivy: fix paying amountless LN invoice (#7935)
- Qt: better handle unparseable URIs (#7941) |
|
|
|
Now, run a loop, checking each and every address for a balance, then you create a transaction that burns the ENTIRE balance in fees. Attackers won't be able to bump this transaction with their own, because nearly the entire balance has already been allocated to miners anyway.
Bitcoin - even the stolen coins contribute to the network security. (Denial-of-service for theives.)
That's very interesting concept. It may be extended into "management of address", where owner signs kind of message which "blocks" given address (we may say it would be irreversible) and any output sent would be burn in the way you described (or any other). Or sends back. To have it working flawlessly, it had to be implemented in every node, not to have 'centralized' database. Which means there would be a way to mark address as 'closed' (like closed account in bank). That would allow for example "addresses managers" (like exchanges, shops, casinos etc, any companies which produces deposit addresses for customers) to block used addresses of given/past clients. |
|
|
|
|
Show Posts
