Bitcoin Forum
June 25, 2024, 12:15:38 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 [557] 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 »
11121  Economy / Gambling / Re: BitcoinTalk Freeroll this Thursday at Seals on: May 24, 2012, 06:44:52 PM
petrescuerz wants to play too and even signed up for a forum account, but she can't post here because she's a newbie.

I asked her how great the site and customer support is.  She told me:

"the site's great because I'm making lots of bitcoins off it and the support's great, I've never had any trouble with it.  He changed my colour for me".
11122  Economy / Gambling / Re: BitcoinTalk Freeroll this Thursday at Seals on: May 24, 2012, 05:47:22 PM
Post your Seals username in this thread to be registered for a 3BTC Texas Hold'em freeroll at 9pm ET on Thursday May 24th. You must do this by 9am ET Thursday to be SURE to get in, but likely I can get some latecomers in.


hi.

i'm a latecomer.

username 'dooglus'.

please and thank you.

Edit: oh.  it isn't 2011 any more?  nevermind.

Edit2:

Post your Seals username in this thread to be registered for a 3BTC Texas Hold'em freeroll at 9pm ET on Thursday. You must do this by 9am ET Thursday to be SURE to get in, but likely I can get some latecomers in.

Feel free to also post how much you love playing at Seals and how excellent you think Seals support is.

that's the one.  Smiley
11123  Economy / Speculation / Re: What is this spike? on: May 24, 2012, 05:25:19 PM
Oh wait, it's because an order did not get filled?

This is simpler than I'm making it out to be, right?

If you were to place a small buy order at Gox offering $10 for 1 BTC, you would expect to get matched with the cheapest currently unmatched sell order, and end up getting your 1 BTC for $5.14 or so.

Occasionally, due to a persistent bug in Gox's code, it seems that buy orders are being accidentally matched with higher sell orders, not the cheapest ones.  So you see spikes like in OP's chart.
11124  Economy / Service Announcements / Re: {ANNOUNCEMENT} WBX Exchange Frozen on: May 24, 2012, 08:16:48 AM
And in the links down the right hand side, where it says "news what's new", etc., it's all bold.  It used to be that the "news" was bold and the "what's new" subtitle wasn't.

This is just weird.  What's going on?
11125  Economy / Service Announcements / Re: {ANNOUNCEMENT} WBX Exchange Frozen on: May 24, 2012, 07:46:59 AM
Site news for this year is missing....
Come on Andre, what's going on?

The orderbook is completely empty too:
  https://www.worldbitcoinexchange.com/?page=orderbook

I think last time I looked, it wasn't.

Edit: my account still exists, but the "you are logged in, but need to become VERIFIED before you can withdraw or Deposit funds" at the top is new.  I used to be "VERIFIED".  So it's not that the database has been completely reset.
11126  Economy / Service Discussion / Re: [ANN] 700,000 Cash Deposit Locations in Brazil, Russia, USA - BitInstant on: May 24, 2012, 05:47:07 AM
--> We're gonna make the "Destination Account" disappear when you choose 'Bitcoin to Email' and notify email will just say 'Email Address or Mobile Number' which should be simple.

Cool?

Cool.

I noticed it disappears if I select 'bitcoin to email' AND THEN edit the 'amount' field.  But the 'destination' field is before the amount field, so it doesn't disappear until after I've become confused by its presence.

Also, it doesn't reappear if I switch back to 'mtgox' or anything else.
11127  Economy / Service Discussion / Re: [ANN] 700,000 Cash Deposit Locations in Brazil, Russia, USA - BitInstant on: May 24, 2012, 05:37:10 AM
Honestly the best way to learn is to do it with $20 and see how easy it is. Go through the process on BitInstant.com, and you'll see all the instructions you need.

I tried it.  I selected 'walmart' and 'to email' options, and tried depositing $20:

It says I'm going to get $19.20 for my $20.  A 4% fee.  Seems good:



It asks me for a 4 digit PIN, then tells me I'm going to receive $18.20 for my $20.  A 9% fee.  What happened there?

Oh, and it also tells me there will be a further 1% fee for the USD to BTC conversion.  So that's a nice round 10% fee in total.



Then when I get the voucher to print, it turns out I have to pay $23.95 (a convenience fee of $3.95 has been added):



That makes a total fee of exactly 25%.  I pay $23.95 to get $18.202 and then have to pay an extra 1% on top of that for the conversion.

I wonder if there's some way of presenting the true cost up front, and making the fees clearer.  It seems, for instance, that I end up getting more money if I deposit $99.99 than if I deposit $100, because the rate goes up 1% at $100.  But the only way of finding that out is by trial and error.  I'd like to see the fee structure spelled out clearly.
11128  Bitcoin / Electrum / Re: [ANNOUNCE] Electrum - a new thin client on: May 24, 2012, 01:41:58 AM
You can see how it's done here:

  https://gitorious.org/electrum/electrum/blobs/a5152462135b6e132c6776a50675eed15e0c46a2/lib/interface.py#line184

The data is sent using a POST request, and is JSON encoded.
11129  Other / Meta / Re: Whats the point of PGP signatures in BitcoinTalk messagess? on: May 23, 2012, 11:46:04 PM
you might want to add a nounce

ask them to add a nounce

It's "nonce".  As in "n once".  A value that you only use "once".

Not to be confused with http://www.urbandictionary.com/define.php?term=nonce.
11130  Bitcoin / Electrum / Re: [ANNOUNCE] Electrum - a new thin client on: May 23, 2012, 03:47:47 AM
I just tried electrum for the first time and have the following observations:

I tried using 'electrum import' while the client was running.  It let me, and told me it had succeeded, but the balance displayed in the running client didn't change.  I shut down and restarted the client, and the balance still didn't change.  I shut down the client, then reimported the key, then started the client and then the updated balance showed up.

It seems that if I import a key while the client is running, then close the client, the imported key gets overwritten.  I would suggest either not allowing keys to be imported while the client is running, or have the running client notice the imported key and update itself accordingly.

Also, importing a key shouldn't require me to specify the address as well as the private key.  The address can be found from the private key, and in fact that is done in the code to tell me if I type the wrong address.  I'd rather just type the private key.

Other than that it seems to be working well so far.
11131  Economy / Service Announcements / Re: [ANN] bitaddress.org Safe JavaScript Bitcoin address/private key [BOUNTY 0.1BTC] on: May 22, 2012, 01:47:10 AM
Whatever works for you.  Smiley
11132  Economy / Service Announcements / Re: [ANN] bitaddress.org Safe JavaScript Bitcoin address/private key [BOUNTY 0.1BTC] on: May 22, 2012, 12:14:56 AM
It should work with any SHA256 hashing program to create the private key.

This is true, but the satoshi client wants it in base58 with a checksum for the importprivkey command, so it's easier to use bitaddress to do that.
11133  Economy / Service Announcements / Re: [ANN] bitaddress.org Safe JavaScript Bitcoin address/private key [BOUNTY 0.1BTC] on: May 21, 2012, 09:50:55 PM
so if i only ever send to the non-compressed bitcoin address, then i must import the non-compressed private key to spend them.

That's right.

Quote
that means an important question is; will the 0.6+ standard client always be able to do this or should i just start over with the compressed types?

got a bit worried that i might lose access to it, but as long as i remember my passphrase i should be okay, right?

There are many unclaimed outputs to uncompressed public keys, and always will be.  Since it's impossible to know by looking at just transaction outputs which of them correspond to private keys that have been lost forever, or even which are to compressed and which are to uncompressed public keys, the client will have to continue supporting uncompressed addresses forever, or risk making a significant proportion of all bitcoins unspendable.

Make sure you keep a copy of bitaddress's source code somewhere safe in case the site goes offline; then you'll always be able to recreate the private key from the passphrase in your brain.
11134  Economy / Lending / Re: need TODAY 5 btc please, back tomorrow 6,50 btc on: May 21, 2012, 07:42:34 PM
then spam not my thread man! it is important and you....
man go out my thread, i like 5 btc , tomorrow 6,50 back, and not so a drivel

Do you have an OTC rating, lumberjack?
11135  Economy / Service Announcements / Re: [ANN] bitaddress.org Safe JavaScript Bitcoin address/private key [BOUNTY 0.1BTC] on: May 21, 2012, 07:21:42 PM
Seems it wasn't true at all...  So how do I access the 1 BTC I sent to the address corresponding to the compressed address?

I had to import the compressed private key to get the compressed address in my client, then I could spend the 2 BTC back to my main wallet:
Code:
$ bitcoind importprivkey 5KVdACbmHJJLxapsSjQyavyN4LdXtWc4xz7jeowDWxwbcNMRneS bita-regular
$ bitcoind importprivkey L4dLbcCSSwMZ6LJHeaCpkmDmwjeFLMfnW76jFtAJFFuykgqR5UGo bita-compressed

Put those two private keys into bitaddress and you get the exact same output for both.

The bitaddress output shows:

Private Key WIF (51 characters base58, starts with a '5'):
5KVdACbmHJJLxapsSjQyavyN4LdXtWc4xz7jeowDWxwbcNMRneS

Private Key WIF (compressed, 52 characters base58, starts with a 'K' or 'L'):
L4dLbcCSSwMZ6LJHeaCpkmDmwjeFLMfnW76jFtAJFFuykgqR5UGo

so you just need to import both of the private keys if you want to be able to receive coins to both of the bitcoin addresses.  Then the client treats the two addresses as if they were really different addresses:

11136  Economy / Service Announcements / Re: [ANN] bitaddress.org Safe JavaScript Bitcoin address/private key [BOUNTY 0.1BTC] on: May 21, 2012, 06:06:20 PM
can someone please explain how 'wallet details' tab can produce two different bitcoin addresses for the one private key?

if i generated one of those, and sent 1 btc to each of those addresses, what would happen when i import that private key?

would it show 2 btc? what address would it show?

 Huh

Do you have an example of how to get it to do that?  I've never seen it happen.

Each private key should map to exactly one bitcoin address, although two private keys can (incredibly rarely) map to the same bitcoin address.

Edit: oh, you're talking about how it shows the regular and compressed addresses?  They're equivalent.

If you sent 1 btc to each of those addresses and imported the private key, you would see 2 btc at the same address.  Which address it shows would depend on the client you used.  I'll do it now and edit this post with the results.

I used vanitygen to make a 'bita' address, put the private key into bitaddress and found the two bitcoin addresses to be:

Bitcoin Address: 1BitaU837DThJpnSY6ppU8Nu8Z9VGd49U1
Bitcoin Address (compressed): 13jETWnEo69sKwPdYQNqwcqMg9mnyapzNr

Here are the transactions at http://bitcoincharts.com/bitcoin/txlist/ awaiting confirmation:



Hmm.  It's only showing 1 BTC in the new wallet with the imported private key, even though both transactions are confirmed and in my copy of the blockchain.  I wonder if this is a bitcoin client bug.

http://blockchain.info/address/1BitaU837DThJpnSY6ppU8Nu8Z9VGd49U1 and
http://blockchain.info/address/13jETWnEo69sKwPdYQNqwcqMg9mnyapzNr are showing a balance of 1 BTC each.

This isn't safe to depend on and is unlikely to be true for very long, if it is even true at all.  The developers have proposed a private key format that includes a flag to indicate that it corresponds to a compressed public key.  For a client to always take a private key and generate TWO bitcoin addresses from it is a needless doubling of resource consumption and complexity and is unlikely to become the status quo.

Seems it wasn't true at all...  So how do I access the 1 BTC I sent to the address corresponding to the compressed address?
11137  Bitcoin / Bitcoin Discussion / Re: Spending and Receiving Stolen Coins. on: May 21, 2012, 03:55:51 AM
You do realize that 1 "tainted" BTC is actually 100,000,000 Million tainted coins if separated and sent properly.

Currently 1 BTC can only be split into 100 million pieces.
11138  Bitcoin / Bitcoin Discussion / Re: A public apology to Donald, Patrick and Amir ("Intersango guys") on: May 18, 2012, 08:28:23 PM
I have violated my promise (of "not to post anything [about Bitcoinica]") yesterday, by posting this in the emergency announcement thread:

It's very hard to judge whether they had anything do to with the security issue, because everything contributes to the disaster.

Patrick - compromised email server.
Me - improper access control.

I think you need to make up your mind; are you going to stop posting about Bitcoinica, or are you going to keep telling us more and more.
11139  Economy / Service Announcements / Re: {ANNOUNCEMENT} WBX Exchange Frozen on: May 18, 2012, 03:00:26 AM
And its back again.  

Wonder whats going on there...

I checked when you wrote that it was down, but it was still up for me.
11140  Bitcoin / Bitcoin Discussion / Re: Sites accepting 0-confirmation txns on: May 16, 2012, 04:59:21 AM
If merchant waited 5 minutes then an attacker would not risk his block unless he expected to gain more than 25BTC from the merchant.

This is true.  The attacker wouldn't attack because he doesn't expect to gain anything.  What I'm disputing is this:

5 BTC / 0.083 = 60 seconds.  At 60 seconds the "double spend game" is fair.  In the long run neither the attacker or merchant will gain or lose anything.

I'm asserting that the merchant will indeed lose something.  He'll lose his product and not get his 5 BTC in the majority of cases with nothing balancing that loss.
Pages: « 1 ... 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 [557] 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!