Author

Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 234. (Read 317079 times)

legendary
Activity: 1722
Merit: 1002
Decentralize Everything
Right.  Good BST morning all.

I need some help and suggestions.

Obviously this coin is getting to a stage where a concerted effort with testing is needed.  Once testing is completed and Thrones are live we will also need to make it as easy as possible to set up a Throne.

This is where it helps that I am a complete idiot when it comes to compiling daemons.

I want to create an idiots guide to compiling Crowncoin on a Linux VPS.  Anybody want to help? 

I spent an hour or two trying to compile on Ubuntu 16.01 yesterday with no luck.

These are the steps I tried:

Code:
sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils

sudo apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev

sudo add-apt-repository ppa:bitcoin/bitcoin

sudo apt-get update

sudo apt-get install libdb4.8-dev libdb4.8++-dev

mkdir -p src && cd src

git clone https://github.com/Crowndev/crowncoin.git

cd crowncoin/

git checkout master

./autogen.sh && ./configure  && sudo make install -j 2

This is the output when compile failed:

Code:
ubuntu@server-1:~/src/crowncoin$ ./autogen.sh && ./configure  && sudo make install -j 2
configure.ac:118: installing 'src/build-aux/compile'
configure.ac:12: installing 'src/build-aux/config.guess'
configure.ac:12: installing 'src/build-aux/config.sub'
configure.ac:37: installing 'src/build-aux/install-sh'
configure.ac:37: installing 'src/build-aux/missing'
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
src/Makefile.am: installing 'src/build-aux/depcomp'
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
parallel-tests: installing 'src/build-aux/test-driver'
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... no
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... no
checking for xgettext... no
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether strerror_r is declared... yes
checking for strerror_r... yes
checking whether strerror_r returns char *... yes
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -pie... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... default
checking for main in -ldb_cxx-4.8... yes
checking miniupnpc/miniwget.h usability... no
checking miniupnpc/miniwget.h presence... no
checking for miniupnpc/miniwget.h... no
checking miniupnpc/miniupnpc.h usability... no
checking miniupnpc/miniupnpc.h presence... no
checking for miniupnpc/miniupnpc.h... no
checking miniupnpc/upnpcommands.h usability... no
checking miniupnpc/upnpcommands.h presence... no
checking for miniupnpc/upnpcommands.h... no
checking miniupnpc/upnperrors.h usability... no
checking miniupnpc/upnperrors.h presence... no
checking for miniupnpc/upnperrors.h... no
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
checking for SSL... yes
checking for CRYPTO... yes
checking for PROTOBUF... no
configure: WARNING: libprotobuf not found; crowncoin-qt frontend will not be built
checking whether to build crowncoind... yes
checking whether to build crowncoin-cli... yes
checking whether to build Crowncoin GUI... no (Qt)
checking if ccache should be used... no
checking if wallet should be enabled... yes
checking whether to build with support for UPnP... no
checking whether to build test_crowncoin... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/test/Makefile
config.status: creating src/qt/Makefile
config.status: creating src/qt/test/Makefile
config.status: creating share/setup.nsi
config.status: creating share/qt/Info.plist
config.status: creating qa/pull-tester/run-crowncoind-for-test.sh
config.status: creating qa/pull-tester/build-tests.sh
config.status: creating src/crowncoin-config.h
config.status: executing depfiles commands
sudo: unable to resolve host server-1
Making install in src
make[1]: Entering directory '/home/ubuntu/src/crowncoin/src'
Making install in .
make[2]: Entering directory '/home/ubuntu/src/crowncoin/src'
  CXX      addrman.o
  CXX      activethrone.o
  CXX      alert.o
  CXX      bloom.o
  CXX      checkpoints.o
  CXX      coins.o
  CXX      init.o
  CXX      keystore.o
  CXX      leveldbwrapper.o
  CXX      main.o
main.cpp: In function ‘bool ProcessMessage(CNode*, std::__cxx11::string, CDataStream&)’:
main.cpp:4274:14: warning: variable ‘allowFree’ set but not used [-Wunused-but-set-variable]
         bool allowFree = false;
              ^
  CXX      miner.o
  CXX      names.o
  CXX      net.o
  CXX      noui.o                                                                 CXX      rpcblockchain.o
  CXX      rpcdarksend.o
  CXX      rpcmining.o
  CXX      rpcmisc.o
  CXX      rpcnames.o
  CXX      rpcnet.o
  CXX      rpcrawtransaction.o
  CXX      rpcserver.o
In file included from /usr/include/boost/move/detail/type_traits.hpp:34:0,
                 from /usr/include/boost/move/core.hpp:54,
                 from /usr/include/boost/move/utility_core.hpp:29,
                 from /usr/include/boost/move/utility.hpp:28,
                 from /usr/include/boost/thread/detail/move.hpp:27,
                 from /usr/include/boost/thread/lock_types.hpp:11,
                 from /usr/include/boost/thread/pthread/mutex.hpp:16,
                 from /usr/include/boost/thread/mutex.hpp:16,
                 from allocators.h:13,
                 from serialize.h:9,
                 from bignum.h:9,
                 from chainparams.h:9,
                 from base58.h:17,
                 from rpcrawtransaction.cpp:6:
/usr/include/boost/variant/get.hpp: In instantiation of ‘typename boost::add_reference::type boost::strict_get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = boost::detail::variant::void_; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’:
/usr/include/boost/variant/get.hpp:284:25:   required from ‘typename boost::add_reference::type boost::get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = boost::detail::variant::void_; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’
rpcrawtransaction.cpp:299:77:   required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE
     BOOST_STATIC_ASSERT_MSG(
     ^
Makefile:886: recipe for target 'rpcrawtransaction.o' failed
make[2]: *** [rpcrawtransaction.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/ubuntu/src/crowncoin/src'
Makefile:908: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/ubuntu/src/crowncoin/src'
Makefile:509: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1
ubuntu@server-1:~/src/crowncoin$


Anybody want to help me write an idiots guide to compiling?
legendary
Activity: 1092
Merit: 1000
legendary
Activity: 1092
Merit: 1000
Will the Thrones feature require to hold the collateral 10,000 CRW in an unencrypted wallet (so that the daemon can sign messages on demand or something), or can the wallet be encrypted as well?

Hi domob,

Absolutely, you can encrypt your Throne wallet.

We're still testing, we could use some help! Ima get a chat going in the Crowncoin slack so we can discuss testing, if youd like to join.

{Slack link}
legendary
Activity: 1764
Merit: 1022
Sure mam, it will run up soon - finishing "thrones" integration now

Is this coin works well?

Some nice movement in the markets today. CRW is up to 400 sat and with buy support on both YoBit and C-Cex.

legendary
Activity: 1135
Merit: 1166
Will the Thrones feature require to hold the collateral 10,000 CRW in an unencrypted wallet (so that the daemon can sign messages on demand or something), or can the wallet be encrypted as well?
hero member
Activity: 808
Merit: 500
Sure mam, it will run up soon - finishing "thrones" integration now

Is this coin works well?
sr. member
Activity: 325
Merit: 250
legendary
Activity: 1092
Merit: 1000
Thrones code is currently being tested. Hopefully we can have Thrones on mainnet within 24hours!

Everyone ready for the gold rush?? Theres going to be a period of time where only a few people have Thrones and will be spliting 40% of the coinbase reward between them. I'm going to be one of them Tongue
hero member
Activity: 808
Merit: 500
Very nice message. Thank you for the support!

I'm looking to buy a fairly large amount of CRW.  PM me if interested in selling.

Would prefer to trade on an exchange to save using escrow.
legendary
Activity: 1722
Merit: 1002
Decentralize Everything
I'm looking to buy a fairly large amount of CRW.  PM me if interested in selling.

Would prefer to trade on an exchange to save using escrow.

The bounty for adding Thrones has a significant amount of Crowncoin as part of the deal.
The dev may not want to keep all the coins we give him.

So I can ask him and at what price he'd like to sell at

Pm me an around figure you wanna buy

Welcome Smiley

I've got my budget...the amount I want to buy depends entirely on how many are for sale and at what price Wink
legendary
Activity: 1092
Merit: 1000
I'm looking to buy a fairly large amount of CRW.  PM me if interested in selling.

Would prefer to trade on an exchange to save using escrow.

The bounty for adding Thrones has a significant amount of Crowncoin as part of the deal.
The dev may not want to keep all the coins we give him.

So I can ask him and at what price he'd like to sell at

Pm me an around figure you wanna buy

Welcome Smiley
legendary
Activity: 1722
Merit: 1002
Decentralize Everything
I'm looking to buy a fairly large amount of CRW.  PM me if interested in selling.

Would prefer to trade on an exchange to save using escrow.
legendary
Activity: 1092
Merit: 1000
----- Crowncoin Thrones Implementation Update -----

Crowncoin will soon become the first crypto currency with merged mining and Thrones (masternodes).

The coinbase reward will stand at 60%/40% to miners and Thrones (6 CRW per block to miners and 4 CRW per block to Thrones, currently.)

The collateral needed will be 10,000 CRW to take a seat. In the future, when we have a healthy established group of Thrones the amount needed for collateral will be considered to drop.

Basicly we're trying to incentivise more long term full nodes on the network.

We hope to be testing within the next 24 hours!

If you want to see this project succeed, please help out in testnet.
More info on testing coming soon.

legendary
Activity: 1092
Merit: 1000
From what i'v been told the team is behind the move and agree it'll be beneficial to Crowncoin.

I can agree that it will bring SOME nodes. But nowhere near what your planning because you don't have near enough marketing or miners to do so. Who wants to setup a masternode for a coin when blocks aren't being processed by miners? Or the difficulty is too high because miners left? I myself only run full nodes for Transfercoin. And I do run masternodes for Transfercoin as well. BUT that is my project. I have the funds to run masternode's for other coins but choose not to. Because the payment for running the node doesn't cover the resources used.

You can pick up a vps for $2 these days.

look at the 100 node section on this sheet. As long as its profitable to host a node, people will

https://docs.google.com/spreadsheets/d/1x4KjbxtqGPKghajJb3scJBL6ED3B_CCBbYES6N6CR28/edit#gid=0
legendary
Activity: 964
Merit: 1000
From what i'v been told the team is behind the move and agree it'll be beneficial to Crowncoin.

I can agree that it will bring SOME nodes. But nowhere near what your planning because you don't have near enough marketing or miners to do so. Who wants to setup a masternode for a coin when blocks aren't being processed by miners? Or the difficulty is too high because miners left? I myself only run full nodes for Transfercoin. And I do run masternodes for Transfercoin as well. BUT that is my project. I have the funds to run masternode's for other coins but choose not to. Because the payment for running the node doesn't cover the resources used.
legendary
Activity: 1092
Merit: 1000
All info on development will be updated on here ASAP
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
I don't have a clue what's going on here.

Me neither  Cheesy

Very strange statements from your "knight".

Still, it looks like you've already decided, so I'll just see how it all unravels.
legendary
Activity: 1092
Merit: 1000
On ignore you go - put a skirt on tonight  Wink a cheap trick in the cryptocurrency world

That's fine.

Thank you for the detailed & mature explanation.


I don't have a clue what's going on here.

Can we keep the conversation to current development? The issue of paid full nodes it hot.
We are very close to agreeing on methods of implementation and i'd like as many people on board as possible.

I'm still unconvinced that adding paid full nodes to Crowncoin is a bad thing. Infact, IMO they will benefit Crowncoin.
From what i'v been told the team is behind the move and agree it'll be beneficial to Crowncoin.

Also with the implementation of paid full nodes, crowncoin will become unique in it's own right. Crowncoin will become the
first crypto currency that has merged mining with bitcoin and masternodes. This will attract new fans and investors, subsequently
making Crowncoin more appealing to merge mine. More pools will pick us up and hashrate will rise.

We will have one unbelievably secure network, with potentially over a P/h of consistent network hashrate and 250 full nodes within 6 months!

How is this bad?

Some speculation on paid full node income

https://docs.google.com/spreadsheets/d/1x4KjbxtqGPKghajJb3scJBL6ED3B_CCBbYES6N6CR28/edit#gid=631622617
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
On ignore you go - put a skirt on tonight  Wink a cheap trick in the cryptocurrency world

That's fine.

Thank you for the detailed & mature explanation.
Jump to: