Pages:
Author

Topic: [ANN] Restart of Quantumcoin (SUCCESSFULLY RELEASED) - page 4. (Read 11471 times)

legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
The block explorer says there are 208 blocks and the difficulty is @ 3.306 which explains why it's dead. The difficulty algorithm for the start must have been a bit over the top for it to get as difficult as that in so few blocks.

If anything this topic just goes to show that people are full of shit in general and don't want a fair release. They want the best of both worlds, a ridiculously low starting difficulty but without the orphans that go hand in hand with it.

getinfo
{
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 3210.00000000,
"blocks" : 16726,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.25887916,
"testnet" : false,
"keypoololdest" : 1370912971,
"keypoolsize" : 101,
"paytxfee" : 1.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
hero member
Activity: 630
Merit: 502
The block explorer says there are 208 blocks and the difficulty is @ 3.306 which explains why it's dead. The difficulty algorithm for the start must have been a bit over the top for it to get as difficult as that in so few blocks.

If anything this topic just goes to show that people are full of shit in general and don't want a fair release. They want the best of both worlds, a ridiculously low starting difficulty but without the orphans that go hand in hand with it.
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
hero member
Activity: 630
Merit: 502
If anyone has the source, please post it Smiley

I have the source that I downloaded on release day:

https://apps.memopal.com/e/VQ4Z5JZW
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
Is it dead?
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
It seems that Lhunephel has abandonned this coin?

If anyone has the source, please post it Smiley

Here is the client I downloaded from the OP, please don't trust on my word it's safe; always scan binaries before using them!

QuantumCoin Windows client on MEGA.com

"difficulty" : 0.14836960

getpeerinfo

08:17:59

[
{
"addr" : "178.32.218.153:32962",
"services" : "00000001",
"lastsend" : 1371016850,
"lastrecv" : 1371016849,
"conntime" : 1370986234,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 209,
"banscore" : 0
},
{
"addr" : "149.210.131.122:35652",
"services" : "00000001",
"lastsend" : 1371016948,
"lastrecv" : 1371016948,
"conntime" : 1370991737,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 208,
"banscore" : 0
},
{
"addr" : "62.163.9.155:9998",
"services" : "00000001",
"lastsend" : 1371017913,
"lastrecv" : 1371017913,
"conntime" : 1371017911,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 16719,
"banscore" : 0
},
{
"addr" : "67.193.198.104:51603",
"services" : "00000001",
"lastsend" : 1371016138,
"lastrecv" : 1371016138,
"conntime" : 1370994523,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1040,
"banscore" : 0
},
{
"addr" : "64.251.188.62:34870",
"services" : "00000001",
"lastsend" : 1371017477,
"lastrecv" : 1371017477,
"conntime" : 1371003069,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 1049,
"banscore" : 0
},
{
"addr" : "77.169.33.78:53947",
"services" : "00000001",
"lastsend" : 1371016215,
"lastrecv" : 1371016215,
"conntime" : 1371016214,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 208,
"banscore" : 0
},
{
"addr" : "46.4.24.69:53075",
"services" : "00000001",
"lastsend" : 1371017272,
"lastrecv" : 1371017271,
"conntime" : 1371017270,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 208,
"banscore" : 0
}
]

quantumcoin.conf

Quote
rpcuser=x
rpcpassword=y
rpcallowip=192.*.*.*
rpcport=9999
daemon=1
server=1
gen=0
addnode=178.32.218.153:32962
addnode=149.210.131.122:35652
addnode=62.163.9.155:9998
addnode=67.193.198.104:51603
addnode=64.251.188.62:34870
addnode=77.169.33.78:53947
addnode=46.4.24.69:53075
addnode=78.47.197.236
addnode=78.46.164.138

Forward port 9998 in router for more connections.
full member
Activity: 224
Merit: 100
wow, what's next.. Universe Coin?
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
Where is the website? Where is the client? 1 wallet is in sync, the other says it has to download another 16k blocks  Huh Any update on this by Lhunephel?
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
Download location for the client is gone?  Huh
legendary
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
When I start the client it wants to download 16k blocks, is it forked?
full member
Activity: 181
Merit: 100
sounds like we should merge the ideas of ELC and QTC...

but as you said no one wants to mine a coin that ISNT CoinChoose top ofthe pile :/
member
Activity: 90
Merit: 10
I updated several parameters to make the block chain reacting smoother, hopefully making it more interesting for other miners. Updated sources are available on GitHub now. Because the block chain is not active at the moment (last block is several hours old Sad) the changes are active immediate. Please update your clients before mining the block chain. An updated Windows binary is also available. The retargeting is now a lot of faster with lower network hash rate and the difficulty should change smoother. Also the target timespan is now decreasing faster with increasing network hash rate.
member
Activity: 90
Merit: 10
I don't think that the block chain should already be declared as dead. At least I hope it. Maybe it takes some time until people will be willing to join. But I think Petr1fied is right. Everybody whines about the new coins with a very low difficulty, with an high amount of precalculated blocks, with a lot of orphans. But when you do a fair release with a higher difficulty as normal, a very fast retargeting at the beginning, nobody is interested. It's sad, but looks like it's the reality.
newbie
Activity: 7
Merit: 0
I tried. I threw my modest 1000 Khash at it until the client would no longer sync. I did think it was weird near the end when I was finding all of the blocks and there were no new blocks detected on the network. RIP quantumcoin.
hero member
Activity: 630
Merit: 502
That probably goes to prove that although people say they want a fair release with a difficulty of 1.0 so that it's not an orphanfest they don't actually mean it. What they really want is to mine when it's very easy so they can find lots of blocks. They just don't want the orphans that go hand in hand with that.
member
Activity: 90
Merit: 10
At the moment the hash rate is too low for the block chain to work like expected Sad
legendary
Activity: 934
Merit: 1000
@tyrion70: But I think there's something wrong with the displayed retarget interval. The maximum retarget interval is 15. Also I think the target spacing is not 60 seconds at the moment. Have a look in the sources (quantumcoin/src/main.cpp), there are three methods calculating the retarget, target spacing and target timespan parameters. I think the p2pool code has to be modified like with the block values.

You're right; I used the wrong spacing and interval params; same as with the subsidy.. But those values are really only used for statistic purposes. I'll take a look at them over the weekend.

Cheers
member
Activity: 90
Merit: 10
@tyrion70: But I think there's something wrong with the displayed retarget interval. The maximum retarget interval is 15. Also I think the target spacing is not 60 seconds at the moment. Have a look in the sources (quantumcoin/src/main.cpp), there are three methods calculating the retarget, target spacing and target timespan parameters. I think the p2pool code has to be modified like with the block values.
Pages:
Jump to: