or did he receive too many goatsee?
In that case, nobody will get their stuff back at least until he regains his eyesight... |
|
|
|
|
And another day has passed, apparently without any progress...
Does anybody know why the "account verification system" was taken offline earlier today? Did Nefario get a smackdown from the other shareholders, did his lawyer suddenly tell him not to do it, or did he just suddenly realise that nobody would trust him with that info any longer?
Anyone with some knowledge would like to shed some light on it?
|
|
|
|
Technically, asking for IDs at this moment is totally unnecessary, because the database has not been compromised. You could work with user ID and passwords to resolve any claims. The reason must be rooted in some legal context. At this point I have zero trust in Nefario.
There is absolutely no way I would trust Nefario with such information, and I would be surprised if anyone else would too - he has basically lost all the trust he once enjoyed around here. But I'm still assuming (hoping) it'll all be solved in due time, and I hope friedcat and the gang concentrate on getting the show on the road rather than worrying about the latest drama(s). |
|
|
|
There are now many threads about "colored coins", "smart contracts" and otherwise tracking specific coins through the blockchain. I have created a simple command-line Python program to handle tracking of "colored coins", "smart contracts" or "blockchain securities" in the blockchain. There are other approaches, and the one I have taken is very simple, but it is a working solution (primitively duct-taped and glued together). I also have not read gone into the details of the other approaches, so it is probably safe to say that the method I have created is completely incompatible with the other methods (which are probably much smarter too). But it is a live and implemented solution, which gives it an advantage over others. It is short, easy to modify and fun to play with. It might be useful for some adventurous security issuers who are looking for a solution now that GLBSE is shutting down. Full source: http://pastebin.com/hbUz0vS9Update Oct 15:The source code has been updated, the new version includes functions to pay dividends to holders of the colored coins. Also, it has been tested more thoroughly, and I have created a 12-step usage example that shows the current capabilities of the script. Update Oct 18:The source code has been updated, the new version includes the functions to include a transaction fee from an (uncolored!) address in your standard/satoshi-client wallet when transferring assets so that the transaction is more likely to confirm more quickly (command-line option -w <fee>, where <fee> is the fee you want to pay in BTC, e.g. -w 0.005 for half a bitcent). Also, the tracking of colored coins is now also believed to be compatible with other approaches for "order-based" tracking, such as the one used in killerstorm's modified Satoshi client (however, I still want to build up a bunch of test-cases to see if the clients interpret all the cases in the same way). Next, I think it is time to create ample test-cases, and tidy up the code - it has turned into a bit of a spaghetti-ball. Usage example:
1. First run config setup:
$ python bitpaint.py
Configuration file bitpaint.conf not found. Creating one...
bitcoind rpc host (default: 127.0.0.1):
bitcoind rpc port (default: 8332):
bitcoind rpc username (default: <blank>): ********
bitcoind rpc password (default: <blank>): ********
2. Create address:
$ python bitpaint.py -n
Address added: 1AEn3U5MhedXYRbpxLKmkL4r5Kz1XkdZA
3. Transfer the colored coins to the address (sent 0.01 BTC to the address above using Satoshi client). Make a note of (1) the Transaction ID: 630bccacd6f4401fde53822af3f011daa47ec1bedd1702bf7d0be4391948f49b, (2) the output that was sent to the address above: 1.
4. "Paint" the output of the transaction, call the painted coins "BITFAIR-SHARES":
$ python bitpaint.py -p BITFAIR-SHARES:630bccacd6f4401fde53822af3f011daa47ec1bedd1702bf7d0be4391948f49b:1
5. Show the ownership info of the painted coins "BITFAIR-SHARES", the output is the owner address, the amount the address owns, and the transaction output which assigned ownership to that address, then a line with a total at the bottom:
$ python bitpaint.py -o BITFAIR-SHARES
*** BITFAIR-SHARES ***
1AEn3U5MhedXYRbpxLKmkL4r5Kz1XkdZA 0.01 630bccacd6f4401fde53822af3f011daa47ec1bedd1702bf7d0be4391948f49b:1
** Total BITFAIR-SHARES: 0.010000 **
6. Create three new addresses (could be done by another user, for example the buyer of the security - the buyers should also run the command in step 4 to initiate the coin tracking), and create a transaction that transfers 0.006 to the first address (represents 60% of "outstanding shares"), 0.003 to the second (represents 30% of "outstanding shares) and 0.001 to the third (represents 10% of "outstanding shares"):
$ python bitpaint.py -n
Address added: 1KbDEaZ99YJYaT62emhFwabFoqQ6LYdJg9
$ python bitpaint.py -n
Address added: 1DAHyXPNJjqLGFNqHhavrukWZ6XkY8Kj21
$ python bitpaint.py -n
Address added: 1Mhx4LMjbmN6KJ9B5BkdZ5zVWQP64F5TJC
$ python bitpaint.py -f 1AEn3U5MhedXYRbpxLKmkL4r5Kz1XkdZA:630bccacd6f4401fde53822af3f011daa47ec1bedd1702bf7d0be4391948f49b:1 -t 1KbDEaZ99YJYaT62emhFwabFoqQ6LYdJg9:0.006,1DAHyXPNJjqLGFNqHhavrukWZ6XkY8Kj21:0.003,1Mhx4LMjbmN6KJ9B5BkdZ5zVWQP64F5TJC:0.001 -w 0.005
01000000019bf4481939e40b7dbf0217ddbec17ea4da11f0f32a8253de1f40f4d6accc0b63010000008b483045022100dd23f8d8cc3c92314127badcdd50c22414fe1bdf50215c3edce89f0aa64836bd02200c940f4a5ca59c133f14269c3cc2568e8340ec09d90f65c3264f869e93f28e010141047002cabfc1da529ab13d035a60b11db585be5709ddd7d8ab5649ce5d71a279bcb681007bb929f8adf7d811726cd82da5aa1fa96cd736cca986a79c89186a1e29ffffffff03e0930400000000001976a91485636c3633be3a41ce4893dc84ab31fd2d96ea4f88aca0860100000000001976a914e3211d2305301fe6421dbf85685a2744ca51817e88acc0270900000000001976a914cbea9e8c8392abc07417f95bfcb2f21406c6599088ac00000000
7. The result of the former step is a hex-encoded raw transaction. Because it contains no transaction fees, the standard satoshi client will refuse to send it. However, the resulting hex-encoded raw transaction can be broadcast on the network using http://blockchain.info/pushtx. PS: At the moment, you cannot be sure that the transaction will be included in a block, since it contains no transaction fee (i.e. compensation to the miners). I am currently working on a solution to this.
8. Update list of BITFAIR-SHARES holders, and show it:
$ python bitpaint.py -u BITFAIR-SHARES
$ python bitpaint.py -o BITFAIR-SHARES
*** BITFAIR-SHARES ***
1DAHyXPNJjqLGFNqHhavrukWZ6XkY8Kj21 0.003 d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:0
1Mhx4LMjbmN6KJ9B5BkdZ5zVWQP64F5TJC 0.001 d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:1
1KbDEaZ99YJYaT62emhFwabFoqQ6LYdJg9 0.006 d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:2
** Total BITFAIR-SHARES: 0.010000 **
9. Pay dividends of 0.1 BTC in total from my wallet account named "bitpaint_donations" to the holders of the colored coins ("shareholders of BITFAIR-SHARES") (not sure if this works with an encrypted wallet, should be easy enough to fix for those who have it):
$ python bitpaint.py -d BITFAIR-SHARES:bitpaint_donations:.1
10. List what shares/colored coins are owned by me, their dividends (and address that the shares/dividends belong to, along with the transaction output that assigned the shares to my address):
$ python bitpaint.py -m
BITFAIR-SHARES 0.003 ( div: 0.03 ) 1DAHyXPNJjqLGFNqHhavrukWZ6XkY8Kj21 d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:0
BITFAIR-SHARES 0.001 ( div: 0.01 ) 1Mhx4LMjbmN6KJ9B5BkdZ5zVWQP64F5TJC d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:1
BITFAIR-SHARES 0.006 ( div: 0.06 ) 1KbDEaZ99YJYaT62emhFwabFoqQ6LYdJg9 d8e8dc799be1b552f29f8cbd2df24a1fcb9c2a9f4a43c9b4444b9dc329bbd17d:2
11. Forward dividends from my asset-addresses to one of my wallet addresses:
$ python bitpaint.py -x 1DAHyXPNJjqLGFNqHhavrukWZ6XkY8Kj21 -y 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
0100000001cf707398596a9f8bf45e22e3f736b819f27ba6d10cb9c12f1ca23a9daf0c6f1d000000008c4930460221009eb892e079fd143fd5b1919c0c07073d1d45a671aabb05d2565721ae3f83aee6022100a60706b226ef968038ef654f8b782103170932201b7e9fc9320ec24027c56e14014104f7e514dad77c0dbf157c1cc88d610a512f9809785fda426ca7ee3c70df59afeee521ccb02f610536e093b954c4718a4b9d2c028aaec62ad2f138d0735a0d918dffffffff01a0252600000000001976a9143a572d6755022d568f7a78d0060234920486cd0f88ac00000000
Paid 0.025 to 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
$ python bitpaint.py -x 1Mhx4LMjbmN6KJ9B5BkdZ5zVWQP64F5TJC -y 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
0100000001cf707398596a9f8bf45e22e3f736b819f27ba6d10cb9c12f1ca23a9daf0c6f1d020000008a47304402203ff6f44811c8d772f16535a3482fcb88e0b992cf3f8574b78b32489146212a28022045e2fff119b1124035849f3d54b5f5fa3cf8ebf88463df38df1ee7f4ab4cf358014104dc22a7249282ba829c4351cd9255690aaaa9a9896bd9b95e6075d5a3ec34b305a6eab56f9524f7a4308f418bd4a6eabdaf887a4622874b32cb4f4f55c28e1092ffffffff0120a10700000000001976a9143a572d6755022d568f7a78d0060234920486cd0f88ac00000000
Paid 0.005 to 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
$ python bitpaint.py -x 1KbDEaZ99YJYaT62emhFwabFoqQ6LYdJg9 -y 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
0100000001cf707398596a9f8bf45e22e3f736b819f27ba6d10cb9c12f1ca23a9daf0c6f1d030000008c493046022100b440c8997b43067a2a96ece768487e6f219391491d83b384fe7408f106adea5b022100b7d47531358afdeb75cd4e98753309c175ce71e1d722ab851c363c0b9f80d2b50141043d0c63308cb4dcc98b966922a7f78435d44c89b63bf94485f0920c3434a5077c4004adb067ac319f3ee1b551b451a11154e0e1a8ba1c686d15bde93f89963044ffffffff0160ec5300000000001976a9143a572d6755022d568f7a78d0060234920486cd0f88ac00000000
Paid 0.055 to 16KUdKHHZ1AUVb4ZH6Q2VY55L3V3gCCSmr
12. The result of each command in the former step is a hex-encoded raw transaction. It contains a transaction fee of 0.005, to help it get mined into a block. The hex-encoded raw transaction can be broadcast on the network using http://blockchain.info/pushtx. Your client should see the transaction within seconds.
- GUI Please be cautious when using it, but feel free to criticise, modify and contribute. And if you like it, support it: 1GsnaaAWYMb7yPwBQ19bSLLMTtsfSyjqg3. |
|
|
|
|
This is a great step ahead, and will greatly benefit the proliferation of Bitcoin.
Those who feel that this foundation does not represent their ideals should rather create their own foundation that does. How is that for freedom and decentralization?? This foundation does nothing to change what the bitcoin protocol is, so I cannot understand all the whining. (And I am sure the developers would even accept your new foundation helping to pay for the development too!)
|
|
|
|
That's not how it works at betfair, as far as I remember.
If I try to back at 1.51 for $0.01, then there will be $0.01 exactly available to lay at 1.51.
The stakes get matched exactly.
Your exposure changes though, which I guess is what you were displaying.
Very shrewdly observed, dooglus. I deliberately did it a bit differently than it is done on betfair, thinking that my way makes a bit more sense: the number shown is the highest amount that can be matched at the given price. Let me explain: in the betfair world, if you try to back at 1.51 for $1.00, betfair shows there is $1.00 available to lay at 1.51. However, in order to match your bet entirely, someone will need to lay $0.51 at 1.51. So betfair shows $1.00 available to lay at 1.51, but you need to lay $0.51 to match it. That is why I decided that instead of showing the $1.00 that was backed, I would rather show the $0.51 that was needed to match the bet entirely. The cited amount on my exchange would therefore always have the meaning "maximum amount of money that could be sent to this address and matched". |
|
|
|
Available to back Man City:
5.4
(0.00227272727273 BTC)
1AthfWf966g3jgAbytSposbzPdWYWgfgSR
I don't know where you're getting that number of BTC from, but BTC is only divisible to 8 decimal places.
Duly noted, thanks! That number comes from a calculation that wasn't rounded off: I sent one bitcent to the corresponding lay address, which means there is 0.01/(5.4 - 1.0)=0.00227272727273 BTC available to back. |
|
|
|
|
Thanks, dooglus & Nefario, I appreciate your replies.
It's actually perfectly understandable that people are not terribly desperate to send their money to some anonymous person with no reputation and low post count.
Unfortunately, a service of this type isn't quite in line with regulations in my area, and there's no chance for me to 'go legit'.
Anyway, the match has started, the market has been closed (no bets taken). The service is going down!
I might try again when multisig transactions increase in popularity and ease of use - could make people more comfortable about the whole thing...
|
|
|
|
"spot price", and the "bid-ask spread" are real values. I do not understand / why would that be misleading?
I quite agree. "Spot price" is often considered to be the price at which the last trade was executed. Although this can cause trouble in markets with little liquidity and infrequent activity, as you rightly have observed, since that price may no longer be available for anyone to trade at. Using the average of highest bid and lowest ask as the "current price" can be misleading in cases when they are far apart. Imagine if the highest bid is at 5 and the lowest ask at 15, and the current price was quoted as 10 ((5+15)/2) - a price which really isn't available for anyone to trade at anyway. So pick your poison!  (However, confusion could be easily avoided in the first place if OgNasty changed the text in OP from "Price per share" to something like "Latest traded price". That would be unambiguous enough, right?) |
|
|
|
Apparently, there is a value in the API that matches what you're caching:
"latest_trade": 44650001
You uhm... you do realize that is NOT the current market price in any way shape or form, that is just whatever arbitrary value someone happened to trade at. if someone was bold enough to actually sell to one of the 0.00001 BTC bids, I'm pretty sure suddenly the value for latest_trade would be that, and would stay there until someone bought or sold (traded) at any other random arbitrary value.
Kuzetsa, I believe you are the only one so far in the history of this operation who seems to have misunderstood this. And AFAIK, GLBSE matches trades against the best price available - meaning that if you try to sell a share at 0.00001 BTC, the order will actually execute at the highest bid instead. So the "latest_trade" field is normally at what was either the lowest ask or highest bid at the moment when the last trade went through. Nothing random or arbitrary about that at all! (And using the average of the bid and the ask as a "current price" would be much more misleading, by the way...) |
|
|
|
|
Not much interest so far, even though the odds currently quoted allows for a bit of arbitrage with other betting exchanges.
I guess people who are interested in bitcoin are not so interested in sports, huh?
(Or it could perhaps be TOR frightening everyone away.)
|
|
|
|
Edit: Service has been closed for now. Will reconsider reopening in a slightly new form when/if multisig becomes more popular and easier to use.Hi y'all, I'm making a betting exchange that uses bitcoin - it has currently passed all my in-house tests, and I would now like to invite all of you to test it. There are currently many options for the gambling bitcoiner. At least a large number of casinos, and SD. For those wagering on real-life events, there's a bookmaker who accepts bitcoin, charging a gigantic overbook, of course, and there is the betsofbitcoin, which has a messy, totally unpredictable payout scheme in addition to charging an enormous commission. Therefore, I have written a betting exchange, similar to for instance Betfair and Betdaq, that tries to leverage the strengths of bitcoin. A betting exchange is a peer-to-peer platform for betting - instead of betting against the house, you are betting with other users. You select the event you want to bet on, the selection you want to bet on (or bet against), and the odds you want, send your bitcoins to the address for those odds, and your bet is matched against the bets of other users or returned if your bet is not matched before the market closes. In this testing period you can only bet on tomorrow's UEFA Champions League match Real Madrid vs Manchester City. The market closes at the scheduled kickoff. Of course, no commission will be charged during this testing period - winnings are paid out in full (apart from a small transaction fee to the miners to ensure the transaction is confirmed in reasonable time). The testing period has essentially two purposes: - Testing the technology: it has passed all in-house tests, but has not been exposed to the wider world yet. Hopefully there are no serious bugs, but be warned!
- Collecting feedback on the concept: I would very much appreciate your honest opinion on the concept of a betting exchange built in this way. What things are bad? What things are good? What is missing? What is superfluous? What is confusing? All feedback will be greatly appreciated.
Visit the site here: http://56ft5sy3qg6q5ua3.onion/http://56ft5sy3qg6q5ua3.tor2web.org/Click on "Help" in the top navigation bar to learn more about the service. How do I place a bet, and how are my winnings paid?Very simple: just send bitcoins to the address corresponding to the odds you would like to bet at ("back") or against ("lay"). Longer explanation: Visit the site, and follow the link to the event you want to bet on. This will take you to the market summary screen, showing the selections and the odds currently available in our book. If you would like to back or lay the selection at any of the available odds listed there, simply send your bitcoins to the corresponding address. If you would like to back or lay a selection at different odds, click on the selection you would like to back or lay, and send your bitcoins to the address corresponding to the odds you would like. When the transaction is detected on the bitcoin network, your bet is matched with other bets in our order book (at the best possible odds, naturally) and any remaining unmatched amount is entered into the order book. Unmatched portions of your bet can be cancelled at any time by signing a message that proves you own (one of the) originating address(es). The winnings, and any bets or portions of bets that are unmatched at market close, are returned to the address from which the bet was sent in the first place when the outcome has been unconditionally determined. ( Users of shared wallet services beware!) Some words of warning- The service is IN TESTING. That means you should keep records of all your transactions, in case anything goes wrong, and that there is a chance your bet will be voided if something unexpected happens, even if it may have previously been considered to be matched. Please don't cry if your bet is voided.
- Make sure you understand betting exchanges before you try it
- Never gamble more than you are prepared to lose
- This service is run in "onionland", that is, as a TOR hidden service (https://www.torproject.org/). To access it, you need to have TOR installed, or use the Tor2web proxy. TOR protects your privacy, and it protects my privacy.
- You should avoid placing large bets at this time because (1) it's a bad idea to send large amounts to some anonymous person in onionland with no reputation yet, (2) the technology is still in testing.
- The site is slow. It's on TOR and hosted on a fairly slow connection. Please be patient - but even though the site is slow, the bets are normally received withing seconds of being sent.
Since I am very short of BTC, I am also looking for sponsors - if you would like to sponsor the service, send me a PM with your offer (looking to buy my signature, some honorable mention, etc.?). Any donations would also be appreciated, and donations and sponsorships would go towards covering hosting costs (1FUwAQVuy3HiDFNbGAsmQ7gfky8tHfm2CK). Betting exchanges are much more fun than traditional bookmakers, and have plenty of advantages - although going through them here would be beyond the scope of this post. I think this concept really shows off the strengths of bitcoin, and offers a lot of value for bitcoin users. In the future I want the service to use multisig transactions - that would make this service truly great. I would like to offer my gratitude to whoever is willing to give it a try and offer their opinion. As said, the service is under development, so please make an effort to keep the feedback constructive. Good luck! bitfair tldr Help testing a betfair clone for bitcoin.
|
|
|
|
...We just shipped orders from the first of August, so we are getting caught up there....
This is the most interesting part of Josh's replay. So we should expect in the next 10 days or so, people to start receiving them, posting results, pictures etc. So why don't you finally post 1 picture of a Jalapeno or another ASIC?
If you are already shipping them it shouldn't be a problem!I understood it as he was talking about orders for their other products which are already out (FPGA), and not the ASICs. I would expect everyone to make much more noise if they were shipping ASICs earlier than expected (Oct/Nov). BFL would at least make a song and a dance about it, full of "I-told-you-so"s. |
|
|
|
If you own 10% of shares, and you purchase company equipment, you will receive a 10% discount of the profits of the sale anyway from your ownership. No other discount is needed.
In fact, if you sell at a discount especially at the beginning, you will not be maximizing revenue for the company. This sort of policy will make much more sense when demand slackens and the marginal board cannot be sold immediately.
+1 |
|
|
|
|
I believe discounts on purchasing mining gear for investors on the ASICs would be hugely unfair to those shareholders who are not interested in personally buying ASIC equipment. It would be like offering extra benefits for just a single group of investors at the expense of the rest.
However, if a shareholder purchases mining gear from the company, he will automatically get an indirect discount in the form of the dividends payed on the shares at a later date - part of which is profit from his own purchases. This will not favor any particular group of investors at the expense of another, and IMHO is a better approach.
And it also avoids all the complications of proving ownership, discounts proportional to the number of shares, etc., that have been distracting this thread for the last week or so...
|
|
|
|
|
Gentlemen,
I think I've run into a serious bug in mktx (and let me apologize in advance if this is the wrong place to post - newbie warning!):
Simply put: Sometimes the coins are sent to the address 1111111111111111111114oLvT2 rather than to the specified receiving address. It happens only with certain addresses, my theory is that it happens when the second character in the address is greater than C - when the second character in the address is C or lower, it appears to work fine.
The example in the first post of this thread works fine. However, to recreate the problem try the same command, only change the second receving address, for example:
mktx create -p priv@c524c555aad1932c24c26ec20439a9caefc49f7c0df6d6bccced890ef980b45c:0 -k priv@keys/privkey -r 12oabCifvHuxzXtYVGhkxVfWZDvKcU743s:2000000 -r 1Def9ia5QENGf8CYVVnhRTNvpop67gs6Jp:58000000
Deserializing the output from that command you can see it has set the second output script to OP_DUP OP_HASH160 0000000000000000000000000000000000000000 OP_EQUALVERIFY OP_CHECKSIG.
BTW, I am using the subvertx ubuntu package on 12.04. I haven't set up my environment to be able to recompile the utilities and such, but I guess I'll have to dive into the source myself unless I hear back...
In either case, thanks for a great bunch of tools!
|
|
|
|
(...) We are also working very hard on getting the ASICs out the door on time. We are really beefing up our production capacity and moving everything we can in house. We've purchased a pick and place machine, an oven, stenciler and other equipment to manufacture all the boards in house. This means we can produce as many boards as we need without being at the mercy of board manufacturers and their timing/runs. (...)
Seems to me like the focus of BFL at this moment is on increasing production scale, rather than getting the product out the door as early as possible. Makes me think some of the other operations might already be mining with their first crude mad-dash batch of ASICs by the time BFL delivers... Interesting race! |
|
|
|
|
Hi everyone,
I'm bitfair, and I've been working on an interesting (but at the moment top secret) bitcoin project - I will be asking for testers shortly after I am released from newbie jail.
Still missing a few pieces of the puzzle, though, but the project is almost ready for testing...
Stay tuned!
bitfair
|
|
|
|
Welcome back Atlas. Did Bane Capital get old already?
I've come across this a few times now, and my curiosity is building, so I need to ask: who the hell is Atlas, and why is everybody suspecting everybody else of being Atlas? Anyone want to bring a newbie up to speed? |
|
|
|
|
Gonna get 100 cups of coffee. Or maybe an art.
154moTUNZLRCpyqqC9NeZs2dt2KJEawHoW
|
|
|
|
|
Show Posts
