Bitcoin Forum
June 25, 2024, 05:01:38 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 504 505 506 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 »
11061  Economy / Service Announcements / Re: Bitcoinary.com - The new smart way to buy and sell Bitcoins. on: June 09, 2012, 05:22:53 PM
I tried signing up but didn't get very far.  Observations so far:

* "Send Money To Another Country ?" has a space before the question mark which bugs me.

* https://www.bitcoinary.com/en/users/sign_up selects the 2nd input field by default, "email".  Why not start at the top?

* After filling in the signup form and submitting it, all I got was "We're sorry, but something went wrong."  Would be nice if you told me what kind of a something.  Was my 32 character password too long for you?  I tried again with 'fred' and it gave me a properly formatted error page, with "is too short (minimum is 6 characters)".  I tried using shorter and shorter passwords, but even a 6 character password still gives me the same "something went wrong" screen.
11062  Economy / Gambling / Re: SatoshiDICE.com - Verified rolls, up to 64,000x winning on: June 09, 2012, 04:45:14 PM
You're not doubling your money every time you win, you are getting 1.343x your money. So the expected value is
Code:
((732422*1.343)+(267578*0.005))/1000000=0.984980636

would you mind trotting that past me again? where'd ya get the 26758*0.005?

i'f i'm understandign the math there correctly, you're saying that over time, you'd lose a small amount. about 2.5%, is that right?

Expected value is the sum of each possible return to you, multiplied by the probability of it happening.

There are 2 possible outcomes:
  * you win 1.343 times your money, with probability 0.732422
  * you win 0.005 times your money, with probability 1 - 0.732422 = 0.267578
(because even when you lose you get a little something back - just to prove they got and processed your bet).

So the expected return is (0.732422 * 1.343) + (0.267578 * 0.005) = 0.984980636 times your money.

That means you lose (1 - 0.984980636) * 100 = 1.5019364% on average per bet.
11063  Economy / Gambling / Re: SatoshiDICE.com - Verified rolls, up to 64,000x winning on: June 08, 2012, 07:20:05 PM
It got processed now. Yay Smiley

Was just weird that that one took so long to show up on the website, while I never had any problems with that before.

I wonder if they're waiting to have enough confirmed funds to pay winners now to avoid the other problem that's been going on of paying out with funds that never confirm.
11064  Economy / Gambling / Re: [SOLVED] Satoshidice doesn't pay me! on: June 08, 2012, 04:39:47 PM
Are you sure about this being resolved ? As I still have outstanding payments i'm waiting on.

Well, no.  I read that at one point it was resolved.  I guess it's an ongoing issue but it does seem that everyone gets paid out eventually.
11065  Economy / Gambling / Re: SatoshiDICE.com - Verified rolls, up to 64,000x winning on: June 08, 2012, 04:30:47 PM
Unless I'm missing something in the maths of the dynamic limit, it's going to harm the business if the way it works isn't changed.

I think you're missing something in the maths.

The house edge is the same whatever the bet size, so the bet size doesn't hurt the expected house win rate, it just affects the risk of ruin.  And the risk of ruin is managed by dynamically adjusting the maximum bet size to only accept bets they can afford to lose.

If they only accept bets up to 100 when they can afford to (which makes sense) they still make 1.5% (or whatever the edge is these days - it's advertised differently in different places) on average each time they take a bet for 100 BTC.

By the way, here's where I saw it say the house edge is less than 1%:


11066  Economy / Gambling / Re: SatoshiDICE.com - Verified rolls, up to 64,000x winning on: June 07, 2012, 09:50:25 PM
Also it doesn't exist on blockexplorer either.

i've noticed there's a lot that doesn't exist on blockexplorer lately.

To be fair, blockexplorer has only ever - uh - explored blocks.  And so unconfirmed transactions, not being in a block, aren't shown.

It's also sometimes quite a few blocks behind.  But is there other stuff is doesn't show that it should?
11067  Economy / Gambling / Re: [SOLVED] Satoshidice doesn't pay me! on: June 07, 2012, 08:35:56 AM
This is discussed at length in the main satoshidice thread, but the summary seems to be:

Someone bet 100 BTC and won 1000 BTC, taking a large percentage of the site's coins.  This meant that winners were being paid out with unconfirmed coins from losers, and some of those coins never confirmed, meaning the payouts couldn't confirm either.  This wouldn't usually happen since there are usually enough confirmed coins in the wallet to not have to use unconfirmed coins from other players.

Everything was resolved in the end.
11068  Economy / Gambling / Re: SatoshiDICE.com - Verified rolls, up to 64,000x winning on: June 07, 2012, 08:28:20 AM
I think this was caused because the output in question was fresh from a mined block and had the output in the older OP_CHECKSIG style.

The input looks like it was a donation payment from the P2Pool software.  For some reason P2Pool blocks always use "pay to public key" outputs for the donation address (see https://en.bitcoin.it/wiki/Transactions#Transfer_to_IP_address) rather than the more common "pay to bitcoin address" type of output (see https://en.bitcoin.it/wiki/Transactions#Transfer_to_Bitcoin_address).

It looks like nelisky may be running his own separate P2Pool with the donation address changed to his own address.  Each of the blocks he found (see http://blockexplorer.com/address/1MgH8iNkdZrDW8rsfzifDzsqJnCjBVyRBV) have very few recipients of the block reward meaning he's not part of the original P2Pool.
11069  Economy / Gambling / Re: StrikeSapphire - NEW Bonus - New $15 Blackjack - New 15 BTC in Weekend prizes! on: June 06, 2012, 09:44:22 PM
Hope that answers your questions...

Yes, thanks.

I was thrown off by the phrase "weekend balance".  The word 'balance' made me think of account balance, not weekend profit/loss.
11070  Economy / Gambling / Re: StrikeSapphire - NEW Bonus - New $15 Blackjack - New 15 BTC in Weekend prizes! on: June 06, 2012, 09:21:47 PM
Can you please clarify what this means exactly?

Quote
Minimum $25 positive weekend balance to qualify. Not available in the United States.

Does it mean that if I hit $25 at any point during the weekend I qualify?
Or that I must be over $25 all weekend, and if I drop below then I'm disqualified?
Or that I must start the weekend with at least $25?
Or end it with at least $25?
Or something else?

Will the leaderboard show players who aren't qualified such that I may find myself trying to catch someone who isn't really even in the game?

So many questions!  Smiley
11071  Bitcoin / Development & Technical Discussion / Re: create btc-address + key in only PHP ? on: June 06, 2012, 08:15:31 PM
Ok, in case it is of use to anyone, I have gotten some help from Joric to create a script that generates keys in only python. This could be called from your PHP. Inside it supports generating keys from a passphrase or from a known private key and more.

https://github.com/weex/addrgen

Very nice, thanks.

If you're aiming for minimal, none of set_privkey(), set_pubkey(), get_privkey() seem to be used at all.
11072  Economy / Service Announcements / Re: {ANNOUNCEMENT} WBX Exchange Frozen on: June 06, 2012, 07:26:19 PM
I received a PM from a WBX user:

Quote
Hi Chris, I just wanted to contact you and let you know where I stand with wbx. I am owed $180 from a cash deposit that never even showed up on my wbx account. This was deposited on the 24/02/12 annoyingly after the site ceased trading.
You're a great man for sticking around. I wouldn't of blamed anyone for washing their hands of the btc and all this carry on so thanks.

I hadn't thought of these kinds of liabilities.  So not only to we have BTC and AUD balances on the site, we also have withdrawals that were never really paid out, and now deposits which were never credited to the WBX accounts.

I've no idea how it's possible to get an idea of the total liabilities when I don't have any handle on the total amount of unpaid withdrawals or uncredited deposits.

Andre, you really need to step up and provide this information at the very least.
11073  Bitcoin / Bitcoin Technical Support / Re: HELP! Transactions not confirming ;( - 4 btc bounty on: June 06, 2012, 01:06:52 PM
The pywallet method definitively works, i had this same issue a while back with one tx and used it without other alternative. You will have to remove the transaction from wallet.dat, which is a database that stores this kind of info, manually. Make sure you have a backup copy of your wallet before doing any of this.

I just followed your instructions and it worked for me.  I had made a mess of my wallet and failed to tidy it up using bitcointools.  Following your instructions I was able to remove the double-spend transaction and get the wallet back to normal.

I already had Python installed, and am running Linux, so I've not tested it on Windows.
11074  Bitcoin / Bitcoin Technical Support / Re: HELP! Transactions not confirming ;( - 4 btc bounty on: June 06, 2012, 12:29:55 PM
I think that using Gavin's bitcointools to mark the 5 rogue transactions as 'unspent' should fix your problem.

Get it from here:
  https://github.com/gavinandresen/bitcointools

Then something like:
  python fixwallet.py --tweakspent ccf585bcfed1283d11b5012c5f3f3429c5695a8d2280287c44e605223b6318b5

I'll experiment here to see if it works, and report back.

I've been unable to get bitcointools to do what I wanted.

https://bitcointalk.org/index.php?topic=29765.0 seems to be a similar issue to Jeremy's, but the solution that was found there is on an old git branch that never made it back to the master branch.
11075  Bitcoin / Bitcoin Technical Support / Re: HELP! Transactions not confirming ;( - 4 btc bounty on: June 06, 2012, 11:34:57 AM
I used my current wallet with a backup of all the rest of the files in the bitcoin folder from 1 day prior to the unconfirmed transactions. My understanding was that the wallet contained nothing but the private keys. Is this incorrect?

Yes, that's incorrect.

See http://bitcoin.stackexchange.com/questions/3173/what-information-does-a-wallet-contain
11076  Bitcoin / Bitcoin Technical Support / Re: HELP! Transactions not confirming ;( - 4 btc bounty on: June 06, 2012, 11:13:17 AM
To the devs: isn't this a bug in the Satoshi client? Shouldn't the client try to rebroadcast unconfirmed transactions once in a while? If it does rebroadcast, just not fast enough for Jeremy's needs, then isn't this an enhancement issue that should be logged anyway? (allowing the user to configure the rebroadcasting periods, and/or adding a command line switch (perhaps even GUI) to manually force the rebroadcast...)

Or is there something peculiar with those transactions that make them be refused by everyone every time they are sent? I'm ruling out voluntary double-spends. (if it's an involuntary one, it's possibly an even more serious issue...)

It is rebroadcasting the transactions over and over.  From the log Jeremy put on dropbox:

Code:
ResendWalletTransactions()
Relaying wtx ccf585bcfe
Relaying wtx ee188b9e04
Relaying wtx b1f331143f
Relaying wtx 11fd5b6aed
Relaying wtx 4b87953acc

I'm wondering if the transactions are invalid for some reason, and so his peers aren't accepting the transactions.  I don't know why that would be though.
11077  Bitcoin / Bitcoin Technical Support / Re: HELP! Transactions not confirming ;( - 4 btc bounty on: June 06, 2012, 11:09:47 AM
I think that using Gavin's bitcointools to mark the 5 rogue transactions as 'unspent' should fix your problem.

Get it from here:
  https://github.com/gavinandresen/bitcointools

Then something like:
  python fixwallet.py --tweakspent ccf585bcfed1283d11b5012c5f3f3429c5695a8d2280287c44e605223b6318b5

I'll experiment here to see if it works, and report back.
11078  Bitcoin / Bitcoin Discussion / Re: [ANN] Selling online never been easier thanks to Mt.Gox's new “Pay Now” button! on: June 06, 2012, 09:35:49 AM
How many people? How much money? How long have they been waiting? When do you expect a resolution?

I think the bigger concern, that I've not seen addressed, is that MtGox may be insolvent.

What is the cause of the problem affecting these "few people".  Is it that you don't have enough US dollars to pay them?

You are unable to process large dollar transactions and many of us suspect it's because of insolvency

I sincerely hope you're wrong about solvency problems.

Well, is he?
11079  Bitcoin / Bitcoin Technical Support / Re: Encrypted wallet.dat, lost password, any solutions? on: June 05, 2012, 10:26:00 AM
I don't suppose you have a backup from before you encrypted the wallet?

Ha!

That's the first thing I thought of when I saw this thread, but forgot it in all the technical details.
11080  Bitcoin / Bitcoin Technical Support / Re: Encrypted wallet.dat, lost password, any solutions? on: June 05, 2012, 10:14:49 AM
Any script authors or white hats interested in making a hundred BTC or so, send me a message.

I sent you a PM.

I've since discovered that it's possible to test whether I've cracked your password without having any of your encrypted keys.

If you can just give us your encrypted master key, the salt, the number of iterations, and your best guess at what you think the passphrase is, we can attempt to find a passphrase that decrypts the master key and know when we've done it, but without getting access to any of your funds.

To get the information we need, get a copy of Gavin's bitcointools: https://github.com/gavinandresen/bitcointools and make the following change in wallet.py:

Code:
-      print("Master Key %d"%(d['nID']) + ": 0x"+ short_hex(d['crypted_key']) +
-            ", Salt: 0x"+ short_hex(d['salt']) +
+      print("Master Key %d"%(d['nID']) + ": 0x"+ long_hex(d['crypted_key']) +
+            ", Salt: 0x"+ long_hex(d['salt']) +

Then close bitcoin-qt and run:

Code:
./dbdump.py --wallet | grep Master.Key

from the bitcointools directory.

It should print a single line, like this:

Code:
Master Key 1: 0x47994851532eb7479886f5dc3c923df2d8a57d1f687d0d41808dee394b50259b209e587f677a3b69db1448ecb18e0d39, Salt: 0xa66b5e971bbd8106. Passphrase hashed 95913 times with method 0 with other parameters 0x

Using this, and bitcoin-qt's crypter.cpp, anyone can verify that the passphrase is 'abc'.  But since nobody has a copy of the wallet I encrypted with 'abc', nobody has access to the coins in the wallet.
Pages: « 1 ... 504 505 506 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!