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

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: emrgohff on March 14, 2021, 07:51:17 AM

Quote from: johnwhitestar on March 11, 2021, 07:53:25 AM

Quote from: emrgohff on March 11, 2021, 07:23:27 AM

thanks

You are welcome! But were you able to solve or at least to improve the situation?

Hello.

Everything is the same.

It seems to me that something is wrong with the "Slimcoin version: v0.6.0.0-g8e9fe2c-alpha".

Example:
Balance = 41.69 SLM (transactions = 75)
Report = 41.69 SLM (transactions = 75)
Coin Control Features = 0 SLM

Net Burnt Coins = 527.92 SLM
Report (Brun Address) = 528.09 SLM

In other words, not all values go to "Coin Control" so the values are not the same in all fields.

I think some of your burnt coins are already decayed thus there is a difference between what's you originally burned and your net burnt coins balance.

If you are still experiencing the issues with the wallet you can try to add some RAM to your computer it helped me greatly once.

Another idea can be to switch to the previous version of Slimcoin wallet. Have you compiled by yourself or just got the binaries from github?

emrgohff

newbie

Activity: 83

Merit: 0

Quote from: johnwhitestar on March 11, 2021, 07:53:25 AM

Quote from: emrgohff on March 11, 2021, 07:23:27 AM

thanks

You are welcome! But were you able to solve or at least to improve the situation?

Hello.

Everything is the same.

It seems to me that something is wrong with the "Slimcoin version: v0.6.0.0-g8e9fe2c-alpha".

Example:
Balance = 41.69 SLM (transactions = 75)
Report = 41.69 SLM (transactions = 75)
Coin Control Features = 0 SLM

Net Burnt Coins = 527.92 SLM
Report (Brun Address) = 528.09 SLM

In other words, not all values go to "Coin Control" so the values are not the same in all fields.

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: emrgohff on March 11, 2021, 07:23:27 AM

thanks

You are welcome! But were you able to solve or at least to improve the situation?

emrgohff

newbie

Activity: 83

Merit: 0

Quote from: d5000 on March 09, 2021, 03:26:22 PM

@emrgohff: For me that looks like that you've many inputs (from mining, staking, PoB minting etc.) in your wallet. Maybe to get an idea you could post the (approximate) number of incoming transactions you received, or how long you are PoB/PoS minting or mining already? (if this is too private you can send me a PM)

If this is the root of the problem, then you should try to consolidate the UTXOs. This means convert many transaction outputs into a few transactions sending them to yourself, which will make your wallet "cleaner" and your Slimcoin client will work faster. The easiest way should be to make a big transaction (as big as possible without the above error) to one of your own wallet addresses first and then use Coin Control to consolidate the rest. Can be a bit tedious but is unfortunately currently not possible automatically. If you need more instructions (don't know about your knowledge level regarding Bitcoin-based coins) simply post your questions.

thanks

emrgohff

newbie

Activity: 83

Merit: 0

Quote from: johnwhitestar on March 09, 2021, 07:55:28 AM

@emrgohff

Do you have many transactions already done with that wallet (included PoB rewards)?

Maybe you can reduce the number of maxconnections.

Also changing server=1 into server=0 and listen=1 into listen=0 may help.

By the way your slimcoin.conf is partially in Portuguese, at least the last version you've published. I'm not sure slimcoin-qt is able to understand Portuguese

Please let me know whether any of above suggestion has improved the situation.

thanks

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

@emrgohff: For me that looks like that you've many inputs (from mining, staking, PoB minting etc.) in your wallet. Maybe to get an idea you could post the (approximate) number of incoming transactions you received, or how long you are PoB/PoS minting or mining already? (if this is too private you can send me a PM)

If this is the root of the problem, then you should try to consolidate the UTXOs. This means convert many transaction outputs into a few transactions sending them to yourself, which will make your wallet "cleaner" and your Slimcoin client will work faster. The easiest way should be to make a big transaction (as big as possible without the above error) to one of your own wallet addresses first and then use Coin Control to consolidate the rest. Can be a bit tedious but is unfortunately currently not possible automatically. If you need more instructions (don't know about your knowledge level regarding Bitcoin-based coins) simply post your questions.

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

@emrgohff

Do you have many transactions already done with that wallet (included PoB rewards)?

Maybe you can reduce the number of maxconnections.

Also changing server=1 into server=0 and listen=1 into listen=0 may help.

By the way your slimcoin.conf is partially in Portuguese, at least the last version you've published. I'm not sure slimcoin-qt is able to understand Portuguese

Please let me know whether any of above suggestion has improved the situation.

emrgohff

newbie

Activity: 83

Merit: 0

Quote from: johnwhitestar on March 09, 2021, 06:50:59 AM

Quote from: emrgohff on March 09, 2021, 06:41:33 AM

Quote from: johnwhitestar on March 09, 2021, 05:34:16 AM

@emrgohff please let us know if you've solved

Hello

The problem is (NOT) solved.

The situation is as follows: After making a move (burning or sending) to be able to make another move, you have to close the client (windows) and open again, which is very uncomfortable and takes a lot of time.

Another flaw that I detected was that the account balances are often not correct (updated) and only remain if the customer is re-started.

Can anyone analyze and correct these situations?

Thanks

What version of wallet-qt are you using?
How much RAM do you have on your computer?

* Versão Slimcoin v0.6.0.0-g8e9fe2c-alpha

* slimcoin.conf
rpcuser = usuário
rpcpassword = pass
listen = 1
server = 1
deamon = 1
rpcport = 41684
splash = 1
reservebalance = 1000000
maxconexões = 127
conectar = 144,76.118.44
conectar = 144.76.64.49
connect = 185.150.190.19
addnode = 109.92.14.98
addnode = 178.222.20.152
...
...

RAM = 8 GB

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: emrgohff on March 09, 2021, 06:41:33 AM

Quote from: johnwhitestar on March 09, 2021, 05:34:16 AM

@emrgohff please let us know if you've solved

Hello

The problem is (NOT) solved.

The situation is as follows: After making a move (burning or sending) to be able to make another move, you have to close the client (windows) and open again, which is very uncomfortable and takes a lot of time.

Another flaw that I detected was that the account balances are often not correct (updated) and only remain if the customer is re-started.

Can anyone analyze and correct these situations?

Thanks

What version of wallet-qt are you using?
How much RAM do you have on your computer?

emrgohff

newbie

Activity: 83

Merit: 0

Quote from: johnwhitestar on March 09, 2021, 05:34:16 AM

@emrgohff please let us know if you've solved

Hello

The problem is (NOT) solved.

The situation is as follows: After making a move (burning or sending) to be able to make another move, you have to close the client (windows) and open again, which is very uncomfortable and takes a lot of time.

Another flaw that I detected was that the account balances are often not correct (updated) and only remain if the customer is re-started.

Can anyone analyze and correct these situations?

Thanks

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

@emrgohff please let us know if you've solved

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

Quote from: emrgohff on March 08, 2021, 10:27:50 AM

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

I never got that error, but searching it on the Web this StackExchange thread appears for an old Bitcoin version.

It is possible that you are moving too many "inputs" at once (inputs are created always when you receive coins, from transactions, mining or staking). Have you got many transactions, e.g. from mining or staking and want to move them all at once?*

Try with a smaller amounts, e.g. if you have got many transactions of 10-15 SLM (like they're common for mining) try to move them in sets of 5000, and if this still doesn't work, of 1000 or even 500 SLM.

*(Explanation according to stackexchange, which requires a little bit of knowledge: this happens when the transaction gets too big. For every input there are about 50-100 additional bytes. The limit for Bitcoin is 100 kB, but I didn't find the limit for Slimcoin).

PeterColumboFalk

jr. member

Activity: 81

Merit: 5

I tried a deposit into freix, and a withdraw from freix, and both have been running fine.

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: emrgohff on March 08, 2021, 10:27:50 AM

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://bitcointalksearch.org/topic/error-transaction-creation-failed-218447
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.

emrgohff

newbie

Activity: 83

Merit: 0

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

gjhiggins

legendary

Activity: 2254

Merit: 1278

Quote from: psycodad on March 01, 2021, 02:39:57 AM

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

johnwhitestar

sr. member

Activity: 697

Merit: 262

Slimcoin - the Proof of Donation inventors!

Quote from: keliokan on March 01, 2021, 06:09:00 AM

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!

keliokan

jr. member

Activity: 86

Merit: 1

Hello All,

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

Thanks all for your help !!

K.

psycodad

legendary

Activity: 1604

Merit: 1564

精神分析的爸

Quote from: gjhiggins on February 28, 2021, 07:23:46 PM

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

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..)

PeterColumboFalk

jr. member

Activity: 81

Merit: 5

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,

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