Topic: Δ DeltaCredits - Trade-in ends in less than 24 hours - page 4. (Read 81047 times)
not getting a single connection, Chain dead, 0 vol on exchange, Gladimor silent and absent. Not looking good at all!!!
Yes, fixing PoS should have priority. But if there will be a fork anyway it might not harm to enable/extend PoW on a no reward basis, just to be sure to have a fallback option.
All depends on what Gladimor has in mind for this coin, though.
All depends on what Gladimor has in mind for this coin, though.
If in the case the network gets stuck again, I will spin up hardware miners to get it moving again.
It is time for this.
I saw that message before, and wanted to try mining this too. Well - not after I looked into the code...
Not sure how he is going to use miners to move the chain. See this:
Quote
bool CBlock::AcceptBlock()
{
// Check for duplicate
uint256 hash = GetHash();
if (mapBlockIndex.count(hash))
return error("AcceptBlock() : block already in mapBlockIndex");
// Get prev block index
map::iterator mi = mapBlockIndex.find(hashPrevBlock);
if (mi == mapBlockIndex.end())
return DoS(10, error("AcceptBlock() : prev block not found"));
CBlockIndex* pindexPrev = (*mi).second;
int nHeight = pindexPrev->nHeight+1;
if (IsProofOfWork() && nHeight > LAST_POW_BLOCK)
return DoS(100, error("AcceptBlock() : reject proof-of-work at height %d", nHeight));
{
// Check for duplicate
uint256 hash = GetHash();
if (mapBlockIndex.count(hash))
return error("AcceptBlock() : block already in mapBlockIndex");
// Get prev block index
map
if (mi == mapBlockIndex.end())
return DoS(10, error("AcceptBlock() : prev block not found"));
CBlockIndex* pindexPrev = (*mi).second;
int nHeight = pindexPrev->nHeight+1;
if (IsProofOfWork() && nHeight > LAST_POW_BLOCK)
return DoS(100, error("AcceptBlock() : reject proof-of-work at height %d", nHeight));
LAST_POW_BLOCK is 5000. This chain is not mixed PoW/PoS now, it is pure PoS. PoW blocks are rejected by the chain after that block.
PoS should be fixed instead and/or big wallets need to stake again.
If in the case the network gets stuck again, I will spin up hardware miners to get it moving again.
It is time for this.
I have one connection now as well, the first of your two actually. But thank you for the nodes, I add the second to my config to try to get connected to it as well. My inputs are still staking locked so I'm no help either, though.
I agree with you on these settings. It seems very few coin devs actually think about changing split and combine, they're the same in any of the few coins I had reason to look them up yet. nCoinbaseMaturity should require a fork, although I'm not sure, but if things are handled properly the network should refuse stakes/transactions from blocks it considers inmature.
The other two settings should mostly affect the wallet behavior only to organize itself ensuring a smoothly staking and running wallet and should need no fork. Which would mean that wallets changed and compiled by the users would work within the chain as well.
I agree with you on these settings. It seems very few coin devs actually think about changing split and combine, they're the same in any of the few coins I had reason to look them up yet. nCoinbaseMaturity should require a fork, although I'm not sure, but if things are handled properly the network should refuse stakes/transactions from blocks it considers inmature.
The other two settings should mostly affect the wallet behavior only to organize itself ensuring a smoothly staking and running wallet and should need no fork. Which would mean that wallets changed and compiled by the users would work within the chain as well.
According to the blockexplorer there has not beet a block in 2 weeks, isn't there really no one staking? 
I am staking (though I don't have many free inputs to stake). But it just does not move. Dunno, maybe the coins do not have enough confirmations after they got out of staking... The code has to be tweaked anyway though.
Yep, I have connections
Here they are:
16:21:37

[
{
"addr" : "94.22.185.125:31414",
"services" : "00000001",
"lastsend" : 1460028026,
"lastrecv" : 1460027910,
"conntime" : 1460027910,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : false,
"startingheight" : 34670,
"banscore" : 0
},
{
"addr" : "5.9.36.211:36519",
"services" : "00000001",
"lastsend" : 1460028026,
"lastrecv" : 1460028025,
"conntime" : 1460028025,
"version" : 60013,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 34670,
"banscore" : 0
}
]
But now (after looking there once more) I understand why wallet not staking... I have split my inputs to move them to different addresses (so they do not automatically combine again), and the coins did not completely confirm yet (just 6 out of 10 needed confirmations..). So my coins are in fact not mature enough.. sorry for that..
This combining threshold of 1000 coins is a pain, and it is the main reason why this blockchain has constant problems moving forward. I suppose the Dev is far from being technically advanced (being mostly trader/PR kind of person), hence he just does not realize the wrong staking parameters he set on the wallet, and does not make any move to fix them (probably because the developer hired to make the coin, needs to be called again for that..
).From other hand, the changes needed to fix this are pretty easy to do:
1. Decrease the nCoinbaseMaturity. Set it to 10, so 20 confirms are enough for a newly minted block.
2. Change the nStakeCombineThreshold. Set it to "50 * COIN" instead of "1000 * COIN"
3. Change the nStakeSplitAge. Set it to "9 * 24 * 60 * 60", instead of "1 * 24 * 60 * 60" (this step is optional, but desirable)
Not even sure fork is needed for this. Most probably not. Even me, with my very limited knowledge on this codebase, could do that. For a developer who is familiar with the codebase, and has the dev environment set, this is like a 20 minute work, including testing.
According to the blockexplorer there has not beet a block in 2 weeks, isn't there really no one staking?
I am staking (though I don't have many free inputs to stake). But it just does not move. Dunno, maybe the coins do not have enough confirmations after they got out of staking... The code has to be tweaked anyway though.
According to the blockexplorer there has not beet a block in 2 weeks, isn't there really no one staking?
I am staking (though I don't have many free inputs to stake). But it just does not move. Dunno, maybe the coins do not have enough confirmations after they got out of staking... The code has to be tweaked anyway though.
According to the blockexplorer there has not beet a block in 2 weeks, isn't there really no one staking?
what will happen to DCRE?
Not much it seems 
what will happen to DCRE?
Nodes please
40 confirmations for a block is too much for a coin with under 100K supply and nStakeCombineThreshold=1K. Such situations with chain stuck will appear again and again, moreover with decreasing supply.
The wallet code really needs to be tweaked to fix this.
The wallet code really needs to be tweaked to fix this.
I also have all coins locked in staking, hopefully someone can move the chain.
Since there are usually not that many wallets online and moving the chain rather slowly (1 connection here at moment and my coins are staking locked) and with me being off into holidays tomorrow (I'll take the machine with the wallet with me but it'll probably drop out for the next few days) it would be nice if someone else could jump in for a while. 
Amount sent to burn address: 2632.56840503 DCR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
Glad to see some action!!! & a sizeable chunk burned!
Nice to see here some movement again.
Looks like stuck again, please stake.
I will wait a little bit more and see if Gladimor continue or really abandoned this project...Otherwise i will dump all i have 
ive come off chat with gladimore a day ago ...
if what he says is true - and he follows through with it - you are best to keep the coins you have ...
i will be watching - and not only that - will be helping gladimore where i can if this comes to light in the next few weeks ...
if you are going to dump - let me know how many coins you are dumping and at what price you want for them ... ill consider whether its a good for me - and maybe we can make a deal happen ...
#crysx
Thank you, i'm gonna hold my coins
Amount sent to burn address: 2632.56840503 DCR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
Nice to see you are still here !
Amount sent to burn address: 2632.56840503 DCR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
http://cryptobe.com/address/DBurnAddressDELTACreditsDCR1MHEkpR
Jump to: