I have seen some real developer incompetence at another thread (Shinycoin) , slim dev no longer 'feels' like a lost case  I hope re-launch happens soon, got nothing to mine with my cpus... Haha... |
|
|
|
I have made a standalone miner for this coin, Linux only for now and sources will be released soon. Download : https://www.dropbox.com/s/dbfxvmoryekyq5i/shinyminerUsage: ./shinyminer -o http://127.0.0.1:PORT -O USER:PASS -t 1 Warning! Each thread uses 15 GB of RAM. |
|
|
|
|
I'll have a pool up pretty soon, if there is interest...
Edit: we do need a standalone miner first.
|
|
|
|
No idea, that's just some random node. o_0 |
|
|
|
|
DNS Seeder is up : dnsseed.slimcoinpool.com
|
|
|
|
what happend i can get sync now ,and block is 17144 now.
Ha, yeah. Just started my wallet up and it's synced to 17151. I think this is irrelevant though as it seems we're going to be re-launching from 16000. Can we get a definitive statement from the dev about this if possible? The hard fork is at block 15934. |
|
|
|
There are some anomalies in the blockchain, look at block 1000, 4000 and 11000 for example.
...
Maybe that's a PoB block mislabeled as PoW?
Because the hash is just a random hash, and the block reward doesn't adhere to reward = 50/((diff*4096)^(1/4))
50/(0.02457705*4096)^(1/4)) = 15.78...
There actually is no label for PoB, check the code. An easy way to identify them from the getblock() response is to check if the nonce == 0 (as is the case in the example you give). I'm not sure that's 100% foolproof, but it held in the first 12,345 blocks at least. Oh ok, that just got me confused. |
|
|
|
Could people post their ./slimcoind getblockhash 15934
0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c 15935: af377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5 |
|
|
|
Definitely instamine after 15934
Of course. After your pool shut down nobody could be sure to connect to main fork so there was someone connected to his own fork and instamine. Relaunch after block 15934. Dev is inactive again ? Pool was actually shut down around block 16315. I remember seeing even higher block, but the network kicked the pool back everytime? So relaunch after block 15934 is a better option. I don't mind losing a few hundert SLMs. Truth is, we mined about 750 blocks after block 16000, of which ~300 were accepted by the network, the others were kicked each time the network synced back ~40 blocks. |
|
|
|
Definitely instamine after 15934
Of course. After your pool shut down nobody could be sure to connect to main fork so there was someone connected to his own fork and instamine. Relaunch after block 15934. Dev is inactive again ? Pool was actually shut down around block 16315. |
|
|
|
|
Definitely instamine after 15934
From pool:
164 1402837916013 {"coin":"slimcoin","ip":"162.220.242.52","reward":16.01,"height":16000,"blockHash":"000000145278a748c37bef93374ddb7e8ab6f951d72a08d10197a9cbc083320f","txHash":"d6b97b6cbd124bd302b6fa5cfe8c9fff30a7afa6281e79712eb72c222773f0ab","time":1402837916013,"founder":"SYHJWERaM8XD3qowYxP2cL6ey1iLYf17dD","type":"immature","delayTimes":0}
Daemon:
slimcoin@euserver:~/.slimcoin$ slimcoind getblock 00000388904d9c15f1e964a07cb2dc
e7147951d9eaf0222c6cec31264240aa92
{
"hash" : "00000388904d9c15f1e964a07cb2dce7147951d9eaf0222c6cec31264240aa92",
"size" : 356,
"height" : 16000,
"version" : 1,
"merkleroot" : "5f1f8a6c66a3064f92a648dfb9df3cffd3a2ad00db89c40530c6cac6741f
8a30",
"time" : "2014-06-15 23:45:48 UTC",
"nonce" : 2147483861,
"bits" : "1e039e01",
"difficulty" : 0.00107989,
"mint" : 34.48000000,
"previousblockhash" : "00000064ef4055db5d5d607d4541e804e08d2bc663f11e8e848e1
d2632ef1e42",
"nextblockhash" : "235695194f18e6c16c25fd3198c5f5b037bb93a1c13acc4540707e0c6
e35aeeb",
"flags" : "proof-of-work",
"proofhash" : "00000388904d9c15f1e964a07cb2dce7147951d9eaf0222c6cec31264240a
a92",
"entropybit" : 0,
"modifier" : "efa208cc309911b5",
"modifierchecksum" : "b927616f",
"tx" : [
"5f1f8a6c66a3064f92a648dfb9df3cffd3a2ad00db89c40530c6cac6741f8a30"
]
}
|
|
|
|
Sandor why did you delete your post ? Who is the OVH guy getting all the blocks (92.222.27.45) ?  You know what that is, you gave me the iptables rules. |
|
|
|
Since when did: "Can I have your addnode address?" mean Slimcoin is turning back to 15000?
We are now at block "blocks" : 16384, I dont know where the 400+ blocks came from so they should ALL be discarded. We should hard-fork at block 15942. Everything above that was not created by the network. If dev starts at 16000 instead i'd find it suspicious, UNLESS someone reputable syncs him with a 16k blockchain. I cant because 4 of my databases stopped at block 16003 and 16005 are corrupted. My working database syncs at 15942 Hard fork at block 15934 better, none of the blocks after that were found by the pool, which had 80% of hashrate at that time. Which means that a fork occurred and no one could connect to it and it was being instamined. |
|
|
|
I want to test this, I cannot make any promises, but it probably will not be tomorrow.
Also, I need a node to sync from that is on a blockchain of height >= 16000. Coping the files does not work.
It does not work probably because of the database format. Not sure which berkeleyDB i've got running on my centos boxes. Anyone else synced above 16000 ? bitspender ? EDIT : OK, this is my windows blockchain at 16005, this has to work. http://144.76.30.136/blk0001.zipHe needs a node to sync from, not the actual db files. |
|
|
|
So we lose everything we made after block 16000 even if we were on the right fork?
Yes Ow nice. I lose about 350 coins until now??!!! What a joke this coin. Not a single working exchange, and all my investement after block 16000 gets lost? I'm on the right fork, so why should i lose all my coins then? This sounds like a great plan from 2 forum members to get rich, and make others lose there money... Don't be selfish, it was agreed upon that we will relaunch the coin at block 16000. There is about 5k coins lost in my pool due to this. |
|
|
|
So we lose everything we made after block 16000 even if we were on the right fork?
Yes |
|
|
|
|
Show Posts
