 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
|
I finally have a real USD bill, in almost a year. How much BTC can I earn by writing something on my $5 bill? And exactly what do I write on it? I am partial to "What is Bitcoin?" on one side, and "A better currency!" on the other side, and weusecoins.com and bitcoin.org somewhere too. But I don't want to cover up anything, just on the edges of the bill.
|
|
|
|
Do you ever plan to implement proof that your games are fair?
Sure if there is demand. You're only the 2nd person that's ever asked me. I put my time so far into getting it just to work. Bitcoin Darts has proof that it's fair, so it mustn't be that hard to implement. As for working, Ha, it's not working at all for me with Chrome. I can't register, or log in. I'm giving up till it works. |
|
|
|
Any other client in the world. And it can have the same keys because you can load your keys into any client you wish. You'll have to manually construct a wallet that contains all your keys but not the hung transactions.
How do I load my keys? How do I manually construct a wallet that has my keys, but not the hung transactions? You think I'm a dev? You think I'm a programmer and can just DO stuff like that? I've used hex editors before, but I don't KNOW what to do with one, it just seems neat to be able to see unscrambled stuff that a normal text editor wouldn't be able to decipher. What, I open my current wallet with a text editor, copy the stuff I want to a new wallet.dat, and ignore the hung stuff? How do I separate out the good from the bad? I Do Not Know What You Are Talking About! Ok, so, I uninstalled bitcoin from windows, it may be messed up somehow, but I dunno. I have a plan. At some point I'll switch this windows Hard Drive for my Linux hard drive which has a more recent copy of my wallet on it, but it doesn't include all those hung transactions, just he one from months ago, I'll run bitcoin there and let it update the block chain. Then I'll see if it has all the transactions it should, not including the hung ones of course. If it does, Yippeeee, I'll just copy that wallet to my external drive, and use that on windows. Lessons learned from all this? Always backup my wallet, and keep multiple backups for different periods, say maybe once a week or something, and keep a month's worth of backups, or something. Or maybe backup my wallet before EVERY payment I make, that way if they get hung and totally unresponsive, I can backtrack to an earlier backup, wiping out the hung transactions. As for your advice, sheesh, you're just confusing the daylights out of me. I wonder how a non-computer literate person would handle this mess. |
|
|
|
Nothing is forcing you to use that client. If another client has the private key corresponding to this account, it will show the correct balance and it will allow the transfer. The issue is 100% localized to that particular client. As far as the rest of the world is concerned, you have your full balance and are free to transfer it. Just stop trying to perform the transactions on the busted client. Perform them on some other client that also has the same key(s).
I don't understand what you are talking about. What other client, and how would it have the same key(s)? I've tried loading an old backup of my wallet, it didn't work out very well. Sure, those hung transactions were not there, as they only existed in the wallet, not the block chain, but a bunch of other transactions that Should be listed, from the block chain, were not because the wallet was too old, didn't have the same bunch of addresses in it as the newer copy. So, since I haven't been backing up my wallet regularly, I can't load one that would include all the blockchain transactions, but not the hung transactions that only exist in this wallet. So, now what? |
|
|
|
Look at rpc.cpp for the list of commands.
Seriously? So, everyone knows C++ but me? I don't understand where this list of commands is in this file. *sigh* I have tried to understand C++ for years, things just are not clicking in my head for some reason. Do you mean this stuff? //
// Special case non-string parameter types
//
if (strMethod == "setgenerate" && n > 0) ConvertTo<bool>(params[0]);
if (strMethod == "setgenerate" && n > 1) ConvertTo<boost::int64_t>(params[1]);
if (strMethod == "sendtoaddress" && n > 1) ConvertTo<double>(params[1]);
if (strMethod == "settxfee" && n > 0) ConvertTo<double>(params[0]);
if (strMethod == "getamountreceived" && n > 1) ConvertTo<boost::int64_t>(params[1]); // deprecated
if (strMethod == "getreceivedbyaddress" && n > 1) ConvertTo<boost::int64_t>(params[1]);
if (strMethod == "getreceivedbyaccount" && n > 1) ConvertTo<boost::int64_t>(params[1]);
if (strMethod == "getreceivedbylabel" && n > 1) ConvertTo<boost::int64_t>(params[1]); // deprecated
if (strMethod == "getallreceived" && n > 0) ConvertTo<boost::int64_t>(params[0]); // deprecated
if (strMethod == "getallreceived" && n > 1) ConvertTo<bool>(params[1]);
if (strMethod == "listreceivedbyaddress" && n > 0) ConvertTo<boost::int64_t>(params[0]);
if (strMethod == "listreceivedbyaddress" && n > 1) ConvertTo<bool>(params[1]);
if (strMethod == "listreceivedbyaccount" && n > 0) ConvertTo<boost::int64_t>(params[0]);
if (strMethod == "listreceivedbyaccount" && n > 1) ConvertTo<bool>(params[1]);
if (strMethod == "listreceivedbylabel" && n > 0) ConvertTo<boost::int64_t>(params[0]); // deprecated
if (strMethod == "listreceivedbylabel" && n > 1) ConvertTo<bool>(params[1]); // deprecated
if (strMethod == "getbalance" && n > 1) ConvertTo<boost::int64_t>(params[1]);
if (strMethod == "move" && n > 2) ConvertTo<double>(params[2]);
if (strMethod == "move" && n > 3) ConvertTo<boost::int64_t>(params[3]);
if (strMethod == "sendfrom" && n > 2) ConvertTo<double>(params[2]);
if (strMethod == "sendfrom" && n > 3) ConvertTo<boost::int64_t>(params[3]);
if (strMethod == "listtransactions" && n > 1) ConvertTo<boost::int64_t>(params[1]);
if (strMethod == "listtransactions" && n > 2) ConvertTo<boost::int64_t>(params[2]);
if (strMethod == "listaccounts" && n > 0) ConvertTo<boost::int64_t>(params[0]);
if (strMethod == "sendmany" && n > 1)
{
string s = params[1].get_str();
Value v;
if (!read_string(s, v) || v.type() != obj_type)
throw runtime_error("type mismatch");
params[1] = v.get_obj();
}
if (strMethod == "sendmany" && n > 2) ConvertTo<boost::int64_t>(params[2]);
Well, there are comments throughout, so that's good, I really get annoyed by spaghetti code. |
|
|
|
I have succeeded in running two bitcoin instances... sort of. I've got the normal GUI running my old wallet, but I could only manage to get the headless daemon to run my new wallet, with this command: c:\program files\bitcoin\daemon\bitcoind.exe -datadir="m:\bitcoin\new wallet" -connect=127.0.0.1 -nolisten That way it connects to the already running instance, with the port open as normal, but won't try to listen on it's own port, since the port is already open that wouldn't work at all. There, two instances of bitcoin... sort of, on the same windows machine. Hmmm, I wonder, what if I tried those commands on the gui, could two gui windows come up? Let's see. Nope, it won't run, it tries to, but eventually kills itself for some reason. I'm sure I can look at the debug.log to see why. |
|
|
|
|
I am apparently unable to run more than one instance of bitcoin on windows, at least being run by the same user. Is there any way to run two instances,
with two wallets, on windows? Maybe create a new user and run it from there?
|
|
|
|
You can only set up your NAT to port-forward to one of the computers.
<snip>
For redundancy in case the first computer goes down, you could have two that connect out and the rest connect to both of them. The first two are run normally, the rest are run like:
bitcoin -connect=<IP1> -connect=<IP2>
I agree with the first statement (you can only forward the port to one computer). Therefore I do not understand the second statement. How does this achieve redundancy? Only one of the two will receive forwarded traffic. If that one goes down then you've lost the connection (AFAIK). Am I being dumb? I can think of how it can be redundant, if the second connect command is connecting to a known, usually running, node Outside your own network, a public IP address. There, redundancy achieved. |
|
|
|
Your balance, as shown by your client, is totally irrelevant. All that matters is what your balance is according to committed blocks in the chain and unconfirmed transactions known to miners that aren't blocked by conflicting transactions.
You can completely ignore the balance shown in your client. It's purely for your convenience.
I don't know whether you've ever used this client or not, but it seems like you haven't. It is not totally irrelevant, unless you know how to get around the client saying you can't do something because you don't have the funds in your balance. How about a picture to illustrate, since you clearly do not understand what I'm talking about.  |
|
|
|
|
Well I did what you suggested, I have a new wallet, I told bitcoin to transfer all of my remaining bitcents to my new wallet, and I've been waiting and waiting and waiting for Any confirmation at all. None. Now I'm totally broke, with All of my bitcoin money hanging in limbo. Nothing is happening. Am I doing something wrong? Am I supposed to have two instances of bitcoin running at the same time with two wallets at the same time?!
|
|
|
|
Thanks Theymos a huge bunch!  Now, how do I load this into a spreadsheet? Hmmm... |
|
|
|
I still don't understand. I can blow away all the files except my wallet, and address book, sure, but my wallet keeps a history of all my transactions, not just the block chain database. So, blowing away the block chain database won't give me back my limbo transactions. Sending bitcoins again to those addresses in limbo won't bring back my limbo transactions, I'll just use more money, and still have limbo transactions. I have no intention of never using this client again, that's silly, the client isn't doing anything except working with the data in my data directory. If I switch to another wallet, then I can use that as a different account, but I'd have to run bitcoin with the new wallet, copy a receiving address to notepad or something, shut down bitcoin, run it again with the older wallet, transfer whatever remains in my account to my new wallet...*deep breath*, wait a while for that to announce, shut down bitcoin, run bitcoin with my new wallet, and wait for the network to confirm the transfer... *deep breath* Then what? My old wallet will still have stalled, limbo, transactions, and trying to do any further transactions with it will not work because it will say I have 0 balance! I keep telling you, my bitcoin client won't let me send a conflicting transaction with money that is not available. Most likely, that last transaction will go through because your 'stuck' transaction never went out at all. But you don't have to worry about it every getting out if you keep that account empty. But it Won't be empty, that's what I keep trying to explain to you, as far as my wallet is concerned the money has already been spent, but is unconfirmed, I won't get it back, the way you are explaining things. I'll just spend more money, and still not have the 40 bitcents! And how would sending the same amount to the same address be a conflicting transaction, exactly? It would still be seen as a New Separate transaction. And the addresses that I would send to, for Bitcoin Darts, are one time use only, so maybe I'd finally see the darts games complete, and maybe get something in return, but those limbo transactions Still won't be fixed. Nothing you have suggested makes any sense to me. I'm still completely confused. I'm going to blow away the stuff in my data directory and let bitcoin re-download everything, except of course for my wallet and address book. I'll see if that helps it finally get those hung transactions announced. If not, I'll eventually be back to where I was.  Here it is, all 0/unconfirmed, no blocks downloaded, now the waiting and wringing of hands, feet, and ears. Ok, as far as my client is concerned I have 0 balance. I can try spending money right now, and nothing will happen. Yup, "Amount exceeds your balance". I can wait for enough blocks to download that it shows I have more money in my Balance than I really do have, then try to spend money I don't really have, weeeee, what fun. |
|
|
|
In any case, this idea that you can perform a conflicting transaction on another client does not help me with my current problem. Is there absolutely NO WAY at all to either push these transactions through the network, or get my money back from this limbo it is stuck in?! Your money's not stuck. Your client is stuck. The simplest solution really is to issue a conflicting transaction from another client. Huh? I don't understand. So, install another copy of bitcoin, load my wallet, and do what? |
|
|
|
|
I've been running bitcoin with microsoft security essentials for a long while now, and it has always been able to get blocks. Port forwarding on my router was simple, it supports UPnP, which I like using. I discovered that running bitcoin caused MSSE to grind away at the hard drive excessively, so I added the bitcoin data directory to the exceptions list, and it calmed down right away. I just now added the bitcoin application to the excluded processes list, just in case that might become a problem some day. I'm running the newest version of Bitcoin, so, maybe that's why it didn't have trouble getting blocks, I dunno.
|
|
|
|
Didn't intend to. I only want to know how much I received in each address, so that I know whoever was supposed to pay me did. Whatever crazy things the client does later to rearrange my funds is not interesting. [/quote] I am not sure what you are describing. Are you talking about what you are seeing on block explorer, or what you are seeing on the bitcoin UI? Because block explorer says that some random amounts will be sent, by your client, to other addresses you own, in the background, in order to obscure exactly how much money you are getting in any transaction, doesn't it? Even though it won't be shown in the UI, the UI reports the full payment coming into an address, not the obfuscating stuff going on in the background. As for knowing whether someone sent what they were supposed to or not, Isn't that why we have Labels for incoming addresses on our bitcoin UI? For instance, I use the same incoming address every time I play Bitcoin Darts, and it's Labeled Bitcoin Darts. That way I know which payments are from Bitcoin Darts, and which are from someone else. Even though Bitcoin Darts is probably sending from different addresses every time, so block explorer would be too confusing to use to figure stuff out. |
|
|
|
|
I just had an idea, make the bitcoin client create a backup snapshot of the wallet, regularly, and put it somewhere else, other than it's normal data directory. People aren't all as computer literate as the geeks like me. Backups are important, this must be stressed very loudly. If the bitcoin app won't do backups, at least have it pop up a reminder when it runs that you should backup your wallet, and have a link to the help file for how to do it. Just a splash screen, with the bitcoin logo, and a reminder to backup your wallet, and secure it.
Sorry dude, if you never backed up your wallet, and your computer is toast, it's as if you lost your Cash in a fire that burned your house down. There is no getting it back. Hey, maybe someone should provide a Bitcoin Insurance service, wow, what an idea! You pay them, say, 1 BTC every month or something, and they guarantee your losses, should they occur. Unfortunately this would open up an opportunity for fraud, hmmmm.... I dunno how to deal with that. I sure wish someone would send me 40 bitcents to counteract the hung transactions on my client that absolutely will not be processed. I'd pay into a Hung Transaction Insurance program, ha!
|
|
|
|
If they're only on your client, you can perform conflicting transactions on another client. [/quote] Yah, so, conflicts should be resolved by the network, right? So, what happens when a transaction is rejected by the network as being invalid? I am not using two computers running bitcoin, I'm using ONE. I can't run two instances of bitcoin on the same computer, just ONE. So, the idea that I could be trying to do conflicting transactions is silly. If the transactions that have not been processed from a client are backtracked, as in reversed, then there would BE no conflicting transactions on another client. I've been running my client now for a whole bunch of hours. Before I went to bed last night I decided to do a little test, I sent some money to myself, it stayed unconfirmed for only a few minutes. When I came back to look at it this morning, it had 77 confirmations from the network. While the hung transactions were still HUNG! My whole point is, There is no possibility of conflicting transactions with transactions that aren't being processed at all, there would be no harm at all in just reversing these, since they only exist on My client. How about until something is confirmed, it is not counted against the balance. How about, instead, you have two separate numbers, one that is the Current Balance, and one that is the Future Balance, or whatever you want to call it. And if you backtrack a transaction before it's even been announced to the network, then no harm done. But that should only be allowed if it says 0/unconfirmed, or maybe there should be a separate indicator that says how often it's been announced, and the announcement recognized by the network. If it's already been announced, doesn't the number next to the confirmed/unconfirmed indicator change too? I've noticed that number does not necessarily mean it's been confirmed yet. So, it will be 1/unconfirmed, then 2, then 3, then eventually it will say it's confirmed. In any case, this idea that you can perform a conflicting transaction on another client does not help me with my current problem. Is there absolutely NO WAY at all to either push these transactions through the network, or get my money back from this limbo it is stuck in?! |
|
|
|
also keep in mind that if you mount your encrypted volume, that your truecrypt password is unencrypted in RAM.
I thought the password was only kept in RAM if you had the Cache option selected, which I don't. How would I retrieve the password for my volume from RAM anyway? And, another thing, if the bitcoin app is using encryption itself for the wallet file, doesn't it have to decrypt the file and keep it in memory to work with it? How is there a difference then between having it on a truecrypt volume, and having the encryption/decryption handled from within the bitcoin app? Oh, and I use XP Pro, I know how to encrypt files on NTFS 5, but I also know that windows does not leave a file only encrypted when the file is in use, no, it decrypts it into RAM so it can be worked with, and encrypts it to the hard drive whenever the file's content changes, constantly, on the fly. Just like TrueCrypt does, and just like the bitcoin app would do if it was handling the encryption. I really see absolutely no difference which way it's being handled because there will always be an unencrypted version in memory. But, the unencrypted volume is accessible to the person who is currently able to read it, so, modifying file permissions in an encrypted volume would be good. And adding Windows NTFS encryption would also be good, so if someone tries to grab the wallet file from the unencrypted volume, they will only get an encrypted file they can't use. |
|
|
|
|
I dunno how to do what you just said. How do I transfer 1 of 10 bitcoins to you, transfer the other 9 to another account I own, then transfer 1 to you Again?! It wouldn't let me, it would say I have a balance of 0! That's what is so frustrating to me with these totally hung transactions, if they only exist on my client and won't go through, why can't I just backtrack? I think that is a feature we need in the bitcoin UI, the ability to backtrack unconfirmed, Hung, transactions, as long as the network has not yet received any notice of them. Like for instance if your client can't seem to connect to any other node for whatever reason, then the network obviously isn't handling the transactions, so why keep them hanging around in a limbo that only exists on the client?! I'm going to keep PeerBlock shut off for a couple days, see if that helps. I wish I could actually See the connections activities going on, like when I'm on a Bit Torrent client, or TOR, I2P, or Freenet, they all give me a lot of info about what is going on with the node. The Bitcoin UI barely gives me Any info.
|
|
|
|
|
