Bitcoin Forum
May 22, 2019, 04:29:07 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 25 26 27 »
321  Bitcoin / Bitcoin Discussion / Re: The dollar cost of bitmining energy on: July 16, 2010, 05:58:44 PM
Neat chart.

Difficulty just increased by 4 times, so now your cost is US$0.02/BTC.
322  Bitcoin / Bitcoin Discussion / Re: bitcoin trademark? on: July 16, 2010, 05:47:05 PM
No, not related at all.
323  Bitcoin / Bitcoin Discussion / Re: Proof-of-work difficulty increasing on: July 16, 2010, 05:29:28 PM
Yes, about 20 hours.  (120 conf / 6 blocks per hour = 20 hours)  That's the normal length of time before you can spend it.  You know long before that that you won one.
324  Bitcoin / Development & Technical Discussion / Re: 0.3.1 release candidate, please test on: July 16, 2010, 05:26:17 PM
Good point.  If you're going to have more than 8 LAN nodes connect to one gateway node, then you'd better have the gateway node set up so it can receive incoming connections.  Otherwise, while the gateway node has 8 or more connections, it will not try to add any more outbound connections.  As the outside nodes you're connected to come and go, it doesn't make new outbound connections to replace them.  You'll be fine if you can accept incoming connections, then there will be plenty of others connecting to you.
325  Bitcoin / Development & Technical Discussion / Re: Source code documentation on: July 16, 2010, 05:15:47 PM
It's in init.cpp.

It's a wxWidgets app, so it doesn't have a main() function.  It may in a little while, since I'm pretty close to making bitcoind build w/o wxBase.  (it'll be in init.cpp)

Sorry about my choice of the filename "main.cpp", another possible name would have been "core.cpp".  It's much too late to change.  I still prefer main.cpp.

We're still in great need of sample code showing the recommended way to use the JSON-RPC functions, like for a basic account system on a typical storefront website.  Using getreceivedbylabel using the username as the label, changing to a new bitcoin address once the stored one for that account gets used.  I posted a sample code fragment on the forum somewhere.  (search on getreceivedbylabel or getnewaddress)  The sample code could be a plain vanilla bank site where you can deposit and send payments.
326  Bitcoin / Bitcoin Discussion / Re: Proof-of-work difficulty increasing on: July 16, 2010, 04:56:54 PM
It adjusted to 181.54 a few minutes ago.  Typical time to get a block is about a week now.

The difficulty can adjust down as well as up.

The network should be generating close to 6 blocks per hour now.
327  Bitcoin / Development & Technical Discussion / Re: Request: expected bitcoins per day display on: July 16, 2010, 04:47:14 PM
Many businesses are like that.  For a car salesman, when will the next customer walk in the door?

On the OP's question, it's a good feature, but the question is, how would we word it so people don't expect to get something after that specific amount of time?  "it said 7 days and I waited more than a week and didn't get anything!"  Approx, average, but still they're going to think that way.  It can't be a whole sentence, unless we think of somewhere else to put it, but where would that be?  Suggestions?

The difficulty quadrupled a few minutes ago to 181.54.  It's going to take typically about a week to generate now.
328  Bitcoin / Development & Technical Discussion / Re: Hash() function not secure on: July 16, 2010, 04:13:53 PM
SHA256 is not like the step from 128 bit to 160 bit.

To use an analogy, it's more like the step from 32-bit to 64-bit address space.  We quickly ran out of address space with 16-bit computers, we ran out of address space with 32-bit computers at 4GB, that doesn't mean we're going to run out again with 64-bit anytime soon.

SHA256 is not going to be broken by Moore's law computational improvements in our lifetimes.  If it's going to get broken, it'll be by some breakthrough cracking method.  An attack that could so thoroughly vanquish SHA256 to bring it within computationally tractable range has a good chance of clobbering SHA512 too.

If we see a weakness in SHA256 coming gradually, we can transition to a new hash function after a certain block number.  Everyone would have to upgrade their software by that block number.  The new software would keep a new hash of all the old blocks to make sure they're not replaced with another block with the same old hash.
329  Bitcoin / Development & Technical Discussion / Re: Source code documentation on: July 16, 2010, 03:37:00 PM
I like that in libraries for the external API's, but you can probably tell from the code that I'm not a fan of it for interior functions.  Big obligatory comment headers for each function space out the code and make you hesitate about creating a small little function where the comment header would be bigger than the function.  They're some trouble for maintenance, as changes to the function then require duplicate changes in the comment header.  I like to keep code compact so you can see more code on the screen at once.

To add them now at this point, what would be written would just be what's obvious from looking at the function.

The external API we have, in rpc.cpp, the usage documentation is in the help string.

Sorry to be a wet blanket.
330  Bitcoin / Development & Technical Discussion / Re: 0.3.1 release candidate, please test on: July 16, 2010, 03:09:59 PM
Because of all the dependencies that different systems don't have.  It's easier to just static link what we can.  It doesn't increase the size by very much.
331  Bitcoin / Bitcoin Technical Support / Re: Resending transaction on: July 16, 2010, 03:01:33 PM
Bitcoin automatically rebroadcasts your transactions if it receives new blocks that don't contain them.  It may take about an hour to get rebroadcasted.  It is relentless though.  It will keep nagging the network forever until your transaction gets into a block.
332  Bitcoin / Bitcoin Technical Support / Re: Fedora 13 libcrypto on: July 16, 2010, 02:55:23 PM
Please try the 0.3.1 release candidate, it should at least resolve the libcrypto dependency:

http://bitcointalk.org/index.php?topic=383.0

Let me know if that works.
333  Bitcoin / Bitcoin Technical Support / Re: Assertion Failure - Ubuntu Lucid on: July 16, 2010, 02:52:04 PM
That's the first time I've seen this error.

How many blocks do you have? (in the status bar)

You should move your blk*.dat files (in ~/.bitcoin) to another directory and let it start over downloading the block chain again.  If you don't mind, could you keep the old blk*.dat files for a little while in case I need to look at them?
334  Bitcoin / Bitcoin Discussion / Re: Proof-of-work difficulty increasing on: July 16, 2010, 02:46:12 PM
The proof-of-work difficulty is currently 45.38.  (see http://www.alloscomp.com/bitcoin/calculator.php

It's about to increase again in a few hours.  It's only been 3-4 days since the last increase, so I expect it will increase by the max of 4 times, or very nearly the max.  That would put it at 181.54.

The target time between adjustments is 14 days, 14/3.5 days = 4.0 times increase.
335  Bitcoin / Bitcoin Technical Support / Re: "SetIcons(): icon bundle doesn't contain any suitable icon" on: July 16, 2010, 02:43:29 AM
That must be it then.

It must be looking for a larger icon like 20x20 but we don't have one.
336  Economy / Marketplace / Re: Donations to freebitcoins.appspot.com needed! on: July 16, 2010, 02:02:07 AM
5 BTC seems like a lot these days, maybe the normal amount should be 1 or 2 BTC.

This is an important service so new users can at least get something if generating is too hard.
337  Bitcoin / Development & Technical Discussion / Re: 0.3.1 release candidate, please test on: July 16, 2010, 12:44:32 AM
Run it with the undocumented switch -minimizetotray and the option is available in the options menu.

I don't know how to fix it.  It's something wrong deep inside wxWidgets or GTK or Gnome.
338  Bitcoin / Bitcoin Technical Support / Re: "SetIcons(): icon bundle doesn't contain any suitable icon" on: July 15, 2010, 11:41:23 PM
in 120DPI mode.
What is "120DPI mode"?  Is that an actual setting somewhere?  Sounds like an obscure enough candidate.  I suppose it needs twice the resolution icon to fill the size of the upper left corner icon.  Only one size is provided.
339  Bitcoin / Development & Technical Discussion / Re: 0.3.1 release candidate, please test on: July 15, 2010, 11:23:04 PM
I don't see either happening, although it did get put into the "Startup" folder.  That is so Windows 95ish (just kidding..... Microsoft has so screwed this up that it isn't even funny).  I would recommend the registry settings for a number of reasons including the fact that most software puts the startup in that location, even though I personally find the startup folder to be more attractive and how most software on Windows should behave.
It could go either way.  The Startup folder has the advantage that the end user can see it and manually remove it with the regular UI (not regedit) if they already blew away the Bitcoin directory and its uninstaller.  Bitcoin will not relentlessly keep re-adding it if you delete it manually.

OpenOffice is another example of something that puts its link in the Startup folder.
340  Bitcoin / Bitcoin Technical Support / Re: Runaway CPU usage for 64bit BitCoin (Linux Client) on: July 15, 2010, 10:22:30 PM
The fix for the thread priority level on linux is available in the 0.3.1 release candidate here:
http://bitcointalk.org/index.php?topic=383.msg3198#msg3198
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 25 26 27 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!