Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 91. (Read 284956 times)

~/slicmoin-executable-master$ ./slimcoind getblockhash 15934
0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c

~/slicmoin-executable-master$ ./slimcoind getblockhash 15935
af377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5

im still receiving pool payouts...

[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15934
0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c

No need to be greedy 15000 is when the issues started.

0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c
15935: af377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5

Could people post their

./slimcoind getblockhash 15934

and

./slimcoind getblockhash 15935

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.

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.

Pool was actually shut down around block 16315.

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 ?

Let me re-post again, important :

I'd like to see mumus and other developers go through the source code and make sure no coins were premined by the developer. I'd also like to know if there is a chance the BURN address actually spends coins - if so that should also be addressed in the hard fork.

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"
    ]
}

Ahh

You know what that is, you gave me the iptables rules.

Sandor why did you delete your post ? Who is the OVH guy getting all the blocks (92.222.27.45) ? 

[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15934
0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c


Everything AFTER 15934 is DIFFERENT from my dbase!

[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15935
000000346f9386b3f4b17c7a7d4fa7928650f10479d401fe8313ef24017ef264
[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15936
0000001443ac4a39ab6c047c412fd0ed5909df41aa7af78ed4004135c002ecab
[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15937
0000001bd2f989bee3eecd7e2e4a32da3c45dab19bc78fb37101470bdfda9f43
[root@CentOS-64-64-minimal .slimcoin]# slimcoind getblockhash 15938
0000002f8cb8a98c2812380954c60aa7214e33f5c4b8441fedf83722f0c01fbb


Dev, hard-fork at 15934

I have unpacked the database archive and i'm ready to sync the dev again to block 15942. Dev PM me if you want a clean sync and i will send the new port #

Sandor, can you sync him to 15934 ? I am afraid couple of nodes that connected with the dev overwrote my database. New sync should be performed 1-1, listen=0 on dev side and you sandor change port(port=xxxxx) so no one connects to you.

I told the dev to delete addr.dat and to change his listening port or change listen to 0 so no one connects while he syncs up. He did not. I see around 10 connections to my node now and i am at block     "blocks" : 16395.

I have no idea if the 'network' overwrote blocks below 15942, which could have happened as they had more 'synced nodes'

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.