Show Posts
|
Pages: [1] 2 3 »
|
raXrWUk5qbTyJkVLejcZJnAAqX4pm5x5X4
|
|
|
My Abe installation was stuck on Namecoin block 99501 (2013-03-10 13:15:28). Attempting to rescan the block chain yielded the following error: block 326226 already in chain 3 commit Exception at 463166665 Failed to catch up {'blkfile_number': 1, 'dirname': '/home/notawake/.namecoin', 'chain_id': None, 'id': Decimal('2'), 'blkfile_offset': 463114051} Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 2428, in catch_up store.catch_up_dir(dircfg) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 2493, in catch_up_dir store.import_blkdat(dircfg, ds, blkfile['name']) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 2626, in import_blkdat store.import_block(b, chain_ids = chain_ids) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 1662, in import_block tx['tx_id'] = store.import_and_commit_tx(tx, pos == 0) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 2147, in import_and_commit_tx tx_id = store.import_tx(tx, is_coinbase) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 2091, in import_tx store.binin(txout['scriptPubKey']), pubkey_id)) File "/usr/local/lib/python2.7/dist-packages/Abe/DataStore.py", line 464, in sql store.cursor.execute(cached, params) DataError: value too long for type character varying(20000)
The next Namecoin block, 99502, has a size of 52606 bytes. In order to allow 99502 (and subsequent blocks) to be imported into the Abe database, I dropped the txout_detail view (because PostgreSQL does not allow changing the column types in tables used by views), removed the length restriction from the column txout_scriptpubkey in the table txout, and recreated the txout_detail view. I'm sure this solution is dangerous if someone manages to stuff much larger blocks into a block chain, but I do not know a reasonable limit for this column yet.
|
|
|
What happened to me was that Abe would act like it was up to date. I saw blkfile_number set to 1 and the last modified for blk0001.dat at the same date with a blk0002.dat, so I added the row with blkfile_number = 2. Then I got a permissions error from Abe on the second file, changed the permissions, and it worked. I'm checking the datadir now and it appears that the existing row also now has the right blkfile_number, so adding the row was not necessary. I'll correct my previous post.
|
|
|
My Abe installation stopped updating after block 188421. (2012-07-10 11:26:50) The problem appears to be that Abe only looks at blk0001.dat by default and does not look at blk0002.dat, which my Bitcoin client created after block 188421.
I fixed the issue by adding the following row to my datadir table and then running Abe to update the database with the new block file's data. [row removed]
However, this is not a permanent fix since Abe will stop updating once the client makes a blk0003.dat and so on until I manually add the row for each block file.
UPDATE: This was a permissions issue on blk0002.dat. Adding a row to datadir for each block file is not necessary.
|
|
|
Hello All,
I am looking for a way other than Gox to convert BTC into US Dollars or Thai Baht. Interested in all ideas.
I will need to do this to pay for the power.
Thanks.
If you don't mind me asking, what was the problem with Gox? I would imagine they have the best liquidity and alternatives may end up costing more in transaction fees, spread, etc.
|
|
|
We had one of the mother boards go bad, I sent it in because it is under warranty. They checked it out and said the damage was due to water or liquid and thus it is not covered. I do not know how water would have got on the board and once I told them this they said maybe a mouse pissed on it. I had to laugh. Anyway it was not in a closed case.
What should we do,
1) fight the warranty
2) fix it at cost
3) replace it
4) do nothing
These guys have been pretty good about fixing all my stuff. About 10 dead cards, 2 other MBs, and one PSU. It will be kinda hard for me to come in swinging about the warranty esp since I can't prove it was not a mouse. Odds are if it was an animal it was a one of the lizards that come and go.
The mother board was one of the lower end boards that supported 4 cards.
Thanks.
What are the costs of each option?
|
|
|
Option logfile = false created file named false The same thing happened to me. I had to comment out that line to suppress the log file.
|
|
|
Is this the best place to make requests/suggestions to the pool operator? It would be cool to have an option for email notification of a dead miner. Like an adjustable timer for a miner not producing any shares... Also, thanks for doing a great job keeping the pool up and running so consistently. +1
|
|
|
Has anything been worked out for paying out dividends while this dispute is being resolved?
|
|
|
I would say it depends on the board itself. Some boards have development connectors that allow new code to be put on them while other boards do not have these and can therefore only run the mining programs. Boards that can only run mining programs won't be as valuable as boards that come with development connectors.
|
|
|
18BTC has been paid out to LIF.B, the asset is not being brought over to GLBSE2.0
Nefario
Number of assets paid 820 Total amount paid 18BTC Payment per share 2195121
I don't know if you mentioned this previously, but what about the other LIF assets?
|
|
|
How can I call a function like: getreceivedbyaddress???
For some API calls such as getreceivedbyaddress, you have to specify which block chain (Bitcoin, Namecoin, etc.) to query in the URL. Example usage for Bitcoin: https://hostname/abe/chain/Bitcoin/q/getreceivedbyaddress/1HZRowLTkmF6M8V11vj2dmVf2r9VK7dVfo
Namecoin example: https://hostname/abe/chain/Namecoin/q/getreceivedbyaddress/MxT6tjJZcYZeWUGNgsAMxJ7wpDgKMdub4y
Other API calls can be used for addresses on any block chain. Example: https://hostname/abe/q/addresstohash/1HZRowLTkmF6M8V11vj2dmVf2r9VK7dVfo
The following URL shows the API calls currently supported by the Abe installation and provides links to documentation for each API call.
|
|
|
Personally, I suspect the price of Bitcoin is tied to the amount of media coverage related to Bitcoin because of the seemingly strong positive correlation between media coverage and Bitcoin price.
I don't see BIP 16/17 having a significant impact on Bitcoin prices unless implementation somehow has a negative impact on the network, which I don't predict.
|
|
|
... I just don't care about them anymore...just let them pile up in my NMC wallet. ...
+1 I think the main issue is the lack of demand. Namecoins only have one use right now, which is the .bit naming system. There aren't enough people browsing .bit domains. Maybe if they were seamlessly integrated into tor, adoption would increase and the value of Namecoins would increase. There was a time when Bitcoins were just as new and had a similar low value compared to USD, but I don't foresee the value of Namecoins hitting US$30 within the next few years ...
|
|
|
Can crop circles be square?
From https://en.wikipedia.org/wiki/Crop_circle : A crop circle is a sizable pattern created by the flattening of a crop such as wheat, barley, rye, maize, or rapeseed. Crop circles are also referred to as crop formations, because they are not always circular in shape. Based on Wikipedia's definition, the answer is yes since a square is a "sizable pattern." If your definition is more strict (i.e. focusing on the word circle) than Wikipedia's definition, then the answer is probably no because a circle cannot be a square and vice versa.
|
|
|
Namecoin explorer show the block 36894 to be the lastest http://explorer.dot-bit.org/. But namecoind tells me we are now at 36928. Who tell the truth? My namecoind says 36930 and Namecoin block explorer still says 36894. I think the block explorer is broken right now.
|
|
|
Paid back early, and according to his PMs I only needed to pay 0.25 BTC in interest.
Paid 3.25 BTC to 146WBykHKBEvUwsquA1qWvzoZ2M5GhN8Mg
This is correct.
|
|
|
Pardon my ignorance, but why does this pool require all users to have the same payout threshold?
|
|
|
|