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.0Can 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. |
|
|
|
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!  |
|
|
|
|
The deposits on Freiexchange are re-enabled.
|
|
|
|
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. |
|
|
|
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? |
|
|
|
Thank you very much! Very useful. But is 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? |
|
|
|
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_DiscoveryThey'll only show up if you have added them with addnode/connect in the config file and they are listening nodes .. slimcoin.conf maxconnections=127
connect=144.76.118.44
connect=144.76.64.49
connect=185.150.190.19
(total 3 connections) "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 necessary for the server? |
|
|
|
...
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. |
|
|
|
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? |
|
|
|
Update2: Freiexchange has reported an error while downloading the above snapshot (Internal Server Error). Probably this one should be ok: 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.zipCheers 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. |
|
|
|
I deleted the last blockchain from february because of uncertenty. There are two blockchains remaining now: ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_20-12-12.tgz
ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-01-17.tar Host 185.150.190.19 did not mint until now, is planned in the future. The current block is 2363595. CryptoID explorer seems to make a full blockchain syncronisation. They were trying to download your snapshot while it was probably already deleted. So I've just gave them your repository link directly. Update: Freiexchange is on the right blockchain already (should be block 2363651 right now). However the deposits are disabled for the moment to be sure everybody is on the right chain. Update2: CryptoID are getting : "Slimcoin: Error loading blkindex.dat" while trying to use each of the snapshots, that's why they resumed to normal sync right now. I guess they are on version 0.5 of the wallet. |
|
|
|
I thought restarting the node would be a good idea as the debug.log was getting a little large (not so sure anymore if it really was a smart thing to do).
Now from debug.log it looks like a lot of blocks are getting orphaned (but I am not clear if these are blocks I have that are getting orphaned or if some other nodes tries to send me these blocks and my nodes doesn't accept them):
I had the same experience working off my old chaindump from a couple of days ago when trying to cross-sync my servers - loadsa orphans being processed. So I started again, with same dump but this time connecting to 185.150.190.19. The first thing my node did was re-org away a pile of blocks and after that it was just a matter of syncing up to the latest block (as far as 185.150.190.19 sees it). I suspect my node was previously on a fork and as there were so many orphaned blocks, there was a good chance that 185.150.190.19 had a cleaner chain - which it seems to have had. I have a parallel node on the main server that is currently syncing from 0, in due course that will give me a chaindump that is definitely orphan-free. I'll make a zipfile available when it's done. In the meantime, here's the most recent chaindump zipfile, the result of the re-syncing to 185.150.190.19 as described above. Latest node as far as my two listening servers are concerned is 2363137 #000005c5918bb70de908caf07cb8b6865ca8ff1220a0b9878eb89132ba46117b Cheers Graham Thank you so much for your hints! @keliokan Graham has provided a lot of useful info here, if you need any additional help please let me know Update: Freiexchange and cryptoId are both on the wrong chain I'm in touch with them. They are solving the issue on their side as well. If I understood it well the instructions are - the following line should be added into slimcoin.conf: - and the Graham's snapshot should be used: https://minkiz.co/noodlings/slm/slmchain.zipFor those behind the main chain just adding the addnode line and restarting the wallet should be enough. Update2: Freiexchange has reported an error while downloading the above snapshot (Internal Server Error). Probably this one should be ok: ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-02-23.tgz |
|
|
|
... "Maybe you can add the following ones as well: addnode=185.150.190.19
addnode=178.223.55.155:53184
addnode=185.79.5.221:53014
addnode=145.239.189.106:53042
addnode=178.221.183.154:9715
addnode=46.0.192.98:60366
addnode=94.25.174.181:39989
They are all up to date, but the majority of them are not on the standard ports, that's why maybe we have issues to connect to them. Don't know whether it's the right thing to add the port in the slimcoin.conf specifically. I'm restarting my server with this new addnode lines to see whether it will sync. (The local wallet hasn't started yet)." Generally spoken, connections on non-standard ports are (in 99.9% cases) incoming to the respective node, most often these are wallets behind firewalls or with listen=0 that do not allow incoming connections and you see the port they are connecting from. When compiling nodes lists, one should IMHO filter to those with "inbound": false, as these are definitely listening nodes to which your node connected. That is not to say all others are not listening, but only from those to which your node connected you can be sure of it. Also knowing one connected listening node is generally enough as it informs your node about all the other nodes it knows about. From the 8 nodes my node is connected to, only one is inound: false, all others are incoming connections. I guess there are just not so much listening nodes around right now. Thank you for the info, I haven't thought that not all the nodes allow inbound connections. @keliokan, then only the first line of the additional ones counts. We'll need to setup more servers, to see whether the issues will go away in that manner. |
|
|
|
Esta interesante la moneda alguien sabe como puedo publicar mi hilo en la plataforma para mí proyecto ?
No hablo mui bien espanol, qué hilo, qué plataforma? Edit @keliokan I need to leave now, will be back later. Let's go on trying to solve this issue. I hope we'll be able to. I'm with you. |
|
|
|
I am actually using : v0.6.0.0-g8e9fe2c-alpha K. Seems like cryptoId version of blockchain is far ahead.
Interesting that their 2364xxx total blocks doesn't show up for any of my node's peers: "addr" : "185.150.190.19:41682", "height" : 2362598,
"addr" : "185.68.67.37:41682", "height" : 2363859,
"addr" : "178.223.55.155:53184", "height" : 2363828,
"addr" : "178.223.55.155:56231", "height" : 2363843,
"addr" : "5.39.70.87:33984", "height" : 2362598,
"addr" : "185.79.5.221:53014", "height" : 2363717,
"addr" : "145.239.189.106:53042", "height" : 2363845,
"addr" : "178.221.183.154:9715", "height" : 2363767,
"addr" : "212.125.247.58:49560", "height" : 2363719,
"addr" : "178.221.183.154:9964", "height" : 2363720,
"addr" : "46.0.192.98:60366", "height" : 2362598,
"addr" : "178.223.55.155:64890", "height" : 2363689,
"addr" : "178.223.55.155:64902", "height" : 2363689,
"addr" : "94.25.174.181:39989", "height" : 2363729,
"addr" : "91.250.62.26:57117", "height" : 2328476,
"addr" : "18.191.168.158:61845", "height" : 2287922,
"addr" : "144.76.64.49:37520", "height" : 2361253,
"addr" : "109.10.108.52:56155", "height" : 1340151,
I've noticed it as well. That's why I thought the right chain should be something around 2363689. @keliokan I've asked Freiexchange to have a look what is their situation, they told me they'll restart their server to see whether you'll be able send funds there. What version are you using? What if you begin from a snapshot again and directly connect your wallet to some of the servers mentioned above? Have you seen this edit of my previous post? "Maybe you can add the following ones as well: addnode=185.150.190.19
addnode=178.223.55.155:53184
addnode=185.79.5.221:53014
addnode=145.239.189.106:53042
addnode=178.221.183.154:9715
addnode=46.0.192.98:60366
addnode=94.25.174.181:39989
They are all up to date, but the majority of them are not on the standard ports, that's why maybe we have issues to connect to them. Don't know whether it's the right thing to add the port in the slimcoin.conf specifically. I'm restarting my server with this new addnode lines to see whether it will sync. (The local wallet hasn't started yet)." |
|
|
|
Seems like cryptoId version of blockchain is far ahead.
Interesting that their 2364xxx total blocks doesn't show up for any of my node's peers: "addr" : "185.150.190.19:41682", "height" : 2362598,
"addr" : "185.68.67.37:41682", "height" : 2363859,
"addr" : "178.223.55.155:53184", "height" : 2363828,
"addr" : "178.223.55.155:56231", "height" : 2363843,
"addr" : "5.39.70.87:33984", "height" : 2362598,
"addr" : "185.79.5.221:53014", "height" : 2363717,
"addr" : "145.239.189.106:53042", "height" : 2363845,
"addr" : "178.221.183.154:9715", "height" : 2363767,
"addr" : "212.125.247.58:49560", "height" : 2363719,
"addr" : "178.221.183.154:9964", "height" : 2363720,
"addr" : "46.0.192.98:60366", "height" : 2362598,
"addr" : "178.223.55.155:64890", "height" : 2363689,
"addr" : "178.223.55.155:64902", "height" : 2363689,
"addr" : "94.25.174.181:39989", "height" : 2363729,
"addr" : "91.250.62.26:57117", "height" : 2328476,
"addr" : "18.191.168.158:61845", "height" : 2287922,
"addr" : "144.76.64.49:37520", "height" : 2361253,
"addr" : "109.10.108.52:56155", "height" : 1340151,
I've noticed it as well. That's why I thought the right chain should be something around 2363689. @keliokan I've asked Freiexchange to have a look what is their situation, they told me they'll restart their server to see whether you'll be able send funds there. What version are you using? What if you begin from a snapshot again and directly connect your wallet to some of the servers mentioned above? Or at least you can add them as addnode in slimcoin.conf I have this list in my slimcoin.conf: addnode=173.249.10.97
addnode=176.105.8.51
addnode=178.223.23.40
addnode=212.125.247.58
addnode=94.25.169.230
addnode=94.25.171.63
addnode=109.10.108.52
addnode=161.53.40.94
addnode=176.9.139.126
addnode=185.104.185.123
addnode=24.232.14.196
addnode=91.250.62.26
addnode=185.68.67.37
addnode=85.212.150.250
addnode=46.101.235.143
Maybe you can add the following ones as well: addnode=185.150.190.19
addnode=178.223.55.155:53184
addnode=185.79.5.221:53014
addnode=145.239.189.106:53042
addnode=178.221.183.154:9715
addnode=46.0.192.98:60366
addnode=94.25.174.181:39989
They are all up to date, but the majority of them are not on the standard ports, that's why maybe we have issues to connect to them. Don't know whether it's the right thing to add the port in the slimcoin.conf specifically. I'm restarting my server with this new addnode lines to see whether it will sync. (The local wallet hasn't started yet). |
|
|
|
It has been few days,
It is possible to reach a consensus on different chains so far in time or it is a kind of a hard fork ?
I think the consensus will be reached. I suppose it's because we don't have many servers constantly online that we have these issues. I'm going to setup another one these days. |
|
|
|
Hello,
Actually there is two blockchain
And the fork occured on the block 2359430
which one is the good one ??
It's unclear to say the least. This is the (edited for brevity) result from my server‘s (blockheight 2362964) getpeerinfo: [
{
"addr" : "185.150.190.19:41682",
"subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
"inbound" : false,
"height" : 2362598,
},
{
"addr" : "185.68.67.37:41682",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-15-g2668a530-alpha)/",
"inbound" : false,
"height" : 2363859,
},
{
"addr" : "178.223.55.155:53184",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363828,
},
{
"addr" : "178.223.55.155:56231",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363843,
},
{
"addr" : "5.39.70.87:33984",
"subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2362598,
},
{
"addr" : "185.79.5.221:53014",
"subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.0(v0.4.0.0-g154b52a-alpha)/",
"inbound" : true,
"height" : 2363717,
},
{
"addr" : "145.239.189.106:53042",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
"inbound" : true,
"height" : 2363845,
},
{
"addr" : "178.221.183.154:9715",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363767,
},
{
"addr" : "212.125.247.58:49560",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363719,
},
{
"addr" : "178.221.183.154:9964",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363720,
},
{
"addr" : "46.0.192.98:60366",
"subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2362598,
},
{
"addr" : "109.10.108.52:63146",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 1265308,
},
{
"addr" : "178.223.55.155:64890",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363689,
},
{
"addr" : "178.223.55.155:64902",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363689,
},
{
"addr" : "94.25.174.181:39989",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2363729,
},
{
"addr" : "91.250.62.26:57117",
"subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2328476,
},
{
"addr" : "18.191.168.158:61845",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
"inbound" : true,
"height" : 2287922,
},
]
Cheers Graham Here is what I have: [
{
"addr" : "185.150.190.19:41682",
"subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
"inbound" : false,
"height" : 2362151,
},
{
"addr" : "145.239.189.106:41682",
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
"height" : 2363689,
"banscore" : 0
},
{
"addr" : "144.76.118.44:41682",
"subver" : "/Satoshi:0.6.6/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f27-dirty-alpha)/",
"inbound" : false,
"height" : 2362597,
},
{
"addr" : "185.68.67.37:41682",
"subver" : "",
"inbound" : false,
"height" : -1,
}
]
Seems like cryptoId version of blockchain is far ahead. They are stuck right now, by the way, since 21 minutes. Their 0 difficulty blockchain has begun around block 2363620 So it's possible we have 3 blockchains right now, the longest one is that of cryptoId, the second one is around the block 2363689 (I suppose is the right one) and another one @keliokan is stuck on. The cryptoId blockchain is moving though. My server seems to be on the same fork @keliokan is, but my blockchain keeps moving. Maybe the servers will agree at some point which blockchain is the right one. I'm waiting my local wallet to start, it requires a lot of time, though. |
|
|
|
Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.
So even if in can still catch up i am on the wrong chain will a lot of other users i guess.
I tried many times to resynch but still get to the same chain at the end.
"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."
Could be because of a fork.
I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.
Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow. But the fact they have 0 difficulty right now means that the miners are on the other chain. So both hypothesis can be the right ones. Do you have connections? Your wallet reports to be synchronized? Are you able to send coins? I have connection and the wallet is synchronised (2362937) i cannot send coin to freiexchange for example. I'll try to start my local wallet to see what will happen. |
|
|
|
Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.
So even if in can still catch up i am on the wrong chain will a lot of other users i guess.
I tried many times to resynch but still get to the same chain at the end.
"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."
Could be because of a fork.
I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.
Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow. But the fact they have 0 difficulty right now means that the miners are on the other chain. So both hypothesis can be the right ones. Do you have connections? Your wallet reports to be synchronized? Are you able to send coins? |
|
|
|
|
Show Posts
