Tja, wenn die ersten 100 (oder 450) BTC an Gewinn eben an den Vorbesitzer gehen statt an mich wäre es sogar zu überlegen, da einfach die Zahlenerstellung auf Blockchain statt manuell zu stellen und Geld zu verdienen. Die Domain ist ja schon mal recht gut, nur leider ist Roulette fast nur in Europa beliebt, nicht in den USA wo die meisten BTC User derzeit sitzen.

Concerning "ponziing" - please really do put the income either to an address you control (sign a message with the private key of that address) and promise to never move that, which can be audited by the block chain or do escrow with someone who does this for you (no pirate deposits etc. - just put it on an (offline) address).

In the end you offer a bet that:
You can sell now e.g. 1000 "1MH/s bonds" for let's say 15 bitcents each.
For the next 6 months you pay in total 3 bitcents per share in dividends, because difficulty rises etc.
Share value on the other hand drops to 5 bitcents because other "1 MH/s bonds" go down as well.
You buy back the 1000 shares for 6 bitcents and earned 6 bitcents per share in total from these early investors.

Your risks:
Difficulty not rising
USD <--> BTC rate swings
Mining bonds not going down, despite bad return rates
Noone buying your bonds
Running out of money for the dividends

Maybe you could offer this as a limited time contract from the beginning?
"Get the earnings for 1 MH/s for the next 12 difficulty changes!" - then you can still bet on difficulty rises via selling at a certain price.
Edit: Then you would put the income from that sale + the 100 BTC (or more, if you manage to raise more via the second issue) in escrow and pay out dividends from these. If you predicted correctly, you have more than 100 BTC left in the end, if you screwed up, you might even have to add more BTC to that fund, depending on how many % more you sold (how much these 100 BTC cover).

Du kennst aber das bisherige Setzverhalten, und einen Martingale Spieler erkennt man doch wohl locker!

Die Spieler werden daran gehindert zu erkennen, dass die 0 zu oft kommt! Derzeit sind 3/4 aller gespielten Zahlen rot. Bei der Stichprobe ist das aber bei Weitem nicht klar ob du jetzt zu oft rot spielst, das geht einfach in der Varianz unter. Auch in deinem Casino sind solche unwahrscheinlichen Runden möglich, aber denen wird trotzdem vertraut weil sie sehr viele Runden spielen.

The block size limit is arbitrary, can be increased and has been chosen to prevent DoS.

sendmany would be probably something useful for deepbit + satoshi's dice...

There needs to be a bitcoind tailored for pool operators, so they can automaticallly include their payouts for free in their own blocks, set cutom fee inclusion rules etc.

There is no reason to sell at 95% of 5day average other than sandbagging, since your dividends are significantly lower than 5% of your 5day average asset value.

Mining bonds are NOT to be expected to become cheaper 5% per week. The actual number is something around 3% per month (Moore's law + 4 year income cut).

It also seems from your edit ("[Edit: Minimum price adjusted for BTC increase in value against USD]") that you are valuating your bond in USD - why?

Naja, das "originalkonzept" ist schon noch immer in Ordnung, nur bisher gab's halt kaum/keinen Anreiz da zu optimieren, was von Anfang an möglich war und auch so im Paper von Satoshi beschrieben ist.

Allerdings gewinnst du sicher bei allen nicht-Zahlenfeldern, sobald eine 0 kommt.

Ohne sehr große Zahlenmengen kann man keine statistische Analyse deiner Zahlenverteilung anstellen, daher kann man auch nicht sagen, ob du die 0 "zu oft" spielst. Klar musst du bei deinem System vor Beginn einer Runde schon festlegen, was gezogen wird und kannst dich (wenn du nicht betrügst und einfach mit den Einsätzen abhaust) nicht rauswinden.

ABER

Da bei Roulette durchaus so einiges an Taktiken bekannt ist (Martingale, 0 = Gewinn für Bank...) könnte man dir leicht vorwerfen absichtlich z.B. 10x eine rote Zahl zu spielen, um Martingale-Zocker auszubluten, selbst falls du wirklich (was ich dir nicht glaube) zufällige Zahlen ermittelst.

Seit mittlerweile 5 Tagen die aktuelle Zahl nicht zu posten ist auch etwas verdächtig, generell finde ich die Idee von Gambling um Bitcoins ja recht ansprechend, aber die derzeitige Ausführung ist mehr als mies.

This was not stated there back then when I bought my bonds.

You are trying to push down the 5 day average pricing of your bond continuously so you can screw everyone who bought bonds for more than 95% of the 5 days average price. Once you dumped the price for your bond enough, you can buy back for far less than you initially sold for and walk away.

I request a minimum price per any bond sold directly via GLBSE of 0.25 BTC (= IPO value), max. 5% discount on bulk sales OTC and issuing new bonds at 105% of the 5 days average instead of 5% below.
I will ask Nefario to disallow bond buyback for this asset until you fully verify with GLBSE as this sandbagging technique seems to much of a scam to me.

No, but maybe it's time to only allow IPOs with a total initial share value of e.g. < 100 BTC for unverified assets. Yes, this can be circumvented by selling OTC, but then it's up to the users to check for identification of their trading partner.

Nefario, do you mean a web site that shows who is verified with you, or a service that actually does verification and it's results can be displayed on GLBSE?

There needs to be much stricter contracts to determine when such informations can be released for that (like missing a dividend payout for 48h for example) and the points in these contracts need to be verifiable with public knowledge, not only via GLBSE insider knowledge ("By the way, the issuer has not even logged in once since 4 months...").

I actually would disagree on that. I would put certain limits on unverified assets though.

Too much JavaScript for my taste, I can't even navigate the tabs on https://cryptostocks.com/securities/2 without JS.

Double the trading fees compared to GLBSE, a signup fee(!), easy to spam assets (1 BTC instead of 8 BTC), no kind of imprint (I want RL names + addresses of the operators!), no terms...

Anyways, let's see what comes out of this, but I fear there will be a LOT of spam and scams, just like on GLBSE 1.0.

Sounds very nice, but would require a special client used to meter the bandwidth and to sign/create these transactions, right?

Also, what happens if the Access Point thinks the user has used 100 MB of traffic, the user client thinks he has used only 99 MB of traffic though and refuses to "pay up"? Overprovision by some percentage? Choke (=rate-limit) the client till he pays up? This might lead to some bad user experience if consequences are harsh and immediate or in some not-paid traffic (or whatever) if there iss too much leeway.

It might work perfectly for per-minute flatrates though, maybe even for "per 10 seconds" types of contracts. Even per second maybe, though this might already start to have some timing issues (or packet loss issues!), especially with wireless connections.

Something where this might also work out, would be a bitcoin powered online hosting provider...

For APs the biggest problem might be to get bitcoins you own into that client - either it has to access your wallet file or it has it's own single private key(s) pre-charged with some amount. One could sell pre-charged private keys at the counter in a cafe for example and the added benefit for the customer would then be that they can use up as much as they like of that and transfer the rest to their wallet and use these as "normal" bitcoins after their session ends.

That way, even if you sell access "vouchers" to the local W-LAN for 30 USD or so while 1 hour only costs 2 USD, they still can afterwards keep and use the remaining balance.

With Cascasius' approach you'd still need to audit the code + trust that the people signing the file etc. are trustworthy and really who they claim to be. Yes, it might be an acceptable risk, but having the block chain yourself and doing the calculations and eventual pruning yourself is still what you need to be ultimately sure. For that you need to have all 200k blocks (pre-pruned or not).

D&T: Yes, you don't need 100% of all transactions, "only" 100% of all currently unspent transactions (something that's not always easy to find out) + block headers. Eventually it might also be nice to have then still stored/hashed in merkle trees, so you can hand at least pruned blocks to the P2P network. It can be estimated that in the future, clearly spent transactions will be pruned as fast as possible, things like this database though might start to bloat these unspent TX. On the other hand, store and delete operations would then be possible, leading to a write being a delete + a new store.

They definitely DO need the whole block chain, otherwise they might include an invalid/double spent transaction and loose a block, because this block won't be accepted by anyone.

This "reliable" set of unspent transactions can only be produced by someone you trust (Bitcoin = 0 trust to others!) or yourself - and this person needs to have the whole block chain to be reliable in filtering out bad transactions.

http://betsofbitco.in/item?id=423 finished, "False"
Proof:
http://bitcoincharts.com/markets/mtgoxUSD.html

Emails are also always just emails, regardless of content. Still I consider some as spam and some not.

Great way of making profits:

Sell bonds for 1.50, sell later for ~1, wait until the price tanks + 360 hours, buy back for ~1.05. 45 bitcents per bond profit - mining payouts (which are ~20 bitcents) - 5 bitcents per share sold at 1 (guessing equal amounts of shares sold at 1.50 and 1) = ~20 bitcents per share sold at 1.50 profit. Not pirate rates, but not a bad deal by far either.

This is just sick - I'm currently on very slow mobile internet and downloading hundreds of MB of SD spam TXs is leading up to a point where I'm currently considering very much not running a full bitcoind at all any more.

Just imagine having your internet line clogged for 1 hour or more EVERY DAY when booting up the PC and loading the latest blocks.

Wann immer du Geld brauchst, postest du also einfach den Hash einer 0...?!

Offenbar ist da nichts automatisiert (z.B. ist das letzte Bild vom 13.6. noch immer nicht da) und die Runden dauern auch ewig. (Edit: Damit dauert es auch noch Jahre um zu sehen, ob deine "händischen" Zufallszahlen auch tatsächlich zufällig verteilt sind)
Ich würde empfehlen, ähnlich wie bei Satoshi's dice die Zufallszahlen aus Transaktionen (oder noch besser: Blöcken) zu entnehmen. Damit könntest du alle ~10 Minuten eine Runde spielen und man muss nicht ewig auf die Ergebnisse warten. Immerhin spielt bei Roulette ohnehin jeder für sich gegen die Bank, lange Runden sind daher nur nervig.