[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[cryptonit]

@cryptonit
How is your sync going?  

half way done
had a few crashes of the PI2 and lost days
i run the PI2 now without overclock and in console mode only lets see if that was the issue

[1715537357]

1715537357

[1715537357]

1715537357

[utahjohn]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

[cryptonit]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

[utahjohn]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

[cryptonit]

thats not what feldenthorn said......

[utahjohn]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

if I modify diamond.pro and makefile.unix as suggested change armv7l references to aarch64
I get a very similar problem in scrypt_mine.cpp

error: 'SCRYPT_BUFFER_SIZE' not declared
and
error: 'scrypt_core' was not declared

I am quite certain although unable to fix this that the problem is in scrypt-arm.S or scrypt_mine.cpp and that cpu not being selected properly, so scrypt_core() not being generated.

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

around line 73 of scrypt_mine.cpp:
insert to the #elif the following
 ||defined(__aarch64__)

this gets past the SCRYPT_BUFFER_SIZE and scrypt_core() errors
but then I get back to this one again:
src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope
Makefile:302: recipe for target 'diamond-qt' failed

Clearly scrypt_core() is not being generated as we are now in linking phase of build ...

@danbi
HELP! LOL

[Hilux74]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

if I modify diamond.pro and makefile.unix as suggested change armv7l references to aarch64
I get a very similar problem in scrypt_mine.cpp

error: 'SCRYPT_BUFFER_SIZE' not declared
and
error: 'scrypt_core' was not declared

I am quite certain although unable to fix this that the problem is in scrypt-arm.S or scrypt_mine.cpp and that cpu not being selected properly, so scrypt_core() not being generated.

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

@danbi
HELP! LOL

Check that scrypt-arm.S is listed under SOURCES in the qt.pro file.

[utahjohn]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

if I modify diamond.pro and makefile.unix as suggested change armv7l references to aarch64
I get a very similar problem in scrypt_mine.cpp

error: 'SCRYPT_BUFFER_SIZE' not declared
and
error: 'scrypt_core' was not declared

I am quite certain although unable to fix this that the problem is in scrypt-arm.S or scrypt_mine.cpp and that cpu not being selected properly, so scrypt_core() not being generated.

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

@danbi
HELP! LOL

Check that scrypt-arm.S is listed under SOURCES in the qt.pro file.

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

around line 73 of scrypt_mine.cpp:
insert to the #elif the following
 ||defined(__aarch64__)

this gets past the SCRYPT_BUFFER_SIZE and scrypt_core() errors
but then I get back to this one again:
src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope
Makefile:302: recipe for target 'diamond-qt' failed

Clearly scrypt_core() is not being generated as we are now in linking phase of build ...

There is no qt.pro file just a diamond.pro used by qmake ...
But yes it is listed in diamond.pro

This I just received in email from  pooler@litecoinpool.org

As documented, there is no Aarch64 implementation in cpuminer.
I do plan to add one in the future, time allowing.

My email:

Have you updates this for aarch64 (armv8), I am failing to compile
DMDcoin/Diamond.git it fails when I get to the linking stage.]
file: scrypt-arm.S

So diamond team will have to update this for aarch64

somehow force build of scrypt-arm for aarch64 as armv7

my complete uname -a
Linux odroid64 3.14.29-37 #1 SMP PREEMPT Tue Mar 15 23:57:29 BRT 2016 aarch64 aarch64 aarch64 GNU/Linux

well this sucks, RPi3, Odroid C2, and any other aarch64 CPU out of luck

[utahjohn]

Well I got firefox working (was seg faulting).
solution:
 apt-get remove firefox
 apt-get install firefox:armhf

But no luck with diamond-qt.

Now I can copy/paste from odroid command line

build/scrypt_mine.o: In function `scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp:(.text+0x5c): undefined reference to `scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed
make: *** [diamond-qt] Error 1

this is caused by scrypt_core() not being compiled.
src/scrypt-arm.S does not support aarch64 (armv8).  

From crashoverride on forum.odroid.com

The .S files are unique to each processor architecture.   They are not interchangeable.  Someone will need to author a version of the .S file for aarch64 before it will work.

I'll bet DMD foundation would post a bounty for someone to create src/srcypt-aarch64.S
here is src/srcypt-arm.S as a starting point: https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S
This code is for arm 32 bit, needs to be translated to 64 bit ...

The other modifications to diamond.pro and src/makefile.unix are relativly simple just adding a few lines for aarch64 ...

If you are going to get one, they are sold-out until middle of April, however I found mine at USA distributor (may still be available there) http://ameridroid.com

Ubuntu 64 bit image for Odroid C2 is available here http://odroid.com/dokuwiki/doku.php?id=en:c2_release_linux_ubuntu

Debian 32 and 64 bit (ODROBIAN-Jessie-2.0-vanilla-s905.img.xz) image for Odroid C2 are available here http://forum.odroid.com/viewtopic.php?f=138&t=18771 (follow links to s905) http://oph.mdrjr.net/odrobian/images/s905/
For the Debian 32 version:

Linux Hybrid Kernel64/Debian32 (aka crashoverride edition)
-All remarks & features posted above apply exactly the same for this version except it's an ARMHF based system.
-This is basically a system with Linux Kernel 64bit running through Debian 32bit based rootfs.
-Maximum compatibility with ARMHF software built for previous ODROIDs meaning you can install anything.
-ARM64 is configured as a foreign architecture so you can also install 64bit applications.
-Hostname is "odroid32" unlike regular version which has "odroid64" instead.
-Some ARM64 packages are installed for kernel with other s905 specific ones to get updates from my repository.
-The idea is by @crashoverride.

I think I'd prefer Debian myself as raspbian is based on it and has lots of support.  Ordered a microSD card reader/writer on e-bay so I can re-flash my card ... and run crashoveride ... see if uname -p returns armv7 ... if so at least it's a temporary solution for DMD.

If you have not ordered yet, much cheaper from manufacturer in Korea http://www.hardkernel.com/main/main.php
Shipping from Korea to Utah, USA is $16 FEDEX (I bought the 32G Ubuntu 64 eMMC 5 card, power supply, case from them).

On another subject: bitcoind 12.0 build just fine on aarch64

[feldenthorne]

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

Thanks for bringing this up to me via PM, utahjohn.

I originally said that whatever returned after using uname -a was fine because we were talking about Raspberry Pis (1 and 2) and the makefile supports both armv6l and armv7l (which are actually identical). It's just not working with any of the previous architecture commands because of the 64-bit OS (see below).

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

It looks like you guys in the thread have already figured it out: someone will need to write a scrypt-aarch64.S file for everything to work smoothly.

Alternatively, I could probably have the wallet fall back to a C++ implementation on unsupported architectures. It would just need to be transparent to the users that their architecture does not perform as well as it might with its own assembly implementation. (That is to say that the performance would be really bad compared to a native solution.)

Speaking of performance hits, though, I'm pretty sure one could the ARM version of QEMU to run a 32-bit binary if you just want to run the wallet on an arm64 board. At least until a more robust solution is found. A guide for setting QEMU up on a Raspberry Pi can be found here, but I'm not sure how well that translates to ODROID's boards. You might have to set up ODROID's boards for virtualization (if they support it) and compile QEMU yourself to get things working.

[utahjohn]

It looks like you guys in the thread have already figured it out: someone will need to write a scrypt-aarch64.S file for everything to work smoothly.

Alternatively, I could probably have the wallet fall back to a C++ implementation on unsupported architectures. It would just need to be transparent to the users that their architecture does not perform as well as it might with its own assembly implementation. (That is to say that the performance would be really bad compared to a native solution.)

Speaking of performance hits, though, I'm pretty sure one could the ARM version of QEMU to run a 32-bit binary if you just want to run the wallet on an arm64 board. At least until a more robust solution is found. A guide for setting QEMU up on a Raspberry Pi can be found here, but I'm not sure how well that translates to ODROID's boards. You might have to set up ODROID's boards for virtualization (if they support it) and compile QEMU yourself to get things working.

need scrypt-aarch64.S for it to really be a solution ...

scrypt-arm.S is taken from pooler cpuminer (pooler@litcoinpool.com) and he said:

As documented, there is no Aarch64 implementation in cpuminer.
I do plan to add one in the future, time allowing.

I'm also working with OKtoshi on ROKOS for aarch64 however he does not have a board yet ...
https://bitcointalk.org/index.php?topic=1084908.msg14308714#msg14308714

I'll bet DMD foundation would post a bounty for someone to create src/srcypt-aarch64.S
here is src/srcypt-arm.S as a starting point: https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S

With the release of RPi 3 out and PINE64+ imminent, there is going to be a large demand for aarch64 support.
I'm lucky to have got the Odroid C2 board, they are sold-out till mid-April.  Specs are quite similar on all Only the Odroid C2 has 2 GHZ though

I PM'ed pallas too but have not got a reply, he's into stuff like this I think ...

Should PM wolf0 too

By the way, who is DMD wallet dev nowadays ... used to be danbi but we don't hear from him much at all ...

another review:
http://www.jeffgeerling.com/blog/2016/review-odroid-c2-compared-raspberry-pi-3-and-orange-pi-plus

[utahjohn]

The point is building the DMD wallet for aarch64, currently there is no support.
It all worked fine for armv6, armv7 but broke when aarch64 came along.  the reference to pooler cpuminer is because he is the author of scrypt-arm.S there is NO scrypt-aarch64.S which is required to build DMD.

I could care less about mining on an armv8 LOL.

However you do know a lot about mining and it seems also armv8

scrypt-aarch64.S is only thing holding me up from building diamond-qt and it DOES NOT exist yet ...

I am not much of a programmer (some x86 assembly years ago) and know absolutely nothing about aarch64 (armv8) or armv6 or 7.

[utahjohn]

It looks like you guys in the thread have already figured it out: someone will need to write a scrypt-aarch64.S file for everything to work smoothly.

Alternatively, I could probably have the wallet fall back to a C++ implementation on unsupported architectures. It would just need to be transparent to the users that their architecture does not perform as well as it might with its own assembly implementation. (That is to say that the performance would be really bad compared to a native solution.)

Speaking of performance hits, though, I'm pretty sure one could the ARM version of QEMU to run a 32-bit binary if you just want to run the wallet on an arm64 board. At least until a more robust solution is found. A guide for setting QEMU up on a Raspberry Pi can be found here, but I'm not sure how well that translates to ODROID's boards. You might have to set up ODROID's boards for virtualization (if they support it) and compile QEMU yourself to get things working.

need scrypt-aarch64.S for it to really be a solution ...

scrypt-arm.S is taken from pooler cpuminer (pooler@litcoinpool.com) and he said:

As documented, there is no Aarch64 implementation in cpuminer.
I do plan to add one in the future, time allowing.

I'm also working with OKtoshi on ROKOS for aarch64 however he does not have a board yet ...
https://bitcointalk.org/index.php?topic=1084908.msg14308714#msg14308714

I'll bet DMD foundation would post a bounty for someone to create src/srcypt-aarch64.S
here is src/srcypt-arm.S as a starting point: https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S

With the release of RPi 3 out and PINE64+ imminent, there is going to be a large demand for aarch64 support.
I'm lucky to have got the Odroid C2 board, they are sold-out till mid-April.  Specs are quite similar on all Only the Odroid C2 has 2 GHZ though

I PM'ed pallas too but have not got a reply, he's into stuff like this I think ...

Should PM wolf0 too

By the way, who is DMD wallet dev nowadays ... used to be danbi but we don't hear from him much at all ...

another review:
http://www.jeffgeerling.com/blog/2016/review-odroid-c2-compared-raspberry-pi-3-and-orange-pi-plus

@feldenthorn
If you can give me example C++ code for maybe I can create aarch64 assembly code from it (I have been looking at several arm 32 bit to aarch64 sites), may not be optimized to the max but just need to get wallet to build for now.  Hell of a way to learn LOL.
I can probably do a side-by-side C++ to assembly code and later tune it with loop un-rolling etc.

u could put C++ fallback code for scrypt_core() in scrypt_mine.cpp, this is where it is used and defined as extern "C".

[cryptonit]

while testing the ROKOS on a raspberry PI2 i will also testing cheap windows10 tablet as a staking solution

will try out this 88€ tablet with 2 GB ram and windows 10
http://www.notebooksbilliger.de/mp+man+mpw815+windows+tablet

just ordered

[cesmak]

while testing the ROKOS i will also testing cheap windows10 tablet as a staking solution

will try out this 88€ tablet with 2 GB ram and windows 10
http://www.notebooksbilliger.de/mp+man+mpw815+windows+tablet

just ordered

Interesting... let all know how it works.... when arrives and set it up....

[galacticpilgrim]

while testing the ROKOS i will also testing cheap windows10 tablet as a staking solution

will try out this 88€ tablet with 2 GB ram and windows 10
http://www.notebooksbilliger.de/mp+man+mpw815+windows+tablet

just ordered

Interesting... let all know how it works.... when arrives and set it up....

That looks good. I need to find one like that in the US..

[metamorphin]

while testing the ROKOS on a raspberry PI2 i will also testing cheap windows10 tablet as a staking solution

will try out this 88€ tablet with 2 GB ram and windows 10
http://www.notebooksbilliger.de/mp+man+mpw815+windows+tablet

just ordered

I am very excited about your results. I am sure, you will find a way for the "little" pocket.

steve

[cryptonit]

hey folks, would you mind to pay a little for presstab explorer ?
( i've another coins to care for )

DMD Diamond Foundation keep
https://chainz.cryptoid.info/dmd/
explorer running

still help is welcome

Hosting can be extended by a donation to
BTC:   1LER8Tt5Y2LV987fYkY1cPFuXbLgGy3kaS



other explorers like presstab are community effort

[cryptonit]

while testing the ROKOS i will also testing cheap windows10 tablet as a staking solution

will try out this 88€ tablet with 2 GB ram and windows 10
http://www.notebooksbilliger.de/mp+man+mpw815+windows+tablet

just ordered

Interesting... let all know how it works.... when arrives and set it up....

That looks good. I need to find one like that in the US..

maybe this?
CHUWI Hi8 8 inch Windows 10/Android 4.4 Dual Boot Tablet PC, with Features of Intel Quad Core, Full HD 1920*1200 IPS Screen, 2G RAM/32G ROM and Winkey
http://www.amazon.com/Windows-Android-Tablet-Features-Screen/dp/B01AN6BBKI

[cryptonit]

there is people asking us how dmd cloudmining can generate payouts
even if nearly all but the newest generation of mining gear is running unprofitable this days

the answer is easy DMD Cloudmining dynamic place and shift value between different kind of payout generating crypto investments
and that not only cloudmining hashrate its also staking coins and crypto lending and similar investment

and addtional we have the regulary DMD reaktor payout that give sweet bonus payouts to DMD cloudmining shareholders

--------------------------------

DMD MULTIPOOL / DMD CLOUDMINING
Visit us:  cloudmining.bit.diamonds

redistributed over 217000 DMD! between its users!
yes thats close to 15% of total coins!


---------------------


---------------------------------------------------------
ROI Boost enabled now:
All accounts who didnt reach ROI 100%
will be boosted with x5 sharepower!
--------------------------------------------------------

(https://cloudmining.bit.diamonds/ log in with DMD Address and activate settings area to enable buy shares mode)


NO Electricity Bills                                
  NO Maintenance                                    
    NO Heat                                                
      NO Noise                                              
        NO Timesink                                        
          NO Complicated technology                
            NO Quickly decreasing mining rewards

Join DMD Cloudmining
     -> EARN DMD EACH DAY!
                    
                   YES!

(additional DMD Cloudmining shares qualify for DMD Reactor  payouts!

Visit us:  cloudmining.bit.diamonds
terms & conditions Terms of Service
for questions Email us: cloud@bit.diamonds

      


What's the best way join into DMD Diamond and DMD Cloudmining?

I suggest split it as follows:

 a) 50% on buying Diamonds directly
 b) 50% in Diamond Cloud Mining.

 This way I could achieve both maximizing the profit and stabilizing the coin.
 Diamond Cloud Mining can earn Diamonds every day, those Diamonds stake with 50% PoS interest.
 Some would call that Double PoS or simply PoS² (Proof of Shares and Proof of Stake).


Step by Step guide how to buy shares is at FAQ section on https://cloudmining.bit.diamonds/



I am not a Registered Investment Advisor, Broker/Dealer, Financial Analyst, Financial Bank, Securities Broker or Financial Planner. The Information is provided for information purposes only. The Information is not intended to be and does not constitute financial advice or any other advice, is general in nature and not specific to you. Before using this information to make an investment decision, you should seek the advice of a qualified and registered securities professional and undertake your own due diligence. None of the information is intended as investment advice, as an offer or solicitation of an offer to buy or sell, or as a recommendation, endorsement, or sponsorship of any security, Company, or fund. DMD Diamond is not a regulated investment vehicle. DMD Diamond, like all crypto currencies, is experimental in nature and should be considered and treated with appropriate caution. There is no central point of control or representative entity, DMD Diamond is a distributed decentralized peer-to-peer currency and commodity. Consult a licensed professional financial advisor before making any investment decisions. I am not responsible for any investment decision made by you. You are responsible for your own investment research and investment decisions.

--------------
--------------

Just in case someone missed this now DMD Multipool mining become easy for everyone!
Working on Nvidia AND AMD based cards!

here come the new nicehash miner tool
https://github.com/nicehash/NiceHashMiner/releases

just use ur https://multipool.bit.diamonds/
BTC address attached to ur registered DMD address
as mining address in nicehashminer and u will earn DMD payouts
provided by our fee free convertion service