Bitcoin Forum
August 18, 2018, 08:45:02 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 [776] 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 »
  Print  
Author Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%  (Read 1184297 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
daschmidty
Newbie
*
Offline Offline

Activity: 7
Merit: 1


View Profile
December 03, 2017, 04:08:59 PM
 #15501

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

WIN: WPgudqUGy2P5RbQLSpnu76xTQ7VmuNsV7j
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
1534625102
Hero Member
*
Offline Offline

Posts: 1534625102

View Profile Personal Message (Offline)

Ignore
1534625102
Reply with quote  #2

1534625102
Report to moderator
NoxX
Sr. Member
****
Offline Offline

Activity: 462
Merit: 252



View Profile
December 03, 2017, 04:50:53 PM
 #15502

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

If you don't have LibreSSL installed, have you tried compiling --with-libressl? That should get it to use the openSSL that was incorrectly identified as libreSSL. At least that is what worked for me on a RasPi...

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
███
███
███
███
███
███
███
███
███
███
   Anonymity Guaranteed
   Anonymous and Untraceable
   Guard Your Privacy
      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
daschmidty
Newbie
*
Offline Offline

Activity: 7
Merit: 1


View Profile
December 03, 2017, 05:14:56 PM
 #15503

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

If you don't have LibreSSL installed, have you tried compiling --with-libressl? That should get it to use the openSSL that was incorrectly identified as libreSSL. At least that is what worked for me on a RasPi...

Adding the --with-libressl switch allows the configure script to complete but the build bombs out with a bunch of ssl related errors:

Code:
CXX      libbitcoinconsensus_la-ecwrapper.lo
ecwrapper.cpp: In function ‘int {anonymous}::ECDSA_SIG_recover_key_GFp(EC_KEY*, ECDSA_SIG*, const unsigned char*, int, int, int)’:
ecwrapper.cpp:62:28: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_add(x, x, ecsig->r)) {
                            ^~
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:62:30: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_add(x, x, ecsig->r)) {
                              ^
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:118:34: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_mod_inverse(rr, ecsig->r, order, ctx)) {
                                  ^~
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:118:36: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_mod_inverse(rr, ecsig->r, order, ctx)) {
                                    ^
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:123:31: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_mod_mul(sor, ecsig->s, rr, order, ctx)) {
                               ^~
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:123:33: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     if (!BN_mod_mul(sor, ecsig->s, rr, order, ctx)) {
                                 ^
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp: In member function ‘bool CECKey::Recover(const uint256&, const unsigned char*, int)’:
ecwrapper.cpp:221:31: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     BN_bin2bn(&p64[0], 32, sig->r);
                               ^~
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:221:33: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     BN_bin2bn(&p64[0], 32, sig->r);
                                 ^
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:222:32: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     BN_bin2bn(&p64[32], 32, sig->s);
                                ^~
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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;
                ^~~~~~~~~~~~
ecwrapper.cpp:222:34: error: invalid use of incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
     BN_bin2bn(&p64[32], 32, sig->s);
                                  ^
In file included from ecwrapper.h:11:0,
                 from ecwrapper.cpp:5:
/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[2]: *** [Makefile:6295: libbitcoinconsensus_la-ecwrapper.lo] Error 1
make[2]: Leaving directory '/home/david/Wallets/Diamond/src'
make[1]: *** [Makefile:7117: all-recursive] Error 1
make[1]: Leaving directory '/home/david/Wallets/Diamond/src'
make: *** [Makefile:594: all-recursive] Error 1



I'm pretty stumped on this one. I tried building an older version of openssl from source, but that has been a mess.

WIN: WPgudqUGy2P5RbQLSpnu76xTQ7VmuNsV7j
NoxX
Sr. Member
****
Offline Offline

Activity: 462
Merit: 252



View Profile
December 03, 2017, 06:22:27 PM
 #15504

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

If you don't have LibreSSL installed, have you tried compiling --with-libressl? That should get it to use the openSSL that was incorrectly identified as libreSSL. At least that is what worked for me on a RasPi...

Adding the --with-libressl switch allows the configure script to complete but the build bombs out with a bunch of ssl related errors:

I'm pretty stumped on this one. I tried building an older version of openssl from source, but that has been a mess.

Hmm, as per here (https://github.com/PIVX-Project/PIVX/issues/149) you could try installing an older version of openSSL alongside the latest one with

apt-get install libssl1.0-dev

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
███
███
███
███
███
███
███
███
███
███
   Anonymity Guaranteed
   Anonymous and Untraceable
   Guard Your Privacy
      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
daschmidty
Newbie
*
Offline Offline

Activity: 7
Merit: 1


View Profile
December 03, 2017, 08:41:06 PM
 #15505

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

If you don't have LibreSSL installed, have you tried compiling --with-libressl? That should get it to use the openSSL that was incorrectly identified as libreSSL. At least that is what worked for me on a RasPi...

Adding the --with-libressl switch allows the configure script to complete but the build bombs out with a bunch of ssl related errors:

I'm pretty stumped on this one. I tried building an older version of openssl from source, but that has been a mess.

Hmm, as per here (https://github.com/PIVX-Project/PIVX/issues/149) you could try installing an older version of openSSL alongside the latest one with

apt-get install libssl1.0-dev


Unfortunately I am not running debian/Ubuntu. Trying to install the openssl1.0-devel package on SUSE conflicts with 1.1 It keeps proposing to uninstall openssl1.1 along with a ton of other stuff. They just moved to 1.1 a few weeks ago and I have never had issues building the wallet until now.

WIN: WPgudqUGy2P5RbQLSpnu76xTQ7VmuNsV7j
NoxX
Sr. Member
****
Offline Offline

Activity: 462
Merit: 252



View Profile
December 03, 2017, 09:13:56 PM
 #15506

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

If you don't have LibreSSL installed, have you tried compiling --with-libressl? That should get it to use the openSSL that was incorrectly identified as libreSSL. At least that is what worked for me on a RasPi...

Adding the --with-libressl switch allows the configure script to complete but the build bombs out with a bunch of ssl related errors:

I'm pretty stumped on this one. I tried building an older version of openssl from source, but that has been a mess.

Hmm, as per here (https://github.com/PIVX-Project/PIVX/issues/149) you could try installing an older version of openSSL alongside the latest one with

apt-get install libssl1.0-dev


Unfortunately I am not running debian/Ubuntu. Trying to install the openssl1.0-devel package on SUSE conflicts with 1.1 It keeps proposing to uninstall openssl1.1 along with a ton of other stuff. They just moved to 1.1 a few weeks ago and I have never had issues building the wallet until now.

Then I'm out of ideas, sorry. I run all my wallets on RasPis...

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
███
███
███
███
███
███
███
███
███
███
   Anonymity Guaranteed
   Anonymous and Untraceable
   Guard Your Privacy
      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
davembg
Sr. Member
****
Offline Offline

Activity: 340
Merit: 251


Smell the glove.


View Profile
December 03, 2017, 09:55:13 PM
 #15507

I am trying to compile the wallet on a fresh linux install (openSUSE tumbleweed) and I am getting a configure error regarding SSL:
"configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!"
I don't actually have LibreSSL installed, but rather openSSL 1.1.0-g. I have read there was a bug in bitcoin wallet that caused it to not build against openssl >1.0, but it appears that has been fixed elsewhere. Any ideas how to best work around this issue? Downgrading openssl on my system will cause a number of dependency issues.

I posted in the slack channel as well, but so far no luck.

Try the depends toolkit included in the github code.
Make sure you have the dependencies installed.
sudo apt install build-essential libtool autotools-dev autoconf pkg-config curl
You will likely have to make changes to the package names for Suse - I don't use Suse, so.....

To build the wallet -

Code:
sh autogen.sh

cd depends

#without gui
make NO_QT=1
#with gui
make

This will take awhile as the dependencies are downloaded and built, you will need a gig or 2 of disk space.

then:
Code:
cd ..
./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu
# the directory "x86_64-pc-linux-gnu" may be named differently on Suse - verify the name in the depends directory.
Code:
make
strip src/qt/diamond-qt
# also verify the  src/qt/diamond-qt binary name

Good luck!

cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 03, 2017, 10:38:54 PM
 #15508

i only use ubuntu sorry
once u have a guide for suse u welcome to write a howto here

https://github.com/DMDcoin/Diamond/tree/master/doc

 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
Lionel
Sr. Member
****
Offline Offline

Activity: 503
Merit: 264


View Profile
December 04, 2017, 09:38:32 AM
 #15509

Hello,
staking is not active since yesterday. What can i do ?

https://bitcointalk.org/index.php?topic=255806.msg25712214#msg25712214
Quote
Hello,
my wallet 3.0.0.13b is running since yesterday and staking is still not active.

I have unlocked my wallet since yesterday as well.

Why ?

EDIT: i have to say that my connection is having issues lately, it's extremely slow. Could it be that ?
cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 04, 2017, 11:05:19 AM
 #15510

Hello,
staking is not active since yesterday. What can i do ?

https://bitcointalk.org/index.php?topic=255806.msg25712214#msg25712214
Quote
Hello,
my wallet 3.0.0.13b is running since yesterday and staking is still not active.

I have unlocked my wallet since yesterday as well.

Why ?

EDIT: i have to say that my connection is having issues lately, it's extremely slow. Could it be that ?

restart wallet
wait until all sync bars disappear
wait 1 min longer
then unlock wallet in "only for..." mode
then after like 1-2 minutes ur diamond icon bottom right should get blue
if u have mature available coins older than 1 hour in wallet
if all coins minted already and none are mature again its normal the diamond get grey until u have again mature coins

most of the POS stay inactive issues are by unlock wallet to early when the MNsync is not finished
keep in mind a POS/Masternode coins need to sync not only the blockchain but also sync with the masternode network
and only if all sync are finished u should start POS (by unlock ur wallet)

 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
Gecko8
Full Member
***
Offline Offline

Activity: 322
Merit: 101


"Bitcore (BTX) - The Future is Now"


View Profile
December 04, 2017, 12:41:14 PM
 #15511

Hello,
staking is not active since yesterday. What can i do ?

https://bitcointalk.org/index.php?topic=255806.msg25712214#msg25712214
Quote
Hello,
my wallet 3.0.0.13b is running since yesterday and staking is still not active.

I have unlocked my wallet since yesterday as well.

Why ?

EDIT: i have to say that my connection is having issues lately, it's extremely slow. Could it be that ?

restart wallet
wait until all sync bars disappear
wait 1 min longer
then unlock wallet in "only for..." mode
then after like 1-2 minutes ur diamond icon bottom right should get blue
if u have mature available coins older than 1 hour in wallet
if all coins minted already and none are mature again its normal the diamond get grey until u have again mature coins

most of the POS stay inactive issues are by unlock wallet to early when the MNsync is not finished
keep in mind a POS/Masternode coins need to sync not only the blockchain but also sync with the masternode network
and only if all sync are finished u should start POS (by unlock ur wallet)

I have same issue with staking. I followed your instructions above. coins are now in the wallet for 1 hour and 40 min. so should be now mature. Also waited before I unlocked the wallet. Any ideas? EDIt: It now works, just were double checking. So obviously it took more time getting the coins mature. What does actually mean Multisend: not active? Do I need this oneß

cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 04, 2017, 12:51:49 PM
 #15512

What does actually mean Multisend: not active? Do I need this oneß

u dont need multisend
its only a special usecase when u want POS/Masternode income be forwarded to another address
this is called multisend

its not required to be configured
and not many usecases with it make sense

 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 05, 2017, 01:07:14 AM
 #15513

DMD Diamond reach new $ per coin and $ total marketcap all time high!

a great year ends with another sprint back up to where we belong into the top 50 blockchains
where we where for a long time already in the early days of crypto

still way to go and early anough to join us on this voyage!


 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 05, 2017, 01:28:56 AM
 #15514

if u remove below 100 BTC marketcap coins
we are one of the 20 best performing coins last 12 months with over 4000% $ value gain
if u add on top the ~25% more coins u generated that year too we are close to top 10 coin
so we perform excelent
and are still way undervalued
we have lot more room to grow

the future is bright!

source: http://alt19.com/




 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
hallared
Full Member
***
Offline Offline

Activity: 150
Merit: 101


The hen or the egg


View Profile
December 05, 2017, 08:35:49 PM
 #15515

Is the DMD Piggy Bank on the move? Smiley Wink




   


blacksidi
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
December 05, 2017, 08:39:31 PM
 #15516

...and just another 15 shares left for the shared masternode.......a good chance to boost your passive income  Smiley
https://dmdmn.miningfield.com/bshare.php
kevindj
Jr. Member
*
Offline Offline

Activity: 44
Merit: 0


View Profile WWW
December 05, 2017, 10:03:43 PM
 #15517

was there any update on the silver coins? obviously quite a few people kicked in 200 DMD and the price has risen a fair bit since they were given, are those coins being staked, and are the remaining slots being sold?

UK-USA IPTV Server For Mag Box PM Me for Trial..
Woody20285
Legendary
*
Offline Offline

Activity: 1176
Merit: 1002


Supporting XDE2, LasVegasCoin, DMD, ERC & PIO


View Profile
December 05, 2017, 10:39:02 PM
 #15518

was there any update on the silver coins? obviously quite a few people kicked in 200 DMD and the price has risen a fair bit since they were given, are those coins being staked, and are the remaining slots being sold?
No one expected BTC to rise so much so quickly.
I am sure the DMD team will take care of their loyal
followers.

shveicar
Legendary
*
Offline Offline

Activity: 1306
Merit: 1012


DMD info: https://diamond-info.github.io/


View Profile
December 05, 2017, 11:37:53 PM
 #15519

was there any update on the silver coins? obviously quite a few people kicked in 200 DMD and the price has risen a fair bit since they were given, are those coins being staked, and are the remaining slots being sold?

All information is available here
There is still availability for registration.

Diamond The best investment in your future! ✧ it's 35% POS and 65% Msternode ✧
cryptonit
Legendary
*
Offline Offline

Activity: 1708
Merit: 1033


bit.diamonds | artis.eco


View Profile WWW
December 05, 2017, 11:59:26 PM
 #15520

was there any update on the silver coins? obviously quite a few people kicked in 200 DMD and the price has risen a fair bit since they were given, are those coins being staked, and are the remaining slots being sold?

All information is available here
There is still availability for registration.


dont register i will prepare with goal up to end of february the offer for the 5th anniversary coin
all who did send 200 DMD will be able to have that convertedtowards the new coin then

the new anniversary coin will be much greater package

not just a limited coin
not just a branded noble woodbox
not just a limited by author handsigned book about DMD
not just a cool DMD branded led light
and and and



we switched the producer of silvercoins
to reach the desired quality
once we have proper prototypes to show
we will start sell unclaimed coins again
once a proper ammount is sold
we start to produce the silvercoins and do the lottery for the 10000 DMD

im sorry for the delay but at the moment my whole energy is focused on DMDv3 release
im sure we can manage finalize the DMD Diamond 4th anniversary silvercoin project pre xmas

i just wonder what increadible value the lottery price of 10000 DMD will then represent!

Any news on the silvercoins? Or are plans shifted toward more expensive matters Wink


it will become a 5th anniversary coin
i did absolute underestimate the time all this things need
good part we will add a lot of goodies like a DMD book and some more DMD promo gimmicks
in the end it will be a limited edition wonder box with many nice things

new release goal is pre june 2018
we might replace the masternode lottery with a much more luxury material selection for the coin
this way everyone is a winner



 
  Diamond [DMD]     ARTIS [ATS]  
Scarce✦✦✦✦ Valuable ✦✦✦✦ Secure ✦     ▬ Streaming Money ▬ Creating Value ▬
Pages: « 1 ... 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 [776] 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!