|
slimcoin (OP)
|
|
September 10, 2014, 09:02:13 PM |
|
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.
|
-Much Donate BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
BitcoinFX
Legendary
Offline
Activity: 2646
Merit: 1721
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
|
|
September 10, 2014, 09:22:37 PM |
|
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.
OK Thanks. Do we have any volunteers ?
|
|
|
|
DOGEbubble
|
|
September 11, 2014, 12:35:31 AM |
|
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.
I set up and synced the wallet yesterday. Today, the wallet forked at 92053. I restarted from the downloaded wallet, syncing all day, forked several times on the way and again forked at 92053, running Conf file with a single -addnode=76.127.202.17 or multiple addnodes makes no difference; and the Roaming files looked different from the previous file (also forked at 92053) renamed for comparison. Did not even have chance to start any thing yet, mining or getting coins and burn-mining etc. It would be pitiful for me to stop at this point. It is easier to do just that. But I would doubt any new comer would do any better, considering that I started to learn programming more then 40 years ago and I have several mining rigs for more than 10 months.
|
|
|
|
DOGEbubble
|
|
September 11, 2014, 12:52:07 PM |
|
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.
I set up and synced the wallet yesterday. Today, the wallet forked at 92053. I restarted from the downloaded wallet, syncing all day, forked several times on the way and again forked at 92053, running Conf file with a single -addnode=76.127.202.17 or multiple addnodes makes no difference; and the Roaming files looked different from the previous file (also forked at 92053) renamed for comparison. Did not even have chance to start any thing yet, mining or getting coins and burn-mining etc. It would be pitiful for me to stop at this point. It is easier to do just that. But I would doubt any new comer would do any better, considering that I started to learn programming more then 40 years ago and I have several mining rigs for more than 10 months. The wallet finally synced overnight. It works now. But it has been quite problematic if any one sees their wallets forked for more than 12 hours with blockchains running more than 200 blocks ahead. Afterward, all the posted info/instructions help very much. Thanks.
|
|
|
|
pantheist
Member
Offline
Activity: 63
Merit: 10
|
|
September 16, 2014, 07:02:29 PM Last edit: September 18, 2014, 08:38:51 PM by pantheist |
|
Got it to stop crashing, but now it's stuck at 93907. Already added in the node slimcoin mentioned.
I think I've had enough with this coin. Glad I only threw in a smallish test investment rather than throwing a lot in at once. If someone else makes a PoB coin (especially if its one or some of the people on this thread who actually know what they're doing) I'll definitely be trying that one out.
edit: nevermind... for whatever reason I spent the time to get it working again. I can't imagine anyone investing real money in this unless it gets some huge improvements and probably a new developer.
edit 2: aaaaand it crashed again. I'm done. For real this time. Probably.
edit 3: got it workin again. Obviously I suck at quitting things. Of course, so do you if you're still reading this comment at this point.
another 1: broken again. I don't think the new code changes anything related to the crashes- even reducing the number of orphan blocks from the 750 default doesn't help
|
|
|
|
DOGEbubble
|
|
September 17, 2014, 07:27:18 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.
|
|
|
|
beitris.dwlul
Member
Offline
Activity: 84
Merit: 10
|
|
September 17, 2014, 03:37:51 PM |
|
I really want to compile a windows binary file cpuminer.
|
|
|
|
vipgelsi
Legendary
Offline
Activity: 1736
Merit: 1001
|
|
September 17, 2014, 03:38:54 PM |
|
Richard Simmons would be really proud of this coin lol
|
|
|
|
DOGEbubble
|
|
September 18, 2014, 10: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.
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.
|
|
|
|
pantheist
Member
Offline
Activity: 63
Merit: 10
|
|
September 19, 2014, 02:41:24 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?
|
|
|
|
rfcdejong
|
|
September 19, 2014, 08: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
|
|
|
|
BitcoinFX
Legendary
Offline
Activity: 2646
Merit: 1721
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
|
|
September 19, 2014, 11: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: listen=0 maxconnections=8 addnode=76.127.202.17
Lets burn some blocks ! PoW difficulty is also fairly low.
|
|
|
|
pantheist
Member
Offline
Activity: 63
Merit: 10
|
|
September 20, 2014, 06:19:58 AM Last edit: September 20, 2014, 06:30:54 AM by pantheist |
|
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
|
|
|
|
rfcdejong
|
|
September 22, 2014, 07: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
|
|
|
|
comerex
Newbie
Offline
Activity: 7
Merit: 0
|
|
September 22, 2014, 10:41:17 PM |
|
@rfcdejong Could you please post your .conf? Using listen=0 maxconnections=8 addnode=76.127.202.17 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 -maxconnections=1 -connect=76.127.202.17 but the node seems to be down, if I start like this I never get a connection.
|
|
|
|
pantheist
Member
Offline
Activity: 63
Merit: 10
|
|
September 22, 2014, 10:49:05 PM |
|
@rfcdejong Could you please post your .conf? Using listen=0 maxconnections=8 addnode=76.127.202.17 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 -maxconnections=1 -connect=76.127.202.17 but the node seems to be down, if I start like this I never get a connection. 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
|
|
|
|
rfcdejong
|
|
September 22, 2014, 11:04:06 PM |
|
@rfcdejong Could you please post your .conf? Using listen=0 maxconnections=8 addnode=76.127.202.17 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 -maxconnections=1 -connect=76.127.202.17 but the node seems to be down, if I start like this I never get a connection. i use 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
|
|
|
|
comerex
Newbie
Offline
Activity: 7
Merit: 0
|
|
September 22, 2014, 11: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?
|
|
|
|
pantheist
Member
Offline
Activity: 63
Merit: 10
|
|
September 22, 2014, 11: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?
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
|
|
|
|
|