Bitcoin Forum
October 22, 2018, 09:00:32 AM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: « 1 ... 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 [360] 361 362 363 364 365 366 367 »
7181  Bitcoin / Development & Technical Discussion / Re: Trojan Time Machine Chain on: August 03, 2010, 06:09:42 AM
It seems that broadcasting your version of block 70,000 or whatever would immediately trigger Reorganize(), which would delete it and make all later blocks invalid. (Assuming I have all the blocks.)

You couldn't modify blocks before ones that are locked in, in any case. (Lockin is at line 1362 of main.cpp.)
7182  Bitcoin / Development & Technical Discussion / Re: How do clients enforce the 50 BTC generation rule? on: August 03, 2010, 04:15:03 AM
The block won't be accepted by legitimate users. See ConnectBlock in main.cpp:
Code:
    if (vtx[0].GetValueOut() > GetBlockValue(nFees))
        return false;
(Line 1089)
7183  Bitcoin / Development & Technical Discussion / Re: JSON-RPC password on: July 30, 2010, 05:54:36 AM
When I upgraded from a version with switch-based passwords to the latest SVN, I ran into a problem: Bitcoin looks for the configuration file in the default "~/.bitcoin/bitcoin.conf" unless I point to any non-existent file. Example:
Code:
$ ls /home/theymos/bitcoin
addr.dat      blkindex.dat  debug.log          status.sh
bitcoin.conf  command.sh    debug.log.old.bz2  stop.sh
bitcoind      database      makefile           transfer.sh
blk0001.dat   db.log        start.sh           wallet.dat

$ ./bitcoind -datadir=/home/theymos/bitcoin -conf=/home/theymos/bitcoin/bitcoin.conf && ./bitcoind getinfo
error: You must set rpcpassword=<password> in the configuration file:
/home/theymos/.bitcoin/bitcoin.conf
If the file does not exist, create it with owner-readable-only file permissions.

$ killall bitcoind

$ ./bitcoind -datadir=/home/theymos/bitcoin -conf=/home/theymos/bitcoin/asdf.conf && ./bitcoind getinfo
bitcoin server starting
error: You must set rpcpassword=<password> in the configuration file:
/home/theymos/.bitcoin/bitcoin.conf
If the file does not exist, create it with owner-readable-only file permissions.

Warning: To use bitcoind, you must set rpcpassword=<password>
in the configuration file: /home/theymos/bitcoin/asdf.conf
If the file does not exist, create it with owner-readable-only file permissions.

Bitcoin is using the correct datadir. Hardcoding the path in util.cpp just gives me "error:getinfo" (though maybe I'm not doing it correctly). Removing the "pathConfig.is_complete()" if statement does the same thing.

I'm on Linux with glibc 2.10.1. I'm using all of the recommended dependency versions. The only dependency I changed during the upgrade was Boost, which I had to recompile to get the additional libraries that Bitcoin now uses.
7184  Bitcoin / Bitcoin Technical Support / Re: wiki registration email? on: July 29, 2010, 03:07:29 AM
WTF?  How did we get on that?  AFAIK, the only e-mail is if you tell the forum to do notifications, and I guess the wiki registration.  I'd consider turning off the forum notification e-mails, I don't know why we have that.

The PBL blocks all hosts that it believes "should not" be sending mail, without any regard for whether it's actually spamming. Whoever owns the bitcoin.org IP address can request removal here.
7185  Economy / Trading Discussion / Re: Looking for a market maker on: July 27, 2010, 12:23:22 PM
Bitcoin's JSON-RPC deals with floating-point numbers internally, so you need to modify the code to get real precision. Here's a function I wrote to do that:

Code:
std::string taToString(int64 source)
{
std::string number;
std::string splitnumber;
std::stringstream strstream;
strstream <<source;
strstream>>number;
int ti=number.length()-1;
bool tdone(false);
while(ti>-1 || tdone==false)
{
if(ti==number.length()-9)
{
splitnumber="."+splitnumber;
tdone=true;
}
if(splitnumber.length()==0)
{
splitnumber=number[ti];
}
else if(ti>-1)
{
splitnumber=number[ti]+splitnumber;
}
if(ti<=-1)
{
splitnumber="0"+splitnumber;
}
ti--;
}

return (splitnumber);
}

Put that in rpc.cpp and replace all instances of nAmount / COIN with taToString(nAmount). Then you'll get a precise string instead of a double.
7186  Bitcoin / Bitcoin Technical Support / Re: wiki registration email? on: July 26, 2010, 03:30:54 PM
As a follow-up, switching to a completely different ISP (I just created a new "throw away" e-mail account to see what was going on here) I was able to get the registration to be completed.  Still, bitcoins.org is on some kind of e-mail blackhole list or at least the ISP that hosts the e-mail server for registration is on one of those lists.

Looks like bitcoin.org is listed on the PBL.
7187  Bitcoin / Development & Technical Discussion / Re: a simple traffic load test run on: July 26, 2010, 01:57:49 AM
Stress testing the "test network" is a way to at least not annoy those who are trying to do positive things with Bitcoins.  Tests of this nature will naturally be causing more work for others who are not necessarily wanting to be involved in these kind of tests.  Those running the test network realize the very experimental nature and don't mind CPU and disk bandwidth being wasted for those efforts.

From a purely ethical point of view, I think it is much better to test on the test network first, especially if it is to exploit something in the communications protocol that you think needs to be strengthened.

The goal (my goal, at least) is to have some working distributed monetary system, not to keep a (potentially) broken system online without interruption. The whole idea of a "test" network is nonsense -- every test should be done on the main network if possible, since real problems that could occur might otherwise be missed.
7188  Bitcoin / Development & Technical Discussion / Re: a simple traffic load test run on: July 25, 2010, 04:05:06 PM
Please do these tests on the test network.  That's what it's for.  Thanks.

You can't get real data from such a small network. Besides, a reliable network must be able to withstand any kind of testing.
7189  Bitcoin / Development & Technical Discussion / Re: a simple traffic load test run on: July 25, 2010, 03:00:43 PM

No.
7190  Bitcoin / Development & Technical Discussion / Re: a simple traffic load test run on: July 25, 2010, 01:13:16 PM
There was a lot of slowdown in the rate of transactions during the second half of the test. If this was a problem with the network, then I would be very worried about future denial of service attacks. Hopefully a bigger test can be organized later.

Here is a packet capture of the event (from an "edge" computer with only one connection) if anyone is interested in exact times and stuff.
http://www.freefilehostingnow.com/filedownload.aspx?code=6bb2dbeea18e6a419daaadda5798bb05ec6b
7191  Bitcoin / Bitcoin Discussion / Re: The MOST Important Change to Bitcoin on: July 24, 2010, 07:20:15 AM
- No dependencies.
- A better way of handling "dust spam" than just forbidding those transactions for now. I anticipate problems with this in the future.
- The difficulty should be automatically reduced to the previous level if no blocks are produced for x hours.
- I'd like "complete" documentation: all non-trivial parts of the source code written in English.

I think the existing economic model is perfect.
7192  Bitcoin / Bitcoin Discussion / Re: I Generated 50.02 BC on: July 23, 2010, 02:31:08 AM
http://www.bitcoin.org/wiki/doku.php?id=transaction_fee
7193  Bitcoin / Development & Technical Discussion / Re: Calculate Hash Target and Probability in PHP on: July 23, 2010, 02:25:42 AM
The difficulty is based on the *minimum* target, and this target is generated rather inexactly as 00000000ffff000000000000000... (eight 0s, four Fs, 0 to taste Cheesy)

No. That target (which I included in decimal in my second formula) is the maximum allowed target. The target is lowered to increase difficulty. The highest target is the lowest difficulty.

This is because the probability of winning with one hash is target/max. Reducing target reduces the probability of winning.
7194  Bitcoin / Bitcoin Discussion / Re: blkindex.dat on: July 23, 2010, 02:17:45 AM
Generation never "stops" - the number of coins generated gets halved every 210,240 blocks (4 years). It will take somewhere around 17.5 years from block 0 to generate 20 million coins. The next 1.024 million will never be completely generated. Generation won't "stop" until the number of coins generated per block is less than 10^-8 (minimum precision of Bitcoin). That will happen somewhere around block 6.76*10^6, or roughly 130years in the future.

Bitcoin has a Merkle Tree implementation that allows old block transactions to be purged or something like that. Read the design paper, it's all a little above my head.

Besides, in 10 years our phones will all have a terabyte of storage and our desktops will have god knows how much.

It will stop. The halving is done as a bitwise right shift instead of division, so the number of coins awarded will eventually be 0. Block #6,929,999 will be the last one to produce coins. This should happen around 2140.
7195  Bitcoin / Bitcoin Discussion / Re: Nenolod, the guy that wants to prove Bitcoin doesn't work. on: July 22, 2010, 08:48:34 PM
Anyone know when the next block that difficulty will be reevaluated at will be?

http://theymos.ath.cx:64150/q/nextretarget
7196  Bitcoin / Development & Technical Discussion / Re: Design Diagrams? on: July 22, 2010, 07:21:38 PM
Is the bitcoin address a SHA-1 hash of the public key? or perhaps some other 160 bit hash? and why is it a 34 character string instead of say the more common 32 char 5 bit representation?

It's a RIPEMD-160 hash of the SHA-256 hash of the public key. It also contains version information and a check code.
7197  Bitcoin / Development & Technical Discussion / Re: How to Backup Wallet on: July 20, 2010, 10:47:43 PM
Yes. But make sure you stop BitCoin before doing that.
7198  Bitcoin / Bitcoin Discussion / Re: They want to delete the Wikipedia article on: July 20, 2010, 07:36:20 PM
Quote from: satoshi
How long does Wikipedia typically leave a question like that open for comment?

7 days from the listing (so pretty soon). More if the closing administrator doesn't feel that a consensus has been reached.

I doubt the article will survive the AfD, but it will be easy to recreate once it appears in a real news source.
7199  Economy / Trading Discussion / Re: Personal Info w/ Payment Processors on: July 20, 2010, 01:26:46 AM
Quote
With Pecunix, you have to set a name which doesn't have to be your real name and can easily be changed. It is displayed when sending or receiving payments.

Liberty Reserve does that, too. The receiver can also see the sender's account number unless the sender paid extra for privacy protection.
7200  Economy / Marketplace / Re: List of honest traders. on: July 19, 2010, 08:08:11 PM
  • Atlas
  • BitcoinFX
  • BrightAnarchist
  • _DarK_
  • Diablo-D3
  • Keefe
  • Kiba
  • NewLibertyStandard
  • OneFixt
  • Xunie
  • c3e0a4636987bcc7152e6b8b9127c4fe (PayPal MD5)
  • dwdollar (Bitcoin Market)
  • grondilu
  • jgarzik (Bitcoin Store)
  • mtgox
  • nanotube
  • sturles
  • xxmalouinxx

People listed in bold had the opportunity to scam me for a large amount of money.
Pages: « 1 ... 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 [360] 361 362 363 364 365 366 367 »
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!