Sounds about right. Smart enough to scam everyone but too dumb to make a working coin.
The person who bought 4.25 BTC of COV yesterday is probably feeling a little dumb right about now. those werent real buys, just a larger holder trying to create volume That means they still had 4.25 BTC of COV. |
|
|
|
Sounds about right. Smart enough to scam everyone but too dumb to make a working coin.
The person who bought 4.25 BTC of COV yesterday is probably feeling a little dumb right about now. |
|
|
|
this is what I am getting, tried reopening wallet but made no difference
Yes, the wallet says "out of sync" if it has been a while since the last block. It doesn't mean you are "out of sync". |
|
|
|
wallet out of sync again  It's not "out of sync". The blocks are moving slow. The wallet looks "out of sync" when it's been a while since the last block. Right now the network is a little fragmented, but it looks like trex is slowly finding the longest chain. We'll see if trex can catch up tomorrow some time. This is all caused by the fact that some users haven't updated. There should be a way to get the latest client to ban those that haven't updated. That would fix the network. |
|
|
|
Hello guys just checking in. We are still transitioning to the new management and there will be constant monitoring once that is complete as promised. Thanks.
Get back to me on transferring ownership of coins to my key, and I'm certain qawzsx and others will stop reporting you to authorities once I buy their BRO from them. |
|
|
|
The tactic of scams and delaying. Delays that make sure u won't report to the authorities because of that tiny hope that your investment is still in safe hands. This is the second time I've encountered this. Surprisingly the first one was also from a poker-based industry.
Too late, I already reported to the authorities alongside 12 fellows. I'm all for reporting scams, but you need to go back and read whatever it was you agreed to when you bought the coins. I'm pretty sure they had language that protected them in case it took a while to release a coin. You could make yourself liable if you file a criminal complaint based on the fact that you didn't understand your contracts. I'm not a lawyer (as far as you know), so make sure you consult one before you open yourself to liability. This is precisely the reason I suggested that breakout should restore the legal mumbo-jumbo on their ICO page. |
|
|
|
Hi I withdrew COV from my wallet to my Bittrex wallet over 8 hours ago.. Is now showing as complete in wallet but no sign in Trex?  Have checked rec address and all good? Any ideas? Trex is on a fork. The chain is frozen for them. It's likely they never updated. |
|
|
|
Some talented community members have contacted me to help aid with correcting issues and progressively continue. Will continue to update.
Um ya... A little more specific. Not to absolutely rip you a new one, but first you push the wrong commit to Github, then the website has problems, then the wallets don't work right, now community members have to supposedly help you code. And we're supposed to believe that you can deliver on the roadmap? Does all of that sound about right? Sorry, but please go back to your software engineering technology certificate program at the local community college. I'm out. Hmm. Thanks for your input; I'd like to point out I began working on the features before even beginning on the roadmap. The community was more concerned with a roadmap then the actual functionality of the features being implemented. Sure, there were issues with Github; which were corrected, but the wallet works fine, it's just everyone has their coins on the markets instead of staking. All your concerns can be easily corrected; and the features being implemented require time and testing. If venting your frustrations at my intelligence satisfies you, by all means fire away. The road map is the features you plan to implement. It's just a to-do list. |
|
|
|
I am staying positive with COV. The roadmap laid out by DEV seems doable except the Ethereum porting as Ethereum has not been released yet. Maybe Dev meant something else or can provide an explanation?. Delay is not so much as Dev is building website, proactively helping with issues on Exchange and alteast giving out minor updates. Maybe Dev has a regular job and it is not possible for him to work full time on the coin. There are of-course Dev's who are super active and working on the coin full time.
The ethereum source has been available for 9 months. They haven't released a main net yet. Users have been building from source since day 1. I've looked at the staking and since the dev reverted the changes, this coin has staked fine. It is only slow because everyone has left their coins on the exchange. The first item on the roadmap is easy. Numerous coins have cloned in stealth addresses. Some of the other features are difficult, but not impossible. |
|
|
|
My mining cost for this coin was only .00018000 so it would not surprise me if dev has already dumped and moved on. He could have had an easy 5-10x exit already.
If he puts in a couple of releases he could have a 200-300x exit. The most he could have made was 1 BTC. Why not 100? |
|
|
|
It looks like the dev is creating a coin based on the ability to port code.
Really...IOT functions when you are likely waiting on ethereum or whomever will supply an open source? Are we just waiting for other devs to do the work for this coin?
It's cool...perhaps it is a credit to the alt coin market that the low supply didn't moon for you...
Sold...and at a loss. I'm cool with that.
At least your back-posts show you walk the talk. You support a pretty clear set of innovative coins. But every coin starts as a port. Even VNL is a fairly transparent port from PPC to a better-written code base (with some definite improvements to the functionality). |
|
|
|
Everyone will be immensely satisfied with the new leadership and their aggressiveness in bringing the project up to speed and also with their extensive gaming experience. You should see a dedicated staff working with the community to answer all their questions on a daily basis. There is a lot to be confident about, especially those who have had access to the software and business plan. Thanks.
What happened to www.breakoutcoin.com? Why is it down for the past few weeks? Where are you guys located? SF Bay area or Las Vegas? Do you have a physical office address? Breakoutcoin.com will be active once again prior to the second ICO. Our USA address is registered in Henderson, NV. A full fledged physical office will be available once financing is available. The expense of running a large office while we are not fully financed is currently avoided in order to prevent large unnecessary costs. You need to bring back up the legal mumbo-jumbo on that page at the bare minimum. If for nothing else than to be quoted by trolls. |
|
|
|
|
@BreakoutGaming: I want to buy coins from some people here. I've PM'd you about transferring ownership of their tokens and Bergstake to my key. I think this will make everyone happy. Please get back to me and at least say whether a transfer is possible. PM will work.
|
|
|
|
Bittrex wallet says 'blocked'.
Trex needs to update to the latest commit and things should get moving again. |
|
|
|
I can see the new blocks generated, but mine is stuck at 1944, trying to reach 1955. How long should this take?
This is because the dev changed the target spacing. The chain is going have big problems until this is straightened out. There is no way that a coin with an 8 hour maturity (original) should have problems moving the chain when it is already a week old. It's been 161 minutes since the last block. I'm not trying to fud, only help. The dev looks legit here, but he butchered block validation on the last commit. It's not a hard fix. Just undo two lines from the last commit. If any one thinks I am fudding this coin, then do this if you have the latest wallet. Look for the exact string "-> 100" in your debug.log files. That string will be found close to the word "misbehaving" and you may see something about "not enough proof of work". All together, that means your client is banning peers and rejecting blocks that it shouldn't be. New clients will never be able to sync a fresh chain because of this problem. That's going to kill adoption and will stop the rise of this coin in it's tracks. I'm psyched about the road map, but the target spacing needs to be fixed. |
|
|
|
got cheap from dumper .. website like goods  If the dev doesn't fix the weight calculation soon, it's going to get a lot cheaper. |
|
|
|
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving. mine is staying sync'd 2 stakes and a couple more deposits since I updated  The new and old clients are probably going to fork. You'll be on the less permissive chain that will probably be orphaned if the dev fixes this the quick, dirty, and easy way. |
|
|
|
just woke up and i'm not syncing either switched back to the last version so i could at least stake and keep the chain moving. Don't panic. This is not a hard fix. The timings just need to be reverted to what they were before the commit. The blocks that have been minted with the new timings will be acceptable to those with old timings, so there probably won't be a bad fork from this. But the dev should get to it sooner rather than later. My guess is that the consensus chain will end up being from the clients previous to the commit, like you have done. It's a good idea and I'm going to do that too. |
|
|
|
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy  Does anyone who is fully synced have a good set of nodes? I can't sync past block 2. did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes? I used the newest wallet as of a few minutes ago and started with a clean app data dir. This is my debug.log. It looks like one of the seed nodes is serving a bad block from early on. Flash mines (I have nothing against those) bubble like this in the earliest blocks, but I've never seen it effect the sync: receive version message: version 60014, blocks=1900, us=174.56.90.17:37768, them=45.55.179.113:22454, peer=45.55.179.113:22454
received block 00000000bce418502eb6
SetBestChain: new best=00000000bce418502eb6 height=1 trust=33554944 blocktrust=16777472 date=04/19/15 03:40:48
ProcessBlock: ACCEPTED
received block 0000000077f387e86aca
SetBestChain: new best=0000000077f387e86aca height=2 trust=50332416 blocktrust=16777472 date=04/19/15 03:40:49
ProcessBlock: ACCEPTED
received block 000000002f8def824329
ERROR: AcceptBlock() : incorrect proof-of-work
And here's the problem with the latest commits: -static const int64_t nTargetTimespan = 60 * 30; // 30m
-unsigned int nTargetSpacing = 1 * 90; // Coven - 1.5 minute blocks
+static const int64_t nTargetTimespan = 60 * 5; // 30m
+unsigned int nTargetSpacing = 1 * 60; // Coven - 1.5 minute blocks Changing the target spacing screws up the calculation of the work required. Anyone who already has a chain fully synced won't see this. People like me who want to re-sync the chain are going to hang. This needs to be fixed. |
|
|
|
at this point it's so cheap I wont risk leaving a buy up and not getting any when I could just buy Does anyone who is fully synced have a good set of nodes? I can't sync past block 2. did you download the new wallet today? mines been working great, what would I have to type into the debug console to get you a node/nodes? I used the newest wallet as of a few minutes ago and started with a clean app data dir. This is my debug.log. It looks like one of the seed nodes is serving a bad block from early on. Flash mines (I have nothing against those) bubble like this in the earliest blocks, but I've never seen it effect the sync: receive version message: version 60014, blocks=1900, us=174.56.90.17:37768, them=45.55.179.113:22454, peer=45.55.179.113:22454
received block 00000000bce418502eb6
SetBestChain: new best=00000000bce418502eb6 height=1 trust=33554944 blocktrust=16777472 date=04/19/15 03:40:48
ProcessBlock: ACCEPTED
received block 0000000077f387e86aca
SetBestChain: new best=0000000077f387e86aca height=2 trust=50332416 blocktrust=16777472 date=04/19/15 03:40:49
ProcessBlock: ACCEPTED
received block 000000002f8def824329
ERROR: AcceptBlock() : incorrect proof-of-work
|
|
|
|
|
Show Posts
