Has the price of account risen recently? The starting bid of 0.06 is quite high for this account. If we want to bid, shall we bid 0.09? That is the BIN.
I thought 0.06 was quite low. You can bid 0.09 if you want, or you can buy it now for 0.09. I am auctioning off a Full Member account with the private key for the staked address.
--snip--
A signed message is available but the address staked is only a few days old because I forgot to stake an address when I acquired the account.
Are the private keys to the address that is only a few days old? If so then giving up these private keys is not going to be much good for the buyer. I hope that you at least have a signed message from the previous owner confirming the transfer of ownership to you. The address was staked last week, but it has been listed in the profile since I got the account. I do have a signed message from the previous owner confirming the transfer. |
|
|
|
Not so, because for two weeks with 8 (and sometimes more) "out" connections, bitcoin-qt was showing "no block source available" and not downloading the recent blocks.
That is, I had good connections showing at the time of the "no block source available" and had not knowingly changed any settings on the router and firewall when it stopped getting new blocks.
This evening it was typically listing 11 or 12 good connections but not updating.
The kludge in progress is to restart from a blank new /.bitcoin/ directory and download the whole blockchain, which seems to be working. This cannot be the proper way?
You want to check the debug window, it will give you more information. Specifically you should check the Peers tab and check each peer. Sometimes it will say you are connected to a peer when you really aren't. You will see that there might be no ping time or the times for the last send and last receive are really big, like several minutes. If you ever see a negative number there, then usually something is wrong as well. |
|
|
|
So how do I (and other Newbies here) learn about the encryption aspect - how do we encrypt a paper wallet?
I'm sure there's plenty of information available, perhaps you could point us in the right direction (if a simple explanation is not possible or appropriate.)
Bitaddress.org, one of the most popular paper wallet generators has the option to BIP38 encrypt the wallet. It is really easy to do. |
|
|
|
I got a similar "No block source available" in bitcoin-qt 0.10.4.0 about two weeks ago and no amount of firewall fiddling, rebooting, reinstalling the -qt wallet nor running with the -reindex option got it to synch.
After reinstalling bitcoin-qt,
bitcoin-qt -reindex
still got nowhere, sticking at 4 years and 46 weeks behind
bitcoin-qt -datadir=anewdirectory
might be working, but this will download and process 53GB
I'm wondering whether something like a .lock file in /.bitcoin/ had been wrong?
What is the proper way to sort out a "No block source available" fault testing for bad .lock files or whatever it is before (not after) opening firewall ports and so on?
about the only good news is that I'm now running bitcoin-qt v0.11.0 and it might catch up in a few days.
at least the little double-arrow round thing in the lower right corner is indicating progress and mouse-hover over it shows a block number which goes up from time to time.
No block source available indicates that you don't have a good connection to download blocks. reindex and the lock files don't matter to that. You want to connect to a good node. |
|
|
|
knightdk and/or shorena,
Do either of you get worried that the paper wallet will get lost or destroyed? Paper is such a delicate and pershible medium. I guess keeping the details of the wallet (the addresses) in multiple locations is wise and using something like Trezor or Armory is recommended but it really makes me worry having my bitcoin vault sitting in a safe in my home or office or bank...any of those places are vulnerable!
Yes. I keep multiple copies of paper wallets in various places. They are encrypted using BIP38 so that even if someone finds the wallet, they cannot spend the coins. If something were to happen to one of my hiding places, there are other places where I keep the same wallet so that the bitcoin doesn't get lost. |
|
|
|
I'm trying to use the -f <filename> but its not working ? Is it possible to search a whole batch of different patterns on the same run from a text file -f <file> File containing list of patterns, one per line (Use "-" as the file name for stdin) -s <file> Seed random number generator from <file> If so could someone please reply with the proper command line for say test.txt Thanks in advance  it would just be |
|
|
|
|
It would not be necessary to send all of the coins through the mixer, just the ones that you bought. Only those new ones are linked to your identity. After mixing them, then they would not be linked to you. However, this also means that the two addresses will be linked to each other, but they won't be linked back to you so it is ok.
|
|
|
|
So, the basic question is why would cpuminer be able to get 0.5 H/s per CPU for LTC mining while bfgminer can't even submit a single hash? Meanwhile, I get 40H/s on my 1.6GHz laptop... Something is not adding up here...
LTC mining uses scrypt. Is bfgminer started in scrypt mode? If it isn't, then it won't work correctly. What are you using on your laptop for mining? |
|
|
|
=
There's a connection. CPUs are detected and used. There's protocol-level dialog. The pool sees me connected. There is no work being submitted...
I can use cpuminer to create work on the same pool(s) that I've tested, and I've tried using bfgminer against multiple pools without success. So, I don't suspect the pools.
Any suggestions/ideas on what might be going on? Thanks for the help!!!
Not really sure why that may be the case. It probably has to do with bfgminer. bfgminer is not optimized for CPU mining so it may not be able to hash as quickly as cpuminer does. Honestly, I would expect that you don't submit any work when cpu mining because the pool difficulty is probably too high anyways. |
|
|
|
|
None of those transactions are on the network. Can you give us the raw hex of each transaction see we can check what is wrong with them? My guess as of now is that those transactions are mistakenly double spending another transaction.
|
|
|
|
|
You can export the private keys and still be able to access the Bitcoin. There is nothing stopping you from doing that.
It has the potential to compromise your wallet though. There was an attack (theoretical I think, don't really remember) that involved knowing the master public key and a private key and through those two, the master private key could be derived. I don't know the specifics to that though.
|
|
|
|
I'm learning as I go.... Blockchain provides a list of unconfirmed transactions( https://blockchain.info/unconfirmed-transactions?format=json). So I add a coin generation transaction(still lost on how to do this) to the top of the list and create a merkle tree from this list. This is how I get the Merkle root for my newly minted header. Now I perform the SHA256(SHA256(Block_Header)). Now through my coding wizardry I find a hash with the appropriate number of leading zero's in the first round(yea, I'm that good, lucky or whatever....). Any idea on how to send this winning header to the collective? I can't see (or don't know where to look for) documentation on this from Blockchain. Once again, thanks everyone for the help. Blockchain.info probably doesn't have information on this. For specific information on Bitcoin protocol stuff, you should read the documentation at https://bitcoin.org/en/developer-documentation. The guide and reference explain things very well. Everything that you want to do is supported by Bitcoin Core. Bitcoin Core has a console command which will allow you to submit a block to the network. It is aptly named submitBlock. The full documentation is at https://bitcoin.org/en/developer-reference#submitblock. To use it, start up Bitcoin Core and open the console in Help > Debug Window and then the console tab. Then just type where <block hex> is the hex string of the block's data. It will submit the block when you hit enter. |
|
|
|
I wrote a patch, but I haven't tested it yet. You can get the full source at https://github.com/achow101/BitcoinArmory/tree/pubkey-dump. All you really need is the armoryd.py file from it and replace the one you already have. edit: had to fix something. The latest version in that branch works. I tested it. |
|
|
|
|
I can probably add the function to armoryd for you. All of the functions are already included in the python code, it is just a matter of linking them to do what you want.
|
|
|
|
|
Not necessarily. You can spend some coins and have the change return to the same paper wallet address, but this is not recommended. It is recommended to use a new address for the change for every transaction, so you should create a new paper wallet for the change to go to.
However, you should not be using paper wallets as your every day wallet for spending. Paper wallets are meant for cold storage. They are like vaults, you put money in and wait a while until you need to withdraw it. Instead, you should have some amount of coins stored in a hot wallet where you do your spending from. And then when you need it, you can go and retrieve the coins from your paper wallets, but it should not be used if you want to spend from that wallet.
|
|
|
|
|
AFAIK there is no way to do that. You would have to write your own code and add it to armoryd in order to have such a function.
|
|
|
|
Obviously I won't do that, but when I don't post anything, and lets say my sister logs in and posts photos of me or my full name and the school I go to and where I work and so on, that is doxxing which is against ToS.
ToS of what? This forum doesn't have any ToS. If it does, please show it to everyone. |
|
|
|
Bitcoin is anonymous. Let's keep it that way.
"Bitcoin is not anonymous" - Bitcoin.org [You need to know]Oh yeah, I'm calling bullshit on the whole thread. "Some effort is required to protect your privacy with Bitcoin. All Bitcoin transactions are stored publicly and permanently on the network, which means anyone can see the balance and transactions of any Bitcoin address. However, the identity of the user behind an address remains unknown until information is revealed during a purchase or in other circumstances.This is one reason why Bitcoin addresses should only be used once". In any other circumstances would mean revealing the actual identity BEHIND the bitcoin address, meaning doxxing. No it does not mean doxxing. Other circumstances can mean many many different things. It could be voluntarily giving away your information, it could be doxxing, but doxxing is just compiling publicly available information into one location. If you can be doxxed, then your identity is already revealed BEFORE you were doxxed. It is another matter if hacking was involved. |
|
|
|
Nope, doxxing is allowed, from the stickied rules thread in meta made by a moderator Q: What about deleting DOXes?
A: Nope, we don't delete them either as long as they are on topic. Why? Because doxing is just compiling information about a user already available publicly, often via search engines.
Bitcoin is pseudo-anonymous, meaning that if moderators were to go against what Bitcoin stands for, then they would be banned.
-snip-
Bitcoin is anonymous. Let's keep it that way.
And why would mods be banned? They don't break any rules. Besides, you literally just contradicted yourself. Bitcoin cannot be pseudonymous and anonymous at the same time. Plus, this site is ran via VPN. Coincidence? I think not.
No its not, it is sponsored by a VPN business but it is not run via VPN. |
|
|
|
|
Show Posts
