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

[freet0pian]

Stay in the process of synchronization in 15164
Right blockchain
getblockhash 15164
0000012af65e1e42e8d18d6d8234ecff7a1dd7d972fc34a8a37021576f28b593

Wrong blockchain
getblockhash 15164
000000e5214eba206a93d099fc1cd6f99178e806183af7749eae9601a424e9b7

Thanks d00de!

[1714891974]

1714891974

[1714891974]

1714891974

[1714891974]

1714891974

[1714891974]

1714891974

[ynyjl]

With "slimcoin-qt.exe -maxconnections=1 -connect=112.113.96.138:41682"
getblockhash 64939
0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957

getblock 0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957
{
"hash" : "0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957",
"size" : 356,
"height" : 64939,
"version" : 1,
"merkleroot" : "61f6ec7c011d5a990f3874e71ea81a74cd7e7bd0fa8e93934fc586a7d048a8e8",
"time" : "2014-08-11 13:51:38 UTC",
"nonce" : 2684537365,
"bits" : "1d468096",
"difficulty" : 0.01418372,
"mint" : 18.11000000,
"previousblockhash" : "6048252aa5ea95140cc0d74d34c1bbc418974fe31435d1c41f00866d32d547b0",
"nextblockhash" : "d14c47e1df7b5acb68c303db774339465397fb5eb79c1041d0cc3115ba561d76",
"flags" : "proof-of-work",
"proofhash" : "0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957",
"entropybit" : 1,
"modifier" : "0c09517780c38b76",
"modifierchecksum" : "941f6e83",
"nEffectiveBurnCoins" : "204231072471",
"Formatted nEffectiveBurnCoins" : "204231.072471",
"nBurnBits" : "1d100927",
"tx" : [
"61f6ec7c011d5a990f3874e71ea81a74cd7e7bd0fa8e93934fc586a7d048a8e8"
]
}

[mbk]

To get the really longest chain delete blk*.dat files and run:

Code:

slimcoin-qt.exe -maxconnections=1 -connect=54.191.247.114

(its AWS instance specially for slimcoin)

To check the blockchain:
getblockhash 65037
000000287fbdc22406e529d414b907e916d96638b4a014e6fc395999a9a58795

getblock 000000287fbdc22406e529d414b907e916d96638b4a014e6fc395999a9a58795
{
"hash" : "000000287fbdc22406e529d414b907e916d96638b4a014e6fc395999a9a58795",
"size" : 356,
"height" : 65037,
"version" : 1,
"merkleroot" : "76f4334abe0515aecf6cb092be8e18cf5658bd6445d5d575df08b2b4cb347644",
"time" : "2014-08-11 15:13:02 UTC",
"nonce" : 31269615,
"bits" : "1d35efab",
"difficulty" : 0.01854014,
"mint" : 16.93000000,
"previousblockhash" : "6e68f21344fe56351c6a0671f4354a6bcdae3a65eed55165360218e303f7c0ef",
"flags" : "proof-of-work",
"proofhash" : "000000287fbdc22406e529d414b907e916d96638b4a014e6fc395999a9a58795",
"entropybit" : 0,
"modifier" : "a9de1e5186def09b",
"modifierchecksum" : "e7554862",
"nEffectiveBurnCoins" : "200654211960",
"Formatted nEffectiveBurnCoins" : "200654.21196",
"nBurnBits" : "1d0cf22d",
"tx" : [
"76f4334abe0515aecf6cb092be8e18cf5658bd6445d5d575df08b2b4cb347644"
]
}

With "slimcoin-qt.exe -maxconnections=1 -connect=112.113.96.138:41682"
getblockhash 64939
0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957

getblock 0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957
{
"hash" : "0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957",
"size" : 356,
"height" : 64939,
"version" : 1,
"merkleroot" : "61f6ec7c011d5a990f3874e71ea81a74cd7e7bd0fa8e93934fc586a7d048a8e8",
"time" : "2014-08-11 13:51:38 UTC",
"nonce" : 2684537365,
"bits" : "1d468096",
"difficulty" : 0.01418372,
"mint" : 18.11000000,
"previousblockhash" : "6048252aa5ea95140cc0d74d34c1bbc418974fe31435d1c41f00866d32d547b0",
"nextblockhash" : "d14c47e1df7b5acb68c303db774339465397fb5eb79c1041d0cc3115ba561d76",
"flags" : "proof-of-work",
"proofhash" : "0000002ab49ed6c6bdc0327f500c3e9594ec4caee68acc41a54b90d12c906957",
"entropybit" : 1,
"modifier" : "0c09517780c38b76",
"modifierchecksum" : "941f6e83",
"nEffectiveBurnCoins" : "204231072471",
"Formatted nEffectiveBurnCoins" : "204231.072471",
"nBurnBits" : "1d100927",
"tx" : [
"61f6ec7c011d5a990f3874e71ea81a74cd7e7bd0fa8e93934fc586a7d048a8e8"
]
}

[almightyruler]

To get the really longest chain delete blk*.dat files and run:

Are you considering the "longest" chain to be the one with the greater height? Generally with PoS (and possibly slimcoin PoW - I don't know much about how it works) the important variable is trust, not height.

For example, I just had a quick look at debug.log and a recent PoW block increased trust by 11 million, while a PoS block increased it by 39 million. So a fork with (say) 10 PoW blocks would have a greater height, but a fork with 5 PoS blocks would have greater trust. That one is the longer chain.

[balanghai]

Things seem to be moving. 

[ynyjl]

Everyone is using the latest version?
I think:
There is a conflict between v0.3.1.0 and v0.3.2.0-2
Please update to v0.3.2.0-2 :
https://github.com/slimcoin/slimcoin-executable
resources:
https://github.com/slimcoin/slimcoin-executable/releases

[primer-]

Let me quote one of my chinese friends :

"Slimcoin is the child with no mother."

Hehe, the Bulgarian has abandoned development  

PS. if you are wondering who is on the right fork - its slimcoinpool.com...

[ynyjl]

Everyone is using the latest version?
I think:
There is a conflict between v0.3.1.0 and v0.3.2.0-2
Please update to v0.3.2.0-2 :
https://github.com/slimcoin/slimcoin-executable
resources:
https://github.com/slimcoin/slimcoin-executable/releases

getblockhash 65175
000000263001c083e53b9c91bcc8fe798ade0181b2a9741b9e77e47877232eaa
getblock 000000263001c083e53b9c91bcc8fe798ade0181b2a9741b9e77e47877232eaa
{
"hash" : "000000263001c083e53b9c91bcc8fe798ade0181b2a9741b9e77e47877232eaa",
"size" : 355,
"height" : 65175,
"version" : 1,
"merkleroot" : "69d9f2b4f210d22bd031a5bb1b11cfe440322b519965c893e4541e25588ab91b",
"time" : "2014-08-11 18:23:24 UTC",
"nonce" : 3231246873,
"bits" : "1d2c01c3",
"difficulty" : 0.02272337,
"mint" : 16.10000000,
"previousblockhash" : "e99024ccc5d96cf4734188bb07441d5a868bf01ff96dc35390272bfce609bc37",
"nextblockhash" : "8a2ab227541bdef5d0fcddd4e5069cbaacd0f87172a5005d4cb37a4758503701",
"flags" : "proof-of-work",
"proofhash" : "000000263001c083e53b9c91bcc8fe798ade0181b2a9741b9e77e47877232eaa",
"entropybit" : 1,
"modifier" : "12e008710173e428",
"modifierchecksum" : "e3453caf",
"nEffectiveBurnCoins" : "204157084766",
"Formatted nEffectiveBurnCoins" : "204157.084766",
"nBurnBits" : "1d169427",
"tx" : [
"69d9f2b4f210d22bd031a5bb1b11cfe440322b519965c893e4541e25588ab91b"
]
}

[ynyjl]

Synce block:
With"-maxconnections=1 -connect=112.113.96.138:41682"
or "-maxconnections=1 -connect=112.113.96.138:41683"
or "-maxconnections=1 -connect=112.113.96.138:41686"

NOTE:
If your slimcoin version is v0.3.2.0-2，wallet synced with "-maxconnections=1 -connect=112.113.96.138:41682".
With no parameters to restart slimcon client.

Fork long
-maxconnections=1 -connect=178.130.36.81:41682
start slimcoin with"-maxconnections=1 -connect=89.182.63.64:41682"
or"-maxconnections=1 -connect=112.113.96.138:41682"
exp:
slimcoin-qt.exe -maxconnections=1 -connect=89.182.63.64:41682
slimcoind.exe -maxconnections=1 -connect=89.182.63.64:41682
slimcoin-qt.exe -maxconnections=1 -connect=112.113.96.138:41682
slimcoind.exe -maxconnections=1 -connect=112.113.96.138:41682

getblockhash 64686
000000456c02e2a05c4adf444599096d6dad8b06daf9969dc0491596a74d9044

getblock 000000456c02e2a05c4adf444599096d6dad8b06daf9969dc0491596a74d9044
{
"hash" : "000000456c02e2a05c4adf444599096d6dad8b06daf9969dc0491596a74d9044",
"size" : 355,
"height" : 64686,
"version" : 1,
"merkleroot" : "b16900e7fe952422f0d5c6ab185c3adfb3e0f5000ec54592b6068d56b9cba380",
"time" : "2014-08-11 08:26:25 UTC",
"nonce" : 378118674,
"bits" : "1d5ff92d",
"difficulty" : 0.01041940,
"mint" : 19.56000000,
"previousblockhash" : "0000003e3d4814c870ab5156425193d3f8880fb977e024037b778cffa05ac3c2",
"flags" : "proof-of-work",
"proofhash" : "000000456c02e2a05c4adf444599096d6dad8b06daf9969dc0491596a74d9044",
"entropybit" : 0,
"modifier" : "5b4411ecc78e77d1",
"modifierchecksum" : "1291cdef",
"nEffectiveBurnCoins" : "200669533214",
"Formatted nEffectiveBurnCoins" : "200669.533214",
"nBurnBits" : "1e05a5b5",
"tx" : [
"b16900e7fe952422f0d5c6ab185c3adfb3e0f5000ec54592b6068d56b9cba380"
]
}

[m5j0r]

It all did not help. Downloaded the whole fucking thing a few times syncing with these commands to no avail.

The SLM I bought on Bter are gone. Lost in the depths of some fork.

Bter doesn't give a fuck obviously. Is there any way for the devs to reimburse me? I have proof that Bter sent the transaction to my address, but they are obviously not on the latest fork....

[ynyjl]

It all did not help. Downloaded the whole fucking thing a few times syncing with these commands to no avail.

The SLM I bought on Bter are gone. Lost in the depths of some fork.

Bter doesn't give a fuck obviously. Is there any way for the devs to reimburse me? I have proof that Bter sent the transaction to my address, but they are obviously not on the latest fork....

Contact bter customer service.

[primer-]

It all did not help. Downloaded the whole fucking thing a few times syncing with these commands to no avail.

The SLM I bought on Bter are gone. Lost in the depths of some fork.

Bter doesn't give a fuck obviously. Is there any way for the devs to reimburse me? I have proof that Bter sent the transaction to my address, but they are obviously not on the latest fork....

Contact bter customer service.

Sure, that will help     

Such idiots ))

[rfcdejong]

It all did not help. Downloaded the whole fucking thing a few times syncing with these commands to no avail.

The SLM I bought on Bter are gone. Lost in the depths of some fork.

Bter doesn't give a fuck obviously. Is there any way for the devs to reimburse me? I have proof that Bter sent the transaction to my address, but they are obviously not on the latest fork....

Contact bter customer service.

If bter rollback the blockchain they never send slimcoin in the first place and they have the coins back. It will be a problem if they didn't lock the wallet and people successfully deposited slimcoin...
but then again, not if a old blockchain is choosen to continue on...

[primer-]

Its OVER you idiots, the coin is DEAD!!




RIP slimcoin

RIP Bulgaria

[ynyjl]

New nodes(updating):

Code:

addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686

-maxconnections=1 -connect=112.113.96.138:41682
-maxconnections=1 -connect=112.113.96.138:41683
-maxconnections=1 -connect=112.113.96.138:41686
-maxconnections=1 -connect=54.191.247.114

[rfcdejong]

New nodes(updating):

Code:

addnode=89.182.170.221:41682
addnode=69.172.231.56:41682

That fork is FAR, at block 65314 now, i fully sycned my wallet with it..

23:36:00
getmininginfo

23:36:01
{
"blocks" : 65314,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.02672901,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00104364,
"pooledtx" : 1,
"testnet" : false
}


23:37:12
getblockhash 65314

23:37:12
00000015a2750ec9c395b837f9567d60ebcb1206b7aad8c99ee74f16f6d9fb59

[primer-]

You guys are pathetic )

[rfcdejong]

You guys are pathetic )

come on, remove your alert

[primer-]

You guys are pathetic )

come on, remove your alert

Haha, its too funny. You should represent the more intelligent population, if what you wrote on page 1/2 is true (programmer with 10yr experience). You are trying to revive a dead cat. Not surprised about other idiots in this thread but you ?! Damn, believe no one in the crypto, -such lies-

[ynyjl]

All pool is not on the correct blockchain.