Topic: [ANN] StarTrek insipred coins =) and mining links (Low Diff) Nice Bounties! - page 16. (Read 60751 times)

Oh plz dont php.

Continue with the python implementation. I am a budding python coder so not much i can do at this point.

I do php and i can tell it will be hard to lock down all of the security risks.  Do python or c++.

thnx.

p.s. i'll do an exchange update on the scificointalk.com.

ASIC - Andorian Security Iridium coin.

Sha coin, asics friendly. What do you think?

Yeah, I would like that too

I wish someone would make a SCIFI coin for SHA-256. I would mine that hard...hint hint

Yeah, I think they will list more coins after the server migration.
XPM market only has 3 coins, so I think it would be the first choice for them.

Dreamwatcher, thanks for being the Keeper of this community.

Scifi, that's sad to hear. Let's hope for the best. I recalled BitcoinJohn did say he wants to list the coins.

Hello everyone.

We are looking at the darsek issue at the moment, and currently have not found the root cause of the issue.  I will be back intouch when we have an update.

As for the exchange, it has been delayed for at least 2 more weeks and more than likely 2 more months.  I told the current developer to stop working on the project after I found that he was lying to me.  Here is what happened.

The current Dev started work on the project on 4th Sept after the 1st guy did not have the skills necessary.  He was to work on the project full time, and he stated that he had done similar projects in the past and with this in mind he suggested a 2 week timescale.  I felt this optimistic but he was confident.

After 15 days he disappeared for 3 days and was not contactable.  He reappeared and apologized, stating the reason was personal, and that he would continue with the project with immediate effect.  

on the approx 22nd Sept he stated that the main reason for the delay was bad planning.  He had planned to write the exchange from the ground up in Golang, and that he admitted this was not his usually language of choice.  He stated the problems were to do with;  the available golang bitcoin libs, being effectively buggy at best, and at worst broken.

He asked me at this point if I was happy to wait a little while longer and it will all be ported to Python,  a language that he has a vast experience with.  I agreed and at the end of September there was a working exchange.  

However there were many bugs and many of the solutions were not immediately obvious.  He decided to rewrite elements of the exchange.  At this point (approx 1st Oct)  I was given 2 days estimate for completion.  

The dev then disappeared again and resurfaced a few days later, stating he was sorry and will continue development straight away.  The reson was that a car had crashed from the street into his office.  I took this reason and allowed him to continue.

Around the 6th or 7th Oct I was told 1-3 days Maximum.  These days passed, and nothing.  on approx the 10th October we tested the wallets and all worked 100% he just needed to finalize the bugs in the exchange algorithm.  and Install the exchange at it's final destination.  I gave the deadline on Sunday 13th.  

On Sunday he was apparently implementing the exchange and uploading it.  however I could see no activity on the VPS and then he stated he needed to visit family.  No probs I thought if we are so close.  He returned that evening but said he will need to complete tomorrow.

On Monday the 14th He was on Skype, stating he could not do the work so quickly as his internet speed is 80Kbps and he did not know the reason for the slow speed.

I checked VPS traffic and there was non.  I knew he was lying and was just buying time.  That evening he was on skype saying he was applying the finishing touches while uploading.  I had to logout of Skype and boot into linux said I would be back in 30 mins.  

After 1 1/2 hours I returned to skype to see he had uploaded nothing and was not on skype, and no emails from him.  The next day he was also AWOL so I cancelled the deal with him. I was angry to say the least and I decided to cut my losses.

I feel bad, because I believe he was a very talented developer, but he has some real issues with time management and communication.  He seems to be a lazy genius,  coding what would take me 2 months in a week.  He's a procrastinator though.

He is a forum member so he is welcome to voice his side of events.  At present though I am not willing to work with someone that has this little regard for someone that is effectively his employer.   we were 6 weeks into a 2 week project and my patience was at it's limit nd he did not seem to give a shit.

As a result, I have some exchange code in Python that I do not know what to do with. But I will write the exchange from scratch in mainly PHP.  but this will delay it by a long time.

The good news is that I have asked Cryptsy to list the coins.  To which they have said they are interested in doing this, but we will need to wait for them to finish their work at the new data-center first.

I expect them to list each coin with exception of Darsek based on the current issue.  I want to say sorry to everyone involved with the coins.  

and if anyone is a python expert then PM me.  

The Klingon High Council approves adn will continue testing during these treacherous times.

The House of Dreamwatcher has Great Honor !!

Thank you.

ended! 

IN LIGHT OF THE ISSUES WITH KED, FOR 24 HOURS (UNTIL 10-17 20:35 UTC) SINCE BLOCK 81660, I WILL COVER THE INABILITY TO MINE POW COINS IN THE POOL OUT OF POCKET.

I will pay the miners  as if the pool were mining 75% of the KED blocks (around what has been normal). 3.5 KED @ 60 blocks per hour = 210 per hour * 75% = 157.50 per hour

If the Darsek development team has not fixed the issue by (10-17 20:25 UTC), I will need to consider shutting off the pool or extending the offer.

Payout will occur about a day after everything has been settled, as I will have to do the calculations by hand, so I only want to do them once  

What is the minimum PoS on KED? I've so far generated a few blocks, all 0.00 KED.

problem confirmed.

i am also getting similar results of the Diff. not matching in the cgMiner 3.0.1

i am throwing 380 Kh/s at it ....so far no blocks.

i will continue gpu mining with cgminer and also cpu mining with Qt client to see if i can produce a block.

good luck.

i'll fire up my darsek Qt and miner to see if i can get a similar result.

It is a POS:

 
It is really looking more and more like some kind of difficulty bug. Here is part of the debug log on one of the rejected blocks from the local solo mine test tonight.

block 81688 seems a bit wierd...and its not POS.

81688   10-17 06:15:29   2   51.61859   0.00390625   491

the bits section seems interesting too..similar to pos..but not pos?


malformed? or is network forking?

As a matter of fact, I just checked my personal wallet that I did the local mine test with , and I guess I have been producing many of the POS blocks that kept the chain moving.

I have shut down my wallet, so it will be interesting to see what happens to the chain.

interesting indeed....

i wonder if scificoin can shed some light?

81660   10-16 21:35:42   1   3.5   0.0273674298   267 - THIS IS THE LAST POW BLOCK ON THE NETWORK

The only reason blocks are coming regularly now is because a wallet(s) is online with enough stake to keep the chain moving.

Mining has not produced a single block since 81660.

Remember, the target time is one minute, yet we are seeing hour gaps. The size of the blocks does not effect hash rate, at least at this coins level.

interesting...

the block explorer reports current block hieght of 81690 as the latest block as of this writing..
 and:
81690   10-17 06:28:38   2   50.63136   0.00390625   492
81689   10-17 06:26:06   2   52.549   0.00390625   493
81688   10-17 06:15:29   2   51.61859   0.00390625   491
81687   10-17 06:06:59   2   54.79624   0.00390625   492

block times dont seem too big...

all i can think of is random luck or someone's pool was on the fritz hopping on and off.


also:
81690   10-17 06:28:38   2   50.63136   0.00390625    492
81689   10-17 06:26:06   2   52.549   0.00390625    493
81688   10-17 06:15:29   2   51.61859   0.00390625    491
81687   10-17 06:06:59   2   54.79624   0.00390625    492
81686   10-17 05:58:53   2   54.00486   0.00390625 492
81685   10-17 05:51:30   2   3.5    0.00390625   458
81684   10-17 05:48:45   2   53.44613   0.00390625   490
81683   10-17 05:45:46   2   3.5   0.00393525           458
81682   10-17 05:43:31   2   3.5   0.00390625     457
81681   10-17 05:43:22   2   51.39943   0.00390625   492
81680   10-17 05:41:04   2   55.29402   0.00390625   493
81679   10-17 05:34:19   2   56.059   0.00390625   491
81678   10-17 05:26:41   2   55.33135   0.0039199502   494
81677   10-17 05:20:42   2   52.549   0.00393066   490
81676   10-17 05:19:23   2   52.539   0.00393066   491
81675   10-17 05:18:23   2   51.44093   0.00390625   490
81674   10-17 05:18:06   2   52.539   0.00390625   492
81673   10-17 05:13:08   2   51.12446   0.00390625   492
81672   10-17 05:06:26   2   53.16146   0.00390625   492
81671   10-17 05:03:57   2   51.19803   0.00390625   491
81670   10-17 05:02:52   3   154.48503   0.00390625   3879
81669   10-17 04:59:33   2   50.96734   0.00390625   491
81668   10-17 04:57:54   2   51.24806   0.00390625   493
81667   10-17 04:54:04   2   51.93961   0.0039380998   492
81666   10-17 04:47:44   2   52.44701   0.00390625   490
81665   10-17 04:47:40   2   51.39916   0.00390625   492
81664   10-17 04:45:42   2   54.39031   0.00390625   493
81663   10-17 04:37:30   2   53.73399   0.00390625   492
81662   10-17 01:42:41   2   3.5   0.00390625   457
81661   10-17 01:27:19   3   7.22295   0.00390625   805
81660   10-16 21:35:42   1   3.5   0.0273674298   267
81659   10-16 23:31:58   1   3.5   0.0548651516   266
81658   10-16 21:34:55   1   3.5   0.0551264212   267
81657   10-16 21:33:22   1   3.5   0.0548082106   267
81656   10-16 21:33:02   1   3.5   0.0552669093   266
81655   10-16 21:31:04   1   3.5   0.0549398996   267
81654   10-16 21:30:45   1   3.5   0.0545434989   266
81653   10-16 21:30:35   1   3.5   0.0541342199   266
81652   10-16 21:30:27   1   3.5   0.0537202097   267
81651   10-16 21:30:20   1   3.5   0.0540380292   266
81650   10-16 21:28:39   1   3.5   0.053843081   265
81649   10-16 21:28:04   1   3.5   0.0556067489   266
81648   10-16 21:25:35   2   3.5   0.00390625    457
81647   10-16 21:23:17   1   3.5   0.0547438413   266
81646   10-16 21:23:05   1   3.5   0.0545937084   266
81645   10-16 21:22:24   1   3.5   0.0544282608   265
81644   10-16 21:21:45   1   3.5   0.0547031201   266
81643   10-16 21:20:10   1   3.5   0.0542926304   266
81642   10-16 21:20:02   1   3.5   0.0540105514   267
81641   10-16 21:19:38   1   3.5   0.0539637692   266
81640   10-16 21:18:44   1   3.5   0.0535899587   268
81639   10-16 21:18:32   1   3.5   0.0533192903   265
81638   10-16 21:18:07   1   3.5   0.0532192215   267
81637   10-16 21:18:00   2   3.5   0.00390625     456
81636   10-16 21:17:20   1   3.5   0.0523933806   265
81635   10-16 21:17:08   1   3.5   0.0521740988   266
81634   10-16 21:16:37   1   3.5   0.0518277511   265
81633   10-16 21:16:23   1   3.5   0.0517230406   267
81632   10-16 21:15:37   1   3.5   0.0513498187   266
81631   10-16 21:15:27   1   3.5   0.0518314391   267

the block sizes (last column) are starting to grow...maybe the network was choking on a few?