Pages:
Author

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

hero member
Activity: 819
Merit: 502
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.

Cheers

Graham


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

jr. member
Activity: 61
Merit: 3
Hello aIA,

With regard to this statement:
... 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
legendary
Activity: 2254
Merit: 1290
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.

Cheers

Graham
full member
Activity: 138
Merit: 100
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 need it compiled for windows I can try if the dependency list isnt crazy to get working.
legendary
Activity: 2254
Merit: 1290
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


full member
Activity: 138
Merit: 100
submitted request to coinsmarket and said would donate a little too.
legendary
Activity: 2254
Merit: 1290
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
sr. member
Activity: 882
Merit: 310
I can say that I'm gathering resources for the website, and if my promoter would allow I'd write a bachellor degree (BA paper) from economics about cryptocurrencies as an alternative payment and settlement system, and would also write about consensuses of blockchain and Slimcoin. But I must get permission from my doctor.
legendary
Activity: 1612
Merit: 1608
精神分析的爸
..
So, "USE_UPNP=-" is what you need, it switches off the requirement for miniupnpc headers/libs


Thanks for setting that straight Graham, sorry for possibly misleading cctothemass.

psycodad
legendary
Activity: 2254
Merit: 1290
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:
Code:
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
legendary
Activity: 1612
Merit: 1608
精神分析的爸
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

I tried to launch a wallet on Windows 10 / 8.1 / 7. The process crashes on all systems after I import the private key and begins the POB mining. I'm a Windows user, but I'll try to install the Debian on the virtual machine and compile Slimcoin from the sources.
Now qmake issues an error - UPNP, and make ~ 800 compilation errors. Maybe I forgot to import any libraries. Is it enough?
Code:
apt-get install qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev \
    libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \
    libssl-dev libdb4.8++-dev

While you mention UPNP, you might miss (among others):
Code:
apt-get install libminiupnpc-dev

Elsewise you can disable UPNP with --without-miniupnpc as argument to configure (if you are going to run your node on a public IP it shouldn't be needed, elsewise UPNP can be helpful if your router/firewall supports it).

HTH
sr. member
Activity: 686
Merit: 287
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

I tried to launch a wallet on Windows 10 / 8.1 / 7. The process crashes on all systems after I import the private key and begins the POB mining. I'm a Windows user, but I'll try to install the Debian on the virtual machine and compile Slimcoin from the sources.
Now qmake issues an error - UPNP, and make ~ 800 compilation errors. Maybe I forgot to import any libraries. Is it enough?
Code:
apt-get install qt4-qmake libqt4-dev build-essential libboost-dev libboost-system-dev \
    libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev \
    libssl-dev libdb4.8++-dev
legendary
Activity: 2254
Merit: 1290
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
sr. member
Activity: 686
Merit: 287
Is https://bchain.info/SLM/ correct? I don't see my transaction from exchange and burning transaction here. Wallet crushes after burning. I think, that i lose my funds Sad Can someone confirm that txid: 6242764151ebcace4589b88371007bb8411822f7d11ffae028738919d4253f1b and burn txid: d86b261b82e46810a82f85bde69b77e2a93d363ace761d8856d17d3d13c5e6f6

ACME, fortunately, is up to date:

6242764151ebcace4589b88371007bb8411822f7d11ffae028738919d4253f1b shows up correctly, the burn transaction too.

Anyway, if a burn transaction (or any other transaction you do) "gets lost" (e.g. because it's included in orphan blocks) then you simply can do a "slimcoin-qt -rescan" (or "slimcoind -rescan") and the balance will get added to your wallet again.

The only way a transaction can get really "lost" is if it comes from an exchange (or online wallet), "gets lost" in an orphan block/chain, and the owners refuse to credit your correctly - but then they're scamming you, because in this case the transaction simply didn't happen.


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.

Edit

If -rescan flag isn't used, wallet doesn't crush, but burn information is lost.
jr. member
Activity: 61
Merit: 3
Hello all,
Some more binarys for you. I have put them all here including the ones from my previous post.

ARM-V7 linux QT:
https://drive.google.com/open?id=1_gR5sKBz2BJQ77e61fVSRWMFwvrt7lbq

ARM-V7 linux cli daemon:
https://drive.google.com/open?id=16I7WMSQdf9tsKOX6iRbrrJBaJraORz3B

ARM-V5 linux QT:
https://drive.google.com/open?id=18j2lk3YeL1ynKmET249c2B3hKvx-7gHI

ARM-V5 linux cli daemon:
https://drive.google.com/open?id=1nK7aouydmPyQ03YLtPq4sdlnsMpSuz4U

I am fairly sure that the last two are ARM-V5, not ARM-V6, but I have been having a bit of confusion with QEMU which I have been using for compilation, so if anyone has any issues with them, please let me know.

ARM-V8 will be next!

Regards
legendary
Activity: 3906
Merit: 6249
Decentralization Maximalist
Is https://bchain.info/SLM/ correct? I don't see my transaction from exchange and burning transaction here. Wallet crushes after burning. I think, that i lose my funds Sad Can someone confirm that txid: 6242764151ebcace4589b88371007bb8411822f7d11ffae028738919d4253f1b and burn txid: d86b261b82e46810a82f85bde69b77e2a93d363ace761d8856d17d3d13c5e6f6

ACME, fortunately, is up to date:

6242764151ebcace4589b88371007bb8411822f7d11ffae028738919d4253f1b shows up correctly, the burn transaction too.

Anyway, if a burn transaction (or any other transaction you do) "gets lost" (e.g. because it's included in orphan blocks) then you simply can do a "slimcoin-qt -rescan" (or "slimcoind -rescan") and the balance will get added to your wallet again.

The only way a transaction can get really "lost" is if it comes from an exchange (or online wallet), "gets lost" in an orphan block/chain, and the owners refuse to credit your correctly - but then they're scamming you, because in this case the transaction simply didn't happen.

jr. member
Activity: 61
Merit: 3
Hello,


No, I do not think that it is correct as from what I can see, the last block visible on bchain.info is from 3 days ago.

Regards
sr. member
Activity: 686
Merit: 287
Is https://bchain.info/SLM/ correct? I don't see my transaction from exchange and burning transaction here. Wallet crushes after burning. I think, that i lose my funds Sad Can someone confirm that txid: 6242764151ebcace4589b88371007bb8411822f7d11ffae028738919d4253f1b and burn txid: d86b261b82e46810a82f85bde69b77e2a93d363ace761d8856d17d3d13c5e6f6
legendary
Activity: 3906
Merit: 6249
Decentralization Maximalist
@gjhiggins: Thanks for looking at it. I read in the last pages that there were problems with the CLTV implementation (tests failed). If there is something I can help testing, PM me (or write me here), I now have more time to dedicate to Slimcoin again.

I have now adapted ACME's blocknotify scripts to my own folder structure (wasn't very hard, I admit). So in theory I could start now to build the Slimcoin RDF/OWL chain with Fuseki.

My original plan is to use the "blocknotify-catchup.sh" script to sync the RDF structure using an already downloaded blockchain. How is this script invoked? Can it sync an entire blockchain? (We were talking about that some weeks/months ago but I don't remember the page ...)

Or is it better to sync from zero using the "blocknotify.sh"? (I would like to avoid that Wink )

Update: I tried to simply run the catchup script from the command line with a Slimcoin client running, but it complains about a missing config["mainnet"] dictionary item, that is supposed to be extracted from a file called "coin.ini". I didn't find this file in the ACME repository, do I have to create it myself - and what to put inside?



@psycodad: You're right, these accounts are very likely bots/farmed accounts. At this page, again the same question popped up about the "necessity of a blockchain". I will ignore them from now on.

Today SLM price in Novaexchange is 77sts. It is lowest in 6 month.
Dev, are you have any plan for future ?

The price is mostly low because of the closure of Novaexchange. Opportunistic/short-term miners and some speculators that have no special relation with Slimcoin and treat it like every other sh!tcoin are panicking and selling, and as registrations are closed, there is no "fresh money flowing in".

The plans are to use decentralized trading methods from now on, and maybe get on another exchange. The original plans (working decentralized websites, code update) have not changed, but we have no "centrally decided" roadmap. The decentralized websites already work but what still is missing is the block explorer structure needed for it.

By the way: Keep in mind that 77 satoshis now are worth still about 8 times more in USD than 77 satoshis at the beginning of 2017 Wink (and we were as low as 20 satoshis then ...). So Slimcoin is one of the few "older" coins that could increase its value with respect to Bitcoin. I'm sure once another exchange is found the situation will improve again.

One more question please. Is there any other project using Proof of Burn please ?
I only remember one clone called TGcoin that uses PoB in the same way than Slimcoin, but it died 2-3 years ago. Other projects that use "Proof of Burn" like Counterparty use it for the initial distribution, not for consensus/block generation.
hero member
Activity: 980
Merit: 502
One more question please. Is there any other project using Proof of Burn please ?
Thanks again
Pages:
Jump to: