We should have Yubikey and Google auth when finished
Topic: [ANN] StarTrek insipred coins =) and mining links (Low Diff) Nice Bounties! - page 27. (Read 60763 times)
September 15, 2013, 11:42:22 AM
We should have Yubikey and Google auth when finished
September 15, 2013, 11:40:35 AM
Are there ways to earn this coin without mining, maybe by writing or sharing links?
Yes !
We will be having big give aways for people posting on Trek forums and for basically spreading the word.
At the moment we are waiting for completion of the exchange, as as soon as this is released then we will begin to push the coins. I just think until we have the exchange ready, promotion of the coins is pointless.
How can I get involved? Is there a specific forum or link to share? Just let me know when you're ready.
We will do ! as soon as the exchange has passed beta testing we will be full time promoting and doing the giveaways and looking at viable services. We have a web host interested in using UFC or KED for hosting. But for now we just need to get fully up and running with the exchange.
September 15, 2013, 11:37:40 AM
should be on course for beta testing the exchange in 5 days! 
Let us know if you like the look ... but it's unlikely we will change it now. The logo will be slightly different. This was a first draft. We are hoping for beta testing to begin on Sat 21st Sept. Then we will really push these coins. We have some big plans.
Let us know if you like the look
... but it's unlikely we will change it now. The logo will be slightly different. This was a first draft. We are hoping for beta testing to begin on Sat 21st Sept. Then we will really push these coins. We have some big plans.
September 13, 2013, 06:20:36 PM
Are there ways to earn this coin without mining, maybe by writing or sharing links?
Yes !
We will be having big give aways for people posting on Trek forums and for basically spreading the word.
At the moment we are waiting for completion of the exchange, as as soon as this is released then we will begin to push the coins. I just think until we have the exchange ready, promotion of the coins is pointless.
How can I get involved? Is there a specific forum or link to share? Just let me know when you're ready.
September 13, 2013, 05:41:41 PM
Happy Friday the 13th... all CCE instances posting Internal Server Errors.
They are back up...for now
Welcome to the wonderful world of beta testing. 
Dam orphan issue again. I need to rethink my whole strategy on that issue. It is the one bug that is holding me back.
September 13, 2013, 04:42:06 PM
Are there ways to earn this coin without mining, maybe by writing or sharing links?
Yes !
We will be having big give aways for people posting on Trek forums and for basically spreading the word.
At the moment we are waiting for completion of the exchange, as as soon as this is released then we will begin to push the coins. I just think until we have the exchange ready, promotion of the coins is pointless.
Promotion of a coin/coins is always a good idea...
September 13, 2013, 04:21:39 PM
Are there ways to earn this coin without mining, maybe by writing or sharing links?
Yes !
We will be having big give aways for people posting on Trek forums and for basically spreading the word.
At the moment we are waiting for completion of the exchange, as as soon as this is released then we will begin to push the coins. I just think until we have the exchange ready, promotion of the coins is pointless.
September 13, 2013, 10:44:55 AM
Happy Friday the 13th... all CCE instances posting Internal Server Errors.
September 13, 2013, 10:29:54 AM
Are there ways to earn this coin without mining, maybe by writing or sharing links?
September 12, 2013, 02:02:30 AM
I have started testing the server environment.
This means all the SCFI coins have moved to their permanent CCE address ( for both testing and release):
UFC:
ufc.cryptocoinexplorer.com or www.ufc.cryptocoinexplorer.com
KED:
ked.cryptocoinexplorer.com or www.ked.cryptocoinexplorer.com
GPL:
gpl.cryptocoinexplorer.com or www.gpl.cryptocoinexplorer.com
The UFC explorer is down for about an hour while I yet again reconstruct its database due to orphans.
This means all the SCFI coins have moved to their permanent CCE address ( for both testing and release):
UFC:
ufc.cryptocoinexplorer.com or www.ufc.cryptocoinexplorer.com
KED:
ked.cryptocoinexplorer.com or www.ked.cryptocoinexplorer.com
GPL:
gpl.cryptocoinexplorer.com or www.gpl.cryptocoinexplorer.com
The UFC explorer is down for about an hour while I yet again reconstruct its database due to orphans.
September 11, 2013, 11:08:07 PM
ufccoin still can not connect, I affirm that I have no problem. I know of at least more than one person is unable to connect, but I found mine pool inside or someone can connect, do not know why?
Make sure your browser is not blocking cookies. The pool front-end uses a security cookie to stop session hijacking. If your browser is blocking it, the front end will not let you log on, you will need to white list the pool.
September 11, 2013, 10:07:40 PM
i have update the gpl client,why the mined coins all lost?
September 11, 2013, 10:04:43 PM
ufccoin still can not connect, I affirm that I have no problem. I know of at least more than one person is unable to connect, but I found mine pool inside or someone can connect, do not know why?
September 11, 2013, 09:11:06 PM
Whomever is responsible for the UFCCOIN really needs to change the black background. The logo can stay but the black background makes it too hard to read other things on the screen. Luckily its almost an exact copy of almost all of the other pools so I know what I am looking at. But for others this could be troublesome.
September 11, 2013, 03:37:09 PM
I have moved the conversion about the orphan issue to the CCE3 test thread as not to clutter up this thread.
https://bitcointalksearch.org/topic/m.3131923
https://bitcointalksearch.org/topic/m.3131923
September 11, 2013, 02:08:44 PM
The DB load module then queries the daemon for all the block and transaction information for blocks not in the explorers' database.
The issue arises when the daemon gives the db loader information about an orphan block because it has not realized it has an orphan block stored.
The issue arises when the daemon gives the db loader information about an orphan block because it has not realized it has an orphan block stored.
Two things...
First, before the Load Module requests to have the transactions fetched... run the query to fetch all non greater than zero output txids, and loop deletetransaction
Second, given it is an orphan, that means you are seeing TWO blocks with the same block number being brought in by the Load Module? So, a line to test when it sees duplicate block numbers and drop the zero output one? Or maybe instead, a test to find zero output txids and have them in an array that the Load Module references as it fetches so it knows before hand that XXX txid is trash?
Come to think of it... would it not be just as easy to make a seperate module just for this and call it before the Load Module? Have this module test for orphans based on zero ouput, delete them and restart daemon if there is, then run Load module, or if there are none, go on its way?
September 11, 2013, 01:53:10 PM
Thank you for the effort daemon, unfortunately that advice my help somebody running a block "crawler" (even the one's that call themselves "Explorers"), but not a true Explorer.
In CCE3 and all true block explorers, all the block and transaction information is sorted and stored in a separate database. In CCE3,when the coin daemon detects a new block on the network, it triggers "Block Notify", which then starts up the explorers' database load module. The DB load module then queries the daemon for all the block and transaction information for blocks not in the explorers' database.
The issue arises when the daemon gives the db loader information about an orphan block because it has not realized it has an orphan block stored. The db loader then stores the incorrect information and does not realize it until a block references a transaction that does not exist in the database. To try and rollback would be difficult since the offending block could be 1000's of blocks back and all the indexes would have to be corrected. This would add an amount of complexity to the code I want to avoid.
I have thought of a couple of ways around this, but I need help with an estimation of the time it takes the daemon to correct itself.
In CCE3 and all true block explorers, all the block and transaction information is sorted and stored in a separate database. In CCE3,when the coin daemon detects a new block on the network, it triggers "Block Notify", which then starts up the explorers' database load module. The DB load module then queries the daemon for all the block and transaction information for blocks not in the explorers' database.
The issue arises when the daemon gives the db loader information about an orphan block because it has not realized it has an orphan block stored. The db loader then stores the incorrect information and does not realize it until a block references a transaction that does not exist in the database. To try and rollback would be difficult since the offending block could be 1000's of blocks back and all the indexes would have to be corrected. This would add an amount of complexity to the code I want to avoid.
I have thought of a couple of ways around this, but I need help with an estimation of the time it takes the daemon to correct itself.
September 11, 2013, 01:01:19 PM
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.
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
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?
September 11, 2013, 12:53:56 PM
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.
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.
September 10, 2013, 07:27:47 PM
Anyone working on a Dabo table?
Not yet ! but great idea. I will take a look after the exchange is running
Jump to: