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.
Topic: [ANN] StarTrek insipred coins =) and mining links (Low Diff) Nice Bounties! - page 15. (Read 60763 times)
October 17, 2013, 09:43:20 PM
October 17, 2013, 09:28:27 PM
did KED issues resolved yet? going to put a bit on pool for couple hours if it can help 
October 17, 2013, 09:10:15 PM
KED getwork gives the following... Can anyone decipher it?
{
"midstate" : "675c64ab03bfcc587dc7631e8ca74dc63bf82d97dcdb79edf2a75b7c5a16b8fd",
"data" : "000000042aa1497ccc07747f86dad47bd873bfccc29b0ee40b8a90bde601bb8b0446f5f40c7cfc9 6cf831532938649867f9565c829409a6437d8c0fc7d0460d5824c3865526098461d828463000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
"hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
"target" : "0000000000000000000000000000000000000000000000000000638402000000"
}
{
"midstate" : "675c64ab03bfcc587dc7631e8ca74dc63bf82d97dcdb79edf2a75b7c5a16b8fd",
"data" : "000000042aa1497ccc07747f86dad47bd873bfccc29b0ee40b8a90bde601bb8b0446f5f40c7cfc9 6cf831532938649867f9565c829409a6437d8c0fc7d0460d5824c3865526098461d828463000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
"hash1" : "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
"target" : "0000000000000000000000000000000000000000000000000000638402000000"
}
October 17, 2013, 09:07:18 PM
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.
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)
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)
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.
October 17, 2013, 08:57:08 PM
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.
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)
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)
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)
October 17, 2013, 08:45:28 PM
And more:
Checkpoints.cpp from Infinte coin on that commit:
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
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 =
static MapCheckpoints mapCheckpoints =
boost::assign::map_list_of
( 0, hashGenesisBlockOfficial )
-
+ ( 21000, uint256("0x00000015bc07113fe21452dab5845900c882a28a8856eac2cc2f2b5f7b527bb3"))
+ ( 42000, uint256("0x0000000110c24701275558c16f9400f98f80dabcfd5874e22932129df2ea6f3f"))
;
static MapCheckpoints mapCheckpointsTestnet =
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
October 17, 2013, 08:38:44 PM
OK, when Infinite coin appeared to have a similar problem, one of the commits that solved it:
Kernel.cpp
These are the same lines in Darsek:
Kernel.cpp
Code:
static std::map mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0x0e00670bu )
+ ( 21000, 0x24b90804u )
+ ( 42000, 0x5743a9a6u )
;
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 mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0x0e00670bu )
;
static std::map
boost::assign::map_list_of
( 0, 0x0e00670bu )
;
October 17, 2013, 08:32:18 PM
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)
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)
October 17, 2013, 07:55:09 PM
scificoin, here's a clue:
https://bitcointalksearch.org/topic/m.3102123
and maybe another:
https://bitcointalksearch.org/topic/m.3146528
cheers.
https://bitcointalksearch.org/topic/m.3102123
and maybe another:
https://bitcointalksearch.org/topic/m.3146528
cheers.
October 17, 2013, 06:01:00 PM
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 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.
October 17, 2013, 05:54:20 PM
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 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
October 17, 2013, 03:21:42 PM
Another altcoin? It can't be even profitable...
October 17, 2013, 03:16:35 PM
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 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)
October 17, 2013, 03:05:50 PM
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.
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.
October 17, 2013, 02:46:37 PM
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.
October 17, 2013, 01:36:47 PM
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.
October 17, 2013, 01:22:05 PM
ASIC - Andorian Security Iridium coin.
Sha coin, asics friendly. What do you think?
Sha coin, asics friendly. What do you think?
If you are a dev, pm me, we can work on a SHA coin
October 17, 2013, 01:18:39 PM
+1 sha coin!
October 17, 2013, 01:13:02 PM
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.
October 17, 2013, 12:55:35 PM
Opened my KED wallet with modest balance and had a POS block roll in and crashed it
Jump to: