Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Changing the hashing algorithm

    Technical Development
    58
    482
    344715
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MrWyrm
      MrWyrm administrators last edited by

      Having support for all the camps from the off will make for a stronger launch.

      Like what I do: 6uuy6isbrW1SBF191Bzgui1gWxPdNKx2PB

      1 Reply Last reply Reply Quote 0
      • kris_davison
        kris_davison last edited by

        I’m hoping we can deal with cudaminer (or sponsor/commission the guys who wrote it to implement neoscrypt?) Again I would be happy to chip in as I am one of the many who would benefit from nvidia support!

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User last edited by

          I’m curios as to how Neo would work out on nVidia… x11 seems to have an advantage with em, could this be the case here?

          1 Reply Last reply Reply Quote 0
          • ghostlander
            ghostlander Regular Member last edited by

            NeoScrypt P2Pool module is ready. P2Pool works on a fake testnet using CPUminer.

            1 Reply Last reply Reply Quote 0
            • V
              voingiappone Regular Member last edited by

              So, ghostlander… now we need to modify the scrypt module in cg/sg-miner.

              I’ve been watching/messing out with the sph-sgminer for Darkcoin as I wanted to modify the algo (I’ll do wathever if it can distract me from my thesis! ;) ). For what I see, it’s enough to exactly “replicate” the algo from the hashing.cpp (in the wallet) to the algo.c file in the root directory. But I may be off-track… Do you think that’s the right path?

              I mean, some optimization should be done (I don’t know where to start) but having a working GPU miner (albeit a non-opt one) from day one looks like a very good start, don’t you think?

              So, the big question is: who is doing this? Is the algo accessible or is it still in a top secret state?

              1 Reply Last reply Reply Quote 0
              • lizhi
                lizhi last edited by

                Suffered a setback . :(

                I’m compiling cgminer on win32(x86) . My IDE is Visual Studio 2013 . After I add neoscrypt.cpp and neoscrypt.h to the cgminer.vcxproj, then compily it .

                But I get a lot of errors:

                ROTL32, Identifier not found

                SCRYPT_BLOCK_SIZE ,Undeclared identifier

                stack, Unknown size

                error_n.jpg

                1 Reply Last reply Reply Quote 0
                • ghostlander
                  ghostlander Regular Member last edited by

                  This is because NeoScrypt is supposed to be compiled by a C compiler, not a C++ one. The work-around is in a PM.

                  1 Reply Last reply Reply Quote 0
                  • wrapper
                    wrapper Moderators last edited by

                    Great work on the algo change. Looks like it might be worth haveing a p2pool test site, with all miner updates needed.

                    1 Reply Last reply Reply Quote 0
                    • V
                      vizay Regular Member last edited by

                      I believe it’s of very great importance that we don’t forget the nvidia cards out there, we want to be open and welcoming to all miners as fast as possible after release :)

                      1 Reply Last reply Reply Quote 0
                      • wrapper
                        wrapper Moderators last edited by

                        most of my GPUs have blown up in the last 2 months.

                        1 Reply Last reply Reply Quote 0
                        • wrapper
                          wrapper Moderators last edited by

                          One thing I have noticed running feathercoind and other coin daemons on a p2pool with tight memory. The 0.6 series daemon takes 190 MB compared to the 0.8 which are more like 230 MB. (can vary higher)

                          Both of which seems higher than they need…

                          That won’t be directly related to the algorythm, but the pool daemon pass round the work, so its something that might be “optimisation” In the builds.

                          Whilst we’re considering testing / improving performance.

                          1 Reply Last reply Reply Quote 0
                          • Wellenreiter
                            Wellenreiter Moderators last edited by

                            I had a mail chat with one of the authors of cudaminer.
                            He is interested to add neoscrypt to cudaminer, but he can’t make it happen soon.

                            Feathercoin development donation address: 6p8u3wtct7uxRGmvWr2xvPxqRzbpbcd82A
                            Openpgp key: 0x385C34E77F0D74D7 (at keyserver.ubuntu.com)/fingerprint: C7B4 E9EA 17E1 3D12 07AB 1FDB 385C 34E7 7F0D 74D7

                            1 Reply Last reply Reply Quote 0
                            • ghostlander
                              ghostlander Regular Member last edited by

                              One thing I have noticed running feathercoind and other coin daemons on a p2pool with tight memory. The 0.6 series daemon takes 190 MB compared to the 0.8 which are more like 230 MB. (can vary higher)

                              Block index is held in memory. More blocks in main chain = more memory consumed.

                              1 Reply Last reply Reply Quote 0
                              • V
                                vizay Regular Member last edited by

                                I had a mail chat with one of the authors of cudaminer.
                                He is interested to add neoscrypt to cudaminer, but he can’t make it happen soon.

                                Is there someone official behind the ccminer? That’s also a viable option for nvidia and perhaps he/she/they have more time to add NS? :)

                                1 Reply Last reply Reply Quote 0
                                • lizhi
                                  lizhi last edited by

                                  I had compily cgminer 3.6.6 with MinGW . It can work with scrypt and keccak. But that work add neoscrypt is very complex and arduous . May God bless us !

                                  ------------------------------------------------------------------------
                                  cgminer 3.6.6
                                  ------------------------------------------------------------------------
                                  
                                  
                                  Configuration Options Summary:
                                  
                                    libcurl(GBT+getwork).: Enabled: -L/usr/local/curl/lib
                                    curses.TUI...........: FOUND: -lpdcurses
                                    OpenCL...............: FOUND. GPU mining support enabled
                                    scrypt...............: Enabled
                                    keccak...............: Enabled
                                    ADL..................: SDK found, GPU monitoring support enabled
                                  
                                    Avalon.ASICs.........: Disabled
                                    BFL.ASICs............: Disabled
                                    BitForce.FPGAs.......: Disabled
                                    BitFury.ASICs........: Disabled
                                    Icarus.FPGAs.........: Disabled
                                    Klondike.ASICs.......: Disabled
                                    ModMiner.FPGAs.......: Disabled
                                  
                                  Compilation............: make (or gmake)
                                    CPPFLAGS.............:
                                    CFLAGS...............: -O2 -msse2
                                    LDFLAGS..............:
                                    LDADD................:  -L/usr/local/curl/lib compat/jansson-2.5/src/.libs/lib
                                  jansson.a -lpthread -lOpenCL   -lws2_32 -lm
                                  
                                  Installation...........: make install (as root if needed, with 'su' or 'sudo')
                                    prefix...............: /usr/local
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • V
                                    voingiappone Regular Member last edited by

                                    Ok… so I definitely missed something: where do I find the files for the neoscrypt?

                                    1 Reply Last reply Reply Quote 0
                                    • lizhi
                                      lizhi last edited by

                                      Step by Step ,

                                      I had compily cgminer 3.6.6 with neoscrypt on MinGW. I set --enable-neoscrypt , Compile support for neoscrypt feathercoin mining.

                                      I get cgminer-neoscrypt.o and cgminer.exe .

                                      Next, there is still a very large number of hard work. Wish me good luck.

                                      neoscrypt.jpg

                                      neoscrypt2.jpg

                                      1 Reply Last reply Reply Quote 0
                                      • kris_davison
                                        kris_davison last edited by

                                        wow thats amazing progress well done. I can feel a tip coming on!

                                        1 Reply Last reply Reply Quote 0
                                        • lizhi
                                          lizhi last edited by

                                          wow thats amazing progress well done. I can feel a tip coming on!

                                          We have not an OpenCL kernel, there is still a very hard work.

                                          1 Reply Last reply Reply Quote 0
                                          • ChekaZ
                                            ChekaZ last edited by

                                            Great job lizihi! :)

                                            BTC: 1Ges1taJ69W7eEMbQLcmNGnUZenBkCnn45
                                            FTC: 6sxjM96KMZ7t4AmDTUKDZdq82Nj931VQvY

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post