Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 333. (Read 1260624 times)
March 30, 2016, 03:50:43 PM
March 30, 2016, 03:48:52 PM
March 30, 2016, 10:18:28 AM
as pump defence place some sellorders between 0.00090 and 0.00125
else we might see a price spike.......
our liquidity suffer if not enough DMD available to be bought
YES thats DMD
here we try to avoid pumps
not many coins even aware that
liquidity not only means coins can be sold without big drop price
liquidity also means coins can be bought without raise the price to much
else we might see a price spike.......
our liquidity suffer if not enough DMD available to be bought
YES thats DMD
here we try to avoid pumps
not many coins even aware that
liquidity not only means coins can be sold without big drop price
liquidity also means coins can be bought without raise the price to much
March 30, 2016, 01:20:46 AM
Can anyone can translate to NEON instructions in C?
https://community.arm.com/groups/android-community/blog/2015/03/27/arm-neon-programming-quick-reference
I put it in scrypt_mine.cpp to run DMD wallet, it is far from optimized and ARMv8 supports NEON.
https://community.arm.com/groups/android-community/blog/2015/03/27/arm-neon-programming-quick-reference
I put it in scrypt_mine.cpp to run DMD wallet, it is far from optimized and ARMv8 supports NEON.
Code:
#if defined(__aarch64__)
static inline void xor_salsa8(uint32_t B[16], const uint32_t Bx[16])
{
uint32_t x00,x01,x02,x03,x04,x05,x06,x07,x08,x09,x10,x11,x12,x13,x14,x15;
int i;
x00 = (B[ 0] ^= Bx[ 0]);
x01 = (B[ 1] ^= Bx[ 1]);
x02 = (B[ 2] ^= Bx[ 2]);
x03 = (B[ 3] ^= Bx[ 3]);
x04 = (B[ 4] ^= Bx[ 4]);
x05 = (B[ 5] ^= Bx[ 5]);
x06 = (B[ 6] ^= Bx[ 6]);
x07 = (B[ 7] ^= Bx[ 7]);
x08 = (B[ 8] ^= Bx[ 8]);
x09 = (B[ 9] ^= Bx[ 9]);
x10 = (B[10] ^= Bx[10]);
x11 = (B[11] ^= Bx[11]);
x12 = (B[12] ^= Bx[12]);
x13 = (B[13] ^= Bx[13]);
x14 = (B[14] ^= Bx[14]);
x15 = (B[15] ^= Bx[15]);
for (i = 0; i < 8; i += 2) {
#define R(a, b) (((a) << (b)) | ((a) >> (32 - (b))))
/* Operate on columns. */
x04 ^= R(x00+x12, 7); x09 ^= R(x05+x01, 7);
x14 ^= R(x10+x06, 7); x03 ^= R(x15+x11, 7);
x08 ^= R(x04+x00, 9); x13 ^= R(x09+x05, 9);
x02 ^= R(x14+x10, 9); x07 ^= R(x03+x15, 9);
x12 ^= R(x08+x04,13); x01 ^= R(x13+x09,13);
x06 ^= R(x02+x14,13); x11 ^= R(x07+x03,13);
x00 ^= R(x12+x08,18); x05 ^= R(x01+x13,18);
x10 ^= R(x06+x02,18); x15 ^= R(x11+x07,18);
/* Operate on rows. */
x01 ^= R(x00+x03, 7); x06 ^= R(x05+x04, 7);
x11 ^= R(x10+x09, 7); x12 ^= R(x15+x14, 7);
x02 ^= R(x01+x00, 9); x07 ^= R(x06+x05, 9);
x08 ^= R(x11+x10, 9); x13 ^= R(x12+x15, 9);
x03 ^= R(x02+x01,13); x04 ^= R(x07+x06,13);
x09 ^= R(x08+x11,13); x14 ^= R(x13+x12,13);
x00 ^= R(x03+x02,18); x05 ^= R(x04+x07,18);
x10 ^= R(x09+x08,18); x15 ^= R(x14+x13,18);
#undef R
}
B[ 0] += x00;
B[ 1] += x01;
B[ 2] += x02;
B[ 3] += x03;
B[ 4] += x04;
B[ 5] += x05;
B[ 6] += x06;
B[ 7] += x07;
B[ 8] += x08;
B[ 9] += x09;
B[10] += x10;
B[11] += x11;
B[12] += x12;
B[13] += x13;
B[14] += x14;
B[15] += x15;
}
static inline void scrypt_core(uint32_t *X, uint32_t *V)
{
uint32_t i, j, k;
int n=1024;
for (i = 0; i < n; i++) {
memcpy(&V[i * 32], X, 128);
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
for (i = 0; i < n; i++) {
j = 32 * (X[16] & (n - 1));
for (k = 0; k < 32; k++)
X[k] ^= V[j + k];
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
}
#endif
static inline void xor_salsa8(uint32_t B[16], const uint32_t Bx[16])
{
uint32_t x00,x01,x02,x03,x04,x05,x06,x07,x08,x09,x10,x11,x12,x13,x14,x15;
int i;
x00 = (B[ 0] ^= Bx[ 0]);
x01 = (B[ 1] ^= Bx[ 1]);
x02 = (B[ 2] ^= Bx[ 2]);
x03 = (B[ 3] ^= Bx[ 3]);
x04 = (B[ 4] ^= Bx[ 4]);
x05 = (B[ 5] ^= Bx[ 5]);
x06 = (B[ 6] ^= Bx[ 6]);
x07 = (B[ 7] ^= Bx[ 7]);
x08 = (B[ 8] ^= Bx[ 8]);
x09 = (B[ 9] ^= Bx[ 9]);
x10 = (B[10] ^= Bx[10]);
x11 = (B[11] ^= Bx[11]);
x12 = (B[12] ^= Bx[12]);
x13 = (B[13] ^= Bx[13]);
x14 = (B[14] ^= Bx[14]);
x15 = (B[15] ^= Bx[15]);
for (i = 0; i < 8; i += 2) {
#define R(a, b) (((a) << (b)) | ((a) >> (32 - (b))))
/* Operate on columns. */
x04 ^= R(x00+x12, 7); x09 ^= R(x05+x01, 7);
x14 ^= R(x10+x06, 7); x03 ^= R(x15+x11, 7);
x08 ^= R(x04+x00, 9); x13 ^= R(x09+x05, 9);
x02 ^= R(x14+x10, 9); x07 ^= R(x03+x15, 9);
x12 ^= R(x08+x04,13); x01 ^= R(x13+x09,13);
x06 ^= R(x02+x14,13); x11 ^= R(x07+x03,13);
x00 ^= R(x12+x08,18); x05 ^= R(x01+x13,18);
x10 ^= R(x06+x02,18); x15 ^= R(x11+x07,18);
/* Operate on rows. */
x01 ^= R(x00+x03, 7); x06 ^= R(x05+x04, 7);
x11 ^= R(x10+x09, 7); x12 ^= R(x15+x14, 7);
x02 ^= R(x01+x00, 9); x07 ^= R(x06+x05, 9);
x08 ^= R(x11+x10, 9); x13 ^= R(x12+x15, 9);
x03 ^= R(x02+x01,13); x04 ^= R(x07+x06,13);
x09 ^= R(x08+x11,13); x14 ^= R(x13+x12,13);
x00 ^= R(x03+x02,18); x05 ^= R(x04+x07,18);
x10 ^= R(x09+x08,18); x15 ^= R(x14+x13,18);
#undef R
}
B[ 0] += x00;
B[ 1] += x01;
B[ 2] += x02;
B[ 3] += x03;
B[ 4] += x04;
B[ 5] += x05;
B[ 6] += x06;
B[ 7] += x07;
B[ 8] += x08;
B[ 9] += x09;
B[10] += x10;
B[11] += x11;
B[12] += x12;
B[13] += x13;
B[14] += x14;
B[15] += x15;
}
static inline void scrypt_core(uint32_t *X, uint32_t *V)
{
uint32_t i, j, k;
int n=1024;
for (i = 0; i < n; i++) {
memcpy(&V[i * 32], X, 128);
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
for (i = 0; i < n; i++) {
j = 32 * (X[16] & (n - 1));
for (k = 0; k < 32; k++)
X[k] ^= V[j + k];
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
}
#endif
March 29, 2016, 07:08:49 PM
i just want to inform u that groestlcoin DMD Diamond merged mining is removed from DMD 2.1 wallet content
this happens because the roadmap to DMD 3.0 move in a direction that make this obsolete
this happens because the roadmap to DMD 3.0 move in a direction that make this obsolete
March 29, 2016, 05:30:15 PM
great stuff is happening in background
while we still working to get wallet 2.1 released
we already have setup a plan for DMD 3.0 wallet and it will be mind-blowing trust me
that will be the moment everyone know again why we carry "evolution" in our thread title!
while we still working to get wallet 2.1 released
we already have setup a plan for DMD 3.0 wallet and it will be mind-blowing trust me
that will be the moment everyone know again why we carry "evolution" in our thread title!
March 29, 2016, 09:40:31 AM
nicehash did merge together mining stats from nicehash and westhash so now https://multipool.bit.diamonds/ show merged stats now too
still missing is that we add visible stats for other algos on our website we will do that in one of next updates
for the DMD payout that doesnt matter because the DMD u recieve just deepend on the arriving BTC so if we track stats or not doesnt matter
its more a cosmetically issue to have stats visible that represent the true miningpower of our userbase
still missing is that we add visible stats for other algos on our website we will do that in one of next updates
for the DMD payout that doesnt matter because the DMD u recieve just deepend on the arriving BTC so if we track stats or not doesnt matter
its more a cosmetically issue to have stats visible that represent the true miningpower of our userbase
March 29, 2016, 04:01:03 AM
can i ask how much a 970 can do with this algo? is it profitable?
You want to mine -groestl algo with a Geforce 970? It's not profitable...
But you can use the miner from nicehash, mine a more profitable algo suited for your card and get payouts in DMD thru multipool...
i've tried and it's actually profitable, not on par with etheruem, but there is profit, you can earn at present, 0.005 with a single 970, each day
March 29, 2016, 03:45:09 AM
March 29, 2016, 03:40:14 AM
can i ask how much a 970 can do with this algo? is it profitable?
You want to mine -groestl algo with a Geforce 970? It's not profitable...
But you can use the miner from nicehash, mine a more profitable algo suited for your card and get payouts in DMD thru multipool...
March 29, 2016, 02:41:31 AM
can i ask how much a 970 can do with this algo? is it profitable?
March 29, 2016, 02:31:35 AM
@devs
I found a cpp source for scrypt_core()
I put it in scrypt_mine.cpp
using ~ 190% cpu on a quad core 64 bit.
Synced up cpu use dropped to about 30% is that about normal on a linux build?
compiling with -O3 and see if that makes a difference ...
Disk usage
I found a cpp source for scrypt_core()
I put it in scrypt_mine.cpp
Code:
#if defined(__aarch64__)
static inline void xor_salsa8(uint32_t B[16], const uint32_t Bx[16])
{
uint32_t x00,x01,x02,x03,x04,x05,x06,x07,x08,x09,x10,x11,x12,x13,x14,x15;
int i;
x00 = (B[ 0] ^= Bx[ 0]);
x01 = (B[ 1] ^= Bx[ 1]);
x02 = (B[ 2] ^= Bx[ 2]);
x03 = (B[ 3] ^= Bx[ 3]);
x04 = (B[ 4] ^= Bx[ 4]);
x05 = (B[ 5] ^= Bx[ 5]);
x06 = (B[ 6] ^= Bx[ 6]);
x07 = (B[ 7] ^= Bx[ 7]);
x08 = (B[ 8] ^= Bx[ 8]);
x09 = (B[ 9] ^= Bx[ 9]);
x10 = (B[10] ^= Bx[10]);
x11 = (B[11] ^= Bx[11]);
x12 = (B[12] ^= Bx[12]);
x13 = (B[13] ^= Bx[13]);
x14 = (B[14] ^= Bx[14]);
x15 = (B[15] ^= Bx[15]);
for (i = 0; i < 8; i += 2) {
#define R(a, b) (((a) << (b)) | ((a) >> (32 - (b))))
/* Operate on columns. */
x04 ^= R(x00+x12, 7); x09 ^= R(x05+x01, 7);
x14 ^= R(x10+x06, 7); x03 ^= R(x15+x11, 7);
x08 ^= R(x04+x00, 9); x13 ^= R(x09+x05, 9);
x02 ^= R(x14+x10, 9); x07 ^= R(x03+x15, 9);
x12 ^= R(x08+x04,13); x01 ^= R(x13+x09,13);
x06 ^= R(x02+x14,13); x11 ^= R(x07+x03,13);
x00 ^= R(x12+x08,18); x05 ^= R(x01+x13,18);
x10 ^= R(x06+x02,18); x15 ^= R(x11+x07,18);
/* Operate on rows. */
x01 ^= R(x00+x03, 7); x06 ^= R(x05+x04, 7);
x11 ^= R(x10+x09, 7); x12 ^= R(x15+x14, 7);
x02 ^= R(x01+x00, 9); x07 ^= R(x06+x05, 9);
x08 ^= R(x11+x10, 9); x13 ^= R(x12+x15, 9);
x03 ^= R(x02+x01,13); x04 ^= R(x07+x06,13);
x09 ^= R(x08+x11,13); x14 ^= R(x13+x12,13);
x00 ^= R(x03+x02,18); x05 ^= R(x04+x07,18);
x10 ^= R(x09+x08,18); x15 ^= R(x14+x13,18);
#undef R
}
B[ 0] += x00;
B[ 1] += x01;
B[ 2] += x02;
B[ 3] += x03;
B[ 4] += x04;
B[ 5] += x05;
B[ 6] += x06;
B[ 7] += x07;
B[ 8] += x08;
B[ 9] += x09;
B[10] += x10;
B[11] += x11;
B[12] += x12;
B[13] += x13;
B[14] += x14;
B[15] += x15;
}
static inline void scrypt_core(uint32_t *X, uint32_t *V)
{
uint32_t i, j, k;
int n=1024;
for (i = 0; i < n; i++) {
memcpy(&V[i * 32], X, 128);
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
for (i = 0; i < n; i++) {
j = 32 * (X[16] & (n - 1));
for (k = 0; k < 32; k++)
X[k] ^= V[j + k];
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
}
#endif
Code compiles ... and syncing static inline void xor_salsa8(uint32_t B[16], const uint32_t Bx[16])
{
uint32_t x00,x01,x02,x03,x04,x05,x06,x07,x08,x09,x10,x11,x12,x13,x14,x15;
int i;
x00 = (B[ 0] ^= Bx[ 0]);
x01 = (B[ 1] ^= Bx[ 1]);
x02 = (B[ 2] ^= Bx[ 2]);
x03 = (B[ 3] ^= Bx[ 3]);
x04 = (B[ 4] ^= Bx[ 4]);
x05 = (B[ 5] ^= Bx[ 5]);
x06 = (B[ 6] ^= Bx[ 6]);
x07 = (B[ 7] ^= Bx[ 7]);
x08 = (B[ 8] ^= Bx[ 8]);
x09 = (B[ 9] ^= Bx[ 9]);
x10 = (B[10] ^= Bx[10]);
x11 = (B[11] ^= Bx[11]);
x12 = (B[12] ^= Bx[12]);
x13 = (B[13] ^= Bx[13]);
x14 = (B[14] ^= Bx[14]);
x15 = (B[15] ^= Bx[15]);
for (i = 0; i < 8; i += 2) {
#define R(a, b) (((a) << (b)) | ((a) >> (32 - (b))))
/* Operate on columns. */
x04 ^= R(x00+x12, 7); x09 ^= R(x05+x01, 7);
x14 ^= R(x10+x06, 7); x03 ^= R(x15+x11, 7);
x08 ^= R(x04+x00, 9); x13 ^= R(x09+x05, 9);
x02 ^= R(x14+x10, 9); x07 ^= R(x03+x15, 9);
x12 ^= R(x08+x04,13); x01 ^= R(x13+x09,13);
x06 ^= R(x02+x14,13); x11 ^= R(x07+x03,13);
x00 ^= R(x12+x08,18); x05 ^= R(x01+x13,18);
x10 ^= R(x06+x02,18); x15 ^= R(x11+x07,18);
/* Operate on rows. */
x01 ^= R(x00+x03, 7); x06 ^= R(x05+x04, 7);
x11 ^= R(x10+x09, 7); x12 ^= R(x15+x14, 7);
x02 ^= R(x01+x00, 9); x07 ^= R(x06+x05, 9);
x08 ^= R(x11+x10, 9); x13 ^= R(x12+x15, 9);
x03 ^= R(x02+x01,13); x04 ^= R(x07+x06,13);
x09 ^= R(x08+x11,13); x14 ^= R(x13+x12,13);
x00 ^= R(x03+x02,18); x05 ^= R(x04+x07,18);
x10 ^= R(x09+x08,18); x15 ^= R(x14+x13,18);
#undef R
}
B[ 0] += x00;
B[ 1] += x01;
B[ 2] += x02;
B[ 3] += x03;
B[ 4] += x04;
B[ 5] += x05;
B[ 6] += x06;
B[ 7] += x07;
B[ 8] += x08;
B[ 9] += x09;
B[10] += x10;
B[11] += x11;
B[12] += x12;
B[13] += x13;
B[14] += x14;
B[15] += x15;
}
static inline void scrypt_core(uint32_t *X, uint32_t *V)
{
uint32_t i, j, k;
int n=1024;
for (i = 0; i < n; i++) {
memcpy(&V[i * 32], X, 128);
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
for (i = 0; i < n; i++) {
j = 32 * (X[16] & (n - 1));
for (k = 0; k < 32; k++)
X[k] ^= V[j + k];
xor_salsa8(&X[0], &X[16]);
xor_salsa8(&X[16], &X[0]);
}
}
#endif
using ~ 190% cpu on a quad core 64 bit.Synced up
cpu use dropped to about 30% is that about normal on a linux build?compiling with -O3 and see if that makes a difference ...
Quote
top - 05:46:50 up 4:30, 3 users, load average: 0.27, 0.36, 0.65
Tasks: 157 total, 2 running, 155 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.2 us, 0.6 sy, 7.0 ni, 92.2 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 1760360 total, 932260 used, 828100 free, 4112 buffers
KiB Swap: 2047996 total, 128036 used, 1919960 free. 112292 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2362 odroid 20 0 1443020 627508 9444 S 29.9 35.6 56:20.24 diamond-qt-O3
Swap barely got touched with all the compiling I've been doing ... probably never touch it after a reboot.Tasks: 157 total, 2 running, 155 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.2 us, 0.6 sy, 7.0 ni, 92.2 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 1760360 total, 932260 used, 828100 free, 4112 buffers
KiB Swap: 2047996 total, 128036 used, 1919960 free. 112292 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2362 odroid 20 0 1443020 627508 9444 S 29.9 35.6 56:20.24 diamond-qt-O3
Disk usage
Quote
odroid@odroid64:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 29940700 3873036 26049272 13% /
udev 10240 0 10240 0% /dev
tmpfs 352072 11624 340448 4% /run
tmpfs 880180 80 880100 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 880180 0 880180 0% /sys/fs/cgroup
/dev/mmcblk0p1 130796 16394 114402 13% /media/boot
/dev/mmcblk1p2 28528640 2856728 24199656 11% /home
tmpfs 176036 4 176032 1% /run/user/115
tmpfs 176036 16 176020 1% /run/user/1000
tmpfs 176036 0 176036 0% /run/user/0
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 29940700 3873036 26049272 13% /
udev 10240 0 10240 0% /dev
tmpfs 352072 11624 340448 4% /run
tmpfs 880180 80 880100 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 880180 0 880180 0% /sys/fs/cgroup
/dev/mmcblk0p1 130796 16394 114402 13% /media/boot
/dev/mmcblk1p2 28528640 2856728 24199656 11% /home
tmpfs 176036 4 176032 1% /run/user/115
tmpfs 176036 16 176020 1% /run/user/1000
tmpfs 176036 0 176036 0% /run/user/0
March 28, 2016, 08:23:23 PM
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
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
Great, that looks perfect! I just ordered one.
Thanks man!
mephoria
Actually, I just ordered another for a friend. Dual boot looks fun!
another one that could be interesting to test
http://www.tinydeal.com/en/ONDA-V891-8-9-IPS-Screen-Win10-Android-4-4-Dual-OS-Intel-Z3735F-2GB-32GB-Tablet-PC-w-Bluetooth-4-0-OTG-HDMI-p-155608.html
i think the interesting part for use such low cost stuff as staking device is
u dont care if its plastic and maybe not robust if carry around
u dont care if battery is weak
u dont care is display is bad
all u need is it to be 24/7 connected on power cable running ur staking wallet at low power useage
i will run mine on some place not even visible to people just talking with router via wlan
this way physical access to the device is hard for a intruder too
Yeah, I'm excited about these little guys!!
March 28, 2016, 05:13:24 PM
Anyone got an armv7 (Pi2) that can compile the wallet and send me a copy of scrypt-arm.o 
I want to try putting the .o from a 32 bit machine in with the 64 bit .o files and try to get it to link.
My email is on left pane. All I need is one file and it should surely fit as attachment to email.
Or send me a complete compiled arm7 32 bit source tree and I can work with that
Theoretically 32 bit can run on 64 bit machine ...
I want to try putting the .o from a 32 bit machine in with the 64 bit .o files and try to get it to link.
My email is on left pane. All I need is one file and it should surely fit as attachment to email.
Or send me a complete compiled arm7 32 bit source tree and I can work with that
Theoretically 32 bit can run on 64 bit machine ...
the rokos guys will go for PI3 pine64 and odroid2 soon too i would wait for their solutions and reuse them
I don't want to wait LOL, If this works, at least I can have my staking system running:) This code is only used during sync right? I don't mind if syncing is slightly slower than if it was pure 64 bit. A hybrid wallet will satisfy me for now
The wallet compiles 64 bit now except for 1 file ...
If this works I can provide a Diamond-qt binary (or source modified to compile along with the critical .o file) for other aarch64 users
ROKOS will probably be months away for 64 bit ... He's going to be starting with a clean Odrobian 64 bit system (Debian for Odroid C2).
AWESOME OKtoshi just sent me scrypt.o file
Trying it now ...
bummer did not work
build/scrypt-arm.o: error adding symbols: File in wrong format
collect2: error: ld returned 1 exit status
Makefile:305: recipe for target 'diamond-qt' failed
Looks like I'll just have to wait for scrypt-aarch64.S to be written or the need for it eliminated in the new wallet if the diamond devs go ahead with plan to remove scrypt algo completely from the blockchain.
March 28, 2016, 04:50:48 PM
Anyone got an armv7 (Pi2) that can compile the wallet and send me a copy of scrypt-arm.o
I want to try putting the .o from a 32 bit machine in with the 64 bit .o files and try to get it to link.
Theoretically 32 bit can run on 64 bit machine ...
I want to try putting the .o from a 32 bit machine in with the 64 bit .o files and try to get it to link.
Theoretically 32 bit can run on 64 bit machine ...
the rokos guys will go for PI3 pine64 and odroid2 soon too i would wait for their solutions and reuse them
March 28, 2016, 07:22:27 AM
crashoveride from the odroid forum wrote:
I already knew about makefile.unix and have some fixes in my source tree and some lines added in diamond.pro
will look at makefile.unix again, can probably leave obj/scrypt-arm.o and just add one line obj/scrypt.o
Damn its already there at line 138
.
scrypt.cpp does NOT provide scrypt-core() which is my whole problem, scrypt_core() not getting built because scrypt-aarch64.S does not exist. So no solution yet.
I'd settle for scrypt-aarch64.cpp for now just to get wallet running
http://forum.odroid.com/viewtopic.php?f=138&t=20203Quote
Actually, its not my Odrobian. Its @XeoSal's. He is the one putting all the hard work into it. 
Who ever maintains the code should be able to get you a work around. After looking at the code, the Makefile keys on "__arm__" so it will always use the 32bit code no matter what. A 64bit kernel on a 32bit OS should make no difference because its asking the compiler, not the OS.
https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S#L10
There appears to be a generic version of the code written in C++.
https://github.com/DMDcoin/Diamond/blob/master/src/scrypt.cpp
By omitting the arm version and using the generic version, you may have better luck getting it to work in a 64bit armv8 environment:
https://github.com/DMDcoin/Diamond/blob/master/src/makefile.unix#L149
(change "obj/scrypt-arm.o" to "obj/scrypt.o")
All of the following should be replaced with the single line "xCXXFLAGS+= -DNOSSE" to disable Intel x86 code paths.
https://github.com/DMDcoin/Diamond/blob/master/src/makefile.unix#L100-L108
This is just a suggestion. You will need to contact the maintainer or post to their forums if you encounter issues.
Excellent analysis by crashoveride Who ever maintains the code should be able to get you a work around. After looking at the code, the Makefile keys on "__arm__" so it will always use the 32bit code no matter what. A 64bit kernel on a 32bit OS should make no difference because its asking the compiler, not the OS.
https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S#L10
There appears to be a generic version of the code written in C++.
https://github.com/DMDcoin/Diamond/blob/master/src/scrypt.cpp
By omitting the arm version and using the generic version, you may have better luck getting it to work in a 64bit armv8 environment:
https://github.com/DMDcoin/Diamond/blob/master/src/makefile.unix#L149
(change "obj/scrypt-arm.o" to "obj/scrypt.o")
All of the following should be replaced with the single line "xCXXFLAGS+= -DNOSSE" to disable Intel x86 code paths.
https://github.com/DMDcoin/Diamond/blob/master/src/makefile.unix#L100-L108
This is just a suggestion. You will need to contact the maintainer or post to their forums if you encounter issues.
I already knew about makefile.unix and have some fixes in my source tree
and some lines added in diamond.pro will look at makefile.unix again, can probably leave obj/scrypt-arm.o and just add one line obj/scrypt.o
Damn its already there at line 138
.scrypt.cpp does NOT provide scrypt-core() which is my whole problem, scrypt_core() not getting built because scrypt-aarch64.S does not exist. So no solution yet.
I'd settle for scrypt-aarch64.cpp for now just to get wallet running
Anyone got an armv7 (Pi2) that can compile the wallet and send me a copy of scrypt-arm.o
I want to try putting the .o from a 32 bit machine in with the 64 bit .o files and try to get it to link.
My email is on left pane. All I need is one file and it should surely fit as attachment to email.
Or send me a complete compiled arm7 32 bit source tree and I can work with that
Theoretically 32 bit can run on 64 bit machine ...
March 28, 2016, 02:36:03 AM
Just installed kodi 16.2 RC2 on the Odroid C2, now my staking box is also my home entertainment system
Plays movies perfectly over network from my archives on windows box ...
This is a truly feature packed home entertainment system.
Good bye windows media player classic
Going to order the odroid infrared remote next ordered 4.95+shipping
(Receiver built into the Odroid C2)
Plays movies perfectly over network from my archives on windows box ...
This is a truly feature packed home entertainment system.
Good bye windows media player classic
Going to order the odroid infrared remote next
ordered 4.95+shipping(Receiver built into the Odroid C2)
March 27, 2016, 09:07:12 PM
all are welcome to have a look at my DMD cloud mining stats copy and past the DMD address in my signature and enjoy the show:)... i have
March 27, 2016, 08:19:41 PM
I have officially reached ROI with my DMD cloudmining and now I am in a nice earning mode. Willing to share my info with anyone interested. I ve been reading a lot of threads about how it is not possible to reach ROI and make profits with cloud mining. Well, when it comes to DMD Diamond, IMPOSSIBLE IS NOTHING.
Congratulations! Welcome aboard the ROI train! :-)
March 27, 2016, 07:27:26 PM
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
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
Great, that looks perfect! I just ordered one.
Thanks man!
mephoria
Actually, I just ordered another for a friend. Dual boot looks fun!
another one that could be interesting to test
http://www.tinydeal.com/en/ONDA-V891-8-9-IPS-Screen-Win10-Android-4-4-Dual-OS-Intel-Z3735F-2GB-32GB-Tablet-PC-w-Bluetooth-4-0-OTG-HDMI-p-155608.html
i think the interesting part for use such low cost stuff as staking device is
u dont care if its plastic and maybe not robust if carry around
u dont care if battery is weak
u dont care is display is bad
all u need is it to be 24/7 connected on power cable running ur staking wallet at low power useage
i will run mine on some place not even visible to people just talking with router via wlan
this way physical access to the device is hard for a intruder too
Jump to: