Gox and Stamp are trading much closer together than normal the last few hours.
|
|
|
Today reminded me how vulnerable bitcoin really is at times. It was going up so strong you could have been fooled into thinking $500 was gone forever. Major eye opener. I'm glad I was here to experience it.
Watch the Bitcoin Daytrading Tutorial again until you achieve enlightenment.
|
|
|
The transaction service works best if you leave enough funds in your wallet to cover your largest ad and just fund sales automatically.
I have WAY too many no-shows for that. That would be a huge hassle. In addition, I don't trust localbitcoins not to get hacked or steal my funds. There have been far too many instances of web hosted bitcoin accounts losing/stealing funds. There is no way I'm going to just leave $15000 worth of bitcoins hanging around in localbitcoins' wallet. The process worked fine before. The only funds that had to be sent to localbitcoins was AFTER someone indicated that they wanted to use the transaction service, and then the funds where only there for a half hour or so before I didn't have to worry about them anymore. What's the benefit of this new system? It only seems to make things significantly less secure, less anonymous, and less convenient. I agree that it's additional risk. It can be worth it in certain circumstances. The benefit is there for the buyer. When transactions get funded automatically that's one way they know the seller is serious. No-shows happen on their end too, I've heard horror stories about that from people who've bought from me. Also if you do online sales of any type it's frequently possible for the process to go from "order created" to "bitcoins released" in less time than it would take to get a single confirmation, much less three. I take the risk of loss by leaving funds in my LocalBitcoins account because it helps get me good feedback due to quick turnarounds, and I've already gained more from that than I would lose if they disappear with my funds tomorrow.
|
|
|
Not happy at all about the new system of funding the "transaction service". Previously the contact would give a unique wallet address specific only to that contact. You could send the exact amount of bitcoins needed from an external wallet to the address specified by localbitcoins. They would collect their 1% fee. Everyone would be happy. Now, every contact uses my default localbitcoins "wallet address" instead of a unique address. This means I have to re-use addresses ( a practice that I am against ). The contact page lies and says: To fund the transaction, send at least #.###### BTC to your LocalBitcoins wallet address.
When I did so, localbitcoins extracted a 0.000033 BTC fee from the amount I received in the wallet??? As such, there wasn't enough in the wallet to fund the transaction. I had to send a second transaction of 0.000033 BTC (and pay another 0.0001 BTC transaction fee) to get enough in the account to fund the transaction. So now localbitcoins has taken not only the agreed 1% for the transaction but an additional 0.000033 BTC from me, and I can only assume they'll take 0.000033 BTC from the receiver as well? I'm not so upset about the cost. Localbitcoins can charge whatever fees they want, and if they get too expensive a competitor will come along and undercut them driving them out of business. That's capitalism. I'm upset that the contact page told me to send a particular amount of bitcoins, but when I sent that amount it wasn't enough. Then when I met with the buyer, the transaction wasn't funded and I couldn't release it. It inconvenienced me, and the buyer. Neither of us had time to wait for 3 more confirmations on another transaction, so we had to reschedule for another day. If this mess isn't cleaned up, I'll refuse to use the "transaction service" any longer. localbitcoins will no longer get the 1% from me, as I'll just send directly to buyers' addresses. The transaction service works best if you leave enough funds in your wallet to cover your largest ad and just fund sales automatically. You can also request a new deposit address each time through the Wallet page so that you don't reuse addresses.
|
|
|
[04:48:45] <@MagicalTux> very large sell order matching too many buy orders, causing the security system to stop the trade and rollback anything that was caused by it
|
|
|
This happens every time there's a sudden increase in demand.
Their capacity will continue grow over time, and hopefully CampBX will be able to pick up some of the slack.
|
|
|
I guess there's not too many NPR listeners here. NPR used to be tolerable to listen to, but starting with the inauguration of Obama they went insane - the Fox News of the Left.
|
|
|
2013-11-17 21:38 (INFO) -- armoryengine.py:12398 - Reading blockchain, pct complete: 99.6 2013-11-17 21:39 (INFO) -- armoryengine.py:12398 - Reading blockchain, pct complete: 0.0 2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online" 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 2qx2YAzB 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: hfGoBPCT 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: v7K4ZC15 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 2mKi33bH9 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: GeZiZcDD 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: umjPW8pw 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1914 - Syncing wallet: 21ZeYZai3 2013-11-17 21:39 (INFO) -- ArmoryQt.py:1926 - Current block number: 270232 2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online" 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2013-11-17 21:39 (INFO) -- ArmoryQt.py:4470 - Dashboard switched to fully-online mode 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull1 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3786 - Switching Armory functional mode to "Online" 2013-11-17 21:39 (INFO) -- ArmoryQt.py:3844 - Switching Armory state text to Mgmt:User, State:OnlineFull2 2013-11-17 21:50 (INFO) -- ArmoryQt.py:4786 - New Block! : 270233 2013-11-17 21:50 (INFO) -- ArmoryQt.py:4810 - Current block number: 270233 2013-11-17 22:05 (INFO) -- armoryengine.py:10553 - Received new block. 00000000000000055f457b8f2c189e90a045f153d42c6afb940cd7b8bc8105ad 2013-11-17 22:05 (INFO) -- ArmoryQt.py:4786 - New Block! : 270234 2013-11-17 22:05 (INFO) -- ArmoryQt.py:4810 - Current block number: 270234 2013-11-17 22:41 (INFO) -- armoryengine.py:10553 - Received new block. 0000000000000002059e7f0c251de4ca86e73d8d8dbb8f3cf9d071114d4cc0a5 2013-11-17 22:41 (INFO) -- ArmoryQt.py:4786 - New Block! : 270235 2013-11-17 22:41 (INFO) -- ArmoryQt.py:4810 - Current block number: 270235 2013-11-17 22:47 (INFO) -- armoryengine.py:10553 - Received new block. 000000000000000656e968d866a3a3b6fb4edbecfc1f49e2e8b36becf82f04dc 2013-11-17 22:47 (INFO) -- ArmoryQt.py:4786 - New Block! : 270236 2013-11-17 22:47 (INFO) -- ArmoryQt.py:4810 - Current block number: 270236 2013-11-17 22:52 (INFO) -- armoryengine.py:10553 - Received new block. 000000000000000649500b42bfd07ffe586a0074f5b2fcfe9445b2053b82b4c8 2013-11-17 22:52 (INFO) -- ArmoryQt.py:4786 - New Block! : 270237 2013-11-17 22:52 (INFO) -- ArmoryQt.py:4810 - Current block number: 270237 2013-11-17 22:53 (INFO) -- armoryengine.py:10553 - Received new block. 0000000000000000060cbaf02710e7c891e06ec9eebada6e572324a685e1cbd6 2013-11-17 22:53 (INFO) -- ArmoryQt.py:4786 - New Block! : 270238 2013-11-17 22:53 (INFO) -- ArmoryQt.py:4810 - Current block number: 270238 2013-11-17 22:59 (INFO) -- ArmoryQt.py:4786 - New Block! : 270239 2013-11-17 22:59 (INFO) -- ArmoryQt.py:4810 - Current block number: 270239 2013-11-17 22:59 (INFO) -- armoryengine.py:10553 - Received new block. 0000000000000000249f70ff362231538dd50ba936ab5f60c01196e75404505a 2013-11-17 23:00 (ERROR) -- armoryengine.py:12265 - BDM was not ready for your request! Waited 20 sec. 2013-11-17 23:00 (ERROR) -- armoryengine.py:12266 - getattr name: hasTxWithHash 2013-11-17 23:00 (ERROR) -- armoryengine.py:12267 - BDM currently doing: ZeroConfTxToInsert (57537226) 2013-11-17 23:00 (ERROR) -- armoryengine.py:12268 - Waiting for completion: ID= 55370105 2013-11-17 23:00 (ERROR) -- armoryengine.py:12269 - Direct traceback 2013-11-17 23:00 (ERROR) -- armoryengine.py:12272 - Traceback: Traceback (most recent call last): File "/usr/lib64/armory/armoryengine.py", line 12262, in passthruFunc out = self.outputQueue.get(True, self.mtWaitSec) File "/usr/lib64/python2.7/Queue.py", line 176, in get raise Empty Empty 2013-11-17 23:00 (ERROR) -- armoryengine.py:13208 - ErrorOut var over-represented number of errors!
|
|
|
Bump
This is the first time I can remember crossing off two milestones in the same day.
|
|
|
Sunde: You can't beat politics with technology
Bitcoin: Challenge accepted.
|
|
|
I'm worried about the increase in market cap. Before we were talking about adding hundreds of millions a day during the bubbles; now we're adding BILLIONS in implied value per day to the Bitcoin ecosystem. If a lot of people panic sell on the pop, there's no way there's that kind of money to back up the price. The correction may be brutal.
Chinese exchanges actually have decent interfaces with their banking system. They can move fiat over there almost as easily as BTC.
|
|
|
Is there no one left to predict an impending crash to single digits any more?
|
|
|
Bitcoin Foundation policy director of some kind, and Bitcointalk's newest sex object.
You're only succeeding in drawing more attention to the comment in question. Just ignore the poster and move on.
|
|
|
Mother of God... With what price I'm going to wake up with?
$1000 or $100. Or something in between.
|
|
|
Why does this thread keep getting bumped. Its annoying always seeing it at the top. lol ... Have random conversations in other threads lol ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) It's got to catch up with the other epic trading thread.
|
|
|
|