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

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: aIA on November 12, 2017, 06:40:35 AM

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

cctothemass

sr. member

Activity: 686

Merit: 287

Quote from: gjhiggins on November 10, 2017, 01:05:35 PM

Quote from: gjhiggins on November 09, 2017, 06:28:23 PM

Quote from: ylpkm on November 09, 2017, 04:20:27 PM

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.

aIA

newbie

Activity: 31

Merit: 0

Quote from: gjhiggins on November 11, 2017, 08:51:03 PM

Quote from: aIA on November 11, 2017, 06:20:26 PM

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.

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: aIA on November 11, 2017, 06:20:26 PM

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

newbie

Activity: 31

Merit: 0

Quote from: gavrilo77 on November 10, 2017, 01:14:18 PM

Quote from: gjhiggins on November 10, 2017, 01:05:35 PM

Quote from: gjhiggins on November 09, 2017, 06:28:23 PM

Quote from: ylpkm on November 09, 2017, 04:20:27 PM

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.

psycodad

legendary

Activity: 1612

Merit: 1608

精神分析的爸

Quote from: hannusolo on November 11, 2017, 05:46:28 PM

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

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

HTH

hannusolo

sr. member

Activity: 434

Merit: 257

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?

bobitza202

sr. member

Activity: 489

Merit: 253

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

gavrilo77

hero member

Activity: 819

Merit: 502

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

gavrilo77

hero member

Activity: 819

Merit: 502

Quote from: Sam123 on November 11, 2017, 12:11:09 AM

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"

Sam123

hero member

Activity: 980

Merit: 502

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

excludedcub

newbie

Activity: 22

Merit: 0

Where to buy tokens?

mamahuhu

newbie

Activity: 56

Merit: 0

Looks promissing!

ylpkm

full member

Activity: 138

Merit: 100

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

gavrilo77

hero member

Activity: 819

Merit: 502

Quote from: gjhiggins on November 10, 2017, 01:05:35 PM

Quote from: gjhiggins on November 09, 2017, 06:28:23 PM

Quote from: ylpkm on November 09, 2017, 04:20:27 PM

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

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: gjhiggins on November 09, 2017, 06:28:23 PM

Quote from: ylpkm on November 09, 2017, 04:20:27 PM

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

hero member

Activity: 819

Merit: 502

Quote from: gjhiggins on November 10, 2017, 04:18:27 AM

Quote from: gavrilo77 on November 10, 2017, 04:02:26 AM

Upon activating PoB 0.5 wallet crashed. 0.3 and 0.4 are working well

Is that using the binary I posted a link to above? What does the debug log show?

Cheers

Graham

Yes, the last binary i was using. debug doesnt show that much. I deleted the old one and after crash it says only nreservebalance read as: 0. No further info. Crash coming once i decrypt the wallet. Same was with previous 0.5 builds.

So i am using 0.3 for PoB

marjon

member

Activity: 350

Merit: 10

Good project

aIA

newbie

Activity: 31

Merit: 0

Quote from: eddycurrent on November 10, 2017, 04:00:28 AM

Hello aIA,

With regard to this statement:

Quote from: aIA on November 05, 2017, 07:00:30 AM

... While the wallet is blocked, the Blockchain updates well, but when it is unlocked and start the mining PoB it crash imminently. I have to try to reinitialize the Blockchain and synchronize from scratch...

When you say it crashes, do you mean that the application closes, or it freezes and has to be forced to close? I ask because I have issues with the client when I stake with the wallet being very unresponsive most of the time during staking, and this could be exacerbated when using lower power divices such as ARM boards.

Regards

Helo eddycurrent, i mean it closes. I'm only running the daemon, because i uses raspbian server (headless). Maybe the cause is the same as in the version of windows that gjhiggins is investigating.

Yesterday it failed during the synchronization, the demon closed, but I started it again and it seems to continue fine.

I would like to buy another Pi to test with Arch Linux, to rule out any problem with Raspbian.

Cheers.

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: gavrilo77 on November 10, 2017, 04:02:26 AM

Upon activating PoB 0.5 wallet crashed. 0.3 and 0.4 are working well

Is that using the binary I posted a link to above? What does the debug log show?

Cheers

Graham

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