 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
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 |
|
|
|
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 |
|
|
|
Hello again, ...what process should I use to validate that the binaries don't contain malware?
I basically want my binarys independently scanned with something like AVG antivirus for example, to ensure that they are not malicious and hence any user can trust them. Regards |
|
|
|
|
Hello again,
I have finally managed to successfully compile an ARM QT client for armhf (arm-v7). If you could tell me how to make this available for others, please let me know. I intend to follow this up with a CLI client and also clients for armel (arm-v5) and arm-v8.
Regarding the POS block generation method in Slimcoin, I was wondering whether a swtich to something like proof-of-stake-time (POSt) as implemented in Verium, would suite Slimcoin better and make it less vulnerable to issues when holders stake only every 90 days, creating huge block rewards.
Regards
|
|
|
|
tell me if it's still possible to mining in cpu? my pc is gtx1060 and with cpu I7 -4900k , please give me advice which pool works fine
Yes I am currently mining solo on a CPU. I believe that there are currently no pools, so solo will be the only option for the moment. |
|
|
|
The POW isn't regular scrypt. right?
Yes right, the algorithm is dcrypt rather than scrypt. I get something like 15-20 time the hashrate from the external miner from the link above compared to the wallet miner, so if you can, I would definitely recommend compiling and using that as you will have a far better chance of finding blocks. Regards |
|
|
|
|
Hello gjhiggins,
Just a quick update. I have been evaluating a few ways of compiling for arm devices, and it looks like one of the best ways may well be to cross compile Slimcoin's dependencies and use those to cross-compile the client itself. Any thoughts?
Regards.
|
|
|
|
Thanks for the update To answer this comment: The reason for wanting to use Arch Linux is that it is the most recent OS (ie. more recent than ubuntu 15.04) that will run on an orange pi, and I am using an orange pi for compilation because then I have qt and other librarys avaliable for arm. Search results are instructive. Optimisation is architecture-specific, so you'll need to use the appropriate flags.
Thanks for the help, but I just tried compiling with -march=native and it is still having segmentation faults. Regards |
|
|
|
|
Glad to be of assistance to you in connecting!
|
|
|
|
This: [
{
"addr" : "37.187.100.75:41682",
"services" : "00000001",
"lastsend" : 1508320014,
"lastrecv" : 1508320015,
"conntime" : 1508318502,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 1135271,
"banscore" : 0
},
{
"addr" : "144.76.64.49:41682",
"services" : "00000001",
"lastsend" : 1508319408,
"lastrecv" : 1508320356,
"conntime" : 1508318503,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-3-g43621dd-dirty-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 1135271,
"banscore" : 0
},
{
"addr" : "5.9.39.9:41682",
"services" : "00000001",
"lastsend" : 1508320377,
"lastrecv" : 1508320385,
"conntime" : 1508318531,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.1(SLMv0.4.1-alpha-62-g97dfe67-dirty-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 1135271,
"banscore" : 0
},
{
"addr" : "185.68.67.37:41682",
"services" : "00000001",
"lastsend" : 1508320376,
"lastrecv" : 1508320378,
"conntime" : 1508318532,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-15-g2668a530-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 1135271,
"banscore" : 0
},
{
"addr" : "88.0.89.0:41682",
"services" : "00000001",
"lastsend" : 1508320086,
"lastrecv" : 1508320357,
"conntime" : 1508318549,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-23-g49b72b8-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 1135271,
"banscore" : 0
},
{
"addr" : "85.10.208.71:41682",
"services" : "00000001",
"lastsend" : 1508318597,
"lastrecv" : 1508319292,
"conntime" : 1508318596,
"version" : 60004,
"subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.0(SLMv0.4.1-alpha-8-g79cecee-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 1127614,
"banscore" : 0
},
{
"addr" : "204.236.246.48:41682",
"services" : "00000001",
"lastsend" : 1508320385,
"lastrecv" : 1508320386,
"conntime" : 1508319888,
"version" : 60003,
"subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-36-gee58cfb-alpha)/",
"inbound" : false,
"releasetime" : 0,
"height" : 315045,
"banscore" : 0
}
]
Regards |
|
|
|
Hello wDUO, Have you tried the set available from the link on the original post on this thread? Here is the link https://justpaste.it/1bcq1Regards |
|
|
|
Thanks gjhiggins! It compiles on my system now. I will now start work on compiling the daemon for arm devices as mentioned as needed in the bounty section in the first post on this thread. I have another question. When I compile I get this warning from the compiler: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
I tried to compile with optimisation recently, but the compiled binary immediately had a segmentation fault when run. Is there a known cause for this and does something need to be done about it? Regards |
|
|
|
Hello, Thanks for the quick code updates. Yes, you were correct that I was mainly wanting to work with a working codebase, but I would also like to learn how the whole system works too. I have tested the changes you made, but unfortunately on my system there are still errors when compiling, as follows: src/key.cpp: In member function ‘bool CKey::SetCompactSignature(uint256, const std::vector<unsigned char>&)’:
src/key.cpp:380:30: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
BN_bin2bn(&vchSig[1],32,sig->r);
^~
In file included from /usr/include/openssl/ecdsa.h:10:0,
from src/key.cpp:9:
/usr/include/openssl/ec.h:1039:16: note: forward declaration of ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
typedef struct ECDSA_SIG_st ECDSA_SIG;
^~~~~~~~~~~~
src/key.cpp:380:32: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
BN_bin2bn(&vchSig[1],32,sig->r);
^
In file included from /usr/include/openssl/ecdsa.h:10:0,
from src/key.cpp:9:
/usr/include/openssl/ec.h:1039:16: note: forward declaration of ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
typedef struct ECDSA_SIG_st ECDSA_SIG;
^~~~~~~~~~~~
src/key.cpp:381:31: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
BN_bin2bn(&vchSig[33],32,sig->s);
^~
In file included from /usr/include/openssl/ecdsa.h:10:0,
from src/key.cpp:9:
/usr/include/openssl/ec.h:1039:16: note: forward declaration of ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
typedef struct ECDSA_SIG_st ECDSA_SIG;
^~~~~~~~~~~~
src/key.cpp:381:33: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
BN_bin2bn(&vchSig[33],32,sig->s);
^
In file included from /usr/include/openssl/ecdsa.h:10:0,
from src/key.cpp:9:
/usr/include/openssl/ec.h:1039:16: note: forward declaration of ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
typedef struct ECDSA_SIG_st ECDSA_SIG;
^~~~~~~~~~~~
make: *** [Makefile:2269: build/key.o] Error 1
This was on an up to date Arch Linux system. I did have to modify this file quite significantly to get it to compile on my system. Regarding this comment, I'm re-checking the build under Jessie (yep, it all compiles, tests pass) and have a Vagrant Arch Linux box, so I can have a play with a modified version of Peercoin's PKGBUILD file.
Does this mean that you will provide AUR packages for Arch Linux or will I still need to do so? Here is the thread where I foud the fix if it is any use: https://github.com/peercoin/peercoin/pull/153?Regards |
|
|
|
Hello gjhiggins, Firstly, thank you for taking the time to respond. In answer to this question:
Would I be correct in inferring that this issue is specific to the Arch Linux distro and not a general issue? Either way, more info would be most useful to me, at least.
No, I belive it affects debian jessie, ie. debian 8, as well. I would imagine that it affects any distribution that uses openSSL1.1, but without further research I could not say for certain. This issue was raised earlier in the thread as well: Debian 8 x64 - still crashing with: from src/bitcoinrpc.cpp:8:
src/bignum.h:52:24: error: invalid use of incomplete type ?BIGNUM {aka struct bignum_st}?
class CBigNum : public BIGNUM
Known bug with Debian 8 apparently: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855574Cheers Graham To answer your second question: What's the most convenient way for you to proceed, as a Slimcoin developer focusing on Arch Linux and devices?
Firstly, I must point out that I will not have much time to work on this for several weeks, however that is currently not an issue as I am testing my code and as the first stage of that is I am waiting for the node to sync. I cannot do anything else until that finishes. From there I would proceed to test all features of the wallet possible, and once all features have been shown to work I intend to submit a pull request to the repository. If you would like me to make this pull request sooner so that you and others can review my code and commence testing I would be happy to do so. I am trying to learn how to use git and github so I will need some help. I created a new branch on my local git reposity to make the changes to so that may make it easier to pull as it will not change the current master branch but will allow others to test and review my code, is this a suitable way to do it? Once the SSL fix is in place I would then proceed to phase two which would be to provide precompiled binarys and make these binary available on the Arch Linux AUR. One other issue that I may need to address is backwards compatability. By the way, I am still very much in the process of learning how to program, so code changes will take me a comparitively long time to accomplish, however I am trying to pick it up along the way. I am also trying to familiarise myself with the infrastrucutre underlying cryptocurrencies. I will now add peerbox to my list of things to investigate. If you need more information about what I am saying don't hesitate to ask. Regards |
|
|
|
|
Hello all yet again,
I just wanted to say a Thank You to gjhiggins, muf18, and all the others involved with Slimcoin for providing a friendly and helpful community and prompt responses to those who are trying to get into this coin.
If you have any issues with any of my posts such as missing or false information, feel free to let me know as I am new to the forum system.
Regards
|
|
|
|
No, you were not wrong. After you cloned the repository you need to enter the directory and run the following command to use the master branch: Regards |
|
|
|
Hello again, I have had the error you mentioned before about net.cpp:56:1: error: reference to ‘array’ is ambiguous
several times and for me it was usually caused by not checking out the master branch on the github repository. If you need more information I would recommend that you read the initial post on this thread, if you have not done so already. Regards. |
|
|
|
|
