SHORT TERM ANALYSIS: BEARS WILL CONTINUE TO POST TERRIBLE THREADS IN HOPES THAT SOME HOW THERE POSTS WILL ACTUALLY IMPACT THE MARKET.
News at 11.
the market always tops during the peak of bullish sentiment. hope you like holding bags. As you are still bearish, we are far from the peak of bullish sentiment.  |
|
|
|
In case you do not aware, checkpoints ( https://github.com/bitcoin/bitcoin/blob/master/src/checkpoints.cpp) are currently applied to Satoshi client. This means no matter how much hashing power one has, he will create a hard fork by trying to replace blocks before the last checkpoint. Therefore, bitcoin is never a pure PoW network. Currently, checkpoints are implemented for about every thousands of blocks, and it is solely determined by the devs. So theoretically, the devs could hardcode every single new blocks as checkpoints, making themselves as the central bitcoin clearinghouse, working like SolidCoin. My proposal is just trying to decentralise the process of checkpointing. If 6 blocks is considered too short, we may make it every 100 blocks, but definitely not thousands of blocks. 100 blocks checkpoint is not too bad, at least I am sure that the 10 million USD worth of BTC that I received in the morning will become completely non-chargebackable in the evening. |
|
|
|
Please, no.
Please, give reasons. |
|
|
|
Address: 1FAhYh9ej5kbF2hXyp22tCzgWjb9cD8jvB
Message: I own this address
Signature: G2ATgBLUY2kSbdPhcaTbhGuOYYuzUxzZwcG500W0lOmQjUAYXvIj0oPxmGG05DRgE83/bp6cauwmyzOGFkAmuto=
Who is "I"? This proves nothing. Even something like "I am hazek of bitcoin.org" proves nothing because everyone can sign this message with their own address. You need to sign a message like "hazek of bitcoin.org owns the address 1FAhYh9ej5kbF2hXyp22tCzgWjb9cD8jvB" with an independent, widely recognized public key of your own. |
|
|
|
Are you just cherry-picking? I will have different conclusion by choosing different time-scale: more bullish (or less bearish) for the longer term |
|
|
|
Although I don't like the loan-based idea of Ripple, I think its consensus model is useful in protecting bitcoin against 51% attack. Read more here: https://ripple.com/wiki/ConsensusWe can apply consensus on top of the current PoW model. When a block has got 6-confirmations, nodes (both miners and non-miners; "validators" in Ripple jargon) will sign the block with their private keys, as a vote of its validity and uniqueness. In a normal situation, all honest nodes should come to consensus, and honest miners will never accept any conflicting blocks. Therefore, any secret 51% attack (secretly mining and suddenly releasing a longer chain) will never succeed for more than 6 blocks. Even a 1-million USD worth transaction is perfectly safe with 6 confirmations, which is not really safe with pure PoW. There will be 3 classes of validators: Elites: Same as Ripple, these validators should be non-anonymous to avoid Sybil Attack. Elites could be bitcoin merchants, devs, trusted OTC traders, and active forum participants. Elites will publish their GPG/bitcoin public key hash on their websites or on the forum. Miners: Miners will include GPG public key hash (or public key hash of an empty bitcoin account) in their coinbase transactions, so they don't need to maintain a hot wallet for this purpose. Miners could be anonymous or non-anonymous. Riches: Riches are holders of big account (aka. proof of stakes). For the same safety reasons, riches will publish an alternative GPG/bicoin public key hash with a specially crafted transaction. Riches could be anonymous or non-anonymous. There will be overlapping between 3 classes of validators, especially if some were anonymous. Therefore, anonymous Miners and Riches will have lower voting power. As long as the validators are highly diversified, the risk of these people colluding to defraud is extremely minimal. If they do so, that will destroy their real-world reputations. In case of network-split, for over 6 blocks, we may need some human interventions. AFAIK, a split in this scale has never happened; and if it did, it would be a disaster on its own and the consensus model would not make it worse. Actually, the consensus model will make the system more robust against a network split, as people will find a large proportion of validators missing, and they will reject any new transaction until the network is re-merged. The current bitcoin client does not give any warning in case of suspected network split. As we have checkpoints in Satoshi client, the system is technically not pure PoW. However, checkpoints are usually thousands of blocks behind and that's not enough to protect us against 51% attack. Philosophically, checkpoints are hard-coding the community consensus to the code. Why don't we make this process more decentralised and automatic? I know this proposal is not new, but I think Ripple is the first one trying to implement this. Let's see how it works then we can implement it to bitcoin. As the bitcoin economy keeps growing, I believe this will give more confidence to all users and investors. EDIT: I don't think Consensus nor PoW is safe enough on their own for millions USD transactions. However they are much stronger when combined and the whole thing is still P2P decentralised. |
|
|
|
|
Update:
1. 2011-06-09 W. Avg: 29.58
2. 2011-06-08 W. Avg: 27.25
3. 2013-02-13 W. Avg: 25.48
4. 2013-02-12 W. Avg: 25.09
5. 2011-06-10 W. Avg: 24.67
6. 2013-02-11 W. Avg: 24.13
7. 2013-02-10 W. Avg: 23.42
8. 2013-02-09 W. Avg: 23.24
9. 2013-02-08 W. Avg: 22.42
10. 2013-02-07 W. Avg: 21.61
11. 2013-02-06 W. Avg: 21.09
12. 2013-02-01 W. Avg: 20.73
13. 2013-01-31 W. Avg: 20.58
14. 2013-02-05 W. Avg: 20.57
15. 2013-02-04 W. Avg: 20.42
16. 2013-02-03 W. Avg: 20.26
17. 2011-06-13 W. Avg: 20.11
18. 2011-06-07 W. Avg: 19.90
19. 2011-06-15 W. Avg: 19.68
20. 2013-01-30 W. Avg: 19.48
|
|
|
|
|
Since 99.99% of the world population have never heard bitcoin, it's definietly far away from everyone thinks that he is gonna be rich
|
|
|
|
Scared yet?  |
|
|
|
OK, some FACTS from http://litecoin.orgLitecoin manages to maintain the unique traits and attributes of Bitcoin, while adding to the mixture CPU-specific mining and a 2.5 minute block rate. This means that Litecoin doesn't have to compete for the used up computational cycles of your graphics card if you're already mining Bitcoins, but can work independently on your processor. Litecoin uses Scrypt as a proof-of-work scheme. Scrypt uses the low-latency cache memory of modern processors to provide greater hash-speeds on CPUs in comparison to GPUs. We would like to extend our thanks to ArtForz for the implementation. in short coin for coin you will get more litecoin per x number of computational cycles then you would bitcoin. it does not state that litecoin is just for CPU mining.this is again an attempt at using information wrongly to say its impossible to mine litecoins using a GPU for profit. Oh well, "CPU-specific mining" means "litecoin is not just for CPU mining"? |
|
|
|
ok a few history and FACTUAL lessons for you all.
LITECOIN is not resistant to any form of computational devices mining it. As long as they can be programmed to do so.
such as CPU,GPU, android phones. and many other devices.
the problem is that the devices such as the bitcoin ASICS have been hard wired to only be able to mine SHA256
litecoin was invented in 2011. asics were invented in 2012. so blame the later for not catering for the former.
the whole "GPU resistant" statement on the wiki is due to a users with a god complex called Luke-JR, whom has taken it upon himself to try to stop anyone's choice/freedoms of moving away from bitcoin to any other alt currencies people with to try, use.
because he does not have the power to physically stop you. he can only control the information available on places that he moderates.
it is Luke-JR that makes the comment that litecoin wont succeed and is not worthy of peoples time.
Luke JR knows deep down that with the lingering stench of illegal activities that media highlight about bitcoin. it will not grow at the speeds he desires. he knows a sound coin with no negative publicity and nothing structurally wrong with it would succeed better going mainstream. i am not saying guaranteed to exceed in value, i am just saying user adoption would be less of a hurdle to climb.
So he wants to prevent any losses in the bitcoin userbase. He cannot shut down silk road, he cannot find a way to program it so that silk road transactions get ignored. so he is powerless to rid bitcoin of negative press. and from what i have seen. he has not been involved in any main stream expansion attempts outside of the forums.
this is what i call an armchair activist. (big mouth on the sofa, no voice on the streets)
but you have the freedom to mine litecoin if you want no matter what people say. so give it a try, and if you don't like it, you can always go back to how you done things before.
with that said feel free to try all the coins. and if you do want to help main stream a crypto currency i am not saying to not help bitcoin expand into the real world of bricks and mortar businesses. all i am saying is litecoin is a lot less of a headache swaying people away from the media propaganda.
which is at the crux of the whole issue.
OK, some FACTS from http://litecoin.orgLitecoin manages to maintain the unique traits and attributes of Bitcoin, while adding to the mixture CPU-specific mining and a 2.5 minute block rate. This means that Litecoin doesn't have to compete for the used up computational cycles of your graphics card if you're already mining Bitcoins, but can work independently on your processor. Litecoin uses Scrypt as a proof-of-work scheme. Scrypt uses the low-latency cache memory of modern processors to provide greater hash-speeds on CPUs in comparison to GPUs. We would like to extend our thanks to ArtForz for the implementation. |
|
|
|
I have just upgraded to Bitcoin 0.8 RC1 and I find that my Armory 0.87 beta would sometimes stop updating. The block count in the right bottom corner shows "Connected (220817 blocks)" but Bitcoin-qt is already showing 220903. Armory stills shows new tx, but the number of confirmation remains 0 despite it has been confirmed. Everything was back to normal for a while after Armory is restarted, but it would somehow stop updating again. 2013-02-12 20:34 (INFO) -- ArmoryQt.py:3205 - Dashboard switched to fully-online mode
2013-02-12 20:34 (INFO) -- ArmoryQt.py:3205 - Dashboard switched to fully-online mode
2013-02-12 20:37 (INFO) -- ArmoryQt.py:3410 - New Block! : 220809
2013-02-12 20:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 20:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000074a783b4427337c720ddc63727dea306f7fc5bb90c17d470bc
2013-02-12 21:18 (INFO) -- ArmoryQt.py:3410 - New Block! : 220810
2013-02-12 21:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003688e6effc415f0551dc8452da8ba8dec22d6035f1559618649
2013-02-12 21:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004829f8ec992570ad67a07c21d0ac188895446c6908a3ec77ce3
2013-02-12 21:25 (INFO) -- ArmoryQt.py:3410 - New Block! : 220811
2013-02-12 21:28 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:28 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000043751773e28d37e5b1628ef08bfde6bdbe13131cf4b1129a8b7
2013-02-12 21:28 (INFO) -- ArmoryQt.py:3410 - New Block! : 220812
2013-02-12 21:35 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:35 (INFO) -- ArmoryQt.py:3410 - New Block! : 220813
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004a2e96fc0e15cba01f0570c1aece435c11e3ec11d24a8ee9804
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 21:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002b4f3f0538deddecf04d7dad72402331977c76576283a8d1f4d
2013-02-12 21:36 (INFO) -- ArmoryQt.py:3410 - New Block! : 220814
2013-02-12 22:07 (INFO) -- ArmoryQt.py:3410 - New Block! : 220815
2013-02-12 22:07 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:07 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002bbfbe339f3dd48316c20b21be7ce1bdb5b5f131f0db296036a
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004667e989a5ad255d6baa7f59db4db3906b02dc128634bf95a18
2013-02-12 22:27 (INFO) -- ArmoryQt.py:3410 - New Block! : 220817
2013-02-12 22:27 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003200a65a5146f8e894704976bd21d1cf209e2dc8c7f3d0d40ea
2013-02-12 22:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015142450a030a8641e9a70290027eaaa8f8d52a6bd9d2afcac4
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000038600b771887da5b3830947bb3ea129f8fc571cec43990410d3
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 22:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001a5964a6deca4a1b842889652e4c301f10a311de51d7a3d2e7
2013-02-12 23:04 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:04 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000c9de2b7ce3bd605cfed4dbbbcd3b3498c9e0946fe5dd0f2296
2013-02-12 23:08 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:08 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000412718fa5a1984a5a675746cf26199bf6cca60a501eaf842382
2013-02-12 23:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003e6afbd5a7215acedbc023c1749a2718145dae1a6c35feb4d71
2013-02-12 23:33 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:33 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000426c1c65d6b80deac16358d74c342724ef1ecfa9a1e0dc00e0e
2013-02-12 23:39 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:39 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000481f700e78826444fc7cc621dd31026b0e48fa2237289284414
2013-02-12 23:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000022ac4a92fe52d54369a983bd6a317761af0c81dbee919798271
2013-02-12 23:54 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-12 23:54 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000219272cdf8221744445a5dad573b31407b9a880d0118f714ba9
2013-02-13 00:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003cc8969bd449abd4e4e2dcf519a0110982748f00ca2db5753a4
2013-02-13 00:33 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:33 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002ce1618afdb84ebfd380049e1afa889ffe25f1b454e07a78039
2013-02-13 00:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001954c5d59d02efe184b1519afed0b00b12586fb5aff9e7c8310
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004f958de0219d509e8ba156d9893f4903f9fa6c23edfed5ef565
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000eb3c170ca260e1dffa2b1a91772dcae18a4df3446f377bd1b4
2013-02-13 00:47 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000040681ba05ed54daa23667b2673d3ef6acbabd2dc36c95d66ab7
2013-02-13 00:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 00:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001f94f1644dfd3d056e5098d325b4b2bf4cb3c2690d7006c1a87
2013-02-13 01:03 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:03 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000379de774e67d9bdb305af68a956f891c548f0da19c538a79071
2013-02-13 01:10 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:10 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001cfaf40b52daf78d4cf9c0e93e427c242b90386ea6aae9d079b
2013-02-13 01:23 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:23 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000437a3ec102cf9050b7a26c0d986acf74cf9b3d6eff8ad7959de
2013-02-13 01:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004af3c30dac15e153941696c078a8e5c968bfe364de9a858e7c0
2013-02-13 01:57 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 01:57 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000576ea85bd5de07bdbc81a00549f6d20f8549b04a7597f5d64a
2013-02-13 02:00 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:00 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002bc74b17eb31d45dcac53ec1ba082c0bc7113e73ec32bae952f
2013-02-13 02:09 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:09 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015bd9e602c027f1eb2367ec7a8c8d4d70baa44cb27e86c6af81
2013-02-13 02:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003ac4741d68090c24d6b7c3fd201a20f781c97759d472fec49a5
2013-02-13 02:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000029b96bec10dc57876c04c434af46751d6cc472c06cd1c92feec
2013-02-13 02:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000043808648eabbeda3022a41cb311bfb6d9af9fc1520b8061ec8
2013-02-13 02:53 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 02:53 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003b45a22c6e1959fd0e79061998e4c2ac5147fb9a99751fa5576
2013-02-13 03:00 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:01 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000c32ac05e662ee9bd4d222b549abe10178fb544d6e6f26e93c9
2013-02-13 03:21 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:21 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000334d1548d2423a37efd06ace379021b2b8385e483964fffa300
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000013255a453dde9658c72a6e0f25d305554448361f35b529b2b73
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:44 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004cbe8d606dc4ba12dbd5cb1341aebac36d7865b5114c8eee0d
2013-02-13 03:51 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:51 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000020bcc1e59ce644505748582a62f4459b94a5f882fafbfbb3ba3
2013-02-13 03:52 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 03:52 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004b3cd2392613cfc92956e0e7a0031f61bc2f7df29734f5d5ea8
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000024553030a164723359019d23ad199392f8a0a15a5e0099db2fd
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:02 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000034daa0096eeded10790f95d5818abfb25c51f1fcbe7e2bb355d
2013-02-13 04:08 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:08 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003900a5672134b4cf28e6644aa8910f4ac6949cf7f4a261cc026
2013-02-13 04:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004af9c6b6a73d0070f174565ba88b5b0c08e752684f28ee6c716
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000039ca2e3e0878ed6a01ab21dac204e542bc30a1a2f3dacbe254a
2013-02-13 04:36 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000046667582296b65fe3aa46b381ac1721529641a131a23f0b8cc5
2013-02-13 04:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001d7ff7cd8e0b0dd99d98a240a3a46600542fa8d5971a88450c
2013-02-13 04:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 04:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004142fb1be064fbecac5aa5f2425e3e8ac81c2983774119f5df7
2013-02-13 05:01 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:01 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000028e922fc468545b37d57384bad8bf0e8865608a00db449c399e
2013-02-13 05:18 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:18 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002d58bea826565a1c18bab38cef66dbb574c3bc50720af4d3644
2013-02-13 05:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000042ad6a204886aab4a988a8a93a88c11db279cc2245b76d29742
2013-02-13 05:42 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:42 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000040bd33ab8464677122f1c549a7993c67b3fb5d22365c84d961
2013-02-13 05:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003eb48fbc7e7f17f49977b7938b5430459ce98821a3f81af360c
2013-02-13 05:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000031547d290a9f4b59cdfaebc82560c0da63ccf0ef435b547fcb6
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000431d261f1612e14e5dd6f92f66fe27faabce1bd5e1a3ae53e1d
2013-02-13 05:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003371e40ad12f89d6f2f23a8b3e2df23f19ca75d4ac082e04d68
2013-02-13 06:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003df0f60971ba1a88de2fd3a89a203dbcf5862629bd0920d3a2c
2013-02-13 06:34 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:34 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002284bc9ab5c6fe33f7941a98a175f028c8643ce61fcbb4311d8
2013-02-13 06:40 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:40 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000006d7aaf3feeecda7e3f12bfabe4848ff866e391d2460a8dc35c
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000492908d9d0271cc1655799c04bbfe1145c18683f67b8627c04b
2013-02-13 06:46 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000002a5c33e8eefbfc2912dcb1109f4ce4ed19abd708d3de921907
2013-02-13 06:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 06:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000028283a043aab59527db4e040e4cf551d6ef35811726e33e0733
2013-02-13 07:09 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:09 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000036770a969c85cea0f7fe3c2779032bc90aecfb0a71dd6cbc7fa
2013-02-13 07:35 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:35 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000001dcce624bb3d76337c1f7c4e8c1ed5b18a6f82f99b3ce8da7d
2013-02-13 07:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 07:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000abb59be4be356bf9bb9b9935c220aa6993c871985925416320
2013-02-13 08:05 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:05 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000038e39a10defe06fef9f21d07556b54ae13aa57156dab628417
2013-02-13 08:17 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:17 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000005c6d7b6836836cdd5b01b0a37363befff5eb715ea063615ef1
2013-02-13 08:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000003759bee816c1839bb0d045e73c9565f121e51a66627be4291cc
2013-02-13 08:25 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:25 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000015a0d2846f580d3f02763480bddd88a3f5f28a6e67620f47809
2013-02-13 08:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004673b271204959ac69f294ee6eeb179ff1568b3b072205e140
2013-02-13 08:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000004415cfdfdec7dd9ce8bbe57cc63bbdd565256b9dc2bd952ed2
2013-02-13 08:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 08:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000002b2c2816eede3e5094bce80d28e410ebc994315862210ac00da
2013-02-13 09:06 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:06 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000022bf19f7191a0752402bf6ac5d078fdcc2c4ec19a461414bec
2013-02-13 09:24 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:24 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000321aa510c47e67cd9ec69a0c748b5fc619fe647e9bafbcd7cba
2013-02-13 09:30 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:30 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001494a50cdf8052692eb3b835ccb0e0ea74ff278da755fb418bf
2013-02-13 09:37 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:37 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000051a25052e0699c1f7295b9c7ebd4999ac99498c462d32d1f632
2013-02-13 09:48 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:48 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001dcca7d765f095078af64cb1553833335bef676fc74db85283c
2013-02-13 09:49 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:49 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001f5fd9e3877102f68641d95308b1088cd4367eb1958be6492c0
2013-02-13 09:56 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:56 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000017e1883d4266c0faf4789436b7eda06a8c77e7b9d624fa80b52
2013-02-13 09:58 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 09:58 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000004ebb76cb1d8db0ea1eb9dd48919fb8dfe78a0dfdbc8730ebf60
2013-02-13 10:03 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:03 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001faa5f06c81b98ef9d008b5853243fa8449c1b4b1f2e6c76194
2013-02-13 10:07 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:07 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000023ba949750231780415d8f78d417a3f31f4582ca0cdc94c61f1
2013-02-13 10:40 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:40 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000001cd76584294b036573375f69242add97919c617913bd11b0e13
2013-02-13 10:45 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:45 (INFO) -- armoryengine.pyc:9372 - Received new block. 00000000000000da7e927f6836ab33d59b2d178058287450aaeccb4294f6f628
2013-02-13 10:52 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:52 (INFO) -- armoryengine.pyc:9372 - Received new block. 000000000000013b888d5d830863e5ecf719cd66b6042405186bed59c434d500
2013-02-13 10:58 (INFO) -- armoryengine.pyc:9355 - New block broadcast received
2013-02-13 10:58 (INFO) -- armoryengine.pyc:9372 - Received new block. 0000000000000443f105fb58797a444555e52626eb5dbc170ae026693a4c67c3 This is the log. It seems armoryengine.pyc keeps receiving new blocks, but ArmoryQt.py is stopped at 220817 (and somehow 220816 is missing) My system is Windows Server 2008 R2 x64 |
|
|
|
The only "problem" I see is that it hasn't been updated in months. I hadn't started litecoin in a couple months and there were barely any changes when I updated my source tree... Is https://github.com/litecoin-project/litecoin still current? Are there any plans to rebase to bitcoin 0.8? Yes, I plan to do that soon. Does it have a design flaw?
It isn't as much flaw as deception. Litecoin used the same scrypt parameters as Tenebrix. Artforz had gamed almost everyone involved in the scrypt()-based coins. He had choosen the set of parameters that made GPU mining possible, but made claims that the design is GPU-resistant. Then he proceeded to mine all the scrypt()-based coins (Tenebrix/Fairbrix/etc) on his GPU farm that was significantly more efficient than the CPU miners. Exactly. Scrypt-based mining is not bad but LTC is just a scam I for one, did not see anything suspicious going on when I launched Litecoin. If I remember correctly, at the start the network hashrate was comparable to about a few hundred CPUs mining and it slowly ramped up from there. If there were any GPUs mining at that time, the network hashrate would be a lot larger than just a few hundred CPUs equivalent. It's true that I probably should not have taken just ArtForz's word on how gpu-resistant scrypt was with those chosen params. But ArtForz was a very well respected member of the bitcoin community and seemed to know a lot about what he was doing... at least a lot more than me. And he has earned enough bitcoins from the early days, that stealing a ton of scrypt-based coins just seemed beneath him. Plus his reasoning for using scrypt with those parameters were posted months before Litecoin launched, and people have looked over his reasoning and no one came out and said anything against his reasonings. So no, LTC is not a scam. Do you consider bitcoin to be a scam? Satoshi designed it so that everyone can mine bitcoins and get in on the action. But now one ASIC is about a million times faster than your CPU at mining bitcoins. Satoshi has never advertised bitcoin as GPU or ASIC resistant, but Litecoin does. Moreover, there was a substantial low hash rate period in 2009, suggesting no GPU was used for mining. |
|
|
|
Why would someone want to overpay for a pizza using bitcoin?
... it's part of the initiation ritual into bitcoin ... if you haven't over-payed for something and been 'deflated' out of a small fortune you probably don't have enough skin in the game, pizzas just happen to be popular item. Pizzas and modified PCI-e extender cables ... yes, but this gimmick won't work for most people |
|
|
|
|
Why would someone want to overpay for a pizza using bitcoin?
|
|
|
|
The real test for bitcoin's enthusiastic investors and speculators is the previous highest mark, which briefly touched $32 before plummeting down to barely more less than $2.
FTFY. It was $1.99998 |
|
|
|
|
We should lower fee for normal transactions but increase fee for spams like Satoshi Dice
|
|
|
|
Does it have a design flaw?
It isn't as much flaw as deception. Litecoin used the same scrypt parameters as Tenebrix. Artforz had gamed almost everyone involved in the scrypt()-based coins. He had choosen the set of parameters that made GPU mining possible, but made claims that the design is GPU-resistant. Then he proceeded to mine all the scrypt()-based coins (Tenebrix/Fairbrix/etc) on his GPU farm that was significantly more efficient than the CPU miners. Exactly. Scrypt-based mining is not bad but LTC is just a scam |
|
|
|
jl2012, I'm not interested in machine translation for exactly the reason youve stated. I'm looking for persons fluent in a particular language to translate a technical geek site.
If I trusted Google's machine translation then youd already see more languages available on bitaddress.
No, that's not worked like you think. There is a simple, deterministic matching scheme to convert Traditional Chinese to Simplified Chinese. Actually they are the same language, just some characters are written differently. They share the same grammar. Therefore, it is not even "translation". It's just "conversion". |
|
|
|
It seems there is a repeating pattern: 1. Resistance for 4-7 days 2. Going up for 2-4 days 3. Last resistance becoming new support Now we meet another resistance at $24. If the pattern holds, we will not reach $25 before Wednesday and we may test the $21 support before that  |
|
|
|
|
Show Posts
