|
I am maintaining this project, just development will be lower and more community based.
Just add -addnode=76.127.202.17 and you should get back on.
|
|
|
|
|
Lately, something 'bigger' has come along and have decided to lower my activity on Slimcoin. I will do compilations and releases, maintain the master seed node for synchronized checkpointing, and review pull requests on github. Apart from that, I only plan on doing small tweaks here and there if necessary. I am not abandoning Slimcoin, I am merely giving the majority of the development up to the community. That does not mean I am gone, I may return to more development here depending on how the future goes.
|
|
|
|
|
When you want to sync, try -addnode=76.127.202.17 first and then if that does not connect, try -connect=76.127.202.17
|
|
|
|
I've noticed several points in time today when consecutive POS blocks led to the blocks getting stuck in some clients. I'm comparing with only blockexperts.com/slm.
79651 - 79653: POW -> POS -> POS: The time difference between these three blocks is almost an hour. It showed that I had 23 orphans.
POW (I mined 79651) -> POS (79652@03:52:35) -> POS(79653@04:41:10) -> POW (I mined 79654@04:41:49)
-> POW (I mined at 03:52:52 -> forked) ... 22 POWs -> *Fork resolved back to the blockexpert's chain. ^
This happened another time: I noticed that blockexperts got stuck at a POS block, but it later resolved towards my chain. I can't remember the block numbers.
Same issue at POW@79776 -> POS -> POS -> POS -> POW (79780).
-> POW (+4 minutes after POS) -> 10 POW orphans -> fork resolved ^
Appears to be happening right now @ 79793. As of now it's 20 minutes since the block expert's client accepted a block, while it appears my client has ignored the POS and is happily going down it's POW chain.
Anything to do with the client #? Blockexperts seem to be a bit behind (v0.3.2.0-alpha vs v0.3.2.0.2-g53d7c33-alpha).
In all these cases, my client rejected the POS despite it being obviously earlier. So I'm guessing the POW score somehow made my client think I'm the winner, and the POS time made the blockexperts think it's the winner?
My client abandoned the POW chain only after another POS block hit in - I'm guessing it is some block score threshold hysteresis?
Since I'm obviously not the only miner around, I assume all other miners also couldn't submit their blocks through?
[edit: 79794, a second POS, brought the network back in line. i don't think this should be the correct behaviour though?]
Thank you for pointing this out. Could you send me your debug.log file in ~/.slimcoin. I would like to see what is causing those orphans after the PoS blocks. |
|
|
|
ErrorFile=C:.... AppData\Roaming\SLIMCoin\db.log All that says is it records all errors in that file. By update I assume you meant download the blockchain. To do that, start the wallet with -connect=76.127.202.17 |
|
|
|
|
The node is back up again. The best blockchain is the same one as the blockchain explorer.
My plans for the future: Slimcoin is a Peercoin fork. I tried to merge it with Novacoin before but Novacoin is too different of a project to be merged at this point. There is a project called Peerunity which is the more maintained and newer version of Peercoin. I will try to merge it into Slimcoin. I will obviously test the newly merged client but hopefully this merging will solve any bugs.
|
|
|
|
|
Do not forget this this coin can also adapt. Whenever I see a place that can make this coin better, I am ready to adapt it to make it better.
|
|
|
|
Will you take off hashharder and slimcoin pool links off of the OP Will do. Also, I have no news from slm.blockquarry. |
|
|
|
|
The general trend is, the more burnt coins active, the smaller the reward. Currently, the burnt coins are remaining at ~200000, so it can be considered a relatively constant reward.
Also, remember that PoB does not guarantee and immediate return of investment. It takes some amount of time.
|
|
|
|
|
For PoB and PoS minting, all you need is the client to be on. For PoS, all you need are some amount of coins in your balance. For PoB, you have to burn some coins. Now, there are over 200000 coins burned, so for you to see some return, you will need to burn quite a bit. For example, burning 1000 coins will get you a 0.5% chance of landing a PoB block in the network. Given the network stabalizes to 1 PoB block every 3 PoW blocks and a PoW block is found at about every 90 seconds, that means about 320 PoB blocks per day. At 0.5%, that gives you 1 to 2 PoB blocks per day.
|
|
|
|
|
I have written to all the pools and will write to them again regarding so.
|
|
|
|
|
There will always be an intrinsic danger for using any type of pool. The safest way to use PoB pools is to send small amounts, amounts that if lost, will not be significant. Once a portion have been decayed, you send more again and keep a steady rate of active burnt coins at a time instead of one big chunk in the beginning.
|
|
|
|
|
Whoever has such exceptions and can compile their client from source, please do so. I have made changes to fix the wallet of such exceptions, it is the latest commit on github. I have never experienced such issues and cannot test if the additions will fix anything. I have tested them to prove they work but am not sure if the exceptions will no longer occur.
|
|
|
|
|
There will always be people mining PoW, yet you are not forced to do so to mine Slimcoins.
|
|
|
|
|
True, but it is explicitly stated in COPYING.
Regardless, the point is understood.
Currently I am working on getting more publicity for Slimcoin. Many exchanges use a voting system to get a currency onto it.
The question is, is voting the best way? Another option would be to write to the exchange personally to attract their attention.
|
|
|
|
|
I restated that license to clarify that I will not be reimbursing any losses as people were complaining about burning too many coins and not seeing an immediate return, etc.
|
|
|
|
|
BTER is back on the correct fork.
|
|
|
|
|
BitcoinFX was kind enough to offer his nodes, once your are done syncing from the main seed node, you could add his nodes also.
addnode=107.181.250.216
addnode=107.181.250.217
|
|
|
|
My system has 16 gigs of RAM so that is definitely not the cause unless your wallet eats 10GB+.
Also with -maxconnections=1 -connect=76.127.202.17 it says "0 active connections". If I start without it I don't get any balance and it crashes.
Try without the maxconnections to try to connect. As for the crashing, could you start the wallet with the -debug flag, let it crash and then send me the debug.log file found in the ~/.slimcoin/ directory so I can diagnose the bug. Thanks. |
|
|
|
There was a large shortage of GPUs and ASICs for mining the SHA256 and Scrypt coins. That disabled many people who wanted to mine such coins, but could get any hardware, simply because of its shortage. As a result, a new cryptocurrency Slimcoin was created which allowed anyone to mine it, without needing powerful hardware. Such is achieved by a new block generation, Proof of Burn. In Proof of Burn, powerful computers offer no advantage over less powerful ones. Official Website: slimcoin.orgOfficial Thread: https://bitcointalk.org/index.php?topic=613213.0Link to Whitepaper: https://slimcoin.org/images/downloads/slimcoin_whitepaper.pdf |
|
|
|
|
Show Posts
