[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!

[mumus]

DNS Seeder is up : dnsseed.slimcoinpool.com

I was also planning to open a dns seeder. Got to the point of having a serer online and compiling the seeder from https://github.com/pooler/litecoin-seeder
Could you please help me with the configuration?
Thanks.

Look here : https://github.com/pooler/litecoin-seeder/commit/3c64ed5ab35f597480712818a27d442100332719
Make the same changes for Slimcoin, change the default port (41682, 41683 = testnet) , pchMessageStart ({ 0xfb, 0xc0, 0xb6, 0xdb }), change REQUIRE_VERSION to 60002. Then add a bunch of node IPs to mainnet_seeds

Thank you very much. Now it's bedtime here so i'll have it online tomorrow morning.

[slimcoin]

It is great to see some DNS seeds. I'll add it into the source code along with the next update fixed.

I am still undecided as to whether relaunch at block 15935 or 16000. It appears there has been a fork there between the nodes. It would be the fairest to go back to block 15935, but I would love input from the rest of the community on this.

[primer-]

WHEN is the relaunch ? Which wallet bugs have you fixed ?

[rfcdejong]

It is great to see some DNS seeds. I'll add it into the source code along with the next update fixed.

I am still undecided as to whether relaunch at block 15935 or 16000. It appears there has been a fork there between the nodes. It would be the fairest to go back to block 15935, but I would love input from the rest of the community on this.

block 15935 or 16000, i don't mind.

ps: Even block 17300 would be good.. i just solo mined 25 blocks in a row for fun, seems syncing works past block 17000 here.. even with this low diff

j/k about 17300 ofcourse, just take 15935 if you feel good about it and it's the most fair.

[primer-]

+1 @15935

[lajz99]

+1 @15935

[reflector]

+1 @15935

[ynyjl]

{
"blocks" : 17607,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00028260,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00001202,
"pooledtx" : 0,
"testnet" : false
}


getconnectioncount
8

nodes:
107.170.185.248
50.116.56.210
113.193.10.70
207.204.73.130
82.114.69.2
54.209.220.225
85.25.195.74
146.185.168.142
92.222.27.45
162.220.242.52
37.128.134.156
46.114.154.159
178.76.206.182
185.21.190.173


getblockhash 15165
0000017fba5ef709509c7380e3e128a69a5ab3c60b526c8345aff592dc8d8f81

getblockhash 15934
0000003144e8cfc1e1a937978dccb1146abc0d0aba1afeb7fbfe8dc9fd71af8c

getblockhash 15935
af377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5

getblockhash 16000
00000388904d9c15f1e964a07cb2dce7147951d9eaf0222c6cec31264240aa92

getblockhash 17607
00000185419eaf9ff123b90dff85481e874562d77d468173c760fa31b1d5144d

[ordeath]

It is great to see some DNS seeds. I'll add it into the source code along with the next update fixed.

I am still undecided as to whether relaunch at block 15935 or 16000. It appears there has been a fork there between the nodes. It would be the fairest to go back to block 15935, but I would love input from the rest of the community on this.

+ 1 @15935

[sp00lin9]

+1 for 15935

[slimcoin]

I am not sure on a date yet, I am syncing up nodes and testing.

[ynyjl]

I want to join the test. Is that ok?

fork @ 10503

getblockhash 10502
00000000705fe8f3464c0a084293f34b15a5c4e3ccd89698f4c5ed67abf67f71
long fork:
getblockhash 10503
1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5
short fork:
getblockhash 10503
00000005282d6cd51df51c0f79352fd7f9e8f023fdabd8b777c14eaa007b00bf

getblock 1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5
{
"hash" : "1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5",
"size" : 2935,
"height" : 10503,
"version" : 1,
"merkleroot" : "a3a2d9fa9e33c635e8c2b4637e3808b93c2220280df05d7547440ec1fb52ccca",
"time" : "2014-06-09 12:03:03 UTC",
"nonce" : 0,
"bits" : "1d08b5ee",
"difficulty" : 0.11480007,
"mint" : 20.24000000,
"previousblockhash" : "00000000705fe8f3464c0a084293f34b15a5c4e3ccd89698f4c5ed67abf67f71",
"nextblockhash" : "000000062f78e9592a9d8d210de017f9a3bfe3a6cf186acd87987ed9a949a0e5",
"flags" : "proof-of-work",
"proofhash" : "1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5",
"entropybit" : 0,
"modifier" : "4bdbe7c21799257f",
"modifierchecksum" : "63bf4377",
"tx" : [
"6921c20c853e32fd9abe0c42811047fad4e83a5c79986f6a135d37ddc9ca4db5",
"ba00c58ecd99662aaf58b87eafa8b853768896f7b367c4d1647752a6e9dbe142"
]
}

getblock 00000005282d6cd51df51c0f79352fd7f9e8f023fdabd8b777c14eaa007b00bf
{
"hash" : "00000005282d6cd51df51c0f79352fd7f9e8f023fdabd8b777c14eaa007b00bf",
"size" : 3247,
"height" : 10503,
"version" : 1,
"merkleroot" : "166c0d672e60bbdac204f6327a0800f920657cb01b6c645a153b094dfc261c0b",
"time" : "2014-06-09 12:13:20 UTC",
"nonce" : 240258,
"bits" : "1d08b5ee",
"difficulty" : 0.11480007,
"mint" : 10.73000000,
"previousblockhash" : "00000000705fe8f3464c0a084293f34b15a5c4e3ccd89698f4c5ed67abf67f71",
"nextblockhash" : "0000000062c5864b5ae68d16b337b2f9244ad8b832ade852f6865a2039794246",
"flags" : "proof-of-work",
"proofhash" : "00000005282d6cd51df51c0f79352fd7f9e8f023fdabd8b777c14eaa007b00bf",
"entropybit" : 1,
"modifier" : "123e82529f21486e",
"modifierchecksum" : "29af9b21",
"tx" : [
"eb0cd2258d17231eb4213df9e78492dc48e1e8ef8d8127afcd3c333fd27a6242",
"1f1186dd4ea0d292b9f20414532cadb4322ffdee67fbc8e70f1bc2cbbc6d49e5",
"ba00c58ecd99662aaf58b87eafa8b853768896f7b367c4d1647752a6e9dbe142"
]
}

[jadefalke]

+1 for 15935

[wendy5]

the burn mode are interesting,lol

[ynyjl]

I think no matter where to start, as long as the problem solved.

[mumus]

+1 @15935

+1

[sleepdog]

+1 for 15935

[Wirel]

+1 for 15935

[AizenSou]

It seems like everyone votes for block 15935. So we only need to wait for an official date from the dev.

[primer-]

Still no launch date, such incompetence. Set the fucking launch date, next week, next month, whenever, set the date!