I have the following error during compilation: /usr/local/cuda/bin/nvcc -I. -I/usr/local/cuda/include -O3 -lineno -Xcompiler -Wall -D_FORCE_INLINES -gencode=arch=compute_20,code=\"sm_21,compute_20\" -o scrypt/salsa_kernel.o -c scrypt/salsa_kernel.cu
nvcc fatal : Unsupported gpu architecture 'compute_20'
Makefile:2717: recipe for target 'scrypt/salsa_kernel.o' failed
make[2]: *** [scrypt/salsa_kernel.o] Error 1
make[2]: *** Waiting for unfinished jobs....
May I ask if someone can help me with this? compute 20 is not supported on cuda9. just remove the relavant parts in Makefile.am, then run autogen.sh and configure again. |
|
|
|
I just cloned the wallet and did another compile and got this:
"/usr/include/c++/5/bits/unique_ptr.h:49:28: note: declared here
template<typename> class auto_ptr;
^
CXX net.o
CXX noui.o
CXX rpcblockchain.o
CXX rpcmining.o
rpcmining.cpp: In function ‘json_spirit::Value getblocktemplate(const Array&, bool)’:
rpcmining.cpp:575:52: error: invalid use of incomplete type ‘class CWallet’
pblocktemplate = CreateNewBlock(pwalletMain->GetDefaultPubKey());
^
In file included from rpcmining.cpp:9:0:
init.h:11:7: note: forward declaration of ‘class CWallet’
class CWallet;
^
Makefile:882: recipe for target 'rpcmining.o' failed
make[3]: *** [rpcmining.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/xcn/Cryptonite/src'
Makefile:904: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/xcn/Cryptonite/src'
Makefile:676: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/xcn/Cryptonite/src'
Makefile:510: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
"
is something not working in there?
my .configure:
./configure CFLAGS="-O3 -march=native -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free" CXXFLAGS="-O3 -march=native -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free" CRYPTO_LIBS="-lcrypto -ltcmalloc" --without-gui --disable-wallet
does it do the same if you remove all the malloc related flags? |
|
|
|
Interesting fact I just learned about bisq: They support other base coins next to BTC. Trading always goes FIAT/Altcoin <-> Basecoin. As a result, I now have a new personal goal: Get bisq to add XCN as a base coin. That would be the perfect place because of our high similarity with BTC - at least with regards to usability. Our faster transactions and way higher scaling potential should become interesting for traders in the future when BTC transaction fees skyrocket even further  Great idea! I hope the decentralised exchanges do finally pick up, maybe we will have less crypto dramas in the future. |
|
|
|
Update: New Coin Request for bisq.network exchange is submitted. Let's hope all goes well and we are accepted. I did everything I can to fulfill their requirements. It all should go smoothly. Unfortunately, my server just started having issues so the explorer is down. I'm on it. edit: back up & syncing from fresh thanks! |
|
|
|
is smth new from yobit?
not yet they don't speak much :-) |
|
|
|
What does the text in Russian means?
6 days behind... does it go ahead, albeit slowly, or is it just stuck? could you please post a snippet of debug.log to better see what's going on? |
|
|
|
Dont get it about simd and groesti.
Two of the slowest algos of the X1X chains, which sp_ devoted a lot of work to (rightfully). Also they are probably what you can improve more, based on alexis code. Ironically two of the better functions on the CPU. There is no HW AES on a GPU so that affects Groestl. Simd on the CPU is horizontally vectorized maybe it will provide some ideas for improving the GPU implementation. By horizontal I mean that a single nonce can be hashed using vector instructions where vertical would be hashing multiple nonces in parallel in a single thread. Expand is done in 8-way, using warp shuffle. |
|
|
|
What does the text in Russian means? |
|
|
|
Hey sp, any possibility to increase speed at phi algo?
Just apply phi to alexis branch. There is no simd nor groestl in phi. So alexis now making some work at phi direction? Dont get it about simd and groesti. Two of the slowest algos of the X1X chains, which sp_ devoted a lot of work to (rightfully). Also they are probably what you can improve more, based on alexis code. |
|
|
|
Hey sp, any possibility to increase speed at phi algo?
Just apply phi to alexis branch. There is no simd nor groestl in phi. |
|
|
|
Pallas, deleting old transactions from the oldblock node localbase occurs only when running with the -prune tag? if node always on uptime miniblockchaine not work? not delete?
Mini-blockchain by default doesn't delete old block data (including transactions). That's by design: we want to be sure all the information about the wallet transactions is not lost. That is, you are not sure about the mini block technology? and can you describe the possible risks? They(risks) fully understood? What do you mean by "you are not sure about the mini block technology?"? And what kind of risks are you asking about: technical ones like loosing coins and the like? If that's the question, I think the answer lies in the almost 4 years of the coin history, and still working and rocking! Yes, I see that everything is working and swinging , but you say that the deletion is disabled for a full node so that transactions are not lost, it means if you enable deletion on all full nodes by default, then there will be possible risks of transaction loss, so I ask you about these risks have a technical description of such situations? situations of loss of transactions? In the case you are describing, the transactions are not lost, they are saved in the wallet database, and on the account balance sheet (as a final amount). And in the nodes who have a long enough blockchain, of course. What you loose is the ability to see the transaction details. That is, they are shown with a question mark on the gui wallet. If you download a blockchain snapshot, that will be fixed, but you also get a big datadir as a side effect. I think that the current default makes the most sense, but of course it is open for discussion. it's just a matter of the design of the design of the wallet and these transaction losses do not affect the balances? why not then design the database of transactions in the wallet, for example, in some way delete these old transactions, not only from the old blocks but also from the wallet database? We have a miniblock protocol, it should logically lead to a mini-wallet protocol? PS sorry for my english google translate..... While I tend to agree with you, I also think that people would get confused if they don't find their old transactions. |
|
|
|
Pallas, deleting old transactions from the oldblock node localbase occurs only when running with the -prune tag? if node always on uptime miniblockchaine not work? not delete?
Mini-blockchain by default doesn't delete old block data (including transactions). That's by design: we want to be sure all the information about the wallet transactions is not lost. That is, you are not sure about the mini block technology? and can you describe the possible risks? They(risks) fully understood? What do you mean by "you are not sure about the mini block technology?"? And what kind of risks are you asking about: technical ones like loosing coins and the like? If that's the question, I think the answer lies in the almost 4 years of the coin history, and still working and rocking! Yes, I see that everything is working and swinging , but you say that the deletion is disabled for a full node so that transactions are not lost, it means if you enable deletion on all full nodes by default, then there will be possible risks of transaction loss, so I ask you about these risks have a technical description of such situations? situations of loss of transactions? In the case you are describing, the transactions are not lost, they are saved in the wallet database, and on the account balance sheet (as a final amount). And in the nodes who have a long enough blockchain, of course. What you loose is the ability to see the transaction details. That is, they are shown with a question mark on the gui wallet. If you download a blockchain snapshot, that will be fixed, but you also get a big datadir as a side effect. I think that the current default makes the most sense, but of course it is open for discussion. |
|
|
|
Pallas, deleting old transactions from the oldblock node localbase occurs only when running with the -prune tag? if node always on uptime miniblockchaine not work? not delete?
Mini-blockchain by default doesn't delete old block data (including transactions). That's by design: we want to be sure all the information about the wallet transactions is not lost. That is, you are not sure about the mini block technology? and can you describe the possible risks? They(risks) fully understood? What do you mean by "you are not sure about the mini block technology?"? And what kind of risks are you asking about: technical ones like loosing coins and the like? If that's the question, I think the answer lies in the almost 4 years of the coin history, and still working and rocking! |
|
|
|
Pallas, deleting old transactions from the oldblock node localbase occurs only when running with the -prune tag? if node always on uptime miniblockchaine not work? not delete?
Mini-blockchain by default doesn't delete old block data (including transactions). That's by design: we want to be sure all the information about the wallet transactions is not lost. |
|
|
|
So will this coin on the YoBit  It's been almost a week since it was announced about adding it to the YoBit. No news from them: I will open a ticket ASAP. |
|
|
|
Pallas, if I send coins to the coinbase address then the coinbase balance increases and the reward for the block increases?
Nobody ever tried it, but I think it would work as you are suggesting. I tried and I succeeded, balance the public key 0 (coinbase) increased, it's funny, you can burn the coins to redistribute their descendants Yes, it's a side effect of the coinbase account I never though of :-) It may be considered a feature by itself, and we could even play a bit of marketing on it... Could you ask btc38 to send any of those "excess" coins to the coinbase account to keep them off market? I guess we could try asking, it won't hurt. |
|
|
|
If we are to compare with the speed of a GTX 1080Ti (~ 24 Mh/s) we can say that there are over 5800 cards mining now.
It's 36 MH/s How do you get 36 Mh/s on a 1080Ti? Which miner? |
|
|
|
|
I'm on a different chain: blocks 108, diff 7
|
|
|
|
|
that's the old test chain.
|
|
|
|
|
Show Posts
