Slimcoin | First Proof of Burn currency | Decentralized Web

[gjhiggins]

if you need it compiled for windows I can try if the dependency list isnt crazy to get working.

Thanks for the offer but I'm okay - I've updated the candidate Windows binary on minkiz: https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.0-win32.zip
I haven't been able to check specifically whether the fault persists.

Welllll, I'm pleased to report that it was another case of “moar ells” ...



and the zip file with updated Windows binary is:

https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

i.e. the previous link was to a zip file with a current datestamp but unchanged contents. I had omitted to clean out the release subdirectory before recompiling, sigh. I nearly missed that, wouldn't have noticed had it not been for the fact that I'd corrected a typo in the print string immediately above my edit and the debug log was still showing the typo. I did it twice (cross-compiled the binary on the old Linux laptop, uploaded it to the server, downloaded it to the Windows VM), omitted to clean the release directory twice, typo showed up twice. WTF? It was only then that I started backtracking, checking my assumptions - finally realising that the zip file content was remaining unchanged. Hence the 0.5.1, for clearer differentiation.

Sorry if I wasted anyone's time with that boo-boo.

Cheers

Graham

[gavrilo77]

if you need it compiled for windows I can try if the dependency list isnt crazy to get working.

Thanks for the offer but I'm okay - I've updated the candidate Windows binary on minkiz: https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.0-win32.zip
I haven't been able to check specifically whether the fault persists.

Welllll, I'm pleased to report that it was another case of “moar ells” ...



and the zip file with updated Windows binary is:

https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

i.e. the previous link was to a zip file with a current datestamp but unchanged contents. I had omitted to clean out the release subdirectory before recompiling, sigh. I nearly missed that, wouldn't have noticed had it not been for the fact that I'd corrected a typo in the print string immediately above my edit and the debug log was still showing the typo. I did it twice (cross-compiled the binary on the old Linux laptop, uploaded it to the server, downloaded it to the Windows VM), omitted to clean the release directory twice, typo showed up twice. WTF? It was only then that I started backtracking, checking my assumptions - finally realising that the zip file content was remaining unchanged. Hence the 0.5.1, for clearer differentiation.

Sorry if I wasted anyone's time with that boo-boo.

Cheers

Graham

Lovely, crash not any more!!! Thank you Graham!!!

Edit: Once again, the new update works well, PoB and PoW. No crashing. Still testing

[ylpkm]

Updated to 5.1, wallet hasnt crashed, Mining works, Ill update if i get a burn block.

[mamahuhu]

Looks promissing!

[excludedcub]

Where to buy tokens?

[Sam123]

I just installed the latest Wallet on Windows. What does it mean: Minting suspending due to locked wallet ? How can I unlocked please
Thanks

[gavrilo77]

I just installed the latest Wallet on Windows. What does it mean: Minting suspending due to locked wallet ? How can I unlocked please
Thanks

go to console and type "walletpassphrase yourpass 999999999999"

[gavrilo77]

Is it possible to add SLM to wallet.trezor.io?

[bobitza202]

Hope i'll be able to withdraw soon from Nova, i kept a small SLM stash there  

[hannusolo]

Hello guys, can anyione help me?

Last time I was using the slimcoin wallet was about a month ago, it worked quite well (0.5). Now I tried to start it today, it loaded the blockhain fine. But after I unlocked it completely floods my cpu, contsant 50% usage, was mining previously only on one thread, now the mining software barely does 0.1 khashes... And the whole wallet is super slow after unlocking...

What am I doing wrong?

[psycodad]

Hello guys, can anyione help me?

Last time I was using the slimcoin wallet was about a month ago, it worked quite well (0.5). Now I tried to start it today, it loaded the blockhain fine. But after I unlocked it completely floods my cpu, contsant 50% usage, was mining previously only on one thread, now the mining software barely does 0.1 khashes... And the whole wallet is super slow after unlocking...

What am I doing wrong?

Your wallet is eventually staking like crazy. Try setting the reservebalance (coins of your wallet that can't stake) in the debug window (Help | Debug window | Console) with:

Code:

reservebalance true <your-balance-or-more>

If that fixes your problem after a few minutes, try decreasing the amount of <your-balance-or-more> until you find a load level that your PC can bear so you still can stake.

HTH

[aIA]

if you need it compiled for windows I can try if the dependency list isnt crazy to get working.

Thanks for the offer but I'm okay - I've updated the candidate Windows binary on minkiz: https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.0-win32.zip
I haven't been able to check specifically whether the fault persists.

Welllll, I'm pleased to report that it was another case of “moar ells” ...

https://i.imgur.com/EJOwVFX.png

and the zip file with updated Windows binary is:

https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

i.e. the previous link was to a zip file with a current datestamp but unchanged contents. I had omitted to clean out the release subdirectory before recompiling, sigh. I nearly missed that, wouldn't have noticed had it not been for the fact that I'd corrected a typo in the print string immediately above my edit and the debug log was still showing the typo. I did it twice (cross-compiled the binary on the old Linux laptop, uploaded it to the server, downloaded it to the Windows VM), omitted to clean the release directory twice, typo showed up twice. WTF? It was only then that I started backtracking, checking my assumptions - finally realising that the zip file content was remaining unchanged. Hence the 0.5.1, for clearer differentiation.

Sorry if I wasted anyone's time with that boo-boo.

Cheers

Graham

Lovely, crash not any more!!! Thank you Graham!!!

Edit: Once again, the new update works well, PoB and PoW. No crashing. Still testing

I am very happy to inform you that after compiling the daemon again in a raspberry pi 3 with Raspbian with the last changes that gjhiggins has introduced in the code, the PoB finally works without closing the application. Since the version of Slimcoin that eddycurrent has been compiling for the different Arm devices was not fully functional I have thought, if the community agrees, that the bounty offered by the functional Arm versions will be divided into two, 5000SLM for gjhiggins to resolve the failure of the PoB and 5000SLM for eddycurrent when recompile the Arm v5 and v7 versions again and provide the v8 all with the new code. I wait for your comments.

Cheers.

[gjhiggins]

bounty offered by the functional Arm versions will be divided into two, 5000SLM for gjhiggins to resolve the failure of the PoB

Let me be the first to point out that gjhiggins introduced the PoB bug in the first place with an improper replacement of the C99 macro. It would be ethically dubious to collect a bounty for fixing a bug I introduced, the bounty should go to eddycurrent in its entirety.

Cheers

Graham

[aIA]

bounty offered by the functional Arm versions will be divided into two, 5000SLM for gjhiggins to resolve the failure of the PoB

Let me be the first to point out that gjhiggins introduced the PoB bug in the first place with an improper replacement of the C99 macro. It would be ethically dubious to collect a bounty for fixing a bug I introduced, the bounty should go to eddycurrent in its entirety.

Cheers

Graham

I understand gjhiggins, thank you for your honesty. Remember: “Success is walking from failure to failure with no loss of enthusiasm” W.Churchill.

In another order of things I found a discrepancy in the result of "getburndata" between the windows version and the daemon in raspberry pi, both with the new code ... and I do not know which is the correct one ..

Windows wallet (a new empty wallet) show:
nEffectiveBurnCoins: -212572955
Formatted nEffectiveBurnCoins:  1533090.00

Raspberry pi wallet (slimcoind with 3200SLM aprox burned wallet) show:
nEffectiveBurnCoins: 536
Formatted nEffectiveBurnCoins:  0.153309

Could anyone compare with that values?

Thanx you.

[cctothemass]

if you need it compiled for windows I can try if the dependency list isnt crazy to get working.

Thanks for the offer but I'm okay - I've updated the candidate Windows binary on minkiz: https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.0-win32.zip
I haven't been able to check specifically whether the fault persists.

Welllll, I'm pleased to report that it was another case of “moar ells” ...

and the zip file with updated Windows binary is:

https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

i.e. the previous link was to a zip file with a current datestamp but unchanged contents. I had omitted to clean out the release subdirectory before recompiling, sigh. I nearly missed that, wouldn't have noticed had it not been for the fact that I'd corrected a typo in the print string immediately above my edit and the debug log was still showing the typo. I did it twice (cross-compiled the binary on the old Linux laptop, uploaded it to the server, downloaded it to the Windows VM), omitted to clean the release directory twice, typo showed up twice. WTF? It was only then that I started backtracking, checking my assumptions - finally realising that the zip file content was remaining unchanged. Hence the 0.5.1, for clearer differentiation.

Sorry if I wasted anyone's time with that boo-boo.

Cheers

Graham

Thank you Graham!
The new version works very well! Wallet with PoB was working all night. No crashing anymore.

[gjhiggins]

In another order of things I found a discrepancy in the result of "getburndata"

I have a nasty suspicion that yet moar ells are required - looks like the result of an integer overflow, i.e. the required precision is incorrectly specified. Fortunately, the use of the C99 macros was limited to print output. I'll go through it again.

Cheers

Graham

[gjhiggins]

Thank you for that, appreciated!BTW, the macintosh binary seems to find yourself in trouble at InchLoading addresses...Inch. Might be because it's meant to use on a testnet and my wallet is around the mainnet?Many thanks!

Sorry for not updatiing the OS X version, will do so now ...

Cheers,

Graham

[hannusolo]

Hello guys, can anyione help me?

Last time I was using the slimcoin wallet was about a month ago, it worked quite well (0.5). Now I tried to start it today, it loaded the blockhain fine. But after I unlocked it completely floods my cpu, contsant 50% usage, was mining previously only on one thread, now the mining software barely does 0.1 khashes... And the whole wallet is super slow after unlocking...

What am I doing wrong?

Your wallet is eventually staking like crazy. Try setting the reservebalance (coins of your wallet that can't stake) in the debug window (Help | Debug window | Console) with:

Code:

reservebalance true <your-balance-or-more>

If that fixes your problem after a few minutes, try decreasing the amount of <your-balance-or-more> until you find a load level that your PC can bear so you still can stake.

HTH

Thnaks for the answer, will try that!

[sluggo]

Is staking on when I unlock the wallet? Im getting lots of 'Mint by Burn' but no stake. or am I stupid and thats the same thing.

[eddycurrent]

Hello gjhiggins and aIA,

The updated clients for v5 and v7 should be up within the next week, however I am still working on a way to compile for v8 (should manage it soon), then I intend to automate the process as much as possible.

Regarding the division of the bounty, I would be more than happy to share it, as gjhiggins has done great things for the Slimcoin community and his openssl1.1 compatability fix was very helpful to me personally.

If anyone is interested, I am considering creating an Android version of the client.

Regards