Slimcoin | First Proof of Burn currency | Decentralized Web - page 6.

PeterColumboFalk

jr. member

Activity: 81

Merit: 5

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" : ""
}

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: PeterColumboFalk on February 28, 2021, 05:45:30 PM

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

jr. member

Activity: 81

Merit: 5

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,

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

The deposits on Freiexchange are re-enabled.

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: psycodad on February 28, 2021, 06:16:04 AM

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 Cheesy

)

I stand corrected, thank you:

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

Cheers

Graham

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: psycodad on February 28, 2021, 06:34:22 AM

Quote from: johnwhitestar on February 28, 2021, 06:27:04 AM

Quote from: psycodad on February 28, 2021, 06:16:04 AM

Quote from: gjhiggins on February 27, 2021, 07:34:45 PM

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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 Cheesy

)

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.

psycodad

legendary

Activity: 1604

Merit: 1564

精神分析的爸

Quote from: johnwhitestar on February 28, 2021, 06:27:04 AM

Quote from: psycodad on February 28, 2021, 06:16:04 AM

Quote from: gjhiggins on February 27, 2021, 07:34:45 PM

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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 Cheesy

)

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

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: psycodad on February 28, 2021, 06:16:04 AM

Quote from: gjhiggins on February 27, 2021, 07:34:45 PM

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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 Cheesy

)

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

legendary

Activity: 1604

Merit: 1564

精神分析的爸

Quote from: gjhiggins on February 27, 2021, 07:34:45 PM

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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 Cheesy

)

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.

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: johnwhitestar on February 27, 2021, 07:17:14 PM

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

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: gjhiggins on February 27, 2021, 07:08:57 PM

Quote from: johnwhitestar on February 27, 2021, 03:52:32 PM

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

legendary

Activity: 2254

Merit: 1278

Quote from: johnwhitestar on February 27, 2021, 03:52:32 PM

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

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: gjhiggins on February 27, 2021, 11:43:19 AM

Quote from: johnwhitestar on February 27, 2021, 03:54:27 AM

But what's not that clear to me. If we have 6 servers online, why is it my local wallet has only 1 connection?

https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery

They'll only show up if you have added them with addnode/connect in the config file and they are listening nodes ..

slimcoin.conf

Code:

maxconnections=127
connect=144.76.118.44
connect=144.76.64.49
connect=185.150.190.19

getpeerinfo (total 3 connections)

Code:

"addr" : "144.76.118.44:41682",
"height" : 2364444,

"addr" : "144.76.64.49:41682",
"height" : 2364444,

"addr" : "185.150.190.19:41682",
"height" : 2364444,

Cheers

Graham

Thank you very much! Very useful.
But is

Code:

listen=1

necessary for the server?

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: johnwhitestar on February 27, 2021, 03:54:27 AM

But what's not that clear to me. If we have 6 servers online, why is it my local wallet has only 1 connection?

https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery

They'll only show up if you have added them with addnode/connect in the config file and they are listening nodes ..

slimcoin.conf

Code:

maxconnections=127
connect=144.76.118.44
connect=144.76.64.49
connect=185.150.190.19

getpeerinfo (total 3 connections)

Code:

"addr" : "144.76.118.44:41682",
"height" : 2364444,

"addr" : "144.76.64.49:41682",
"height" : 2364444,

"addr" : "185.150.190.19:41682",
"height" : 2364444,

Cheers

Graham

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: PeterColumboFalk on February 27, 2021, 07:47:24 AM

Quote from: johnwhitestar on February 27, 2021, 03:54:27 AM

...
But what's not that clear to me. If we have 6 servers online, why is it my local wallet has only 1 connection?

I have this behaviour too. My minting homewallet currently says "3 active connection(s) to Slimcoin network), and command getpeerinfo tells me about two connections at the same time. Yesterday evening I did "addnode 185.150.190.19" to my homewallet, and I wonder why host 185.150.190.19 does not forward some of his 22 connections (maxconnections=64) to my homewallet.

Homewallet is version 0.6.0 on Windows 8.1.

I'm thinking maybe my server's slimcoin.conf misses something. So it's not considered a seeding node at all by the net.
What would be the best slimcoin.conf setup from the point of view of our public usefulness?

By the way we should also have another node of someone who is PoBing, so there should be at least 7 active connections each time.

PeterColumboFalk

jr. member

Activity: 81

Merit: 5

Quote from: johnwhitestar on February 27, 2021, 03:54:27 AM

...
But what's not that clear to me. If we have 6 servers online, why is it my local wallet has only 1 connection?

I have this behaviour too. My minting homewallet currently says "3 active connection(s) to Slimcoin network), and command getpeerinfo tells me about two connections at the same time. Yesterday evening I did "addnode 185.150.190.19" to my homewallet, and I wonder why host 185.150.190.19 does not forward some of his 22 connections (maxconnections=64) to my homewallet.

Homewallet is version 0.6.0 on Windows 8.1.

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: gjhiggins on February 26, 2021, 09:28:51 PM

Quote from: johnwhitestar on February 26, 2021, 07:50:33 PM

I'll let them know immediately, but I'm not sure they'll decide to compile v.0.6 and whether the issue they have ("Slimcoin: Error loading blkindex.dat" error message) has to do with the different version of the wallet they use.

Not the wallet, the error msg is explicit, it's an issue with the client-generated db index file and it may be a mismatch in bdb versions, if they're using an earlier version than the libdb5.3 that my server client was linked with. If it proves to be an issue, I can recompile the node linking it against libdb4.8 and create a chaindump from that.

Cheers

Graham

Message delivered, I'm waiting for their replay.

Update: The issue is solved by CryptoID as well. They compiled the v.0.6 and reported as following: "I recompiled from GitHub and it worked, though version reported by rpc API is a mix of 0.5 and 0.6. I am also on a server with a libdb5.3"

@keliokan were you able to solve the issue on your side?

Update2: Fedde from Freiexchange proposes to ban the servers that are creating this kind of issues. But it seems like we have only 6 servers constantly online right now. Namely it should be 1 mine, 1 of PeterColumboFalk, 1 of cryptoId, 1 of Freiexchange, 2 of Graham. The others are opening and closing to get rewards only. So I don't know whom we should ban and how we can calculate the "bad" servers.

I'm going to set up another server these days.
But what's not that clear to me. If we have 6 servers online, why is it my local wallet has only 1 connection?

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: johnwhitestar on February 26, 2021, 07:50:33 PM

I'll let them know immediately, but I'm not sure they'll decide to compile v.0.6 and whether the issue they have ("Slimcoin: Error loading blkindex.dat" error message) has to do with the different version of the wallet they use.

Not the wallet, the error msg is explicit, it's an issue with the client-generated db index file and it may be a mismatch in bdb versions, if they're using an earlier version than the libdb5.3 that my server client was linked with. If it proves to be an issue, I can recompile the node linking it against libdb4.8 and create a chaindump from that.

Cheers

Graham

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: gjhiggins on February 26, 2021, 07:46:34 PM

Quote from: johnwhitestar on February 26, 2021, 02:11:05 PM

Update2: Freiexchange has reported an error while downloading the above snapshot (Internal Server Error). Probably this one should be ok:

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-02-23.tgz

Doh. My bad. Fixed now, fwiw. https://minkiz.co/noodlings/slm/slmchain.zip

Cheers

Graham

I'll let them know immediately, but I'm not sure they'll decide to compile v.0.6 and whether the issue they have ("Slimcoin: Error loading blkindex.dat" error message) has to do with the different version of the wallet they use.

Topic: Slimcoin | First Proof of Burn currency | Decentralized Web - page 6. (Read 136744 times)