How was your account compromised? Did you have a very weak password?

A few other users claim to have had their accounts compromised today, though these users were just posting useless garbage, not scamming. The attacker seems to come from 83.167.240.*.

No, it's not. "Cipher" is a synonym for "encryption algorithm". The core Bitcoin protocol doesn't use any encryption.

The word is still commonly used in the terms "block cipher", "stream cipher", "symmetric cipher", "ciphertext", "cipherspec", etc.

Only the top item in the scriptSig is taken to be a serialized script. The others there would not be executed.

That DoS attack is still prevented because serialized scripts still have their sigops counted and limited.

No. P2SH transactions can only have data in the scriptSig -- the OP_DUPs wouldn't be allowed.

806.

At the moment I slightly prefer BIP 16 over 17. BIP 16 seems a little more security-conservative because the scripting system isn't being modified and non-P2SH scripts will not be touched at all. There's no chance that anyone will actually want to use "OP_HASH160 [20-byte-hash-value] OP_EQUAL" as their entire scriptPubKey unless they're using P2SH, so I don't believe that BIP 16 undermines Script.

I find P2SH's use of special-case-scripts to be inelegant, though Script is already inconsistent and inelegant, so I don't care that much. Hopefully when the max block size is increased, Script will be totally revamped to fix all of the imperfections.

I'm amazed at how much argument there is over this tiny issue. BIP 16 and 17 have few real differences (and these differences are very technical), but it seems like everyone on this forum has some strongly-held opinion about it.

This would be interesting:
- RISC-like simple ops only.
- Each block can define one new script function which can be called in scripts by specifying that block number.
    - Obviously functions should only be called once the block is so deep in the chain that there is no chance of it ever being replaced.
    - Most scripts will just call a single function, keeping the block chain size low.
    - Frequently-used functions (like the normal CHECKSIG function) can be handled specially by nodes so that the script processing doesn't need to be done every time the function is used.
- Input to scriptPubKey goes in two separate fields: one unsigned for scripts and one signed for non-signature data. Neither can contain any "raw" script. The length of each item in the unsigned field can also be optionally signed.
- For P2SH-style functionality (and looping), the script will be allowed to execute any data with something like OP_EVAL. However, each OP_EVAL must be given a constant number which will be used as the maximum number of opcodes that can be executed through that OP_EVAL (possibly through multiple nesting levels, and including the opcodes used in functions). The maximum cost of running the script can then be calculated accurately without actually running it.

I think the security of this system would be easier to prove. Since functions are only aliases for a sequence of simple ops, you'd only need to prove the security of a handful of simple ops. There are also no weird special cases like OP_CHECKSIG and OP_CODESEPARATOR.

This system also allows much of the crypto to be replaced without requiring everyone to upgrade.

PHP is my favorite language for small projects. It's far from the best language for any task, but it has so many built-in functions that you can do anything with it. I've even written a little Bitcoin network client with it.


You can use ErrorException to change this.


There's a reason for this, though it probably could have been done in a better way. Text after a dollar sign is just a string representing the variable name, so you can do stuff like this:
Bitcoin Block Explorer uses this feature to create variables from the slash-separated data in the URL:

I'm planning on spacing out the current titles and adding more once the new software is done. The new software will determine titles based on both post count and time online so that people aren't incentivized to post a lot of low-quality stuff.

Ubitex, unfortunately. I thought this was a very good idea.

Also, the original Bitcoin wiki is down now. (I still have the database if anyone's interested.)

As Matthew mentioned, topics in "Auctions" are item-specific, so this can't really be fixed without creating annoying restrictions or adding subsections for very specific things.

Solutions:
- You can post your auctions elsewhere. Auctions are not required to go in the "auctions" section.
- You can advertise your auction in another section so that people don't have to dig through many other auctions to see yours.

You should use this page instead:
http://blockexplorer.com/q/getsentbyaddress

It's much less likely to change randomly.

Right. Both versions were correct. BBE was ordering those sends "randomly". I changed it to use a consistent ordering.

Or maybe it could be split into "Lenders" and "Borrowers" as you suggest, and then the upper-level "Lending" section will be just for long-term offers.

Does anyone else have comments on how the section should be structured?

PHP or C++ are greatly preferred because I am very familiar with these languages and they are both fast enough. I will consider bids in other languages, though.

You can also have PMs be saved to your outbox by default by changing a setting in your profile.

Maybe a subforum for long-term lending offers and lending sites.

In order to collect more money for the creation of good forum software, the forum is selling ad space in the area beneath the first post of every topic page.

Ads this week will be allowed to contain any non-annoying HTML/CSS style. No images, JavaScript, or animation (no marquee or blinking). Ads must appear 3 or fewer lines tall in my browser. Ads will be prefixed with "Advertisement:". Ad text may not contain lies, misrepresentation, or inappropriate language. Ads may be rejected for other reasons.

There are 10 total ad slots which are randomly rotated. So one ad slot has a one in ten chance of appearing. Seven of the slots (not the normal eight) are for sale here.

The ad lasts 7 days starting from when I put it up.

Stats: On the 20^th of November, 2011, there were about 120,000 views of topics. So one slot would have appeared around 12,000 times per day. The ad doesn't appear on topic pages with only one post, though, and it only appears for people using the default theme. Total views per day on more recent days (in January):
- 12^st: 126538
- 13^nd: 116588
- 14^rd: 115597
- 15^th: 122084
- 16^th: 146852
- 17^th: 136190
- 18^th: 144154

Efficacy stats:
https://bitcointalk.org/index.php?topic=54182.0

Info about the current ad slots:
https://bitcointalk.org/adrotate.php?adinfo

Auction rules

Post your bids in this thread. Prices must be stated in BTC per slot. You must state the max number of slots you want. When the auction ends, the highest bidders will have their slots filled until all eight slots are filled.

So if someone bids for 8 slots @ 5 BTC and this is the highest bid, then he'll get all 8 slots. If the two highest bids are 8 slots @ 4 BTC and 1 slot @ 5 BTC, then the first person will get 7 slots and the second person will get 1 slot.

- When you bid, all of your previous bids are automatically canceled.
- All bid prices must be divisible by 0.5.
- The bidding starts at 0.5.
- The auction end time is 02:00:00 on January 28, UTC. Countdown. (The end time may be extended -- see below.)
- If two people bid at the same price, the person who bid first will have his slots filled first.
- Bids are considered invalid and will be ignored if they do not specify both a price and a max quantity, or if they could not possibly win any slots

If any valid bids occur less than 30 minutes before the auction end time, then the auction will be extended by 30 minutes. If any valid bids occur less than 30 minutes before the new end time, then the auction will be extended again, etc. The time will not extend beyond 6 hours total.

You must pay for your slots within 24 hours of receiving the payment address. Otherwise your slot may be sold to someone else.

Current state:
Slots BTC Person
2 7 FairUser
2 5 geebus
1 4.5 cablepair
1 4 NothinG
1 4 Goat
1 3.5 wm-center.com

Current state:
Slots BTC Person
2 7 FairUser
1 4.5 cablepair
1 4 NothinG
1 4 Goat
3 3.5 wm-center.com