Ninjastic
Search content
Sort by
Showing 20 of 31 results by aIA
Post
Topic
Re: Slimcoin | First Proof of Burn currency | 0.5.1 binaries | Redesigned Website
by
aIA
on 07/01/2018, 22:45:53 UTC
Quote from: muf18 on January 07, 2018, 09:33:05 PM

I think it's nice idea, and would actually, be within our main purpose of "burning" coins.
Anyone who, would want to participate, would have to burn coins through client, mined or bought with exchange.

It should be decided of course, with everyone approval. What do you think?


I think it would be a nice workaround for update features quickly. But I think that we will haven’t liquidity to move SLM on exchanges, and get SLM listed over some months.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | New v0.5.1 binaries
by
aIA
on 13/12/2017, 20:49:39 UTC
Quote from: muf18 on December 13, 2017, 08:42:49 PM
We have been added to the new exchange - coinsmarket.com

https://coinsmarkets.com/trade-BTC-SLM.htm

Happy trading.
For now there is a wallet synchronization, so wait until, it will be synchronized.

That is a very good new!!!
Post
Topic
Re: Slimcoin | First Proof of Burn currency | New v0.5.1 binaries
by
aIA
on 20/11/2017, 19:22:55 UTC
Quote from: eddycurrent on November 17, 2017, 11:30:42 PM
Hello aIA,

Did those binarys I posted for ARMv8 work on your system? I just want to verify that it didn't just work on my local system, but will work on any system.


Hi eddycurrent, I have just tested with V7 and work perfectly. Can´t test v8 because raspbian its only 32bit and Raspberry Pi 3 (armv8) with 32bits OS report itself as armv7 and woks with armv7 instructions set.

armv5 doesn´t work on raspberry pi with raspbian.

Maybe someone with other arm device could test v5 and v8.

Cheers.

Edit:

Hi gjhiggins, you have a PM.
Cheers.

Post
Topic
Re: Slimcoin | First Proof of Burn currency | New v0.5.1 binaries
by
aIA
on 17/11/2017, 18:22:03 UTC
Quote from: d5000 on November 15, 2017, 03:16:21 AM
@aiA: Done! I have also deleted some redundancies between the installation and the resources section.

I assume eddycurrent has won the ARM bounty, so I can delete it fully ...


Thank you d5000, and yes, eddycurrent has won the bounty. Thanks to all people that make that awesome community!!!

Cheers.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 14/11/2017, 22:32:59 UTC
Quote from: eddycurrent on November 12, 2017, 11:25:16 PM
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


Hello eddycurrent and gjhiggins,

then if you agree we can distribute the bounty for example at 60% for eddycurrent and his compilation work and 40% for gjhiggins to reward all the improvements he is making.

Eddycurrent: I like how you are organizing the folder to undo the different versions. If you could automate the compilation method a bit so that each new improvement that gjhiggins incorporates is soon available to users would be great.

Hi d5000: would it be possible to add the following links in the first post? I think they will be useful for all users.

- The download of the Arm versions that prepares eddycurrent.
- The snapshot of the Blockchain that prepares gjhiggins daily.
- The latest version of Windows client 0.5.1.

Thank you all.

Cheers.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 12/11/2017, 11:40:35 UTC
Quote from: gjhiggins on November 12, 2017, 01:51:03 AM
Quote from: aIA on November 11, 2017, 11: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.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 11/11/2017, 23:20:26 UTC
Quote from: gavrilo77 on November 10, 2017, 06:14:18 PM
Quote from: gjhiggins on November 10, 2017, 06:05:35 PM
Quote from: gjhiggins on November 09, 2017, 11:28:23 PM
Quote from: ylpkm on November 09, 2017, 09: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.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 10/11/2017, 10:37:22 UTC
Quote from: eddycurrent on November 10, 2017, 09:00:28 AM
Hello aIA,

With regard to this statement:
Quote from: aIA on November 05, 2017, 12:00:30 PM
... 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.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 05/11/2017, 15:45:21 UTC
Quote from: psycodad on November 05, 2017, 12:54:52 PM
From my personal expericence with all kinds of embedded computers (RPI, Panda, Cubieboard, pcDuino, Olinuxino and so on), these have some limitations that make them not the perfect choice for running a full node, especially when it is a POS or POB node:
1. Memory
2. Wearing out the flash based harddisks

Without staking and just little burning, my Slimcoin node uses ~700GB of memory. I suspect while synching up this amount is noteably higher. The Raspi 3 has 1GB memory AFAIK, if you also run a graphical desktop on the same device that won't just cut it and swapping to an SDcard maybe is suboptimal as well. Right now, while replying, my browser uses ~2.8G memory.

If you have coins in your wallet, you might want to try to synch up with an empty wallet and see if you get any further that way. Also quitting all memory-intensive programs like browser and such could help (if you do you run an graphical desktop on it). Then once it crashes, check your syslogs for messages about the OOM killer ("Out of Memory: Killed process XY").
But in the end I do not think that any kind of device with under 2GB (better 4GB) of memory and a fast storage medium will be able to run a full node of Slimcoin in the long run.

HTH

Hi psycodad, I think that you are right, but I try workaround that installing Raspbian OS in raspberry pi on a usb memory and the Blockchain and wallet files on a usb hard disk drive. Also I added 4gb of swap file on hdd. With htop I can see how sometimes slimcoind take part of swap file, but less than 1gb. I use server version of Raspbian, without graphical environment. All run smoothly until I unlock the wallet.

Now I’m syncing the Blockchain from scratch with the new binary compiled from eddycurrent trying to do other test.

Greetings.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 05/11/2017, 12:00:30 UTC
Quote from: eddycurrent on November 04, 2017, 03:15:45 AM
Hello all,

Here is the arm-V7 linux QT binary:

https://drive.google.com/open?id=1_gR5sKBz2BJQ77e61fVSRWMFwvrt7lbq

and the cli daemon binary for the same architecture:

https://drive.google.com/open?id=16I7WMSQdf9tsKOX6iRbrrJBaJraORz3B

Could some other users please validate that these binarys work and contain no malware?

If there is a better way to make these available, please let me know.

Regards

Hello, I appreciate the work you are doing. I have tried the CLI version that you have posted on a Raspberry pi 3 (armv8) and in principle it runs well but I find the same problem as in the compilation tests that I have made some time ago.

https://bitcointalk.org/index.php?topic=1141676.msg20954309#msg20954309

https://bitcointalk.org/index.php?topic=1141676.msg21695133#msg21695133


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 (I used a copy of my Windows wallet) I will also try to change the operating system. I currently use Raspbian (based on debian) and I will try Arch Linux for Raspberry pi. I keep you informed.

Greetins.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 18/10/2017, 13:45:27 UTC
Quote from: wDUO on October 18, 2017, 09:28:20 AM
I need some nodes....  help?

May it help:

addnode=101.176.118.103:25128
addnode=104.220.53.130:25128
addnode=109.11.168.174:25128
addnode=113.106.95.46:41682
addnode=118.126.8.18:41682
addnode=124.237.121.111:41682
addnode=134.255.216.245:3133
addnode=134.255.218.110:3133
addnode=134.255.220.128:3133
addnode=134.255.234.9:25128
addnode=144.76.64.49:41682
addnode=156.34.12.254:25128
addnode=161.53.40.94:41682
addnode=163.158.18.61:25128
addnode=163.172.122.122:3133
addnode=174.97.212.25:25128
addnode=182.74.64.221:41682
addnode=185.165.168.137:25128
addnode=185.68.67.37:41682
addnode=185.78.191.159:25128
addnode=198.2.196.177:25128
addnode=204.236.246.48:41682
addnode=213.22.209.46:41682
addnode=217.41.8.34:25128
addnode=23.248.72.180:3133
addnode=37.187.100.75:41682
addnode=45.32.5.145:25128
addnode=45.76.7.44:25128
addnode=46.172.148.58:3133
addnode=46.4.84.83:41682
addnode=5.9.20.80:41682
addnode=5.9.39.9:41682
addnode=61.77.6.129:41682
addnode=62.210.247.39:3133
addnode=64.184.111.132:25128
addnode=68.131.33.61:25128
addnode=69.156.127.151:25128
addnode=69.158.155.203:25128
addnode=69.206.138.108:3133
addnode=71.87.135.158:3133
addnode=73.66.139.249:3133
addnode=73.89.244.40:25128
addnode=77.58.32.169:3133
addnode=80.194.189.110:25128
addnode=85.10.208.71:41682
addnode=88.11.174.20:41682
addnode=89.217.220.115:3133
addnode=93.73.107.79:3133
addnode=95.31.222.179:25128
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5
by
aIA
on 05/10/2017, 18:06:43 UTC
Quote from: d5000 on October 04, 2017, 07:47:04 PM
The problem emerges if we want to describe Slimcoin's advantages versus other competitors. Here, I think, at least a very basic Proof of Burn description would have to be included. And I think there are advantages (as I wrote here), above all the stability-favouring aspect.
I'm agree with that idea. PoB is the differentiating element of this coin. I understand the internal mechanism (more or less), but for any one that doesn't interest that, could be interesting the fact that it's a way to investiment in middle-long term with low CPU power. Is for that I'm so interested in Raspberry or similar device wiht full working Slimcoin daemon or at least syncing and PoB functionalities.

Cheers.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 13/09/2017, 18:27:27 UTC
Quote from: gjhiggins on September 13, 2017, 02:37:29 PM
Some work required, still.

Thank you Graham. I would like offer another bounty, 5000 SLM, for that feature. When you consider this is fully working, please inform us and I will send you the reward.

@d5000, please Slimcoin Comunity, could you write down the two bountys i offered? Thank you so much.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 10/09/2017, 15:43:05 UTC
Quote from: muf18 on September 10, 2017, 02:20:01 PM
@aIA - I think it was done (Rasperry Pi version of Slimcoin client), by @cryptovore - some posts ago.
I thought about also, making a full node version of Slimcoin, cause it's mainly written in C++ and python, with the usage of QT libs, which are compatible with Android.


Please, could you point me message number? I have been locking for without luck.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 10/09/2017, 14:02:49 UTC
Hi guys, I think that the spirit of Slimcoin must be this, be slim...

As proposed muf18, adding a feature to preseved very important files could be an attractive feature for some people and may grow our community. May be if it could be achieved in a parallel block chain and that were optional to support and there were rewards to user for use their nodes (as storj style). Don't know sure how to incorporate that. But more important part is do that in the way that don't change Slimcoin spirit.

I have been attracted to Slim thinking that I could mining with low power device. But not really... For the moment.
I think that differential feature of Slimcoin is PoB and if we're possible that works perfectly on low power hardware like Raspberry Pi and other ARM device this could attract lot of people that haven't high power pc or greats mining rigs as me. And achieve it in a low power consumption device it could be economically viable to motivate lots of users to get running full nodes (ok, is not useable for PoW and PoS, but at least for PoB)

As you can read some pages back I have been trying to do Slimcoin daemon compiling and working in Raspberry pi... I only achieved to run 0.5 (compiled with BerkleyDB 4.8 in order to pass blockchain files from windows wallet because daemon doesn't sync from scratch, always stuck) with encrypted wallet because it crash always when try to do PoB. At least work as a full node because syncing new blocks does work.

I would like offer a bounty of 10.000 SLM for a full functionally ARM updated version of daemon. If any one can support this bounty it could be interesting for a dev.

Please, excuse my poor English grammar.

Cheers.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 24/08/2017, 11:12:33 UTC
Quote from: d5000 on August 23, 2017, 10:23:10 PM
Does Beatcoin plan to add an English interface? For now, I only see a Polish one ... that unfortunately would limit the target public a bit.

+1

I like so much the interface but can't understand almost anything. Are they planning add English language at least?

I can contribute with 3000 SLM, but I think it's very important don't move them from Nova... we would like have more than one Exchange but not loose Nova.

Cheers.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 20/08/2017, 16:38:55 UTC
Hi, i have been reading debug.log file trying identify why slimcoin daemon on raspbery pi (with raspbian) crash so frequently.

I have found that:

Code:
getblocks 253404 to 00000007281451e91875 limit 500
  getblocks stopping at limit 253903 0000000942578c720b5f (0 bytes)
getblocks 253404 to 3bfbb86e0474e8dfb756 limit 500
  getblocks stopping at limit 253903 0000000942578c720b5f (0 bytes)
getblocks 253404 to 64d9ae181c771879b0b2 limit 500
  getblocks stopping at limit 253903 0000000942578c720b5f (0 bytes)
getblocks 1 to 0000000f0c1baa5f2ec8 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000e63eee9fb2b62 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000c8f10b8c2133a limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000005a497af15e194 limit 262653
  likely old client, incrementing misbehaviour count.trying connection 180.155.8.122:41682 lastseen=-28024.5hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000169ff77e7e6903 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000181b4c9e912624 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000116f0c1e4a4b3c limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000b6916ce241de2 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000151a0612e299c2 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000ae4d14270f56f limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000b40a5a86708cb limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000005bc51aa13710 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001c0569ee0c51e1 limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
trying connection 65.94.75.10:41682 lastseen=-26622.2hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000b2cf653b4186c limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000002e91f0b23157a limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001b1f2ea040c19f limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000006f5e524cf638d limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001ce7f3b7b96930 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000f3d0605759654 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001b4ff5aa7723db limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000b7122fc28c93b limit 262653
  likely old client, incrementing misbehaviour count.trying connection 113.106.95.46:41682 lastseen=-389780.4hrs
connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001f5b5e3021be34 limit 262653
  likely old client, incrementing misbehaviour count.trying connection 151.232.214.142:41682 lastseen=-7552.2hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000001003f5885c5ed limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000464acf3dc4af5 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000e6d9a1b967a60 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000fc6ab6ddeff42 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000003f7005b0f096f limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000003a6b8f6398deb limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001335edd3b7d87e limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001733659d322a3d limit 262653
  likely old client, incrementing misbehaviour count.trying connection 118.126.8.18:41682 lastseen=-389780.4hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000009252e20c313ec limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000df096a276b3cc limit 262653
  likely old client, incrementing misbehaviour count.trying connection 130.204.61.171:41682 lastseen=-12147.9hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001198ca6e32ed61 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000009e5595a8b672d limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
trying connection 130.255.73.170:41682 lastseen=-389780.4hrs
connect() failed after select(): Connection refused
trying connection 149.169.122.151:41682 lastseen=-389780.4hrs
connection timeout
trying connection 87.161.65.18:41682 lastseen=-27845.4hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001038c5e534d4f3 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000001a252c674d117 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000019f1ab36c0c76b limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000018a382f520379d limit 262653
  likely old client, incrementing misbehaviour count.trying connection 149.169.123.98:41682 lastseen=-389780.4hrs
connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000016db4fc1502c06 limit 262653
  likely old client, incrementing misbehaviour count.trying connection 67.9.132.6:41682 lastseen=-28305.5hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001508e9f8256bcd limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000003c88f63ab7ac7 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001511c49242dbd8 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001942cbec784fcb limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001e091563c8f8b7 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000002a7c5e0e83da3 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000071b67c4b2ddad limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 000000015125fa4b53b1 limit 262653
  likely old client, incrementing misbehaviour count.connection timeout
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000014fdecd50e5f57 limit 262653
  likely old client, incrementing misbehaviour count.trying connection 161.53.40.94:41682 lastseen=-389780.4hrs
connected 161.53.40.94:41682
connection timeout
socket closed
disconnecting node 161.53.40.94:41682
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 00000000b6fe366a154d limit 262653
  likely old client, incrementing misbehaviour count.trying connection 175.195.8.141:41682 lastseen=-389780.4hrs
trying connection 86.52.165.68:41682 lastseen=-28077.6hrs
  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000fd4973700c114 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000001ce878a1225760 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)


************************
EXCEPTION: St9bad_alloc       
std::bad_alloc       
slimcoin in ThreadMessageHandler()       

At first lines you can read that getblock fuction is trying to get block on packets of 500. Suddlenly it reset the count and start again, from block 1... in this case packets of 262653 blocks. Here´s:

Code:
getblocks 253404 to 3bfbb86e0474e8dfb756 limit 500
  getblocks stopping at limit 253903 0000000942578c720b5f (0 bytes)
getblocks 253404 to 64d9ae181c771879b0b2 limit 500
  getblocks stopping at limit 253903 0000000942578c720b5f (0 bytes)
getblocks 1 to 0000000f0c1baa5f2ec8 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000e63eee9fb2b62 limit 262653
  likely old client, incrementing misbehaviour count.  getblocks stopping at limit 262653 0000000b2920ce6ec7c0 (0 bytes)
getblocks 1 to 0000000c8f10b8c2133a limit 262653

In few secons it consumes all memory (I have saw with htop how slimcoind got full about 600Mb of ram a 1024Mb of swap file just before throw the faliure and finally crash:

Code:
EXCEPTION: St9bad_alloc       
std::bad_alloc       
slimcoin in ThreadMessageHandler() 

I have been locking for the code that generate the getblock fuction... I think it´s that, in main.cpp

https://github.com/slimcoin-project/Slimcoin/blob/slimcoin/src/main.cpp#L3691

But my programmings skills are so limited, I don´t know c or c++ but i can read it hardly.

Somebody could read it to get an idea about the failure?
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 18/08/2017, 12:52:43 UTC
Quote from: gjhiggins on August 17, 2017, 03:23:01 PM
Quote from: aIA on August 17, 2017, 10:40:38 AM
Anybody are suffering the same symptoms?

Yes. eliteyo is.

I wonder if it's possibly due to platform+OS differences in C++ implementation:

https://github.com/slimcoin-project/Slimcoin/commit/8e9fe2c832e62ba60dc57aacef52918ba2d115fb#diff-7ec3c68a81efff79b6ca22ac1f1eabbaL5306

I doubt I can replicate on a VM. If anyone's experiencing that problem and is compiling natively for Windows, does reverting that line to the C99 macro fix it?

Cheers

Graham

Quote from: cryptovore on August 17, 2017, 04:13:06 PM
The Slimcoin version 0.5.0 is not working properly on any of my ARM boards (Raspberry Pi & Odroid XU4) even if I manage to compile it properly. It crashes randomly and my debugging skills got me as far as dumping a core and investigating the stack frames, but no useful thing came out of this.

My hunch is that it may have something to do with the boost libraries. But I may be wrong.

In have just found this doc on github about compiling bitcoin for differents platforms.


https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

Take a look at the section "ARM Cross-compilation".

Could anybody try it? Maybe I could try this weekend.

Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 17/08/2017, 12:31:57 UTC
Quote from: gavrilo77 on August 16, 2017, 08:54:43 PM
I dont understand something:

Explorers on slimcoin.info and Bchain.info showing different things for the same blocks?

I think all it´s correct... explorer on Slimcoin.club sometime not showing you the block you select... example: you select 1076472 and it show you "height": 1076476". Make sure it´s showing the block you desire.
Post
Topic
Re: Slimcoin | First Proof of Burn currency | Test v0.5 release candidates
by
aIA
on 17/08/2017, 10:40:38 UTC
Quote from: gavrilo77 on August 16, 2017, 06:55:59 PM
Quote from: aIA on August 16, 2017, 06:49:36 PM
Quote from: gavrilo77 on August 16, 2017, 04:58:11 PM

Try with this:

sudo apt-get install git build-essential libssl-dev libdb5.3++-dev libminiupnpc-dev libboost-all-dev qt5-qmake libqt5gui5 qt5-default qtdeclarative5-dev qttools5-dev-tools libqt5dbus5
git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
cd src
make -f makefile.unix

Thank you so much!! It seems work perfectly!!!



You are welcome!!! Enjoy in SLM


Hi, today I have been done more intensive testing of Raspi Slimcoin daemon and it crash every time it try to do PoB, I think. My wallet it's encrypted, I have burnt some coins on windows client before copy Blockchain and wallet files to Raspberry. Trying to mint by burn with Pi, I unlock wallet with "./slimcoind walletpassphrase pass 100000 true" and immediately it crash.... there's last lines of debug.log:

Code:
trying connection 39.50.208.44:41682 lastseen=-15495.2hrs
connection timeout
trying connection 173.102.114.151:41682 lastseen=-26962.5hrs
ThreadRPCServer method=walletpassphrase
connection timeout
SlimCoinAfterBurner():
        Smallest Hash is 0000003138af0000000000000000000000000000000000000000000000000001
        by tx 1f1b6e070f59560cb86d919d2f37faeac9faafb5f51762cc46b16e5b11d45c89
        with Block height 976294, transaction depth 2, vout depth 1
        PoB Tartget is 0000000088be0000000000000000000000000000000000000000000000000000
pi@PiServer:~/hdd1/Slimcoin $

Anybody are suffering the same symptoms?