So long as you are sure. Is the case a big heatsink or is there a fan? There's a fan. Actually TOR might be the issue, I am re-syncing 2 nodes on the exact same hardware one TOR on clearnet and as of now the clearnet is at 55% and the TOR is below 40% done.
You should have told me this before I waited over three weeks to finish.  Anyway, now that I know what is probably the issue, I'll change the configuration file if I ever need to resync it again. I need Tor to connect with my node outside home. I don't know if it's possible to run both on clearnet and connect with Tor. How did my testnet node finish syncing within hours, though? It runs over Tor too. |
|
|
|
enable debug logging in the client and see what it says: I did and I guess that's the faulty part: 20210926T061438.669179Z | INFO | interface.[192.168.2.7:50002] | connection established. version: ['electrs 0.8.11', '1.4']
20210926T061438.669179Z | INFO | interface.[192.168.2.7:50002] | set blockchain with height 702243
20210926T061438.669179Z | INFO | interface.[192.168.2.7:50002] | can't connect 2096356
20210926T061438.669179Z | INFO | interface.[192.168.2.7:50002] | requesting block header 702244 in mode backward
20210926T061438.669179Z | INFO | network | switching to 192.168.2.7:50002:s
20210926T061438.684803Z | INFO | gui.qt.ElectrumGui | Qt GUI starting up... Qt=5.15.2, PyQt=5.15.4
20210926T061438.684803Z | INFO | network | fee_estimates {25: 1000, 10: 1000, 5: 1000, 2: 1000}
20210926T061438.684803Z | INFO | interface.[192.168.2.7:50002] | requesting block header 659231 in mode backward
20210926T061438.684803Z | INFO | network | fee_histogram []
20210926T061438.684803Z | INFO | interface.[192.168.2.7:50002] | disconnecting due to GracefulDisconnect('server chain conflicts with checkpoints') I dug up the code a little bit, searching what's that GracefulDisconnect and it turns out that it can't search the block headers backwards. Although, I don't understand how it conflicts with checkpoints and which checkpoints are those. But, that's probably what's wrong. It, then, retries connecting, but gets the same disconnection error. Edit: No one has faced this before.  |
|
|
|
Total mined as at present = 18,375,000 mined in the previous halvings + the mined blocks after block 630000 To be ghastlily pedantic, this is a false way to assume the total coins issued. It'd be correct if it was mandatory, by a consensus rule, for each block to have a specific reward in each epoch. But, a miner can choose to issue no bitcoins if they want to. They're free to secure the network by only acquiring the network fees or even dumping those too; although none does. However, there have been cases where the miner lost the block reward either by accident or intentionally. Check block 124,724. The miner destroyed 0.01000001 by deciding to earn 1 satoshi less from the block reward and by burning the fees. |
|
|
|
How is your cooling? Thermal throttle can be a big issue with RPis at times. The case I have covers the cooling part. What type of USB drive are you using? A 1TB external one with USB 3.0. Specifically, this one. (Yes, I plugged it on the 3.0 port)Are you downloading over clearnet or TOR? I'm downloading over Tor, but I don't think that's the issue. I believe that what's taking so long is the verification of those blocks. I would make a backup of the blockchain files someplace for now, so if you ever have to or want to do it again you have a known clean copy of the blockchain up to today. Well, a backup would require another 1TB disk. Is it that necessary? Have you ever experienced a hard drive issue from a power surge? |
|
|
|
I've setup my electrs as it's written in here except from the directory's name. I had chosen “electrs” for my test net server so I couldn't choose the same for main net. Thus, I named it “electrs_main”. Node works fine, server works fine and once I run: electrum.exe --oneserver --server=192.168.2.7:50002:s This is what it returns me in the Linux console (from my Pi): Sep 25 10:46:15 raspibolt electrs[2722]: 2021-09-25T10:46:15.378+01:00 - TRACE - RPC Request("{\"jsonrpc\": \"2.0\", \"method\": \"blockchain.block.header\", \"id\": 22, \"params\": [659231]}\n")
Sep 25 10:46:15 raspibolt electrs[2722]: 2021-09-25T10:46:15.383+01:00 - TRACE - RPC Done
Sep 25 10:46:15 raspibolt electrs[2722]: 2021-09-25T10:46:15.383+01:00 - DEBUG - [127.0.0.1:48976] shutting down connection
Sep 25 10:46:15 raspibolt electrs[2722]: 2021-09-25T10:46:15.384+01:00 - INFO - [127.0.0.1:48976] disconnected peerAnd then it repeats. It continuously tries to establish a connection and reads my balance, but fails and I remain disconnected. (The test net server works fine) |
|
|
|
Your questions aren't very clear, but I'll give it a try. So when I want to calculate P = Q + R, what does that actually look like in terms of which parts of the public keys to use? Let's take your public key which is Q: x: F11D0ECD3686E66695A3B28555264F9EF60EFEDF905BE79E2937F7FA1BA3317E
y: 9002C25FB82362A4EDCA54A6DE49C78448F5DA2264B5E944D116A9D8A7769F59 And another public key R. In this case, I'll just take the point G to simplify: x: 79BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F81798
y: 483ADA7726A3C4655DA4FBFC0E1108A8FD17B448A68554199C47D08FFB10D4B8 Now, you'll have to perform ECC addition of those two points (Q + R) which will give you this P: x: 89B9A2CC85F56A5B29E72711D95159CF4C80C2787F1716C38762C7DEACC29D8A
y: 64B2D208EFA41213F4924542ABFD245AA7228754FDDDC9006AEA3BCC75F2C6F6 This new point's private key is the private key of Q plus the private key of R or in this case, it'll be the private key of Q plus 1.
If you're asking what are the maths behind ECC addition, take a look in here: Adding Points in Elliptic Curve Cryptography |
|
|
|
I very much agree with this: Start small and play it safe. Purchase bitcoin, hold it and be happy that you still belong to the early adopters. Most of the newcomers assume that it's too late to invest in Bitcoin and decide to touch altcoins whose market cap is much lower. Indeed, they're more likely to go upwards percentwise than Bitcoin, but they're also more likely to go downwards or completely disappear. In this unethical crypto-industry, there are many hidden dangers such as Ponzi schemes or scams. In my opinion, even experienced traders should avoid dealing with such projects unless they're the creators or are related with the creators. I'd also avoid margin trading. It's gambling squared. |
|
|
|
I just needed few clips from articles i could read for more details on how i could achieve what i wanted But, how can we know those few clips if we don't firstly understand what's your issue? You said you're having some tough problems when you try to run a full node; please elaborate! Was this an older 2GB unit? Slow internet? something seems off. Well, no. I'm not having an older 2GB unit neither a slow internet connection. Does it matter if I've set txindex=1? I'm running both main net and test net, but that shouldn't be the issue. I really don't know what went that wrong. The synchronization started in 30st of August and ended yesterday. (Almost a month) |
|
|
|
|
You've mentioned all these, but not the most significant: How does mining actually work?
It is very important for the beginner to know what their computers are calculating. What's the procedure theoretically. For instance, they should understand what's proof of work and that they can enter a random number as a parameter in a function called SHA256 that will return a completely unpredictable result. That the computers just try different combinations until they've found a number which is lower than another number we've decided to not exceed to consider the block valid.
The beginners should be educated about the essentials first.
|
|
|
|
I mean I guess they could find someone with a torrent of a snapshot or even a zip, download it to the blocks/ folder and then start core; But, that wouldn't make the process finish sooner. Once you would have downloaded all the blocks it'd require you to verify them which is the main reason it takes so much time. You can change the way your node will synchronize with the network, but not the time it'll take. There's no faster way other than running bitcoind from your cmd. |
|
|
|
Who the hell calls humpbacks those who own more than 5,000 BTC? LOL. Also since when these fish are bigger than octopuses? Subjective dictionary. No one is ever going to use these terms, so they were picked for fun as said by mk4. You'll choose to either name me bitcoiner, no-coiner or whale. The in-between categories are just excessive. (Also, change the image size dude!) |
|
|
|
Assuming your problem is that you don't have an answer to this question: * is there any smart way to download the whole block chain ? There's no smarter way to receive anything in the internet other than downloading it. There's also not a smarter way to run a full node. You're “doomed” to connect with the peers of the network, receive blocks, verify their validity and repeat until they have no other blocks to give you. Once that happens, you'll have the most recent version of the block chain. As long as there are valid blocks waiting to be verified from your computer, you'll have to let it finish. With my Raspberry Pi 4 it has taken around a month to finish. It should take less to you if you're having a better CPU than my Pi's. (Which you'll most likely have) |
|
|
|
No I don't want to steal just check a list of keys may be 10M keys But, if you ever found a balance from a list of 10M keys, it'd essentially be stealing. Those funds wouldn't be yours; you would have found another person's keys. Anyway, I'm not going to prevent you from doing this. That's the point of the large ranges used in cryptography; to make brute forcing meaningless. If you want to generate 10M keys and check if they have a balance, you should pick a random number between these two: [1, 115792089237316195423570985008687907852837564279074904382605163141518161494336] Now you should write a script that'll take the number and the next 10M and will convert them into WIFs. That's an easy thing to do. You should then synchronize with the network using a full node and query all those keys. To do so, running an Electrum server will make things easier. You should connect your Electrum server with your full node and then your Electrum client with your Electrum server. Now you can create a wallet by importing private keys and it'll return you their balances. If you have any questions tell me. I'm willing to help you achieve all the above, I just find it honestly a loss of time for you. |
|
|
|
How will this impact Bitcoin and other cryptoprojects?? What do you think guys? I think that we keep reading the same news. China's reporters announce that it became illegal once again. They, then illegalize mining. Price drops temporarily. There's fear for a week. The #Bitcoin hashtag becomes relevant in Twitter and most of the verified Bitcoiners spit some wise words and why Bitcoin cannot die. It's a loop and I hope China someday realize that if they want to retain their socialism, they'll have to either cut off their internet connection or accept the fact that Bitcoin is going to affect their economy one way or another due to the fact that it's available in capitalistic nations too. |
|
|
|
Genesis address is different from the rest of the bitcoin addresses, consensus rules prevent you from spending bitcoins from the Genesis address even if you have its private key. Actually they do allow you. You're just unable of spending the genesis block's coinbase UTXO. The address has 18.52264025 spendable bitcoins sitting in the dust. Quite huge amount if we're talking about crackable puzzles. I'm not falling for anything here. I am only interested to know who the owner of these 1.2 BTC is. This is what I was asking too. It turns out that some people intentionally left some BTC to be found from individuals. It's probably a way to test the system's security. The money is the incentive for their work. Here's another puzzle: Bitcoin puzzle transaction ~32 BTC prize to who solves it |
|
|
|
On can send millions of dollars through Bitcoin with a small fee and at a faster way without any third party involvement. Is that it? Let me add more about financial independence; - No permission. Wherever you are, if you're internet connected you can install the software and enjoy it.
- Censorship-resistant. No one can decide to exclude my transaction from the ledger. No matter the excuse.
- Fixed inflation which constantly decreases. This guarantees that you own a specific part of the system and that it won't be devaluated in the future unless the market cap does.
- Better privacy than before. There's no third party to sell private information such as which services you paid etc.
|
|
|
|
Some governments are currently talking about the potential for "programmable" central bank digital currencies, which would allow the central banks to dictate where you can and cannot spend your money. It sounds utterly horrifying. Such a thing will 100% never happen with Bitcoin. It sounds utterly horrifying the way you've put it. A government may or may not dictate the way money circulates. But, the government has to somehow have a role in its currency; it can't leave the people responsible for the state's economy. The government has to intervene in businesses to maintain law & order. It has to protect the citizens from living a free market. So, unless you want a complete disappearance of the state's intervention to the society, what you were trying to mean is oxymoron. Either way, a society being preserved solely from Bitcoin sounds much more horrifying to me. |
|
|
|
Do you guys have any suggestions on how to explain coins to non-crypto people? Question them the following: What if I told you there's a currency which isn't regulated from any authorities and each user has equal rights upon it? That the tasks of securing the system are managed collectively by any user who wants to participate in a mathematical procedure? If they have their doubts of Bitcoin being completely independent from any “Administrators”, mention terms such as public-key cryptography, peer-to-peer network and open-source software. If they insist that you're wrong, tell them to provide some counter-arguments (since they won't have provided, but just canceled you prejudicially). You've done your best on convincing them it's decentralized and it'd be advisable to message those people some useful links which would make their opinion less prejudicial.
Don't fault them; Bitcoin isn't an easy term to understand. |
|
|
|
|
Show Posts
