[ANN] StarTrek insipred coins =) and mining links (Low Diff) Nice Bounties!

[dreamwatcher]

the ufc pool can't connect?

Are you still having issues? I just tested the pool with one of my rigs and it is working.

If you are able to connect now, there must of been a internet outage on the server side that is now restored.

IF you are still unable to connect, let me know.

[Thrash]

Looks like the block explorers are dead. I'm getting 500 errors o nthe pages.

[dreamwatcher]

Looks like the block explorers are dead. I'm getting 500 errors o nthe pages.

Thanks you  for letting me know. I was just about to check them.

It looks like the KED and UFC Explorers went down. Remember these are beta test explorers, so this is prone to happen.

I believe the main bug right now occurs when somebody requests a ledger from an account with a long history, and clicks away before the ledger shows up.

Just a reminder, some accounts will take a few seconds to load, these are usually accounts with transactions numbering in the thousands. So give it a few seconds.

[huahua520]

the ufc pool can't connect too.
Only has been solo.

[dreamwatcher]

the ufc pool can't connect too.
Only has been solo.

Hmm, this is interesting.

I am able to connect to it , as are 5 other miners currently on it.

Could you please send me the command line or conf file you are using? PM or post.

Thank you

[huahua520]

the ufc pool can't connect too.
Only has been solo.

Hmm, this is interesting.

I am able to connect to it , as are 5 other miners currently on it.

Could you please send me the command line or conf file you are using? PM or post.

Thank you

cgminer --scrypt -o stratum+tcp://ufccoin.com:4444 -u username -p password

[dreamwatcher]

the ufc pool can't connect too.
Only has been solo.

Hmm, this is interesting.

I am able to connect to it , as are 5 other miners currently on it.

Could you please send me the command line or conf file you are using? PM or post.

Thank you

cgminer --scrypt -o stratum+tcp://ufccoin.com:4444 -u username -p password

The only thing I can think of: Did you create a worker(s)?

The login your miner uses is separate from your pool account login. The reason for this : most back-end mining software will only read clear text passwords from the pool_worker table in the database. Your account password is encrypted in a different table in the database.

Go to: My Account > My workers. Add a worker by placing anything in the user box <Your username>.<user>  and a password in the password box. then click the add worker button. Do not make the mining password the same as your account password as it is stored as clear text. In the case of workers, that does not matter because all somebody can do with your worker password is mine for you and generate coins for you.

Then use <your username>.<whatever you used here> and the worker password in your command line.

[Scooby903]

Anyone still mining KED?  I've got almost 8k now 

[meta.p02]

Anyone still mining KED?  I've got almost 8k now 

25 blocks (and 1 orphan)! And I've only got 44KH/s.

Meanwhile in UFC-land I've got 10/1.

[truckythin]

not heard anything above trading KED so i give up few week ago. 

[ropyu1978]

i have update the gpl client,why the mined coins all lost?

[sapsan]

Can't compile Qt-GPL on my Ubuntu 12.10 x64 and on 13.04 x64:

Code:

/usr/bin/ld: cannot find -lboost_system-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_filesystem-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_program_options-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_thread-mgw46-mt-sd-1_53
collect2: error: ld returned 1 exit status
make: *** [GoldPressedLatinum] Error 1

Looks like Qt-sources only for windows.

[huahua520]

gpl very good, good, there are plans to do on the trading platform(cryptsy)?

[scificoin]

gpl very good, good, there are plans to do on the trading platform(cryptsy)?

It would be worth reading the thread.  I think i have answered this 3 times already. 

[scificoin]

Can't compile Qt-GPL on my Ubuntu 12.10 x64 and on 13.04 x64:

Code:

/usr/bin/ld: cannot find -lboost_system-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_filesystem-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_program_options-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_thread-mgw46-mt-sd-1_53
collect2: error: ld returned 1 exit status
make: *** [GoldPressedLatinum] Error 1

Looks like Qt-sources only for windows.

The source is here,  the daemons all compile fine in debian 6, 7  and Ubuntu 12.04 64bit
with the exception of Darsek (KED) which has a problem in debian 6.
https://github.com/scificoin/Gold-Pressed-Latinum

As for a linux QT.  I have not looked at this but if someone wants to have a go we could look at a bounty in the form of KED or UFC.

[scificoin]

So this is really just a quick update on the exchange.

 All daemons are installed and running rock solid,  daemon interactions are all behaving as expected with no surprises.

 The wallet system we are building should be finished in 2 days and then we can finalize the trading system.  We are currently hoping for 10 days to beta testing. 

[Xaltotun]

Anyone working on a Dabo table?

[scificoin]

Anyone working on a Dabo table?

Not yet ! but great idea.  I will take a look after the exchange is running

[dreamwatcher]

The block explorers are back up. The reason for the issues  continues to be orphan blocks. This issue has plagued me since starting the CCE3 project.

Now for a little rant:

I have asked over and over for developer input on how to handle orphans. Even something as simple as an opinion on how long the daemon takes to realize it has an orphan block, correct the information, and start reporting the correct information.

Know what I got:

Crickets. Not a single answer from ANY developer. In fact, I have not gotten ANY advice from any developer. Sometimes makes me wonder why I am bothering. I put all this effort, time and money into the project and seems like nobody gives a crap.

CCE has been around a little over a year now, so the excuse " I have not heard of it" is a complete garbage.

--End Rant--

Now this not necessary aimed at the scifi coin developers, as this is a new venture and they may not have seen the questions or even known about the CCE3 project. But I am going to paste this all over so maybe somebody will get the picture.

[daemonfox]

The block explorers are back up. The reason for the issues  continues to be orphan blocks. This issue has plagued me since starting the CCE3 project.

Now for a little rant:

I have asked over and over for developer input on how to handle orphans. Even something as simple as an opinion on how long the daemon takes to realize it has an orphan block, correct the information, and start reporting the correct information.

Know what I got:

Crickets. Not a single answer from ANY developer. In fact, I have not gotten ANY advice from any developer. Sometimes makes me wonder why I am bothering. I put all this effort, time and money into the project and seems like nobody gives a crap.

CCE has been around a little over a year now, so the excuse " I have not heard of it" is a complete garbage.

--End Rant--

Now this not necessary aimed at the scifi coin developers, as this is a new venture and they may not have seen the questions or even known about the CCE3 project. But I am going to paste this all over so maybe somebody will get the picture.

Not that this is in any way a definite... i am just tossing out a thought... but... is it that the daemon needs to be kicked? I notice my restarted GPL client has no orphans listed... only clean transactions...

Also... if their is a txid for thiose orphans and a way to have the cronjobs see a txid is indeed an orphan... you can always RPC call the deletetransaction <txid> function to remove it then restart the daemon?

If orphans are easily picked out that a cronjob can be written... parse all known orphans into an array of txids, then loop deletetransaction on the array and end it with restarting the daemon.

EDIT: It occurs to me the test to pass whether an orphan is simple... is the Value of the output greater than zero? if yes... move along... if no... add it to the array.

Think that will do it?