Slimcoin | First Proof of Burn currency | Decentralized Web

[gavrilo77]

Not sure what I'm doing wrong beside using OSX but I don't seem to get anything from mining or staking or burning and it's been more than a week of being in sync and left on and open (and kept reserve balance at 0).

Any idea how I can find out what's going on with it?

What version do you use? I've got 0.5, works fine. I didn't try burning but staking works.

Think I'm using 0.5
SLMv0.5.0-3-g43621dd-dirty-alpha

Yeah, same as mine. I didn't do anything special, just set reserved balance to zero and it started staking. In the first hours I already got some coins.

goddd not idea what Im doing wrong, been staking for long time and I get nothing.... Should I dl a new wallet or something?

When i want to stake i put in console: reservebalance true 1

Tried that as well... Starting to think it's an issue with the wallet config for OSX. The only errors I get is that I cannot connect to some nodes but still have 5 connections anyway. If no one can offer any solution I think I'll download the wallet again and see if it works, if not then I'll assume it doesn't work for OSX lol...

My wallet started staking after 7-9 days

[IThoughtIKnewItAll]

Dev here, still need help on fixing the most annoying bugs of the client ?

[PondSea]

Is there a OTC thread?

[muf18]

There is old OTC topic inactive at the moment.
I would like to buy some SLM too, though I didn't find any seller apart from exchange on nova

[d5000]

Dev here, still need help on fixing the most annoying bugs of the client ?

Hi! Some of the bugs mentioned in the OP have probably already been solved in version 0.5 which we are testing now.
The "Linux client getting stuck" bug is very probably fixed. I am uncertain if the bug that makes the Windows wallet freeze is still present. Perhaps a Windows user can confirm - or was this problem also related to the PoS memory usage problem we all (should) know now?

There is old OTC topic inactive at the moment.
I would like to buy some SLM too, though I didn't find any seller apart from exchange on nova

What do you think about a general "Slimcoin marketplace" thread where you not only could buy and sell SLM but also offer goods and services for it? (I hope that's allowed by forum rules).

[muf18]

Slimcoin marketplace is good idea, but not only as a thread, but also as a website/platform for trading goods with crypto.
I thought for some time for creating something like this, will consider again when I will have access to computer again.

Ok, so as I stated beatcoin probably would include us with their trading exchange, owners seems to be trustworthy, at least as I have seen people on fb, which are engaged in project, and they would probably list us free, if we would help them adding coin.
If we could be listed with fiat currency - that would give some window to world. Even though volume there small now, I think they will start promoting soon, and platform is good, so they could become 2nd or 1st crypto exchange in Poland, which would be like 3-5 milion $ of volume daily.

[drbarber]

Code:

rpcuser=user
rpcpassword=pass
listen=0
server=1
deamon=1
rpcport=41684
splash=0
reservebalance=1000000
addnode=37.187.100.75:41682
addnode=212.243.7.37:57208
addnode=161.53.40.94:54692
addnode=217.175.119.125:35959
addnode=217.65.8.75:34987
addnode=217.65.8.75:27670
addnode=5.9.39.9:41682
addnode=212.74.203.97:21773
addnode=91.20.13.10:56064
addnode=92.193.110.121:48782
addnode=92.193.110.121:40066
addnode=92.193.110.121:51681
addnode=5.105.63.44:64536
addnode=94.25.179.179:53001
addnode=39.128.196.200:2410

Couple questions:
This is the conf file-

Should I replace the nodes with the ones on the first page?

Do I need to change these:
rpcuser=user 
rpcpassword=pass
(What user & pass?)

What do the following do? Should I change them?
listen=0
server=1
deamon=1
rpcport=41684
splash=0

Here's a screenshot of my folder (redownloaded the wallet and noticed it doesn't have the conf file in it:

[psycodad]

@drbarber:
Try removing your current conf file (or better move it to another directory).
Create a new one with only reservebalance=0 in it.
Make sure you have no instance slimcoin daemon running anymore.
Start your wallet again and enjoy staking.

In short: If you do not have more than 1000000 SLM in your wallet, you will not stake with a reservebalance=1000000.
HTH

[gjhiggins]

Couple questions:
This is the conf file-

Do I need to change these:
...
listen=0
...
deamon=1

https://github.com/slimcoin-project/Slimcoin/blob/master/README.md#all-cmmand-line-options


-listen                 Accept connections from outside (default: 1)

-rpcuser=<user>         Username for JSON-RPC connections

-rpcpassword=<pw>       Password for JSON-RPC connections


Hmm. So not “all cmmandline options” ...

./slimcoin-master/src/init.cpp:693:            "  -daemon          \t\t  " + _("Run in the background as a daemon and accept commands") + "\n"

When running the GUI wallet, the -daemon must default to 1 but the slimcoind headless (i.e. non-GUI) client is also capable of acting as a command-line client and this is where -daemon is used to indicate “no, don't sit there with a prompt, waiting for input, holding a terminal session open forever, just get on with it in the background and listen on the RPC port for further instructions.”

According to Stackexchange, the term was coined by MIT folk in the 60s, as a computational analogy to the demon posited by Maxwell in his gas molecule sorting thought experiment. I always thought it was a reference to the demons in Oliver Selfridge's 50's Pandemonium architecture, “one of the first computational models in pattern recognition” but I guess, at the time, MIT weren't into AI.

Example slimcoin.conf

Code:

rpcuser=<anything-you-like->
rpcpassword=<I-usually-use-a-uuid-here>
reservebalance=0 # or 100000000000000 # translates to staking=on / staking=off

That's all you need as a default. If the default assignments for the port (41682) and rpcport (41683) are locally difficult (i.e. the port is already in use by another app), the port=XXX, rpcport=YYY come in handy, defaults are listed in the README linked to (above)

PORT: 41682 RPC_PORT: 41683 TESTNET_PORT: 41684 TESTNET_RPC_PORT: 41685

Cheers

Graham

Edit: added example config

[gjhiggins]

For some odd reason, using a non-standard port will result in the node only ever seeing a subset of the entire network:

I run two mainnet headless clients, one that is lavishly funded and linked against BerkeleyDB 5.3 (non-portable) for the porpoises of instrumenting the internal minting environment and one that is unfunded and linked against “standard” bdb 4.8 to allow for datadir snapshots and for ACME to interrogate.

Unfunded client on default port:

gjh@Ubuntu-1510-wily-64-minimal ~ $ date; ~/bin/slimcoindb48 getinfo; date
Wed Aug  2 11:37:53 CEST 2017
{
    "version" : "SLMv0.5.0-3-g43621dd-dirty-alpha",
    "balance" : 0.00000000,
    "blocks" : 1061697,
    "moneysupply" : 16783227.64363700,
    "connections" : 36,
    "ip" : "144.76.64.49",
    "difficulty" : 0.08819575,
}
Wed Aug  2 11:37:55 CEST 2017

Lavishly-funded client on non-default port:

gjh@Ubuntu-1510-wily-64-minimal ~ $ date; ~/bin/slimcoin getinfo; date
Wed Aug  2 11:38:16 CEST 2017
{
    "version" : "SLMv0.5.0-1-g5d060e9-dirty-alpha",
    "balance" : <non-zero-amount>,
    "blocks" : 1061695,
    "moneysupply" : 16783201.33363700,
    "connections" : 6,
    "proxy" : "",
    "ip" : "144.76.64.49",
    "difficulty" : 0.08941558,
}
Wed Aug  2 11:39:00 CEST 2017

It's the same code (apart from the linked BerkeleyDB binaries), so the difference in number of connections must be due to some infelicity in the code with respect to handling nodes and “non-default” ports.

Note that the funded client is very slow to respond and appears now to be lagging by a few blocks. The output of top suggests why this may be the case:

13441 gjh       20   0 1344492 561640  43520 S 100.9  1.7  23030:04 slimcoind
13422 gjh       20   0 4317964  34148  19876 S  41.0  0.1   5430:41 slimcoind

The funded client is using 100.9% of its allocated thread. The amount of stake calculation is probably dragging at the client's heels and it is gradually falling behind the blockchain.

Cheers

Graham

[psycodad]

@gjhiggins: Maybe its this line in net.cpp that is the culprit for the low connection count on the non-standard port:

https://github.com/slimcoin-project/Slimcoin/blob/slimcoin/src/net.cpp#L1225:

            // do not allow non-default ports, unless after 50 invalid addresses selected already
            if (addr.GetPort() != GetDefaultPort() && nTries < 50)
              continue;

I was actually looking for something in net.cpp that keeps nodes from within the same B-class network connecting to each other (didn't find it) when I found the above.

Cheers - psycodad

[gjhiggins]

@gjhiggins: Maybe its this line in net.cpp that is the culprit for the low connection count on the non-standard port:

Good find.

Apparently a “design feature”, it's still in the latest Bitcoin Core:

https://github.com/bitcoin/bitcoin/blob/master/src/net.cpp#L1819

So that’s one mystery solved. Thank you.

Cheers

Graham

[drbarber]

Thanks @gjhiggins & psycodad.

Is it okay if I leave the user & pass as is? Thought it was for pool info?

Changed the reservebalance to =0 and listen to =1

I tried changing rpcport to =41682 but I don't think my router or ISP allows me to use it (or even 41683 & 41684).
I checked on http://canyouseeme.org/ and came back saying connection timed out.
Do I need this port to work or is it for pools or is there something else I can change it to?

Thanks

[dzarmush]

Why this address sent 5000 Slim almost 10000 times to itself: https://bchain.info/SLM/addr/Sg257jEXmiJJjPS9YTxUXqrMMAFQWvnSFa
Why this address shows error 502: https://bchain.info/SLM/addr/SWGkFvmArmb8pQUYGKpyaQH3LoMyMgWVKk

[psycodad]

Thanks @gjhiggins & psycodad.

Is it okay if I leave the user & pass as is? Thought it was for pool info?

You're welcome, hope it helps you see your first stake block finally.

You should either remove the two rpcuser/-pass lines or set the at least the password to something sensible. AFAIK for running the Qt-Wallet these are not needed, if you want to use the cli interface like in "slimcoind getinfo" in a shell, they need to be present (again, set a good password). I believe by default rpcallowip is restricted to 127.0.0.1 but I don't know for sure, might be a good idea to set it to 127.0.0.1/32 anyway.
The rpc interface is used to query and command the slimcoin daemon over the network from applications like for example a mining pool, exchange or a block explorer.

Changed the reservebalance to =0 and listen to =1

I tried changing rpcport to =41682 but I don't think my router or ISP allows me to use it (or even 41683 & 41684).
I checked on http://canyouseeme.org/ and came back saying connection timed out.
Do I need this port to work or is it for pools or is there something else I can change it to?

You shouldn't set the rpcport at all, which means it will use the default, if you do not have any conflicts on the default port it uses.

HTH - psycodad

[psycodad]

Why this address sent 5000 Slim almost 10000 times to itself: https://bchain.info/SLM/addr/Sg257jEXmiJJjPS9YTxUXqrMMAFQWvnSFa
Why this address shows error 502: https://bchain.info/SLM/addr/SWGkFvmArmb8pQUYGKpyaQH3LoMyMgWVKk

This might be a sign of the coin-control features in the client at work. People often create inputs in a certain size with that feature with the idea/goal of staking faster or more often or both  . The coin age (time your coin sits unspent in your wallet) multiplied by the number of coins in an input give your unspent input a staking weight which is one of the factors that decide if your input is eligible for a PoS of the next block coming.

I am actually not sure if this is looking like this on the blockchain if somebody is reorganizing their inputs for better staking, I hope somebody with better knowledge can confirm this.

Edited to add: The above is regarding the first link, I don't know about the latter.

Cheers - psycodad

[dzarmush]

Why this address sent 5000 Slim almost 10000 times to itself: https://bchain.info/SLM/addr/Sg257jEXmiJJjPS9YTxUXqrMMAFQWvnSFa
Why this address shows error 502: https://bchain.info/SLM/addr/SWGkFvmArmb8pQUYGKpyaQH3LoMyMgWVKk

This might be a sign of the coin-control features in the client at work. People often create inputs in a certain size with that feature with the idea/goal of staking faster or more often or both  . The coin age (time your coin sits unspent in your wallet) multiplied by the number of coins in an input give your unspent input a staking weight which is one of the factors that decide if your input is eligible for a PoS of the next block coming.

I am actually not sure if this is looking like this on the blockchain if somebody is reorganizing their inputs for better staking, I hope somebody with better knowledge can confirm this.

Cheers - psycodad

Hm, interesting.

A few more 502 errors.
https://bchain.info/SLM/addr/SekdrkdiHy6A1RXevM1BoWJxndqT5BvoW6
https://bchain.info/SLM/addr/SZEHwJm2RDspGXpFzbtTgxHRs5jTVJNyM9
https://bchain.info/SLM/addr/SYV4T7oMf32Zn5PXEnp1miRCR13sZ95vnD
https://bchain.info/SLM/addr/STR8B3UCLjEuyyx6NtemNCBpKwCPVxmd3X

[psycodad]

Please note: I was only referring to the first link, I have no clue about the 502 links.

[dzarmush]

Please note: I was only referring to the first link, I have no clue about the 502 links.

I got it, yeah.

[d5000]

Good news regarding a better Coinmarketcap integration: I have found a way how to extract the "circulating supply" from http://slimcoin.club - that is the number that is missing to calculate the correct market cap. There are some hidden URLs that can be spotted if you open the javascript files included in the home page (view source code for that). There seems to be a complete Slimcoin JavaScript frontend there and even a DCrypt "port".

I hope @a123 (creator of slimcoin.club) is not annoyed if I grab the total supply every 5 minutes to provide it to Coinmarketcap (the server load should be minimal). I don't know if he released that Javascript files somewhere or if it's only a "private" implementation for his web site - @a123, if you are reading here, it would be cool if you could open source it ...

I have written a little Python script that collects this number, I could extend and publish it to provide it to CMC in a more accesible way. However, it's so easy to grab that perhaps they can grab it by themselves - I've sent them the link and the method to grab the number. They say they need "up to 7 days" to add/change information, so if in ~2-3 weeks the figures are still not correct, I'll provide them a web service.

@dzarmush: I guess the 502 errors are simply a bug/problem on bchain.info. Yesterday I consulted them several times and they had some load problems.