Pages:
Author

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

member
Activity: 86
Merit: 10
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"
]
}
member
Activity: 86
Merit: 10
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"
]
}
legendary
Activity: 1092
Merit: 1000
Let me quote one of my chinese friends :

"Slimcoin is the child with no mother."

Hehe, the Bulgarian has abandoned development  Grin

PS. if you are wondering who is on the right fork - its slimcoinpool.com...
member
Activity: 86
Merit: 10
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

sr. member
Activity: 364
Merit: 253
Things seem to be moving.  Grin
legendary
Activity: 2268
Merit: 1092
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.
mbk
member
Activity: 106
Merit: 10
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"
]
}
member
Activity: 86
Merit: 10
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"
]
}
full member
Activity: 156
Merit: 100
Stay in the process of synchronization in 15164
Right blockchain
getblockhash 15164
0000012af65e1e42e8d18d6d8234ecff7a1dd7d972fc34a8a37021576f28b593

Wrong blockchain
getblockhash 15164
000000e5214eba206a93d099fc1cd6f99178e806183af7749eae9601a424e9b7

Thanks d00de!
member
Activity: 86
Merit: 10
Stay in the process of synchronization in 15164
Right blockchain
getblockhash 15164
0000012af65e1e42e8d18d6d8234ecff7a1dd7d972fc34a8a37021576f28b593

Wrong blockchain
getblockhash 15164
000000e5214eba206a93d099fc1cd6f99178e806183af7749eae9601a424e9b7
newbie
Activity: 41
Merit: 0
Is this pool active now?

For anyone interested the Slimcoin pool at https://slm.blockquarry.com is back up and running. We appear to be in sync with the correct block chain at block 59904 which agrees with the block explorer.
full member
Activity: 140
Merit: 100
That is a fucking joke right.
I just bought some more at BTER and withdrew them immediately. They don't show up.
Are they frickin lost?

Because if they are I'll give up on this bullshit... Besides the biggest bullshit of a wallet ever made this coin features forks and forks and forks..
member
Activity: 86
Merit: 10
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"
]
}
member
Activity: 86
Merit: 10
getblockhash 62703
de6c470f108e5f26383f0fedb1bbad9b723fb6176bb5aa2312f1173377e755c5

getblockhash 64430
000000253e3e8b7189d0626200698ea7fbcf18c941c95ca373ba904db3a5229b
member
Activity: 98
Merit: 10
HELP! I've got over 600 coins paid to me in the past few days, but none are showing up in my wallet. I've had the blockchain downloaded for over 12 hours, and still no sign of my coins. How long does it take for the transaction to show up? I'd think it'd be less then 12 hours. Does anyone have any idea how to fix this?

there appears to be no current consensus on which is the valid blockchain, as the admin's nodes and checkpoint nodes appear to be down. you might not be on the correct chain which your 600 slm transaction occurred. wait a couple of day and let the forks resolve first.
member
Activity: 98
Merit: 10
how about block 62703 ?

all have this hash?

getblockhash 62703
de6c470f108e5f26383f0fedb1bbad9b723fb6176bb5aa2312f1173377e755c5



i have this:

getblockhash 62703
de6c470f108e5f26383f0fedb1bbad9b723fb6176bb5aa2312f1173377e755c5
newbie
Activity: 3
Merit: 0
HELP! I've got over 600 coins paid to me in the past few days, but none are showing up in my wallet. I've had the blockchain downloaded for over 12 hours, and still no sign of my coins. How long does it take for the transaction to show up? I'd think it'd be less then 12 hours. Does anyone have any idea how to fix this?
hero member
Activity: 798
Merit: 500
how about block 62703 ?

all have this hash?

getblockhash 62703
de6c470f108e5f26383f0fedb1bbad9b723fb6176bb5aa2312f1173377e755c5
member
Activity: 98
Merit: 10
getblockhash 63204
6520b565111078281bce8c574b49182765d27ddb299a9ad2ae0e6fd784687a09

getblockhash 63204
0000000439239c957deb709b3ef6040986c1b1a9af8d9a8460efe94c9b4c819e

Sad

I've been mining via slimminer and the client for about 3 days, with not a single block found. Looks like even if I did find a block I may be wasting my time. I think I'll shut down the client until the forks are resolved.

getblockhash 63204
0000000439239c957deb709b3ef6040986c1b1a9af8d9a8460efe94c9b4c819e

perhaps we should share our node ips? i don't mind how the forks resolve as long as they do. i'm on 192.3.21.71, currently at block 63693, diff 0.00539.
Pages:
Jump to: