The mixer account from this accusation still has a link to his site in his forum profile That's one backlink that can be removed, but the mixer's name is like "DomainExtension", which still makes it very obvious. |
|
|
|
IBD, why every node has to do it? You can of course use prunednode.today, and download a pruned node. I just tried: it took my server 75 seconds. But you'll never be absolutely sure it's completely legit. And if enough people do it, someone will find a way to scam them. This guy knows a thing or 2 about the subject: FWIW, I just removed a nearly year old post with a .bitcoin directory download that would have stolen all your bitcoins.
Case in point as to why these "download the blockchain" links are a disaster. God knows how many people got robbed due to it. But the chainstate database/etc. aren't intended as external interfaces and I would be totally unsurprised if there was a way for malicious data in them to result in code execution. |
|
|
|
You just have to manually craft a raw TX to spend all of the UTXO in a single transaction, but you would have to sign them separately as I'm not aware of any wallets allowing different address formats to be mixed in the same address. Bitcoin Core allows any different address types to be used as input for one transaction. I'm pretty sure Electrum can do it too if you import the private keys with the correct prefix. |
|
|
|
I left you the final one. Exactly what I told you in the last PM is what I'm going to do. Change is constant. Judging by your recent posts, you've moved from spamming the Gambling board to spamming Reputation. I count 5 posts in my topic already. Did you even read what this topic is about? Allow me: DT1 and DT2 members who have negative feedback (or are banned). You're not a DT-member, so your negative feedback is off-topic here. Since you get paid up to $1.75 per post, it looks like you're monetizing your negative feedback. I won't allow that in my topic, so please stop. If you wouldn't be a shitposter, I'd tell you to create your own topic. I said "please stop". You didn't, so I'm deleting 6 posts now. There goes $10.50, but don't worry, you can easily make up shitposting the Gambling board. |
|
|
|
Is it Ok for DT members to interfere with moderation rules/duties?
~
Hitler used to kill/burn disabled children And this is why nobody will ever take anything you post seriously. There's no point even responding to your Godwin. |
|
|
|
I just got mine uninvited, unjustifiable and without evidence. JollyGood I need explanations. I just read your PM. Here's the thing: Hey, I got one too  @borovichok: you're a spammer, and you're paid by the worst Bitcoin-paying spam campaign on Bitcointalk (Stake). You spam 121 posts per week, and nobody cares about them. Your negative feedback may not be correct use of the Trust system, but if it stops Stake from paying you for your posts, it may stop you from spamming shitposts. This is the post that got me tagged, poorly worded but AI generated? No Stick to a player that's outstanding and confident in scoring points. Every team do triggered winning and losing, we have potentials of winning, if they do not have this hope, they wouldn't have compete or contend for any solidable points in the league. Thrilling victory is achievable and everyone has the right to be able to place wager on games. We all have choices to make and our favorites in the game. @morvillz making an exception of choosing Wilson or Flacco over Brownings bases on the tactical date examined, but the same underrated Brownings is the favorite of most viewers in the system. AI spambots create better sentences than you do. This verbal diarrhea should get you banned, not tagged. |
|
|
|
I want to move my wallet Why? Is it really necessary to do this now? You have 488 inputs, which means you're going to have a very large transaction. You should read my topic on consolidating inputs. You basically have 3 options: pay the high fee, wait and hope for lower fees later on (this can take months, there is no guarantee), or move only a part of your funds now and leave the rest for another time. To move a part of your funds, manually select which inputs to use (this is called Coin Control). By selecting only a few large inputs your transaction size (in bytes) is smaller and you pay less in fees. I checked your address from your screenshot: you even have a 547 sat dust input. That's not worth the fee, freeze it and don't use it. Other small inputs are barely worth the fee. If you select for instance the 30 largest inputs from that address, you can already send 35% of your Bitcoins but pay only 6% of the transaction fee.  Also: if you use Segwit addresses from now on, it would save a lot on fees in the future! |
|
|
|
He doesn't know the bitcoin address at all.
He said he has multiple hex private keys. One of them is for an address with only $10 worth of bitcoin and he asked me if I can check it. How does he know the balance without knowing the address? I warned him about messages not being encrypted and the risk involved in sending a private key via pm.
He said he doesn't mind losing the $10 and insisted on sending me the hex private key. I wouldn't worry about Bitcointalk PMs being compromised for $10. |
|
|
|
you missed this part: I didn't miss that. It's just very easy to type for 8 minutes on a long post, and those are the ones I care about. I don't care about losing 5 seconds of typing. Sometimes I have multiple posts open for editing, before posting them. That can take days. Usually I save a local backup, but I also rely on the "Preview" button to save a Draft. It would be bad if typing in one post wipes my other post from Drafts. |
|
|
|
Then I've used Electrum and attempted to 'Sweep' the WIF (tried both compressed and uncompressed) into a standard wallet but I keep getting a message saying 'No Inputs Found' The error message means that there is no fund at the address derived from the private key you are sweeping. How did you create the 64 character private key? That's not a very common format. |
|
|
|
I accustomed myself to VPN service when connecting Bitcoin Core to peers and sometime, being connecting via servers with the certain IPs, experienced the slow sync. If your VPN can't handle the bandwidth, obviously changing can help. I would add blocksonly=1 entry in bitcoin.conf file and set the correct value of dbcache in it. In general situation the rule of thumb dbcache=1/4 RAM, i.e. for 8 Gb of RAM dbcache=2048 I prefer to have dbcache > chainstate, but that only works if you can allocate 10 GB to it. I wouldn't recommend a quarter of your RAM, that depends on what else you're doing on the system. |
|
|
|
(default: 5 seconds) Shouldn't that be like 5 minutes by default? Otherwise it takes only 8 minutes to completely overwrite the 100 drafts stored by Bitcointalk, which is especially annoying if you use multiple tabs to edit longer posts. |
|
|
|
Can I add extra nodes that are more close to me, to speed up the syncing? In my experience, it's not needed. If your ISP isn't throttling you, Bitcoin Core should find fast enough nodes on it's own. Odds are the rest of your hardware is more limiting though. |
|
|
|
My setup: Bitcoin Core 26.0 on Ubuntu Linux 20 LTS, with settings: ./bitcoind -dbcache=4096 -prune=550 Every hour I store the output of: ./bitcoin-cli getblockchaininfo
free # for memory usage
ifconfig # for bandwidth usage My system: Intel i3 laptop with 8 GB RAM, no swap, SSD, VPN and about 70 Mbit/s fibre (shared with the rest of the house). Hourly snapshots: Memory usage (in kB): the column under "used" is actual RAM in use by running programs, the amount under "buff/cache" is file cache. So my 8 GB ram has 1.4 GB in use, and 6 GB as cache. I'm not sure how Bitcoin Core's dbcache is counted here, it looks like it's part of "buff/cache": total used free shared buff/cache available
0: Mem: 7896464 886744 3540780 71976 3468940 6631040
1: Mem: 7896464 1330572 1431872 67472 5134020 6191636
2: Mem: 7896464 1430260 370860 56728 6095344 6102660
3: Mem: 7896464 1415924 212176 55604 6268364 6118096
4: Mem: 7896464 1406264 265548 55612 6224652 6127556
5: Mem: 7896464 1464192 604184 56784 5828088 6068652
6: Mem: 7896464 1438192 466904 56788 5991368 6094572
7: Mem: 7896464 1453828 536400 56812 5906236 6078956
8: Mem: 7896464 1471348 475660 57364 5949456 6061140
9: Mem: 7896464 1450140 496528 57364 5949796 6082164
10: Mem: 7896464 1462976 282460 56852 6151028 6070016
11: Mem: 7896464 1433148 383072 56812 6080244 6099500
12: Mem: 7896464 1345788 679108 56768 5871568 6186660
13: Mem: 7896464 1362892 570220 58164 5963352 6168708
14: Mem: 7896464 1470504 689756 59260 5736204 6060004
15: Mem: 7896464 1466812 736848 58212 5692804 6064640
16: Mem: 7896464 1468596 667628 59388 5760240 6061412
17: Mem: 7896464 1459996 600740 59456 5835728 6070040
18: Mem: 7896464 1471352 564384 59272 5860728 6058980
19: Mem: 7896464 1453480 635228 59480 5807756 6076660
20: Mem: 7896464 1462944 319308 58824 6114212 6067856
21: Mem: 7896464 1465848 379816 59596 6050800 6063936
22: Mem: 7896464 1476788 228816 60656 6190860 6051860
23: Mem: 7896464 1379152 326068 60616 6191244 6149720
24: Mem: 7896464 1435832 263568 59068 6197064 6094576
25: Mem: 7896464 1477692 544540 58100 5874232 6053500
26: Mem: 7896464 1449552 512540 58512 5934372 6081168
27: Mem: 7896464 1465168 710916 59616 5720380 6064528
28: Mem: 7896464 1500760 139072 57912 6256632 6030720
29: Mem: 7896464 1458464 299044 59600 6138956 6071308
30: Mem: 7896464 1516848 491032 57772 5888584 6014708
31: Mem: 7896464 1515076 189824 59604 6191564 6015588
32: Mem: 7896464 1510132 137576 57704 6248756 6023336
33: Mem: 7896464 1514920 203540 57264 6178004 6020008
34: Mem: 7896464 1498772 125608 59504 6272084 6037380
35: Mem: 7896464 1419124 135508 59432 6341832 6118808
36: Mem: 7896464 1489180 159092 59456 6248192 6049372
37: Mem: 7896464 1495980 188368 59560 6212116 6042884
38: Mem: 7896464 1487280 487328 58468 5921856 6049808
39: Mem: 7896464 1468228 149468 57704 6278768 6066864
40: Mem: 7896464 1473212 131732 58660 6291520 6061800 0: "verificationprogress": 1.054359111951477e-09,
1: "verificationprogress": 0.04891353970646389,
2: "verificationprogress": 0.09407763328821177,
3: "verificationprogress": 0.1452094064674858,
4: "verificationprogress": 0.1999485637578325,
5: "verificationprogress": 0.2502986361236066,
6: "verificationprogress": 0.2948632578813903,
7: "verificationprogress": 0.3253893081185931,
8: "verificationprogress": 0.3667325462341976,
9: "verificationprogress": 0.4181769295434056,
10: "verificationprogress": 0.4684429325547408,
11: "verificationprogress": 0.5167469289823825,
12: "verificationprogress": 0.5560739987615844,
13: "verificationprogress": 0.5856895281560425,
14: "verificationprogress": 0.6149000806640802,
15: "verificationprogress": 0.6362808879763396,
16: "verificationprogress": 0.6572300384174818,
17: "verificationprogress": 0.6743030443020936,
18: "verificationprogress": 0.6898836424965333,
19: "verificationprogress": 0.707189535621089,
20: "verificationprogress": 0.7257414464822198,
21: "verificationprogress": 0.7432379893745559,
22: "verificationprogress": 0.7591546335013464,
23: "verificationprogress": 0.7755112799090741,
24: "verificationprogress": 0.7921896358067945,
25: "verificationprogress": 0.8087255859251153,
26: "verificationprogress": 0.8238380369120022,
27: "verificationprogress": 0.8390669815384693,
28: "verificationprogress": 0.8552901640231105,
29: "verificationprogress": 0.8702372187018386,
30: "verificationprogress": 0.8939735382422083,
31: "verificationprogress": 0.9077083890464666,
32: "verificationprogress": 0.9246245153988459,
33: "verificationprogress": 0.9385434003500938,
34: "verificationprogress": 0.9489972191119592,
35: "verificationprogress": 0.9542581918963842,
36: "verificationprogress": 0.9589770006924087,
37: "verificationprogress": 0.9668372904078799,
38: "verificationprogress": 0.9784829067702089,
39: "verificationprogress": 0.9874556287852982,
40: "verificationprogress": 0.997143865345627, Converted to progress per hour:  The dip after 7 hours may have been caused by internet congestion. During the first hours, the sync speed was limited by my internet speed. After 13-15 hours, it's clear that bandwidth is no longer the limiting factor. I'm not sure what caused the dip in progress at 35-36 hours: if I have to guess, blocks were mostly filled with Ordinals at that time. During the last hours, sync speed was limited by my SSD speed (and the lack of RAM).
It would be interesting to compare sync times between Windows and Linux, on the exact same hardware. Unfortunately, I don't have Windows to test this. |
|
|
|
And that's why you don't leave anything at any third-party service at all, be it 20 cents worth of sand or 2 million. It's usually not possible to withdraw everything. I have dust at various (abandoned) exchanges, and apart from the minimum, exchanges also add digits behind the comma that can't possibly be withdrawn. |
|
|
|
tell me If i should go forward with my idea. 2017 wants it's ICO back! The tokens will represent ownership of a specific square footage of the properties Lol. I've only seen this thousands of times. It used to be a great way to grab money and earn easy millions for the creator, but by now everyone knows it's a scam. So they moved to many new scams: Forks, DeFi, NFT, Ordinals and I have no doubt they'll come up with other scams in the future. $100 million to $500 million...so that's our goal to collect funds. [Read in a sarcastic voice:] Good luck with that  |
|
|
|
The workload is equivalent to downloading a 600GB file in your browser and scanning it for viruses. It's a lot more than that. My (laptop) sync is almost done, and my disk %util is now consistently around 96%. It has written 4.58 TB to disk in 42 hours. When it's done, I'll create a progress graph. the process of syncing your Core Node one time doesn't affect your disk life much if at all. For a modern disk, that's correct. My 2 TB Samsung has 1200 TBW. One of my old SSDs can only write 36 TB. It won't instantly kill it, but it takes a significant chunk out of it's life. |
|
|
|
I would use casino grade dices and test it for its bias before using it. How are you going to test this? |
|
|
|
•What damages can a malware cause to your wallet?
•What are the signs that your wallet being attacked by malwares?
•How can it be prevented? I think you're going at this all wrong. When it comes to malware, you should always assume the worst. Assume it's going to steal everything, and destroy all data on your computer. Once you've accepted that there is no safe online wallet, you can decide how to store your Bitcoins. So keep only small amounts on hot wallets for daily spending, and keep the majority of your coins safely offline. "clipboard malwares" See: How to lose your Bitcoins with CTRL-C CTRL-V. |
|
|
|
Another experiment: ./bitcoind -dbcache=4096 -prune=550 -datadir=/dev/shm/bitcoin I'll keep hourly status-snapshots again. I'm running this on a 6-core Xeon (E-2236) with 32 GB RAM and 1 GBit internet (and HDD, but I won't be using that). This took 11 hours and 10 minutes to sync  Unfortunately, I didn't store data from getblockchaininfo. Somehow bitcoin-cli couldn't connect to the daemon now. So I can't tell how the progress estimate changed over time. |
|
|
|
|
Show Posts
