Got tired of waiting so i got angry and boom!!!! We have windows x64 build.  I think i'm addicted to my keyboard.  |
|
|
|
|
qmake "USE_QRCODE=1" "USE_UPNP=1" "USE_IPV6=1" bitcoin-qt.pro
mingw32-make -f Makefile.Release
"USE_UPNP=-"
|
|
|
|
No NRS potential
LOL...what One innovation does groupcoin have? |
|
|
|
any progress on code?
The old version has died, but the new one has not born yet.
The code works, there is source code already. I am trying to build an x64 windows wallet for release right now. Being slowed down by upnp. If i build it without, i can make the wallet available immediately. DO IT GUY!  I have contacted someone who may be able to help. I'm sure the version will be out very soon. |
|
|
|
Barwizi what is your view of supernet and do you think new nrs might have a place in it? Would it be beneficial to nrs to be part of this?
Well...you caught me. LOL, i already consulted with them and am working on a background project that is being considered for superNet. NRS itself should not be pulled into non NG initiatives so i stepped up the ante on my schedule. The initial idea was good enough for consideration, but i decided to really pull out all the stops. It has elements of previously suggested DACs in it and some new ideas as well, one thing i am hoping to make a permanent feature of all DAS and DACs is the voting function, it will enable compartmentalization of projects so i can keep moving on. Project X
============================
What Is Project X?
----------------------------
Project X is a Cryptocurrency that uses colored coins to discriminate types of currency.
The proposed implementation is to use 3 types of distinguishable colors whose properties will vary.
Color 1: Ordinary Tokens attained via PoW, they cannot however gain PoS
Color 2: Given out at block 1 to donators, they cannot be produced via PoW but gain 10% PoS which is paid out in color 1 tokens
Color 3: Given out at block 1 , airdropped to participating currencies. Can gain 1% which is paid out in color 1 tokens.
When will Project X be launched?
----------------------------------
Tentative Expected Launch date is 15/11/14, meanwhile, source code tested for building (without the balances for color 2 and 3)
will be available everyday @ 00:00 GMT. This will allow visible progress of the project. Once there is sufficient interest a nightly windows build will also be
made available for download.
Why Project X ?
--------------------------
Project X provides users the unique ability to acquire use, and even trade their currency using different property coins for different purposes.
example -- Keeping your Color 2 coins in your wallet without ever spending them allows them to gain more weight, meaning that your earn more interest on them.
You can then use your gained color 1 coins to perform your everyday purchases or trading on altcoin exchanges.
How to get Tokens
--------------------------
Color 1 token will only be available AFTER launch and can only be attained through mining or purchase from a miner, either on the forums or on an exchange.
Color 2 tokens will only be available BEFORE launch, these will be allocated based on donations made to the mutual fund. Overall Color 2 tokens will
represent 35% of the total money supply.
Color 3 tokens will only be available by holding balances of selected coins, these coins will be announced on the forum threads. On launch day, your balance @ 00:00 GMT will be recorded and allocated on the Project X
blockchain. These will represent 5% of the total money supply. The specs are in constant shift as i try to make it all functional and less prone to problems and conflicts. One of the biggest issues is the non divisibility of the tokens. Last time someone tried that (Pennies aka CENT) we all know what happened. |
|
|
|
I keep telling you, if you want to see a hoard of devs, copy-paste or otherwise, lets have a c++ version. And I will tell you again, it was started as a C++ version two years ago: https://github.com/killerstorm/bitcoin/tree/cbtcI implemented it in about a week. I guarantee half the altcoin forum will be on this in a matter of weeks. I don't see how that helps. Very few changes made by alt-coiners get back to Bitcoin Core, as most of those changes are risky, silly or not well-thought-out. Look at all the suggested improvements for bitcoin that made it to alts first (some that btc is only incorporating now). Well, compare number of commits which Bitcoin Core devs add to Bitcoin Core: https://github.com/bitcoin/bitcoin/commits/masterTo a number of commits which come from alt-coin devs to Bitcoin Core. Eve the UI designs you see in alts have more functionality and features as well as creative looks. UI designs are easy to make. Well, anyway, we will soon have a web/mobile wallet which is easy to integrate with alt-coins... In fact, it can also work with multiple alt-coins in one wallet. Forgive the fly by TO BITCOIN, which lacks the "incentive" you so rightly mentioned. I don't see how that helps. Very few changes made by alt-coiners get back to Bitcoin Core, as most of those changes are risky, silly or not well-thought-out. true since most of it is garbage but some ideas are actually quite good. UI designs are easy to make. Wish i could say the same Well, anyway, we will soon have a web/mobile wallet which is easy to integrate with alt-coins... In fact, it can also work with multiple alt-coins in one wallet.
I guess that will bring use to it, but i'm not sure about development. |
|
|
|
I am compiling bitcoin-0.9.3, I have some undefined reference about UPNP. But I had made miniupnpc-1.9.
make[3]: Entering directory `/D/BTC/Dev/bitcoin-0.9.3/src'
CXXLD bitcoind.exe
libbitcoin_server.a(net.o): In function `Z13ThreadMapPortv':
d:\BTC\Dev\bitcoin-0.9.3\src/net.cpp:1066: undefined reference to `_imp__upnpDiscover'
d:\BTC\Dev\bitcoin-0.9.3\src/net.cpp:1073: undefined reference to `_imp__UPNP_GetValidIGD'
Try using miniupnpc-1.9.20140610 or later, see https://github.com/bitcoin/bitcoin/commit/9f7f504efca27c7d390f121410846b45c1732761Tried this, no luck... bump anyone? |
|
|
|
|
Satoshi wanted to move it into 1.3 was it , a while ago.
|
|
|
|
Not saying this happened here...but don't cops have a habit of "finding" things when they need to.
I propose a situation whereby they were tipped off and did raid his home, found nothing and knew after all the recent lashing out at police tactics they would be in a difficult position since they just broke into his home with flimsy probable cause. A deal was made which benefited the guy and so the sentence was conveniently "suspended".
I don't know much about your legal system, but is this a possibility?
It's far more possible that a former MJ dealer had some drugs in his house isn't it? Let's be honest , guys dealing in illegal drugs don't suddenly turn into angels.Quite true, but as we all know there is always three sides to a story, i was throwing in a hypothesis. |
|
|
|
|
Not saying this happened here...but don't cops have a habit of "finding" things when they need to.
I propose a situation whereby they were tipped off and did raid his home, found nothing and knew after all the recent lashing out at police tactics they would be in a difficult position since they just broke into his home with flimsy probable cause. A deal was made which benefited the guy and so the sentence was conveniently "suspended".
I don't know much about your legal system, but is this a possibility?
|
|
|
|
Which Ubuntu? are you sure your ppas' are correct? Unable to correct problems, you have held broken packages. Try removing all the boost libs installed and start afresh. Is this a local machine or a server? If local i would suggest you use 14.04 and start from scratch. And if you are new to using bash just copy paste this line and press ret. sudo apt-get update && sudo apt-get upgrade && sudo apt-get install libjansson4 cmake qt4-qmake libgmp3-dev autotools-dev nautilus-open-terminal autoconf curl dos2unix libtool libcurl4-openssl-dev mesa-utils libncurses5-dev libboost-all-dev python3-pycurl python-simplejson python3-urllib3 python-beautifulsoup python-numpy-dev python3-numpy-dev libssl-dev libminiupnpc-dev libdb++-dev git qt-sdk openssh-server cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases lib32gcc1 libc6 libcurl4-openssl-dev libncurses5-dev pkg-config automake qt5-qmake
You can edit out the stuff you dont use, but basically this line sets up any ubuntu i have used for development and testing of coins. |
|
|
|
any progress on code?
The old version has died, but the new one has not born yet.
The code works, there is source code already. I am trying to build an x64 windows wallet for release right now. Being slowed down by upnp. If i build it without, i can make the wallet available immediately. |
|
|
|
How is the progress? Project seems to develop terribly slow, Yes, it have failed to attract a strong team of open source developers. I kinda understand why: people prefer to work on ambitious, beautiful projects (e.g. Ethereum), or on ones which are easy to monetize (alt-coins, startups). A good example is Vitalik Buterin: he started with colored coins, wrote some code and started the spec, but then switched to Ethereum. I think there was only one person besides me who had a resolve to make "fully usable" colored coins software, and was able to allocate enough time... But that person died(?) about a year ago... And I'm fairly good at building prototypes and developing concept, but I'm very reluctant to make final decisions and I hate taking responsibility. So this is unfortunate: I just couldn't finish it without a team. So the only option to keep the project alive was to commercialize it. ChromaWallet is now being developed by a startup company called ChromaWay, see here: http://chromaway.comIt is still open source, but priorities are different. So, about progress: we have been working on web/mobile wallet implemented in JS. It was started in July, now we have a complete wallet core and are integrating UI, I expect that it will be available in a week or two. You can find source code here: https://github.com/chromawayAs for the desktop wallet, beta version was released in June. It has few warts, which could have been fixed by now, but finishing it wasn't my priority. which is sad since issuing and P2P exchange of shares is IMHO one of most important and promising features of blockchain technology. I'm no longer interested in 'shares'. I've been following Bitcoin capital markets since 2012, and I came to a conclusion that they aren't good. The problem isn't in a lack of a decentralized marketplace, but in the very nature of the companies listed on these markets. There is a lot of scams, and there is also a lot of people doing it in a half-assed way, which is a recipe for a failure. There are almost no companies which are honest and profitable. There are also legal problems: selling shares without registering a public company is illegal in USA and many other countries. So I'm not interested in helping this shady market, especially if there is a chance that regulators will go after those who help to facilitate transactions. On the other hand, I cannot prevent people from issuing shares and bonds. BTW, while we are at it, I believe there is a better way to do crowdfunding with Bitcoin. Well, there are several ways to do it, the most intriguing is a combination of assurance contracts (like in Lighthouse: https://github.com/vinumeris/lighthouse/blob/master/README.md) with colored-coin like stuff. But it is more technically complex, so we will do it after we do normal colored coins. Any ETA on fully usable software? It depends on what qualifies as a fully usable software... I keep telling you, if you want to see a hoard of devs, copy-paste or otherwise, lets have a c++ version. I guarantee half the altcoin forum will be on this in a matter of weeks. The incentive of money always drives the fastest development. Look at all the suggested improvements for bitcoin that made it to alts first (some that btc is only incorporating now). Eve the UI designs you see in alts have more functionality and features as well as creative looks. |
|
|
|
the snapshot should have been taken at the moment the fork was ready to go live.
when all the coding is done, snapshot the addresses again and let all the dihonest ppl out.
I think it's pretty likely to happen as there was an issue with incorrect balances for some addresses. snaidervp, quite right. Queeq, the same 3 problem addresses. Fixed them all, except one individual...lol, @ 00:01 9/9/14 someone decided to send their coins to polo....likely to offload what they had bought up. Snapshot accuracy was confirmed later around 04:00 9/9/14. What do i do with this person? Do i allocate them their balance @ 00:00 or their actual snapshot balance? Thanks. From the neutral, simply switching standpoint that's nothing wrong with such behavior (dump once coin is abandoned by the original dev). From the more humanistic standpoint I'd allocate the balance after dump. Though it would contradict the initial announcement which is bad in general, so it must be more correct to stick to original plan. That would be me. You guys can blame me. But if the dev told me "Do not move your NRS after confirmation" or "Do not sell your NRS after snapshot", I would not move my coins to polo. I just trusted barwizi's plan (snapshot at 0:00 9/9/14) and followed market mechanism as I did with PTS. I'm just curious why snapshot is taken at different time from original announcement... Snapshot wasn't taken at a different time, IMO you jumped the gun a bit. ten minutes wait would have resulted in your balance showing properly. There is always variance in time , few seconds here, few minutes there. I will fix your balance, but i think you could have been a lot more cautious, and noone ( at least i dont) blame you for what you did. |
|
|
|
the snapshot should have been taken at the moment the fork was ready to go live.
when all the coding is done, snapshot the addresses again and let all the dihonest ppl out.
I think it's pretty likely to happen as there was an issue with incorrect balances for some addresses. snaidervp, quite right. Queeq, the same 3 problem addresses. Fixed them all, except one individual...lol, @ 00:01 9/9/14 someone decided to send their coins to polo....likely to offload what they had bought up. Snapshot accuracy was confirmed later around 04:00 9/9/14. What do i do with this person? Do i allocate them their balance @ 00:00 or their actual snapshot balance? |
|
|
|
|
Finally made some progress
but now i get stuck here Code: obj/net.o: In function `ThreadMapPort2(void*)':
c:\NoirShares\src/net.cpp:1052: undefined reference to `__imp_upnpDiscover'
c:\NoirShares\src/net.cpp:1059: undefined reference to `__imp_UPNP_GetValidIGD'
c:\NoirShares\src/net.cpp:1129: undefined reference to `__imp_freeUPNPDevlist'
c:\NoirShares\src/net.cpp:1064: undefined reference to `__imp_UPNP_GetExternalIP
Address'
c:\NoirShares\src/net.cpp:1087: undefined reference to `__imp_UPNP_AddPortMappin
g'
c:\NoirShares\src/net.cpp:1092: undefined reference to `__imp_strupnperror'
c:\NoirShares\src/net.cpp:1120: undefined reference to `__imp_strupnperror'
c:\NoirShares\src/net.cpp:1100: undefined reference to `__imp_UPNP_DeletePortMap
ping'
c:\NoirShares\src/net.cpp:1102: undefined reference to `__imp_freeUPNPDevlist'
c:\NoirShares\src/net.cpp:1103: undefined reference to `__imp_FreeUPNPUrls'
c:\NoirShares\src/net.cpp:1131: undefined reference to `__imp_FreeUPNPUrls'
Any ideas?
ifndef USE_UPNP
override USE_UPNP = -
endif
ifneq (${USE_UPNP}, -)
LIBS += -l miniupnpc -l iphlpapi
DEFS += -DMINIUPNP_STATICLIB -DUSE_UPNP=$(USE_UPNP)
endif
INCLUDEPATHS= \
-I"$(CURDIR)" \
-I"/c/deps/boost_1_55_0" \
-I"/c/deps/db-4.8.30.NC/build_unix" \
-I"/c/deps/openssl-1.0.1i/include" \
-I"/c/deps/miniupnpc"
LIBPATHS= \
-L"$(CURDIR)/leveldb" \
-L"/c/deps/boost_1_55_0/stage/lib" \
-L"/c/deps/db-4.8.30.NC/build_unix" \
-L"/c/deps/openssl-1.0.1i" \
-L"/c/deps/miniupnpc" |
|
|
|
Thanks for the news Barwizi,
When possible please enlight us about:
- When will exchanges have access over the new blockchain?
- How will the "new NRS" be claimed?
Personal suggestion to change NRS name:
NRS NoirShares -> NSX or NRSX (NoirSharesX)
Exchanges can have it as early as wednesday if we are satisfied with functionality. To claim your NRS simply import your private key. As for the name changes, i like the idea but NRSX sounds too similar to BTSX. I'll keep it in mind, mean time, i'm taking a few hours off. Working IRL + coding at night has me ready to collapse. I know the feeling. =) I suggested NoirSharesX because of popularity terms but yes, it should be different from them. More importantly I think it needs just to change. Keeping the same tag and using a different blockchain will open room for schemes... Besides that.. there is the problem of everyone trying to represent both "NRS" versions everywhere.. example: coinmarketcap, exchanges already with old NRS, faucets, and others. It can always have a "new" word before it.. or a version number, but I think it stands better for a new tag. we call them but simply NoirBitShares  easily NBS NoirBitSharesor NBSS NoirBitShareS or NRBSNoiRBitShares that's my favorite Interesting, |
|
|
|
When everything is ready, it would be good to post a guide with the link to download the new wallet and how to get the new NRS
I'm hoping some members of the community will step up and help. Right now my entire focus is on the actual wallet so i dont get time to do the stuff that requires human readable language (not too good at it myself). I think i'll post bounties for that too. is to test a wallet ready? Source code only |
|
|
|
When everything is ready, it would be good to post a guide with the link to download the new wallet and how to get the new NRS
I'm hoping some members of the community will step up and help. Right now my entire focus is on the actual wallet so i dont get time to do the stuff that requires human readable language (not too good at it myself). I think i'll post bounties for that too. |
|
|
|
Thanks for the news Barwizi,
When possible please enlight us about:
- When will exchanges have access over the new blockchain?
- How will the "new NRS" be claimed?
Personal suggestion to change NRS name:
NRS NoirShares -> NSX or NRSX (NoirSharesX)
Exchanges can have it as early as wednesday if we are satisfied with functionality. To claim your NRS simply import your private key. As for the name changes, i like the idea but NRSX sounds too similar to BTSX. I'll keep it in mind, mean time, i'm taking a few hours off. Working IRL + coding at night has me ready to collapse. I know the feeling. =) I suggested NoirSharesX because of popularity terms but yes, it should be different from them. More importantly I think it needs just to change. Keeping the same tag and using a different blockchain will open room for schemes... Besides that.. there is the problem of everyone trying to represent both "NRS" versions everywhere.. example: coinmarketcap, exchanges already with old NRS, faucets, and others. It can always have a "new" word before it.. or a version number, but I think it stands better for a new tag. Please check Pm |
|
|
|
|
Show Posts
Code:
