 Show Posts
|
|
Pages: [1] 2 »
|
Hey, there are a bunch of cheap ANC on ExchangeD right now  3069 ANC @ 0.00025 BTC |
|
|
|
^ oh and for those of you landing on this page, the above picture is version 0.9.4.4 wallet, and the theme is not finished yet (for example I have to get rid of the hardcoded ugly buttons in the upper tool bar) You can do your own QT theme too! Documentation |
|
|
|
clearnet only? cmon!
You're right, ANC deserves better here is the wallet runnin on i2p only, with static address. (The OS is Linux Mint 17):  |
|
|
|
This is an actual 0.9.4.4 anoncoin wallet I'm styling. It not so bad but I just need to get rid of these ugly bitcoin tool bar icons, looks like they're hardcoded... Don't mind the network state, I was not connected to the internet.  |
|
|
|
Just to let others know, I tried again to build the develop-themes branch on Debian (9) stretch x86 (and I'm not in a VM) but this time I deleted every anoncoin directories and started all new. I did follow the instructions and did exactly what is told here https://wiki.anoncoin.net/How_to_build_Anoncoin_develop , except that I did 'git checkout develop -themes' in that case. Unfortunately the last 'make' command still ends with the scrypt-sse2 error that I already posted, and no anoncoin programs are build. So my next step is to install debian 8 (Jessie) in a VM and try again. Sorry to flood here. Should I fill a bug report somewhere? can it be a problem with the chipset of my laptop? |
|
|
|
...ehrr.... there is still this same problem as before. I finished to build in the depends directory. Thank you lunokhod and cryptoslave for your fast answers. Fetching qt46 was long, and fetching bdb was a little too. And then after that I went back and cleaned the "root" directory anoncoin-develop-themes. I ran 'make clean', deleted the configure file, the makefile and all other files standing there except directories. Then I uncompressed the original develop-themes.zip again to take all the original files needed. As there is no configure script at first, I ran ./autogen.sh in there (not in depends anymore). and after that I did accordingly to the wiki tutorial shown by lunokhod ( https://wiki.anoncoin.net/How_to_build_Anoncoin_develop) ./configure --prefix=`pwd`/depends/i686-pc-linux-gnu And then it's here again, same errors: Making all in src
make[1]: Entering directory '/home/user/Code/anoncoin-develop-themes/src'
make[2]: Entering directory '/home/user/Code/anoncoin-develop-themes/src'
CXX libanoncoin_common_a-scrypt-sse2.o
scrypt-sse2.cpp: In function ‘void scrypt_1024_1_1_256_sp_sse2(const char*, char*, char*)’:
scrypt-sse2.cpp:124:50: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi]
X.i128[k] = _mm_xor_si128(X.i128[k], V[j + k]);
^
In file included from scrypt-sse2.cpp:36:0:
/usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h: In function ‘void xor_salsa8_sse2(__m128i*, const __m128i*)’:
/usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1282:1: error: inlining failed in call to always_inline ‘__m128i _mm_xor_si128(__m128i, __m128i)’: target specific option mismatch
_mm_xor_si128 (__m128i __A, __m128i __B)
^
scrypt-sse2.cpp:44:39: error: called from here
X0 = B[0] = _mm_xor_si128(B[0], Bx[0]);
^
In file included from scrypt-sse2.cpp:36:0:
/usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1282:1: error: inlining failed in call to always_inline ‘__m128i _mm_xor_si128(__m128i, __m128i)’: target specific option mismatch
_mm_xor_si128 (__m128i __A, __m128i __B)
^
scrypt-sse2.cpp:45:39: error: called from here
X1 = B[1] = _mm_xor_si128(B[1], Bx[1]); and finishes like that: scrypt-sse2.cpp:92:31: error: called from here
B[3] = _mm_add_epi32(B[3], X3);
^
Makefile:2674: recipe for target 'libanoncoin_common_a-scrypt-sse2.o' failed
make[2]: *** [libanoncoin_common_a-scrypt-sse2.o] Error 1
make[2]: Leaving directory '/home/user/Code/anoncoin-develop-themes/src'
Makefile:5136: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Code/anoncoin-develop-themes/src'
Makefile:573: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
So the only way I see to be sure is to delete everything and restart building clean. will do that in a few hours I think... |
|
|
|
wow, thank you lunokhod, I was totally looking in the wrong direction... not building in the depends folder was my error. I needed to "cd depends" after autogen.sh I'm used to stick to the README and INSTALL files when I'm compiling, and the instructions in the INSTALL file of the anoncoin-developp-themes were: ./autogen.sh
./configure
make
make install Next time I'll look more carrefully in the wiki before posting here. So now I have another building problem: I ran autogen.sh in the root of the anoncoin-developp-themes uncompressed folder, then ran cd depends, and make. But after 20 minutes or so, it is stuck at "fetching qt46", and top command shows no cpu activity for that task. I stopped, ran make again, same thing. All dependencies are satisfied by the way. |
|
|
|
Hi, I'm trying to compile the develop-themes on debian testing (stretch), and I have some errors related to sse2 as much as I can tell. I did 2 or 3 hours of research, no luck, so I'm turning to you because I can't acces IRC for the moment what I did:After succesfully running autogen.sh and configure, make stops and gives these particular errors (I'm giving interestings chunks of logs only): CXX libanoncoin_common_a-scrypt-sse2.o
scrypt-sse2.cpp: In function ‘void scrypt_1024_1_1_256_sp_sse2(const char*, char*, char*)’:
scrypt-sse2.cpp:124:50: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi]
X.i128[k] = _mm_xor_si128(X.i128[k], V[j + k]);
^ then many times this same error, repeatedly: In file included from scrypt-sse2.cpp:36:0:
/usr/lib/gcc/i586-linux-gnu/4.9/include/emmintrin.h:1282:1: error: inlining failed in call to always_inline ‘__m128i _mm_xor_si128(__m128i, __m128i)’: target specific option mismatch
_mm_xor_si128 (__m128i __A, __m128i __B)
^ and it all finishes like that: scrypt-sse2.cpp:92:31: error: called from here
B[3] = _mm_add_epi32(B[3], X3);
^
Makefile:2674: recipe for target 'libanoncoin_common_a-scrypt-sse2.o' failed
make[2]: *** [libanoncoin_common_a-scrypt-sse2.o] Error 1
make[2]: Leaving directory '/home/user/Code/anoncoin-develop-themes/src'
Makefile:5136: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Code/anoncoin-develop-themes/src'
Makefile:573: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1 I tried to add -msse2 flags to the makefile on the CPPFLAGS CXXFLAGS lines, but none of these work (nothing changed, and I did run "make clean" after every try). Is it really an sse2 related error? where can I make sure the -msse2 option is passed to the compiler? And yes my CPU has the sse2 flag (as far as cat /proc/cpuinfo can tell). Hope anyone of you can help me |
|
|
|
Hi all, the following is not an actual wallet theme, just a layout I've made to show the new logo background image I created. Wich is just a proposal and can still be modified. So pay only attention to the logo background at the bottom of this pix. If this is appreciated and if I'm not able to make a real QT wallet theme I can provide the background image for others to include in their own QT theme (and I'm not asking for a bounty for doing this  )  other link for picture: https://img.bi/#/Xo9njgk!m95U3Aj_C-bQEMz8Aw8WN-1wPwmfvg8o256QP1gd |
|
|
|
This is fucked up. From an assured Oct 15th testnet, to a week delay, to a 2-3 month delay. There's really nothing I can say, very weird way of acting.
When the darkcoin dev made a few mistakes along the way, I always felt assured that he would pull through with results, since he had his real name and face out there since day 1 (and had been delivering actual results) . With gnosis it feels like he can just walk away from all this stuff if he decides to and no one can hold him accountable for it. If he feels the task is too big after all, all he needs to do is stop posting.
These "delays" are going on for around a year already. Do not send any donations. As long as they receive donations they will pretend an activity "2 weeks" (TM). If gnosis was ever serious he would finish the coin long time ago and could become rich instantly from its repricing. But he is focused on cashing the donations only. Why is that? If I was not serious about implementing Zerocoin, don't you think I would have cashed out my donations by now? Note that they haven't moved: http://ancblockchain.com/address/AU4hFCFZLhB2gTyG4VbaEurXGrTMNW2nu6Listen, no one has even come close to the possible breakthrough that ANC/ZC represents. We recognize this isn't an easy undertaking and I'll admit, I was surprised at the fast time table ^_^. Shit happens, no worry lol. We understand that the coding takes time and are just a bit disappointed. The promise is still there and really the only hope for the future. I think the most important thing is just the question as to whether we can still get the initial hard fork to deal with multipool dumping/gaming the system and the txid >100kb transaction issue, aka digishield implementation + aux/pow. I think facilitating those updates in a short term manner, like immediately, would do a lot to help stabilize any uncertainty regarding the coins future. As long as we can still transfer coins back and forth from exchanges and private holders it helps address the a lot of the concerns; then we just wait for zc but can help work on the network strength in the meantime. Meeh, whats the good word  ? I agree with last comment above. We are urgently waiting for a word from Meeh and an upgrade to at least get stability and withdraw from the exchanges. |
|
|
|
Gnosis: hold on ! (and have sleep also). Your work is much appreciated |
|
|
|
Alacast- #1 = #1 lol then again the current logo's cool too, just very very different stylistically, like new modern techno vs crypto anarchism I know that n00n doesn't like 3D stuff, but here is a little compromise between the actual flat logo and something more techno-ish :   |
|
|
|
robinson5 (and stealth923 ?), unconfirmed transactions can happen with every coin (and this is unrelated to the bigger-than-100kb-transaction-size issue from the exchanges) I'm not an expert so anyone feel free to correct, but there are at least 2 things you can do: ===================== UNCONFIRMED TRANSACTIONS
What to do before saying Coin is broken  ===================== if your peers connexions are not good enough, transactions could be not well broadcasted. I think unconfirmed transactions are re-broadcasted regularly if you leave the wallet open (every 90 minutes ?). If this doesn't help, try the following:1. Rescan while your wallet is shut down: linux: windows (I think, not sure): If the transaction isn't broadcasted to other nodes, you may not be very connected to others, or not enough. It might really be a network/peers issue with your wallet/computer/firewall/ISP (?) Do the following: 2. get your transaction id : Run the wallet, and in the details, get to the unconfirmed transaction id, right click to get the transaction id. Then go to the console inside the wallet (help > debug window > console) and type this: getrawtransaction <transaction ID> replace <transaction ID> with the actual transaction ID you got previously in the wallet sent transactions details. You will then get a very large number. What you should do now is give that number to someone else who has his own anoncoin wallet well connected to network of peers, and let him broadcast the transaction for you, by going in his wallet console (help > debug window > console) and typing: sendrawtransaction 02bf32c36565verylargenumbershortened ( the raw transaction is very bigger than this above ) CONCLUSION ======== If and only if these methods didn't work, provide any error message and/or screenshots before saying the coin is broken please. If you dont believe this can happen in other coins (even bitcoin), search for "darkcoin frozen transactions how to fix it". Hope that helps... |
|
|
|
Alacast - I like your most recent logo. It's simple yet powerful. Could you use that with a darker/greyscale/black color scheme? I'd just like to see how else it would look. Keep the logos coming though, I like the creativity!
sure :  |
|
|
|
just to entertain you, here is another logo work (while more important issues are getting sorted out):  Everyone else is here: https://wiki.anoncoin.net/Logo |
|
|
|
|
