 Show Posts
|
|
Pages: [1] 2 3 4 »
|
|
Hello
I lost my bitcoin node. I have my rpc username/password. My wallet.dat and keys all backed up
I installed a new bitcoind instance to run a full node. I am trying to get my bitcoins
I have setup a new bitcoin.conf file w/ old rpc username and password
I imported my wallet.dat file to replace default
I cannot start the server. Could't connect to server: unknown (code -1)
Can someone please advise.
How do I get my wallet (bitcoins) -> what is the best way. If I have the wallet.dat, passphrase, privkeydump...
Thank you,
|
|
|
|
If you do not see how it is bad, then you do not understand the importance in miner incentive and the model of decentralization. If three pools are responsible for 75% of mining hash, to me, this is centralizing the control of incentive for mining. The simple fact that companies like BitMain (Chinese) are making the software in their antmining products read-only is also sketchy. You buy hardware that remains in control of the largest mining pool? You cannot change default ssh passwords? Pretty sketchy.
Decentralization is termin related for bitcoin not for mining. Bigger question is distribution, and it is not so good. Decentralization is guaranteed because no one controlling bitcoin as one entity such as banks or government, and this is accomplished using wallets, and transaction through blockchain.. You missed my point. I am saying that the centralization of mining is on course to be a major problem. If for some reason China went offline - this would be a major threat to bitcoin based on the centralization to mining coming out of China. What is the impact on Chinese mining perception towards an increase in block size given the government limitation on throughput? I guess we would find out how many Non-Chinese miners are using Chinese pools - because they would be forced to relocate. And this is a pretty interesting exercise. |
|
|
|
So basically everyone in the US that points there miners to a Chinese pool is basically screwing themselves and the whole BTC community outside of China.
I don't see how it this bad? Bitcoin have nothing with this. You can mine it or buy it. Only if you don't like China economic growth supported with this mining farms (but this is insignificant at the global level). Bitcoin is good because you really don't need to know who was previous owner and where is mined, this is point! If you do not see how it is bad, then you do not understand the importance in miner incentive and the model of decentralization. If three pools are responsible for 75% of mining hash, to me, this is centralizing the control of incentive for mining. The simple fact that companies like BitMain (Chinese) are making the software in their antmining products read-only is also sketchy. You buy hardware that remains in control of the largest mining pool? You cannot change default ssh passwords? Pretty sketchy. |
|
|
|
How can mining be decentralised it is associated with price of mining and electricity, and if you can get cheap electricity, you will get more BTCs this can be changed in future. And most of btc will hold investors who are willing to buy them no matter where they live in China or Europe.
If Satoshi wakes up i doubt he will kill his child.
So basically everyone in the US that points there miners to a Chinese pool is basically screwing themselves and the whole BTC community outside of China. |
|
|
|
any reason why not the s7?
it would be very hard for him to do to the s5/s7 that he did for s3 because the s5/s7 use a read only file system. so once you reboot it, it will get set back to stock  Is this why I can't change the root ssh password? Chinese need their backdoors. It wont be a backdoor unless you leave your router wide open as well. Still, passwd doesnt work? Password works but only default. If you change the ssh password (which is a pre-req in my book) it just reverts back to "admin" Yes - I am a networking/security professional so I build my own firewall, virtual servers... all open source. Not Password to login. passwd, to change the password, worked for me. You probably know already, since you're a networking/security professional, but this is how to use passwd; passwd root newpass newpassagain http://www.cyberciti.biz/faq/changing-password-of-specific-account-in-linux-commandline/This revert the password to admin? yes it does. |
|
|
|
any reason why not the s7?
it would be very hard for him to do to the s5/s7 that he did for s3 because the s5/s7 use a read only file system. so once you reboot it, it will get set back to stock Is this why I can't change the root ssh password? Chinese need their backdoors. It wont be a backdoor unless you leave your router wide open as well. Still, passwd doesnt work? Password works but only default. If you change the ssh password (which is a pre-req in my book) it just reverts back to "admin" Yes - I am a networking/security professional so I build my own firewall, virtual servers... all open source. |
|
|
|
I am curious...is the basic root cause of the problem simply bad hardware/firmware or is it something that could be seen as intentional?
There's 2 issues. 1) I can't tell what the hardware is, they use a proxy 2) It's almost certainly intentional since they've changed things around since I commented about it and they 'tried' to avoid being found. Most of the accounts where created in Jan, then no changes for 1.5 months, then 11 switched to address accounts over the last 3 days. how much hash power are we talking? thats a great question considering how much ~25% is gone from this past weekend when we were peaking right before the long drought. |
|
|
|
|
800,592.01812447 BTC - block
Holy Toledo Batman
|
|
|
|
go tich go! Nice $20k in 23minutes. not to shabby  |
|
|
|
|
This past weekend dry spell - was it just luck (or lack of) or technical? Both?
Also with the block we missed 402609 - is there anything I can do on my node (add CKPool node?) that might of helped get the relay out to more nodes?
THanks,
|
|
|
|
any reason why not the s7?
it would be very hard for him to do to the s5/s7 that he did for s3 because the s5/s7 use a read only file system. so once you reboot it, it will get set back to stock Is this why I can't change the root ssh password? Chinese need their backdoors. |
|
|
|
|
any reason why not the s7?
|
|
|
|
|
who is BCMonster? And how does AntPool constantly win the empty blocks. Is there nothing the network can do about that? So frustrating to see those empty blocks getting solved.
|
|
|
|
Everyone keep in mind that this is all speculation at this point. Kano has not come right out and said what is going on. He hinted towards something in a couple posts, but let us wait until he confirms things himself. I sure he wants to get it all sorted out and be sure of things before he says anything.
The only good thing if it was an attack is that it can be fixed. Then we can get back to block busting. |
|
|
|
coinbase sent email saying ghost block has been sorted out.
I need to check.
BTC inbound. Excellent. Was the analpaper block.
yep it has been credited to my account. Thanks for posting the heads up This was for 401983 - it was sent out by Kano right away. It was Coinbase that "misplaced" it? |
|
|
|
That's weird...I received payments for 402505, 402347, and 402342 that came after 402133. Of course, I never got payment for block #401842 that made it to Coinbase but not into my wallet (along with several others here as well). No replies from Coinbase yet on that one.
I have a case opened with them. They have escalated and asked me to provide my wallet address (again) and the amount. They are looking into it. I have since moved my kano.is payments to a personal wallet. |
|
|
|
it looks like today there is 2511 classic nodes to 1500 core nodes any thoughts.  this site says otherwise: https://coin.dance/nodescore is still 61% This post -https://bitcointalk.org/index.php?topic=1355337.0 Says that most of the bicoin classic nodes have just been brought online and are straw men? |
|
|
|
I just wonder why Gavin is so sure that "thousands of Classic nodes will appear". They didn't appear for XT. Maybe, he knows that "a little help from unknown friends" is sure to come...
I thought the post was pretty clear, it was " People are committing to spinning up thousands" and 'not thousands of people are committed to spinning up a node'-- it's a planned sybil attack-- and that is also what I've seen from this rise of "classic" "nodes". There are several less obvious node count measures that don't show the growth. AFAICT, the latest strategy is to fake out the node counts with large numbers of sybils and then try to use that to pressure miners into adopting classic; which would then pressure actual users to go along with it. This isn't going to work, and most charitable way I can explain the strategies used by the people frantically pushing for a controversial hardfork is that the people involved in these forks keep thinking that everyone else in Bitcoin is stupid. How else can you explain the faux urgency-- that almost no one bought-- or the bait and switch policies for miners-- to the cheap characterization that Bitcoin Core is all blockstream and so on? All these nonsense and attacks frustrate me-- they waste a tone of time and energy that could be used driving Bitcoin forward. So for those that believe in bitcoin to be a decentralized currency. And agree with the fundamental disruptive potential for bitcoin - what should we / can we/ do? I run a full node of bitcoin core. I do believe that the bankers and gov's will try to control this. What can I do? |
|
|
|
Yep as it says now on the web site, it's an orphan. The timing was very close so it simply depended on if anyone saw our block first, but that was unlikely due to the timing. So basically we sent our block out on the relay (000026e9) but then got the other one (00001735) before ours came back The relay is clearly running slow  We sent, then got the other one 652ms later, then finally got ours back 1537ms later. i.e. they had sent it out on the relay just before we did, but we didn't get it from the relay until after we processed our block (which only took 240ms) and sent out our own Is there anything I can do on my node that would of helped propagation? |
|
|
|
|
