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

[gorgorom]

ASIC - Andorian Security Iridium coin.

Sha coin, asics friendly. What do you think?

If you are a dev, pm me, we can work on a SHA coin

[MaGNeT]

Opened my KED wallet with modest balance and had a POS block roll in and crashed it 

yeah..Stake blocks are the only ones barely getting thru....Work blocks are being rejected.

Issue is being worked on.

Looks like the same problem with COL and Maples.

[dreamwatcher]

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.

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.

Agreed , PHP can be a pain to secure up, plus with all the database operations an exchange operates closer to a C++ program then a PHP application.

My suggestion would be to write it like CCE3, Python (2.7 or 3) and use the Cherrypy3 HTML framework. C++ can be great for speed, but it really was not designed with facing the internet in mind, so a developer really needs to be sure of their C++ skills, because it is real easy to introduce security holes in C++. Remember C++ is closer to being a low level language vs Python/PHP. This gives great flexibility and speed, but a much larger responsibility for anticipating and dealing with security issues.

This is not to say that c++ cannot be secure against the internet, just that there is less room for error. Languages like Python were written with facing the internet in mind, so it tends to be more forgiving if a security protocol or practice is missed.

One of the advantages of python is that it integrates C++ modules well, so one can design fast c++ modules that do not directly interact with the internet,  but leave the web service to Python/Cherrypy.

Anyway my public 0.2 GPL on the subject.  

[unfocus]

I did contact scifi to send me and dream the existing python code.

I am a python developer in real-life. I am not promising anything, but I'll try my best to complete it. Hopefully it just need  finishing touches rather than having gaping holes or even  malicious code.

[dreamwatcher]

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  

I am going to extend this offer for another 24 hours.

After this extension I will need help if I am to extend it longer. As of now it will cost me 3,780 KED per day, but I want to keep interest up in the coin.

Basically I will pay out of pocket, all the shares that go into solving the next POW block in the pool. We are over 118,225 shares at present, so if the client/daemon were repaired now and the pool found a block, each share would be worth 3780/118,225 ~ 0.03197 KED.

This means miners who continue to mine at the pool will get paid pretty much as if everything was working (As was laid out in the original offer), once the next POW block is mined (Client/Daemon fixed)

[imrer]

Another altcoin? It can't be even profitable...

[jonoiv]

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  

I am going to extend this offer for another 24 hours.

After this extension I will need help if I am to extend it longer. As of now it will cost me 3,780 KED per day, but I want to keep interest up in the coin.

Basically I will pay out of pocket, all the shares that go into solving the next POW block in the pool. We are over 118,225 shares at present, so if the client/daemon were repaired now and the pool found a block, each share would be worth 3780/118,225 ~ 0.03197 KED.

This means miners who continue to mine at the pool will get paid pretty much as if everything was working (As was laid out in the original offer), once the next POW block is mined (Client/Daemon fixed)

cgminer just said, block found for pool (kedcoin.com pool) ! Strange.    I was solo on a different machine and just getting rejects.  Does anyone know if there were any issues with cosmoscoin? because this is supposed to be identical.  


and by the way, I will mine for free.  I have enough of these coins to have a vested interest +  I want to see the whole syfy thing succeed,  It's a cool little branch of crypto that could really take off

[scificoin]

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  

I am going to extend this offer for another 24 hours.

After this extension I will need help if I am to extend it longer. As of now it will cost me 3,780 KED per day, but I want to keep interest up in the coin.

Basically I will pay out of pocket, all the shares that go into solving the next POW block in the pool. We are over 118,225 shares at present, so if the client/daemon were repaired now and the pool found a block, each share would be worth 3780/118,225 ~ 0.03197 KED.

This means miners who continue to mine at the pool will get paid pretty much as if everything was working (As was laid out in the original offer), once the next POW block is mined (Client/Daemon fixed)

I will send you the 10000 premine seen as It is not being used for anything.  as soon as this sorted out.   At the moment I'm drawing blanks.  

Opened my KED wallet with modest balance and had a POS block roll in and crashed it  

yeah..Stake blocks are the only ones barely getting thru....Work blocks are being rejected.

Issue is being worked on.

Looks like the same problem with COL and Maples.

Do you have any info or links for this as I can't find anything.  

[Shad3dOne]

scificoin, here's a clue:

https://bitcointalk.org/index.php?topic=279601.msg3102123#msg3102123

and maybe another:

https://bitcointalk.org/index.php?topic=279601.msg3146528#msg3146528

cheers.

[dreamwatcher]

After looking at above link, and poking around a bit:

81660 was the last POW Block accepted into the network.

81661 was the FIRST POS BLOCK GENERATED ON THE BLOCK CHAIN (I am almost positive, I have not seen a POS block before 81661)

[dreamwatcher]

OK, when Infinite coin appeared to have a similar problem, one of the commits that solved it:

Kernel.cpp

Code:

static std::map<int, unsigned int> mapStakeModifierCheckpoints =
     boost::assign::map_list_of
     ( 0, 0x0e00670bu )
+    ( 21000, 0x24b90804u )
+    ( 42000, 0x5743a9a6u )
     ;

These are the same lines in Darsek:

Code:

// Hard checkpoints of stake modifiers to ensure they are deterministic
static std::map<int, unsigned int> mapStakeModifierCheckpoints =
    boost::assign::map_list_of
    ( 0, 0x0e00670bu )
    ;

 

[dreamwatcher]

And more:

Checkpoints.cpp from Infinte coin on that commit:

Code:

@@ -25,7 +25,8 @@
     static MapCheckpoints mapCheckpoints =
         boost::assign::map_list_of
         (    0, hashGenesisBlockOfficial )
-
+  ( 21000, uint256("0x00000015bc07113fe21452dab5845900c882a28a8856eac2cc2f2b5f7b527bb3"))
+  ( 42000, uint256("0x0000000110c24701275558c16f9400f98f80dabcfd5874e22932129df2ea6f3f"))
     ;
 
     static MapCheckpoints mapCheckpointsTestnet = 

It appears to me that the block checkpoint for zero block uses a variable whereas the Stake modifier uses a hard-coded value that appears the same in both coins.

Should they be the same, or do we need to modify the block 0 stake modifier to match a value in Darsek?

Never mind, UFC is using the same value and it does not have the problem....Dam

[meta.p02]

Disagree with SHA coin. Assuming our intention is to make this marketable to Star Trek fans, we should not require specialised equipment to mine it.

After looking at above link, and poking around a bit:

81660 was the last POW Block accepted into the network.

81661 was the FIRST POS BLOCK GENERATED ON THE BLOCK CHAIN (I am almost positive, I have not seen a POS block before 81661)

No - I mined PoS blocks 75306, 75170 and 73945. All zero reward. (for some reason min PoS reward is set rather high, I think it should be set to a lower value say 0.0001)

Also, what's the maturity time for stake? Is it 30 days? (I hope not... I just sent my entire 189 KED to myself for stake generation)

[dreamwatcher]

Disagree with SHA coin. Assuming our intention is to make this marketable to Star Trek fans, we should not require specialised equipment to mine it.

After looking at above link, and poking around a bit:

81660 was the last POW Block accepted into the network.

81661 was the FIRST POS BLOCK GENERATED ON THE BLOCK CHAIN (I am almost positive, I have not seen a POS block before 81661)

No - I mined PoS blocks 75306, 75170 and 73945. All zero reward. (for some reason min PoS reward is set rather high, I think it should be set to a lower value say 0.0001)

Also, what's the maturity time for stake? Is it 30 days? (I hope not... I just sent my entire 189 KED to myself for stake generation)

Dammit..there kind of goes that theory. It just appears to be stake difficulty related. As if somehow POS information is getting mixed up POW (Getwork information).

Maybe I have been up too long with no sleep, second time today I made a complete ass out of myself.

[meta.p02]

KED getwork gives the following... Can anyone decipher it?

{
"midstate" : "675c64ab03bfcc587dc7631e8ca74dc63bf82d97dcdb79edf2a75b7c5a16b8fd",
"data" : "000000042aa1497ccc07747f86dad47bd873bfccc29b0ee40b8a90bde601bb8b0446f5f40c7cfc9 6cf831532938649867f9565c829409a6437d8c0fc7d0460d5824c3865526098461d828463000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
"hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
"target" : "0000000000000000000000000000000000000000000000000000638402000000"
}

[truckythin]

did KED issues resolved yet? going to put a bit on pool for couple hours if it can help 

[unfocus]

Dream,

Don't beat yourself up. You are probably the most capable person to fix this, and you've done a lot for the community.

[dreamwatcher]

KED getwork gives the following... Can anyone decipher it?

{
"midstate" : "675c64ab03bfcc587dc7631e8ca74dc63bf82d97dcdb79edf2a75b7c5a16b8fd",
"data" : "000000042aa1497ccc07747f86dad47bd873bfccc29b0ee40b8a90bde601bb8b0446f5f40c7cfc9 6cf831532938649867f9565c829409a6437d8c0fc7d0460d5824c3865526098461d828463000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
"hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
"target" : "0000000000000000000000000000000000000000000000000000638402000000"
}

I have been looking at those all night and comparing to getblocktemplate to find discrepancies.

Here is a primer on the getwork protocol:

https://en.bitcoin.it/wiki/Getwork

[dreamwatcher]

And here is a getwork primer geared towards Scrypt based coins:

https://litecoin.info/Scrypt

Breakdown of data and header

    See Block hashing algorithm

~/litecoind getwork
{
    "midstate" : "40fd268321efcf60e625707d4e31f9deadd13157e228985de8a10a057b98ed4d",
    "data" : "0000000105e9a54b7f65b46864bc90f55d67cccd8b6404a02f5e064a6df69282adf6e2e5f7f953b 0632b25b099858b717bb7b24084148cfa841a89f106bc6b655b18d2ed4ebb191a1d018ea7000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
    "hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
    "target" : "0000000000000000000000000000000000000000000000000000a78e01000000"
}

The data field is stored in big-endian format. We need to cover that to little-endian for each of the fields in the data because we can pass it to the hashing function.

Data is broken down to:

    Version - 00000001 (4 bytes)
    Previous hash - 05e9a54b7f65b46864bc90f55d67cccd8b6404a02f5e064a6df69282adf6e2e5 (32 bytes)
    Merkle root - f7f953b0632b25b099858b717bb7b24084148cfa841a89f106bc6b655b18d2ed (32 bytes)
    Timestamp - 4ebb191a (4 bytes)
    Bits (target in compact form) - 1d018ea7 (4 bytes)
    Nonce - 00000000 (4 bytes)

You need covert these from big-endian to little-endian. This is done 2 characters at a time because each byte is represented by 2 hex chars. (each hex char is 4 bits)

    Version becomes 01000000
    Previous hash becomes e5e2f6.....a5e905
    Merkle root becomes edd218...53f9f7
    Timestamp becomes 1a19bb4e
    Bits becomes a78e011d
    And Nonce is a 32-bit integer you choose that will make the scrypt hash be less than the target.

Remember that you will need to convert the 32-bit nonce to hex and little-endian also. So if you are trying the nonce 2504433986. The hex version is 9546a142 in big-endian and 42a14695 in little-endian.

You then concatenate these little-endian hex strings together to get the header string (80 bytes) you input into scrypt

01000000 e5e2f6.....a5e905 edd218...53f9f7 1a19bb4e a78e011d 42a14695

[unfocus]

Just an idea, why don't you make the changes locally, and recompile ked. Who knows if it will work. UFC uses the same value, but it has different other settings.