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

[rfcdejong]

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-

I haven't invested into slimcoin beside some cpu power, i sold some and got half a BTC in the start, so all in here is just fun.

Aside from slimcoin i have 14 yr professional programming experience before that i was into hardware, when mainboards were all jumper based. Commodore 64 as a hobby with tapes (i didn't even had a 5 1/4 floppy). My first PC was a 286 with msdos 5 (i don't call an amiga a PC) and my 2nd a 386 with windows 3.11. My 486 dx4 was expensive! 100 mhz! wow I worked with pentium 1 60 and 90 using all those jumpers driving me insane and from there on it went fast until pentium 4 where i switched to software. Anyway, fun is all i want. Got my investment mostly in monero, xc and sync.

We are all idiots gambling, some idiots get rich others are less rich.. but noone in here is poor unless he rented money and bought bitcoins when they were worth 1200 dollar... or poor when he had all his bitcoins on mtGox...

[rfcdejong]

Anyway i got something better to do, if you can answer it i won't call you an idiot either:

Not being a frontend guy, i need to do something in it

i need to to override jQuery widget options (i will not adjust the original .js file)

[mbk]

The chain is at block 65525 with 3Mhs of hash power. To choose it: -connect=54.191.247.114. 


Code:

{
"blocks" : 65525,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.05411402,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00297972,
"pooledtx" : 0,
"testnet" : false
}

[m5j0r]

How about the real devs fix this?

[SpeedDemon13]

New nodes(updating):

Code:

addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682

The chain is at block 65525 with 3Mhs of hash power. To choose it: -connect=54.191.247.114.  


Code:

{
"blocks" : 65525,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.05411402,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00297972,
"pooledtx" : 0,
"testnet" : false
}

Does that addnode work with the one's ynyjl posted or on it's own?

The wallet seems to crash once in a while.

[almightyruler]

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....

Don't panic.

If bter are on what becomes the "main" chain, and you're on another fork, you'll see your funds once you're synced to the main chain.

If it's bter that is on the "wrong" chain, then once they get back onto the correct chain the transaction to you will be orphaned, and should be automatically resent. If that doesn't happen, they will be able to recover the funds manually (rescan or repairwallet), so they can send again.

Given the current confusion about which chain is right I'd sit back for a bit and wait for things to resolve themselves. I'm surprised bter still have deposits enabled.

[SpeedDemon13]

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....

Don't panic.

If bter are on what becomes the "main" chain, and you're on another fork, you'll see your funds once you're synced to the main chain.

If it's bter that is on the "wrong" chain, then once they get back onto the correct chain the transaction to you will be orphaned, and should be automatically resent. If that doesn't happen, they will be able to recover the funds manually (rescan or repairwallet), so they can send again.

Given the current confusion about which chain is right I'd sit back for a bit and wait for things to resolve themselves. I'm surprised bter still have deposits enabled.

What's the right node(s) for the main chain? I'm stuck at 64320 after syncing for a while and others are syncing on 65000 and above.

Which pool is on the right chain?

[ynyjl]

New nodes(updating):

Code:

addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682

The chain is at block 65525 with 3Mhs of hash power. To choose it: -connect=54.191.247.114.  


Code:

{
"blocks" : 65525,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.05411402,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00297972,
"pooledtx" : 0,
"testnet" : false
}

Does that addnode work with the one's ynyjl posted or on it's own?

The wallet seems to crash once in a while.

I don't mining, I'm just trying to safeguard it.
Node 154.191.247.114 is not stable

[almightyruler]

What's the right node(s) for the main chain? I'm stuck at 64320 after syncing for a while and others are syncing on 65000 and above.

See my earlier reply about height versus trust. The chain with the highest block number may not actually have the highest trust. If you choose a chain with lower trust, once your client becomes aware of a better chain it may change to that one.

I don't know if there's a way to see trust from within the client, but you can find it by searching the debug log for the height number. For example, to search for block 63264, search for height=63264

SetBestChain: new best=00000002effa853469ad  height=63264  trust=101388624495  moneysupply=569991.408021 nEffectiveBurnCoins=200663.689991

[bitcoinkkk]

11:49:27

getblockcount


11:49:27

65688


11:52:18

getcheckpoint



11:52:18

{
"synccheckpoint" : "0000000f4b51b2dc9b43369bf66808f07e74dbcc3154cf3ccd9fb94e2121d37f",
"height" : 9600,
"timestamp" : "2014-06-08 15:34:42 UTC"
}

[almightyruler]

11:52:18

{
"synccheckpoint" : "0000000f4b51b2dc9b43369bf66808f07e74dbcc3154cf3ccd9fb94e2121d37f",
"height" : 9600,
"timestamp" : "2014-06-08 15:34:42 UTC"
}

There are actually hardened checkpoints in the source code (checkpoints.cpp) well past that. I think it's a bug with the checkpointing code; I've seen other coins get stuck on older hardened checkpoints too. ('getcheckpoint' returns the genesis block 0 for me!)

Code:

    ( 0, hashGenesisBlockOfficial )
    ( 9012,   uint256("0x00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246"))
    ( 9013,   uint256("0x000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee"))
    ( 9201,   uint256("0x0000000ab86098c475566cf8f494d131c4d17aa18a26e946f6b6143be4989d43"))
    ( 9401,   uint256("0x0000000538be9059aa111cdee43d7f6c5c4e6581073af1f4478a8705f5817f3b"))
    ( 10198,  uint256("0x000000086631340ce44f7ee72e7125654eef62181a08bacf69b42f797fd7bb4c"))
    ( 10503,  uint256("0x1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5"))
    ( 15165,  uint256("0x0000017fba5ef709509c7380e3e128a69a5ab3c60b526c8345aff592dc8d8f81"))
    ( 15935,  uint256("0xaf377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5"))
    ( 15936,  uint256("0x0000002a4ba8fac73286a3cbcac76610a11f3faebec4ce19c13aca30990684f4"))
    ( 35587,  uint256("0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155"))
    ( 43685,  uint256("0xa91550beeed702374a01bd8999669cc9dc6952752f2ede01ef446cb0d2113e6f"))

[SpeedDemon13]

New nodes(updating):

Code:

addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682

The chain is at block 65525 with 3Mhs of hash power. To choose it: -connect=54.191.247.114.  


Code:

{
"blocks" : 65525,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.05411402,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00297972,
"pooledtx" : 0,
"testnet" : false
}

Does that addnode work with the one's ynyjl posted or on it's own?

The wallet seems to crash once in a while.

I don't mining, I'm just trying to safeguard it.
Node 154.191.247.114 is not stable

You got the wrong node I am referring too and I highlighted it in red.

I can't get my wallet to sync to that latest block height and it has a message on the bottom saying; "Checkpoint is too old......"

The wallet needs to be hard coded with the new nodes after the fork issue.

[mbk]

Current state for node 54.191.247.114 (other nodes posted in this thread are on other forks so don't mix them).

Code:

SetBestChain: new best=00000006eff4be409fec  height=65928  trust=105709355121  moneysupply=619565.663472 nEffectiveBurnCoins=200456.503543

{
"blocks" : 65928,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.06259049,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00331882,
"pooledtx" : 0,
"testnet" : false
}

[ynyjl]

These nodes at the same blockchain.

Code:

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

See:
https://bitcointalk.org/index.php?topic=613213.msg8299703#msg8299703
https://bitcointalk.org/index.php?topic=613213.msg8301866#msg8301866

[ynyjl]

The king of the solo?
54.191.247.114

[SpeedDemon13]

These nodes at the same blockchain.

Code:

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

See:
https://bitcointalk.org/index.php?topic=613213.msg8299703#msg8299703
https://bitcointalk.org/index.php?topic=613213.msg8301866#msg8301866

Are these the proper nodes then?
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682
addnode=54.191.247.114

Also, have any of the pools been contacted if they are on the right chain?

[almightyruler]

Guys... you need to do more than use addnode. This only adds the IPs to the peer list, so the client will probably connect to them, but it doesn't limit the client connecting to other peers (or other peers connecting to you)

The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:

connect=54.191.247.114
listen=0

Or on the commandline:

slimcoin-qt.exe -connect=54.191.247.114 -listen=0

(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)

Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.

[SpeedDemon13]

Guys... you need to do more than use addnode. This only adds the IPs to the peer list, so the client will probably connect to them, but it doesn't limit the client connecting to other peers (or other peers connecting to you)

The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:

connect=54.191.247.114
listen=0

Or on the commandline:

slimcoin-qt.exe -connect=54.191.247.114 -listen=0

(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)

Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.

That is understood, but which node(s) are the proper ones. Seem like nodes are just being thrown around without any form of validity.

[primer-]

Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.

You will need to fix the block propagation issue first. Good luck!

[mbk]

I checked the nodes posted above:
54.191.247.114 is at 66270

Code:

SetBestChain: new best=60133ce7ffbf9f49b6f6  height=66270  trust=112643180633  moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924

69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.

If you know other forks at similar height and trust value - post their nodes.