I might be interested but the heatledger website sucks so badly I couldn't find any details on setting up anything. Doesn't inspire confidence. Cheers Graham |
|
|
|
Slimcoin version vSLMCOIN_VERSION_MAJOR.SLMCOIN_VERSION_MINOR.SLMCOIN_VERSION_REVISION.SLMCOIN_V ERSION_BUILD-g154b52a-alpha ()
The good news is that the above confirms you haven't actually been using the latest sources to compile from, which is possibly why the issues look familiar - we have an entirely different, fresh set of issues today  . git log should show the last commit hash as 7d4cacc05c31b3746a349923293cfe4358693e9c - the github default is unusual in that it isn't the master. Cheers Graham |
|
|
|
I'll give the current source a go.
You might be able to speed up the syncing by moving your existing wallet to one side and letting it sync with an empty wallet. Otherwise, there is a nighlty datadir snapshot which might work (experiences vary): https://minkiz.co/noodlings/slm/slm-datadir-snapshot.zipThe current version remains on test to allow me to discover all the bugs I've introduced. Cheers Graham |
|
|
|
what graham is trying to do with our emulation of pivX.
Not looking too favourable for bee-as-pivx (work-in-progress has been committed as beep). Going down the PIVX route without a strong technical team could be terminally disastrous. Max Guevara did call it correctly when he observed: Porting over a bunch of complicated features at once is a sure fire way to break lots of things. Trying to implement two big projects like Masternodes and PoS at once is not very prudent. A phased approach where each feature is added and thoroughly reviewed and tested is the way to go. PivX is on a different code base from Quark, this complicates matters. PivX also has an old modified PoS implementation that's different from Peercoin. In a different context (Slimcoin, a PPclone), I was recently informed: “Blocknet (a Pivx/Dash/PPcoin clone) was hacked in early Oct by someone who discovered a way to exploit the staking mechanism for personal gain. Apparently PIVX had discovered and quietly repaired its code some time before.” and directed to a reddit post: “On 27 Sept, we became aware of a critical staking protocol bug inherited from the PPC/Dash/PivX codebase. Furthermore, we noticed a malicious actor appeared to have exploited this bug the very day before. (which, however improbably, was that the code lacked a check on the number of coins in a stake reward).”
(The PPcoin code that implemented the check on stake reward value had apparently been lost during the extensive refactoring to PIVX.) The other route that I'm investigating involves removing the proprietary anon functionality from Navcoin, a Core 0.13 clone adapted to use PoW-then-PoS (work-in-progress has been committed as been). One important feature of Core 0.13 is the introduction of OP_CHECKLOCKTIMEVERIFY, gateway to the existing decentralised exchanges. Cheers Graham |
|
|
|
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 |
|
|
|
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 |
|
|
|
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 |
|
|
|
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.zipI 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.zipi.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 |
|
|
|
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 |
|
|
|
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.zipI haven't been able to check specifically whether the fault persists. Cheers Graham |
|
|
|
Guessing from the truncation of the debug log, the “Afterburner” PoB processing thread seems to create a problem on some Windows systems.
Following up on this, I noticed an earlier post of mine on the same topic in which I speculated that the C99 macro replacement might be an issue - I think it might well be. Upon close inspection, elsewhere in the code the PRI64u macro for nEffectiveBurnCoins is replaced by llu, rather than just the u in the print statement (that's 'cos it's a long long unsigned int, I kid you not) which is, suspiciously, exactly where things grind to a halt. So, even moar ells are required by the looks of it. I can't get the cross-compiler to work on this new Mint system, so I need to switch back to the old laptop, make the change, cross-compile a Windows binary, switch back to the new laptop, fire up the Windows VM, grab the binary and start it up, import a privkey with a burn tx recorded and see if it falls over. Here's hoping. Cheers Graham |
|
|
|
If you're such a crack dev team
I'm not part of the dev team, I'm lending some informal background tech support while the team gets off the ground, so to speak. Ill-informed, grumpy and off-topic. Cheers Graham |
|
|
|
For an ecosystem that champions individualism, decentralized control, and anonymity - the trend of forcing people to deobfuscate themselves by joining a project's Slack is just plain against what many in the community want out of crypto projects.
Pseudonymity, not anonymity, rather a crucial difference - coins101 is on slack, how does that deobfuscate his identity? How are developers supposed to contribute to github repository code without having accounts on github? Does that also deobfuscate them? HLM already can link SPR history to HLM, and now you want to force people to link email accounts/handles even more so? And you attack people who don't want to participate in that system of centralized power over information? Shameful, selfish, and short-sighted.
Thank you for making my point: ill-informed and grumpy. Cheers Graham |
|
|
|
Thanks for setting that straight Graham, sorry for possibly misleading cctothemass.
Drat it, rumbled. Obviously not the delicately-wrought, gentle nuance of a post that I'd fondly imagined it to be. Cheers Graham |
|
|
|
almost a month now and no HLM wallet or update on its thread.
Yes, it's such a shame that most people prefer the more pro-social experience of the Helium slack instead of the ill-informed grumpy blithering of bitcointalk. You complain about what you see as a whole month's delay? On the spreadcoin thread? Classic ROFL. Cheers Graham |
|
|
|
Elsewise you can disable UPNP with --without-miniupnpc as argument to configure
For a Qt Creator/qmake build (as opposed to a later Core 0.9+ autotools build), the flags are: qmake "USE_UPNP=1" (enabled by default; default)
qmake "USE_UPNP=0" (disabled by default)
qmake "USE_UPNP=-" (not supported)
: So, "USE_UPNP=-" is what you need, it switches off the requirement for miniupnpc headers/libs Cheers Graham |
|
|
|
For PoB my wallet should be online. But after transaction to burn address my wallet always crushes. When wallet is empty - it's ok. After wallet.dat is changed or importprivkey command, wallet immedeatly crushes.
This is a known issue that seems to affect only nodes running on Windows systems. InferringGuessing from the truncation of the debug log, the “Afterburner” PoB processing thread seems to create a problem on some Windows systems. There is, as yet, insufficient information as to whether the issue is limited to specific versions of the code or the version of Windows or the host architecture. The group is unfortunate in that the main reason for the problem persisting is that the group has not been able to attract volunteer technical contributors with expertise in the varieties of Windows OS. Cheers Graham |
|
|
|
1) Who is the developer of this project please. Is it gjhiggins?
2) Why the coin price is very low did the original dev left?
1) It's a FOSS project, I'm merely one of a number of contributors. 2) Yes the original dev left (it's at the end of the OP but it *is* In the OP): https://bitcointalk.org/index.php?topic=613213.0 (The original Slimcoin developer has not posted in this forum since the end of 2014, and he has stated that for the moment he is too busy to continue maintaining the coin. Some of the links in the release announcement are outdated and the formerly official website is offline now. So some members of the community have decided to restart the thread.) (how that relates to your perception of “very low” I couldn't say) Cheers Graham |
|
|
|
|
Show Posts
