jdlrexy
Newbie
Offline
Activity: 14
Merit: 0
|
|
February 10, 2014, 06:31:18 AM |
|
Cool yup the info is correct! Thanks
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 06:58:02 AM |
|
Wolong announcing DEV pump above 0.0001 Is this trustable ?
Where did he announce this? Do you have a link / source? As more and more people discover DVC, and as the number of Devcoins in the shares for developers decrease - over the long term the value of DVC / BTC will increase considerably, as individuals will have less to dump on the market at any one time. DVC should take a quantum leap in value sometime soon - whether from a pump or from ever increasing interest in DVC, or both Yea i think the 100k+ dvc share days are comin to a close.
|
|
|
|
Hunterbunter
|
|
February 10, 2014, 07:25:22 AM |
|
Wolong announcing DEV pump above 0.0001 Is this trustable ?
Where did he announce this? Do you have a link / source? As more and more people discover DVC, and as the number of Devcoins in the shares for developers decrease - over the long term the value of DVC / BTC will increase considerably, as individuals will have less to dump on the market at any one time. DVC should take a quantum leap in value sometime soon - whether from a pump or from ever increasing interest in DVC, or both Yea i think the 100k+ dvc share days are comin to a close. That all depends on the price . Shares have increased in the past after a couple months of $10/share.
|
|
|
|
psybits
Legendary
Offline
Activity: 1386
Merit: 1000
|
|
February 10, 2014, 08:54:26 AM |
|
Judging by the massive buy support on Cryptsy for the current price of 0.00000111 and upwards (100 BTC or so) I would say we are about to see a massive movement upwards. Value is up roughly 75-80% on yesterday and the buy support is there to keep it moving. *This is not advice to invest - just my opinion* edit: we are already up to 0.00000117 and still going up strong with phenomenal buy support. This is definitely a breakout in DVC value right now. It looks exactly like what happened to DOGE a couple of weeks ago - except the DVC sell orders are thinner so I expect DVC to go up more than DOGE did. Again this is just my opinion. I wouldn't be selling any DVC right now - the current activity is definitely something of a different scale right now signalling massive movements upwards. edit 2: The massive buy walls just disappeared - not sure what's going on
|
|
|
|
weisoq
|
|
February 10, 2014, 09:44:18 AM |
|
technical analysis can give you some basic idea if there are cyclic variations, and some idea what's " normal", but without qualitative analysis, yes, it's voodoo.... for instance, i have been sitting on 8 sell orders of 1000dvc each for about a month. while the normal trading range seemed to be dropping (the voodoo would have said to cancel my more ambitious orders, and cut my losses) i just let them sit... sure enough, DVC went up enough to execute 4 of my sell orders (with about 30% margin) and am within "spitting distance" of 3 of the other 4. you see, the qualitative part of the analysis had a press release a couple of days ago, plus a new influx of writers just before this round's deadline, plus the start of a new round... so i hung in there rather than cancelling orders that the "voodoo" would have indicated cancelling....
There's a difference between indicators reflecting price patterns and momentum (e.g. moving averages, rsi) and others constructing forward looking trades. In my experience patterns are important, as are psychology and herding which TA can reflect, but I think it's self-perpetuating. There are some markets where TA seems to work better, FX is one of them and particularly in short term charts. For example if trading interest rates then USD/JPY charts help, but I see that as price reflection with an obvious inter-relationship rather than anything else. So I said voodoo partly just to be provocative and partly because I do think it's an eternal fruitless quest to wrap mass psychology in an indicator. But I still use it as a tool because sometimes it helps, I'd just never actually trade off it mechanically. I've written articles on TA so not slating the concept only how it can be applied as more than retrospective. I'm also not a massive fan of qualitative analysis as it goes. Again it's a tool, because it doesn't really matter what I think, it's what everybody else thinks and does. I tend to look at relative value where possible, or momentum and sometimes just gut feeling. Risk management is probably the most important thing - more often than not flipping a coin and having the discipline to cut losses quickly and let gains go works, but mentally that's very hard to do.
|
|
|
|
gencoinx
|
|
February 10, 2014, 09:55:20 AM |
|
For anyone that wants to know wolong's plans for DVC follow him in his twitter https://twitter.com/GameOfDeceptionhis pumps are not 1 minute pumps, he no just pumps the price, he also helps stabilize the coin at a higher price
|
|
|
|
PureGreen
Newbie
Offline
Activity: 5
Merit: 0
|
|
February 10, 2014, 11:01:41 AM |
|
|
|
|
|
Hunterbunter
|
|
February 10, 2014, 11:20:21 AM Last edit: February 10, 2014, 11:32:28 AM by Hunterbunter |
|
sorry had to reinstall gitlab and it messed up everything. It'll be up shortly. EDIT: back up
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 11:33:07 AM |
|
anyone buy $100 btc? wow
|
|
|
|
Hunterbunter
|
|
February 10, 2014, 11:36:24 AM |
|
anyone buy $100 btc? wow
I know right...it only happened on btc-e though. Can I put a petition through to improve devtome's hosting? It's failing more often than being readable at the moment. Scotty is pooped.
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 11:54:57 AM |
|
So since we are forking now anyways makes sense to start fresh with new wallet? Merged mining should now work when everyone is on newer client? We can also fix any fee stuff now decide what we want to do and also think about the difficulty algorithm to change back to bitcoin to speed up blockchain downloads aswell as easier to develop new devcoin clients...
Hunterbunter if we have only say a new node trying to mine with the pool proxy and then you connect the proxy to the latest client will it request work properly? No crash? I assume so since both versions have same fee structure etc.
|
|
|
|
Hunterbunter
|
|
February 10, 2014, 12:23:20 PM |
|
So since we are forking now anyways makes sense to start fresh with new wallet? Merged mining should now work when everyone is on newer client? We can also fix any fee stuff now decide what we want to do and also think about the difficulty algorithm to change back to bitcoin to speed up blockchain downloads aswell as easier to develop new devcoin clients...
Hunterbunter if we have only say a new node trying to mine with the pool proxy and then you connect the proxy to the latest client will it request work properly? No crash? I assume so since both versions have same fee structure etc.
Did you figure out what the problem was? I'm not sure I understand what you mean about the new node/pool proxy. Can you clarify?
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 12:33:38 PM |
|
If there is a real fix and mtgox claim stands even though this can be true: https://bitcointalk.org/index.php?topic=456740.new#newthen we are at a hardfork. Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else. Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix.. If it crashes with new client and old client mining then it may still be the setup and not the code? If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches.
|
|
|
|
psybits
Legendary
Offline
Activity: 1386
Merit: 1000
|
|
February 10, 2014, 12:42:57 PM |
|
If there is a real fix and mtgox claim stands even though this can be true: https://bitcointalk.org/index.php?topic=456740.new#newthen we are at a hardfork. Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else. Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix.. If it crashes with new client and old client mining then it may still be the setup and not the code? If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches. Bitcoin is not hard forking. Mt Gox is full of crap. The developers have said the problem is not crippling to Bitcoin and is not even on their priority list (they are aware of it).
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 12:52:05 PM |
|
If there is a real fix and mtgox claim stands even though this can be true: https://bitcointalk.org/index.php?topic=456740.new#newthen we are at a hardfork. Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else. Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix.. If it crashes with new client and old client mining then it may still be the setup and not the code? If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches. Bitcoin is not hard forking. Mt Gox is full of crap. The developers have said the problem is not crippling to Bitcoin and is not even on their priority list (they are aware of it). if thats true lets follow original path Hunterbunter and see if we can single out the problem in the new client code.. You can run another node connected to the proxy which is connected to your server node.. I think your seeing problem right away when proxy wakes up and sees that a new miner is available? Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue.. Do you follow or should I write it up more clear? Im on my iphone and its 5am so if so Ill do it on desktop later.
|
|
|
|
nibyokwy
Newbie
Offline
Activity: 51
Merit: 0
|
|
February 10, 2014, 01:16:05 PM |
|
has the new devcoin client added any of the hard or soft forking options that the new bitcoin activates? what has it done with regards to:
* version 2 blocks. i believe devcoin currently uses version 1 coinbases. when version 2 coinbases were first used in bitcoin the client had code that would reject version 1 blocks when a majority of version 2 blocks existed in the last X blocks. this was later removed once the supermajority was met and i believe the current bitcoin code now rejects version 1 blocks.
* is p2sh activated? p2sh transactions are unsafe if the majority of miners don't run p2sh enabled clients.
* there was a fork during the 0.8 version of the client due to the change to leveldb and differing locking behavior to bdb in the older client. this caused a chainfork when the old client rejected blocks that the new client created due to size constraints. a patch was created for old clients to enable them to have better locking constraints to accept the unusual blocks from the new client. this issue will exist in devcoin if miners run old and new clients. it will be possible for new client operators to force a chain split.
i'm sure there are other differences. were fee policies changed?
Any response to this? Unthinkingbit, what are the plans with regards to forking changes in the new client? I see mention of difficulty changes and other things? Is devcoin going to change quite a bit?
|
|
|
|
unclejed613
Newbie
Offline
Activity: 49
Merit: 0
|
|
February 10, 2014, 01:17:29 PM |
|
Judging by the massive buy support on Cryptsy for the current price of 0.00000111 and upwards (100 BTC or so) I would say we are about to see a massive movement upwards. Value is up roughly 75-80% on yesterday and the buy support is there to keep it moving. *This is not advice to invest - just my opinion* edit: we are already up to 0.00000117 and still going up strong with phenomenal buy support. This is definitely a breakout in DVC value right now. It looks exactly like what happened to DOGE a couple of weeks ago - except the DVC sell orders are thinner so I expect DVC to go up more than DOGE did. Again this is just my opinion. I wouldn't be selling any DVC right now - the current activity is definitely something of a different scale right now signalling massive movements upwards. edit 2: The massive buy walls just disappeared - not sure what's going on i'm just letting the remainder of my bracketed sell orders "ride".... had 6 of them go through last night, averaging about 15% margin ... got 2 still waiting.... these are only 1000dvc each, part of a trading experiment... 15% margin in a month of running the experiment is not too bad.... better than when i traded stocks.... btw.... when the price is going up like this it's the wrong time to "invest"... the best time to invest is when the price is low....
|
|
|
|
Flam
|
|
February 10, 2014, 01:17:53 PM |
|
The problem is known since 2011.
It's just a "smart" move from Gox who sold some BTC of its client and then they will buy it back after the crash. Basic market manipulation.
|
|
|
|
Hunterbunter
|
|
February 10, 2014, 01:31:29 PM |
|
if thats true lets follow original path Hunterbunter and see if we can single out the problem in the new client code..
You can run another node connected to the proxy which is connected to your server node.. I think your seeing problem right away when proxy wakes up and sees that a new miner is available? Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue..
Do you follow or should I write it up more clear? Im on my iphone and its 5am so if so Ill do it on desktop later.
Ok this is the bit I'm not following: Another node as in another p2pool node separate to the one I've already set up? What do you mean by proxy? The problem happens like this: - I start the newest source devcoin daemon, it connects to network and syncs with the network just fine, at this point it ignores P2Pool requests. While it's still syncing, P2Pool has an error when it tries to access the devcoin daemon, which says "devcoin is still downloading blocks". When devcoin daemon is stopped, it just says "can't connect to devcoind daemon" - When devcoin daemon is synced, it listens to the P2Pool request, but spits out that error below, and begins rejecting connections and disconnecting, and eventually terminates. - The P2Pool carries on doing what it's doing, and just spits out a little error every now and then saying "can't talk to the devcoin daemon", but it can continue talking to the miners and the other daemons. It seems unaffected by whether the daemon is alive or dead. - This happens on your newest code on github, but not on the 'initial devcoin based on bitcoin 0.8.5' commit e646ca6740862d6d5914d83b7e69bf31f95c25dc. On that commit, it seems to work normally (as in there are no errors, and the daemon doesn't terminate). I haven't found any blocks yet but that's probably just because of the relatively low hash power at the moment. The devcoin daemon always complains with the same problem: ERROR: CTransaction::CheckTransaction() : txout.nValue negative ERROR: CheckBlock() : CheckTransaction failed
Does that help?
|
|
|
|
nibyokwy
Newbie
Offline
Activity: 51
Merit: 0
|
|
February 10, 2014, 01:39:40 PM |
|
Does that help?
paste more of the log. is there a section before that showing details of a block submission? could there be a problem with the transactions in the coinbase related to the devcoin payouts that come from the file it regularly downloads? that's another thing that probably needs testing. testing blocks found before and after the boundaries of new file data.
|
|
|
|
|