Show Posts
|
|
Pages: [1]
|
Ok, I've been around and around and I have no earthly idea what's going on here. I built bitcoind ("version" : 99900) from git on a headless ubuntu 13 machine. Running the following command: sudo bitcoind -datadir=/home/ben/.bitcoin/ -conf=/home/ben/.bitcoin/bitcoin.conf -daemon Everything works great, as long as I remain connected to my ssh session. Logging off for a few seconds doesn't interrupt, but if I leave it disconnected for more than a few seconds, I get the following error: 2014-08-23 06:02:13 LevelDB read failure: IO error: /home/ben/.bitcoin/chainstate/000174.sst: No such file or directory 2014-08-23 06:02:13 IO error: /home/ben/.bitcoin/chainstate/000174.sst: No such file or directory 2014-08-23 06:02:13 *** System error: Database I/O error 2014-08-23 06:02:13 Error: System error: Database I/O error 2014-08-23 06:02:13 ERROR: ProcessBlock() : AcceptBlock FAILED 2014-08-23 06:02:13 Loaded 754 blocks from external file in 4783ms 2014-08-23 06:02:13 Reindexing block file blk00006.dat... 2014-08-23 06:02:13 addcon thread interrupt 2014-08-23 06:02:13 opencon thread interrupt 2014-08-23 06:02:13 msghand thread interrupt 2014-08-23 06:02:13 dumpaddr thread stop 2014-08-23 06:02:13 ProcessBlock: ORPHAN BLOCK 0, prev=00000000000007169e562472fb20f0e940fc2b17b8aa27be620c49f0da3abc14 2014-08-23 06:02:13 net thread interrupt 2014-08-23 06:02:13 Shutdown : In progress... 2014-08-23 06:02:13 StopNode() 2014-08-23 06:02:13 Shutdown : done
Different "sst" file every time I restart. Doesn't matter how far along I am in the chain. For some reason, it's as if the chainstate sst files just "disappear" after I log off my ssh session. Restarting gives me: Error opening block database.
Do you want to rebuild the block database now?
Running again with "-reindex" re-indexes just fine and starts it back up; that is until I exit my ssh session again. I've rebuilt bitcoin from source, downloaded the blockchain about 40 times, moved the data directory, etc. Any suggestions?
|
|
|
|
I'm trying to understand the internal workings of a transaction, so I executed the following command against bitcoind bitcoind getrawtransaction fd3d049c9e75f96f9786b965b77b99fa0e7d39fa95e0b126682658299e71ac70 1 Here's the response: { "hex" : "0100000001359815939bba9941e3bc0f9ffedea4e6b1c5c1885250b54cc11a20bc9c7fae51010000008c493046022100fbb4a90b868bdbd9229d7cc834373b502aa00eebb3d045088e8173be714f6943022100a26707f25a9955c23e71819300c1b32224881d8c09f65333503cb09d4fe62d4a014104558f3b743874639994ea070955847e85824b8bb9327c0297647f468bfd18e669c31ede14c44ae06af1b0bc4ffd06d6ffe564560e9c725b060bfd1ce89c843f2cffffffff028861706b030000001976a9148ca2fb6f0fcc4447764c6e4ed7929ed06f9797de88ac7874a112000000001976a9144640f7994705548593e476856e3680c42a641f8788ac00000000", "txid" : "fd3d049c9e75f96f9786b965b77b99fa0e7d39fa95e0b126682658299e71ac70", "version" : 1, "locktime" : 0, "vin" : [ { "txid" : "51ae7f9cbc201ac14cb5505288c1c5b1e6a4defe9f0fbce34199ba9b93159835", "vout" : 1, "scriptSig" : { "asm" : "3046022100fbb4a90b868bdbd9229d7cc834373b502aa00eebb3d045088e8173be714f6943022100a26707f25a9955c23e71819300c1b32224881d8c09f65333503cb09d4fe62d4a01 04558f3b743874639994ea070955847e85824b8bb9327c0297647f468bfd18e669c31ede14c44ae06af1b0bc4ffd06d6ffe564560e9c725b060bfd1ce89c843f2c", "hex" : "493046022100fbb4a90b868bdbd9229d7cc834373b502aa00eebb3d045088e8173be714f6943022100a26707f25a9955c23e71819300c1b32224881d8c09f65333503cb09d4fe62d4a014104558f3b743874639994ea070955847e85824b8bb9327c0297647f468bfd18e669c31ede14c44ae06af1b0bc4ffd06d6ffe564560e9c725b060bfd1ce89c843f2c" }, "sequence" : 4294967295 } ], "vout" : [ { "value" : 146.87429000, "n" : 0, "scriptPubKey" : { "asm" : "OP_DUP OP_HASH160 8ca2fb6f0fcc4447764c6e4ed7929ed06f9797de OP_EQUALVERIFY OP_CHECKSIG", "hex" : "76a9148ca2fb6f0fcc4447764c6e4ed7929ed06f9797de88ac", "reqSigs" : 1, "type" : "pubkeyhash", "addresses" : [ "1Dpcr4DhdAF8HaNKEnYgv9PJgBjErdUdnM" ] } }, { "value" : 3.12571000, "n" : 1, "scriptPubKey" : { "asm" : "OP_DUP OP_HASH160 4640f7994705548593e476856e3680c42a641f87 OP_EQUALVERIFY OP_CHECKSIG", "hex" : "76a9144640f7994705548593e476856e3680c42a641f8788ac", "reqSigs" : 1, "type" : "pubkeyhash", "addresses" : [ "17QU8RmoQT9T2uQadi24piJ2nE1rDjfn8g" ] } } ], "blockhash" : "000000000000050f650c03af06696d141dfaf39a213d1cd8aa46837fd37e425b", "confirmations" : 101258, "time" : 1348383754, "blocktime" : 1348383754 }
In a multi-sig scenario, I'm assuming the "reqSigs" under scriptPubKey (which is 1 in this example) would be higher than 1 and there'd be multiple addresses in the "addresses" array. So here's my questions - Does anyone know of a multi-sig transaction I could look up on the blockchain to see it's structure?
- How do you determine the target address of the multi-sig output?
I've tried some preliminary googling but can't seem to get a straight answer on the JSON representation of a multi-sig transaction. Thanks.
|
|
|
|
So here's my problem. I've got bitcoind running as a daemon and it syncs fine for a while, and then slows down and stops syncing, and then I have to restart it to get it going again. A couple of questions. I see this sometimes in my debug.log before it stops: 2014-05-09 11:23:39 ERROR: AcceptToMemoryPool : nonstandard transaction: scriptsig-non-canonical-push 2014-05-09 11:23:50 ERROR: AcceptToMemoryPool : nonstandard transaction: dust Are these potential culprits? Second, I found a script that modifies tc rules to restrict bandwidth. I ran them, but then later ran tc -s qdisc ls dev eth0 so it should be cleared, right? Third, My distro came with berkeley db 5.3, and won't install 4.8, so I had to compile with --with-incompatible-db flag. Would this make a difference? Fourth, This is a new install because my previous install got messed up (don't chown -R on /usr/bin!). I had my .bitcoin folder backed up, including the blockchain. It looks like the new compile of bitcoind didn't like the old blocks, and so is replacing them with new blocks from sync. Is there something that could have happened here to cause my problem? Finally, I discovered that my swap partition hadn't been mounted and had no swap space. I've re-enabled it and restarted bitcoind but I'm still having problems. What else can I check? I'm on Ubuntu 14.04 server Edit: Also, why do I sometimes see long strings of ORPHAN BLOCK 112, prev=000000000000000033cac1b48e35a41c3834b7678269a5a5e8d3e61b618a6dca in my debug.log? Are there really that many orphaned blocks? Edit2: Here's some more errors I get a bunch: 2014-05-09 12:08:22 ProcessBlock: ACCEPTED 2014-05-09 12:08:24 ERROR: CheckTransaction() : vin empty 2014-05-09 12:08:24 ERROR: AcceptToMemoryPool: : CheckTransaction failed 2014-05-09 12:08:24 Misbehaving: 93.77.226.90:8333 (0 -> 10) 2014-05-09 12:09:13 ResendWalletTransactions() 2014-05-09 12:09:13 Relaying wtx 3e1a26f1814be4146b6574924231d4c0f7fd285660a5d6c001c8d64cff58dc9d 2014-05-09 12:10:12 socket recv error 104
|
|
|
|
So I decided to go ahead and put up a bitcoin full node on a recently repurposed machine. I installed bitcoind and ran the daemon using sudo bitcoind -daemon . The debug.log shows it is syncing the block chain. When I try to issue a command like bitcoind getinfo it responds with error: no response from server I have the bitcoin.conf file set with an rpcuser and rpcpassword, but I'm running the commands from the same machine so I shouldn't need rpc authentication, right? Additionally even if it did need rpc authentication, I should still get SOME kind of response, right? What am I missing here?
|
|
|
|
|
Is there any talk about the next major US bitcoin conference? I'm interested in attending and would like to start making arrangements. Any one have any word, or barring that a newsletter I can sign up for to get updates? I believe the last one was in San Jose.
|
|
|
|
I just found out this morning that the "Ignore" button in classic skin gets darker the more people ignore a person. This feature is not available in all skins.  Can this be addressed? I'd prefer a black background but want to know if someone is widely seen in the community as a troll.
|
|
|
|
I know there's been a lot of discussion regarding the Avalon chips. I don't have a huge stake in this game, but a couple hundred is enough for me to treat my family to a couple of nice dinners or a weekend trip. I understand we knew that there were risks, and so this post is not an attempt to seek some kind of restitution. I just simply want to know what happened. Chips were supposed to be shipped out 6 weeks ago. You claim that 200K chips are held up in customs and have been there for two weeks. So here are my questions. - Why were the chips 4 weeks late?
- Why are the chips held up in customs?
- Are you doing anything to get the chips out of customs?
- When can we expect additional shipments to come out?
- Do you have any plans to make up for this delay with people who trusted you with millions of dollars in capital?
I'm not on a witch hunt here, I just think the community as a whole would really appreciate a more complete picture. You are frequently active on the forums, so I know you've been monitoring the situation, even if only passively. Yifu, please let us know what is going on with our chips. We just want to know.
|
|
|
|
Update 08/01/2013There's been no interest at this price point for a group buy, considering more than 3 makes it pointless to add a step in. Therefore I've decided to go ahead and close it up. I'll be watching the Nano landscape closely, and you may see me attempting to start up a group buy somewhere else if there is a need. Thanks for the votes of confidence to those who were willing to jump in early.
So I've decided to take the plunge and go ahead and start taking names and quantities for the group buy. I'm building in the cost of 2 miners into the price so I get a little compensation for putting this together and executing it well. I'll also be purchasing 2 of my own. Please remember that the risk you are taking is not only with me, but with Bicknellski and his company Big Picture Mining. I've contacted John K for escrow, and I am hoping he will accept my request, so I've built his 2.5% escrow fee into everything. Our first target is 50 miners. According to the Bicknellski Website ( https://bigpicturemining.com/klondike-miner), miners are currently priced at $49.99. Should we receive pledges for more than 50, we'll recalculate shipping from Indonesia and retarget at 100 miners. If we don't get 50 miners, I'll dissolve the group buy and return any already commited funds. Bigger is better here, folks. Breakdown: Miners:$49.99 * 50 = $2499.50 Handling: $4.95 Shipping to USA: $90.00Shipping to USA: $40.00Subtotal: $2594.45Subtotal: $2544.45Escrow Service: (2594.45 * .025) = $64.87Escrow Service: (2544.45 * .02) = $50.89Total before shipping: $2659.32 / 48 = $55.41 per unit.Total before shipping: $2595.34 /48 = $54.07 per unit.Shipping will be done USPS First Class with tracking for up to 10 miners and is only available to the continental US at quoted prices. Other locations PM me for quotes. Shipping for 1 unit will be $3.25. Add $.75 for each additional miner up to 10. I'll only ship in units of 10 to mitigate risk of loss or damage. If you want 20 I'll send you 2 boxes. All of these prices are subject to change should Big Picture Mining change it's policies. I will update this thread once a day (barring unforeseen emergencies) even if no progress is made. I know what it's like to be left in the dark and I won't do that, even if I have nothing to report. Please PM me or post in this thread your pledge. When/If John K provides us escrow, we can begin collecting money. I'll be working out how to take bitcoin while mitigating my own risk, since Bicknellski has pegged his price to USD. Let's get started. 46 left. Update 1 2013-07-2633 already vouched for. 17 left to hit the 50 mark. Tracking sheet here: https://docs.google.com/spreadsheet/ccc?key=0ApT7WUJuJCwMdDBtN2VSNXhxczgxT2toWVhXb1ZlbXc#gid=0Update 2 2013-07-263Currently, even should we reach 50, we are holding on the following points: - Waiting on John K to respond for escrow
- Waiting on Bicknellski to finalize shipping methods & costs (website is under maintenance)
- Trying to figure out how to mitigate bitcoin volatility risk when using escrow
For bullet point three, one way to go is to take payments for a specific low exchange rate (say 1 BTC = $75) and then refund back any extra after the transaction. I'm unfamiliar with this process when using escrow. If I was receiving the money directly I would probably use Bitpay or just sell on the exchange myself (which would mean another little bit on top to pay for exchange fees), but I understand that escrow eases people's minds. Any ideas or suggestions would be welcome. Also, I'm not sure what the shipment from Indonesia will cost as far as customs is concerned. That would also have to be included in the price. Update 3 2013-07-26John K has accepted the request for an escrow service, and his fee is only 2% as opposed to the 2.5% I quoted before. In addition, Big Picture Mining's site has fixed their shipping costs, and for an order of 50 the cost is $40.00 (not including customs fees). If anyone familiar with receiving packages internationally can give us an idea of what customs costs will/might be, I'll incorporate an estimate into the spreadsheet. All pledges and price changes updated in the spreadsheet and in OP. Update 4 2013-07-26Just checked; if we get 100 miners, shipping is $65. This would bring the price to $52.76 each before shipping. Update 5 2013-07-26This group buy will be accepting bitcoin only. I can't be held responsible for chargebacks; I don't have the funds to do so. I'm currently trying to ascertain the best way to collect bitcoin so as to hedge my own risk of receiving it. Hopefully John K has some experience here; if it was me I would just take bitpay and convert to dollars, or worst case, just sell the bitcoin to convert to fiat. Suggestions are welcome. It's unfortunate that Bicknellski is pegging his miner's price to USD, but bitcoin is still pretty volatile so I don't fault him for it. Update 1 2013-07-27So far the best option for accepting payments is to over-estimate the cost and offer refunds for overages. Therefore, I will price each unit at BTC.64 which does not include shipping to you. Since Bicknellski's website takes bitcoin, the price you end up paying will be determined based on the actual cost of the miners. Once we near completion, we can make another assessment and see how far off the mark we are. I've updated the spreadsheet to show conversion to BTC. I'll be sending John K my identity verification in the morning when I can take some pictures. Update 2 2013-07-27Bicknellski and Big Picture Mining have updated their shipping policies again. They now have EMS Shipping available. Here is the most up to date comparison of the group buy vs direct purchase from Big Picture Mining using EMS shipping (which is cheaper for small amounts of units): | Num Miners | Group Buy | Direct | Difference | | 1: | $57.32 | $70.95 | $13.63 ($13.63 each) | | 2: | $112.14 | $120.94 | $8.80 ($4.40 each) | | 3: | $166.96 | $175.35 | $8.39 ($2.80 each) | | 4: | $221.78 | $225.34 | $3.56 ($0.89 each) | | 5: | $276.60 | $275.33 | -$1.27 (-0.26 each) |
At this point the only reason I can see to participate in this group buy is if you only want between 1 and 3. At four the price difference doesn't really warrent the extra step of shipping to me. As long as the price difference for one remains the same I'll continue the group buy. Update 1 2013-07-28Escrow service has been set up. Please send your bitcoin to 1JtPi2MbvCuMvBGT7VeyoyBcoGLTHYYYDp to secure your place in the group buy. John will send payment to Bicknellski once we've got 50. Thanks John!
|
|
|
|
So I'd like to gauge interest in doing a group buy for Bicknellski's K1 Nano. Here's the order page: https://bigpicturemining.com/klondike-miner/k1-nanoHere's the bitcointalk thread: https://bitcointalk.org/index.php?topic=251831.msg2674532#msg2674532Notice on the order page that if 50 or more are ordered, the price is $65. If we can get 50 Nanos ordered, I'd buy 2 myself, and would ask for 2 as part of organizing the group buy. At $65 per, the total order would be $3250. Divided by 48 would be $67.71. Shipping would be by USPS First class (unless otherwise requested) Shipping would be 83.61 from Bicknellski to me with a handling fee of $4.95; so that would bring the total to $69.55 each before escrow and shipping to you. (which is better than ASICMiner block erupter). Willing to do escrow with John K if he's willing, and would price his fee into the purchase price. To re-iterate; I'm just looking for interest. If enough people want to do this then I'll create another thread for the group buy.
|
|
|
|
|
So I've been seeing a lot of interest in PrimeCoin, and some mention of scientific work being done using primecoin, but I don't get it. What's PrimeCoin doing for the scientific community? The whitepaper says it's not finding new primes because they are too big to work on. Can someone EILI5?
|
|
|
|
 Notice for GPU1 the temp-overheat is set to 85C, the temp-hysteresis is set to 1, and the temp on GPU1 is at 88C. Why is cgminer not reducing the clockspeed to lower the temp? Are my settings wrong?
|
|
|
|
Here's my build: Power: CORSAIR Enthusiast Series TX650 V2 650W ATX12V v2.31/ EPS12V v2.92 80 PLUS BRONZE Certified Active PFC High Performance Power Supply Motherboard: GIGABYTE GA-F2A55M-HD2 FM2 AMD A55 APU: AMD A10-5800K Trinity 3.8GHz FM2 100W Quad-Core Desktop APU (CPU + GPU) with DirectX 11 Graphic AMD Radeon HD 7660D Video Card: SAPPHIRE 100314-5L Radeon HD 6870 1GB GDDR5 PCI Express Video Card (One of the rebranded 5870s) I was mining on the 6870 @ 950 MHz with around 400 MH/s using GUIMiner I was mining on the APU with around 80 MH/s Saturday evening, this happened to my motherboard:  These are two chips labeled DEQ1 and DEQ2 just above the CPU socket. I've RMA'd the board, but I was only using 1 video card (two if you count the onboard one). One other thing, my power supply would run even if the power switch was switched to off, so maybe my power supply is doing something funky. I'm wondering wtf went wrong here, this build is only 4 months old and has been running just about nonstop since then with no issues.
|
|
|
|
|
So for some reason my onboard Radeon HD 7660D just dropped from over 80 MH/s down to 20. I can't figure out why and I can't get it to go back up. I just reinstalled the drivers, nothing. Temp would sit at 65-70 C with spikes to 75 Csometimes, now 30-35 C even when mining. I'm using GUIMiner v2012-12-03; mobo is Gigabyte GA-F2A55M-HD2 with AMD A10-5800K APU, 650W PSU, 16GB RAM on Win7 64.
What can I check? What would cause me to lose 75% of my hashing power?
|
|
|
|
|
I'm trying to understand change addresses, because I had the following situation happen. I backed up my wallet and soon after proceeded to have a computer crash. This wiped my system. Pulled in the wallet I had backed up, and was missing many address labels I had created between backing up and failing (far less than 100, addresses were still stored in wallet). Understanding that a wallet had 100 addresses preloaded, I started recreating addresses and matching up transactions I remembered. I got most of them, and things were ok. The other day, after learning about change addresses, I wondered if creating new addresses in my wallet would uncover those change addresses. It appeared that it did. I have created over 50 test addresses new from my wallet and all of them but one have activity on blockchain.info.
Here are my questions.
1) Is there a way to view all the change addresses that have been created for me or do I have to keep creating them until I have them all? 2) When I create a new address for receiving in bitcoin-qt, does it randomly pick addresses from the pregenerated pool or proceed in order? I had one address that I generated that showed no activity, and then the next one did. 3) Is this optional functionality? Is there a way to turn this on and off? 4) These change addresses all have 0 balance. Do they get transferred? How does this all work?
|
|
|
|
|
Ok, so my computer crashed. I have a backup of my wallet, and I put it on a new computer. However, I generated a couple of new addresses since my last backup and the backup doesn't have a record of them. I'm downloading the blockchain now, but I don't know how to import my addresses into my new bitcoin client so it can update my balances. How do I do this?
|
|
|
|
Hey All, I'm trying to test out paysius before I put it on a working merchant site, but I'm having a hard time figuring it out. I'm using PHP and cURL, but it appears that I can't connect to their server. Here's the pertinent info: I've got the CA.pem installed on my server next to this php <? $gate = "https://paysius.com:53135/api/getnewaddress"
$post_string = "qty=1&key=8GEb5x01u3&hmac=7c3a4c7c2f629942e90983c97db8bae160b822620d16484d1c758daa182421663c0f32c1be58084dcea0054e1eb0cef8e18b2b003841c0e5199193a8b2487d63"
$curl = curl_init($gate); curl_setopt($curl, CURLOPT_PORT, '53135'); curl_setopt($curl, CURLOPT_RETURNTRANSFER, TRUE); curl_setopt($curl, CURLOPT_CAINFO, getcwd() . "/CA.pem"); curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false); curl_setopt($curl, CURLOPT_FORBID_REUSE, TRUE); curl_setopt($curl, CURLOPT_FRESH_CONNECT, TRUE); curl_setopt($curl, CURLOPT_POST, TRUE); curl_setopt($curl, CURLOPT_FOLLOWLOCATION, false); curl_setopt($curl, CURLOPT_POSTFIELDS, $post_string);
$response = curl_exec($curl); if (curl_errno($curl)) echo curl_errno($curl); else var_dump($response); ?>
However, I keep getting a cURL error 7, which tells me that it can't connect. Anyone else use Paysius? What am I missing?
|
|
|
|
|