 Show Posts
|
|
Pages: [1]
|
OK. Disclaimer: I have never tried this myself. But if you have your virgin snapshot and still want to try it: sudo apt-get install gcc-4.8-base Not sure if this will deinstall 4.9, though. Try the gcc --version again after apt-get is finished. Edit: You may have to do the same with g++-4.8 |
|
|
|
Your compiler complains about lines that it should not complain about. Are you using a gcc version 4.8 or higher? What is the output of ? I get this: gcc (Ubuntu 4.9-20140406-1ubuntu1) 4.9.0 20140405 (experimental) [trunk revision 209157] That... looks kind of cool. Did you compile gcc yourself? All I can say is that gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1
works for me. If it isn't too much of a hassle, you could try to downgrade maybe? Okay, I'll try that. But... How can I downgrade? I still a noob. Thanks for your help. Hmm. What is the output of apt-cache policy gcc-4.8-base on your machine? |
|
|
|
Your compiler complains about lines that it should not complain about. Are you using a gcc version 4.8 or higher? What is the output of ? I get this: gcc (Ubuntu 4.9-20140406-1ubuntu1) 4.9.0 20140405 (experimental) [trunk revision 209157] That... looks kind of cool. Did you compile gcc yourself? All I can say is that gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1
works for me. If it isn't too much of a hassle, you could try to downgrade maybe? |
|
|
|
In http://monero.cc/getting-started there is a script written by Quanttek: cd ~ && rm -f install_monero.sh && wget https://monero.cc/downloads/install_monero.sh && bash install_monero.sh It will install all the pre-requirements and then it'll compile it for you. I tried this script twice, it did not work for me. Please could anyone tell me the meaning of these errors: /home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’:
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’
typedef unsigned __int128 uint128_t;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope
uint128_t res = (uint128_t) a * (uint128_t) b;
^
/home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope
low = (uint64_t) res; I dont think those are the errors to worry about, its the compiler just pointing out a few minor issues, it looked to me like your problem is with the make command trying to create folders, but I dont understand the error msgs. No, the necessary folders are created, I can see them after the make command has halted because of the shown errors. Therefor I am quite sure, that these errors cause the abort. Additional information: The OS runs in a virtual machine and I took a snapshot of the virgin. Each trial was done with an unaffected OS. Your compiler complains about lines that it should not complain about. Are you using a gcc version 4.8 or higher? What is the output of ? |
|
|
|
You can still doublespend with a 51% attack, nothing has changed about that attack vector
The 51% double-spend in either Bitcoin or CryptoNote is done by legitimizing a new chain after spending on the old chain. No scheme can prevent this because it outright replaces blockchain data. Networks are based on always trusting the longest chain.
In CryptoNote, the 51% attacker's new chain wouldn't have the spent key image so the DS would succeed. The DS proof mentioned in the whitepaper refers to spends on the same chain (51% attacks involve 2+ chains). Normally this wouldn't be worth mentioning since Bitcoin is also DS proof in the same sense, but CryptoNote's ring signatures are anonymous so preventing it isn't trivial. This is why they made a special mention of being DS proof, but it's not referring to a 51% attack situation.
Thank you guys, that was what I thought. Just more eloquent and succinct than I could have said it. And now I also see where the misunderstanding that Cryptonote is resistant to a 51% attack appears to come from: The guy didn't say anything near FUD. He was talking about XMR's ability to reduce negative affects of 51% issues such as a double-spend flaw. Here's the link and it has nothing to do with FUD but everything to do with the benefits of cryptonote (which includes XMR) https://cryptonote.org/inside.php#double-spend-proofThis also has more links to features of cryptonote: https://cryptonote.org/#Hope that helps clear things up. smh In this respect, it actually doesn't help. This overview causes confusion. The people responsible for https://cryptonote.org/inside.php#double-spend-proof should amend that section. It should be explicitly stated that it talks about prevention of doublespends strictly on the same chain, that is, when there is no alternate blockchain attack (These are possible with a hashing power of less than 50% of the network by the way. See https://bitcoil.co.il/Doublespend.pdf). People looking to invest in XMR read it when doing their due diligence and get wrong ideas, which they spread on the forums. Which in turn makes Monero look shady at first glance (making impossible promises raises red flags that it might be a scam). Sorry if I looked like a FUDster, just a long time lurker with low post count who needed clarification |
|
|
|
[...] Monero is most fundamental coin to the day. Not only it is strictly anonymous, it has double-spend proof even in case 51% attack. [...]
That's new to me. Is this true? How is that supposed to work? |
|
|
|
I have a problem compiling from the github repository version on Linux.
gcc 4.8.1, cmake 2.8.7 and libboost-all-dev 1.55
..
Can anyone help?
What linux? 64 bit? What command for compile? Ubuntu 12.04.4 LTS 64 bit. I removed the directory for tests from CMakeLists.txt and just invoked 'make'. Try this: https://bitcointalk.org/index.php?topic=577267.msg7383561#msg7383561No, still doesn't work. What was that remark about using cmake supposed to mean? |
|
|
|
I have a problem compiling from the github repository version on Linux.
gcc 4.8.1, cmake 2.8.7 and libboost-all-dev 1.55
..
Can anyone help?
What linux? 64 bit? What command for compile? Ubuntu 12.04.4 LTS 64 bit. I removed the directory for tests from CMakeLists.txt and just invoked 'make'. |
|
|
|
I have a problem compiling from the github repository version on Linux. gcc 4.8.1, cmake 2.8.7 and libboost-all-dev 1.55 Linking CXX executable connectivity_tool
`.text._ZN5boost16exception_detail19error_info_injectorINS_9gregorian9bad_monthEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_9gregorian9bad_monthEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_9gregorian9bad_monthEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_date_time.a(greg_month.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_9gregorian9bad_monthEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_9gregorian9bad_monthEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_date_time.a(greg_month.o)
`.text._ZN5boost16exception_detail10bad_alloc_D2Ev' referenced in section `.text._ZN5boost16exception_detail10bad_alloc_D1Ev[_ZN5boost16exception_detail10bad_alloc_D1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail10bad_alloc_D2Ev[_ZN5boost16exception_detail10bad_alloc_D5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail14bad_exception_D2Ev' referenced in section `.text._ZN5boost16exception_detail14bad_exception_D1Ev[_ZN5boost16exception_detail14bad_exception_D1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail14bad_exception_D2Ev[_ZN5boost16exception_detail14bad_exception_D5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_17bad_function_callEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_17bad_function_callEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_17bad_function_callEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_program_options.a(cmdline.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_17bad_function_callEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_17bad_function_callEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_program_options.a(cmdline.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_15program_options16validation_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_15program_options16validation_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_15program_options16validation_errorEED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_program_options.a(value_semantic.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_15program_options16validation_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_15program_options16validation_errorEED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_program_options.a(value_semantic.o)
`.text._ZN5boost16exception_detail19error_info_injectorISt13runtime_errorED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorISt13runtime_errorED1Ev[_ZN5boost16exception_detail19error_info_injectorISt13runtime_errorED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_regex.a(instances.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorISt13runtime_errorED2Ev[_ZN5boost16exception_detail19error_info_injectorISt13runtime_errorED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_regex.a(instances.o)
`.text._ZN5boost16exception_detail19error_info_injectorISt11logic_errorED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorISt11logic_errorED1Ev[_ZN5boost16exception_detail19error_info_injectorISt11logic_errorED1Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_regex.a(instances.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorISt11logic_errorED2Ev[_ZN5boost16exception_detail19error_info_injectorISt11logic_errorED5Ev]' of /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_regex.a(instances.o)
collect2: error: ld returned 1 exit status
Can anyone help? |
|
|
|
10% Mining Bonus at Extremehash.com
www.extremehash.com is consistently finding blocks, and welcomes you to cash in on the bonus! Consistent blocks | Larger payments | Solution to Dust problems
Profit now!minerd -a cryptonight -o stratum+tcp://mro.extremehash.com:7777 -u address -p x What is this "solution"? I still receive dust from you. |
|
|
|
|
Guys.
Guys, moneropool.com is hashing at 56% of the network.
Stop mining at moneropool.com!
At the moment it would be just as secure (and better for the environment) if we forgot about all that proof-of-work thing and let the pool owner just sign the damn blocks directly...
|
|
|
|
 Can anyone explain this odd discrepancy (my first three hashes submitted to monero.chickenkiller.com:8080)? One screenshot shows the sharediff - the other your total amount of hashes. They have nothing todo with each other. Hmm, OK. How is the number on the web page calculated, then? That's the one that counts when it comes to payout, right? |
|
|
|
Hello everybody, This is my first post here in bitcointalk (but i have been following it for some times now ..). As I really love monero, i decided to start my involvement in it by setting up a pool. Fees are 0% ! The pool is hosted on an 8-core dedicated VPS, hosted in France and is available to this address : http://monero.chickenkiller.comThanks to everybody for helping me launching the pool  See ya ! Edit : template and adding pool location Can anyone explain this odd discrepancy (my first three hashes submitted to monero.chickenkiller.com:8080)? |
|
|
|
|
Is there an easy way to export the private keys in a human-readable format?
|
|
|
|
I looked at mining algorithm and I see that pow is calculated over WHOLE block (sha3). Not block header like in bitcoin, but whole block with transactions. Is that true or am I mistaken?
If that's true this means that ignoring transactions gives a small speed boost in mining. That's not very good for the future...
I skimmed the code, and you may be right. src/cryptonote_core/miner.cpp:
...
b.nonce = nonce;
crypto::hash h;
get_block_longhash(b, h, height);
if(check_hash(h, local_diff))
{
//we lucky!
...
Could a developer comment on that? Will larger blocks hash slower? If so, what incentives do miners have to include more than the coinbase transaction in their blocks (transaction fees seem negligible at the moment imo)? The slow hash is not computed on the entire block, directly. There is an intermediate fast hash, just as with other coins. But just as with other coins it is indeed the case that larger blocks are slower. After all you still have to validate the transactions and compute the block hash. That's why there need to be some transaction fees to get miners to include transactions into a block, otherwise they won't. There can also bit a bit of social pressure to do the right thing. For example, with bitcoin there is no real incentive to include the fee-free high-priority transactions, but most of the big pools do it anyway. With this coin there is not currently a transaction priority mechanism so fee-free transactions are not workable, even if they are workable for bitcoin (which is questionable longer term). EDIT: BTW transaction fees were raised in the last update and may be raised again. They need to be economically significant. Looking into the get_block_longhash function I see that you are right. I did not know about that quick tree hash/slow pow hash thing. Thank you for your quick answer. |
|
|
|
I looked at mining algorithm and I see that pow is calculated over WHOLE block (sha3). Not block header like in bitcoin, but whole block with transactions. Is that true or am I mistaken?
If that's true this means that ignoring transactions gives a small speed boost in mining. That's not very good for the future...
I skimmed the code, and you may be right. src/cryptonote_core/miner.cpp:
...
b.nonce = nonce;
crypto::hash h;
get_block_longhash(b, h, height);
if(check_hash(h, local_diff))
{
//we lucky!
...
Could a developer comment on that? Will larger blocks hash slower? If so, what incentives do miners have to include more than the coinbase transaction in their blocks (transaction fees seem negligible at the moment imo)? |
|
|
|
 ... oder ist das ein Bug auf bitcoincharts? |
|
|
|
There is a lottery? Yes please! 12YxVvX9jUWFMzrBUSj6K1RP3Ubz88yvfN ... also, please come to the Strike Sapphire site that is mentioned in the first post, there are not enough people (at least 4) to start the hourly freerolls  |
|
|
|
|
Offenbar dürfen neue Benutzer hier keine PMs schicken.
Hast du schon jemanden gefunden?
|
|
|
|
|
