Hi barwizi,
Could you tell me what's the target blocktime of NRS?
Topic: [ANN] NoirShares Trade on PoloniEX, Noir Investment Options Open - page 12. (Read 53424 times)
March 19, 2014, 06:07:28 AM
March 19, 2014, 05:40:52 AM
Where are the current/proposed short term investments documented? Can't see on this thread or noirbitstalk.
I guess that means there are none at the moment.
Where would they be normally then please? I'm surprised there are none as there seems to be posts on a mining investment or is that something else?
The mining investment is actually coming from the General Fund. Noir Group is still in development so the General Fund is all there is at the moment, and the mining is basically putting the investments to work in the mean time.
Thanks for explaining. Another thing is that short term investments require work which i can't put it because at the moment we need at least two long term ventures operational. NoirShares is not a venture, it's a vehicle. First will be the exchange then maybe the content store. If the investors agree, then i'll be tasked to do a short term one, or else they'll ask me to find someone that will while i keep working on other projects. Investors make the policy around here and i just effect it.
March 19, 2014, 05:11:29 AM
Where are the current/proposed short term investments documented? Can't see on this thread or noirbitstalk.
I guess that means there are none at the moment.
Where would they be normally then please? I'm surprised there are none as there seems to be posts on a mining investment or is that something else?
The mining investment is actually coming from the General Fund. Noir Group is still in development so the General Fund is all there is at the moment, and the mining is basically putting the investments to work in the mean time.
March 19, 2014, 05:04:10 AM
Where are the current/proposed short term investments documented? Can't see on this thread or noirbitstalk.
I guess that means there are none at the moment.
Where would they be normally then please? I'm surprised there are none as there seems to be posts on a mining investment or is that something else?
March 19, 2014, 04:59:03 AM
Hi!!
I need some help here
I cant use coyote miner i'm getting this
I need some help here
I cant use coyote miner i'm getting this
Code:
[root@localhost Documentos]# ./linux_coyote_miner.0.3.0
./linux_coyote_miner.0.3.0: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
./linux_coyote_miner.0.3.0: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
Install "libssl1.0.0" and "libssl-dev" on your system.
March 19, 2014, 04:57:36 AM
Where are the current/proposed short term investments documented? Can't see on this thread or noirbitstalk.
I guess that means there are none at the moment.
March 19, 2014, 04:49:06 AM
Where are the current/proposed short term investments documented? Can't see on this thread or noirbitstalk.
March 19, 2014, 04:25:59 AM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
Pass on Gridseed, 3 months warranty = they must have faith in their product.
March 19, 2014, 02:34:24 AM
sent 0.15 BTC as investment for NIG.
user Frigga77
Tx ID: 88c9044ef110688d14c03305155ae27a220d50e26729d4d2bde4320225d89c49
user Frigga77
Tx ID: 88c9044ef110688d14c03305155ae27a220d50e26729d4d2bde4320225d89c49
March 19, 2014, 01:32:37 AM
Can someone,very briefly, explain the investment system? I have seen the documents about it but it seems kinda complicated :-)
I would like to hear a "for dummies" from another user.
Thanks in advance!
I would like to hear a "for dummies" from another user.
Thanks in advance!
March 19, 2014, 01:18:18 AM
what problem with pool? can't connect.!
March 18, 2014, 11:02:42 PM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
I would say pass on gridseed as well. Though I would encourage you using more funds toward development. I imagine many of us already mine at home so are less concerned about shares in mining and more interested in further development.
Update: Back in business, finding blocks, processing payouts etc. Sorry for the lengthy delay, blockchain download kept getting stuck.
Investors tend to like returns that are tangible and i have noticed that many attempts at bulding platforms died because managment took a long time to deliver. I was hoping to keep invetsors interested, while not just sitting on their funds. For now i am looking for web developers to help with modifying noirbitstalk to add some NIG specific features.
March 18, 2014, 10:33:36 PM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
Couple thoughts:
1. There is so much heavy hashing equipment coming down the pipe for sha256. I think we will see a huge jump in difficulty again so I am concerned with trying to constantly play catch up.
2. The money in altcoins right now could disappear due to all the scams and pump & dumps. This would result in a retreat into LTC. If that does happen then scrypt mining will become extremely unprofitable because all the horsepower will be concentrated and the gridseed worthless.
Stick with sha256, mergemining ftw.
March 18, 2014, 09:28:42 PM
Hi!!
I need some help here
I cant use coyote miner i'm getting this
I think is something about shared libraries
so i decided build my own
this is my best approach
Any help would be appreciated i really like this coin
I need some help here
I cant use coyote miner i'm getting this
Code:
[root@localhost Documentos]# ./linux_coyote_miner.0.3.0
./linux_coyote_miner.0.3.0: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
My environment is a CentOS 6.4 and Dual Xeon ./linux_coyote_miner.0.3.0: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
I think is something about shared libraries
so i decided build my own
this is my best approach
Code:
[root@localhost coyote_miner]# cd bitshares/
[root@localhost bitshares]# git clone https://github.com/InvictusInnovations/fc.git
Initialized empty Git repository in /home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/.git/
remote: Counting objects: 3908, done.
remote: Compressing objects: 100% (1912/1912), done.
remote: Total 3908 (delta 1814), reused 3891 (delta 1803)
Receiving objects: 100% (3908/3908), 2.69 MiB | 496 KiB/s, done.
Resolving deltas: 100% (1814/1814), done.
[root@localhost bitshares]# cd ..
[root@localhost coyote_miner]# cmake . -DCMAKE_BUILD_TYPE=Release -DBoost_INCLUDE_DIR:PATH=/opt/include -DBoost_LIBRARY_DIR:PATH=/opt/lib
statusCompiling on UNIX
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- thread
-- date_time
-- system
-- filesystem
-- program_options
-- signals
-- serialization
-- chrono
-- unit_test_framework
-- context
-- coroutine
-- Configuring project fc located in: /home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc
-- Configuring fc to build on Unix/Apple
-- Using custom FindBoost.cmake
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- thread
-- date_time
-- system
-- filesystem
-- program_options
-- signals
-- serialization
-- chrono
-- unit_test_framework
-- context
-- coroutine
-- locale
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
-- Finished fc module configuration...
-- Using as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib64/libdb_cxx.sooptimized/usr/lib64/libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Configuring Bitshares on UNIX/APPLE
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.3")
-- Finished Bitshares configuration...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/Desarrollo01/Documentos/Noir/coyote_miner
[root@localhost coyote_miner]# make
Scanning dependencies of target easylzma_static
[ 1%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaDec.c.o
[ 1%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zBuf2.c.o
[ 2%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bra86.c.o
[ 2%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaEnc.c.o
[ 3%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zBuf.c.o
[ 3%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bcj2.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/BraIA64.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zStream.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bra.c.o
/home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/vendor/easylzma/src/pavlov/Bra.c: In function ‘SPARC_Convert’:
/home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/vendor/easylzma/src/pavlov/Bra.c:108: warning: suggest parentheses around ‘&&’ within ‘||’
[ 5%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zFile.c.o
[ 5%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zCrc.c.o
[ 6%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaLib.c.o
[ 6%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzFind.c.o
[ 7%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Alloc.c.o
[ 7%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/compress.c.o
[ 8%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma_c.c.o
[ 8%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma_header.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzip_header.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/common_internal.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/decompress.c.o
Linking C static library libeasylzma_static.a
[ 9%] Built target easylzma_static
Scanning dependencies of target fc
[ 10%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/uint128.cpp.o
cc1plus: error: unrecognized command line option "-std=c++11"
cc1plus: warning: command line option "-fmax-errors=3" is valid for Fortran but not for C++
cc1plus: warning: command line option "-fmax-errors=3" is valid for Fortran but not for C++
cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs"
cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs"
make[2]: *** [bitshares/fc/CMakeFiles/fc.dir/src/uint128.cpp.o] Error 1
make[1]: *** [bitshares/fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2
[root@localhost bitshares]# git clone https://github.com/InvictusInnovations/fc.git
Initialized empty Git repository in /home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/.git/
remote: Counting objects: 3908, done.
remote: Compressing objects: 100% (1912/1912), done.
remote: Total 3908 (delta 1814), reused 3891 (delta 1803)
Receiving objects: 100% (3908/3908), 2.69 MiB | 496 KiB/s, done.
Resolving deltas: 100% (1814/1814), done.
[root@localhost bitshares]# cd ..
[root@localhost coyote_miner]# cmake . -DCMAKE_BUILD_TYPE=Release -DBoost_INCLUDE_DIR:PATH=/opt/include -DBoost_LIBRARY_DIR:PATH=/opt/lib
statusCompiling on UNIX
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- thread
-- date_time
-- system
-- filesystem
-- program_options
-- signals
-- serialization
-- chrono
-- unit_test_framework
-- context
-- coroutine
-- Configuring project fc located in: /home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc
-- Configuring fc to build on Unix/Apple
-- Using custom FindBoost.cmake
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- thread
-- date_time
-- system
-- filesystem
-- program_options
-- signals
-- serialization
-- chrono
-- unit_test_framework
-- context
-- coroutine
-- locale
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
-- Finished fc module configuration...
-- Using as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib64/libdb_cxx.sooptimized/usr/lib64/libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Configuring Bitshares on UNIX/APPLE
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.3")
-- Finished Bitshares configuration...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/Desarrollo01/Documentos/Noir/coyote_miner
[root@localhost coyote_miner]# make
Scanning dependencies of target easylzma_static
[ 1%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaDec.c.o
[ 1%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zBuf2.c.o
[ 2%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bra86.c.o
[ 2%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaEnc.c.o
[ 3%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zBuf.c.o
[ 3%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bcj2.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/BraIA64.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zStream.c.o
[ 4%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Bra.c.o
/home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/vendor/easylzma/src/pavlov/Bra.c: In function ‘SPARC_Convert’:
/home/Desarrollo01/Documentos/Noir/coyote_miner/bitshares/fc/vendor/easylzma/src/pavlov/Bra.c:108: warning: suggest parentheses around ‘&&’ within ‘||’
[ 5%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zFile.c.o
[ 5%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/7zCrc.c.o
[ 6%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzmaLib.c.o
[ 6%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/LzFind.c.o
[ 7%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/pavlov/Alloc.c.o
[ 7%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/compress.c.o
[ 8%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma_c.c.o
[ 8%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzma_header.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/lzip_header.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/common_internal.c.o
[ 9%] Building C object bitshares/fc/vendor/easylzma/src/CMakeFiles/easylzma_static.dir/decompress.c.o
Linking C static library libeasylzma_static.a
[ 9%] Built target easylzma_static
Scanning dependencies of target fc
[ 10%] Building CXX object bitshares/fc/CMakeFiles/fc.dir/src/uint128.cpp.o
cc1plus: error: unrecognized command line option "-std=c++11"
cc1plus: warning: command line option "-fmax-errors=3" is valid for Fortran but not for C++
cc1plus: warning: command line option "-fmax-errors=3" is valid for Fortran but not for C++
cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs"
cc1plus: warning: unrecognized command line option "-Wno-unused-local-typedefs"
make[2]: *** [bitshares/fc/CMakeFiles/fc.dir/src/uint128.cpp.o] Error 1
make[1]: *** [bitshares/fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2
Any help would be appreciated i really like this coin
March 18, 2014, 08:43:10 PM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
I would say pass on gridseed as well. Though I would encourage you using more funds toward development. I imagine many of us already mine at home so are less concerned about shares in mining and more interested in further development.
Update: Back in business, finding blocks, processing payouts etc. Sorry for the lengthy delay, blockchain download kept getting stuck.
March 18, 2014, 08:39:22 PM
Just a quick FYI before I start getting PM's. The pool is having an issue. The blockchain got corrupt, we are resyncing and should be good to go again really shortly.
March 18, 2014, 08:25:24 PM
Date: 3/18/2014 17:12
To: 9cViAqUd7AKKZY5UyJUQo6nXCVJGTar1F7
Debit: -2500.00 NRS
Transaction fee: -0.01 NRS
Net amount: -2500.01 NRS
Transaction ID: 4fcff9a3a5f5a98a60f67b8058d2d5c434e38f4d0971d0f01b7b3857c66c7f43
It's for NIG
To: 9cViAqUd7AKKZY5UyJUQo6nXCVJGTar1F7
Debit: -2500.00 NRS
Transaction fee: -0.01 NRS
Net amount: -2500.01 NRS
Transaction ID: 4fcff9a3a5f5a98a60f67b8058d2d5c434e38f4d0971d0f01b7b3857c66c7f43
It's for NIG
March 18, 2014, 08:22:58 PM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
IMO pass on gridseed and wait for something a little bigger.
I'd like to get in on a little scrypt action if that's what the group decides.
I also know of a site that can be used for voting for things like this if you want to go that route in the future.
March 18, 2014, 07:36:58 PM
BTW, sorry guys, it seems i'm making unilateral decision, should i expand our sha256 base or should i buy some gridseed? My personal calculations and opinion say to stick with sha256 but your opinions collectively are what i am more interested in.
March 18, 2014, 06:50:53 PM
User: jerjian
Amount: 0.55 BTC
Transaction number: ac73f0cc488306175ce3f1215afcd5875d9af2282ee981ad77bb5858d37197c4
Amount: 0.55 BTC
Transaction number: ac73f0cc488306175ce3f1215afcd5875d9af2282ee981ad77bb5858d37197c4
Jump to: