Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 24. (Read 284948 times)
September 26, 2014, 03:46:00 PM
he didn't leave, he said he will keep it alive, but won't do new improvements for the time being. hoping others will take over.
September 26, 2014, 05:06:21 AM
what this coin need is to be added to poloniex or bittrex
Poloniex would be the best bet. They latch on to innovation, but SLIM has no volume...
The dev has left. No one with skill will step up ? People don't buy because the wallet is buggy and the dev is nowhere to find.
September 25, 2014, 09:27:39 PM
what this coin need is to be added to poloniex or bittrex
Poloniex would be the best bet. They latch on to innovation, but SLIM has no volume...
September 24, 2014, 03:08:22 PM
what this coin need is to be added to poloniex or bittrex
September 23, 2014, 04:21:19 AM
, TWC supports Slim? Prepare for panic buy 
PS: I'm only joking. We need a dev to stabilize the coin first. If the old dev lefts, anyone with experience in core function will step up as lead dev? I think we need to remove PoS, the source of all errors.
September 22, 2014, 11:39:48 PM
this was my blockchain from 6 sep, syncs great when you place that one in your %appdata%
https://mega.co.nz/#!mQYxlCoQ!fQqJbRCe9CGHLrOkYCrUpwBoxyhzfIEbk1ULf-Qy30c
i could make a new one, but going to bed first lol
https://mega.co.nz/#!mQYxlCoQ!fQqJbRCe9CGHLrOkYCrUpwBoxyhzfIEbk1ULf-Qy30c
i could make a new one, but going to bed first lol
That worked, thanks!
Let's see how long it takes for this to crash.
Abandoned project much?
Price on BTER basically went down to 0. Only very few bids around.
September 22, 2014, 07:01:02 PM
Just wondering if I've strayed onto a seperate fork from you guys...
slimcoind getblockhash 103534
0000001587615ea9a0ce6c3cfcd3549d701dc167d68c8187cd939c2d6909bae3
slimcoind getblockhash 103534
0000001587615ea9a0ce6c3cfcd3549d701dc167d68c8187cd939c2d6909bae3
September 22, 2014, 06:48:24 PM
this was my blockchain from 6 sep, syncs great when you place that one in your %appdata%
https://mega.co.nz/#!mQYxlCoQ!fQqJbRCe9CGHLrOkYCrUpwBoxyhzfIEbk1ULf-Qy30c
i could make a new one, but going to bed first lol
https://mega.co.nz/#!mQYxlCoQ!fQqJbRCe9CGHLrOkYCrUpwBoxyhzfIEbk1ULf-Qy30c
i could make a new one, but going to bed first lol
September 22, 2014, 06:26:16 PM
Thank you.
It just crashed again using yours @pantheist.
I'll remove the blockchain and try with @rfcdejong ones again.
Edit: Now I don't get any connection at all. (after deleting the blockchain and using @rfcdejongs config) What is wrong with this coin?
It just crashed again using yours @pantheist.
I'll remove the blockchain and try with @rfcdejong ones again.
Edit: Now I don't get any connection at all. (after deleting the blockchain and using @rfcdejongs config) What is wrong with this coin?
heh yeah... I thought I was on to something, but I was just coming back to say I jinxed it apparently- crashed right after I posted
September 22, 2014, 06:13:48 PM
Thank you.
It just crashed again using yours @pantheist.
I'll remove the blockchain and try with @rfcdejong ones again.
Edit: Now I don't get any connection at all. (after deleting the blockchain and using @rfcdejongs config) What is wrong with this coin?
It just crashed again using yours @pantheist.
I'll remove the blockchain and try with @rfcdejong ones again.
Edit: Now I don't get any connection at all. (after deleting the blockchain and using @rfcdejongs config) What is wrong with this coin?
September 22, 2014, 06:04:06 PM
@rfcdejong
Could you please post your .conf?
Using
it crashes after a few minutes again.
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
but the node seems to be down, if I start like this I never get a connection.
Could you please post your .conf?
Using
Code:
listen=0
maxconnections=8
addnode=76.127.202.17
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
Code:
-maxconnections=1 -connect=76.127.202.17
i use
Code:
rpcallowip=127.0.0.1
rpcallowip=192.168.2.*
server=1
daemon=1
listen=0
addnode=76.127.202.17:41680
addnode=76.127.202.17
addnode=96.237.174.192
but i also have a backup zip which i had to use since i crashed as well
crashing seems to happen when a long fork is part of your blockchain, a bit of a corrupted blockchain... i'm running the wallet stable for days again, not a single crash
September 22, 2014, 05:49:05 PM
@rfcdejong
Could you please post your .conf?
Using
it crashes after a few minutes again.
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
but the node seems to be down, if I start like this I never get a connection.
Could you please post your .conf?
Using
Code:
listen=0
maxconnections=8
addnode=76.127.202.17
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
Code:
-maxconnections=1 -connect=76.127.202.17
I definitely know less than most people here (and I'm not sure if my max orphan block thing actually does anything), but I've been stable for a couple days so far (I was crashing every 15 minutes to few hours before) with this:
MAX_ORPHAN_BLOCKS=200
addnode=76.127.202.17
addnode=144.76.139.111
addnode=23.92.86.148
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
September 22, 2014, 05:41:17 PM
@rfcdejong
Could you please post your .conf?
Using
it crashes after a few minutes again.
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
but the node seems to be down, if I start like this I never get a connection.
Could you please post your .conf?
Using
Code:
listen=0
maxconnections=8
addnode=76.127.202.17
I have a few k burned as well and don't get any because it's crashing all the time.
It was more stable with
Code:
-maxconnections=1 -connect=76.127.202.17
September 22, 2014, 02:17:25 PM
i'm still burning all i mine, with 4895.178461 effective burned i'm nearing 2% of the total amount burned.
Mining between 70-100 coins a day
The difficulty is low, and we passed the 100K blocks!

{
"blocks" : 103344,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.04295408,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 872,
"networkghps" : 0.00166204,
"pooledtx" : 1,
"testnet" : false
}
"Formatted nEffectiveBurnCoins" : "270490.447845"
4895.178461 coins burned
(4895.178461 / 270490) * 100 = 1.8097 % of the network
Mining between 70-100 coins a day
The difficulty is low, and we passed the 100K blocks!

{
"blocks" : 103344,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.04295408,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 872,
"networkghps" : 0.00166204,
"pooledtx" : 1,
"testnet" : false
}
"Formatted nEffectiveBurnCoins" : "270490.447845"
4895.178461 coins burned
(4895.178461 / 270490) * 100 = 1.8097 % of the network
September 20, 2014, 01:19:58 AM
So what's really driving me crazy is when I only had a few coins burned my wallet was stable 24/7, then, as soon as I burned a bunch more it won't even stay open for more than a couple hours at most. Any theories on why that would be?
try to set listen=0 which worked for me
Seems to have worked (fingers crossed)-thanks! I did it at the same time as setting the affinity to 1 (no real logical reason, just figured it helps with some unstable programs and why not since I'm on a laptop so even if I ever mine I just use one core to keep the temps low) deleted a bunch of nodes from my config file, and added a line to config lowering orphan blocks (I think..)... Been running around 12 hours, stays stable I'll probably go through and undo the changes one at a time to see what's necessary for a lower ram computer
I've been hovering right around 300-310 MB, which seems much more reasonable for a wallet
September 19, 2014, 06:36:21 PM
So what's really driving me crazy is when I only had a few coins burned my wallet was stable 24/7, then, as soon as I burned a bunch more it won't even stay open for more than a couple hours at most. Any theories on why that would be?
try to set listen=0 which worked for me
That does actually seem to help rfcdejong ! Still need > 4 GB of RAM to be stable with the current release on windows though it would seem.
Using a simple .conf excluding server and daemon options is best for now:
Code:
listen=0
maxconnections=8
addnode=76.127.202.17
Lets burn some blocks ! PoW difficulty is also fairly low.
September 19, 2014, 03:32:00 PM
So what's really driving me crazy is when I only had a few coins burned my wallet was stable 24/7, then, as soon as I burned a bunch more it won't even stay open for more than a couple hours at most. Any theories on why that would be?
try to set listen=0 which worked for me
September 19, 2014, 09:41:24 AM
So what's really driving me crazy is when I only had a few coins burned my wallet was stable 24/7, then, as soon as I burned a bunch more it won't even stay open for more than a couple hours at most. Any theories on why that would be?
September 18, 2014, 05:15:58 AM
I have not been able to get SLIMcoins (purchased from Bter) transferred to my wallet for more than 4 days. I was told by Bter exchange that it was due to 'network' issues although my wallet has been synced well. Maybe there are multiple forks going on? I need these coins to test PoB. .............Maybe using Banana PI,for example, in the near future.
The PoB concept and ability to mine with a slimmed down/primitive/no-frill computer are otherwise pretty much intriguing. It would be a shame to see the basic wallet issues are hampering mining and coin transfer as well as probably the ultimate prosperity of this crypto.
The PoB concept and ability to mine with a slimmed down/primitive/no-frill computer are otherwise pretty much intriguing. It would be a shame to see the basic wallet issues are hampering mining and coin transfer as well as probably the ultimate prosperity of this crypto.
It took 3-4 days to get the coins transferred; unclear if it was not completed until Bter brought their wallet up-to-date. Nevertheless, this crypto starts to look quite promising.
Jump to: