Are withdraws broken? I'm not able to withdraw and a script error is showing in the Javascript console when I try. Uncaught TypeError: Property 'withdrawConfirm' of object [object Object] is not a function Tested on Firefox 20.0.1, and Chrome 26.0.1410.64 with no success. |
|
|
|
ALL TICKETS SOLD!
The block 198311 will be used to determine the winner...someone quote this please!
Quoted. |
|
|
|
Thanks for adding the long polling! And I just noticed the fadeout stuff on the site. It looks good! *thumbs up*  |
|
|
|
|
I just placed a bet and got a return in just a few seconds. So, I guess it's fixed now?
|
|
|
|
You pay back really fast! I placed 10 bets and had already got back 8 payments before I could finish placing the 10th! I think I'm going to bet here from now on.  |
|
|
|
ok with regret I am r re-adding the note about their regular outages.
I had the request just 1 week ago and it has been 1 week of large payouts not being processed with no response from the site ops.
Im still sure they will resolve this when they get around to answering their mail but gamers need to be warned.
I switched to BTCDice, for the time being, for this exact reason... not a fan of missing payments for days at a time... hope it gets fixed soon. |
|
|
|
Also, if not using the command line (i.e. using Python or PHP) you can use "*" as the account name and it actually will wildcard all accounts. Python: (requires python-jsonrpc package) #!/bin/python
from jsonrpc import ServiceProxy
from jsonrpc.proxy import JSONRPCException
from jsonrpc.json import JSONDecodeException
RPC = ServiceProxy("http://%s:%s@%s:%s" % ('yourusername', 'yourpassword', '127.0.0.1', 8332))
try:
print "%s" % RPC.getbalance("*", 0)
except JSONRPCException, e:
print e.error['message']
except:
pass
PHP: (requires jsonRPCClient Class) <?php
require_once("jsonRPCClient.php");
$RPC = new jsonRPCClient("http://yourusername:yourpassword@127.0.0.1:8332");
echo $RPC->getbalance("*", 0);
?>
|
|
|
|
My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... T
I think that's your problem right there. When you shut down the client, it forgets about these invalid and unconfirmed transactions sent long, long ago from SatoshiDICE but since forgotten on by everyone else since they never confirmed. But then when you start your client back up, it learns of these again from these other four (polluted) nodes of yours. Why not try a normal startup to the outside world, or with -connect= to a well connected node. Each of the nodes I connect to have been modified to hold hundreds of connections. Likewise, I've tried restarting without connecting to them, rescanning, etc... If it's a matter of starting it differently, rescanning, or redownloading the block chain, you can assume I have already tried it. |
|
|
|
I would guess that maybe you have some problems with your 0.6+ wallet, and so exporting and re-importing the keys is probably the best thing to do anyway.
Then when I ran bitcoin-qt again, the transaction was no longer showing at all. It's still on blockchain.info as an unconfirmed transaction, and I'm sure it will eventually confirm, at which point I will see it in my wallet again.
My issue is that these transactions do not exist in the blockchain and were generated during a split. The transactions that are showing on blockchain.info do not appear in my wallet... weird issue. I imagine that rebuilding a new wallet from the private keys should fix it though, since it re-verifies every transaction for every private key imported. |
|
|
|
PyWallet errors on wallets that have been opened in Bitcoin-qt v 0.6+
Not for me it doesn't. Maybe you need a newer PyWallet. No, pywallet won't work with Bitcoin-qt 0.6+, nor will it work with encrypted wallets. Are you sure? I used it just a few days ago, and I've not had anything older than bitcoin-qt 0.6 for a long time. Maybe I didn't encrypt the wallet I used it with, but I created it using bitcoin-qt 0.6+. Yeah, I tried it last night and it just throws a bunch of errors on my 0.6+ wallet, but worked fine on a 0.5.x wallet. |
|
|
|
My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... This wallet is only used for Satoshidice, so no other TX's (aside from the one I funded the wallet with) exist.
Neither a rescan, nor a re-download of the blockchain resolved the issue.
I'm currently rebuilding the wallet by exporting all the private keys from it and re-importing them 1-by-1 into a new wallet... it will take a few days to run, since there are ~2100 private keys and it averages 45 seconds per key to import. I'll let you know how it works out.
That will work, but it would be a lot quicker to just remove the bad transactions from your wallet using PyWallet. Why don't you try exporting the keys you used in the faulty transactions first and importing them into your new wallet - then you'll see that the bets have been paid out, and that it's just bad transactions in your wallet that prevent you from seeing them. PyWallet errors on wallets that have been opened in Bitcoin-qt v 0.6+ |
|
|
|
No idea if it is the reason, coz it depends on how the SatoshiDICE server works, however:
In bitcoind, an unconfirmed transaction may be lost if bitcoind restarts.
Unconfirmed transactions from other bitcoinds are stored in a memory pool so are lost when bitcoind stops.
Or, if for some reason the 0-confirm transaction didn't make it to the bitcoind (networks aren't perfect) it wont know about it (though rare)
This also means that if bitcoind wasn't running when the transaction was sent out, it won't know about it until either it ends up in a block, or some other 0-confirm transaction requires it and bitcoind requests it from another bitcoind.
i.e. it will eventually get the transaction back again since probably every other bitcoind still has it and eventually a block will include it.
But bitcoind may not find out about it until it lands in a block (which can be more than an hour on some rare occasions - or longer if some pools are ignoring processing the transaction)
My bitcoind runs 24/7, and has 4 specific other nodes that I run, which it connects to... This wallet is only used for Satoshidice, so no other TX's (aside from the one I funded the wallet with) exist. Neither a rescan, nor a re-download of the blockchain resolved the issue. I'm currently rebuilding the wallet by exporting all the private keys from it and re-importing them 1-by-1 into a new wallet... it will take a few days to run, since there are ~2100 private keys and it averages 45 seconds per key to import. I'll let you know how it works out. |
|
|
|
I guess go back to the beginning.
Step 1. Make a backup of wallet.dat
Step 2. Remove every file in the bitcoin folder except for wallet.dat
Step 3. Launch bitcoin and let it download all the blocks again.
--------
If that still doesn't give you a solution, then you might try pywallet to export the private keys and import them elsewhere.
I've done that (re-download block chain), but those transactions still show. I can't seem to figure out how to export keys, or import them back (in bulk) into a new wallet using pywallet. Know of a tutorial anywhere? |
|
|
|
What client and version are you using?
Satoshi Client 0.6.2 |
|
|
|
I have 12 transactions from 6/7/2012 that are still sitting unconfirmed in my wallet. The transaction IDs are not found on blockexplorer or blockchain.info, and the transaction ID on the payment sitting in my wallet does not match the transaction ID of the payment on Satoshidice.
Every one of your "MY SEND" payments does show in blockchain.info. Each then shows in SatoshiDICE as CONFIRMED as well (meaning the payout has confirmed). So SatoshiDICE looks to have properly received, and paid out to the origin address on each of those. Now why you wouldn't see those as confirmed in your client, I have no idea. Are you absolutely sure you have the latest block? Currently it is block 184,160. (Shows in the bottom right, hover over the icon, for 0.6.2). Take just the first transaction in your list. Are you saying your client is at block 184,160 or greater and yet does not show a payment to that payout address for that specified payout amount (it should have at least 542 confirmations)? I am 100% sure my blockchain is updated. I know all of my sends are valid. The issue lies in the fact that the receive transactions that correlate to each one of those send transactions remains unconfirmed, and the transaction ID on those receives does not match the transaction ID that SatoshiDICE shows on their website for their payment back to me. The receive transactions I have in my wallet do not appear on blockchain.info or blockexplorer.com, and the transactions for SatoshiDICE's payments to me do not appear in my wallet anywhere (I have checked, multiple times). Things I have already done:- - Rescan my wallet
- - Delete and re-download the entire blockchain
- - Waited 3+ days for transactions to confirm (they have not)
I'm open to suggestions. |
|
|
|
|
I have 12 transactions from 6/7/2012 that are still sitting unconfirmed in my wallet. The transaction IDs are not found on blockexplorer or blockchain.info, and the transaction ID on the payment sitting in my wallet does not match the transaction ID of the payment on Satoshidice.
MY SEND: 79c61ac77c36439f32cdc172e15a1666f7f35f5b3e16e4597491c474647ed3d7
MY RECEIVE: 18e77ef82e9be9fa82afd72c9da0e36d9d49ce03e44d02f1a55fcd8515ea65ac
SD PAYMENT TX: d2768db6562c0231da78188c282748b0b4219064792221ff6e32266ca07f01c1
MY SEND: 02636cacb8efe6b8c4005c3a7afb6a55c0458344d7ce54da53c6f85efb8855c8
MY RECEIVE: 7f1fe410a0209a82c476751e21cb124415219c37477c507acca4eda937134bdb
SD PAYMENT TX: ad1d52e036cd1d030a1436ec82a845110fb0a3cc27fe31adcd18fa2aa76ae56a
MY SEND: 4aac9912301e5ef52d96521948d1f1be3a5385f004232ea85d4c15b696009fbf
MY RECEIVE: b6d43e7f22d0eac61071ac1abee93e6665cb179aaa87ccc88705bee86ce1e45a
SD PAYMENT TX: 512d71e7fe2a673c467862264d40accb0b99ad5245756878d72920c1d73e0c47
MY SEND: 255795f7ab00c0b1d96304c525fcc907c22326bdc7dc9eeacb6e9bf704fdf720
MY RECEIVE: 1faa2d9e7911679856294efd7a0494877622b14ae7797ee4a0e0b5e1217567c2
SD PAYMENT TX: 1194903667fcbe9b601386ba34c90e3a63c6388288f6d50d1f4011a93acd7858
MY SEND: 801be45e210a1d57c7982d7cd74ea8212ba66ce1a7dad33daeaf976243c35b4e
MY RECEIVE: 2ccefa0ea4d43df5308fad136cf717a1dbfa8ef228342980a7b9f8f1aa1ca7b8
SD PAYMENT TX: 1aac64d6e8294e06a08669e09e5ac98c4d64eeab6c0ed2de4cc1c98926a92c29
MY SEND: 236ff462fda8b65a0e909ce1d8811dd5880f3319e776d004c02aaaf1602bd6f6
MY RECEIVE: 4a50653c48bd9bf61aa978a9c80031a549141856a753b710c747839421f59f76
SD PAYMENT TX: c443f91ab6c7e0bfe9e0848c7163daaa215b28caee124d8069786a5c1513be5f
MY SEND: 6ddcf6628a07a95397fa79c564773f041233b110e7e5405623d452ea22e5dc04
MY RECEIVE: d1c1f056c7edb6088dda96d2ac4efc331c5f1a3ba49baa75de46d687813560e4
SD PAYMENT TX: 05eb31104533837395bc118672fa04432ca495a081ea904f05270e1f9d5d5b80
MY SEND: c72108131b8d0f3d8e4d92da78ab77d6f3cc15621a1063eea8fb6d161cd00a9f
MY RECEIVE: 21a961b04202f57380aee647411498f7a9269fbc2bb5250df37a5ab870c3f881
SD PAYMENT TX: 7c02f1e7bc54eacc3c180b8ada456e9d9729a214705d2ba495507f10289cb419
MY SEND: e88a3b6a444fd68921867d2a887e766b9376839a872d784a0df371573551c008
MY RECEIVE: d7262d7ef08dacfdfc163659f23ea43fac6b78ae5cbfe714a9ac0cb0b8275f00
SD PAYMENT TX: e3b6962c26edb09c2be5da8040a896e013d78724791a2579f3b73dd30b191511
MY SEND: 45e8ef83c2b0a067930d57954912a23f57ff8ec1f16900c64d344e2ce82ad243
MY RECEIVE: 029da454bffbd3a6b53be671a1916885ac1c6abbc5f9121c1f632ae141b470c5
SD PAYMENT TX: b36b2f0497ce216eb3e96a618307ac8affe15bbf75d2f45b794dde7e8485b9f4
MY SEND: c57b438160d2f57a00bfaa6da900512c0697090dd55850c028ffae5da2005916
MY RECEIVE: 37d5ca061bc8d2746c9189494337b352c49b38e44edb003fc6bbd5f34ec5f23f
SD PAYMENT TX: 7d887c5e3ebb60c385b0b84ce7279ff3846bdd8d71181825175818b556c9fcf2
MY SEND: 8a155cfbb23b91c60c83bf54edd2b308567c7db1143a2c0ed4cf628747fc400f
MY RECEIVE: 672dfbb0d521c3d15f080d59e702e2af75bb0a05d3fd97f7544c1e06559d7e10
SD PAYMENT TX: 0f7f022b49bf817d7a5175d978b9b3e34509e63d1a722f169fb654bb8c7eebb3
"MY SEND" is the transaction ID of my bet placed to SatoshiDice.
"MY RECEIVE" is the transaction ID of the return payment I received from SatoshiDice (all of which are still unconfirmed).
"SD PAYMENT TX" is the transaction ID that SatoshiDice claims the payment should have had.
This is a total of 19.54851363 BTC.
I have completely re-downloaded the blockchain and rescanned, but the transactions remain unconfirmed and non-existent as far as blockchain.info and blockexplorer are concerned. However, the transaction IDs that Satoshidice claims they sent can be found on both sites, but the bitcoins are not in my wallet, and I do not see the transactions for them.
|
|
|
|
If anyone wants my attention, any page they present us with better have a BIG ASS BITCOIN ACCEPTED HERE logo emblazed on it or I'm probably just going to roll my eyes and move on to the next post.
edit: I realize there's a mention of Bitcoin, but it does not jump out at me, nor would it for the casual non-bitcoiner visiting the page - which is a pretty big deal for me.
I'll tell him to add an image to the page. Super secret download of a non-album track just for bitcoin supporters, but let everyone know it out there.
Huge banner advertising.
Bitcoin logo tattooed on the lead singer, shown prominently at all shows.
Custom print cd's sold at shows with the image of the bitcoin for the entire background, and make all liners notes encrypted that require a satoshi or two to unlock.
And if you really want a lot of creative help... let us know a little bit more about the band. The name suggests some concern for the environment, or a disagreement with current government policies. If you have an agenda, play it up.
All odd, but interesting ideas... And knowing what the sound is would help a lot. If it's country, or whiny emo tripe, the free taste above is all you will see from me; if it is Newfoundland drinking jigs and reels with a contemporary twist, well I could probably line up a whole production and distribution deal for you.
And finally- shop around for a better production deal. Five grand sounds a lot like an engineering solution designed to liberate a lot of money from a start-up band, unless you are getting some amazing engineer/producer who has the magical ability to get you signed with a major label on the power of your first indie release. Otherwise, look to crafting it yourselves, you will get a lot more bang for your buck.
It's pop/rock/punk type stuff... I think? I'm not good at defining music by genre, but I think it's a good enough guess. As far as the producer goes, I think only a large portion is for the producer, and I don't know many of the details, but I've heard mention of some sort of management/marketing thing that goes along with it, so there might be more to it than I'm aware of. |
|
|
|
|
Show Posts
