Topic: ▉ANN▉ MTNC ▉▉▉▉░ Masternodecoin ░▉▉▉ Multiple Privacy Center Platform - page 235. (Read 239101 times)

Sorry I read your comment, you, they gave you the 50,000 coins in the first round? I also thought that they would continue giving 50000 coins to new users and those who will participate in the following rounds, but what I think is that they are opting for the distribution model of: Deeponion

I was all for this project, but there's a few things that's making me suspicious.

- Originally it was said they wanted '1000' masternodes running which were going to be given to the community in airdrops. The first Airdrop was 50k, but then the second one was reduced to this:

Payment will be based on weekly MTNC: (That means payment will not send together ,just according to your submit date)
Newbie: 20 MTNC/weeks
Jr Member: 40 MTNC/weeks
Member: 60 MTNC/weeks
Full Member: 80 MTNC/week
Sr Member: 100 MTNC/week
Hero and Legendary: 120 MTNC/week

Im sorry, but from 50k each to about 400coins for the same amount of time, what?

- The block explorer doesn't work (http://23.247.2.51/) we have no idea if the dev is staking the 95million+ coins he has.. You can search for a transaction ID, but not an address etc. (M9EFGF1daJArCNFwg7VYtmMspt4qiiwr4p) is the address that received the premine of 100m, but I can't see any futher details as I can't search.

-  The funds gathered by the dev  (3BTC?) to be used for exchanges, where simply not used for exchanges..? Where is Yobit? They have a service to pay and have the coin listed in 3 days etc, instead we had to vote for exchanges.. IE https://c-cex.com/?id=vote&coin=mtnc (Which has NO votes. Surely if BTC was raised for this, we should have votes on it with BTC..)  How about using some of them to get a working block explorer?

- I don't see how this can be developed any further, there is no roadmap, no hints as to what is to come.

- What is to stop anyone else from simply cloning PRIVX/DASH and doing exactly the same, but being more transparent and fair?

- Bounties, I applied for the post of 'TEAM partner bounty' had nearly 200 posts with the signature and avatar, made a video, made a subreddit, made a discord etc, and was told ' tanks we pm if we need you' because id already done it all! Where is my bounty of 30k coins for making the video? I quote from the OP:

'making video will get 30000 MTNC for additional reward.'

Im not trying to FUD, just airing my concerns about this project and the future.  Until my questions have been answered to a satisfactory level, im removing the avatar and signature.

participants of second airdrop will receive 100 coins?

what a joke  

Have you installed all of the dependencies from the README file on Github?

pi@raspberrypi:~/masternodecoin $ make
cd /home/pi/masternodecoin/src/leveldb && CC=gcc CXX=g++ make OPT="-pipe -fstack-protector-all --param ssp-buffer-size=1 -D_FORTIFY_SOURCE=2 -O2" libleveldb.a libmemenv.a
make[1]: Entering directory '/home/pi/masternodecoin/src/leveldb'
make[1]: 'libleveldb.a' is up to date.
make[1]: 'libmemenv.a' is up to date.
make[1]: Leaving directory '/home/pi/masternodecoin/src/leveldb'
cd /home/pi/masternodecoin/src/secp256k1 && ./autogen.sh && ./configure --enable-module-recovery && CC=gcc CXX=g++ make OPT="-pipe -fstack-protector-all --param ssp-buffer-size=1 -D_FORTIFY_SOURCE=2 -O2"
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux/m4'.
libtoolize: copying file 'build-aux/m4/libtool.m4'
libtoolize: copying file 'build-aux/m4/ltoptions.m4'
libtoolize: copying file 'build-aux/m4/ltsugar.m4'
libtoolize: copying file 'build-aux/m4/ltversion.m4'
libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
configure.ac:10: installing 'build-aux/compile'
configure.ac:9: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
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 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 for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert armv7l-unknown-linux-gnueabihf file names to armv7l-unknown-linux-gnueabihf format... func_convert_file_noop
checking how to convert armv7l-unknown-linux-gnueabihf file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether make supports nested variables... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcc... gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for gcc option to accept ISO C89... (cached) none needed
checking if gcc supports -std=c89 -pedantic -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wstrict-prototypes -Wno-unused-function -Wno-long-long -Wno-overlength-strings... yes
checking if gcc supports -fvisibility=hidden... yes
checking for __int128... no
checking for __builtin_expect... yes
checking for x86_64 assembly availability... no
checking gmp.h usability... no
checking gmp.h presence... no
checking for gmp.h... no
checking for CRYPTO... yes
checking for main in -lcrypto... yes
checking for EC functions in libcrypto... yes
checking whether byte ordering is bigendian... no
configure: Using assembly optimizations: no
configure: Using field implementation: 32bit
configure: Using bignum implementation: no
configure: Using scalar implementation: 32bit
configure: Using endomorphism optimizations: no
configure: Building ECDSA pubkey recovery module: yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: executing depfiles commands
config.status: executing libtool commands
make[1]: Entering directory '/home/pi/masternodecoin/src/secp256k1'
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
gcc gen_context.o -o gen_context
./gen_context
  CC       src/libsecp256k1_la-secp256k1.lo
  CCLD     libsecp256k1.la
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
  CC       src/tests-tests.o
src/tests.c: In function ‘test_ecdsa_der_parse’:
src/tests.c:3561:52: error: dereferencing pointer to incomplete type ‘ECDSA_SIG {aka struct ECDSA_SIG_st}’
         valid_openssl = !BN_is_negative(sig_openssl->r) && !BN_is_negative(sig_openssl->s) && BN_num_bits(sig_openssl->r) > 0 && BN_num_bits(sig_openssl->r) <= 256 && BN_num_bits(sig_openssl->s) > 0 && BN_num_bits(sig_openssl->s) <= 256;
                                                    ^~
Makefile:933: recipe for target 'src/tests-tests.o' failed
make[1]: *** [src/tests-tests.o] Error 1
make[1]: Leaving directory '/home/pi/masternodecoin/src/secp256k1'
Makefile:846: recipe for target '/home/pi/masternodecoin/src/secp256k1/src/libsecp256k1_la-secp256k1.o' failed
make: *** [/home/pi/masternodecoin/src/secp256k1/src/libsecp256k1_la-secp256k1.o] Error 2
pi@raspberrypi:~/masternodecoin $

Hello! I had created an account at Bitzure some days before, but till now It`s free of 25 MTNC. Can You che this  ck it? My email [email protected]!

The first time Airdrop I attended, but I still did not receive the coin now. Is the problem in that?

Not much! About 770 MTNC...

Does anyone know how many coins a masternode generates per day?

500   Yeahr .....

I invested 0.9 btc at 0.00002500 on average

Thats Life  

People worried about the dip should relax all crypto is down right now even ethereum.

We just need to wait out this little speed bump

I have read the doc: https://github.com/masternodecoin/masternodecoin/blob/master/doc/readme-qt.rst

But the Link is dead... https://github.com/masternodecoindev/Ion/blob/master/doc/build-unix.md

But this file the same: https://github.com/masternodecoin/masternodecoin/blob/master/doc/build-unix.md

? regards and thanks

WTB 50000 MNTC , please pm for offers.

Have you installed all of the dependencies from the README file on Github?

sudo apt-get install qt5-default qt5-qmake qtbase5-dev-tools qttools5-dev-tools build-essential libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev libdb++-dev libminiupnpc-dev qt4-dev-tools libboost-dev libboost-thread-dev libboost-program-options-dev libboost-filesystem-dev libboost-system-dev libdb++-dev libminiupnpc-dev libssl-dev

very to late for joining