Slimcoin | First Proof of Burn currency | Decentralized Web

[gjhiggins]

Thank you very much! Very useful.
But is

Code:

listen=1

necessary for the server?

No problem.

Yes, it is necessary.

If you're running a Slimcoin node at home and want it to be a listening client, then you'll need to ensure that your router supports UPNP and that the router is configured to allow incoming connections to the port and ipaddress of your node. UPNP allows your local host to connect via the default Slimcoin port, then you can advertise your ip address as a listening node for addnode inclusion. Do bear in mind that running a listening node at home will impact your upload usage if the size of the network is significant, as other nodes access your node for data which your node then uploads. Overloading your upload channel can nuke your download channel as the upload channel carries sync information for both up- and down-stream and a maxed-out upload channel can bring your download channel to a halt.

Of course "up" and "down" are entirely perceptual. I once used the term "download from" in conversation with a network hardware engineering friend of mine. He cocked an eyebrow and said that he always thought of the net as below him, not above him, so he downloaded to the net and uploaded from it. I thought that was an excellent perception and have followed it ever since.

Cheers

Graham

[johnwhitestar]

Thank you very much! Very useful.
But is

Code:

listen=1

necessary for the server?

No problem.

Yes, it is necessary.

If you're running a Slimcoin node at home and want it to be a listening client, then you'll need to ensure that your router supports UPNP and that the router is configured to allow incoming connections to the port and ipaddress of your node. UPNP allows your local host to connect via the default Slimcoin port, then you can advertise your ip address as a listening node for addnode inclusion. Do bear in mind that running a listening node at home will impact your upload usage if the size of the network is significant, as other nodes access your node for data which your node then uploads. Overloading your upload channel can nuke your download channel as the upload channel carries sync information for both up- and down-stream and a maxed-out upload channel can bring your download channel to a halt.

Of course "up" and "down" are entirely perceptual. I once used the term "download from" in conversation with a network hardware engineering friend of mine. He cocked an eyebrow and said that he always thought of the net as below him, not above him, so he downloaded to the net and uploaded from it. I thought that was an excellent perception and have followed it ever since.

Cheers

Graham

Very interesting, thank you!

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

[gjhiggins]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Cheers

Graham

[gjhiggins]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Edit: I configured my local node to listen=1 and ensured that the router was UPNP-enabled. My incoming IP address is 51.148.146.204 and this is what my restarted (old) server (configured with connect=51.148.146.204) RPC/API getpeerinfo call reports:


"addr" : "185.150.190.19:41682",
"inbound" : false,
"height" : 2364810,

"addr" : "185.68.67.37:41682",
"inbound" : false,
"height" : 109603,

"addr" : "144.76.118.44:41682",
"inbound" : false,
"height" : 2364810,

"addr" : "51.148.146.204:41682",
"inbound" : false,
"height" : 2364810,

"addr" : "178.223.10.23:57705",
"inbound" : true,
"height" : 2364810,

"addr" : "178.223.10.23:63870",
"inbound" : true,
"height" : 2364810,


My local node is now listening.

Cheers

Graham

[psycodad]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Cheers

Graham

I believe listen=1 is assumed when the parameter is missing from the .conf file.
At least it was this way with all the wallets I used (and with slimcoind v5 too I get inbound connections in complete absence of any listen= setting).

Not trying to be a smartass (well maybe a little bit  )

Otherwise my node is still synching, I remember it takes quite some time but I hoped to get more than 300k blocks in 24 hours.

[johnwhitestar]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Cheers

Graham

I believe listen=1 is assumed when the parameter is missing from the .conf file.
At least it was this way with all the wallets I used (and with slimcoind v5 too I get inbound connections in complete absence of any listen= setting).

Not trying to be a smartass (well maybe a little bit  )

Otherwise my node is still synching, I remember it takes quite some time but I hoped to get more than 300k blocks in 24 hours.

You are not using Grahams snapshot, are you?

[psycodad]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Cheers

Graham

I believe listen=1 is assumed when the parameter is missing from the .conf file.
At least it was this way with all the wallets I used (and with slimcoind v5 too I get inbound connections in complete absence of any listen= setting).

Not trying to be a smartass (well maybe a little bit  )

Otherwise my node is still synching, I remember it takes quite some time but I hoped to get more than 300k blocks in 24 hours.

You are not using Grahams snapshot, are you?

No, I am trying to synch from scratch again. While I understand loading the snapshot would make stabilize the network much faster, I want to see my node synched the traditional way. I tried with snapshot on a (much) earlier occasion and ended up synching from the network so I thought I'd go that way again.

[johnwhitestar]

So my idea that by PoBing at home one automatically provides a listening node to the net is completely wrong, right?

Not a listening node unless configured with listen=1 and UPNP-connected via the standard port.

Cheers

Graham

I believe listen=1 is assumed when the parameter is missing from the .conf file.
At least it was this way with all the wallets I used (and with slimcoind v5 too I get inbound connections in complete absence of any listen= setting).

Not trying to be a smartass (well maybe a little bit  )

Otherwise my node is still synching, I remember it takes quite some time but I hoped to get more than 300k blocks in 24 hours.

You are not using Grahams snapshot, are you?

No, I am trying to synch from scratch again. While I understand loading the snapshot would make stabilize the network much faster, I want to see my node synched the traditional way. I tried with snapshot on a (much) earlier occasion and ended up synching from the network so I thought I'd go that way again.

I usually need a couple of weeks to synchronize from scratch.

[gjhiggins]

I believe listen=1 is assumed when the parameter is missing from the .conf file.
At least it was this way with all the wallets I used (and with slimcoind v5 too I get inbound connections in complete absence of any listen= setting).

Not trying to be a smartass (well maybe a little bit  )

I stand corrected, thank you:

https://github.com/slimcoin/slimcoin/blob/afd8ef7e18e17f876f0bc7b44e79ee867f0b3ac1/src/init.cpp#L607

Cheers

Graham

[johnwhitestar]

The deposits on Freiexchange are re-enabled.

[PeterColumboFalk]

My linux host 185.150.190.19 is on block 2365695 now, and so is my home minting wallet on windows. But the 22 connections of my linux host are all back a lot of blocks, why? This is a really nerd project.

Code:

        "addr" : "45.129.56.151:51023",
        "height" : 2362102,
        "addr" : "46.0.192.98:31351",
        "height" : 2362103,
        "addr" : "185.79.5.221:53276",
        "height" : 2363721,
        "addr" : "5.39.70.87:47248",
        "height" : 2362985,
        "addr" : "89.24.32.31:18516",
        "height" : 2277688,
        "addr" : "85.19.25.38:18461",
        "height" : 2360592,
        "addr" : "145.239.189.106:58412",
        "height" : 2364577,
        "addr" : "178.223.10.23:50289",
        "height" : 2364760,
        "addr" : "91.250.62.26:59812",
        "height" : 2364725,
        "addr" : "51.148.146.204:55676",
        "height" : 2364792,
        "addr" : "144.76.64.49:52762",
        "height" : 2364809,
        "addr" : "144.76.118.44:38492",
        "height" : 2364950,
        "addr" : "90.188.3.212:62984",
        "height" : 2363707,
        "addr" : "111.201.49.182:35568",
        "height" : 1758311,
        "addr" : "178.221.183.154:9256",
        "height" : 2364109,
        "addr" : "109.10.108.52:54800",
        "height" : 2365492,
        "addr" : "94.25.172.40:15929",
        "height" : 2364093,
        "addr" : "178.223.10.23:50055",
        "height" : 2365631,
        "addr" : "178.223.10.23:50237",
        "height" : 2365634,
        "addr" : "178.223.10.23:65157",
        "height" : 2365653,
        "addr" : "178.223.10.23:65259",
        "height" : 2359429,
        "addr" : "185.68.67.37:46258",
        "height" : 495577,
        "addr" : "94.25.172.40:33715",
        "height" : 2365678,

[gjhiggins]

But the 22 connections of my linux host are all back a lot of blocks, why? This is a really nerd project.

I found that if you stop and restart the node, the list of peers gets refreshed with updated heights.

Yes, the node is very lazy about updating the heights of the peers, maybe that was a design trade-off at the time.

Cheers

Graham

[PeterColumboFalk]

I will stop my node now, make a fresh backup, and start it again if finished. Will take around 15 minutes. This is the current state, block count is the same as CryptoID has.

Code:

$ ./slimcoind getinfo
{
    "version" : "v0.6.0.0-g8e9fe2c-alpha",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 2365837,
    "moneysupply" : 31394496.99831600,
    "burnt" : 3324521.17335400,
    "connections" : 24,
    "proxy" : "",
    "ip" : "185.150.190.19",
    "difficulty" : 0.03205795,
    "testnet" : false,
    "keypoololdest" : 1606559033,
    "keypoolsize" : 102,
    "paytxfee" : 0.01000000,
    "errors" : ""
}

[PeterColumboFalk]

current blockchain and md5sum checksum:

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-03-01.tgz
ftp://185.150.190.19/README

Full node restarted. Indeed, many connections are near the current block.

Code:

        "addr" : "51.148.146.204:49006",
        "height" : 2365844,
        "addr" : "145.239.189.106:41682",
        "height" : 2365844,
        "addr" : "45.129.56.151:52849",
        "height" : 2365844,
        "addr" : "144.76.64.49:53704",
        "height" : 2365844,
        "addr" : "185.68.67.37:52894",
        "height" : 588587,
        "addr" : "90.188.3.212:62987",
        "height" : 2363707,
        "addr" : "178.223.10.23:57869",
        "height" : 2365845,
        "addr" : "109.10.108.52:53954",
        "height" : 2365846,
        "addr" : "85.19.25.38:31356",
        "height" : 2365846,
        "addr" : "144.76.118.44:55088",
        "height" : 2365847,
        "addr" : "178.221.183.154:9544",
        "height" : 2364109,
        "addr" : "89.24.32.31:18457",
        "height" : 2342772,
        "addr" : "185.79.5.221:58778",
        "height" : 2364086,
        "addr" : "94.25.172.40:32818",
        "height" : 2364093,
        "addr" : "5.39.70.87:47638",
        "height" : 2365847,
        "addr" : "91.250.62.26:58196",
        "height" : 2365847,

[psycodad]

But the 22 connections of my linux host are all back a lot of blocks, why? This is a really nerd project.

I found that if you stop and restart the node, the list of peers gets refreshed with updated heights.

Yes, the node is very lazy about updating the heights of the peers, maybe that was a design trade-off at the time.

Cheers

Graham

I am not sure (and haven't checked in the code), but the height shown at getpeerinfo should probably be labeled "startingheight" as it is in other wallets. This would imply that the height shown is the height the peer node had when a connection was made. I don't think that it is getting updated after initial connection was made.

(A quick test shows that these numbers do not seem to update after connect, though beware I have a talent for being totally wrong..)

[keliokan]

Hello All,

Looks like everything is getting sorted,
My wallet is now on the "good" chain,

Thanks all for your help !!

K.

[johnwhitestar]

Hello All,

Looks like everything is getting sorted,
My wallet is now on the "good" chain,

Thanks all for your help !!

K.

You are welcome! 

[gjhiggins]

the height shown at getpeerinfo should probably be labeled "startingheight"

True, dat: https://github.com/slimcoin-project/Slimcoin/blob/03914e38ab9724d3d1a0d18afff65293a7142e43/src/bitcoinrpc.cpp#L737

Code:

        obj.push_back(Pair("height", stats.nStartingHeight));

Cheers

Graham

[emrgohff]

Hello

I'm starting and trying to understand slimcoin.

I've burned coins and everything is ok

Now I was trying to send coins to the FreiExchange exchange but the following message "Error: Transation Creation Failed" appears.

I don't understand why, is help possible?

* Slimcoin version v0.6.0.0-g8e9fe2c-alpha

* slimcoin.conf
rpcuser=user
rpcpassword=pass
listen=1
server=1
deamon=1
rpcport=41684
splash=1
reservebalance=1000000
maxconnections=127
connect=144.76.118.44
connect=144.76.64.49
connect=185.150.190.19
addnode=109.92.14.98
addnode=178.222.20.152
...
...

Thanks

[johnwhitestar]

Hello

I'm starting and trying to understand slimcoin.

I've burned coins and everything is ok

Now I was trying to send coins to the FreiExchange exchange but the following message "Error: Transation Creation Failed" appears.

I don't understand why, is help possible?

* Slimcoin version v0.6.0.0-g8e9fe2c-alpha

* slimcoin.conf
rpcuser=user
rpcpassword=pass
listen=1
server=1
deamon=1
rpcport=41684
splash=1
reservebalance=1000000
maxconnections=127
connect=144.76.118.44
connect=144.76.64.49
connect=185.150.190.19
addnode=109.92.14.98
addnode=178.222.20.152
...
...

Thanks

Hi emrgohff,
this issue is a bit hard for me to understand so I hope someone more senior will help us.

I've found this conversation about the same message in bitcoin-qt: https://bitcointalk.org/index.php?topic=218447.0
Can it be useful for you?


Edit: Here is a bit late, so I'll be back tomorrow to see what has happened and whether I can go on supporting you.