|
dreamspark
|
 |
May 06, 2014, 02:18:05 PM |
|
is it supposed to be hypen (-) or underscore (_)
start-mining or start_mining
thanks.
Underscore. |
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
equipoise
|
|
May 06, 2014, 02:18:51 PM |
|
2^ in the command line it's: bitmonerod --start-mining... and in bitmonerod console it's start_mining... - two different things
|
|
|
|
emontmon
Member
 Offline
Activity: 196
Merit: 10
|
|
May 06, 2014, 02:53:43 PM |
|
underscore does not start the miner. however the hyphen does start it.
in the responses above, people are using hyphen not underscore.
this is more complex than i realized.
|
|
|
|
|
|
Hexah
|
|
May 06, 2014, 03:00:06 PM |
|
We need optimized miner.
Like Monero have.
NopeDope please release it, don't hold it for closed group.
Hello! Can you elaborate on this? Is there a source code for it we can look up to? It should be here https://github.com/monero-project/bitmonero it is much better optimised for windows. Also BCN diff today reached all time high 4.27m  Compiled it. No changes in hashrate detected. Ubuntu 13.10 Hey, NoodleDoodle optimized the slow hash code recently to about 225% performance. However, he has decided not to release the source code and has only released binaries. I think he is enjoying mining MRO with very high hash rates from Linux right now. Eventually we hope he will release the code. Our git repo has the same code as BCN 0.8.6, so will be the same speed. I remember times when people refused to mine BCN on MinerGate just because it was closed source. And now you have closed source binaries and are happy with it. Hypocrisy much? Where did all this “open source” fighters go? |
|
|
|
|
Redwinego
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 06, 2014, 03:00:46 PM |
|
Hypocrisy much? Where did all this “open source” fighters go?
|
|
|
|
|
|
pozmu
|
|
May 06, 2014, 03:02:18 PM |
|
WTF with all newbie accounts?
|
|
|
|
surfer43
Sr. Member
Offline
Activity: 560
Merit: 250
"Trading Platform of The Future!"
|
|
May 06, 2014, 03:04:47 PM |
|
We need optimized miner.
Like Monero have.
NopeDope please release it, don't hold it for closed group.
Hello! Can you elaborate on this? Is there a source code for it we can look up to? It should be here https://github.com/monero-project/bitmonero it is much better optimised for windows. Also BCN diff today reached all time high 4.27m Compiled it. No changes in hashrate detected. Ubuntu 13.10 Hey, NoodleDoodle optimized the slow hash code recently to about 225% performance. However, he has decided not to release the source code and has only released binaries. I think he is enjoying mining MRO with very high hash rates from Linux right now. Eventually we hope he will release the code. Our git repo has the same code as BCN 0.8.6, so will be the same speed. I remember times when people refused to mine BCN on MinerGate just because it was closed source. And now you have closed source binaries and are happy with it. Hypocrisy much? Where did all this “open source” fighters go?  NoodleDoodle is also mining BCN with his optimized miners, so BCN has this issue too. Others probably have optimized miners as well... |
|
|
|
|
|
Hexah
|
|
May 06, 2014, 03:14:25 PM |
|
We need optimized miner.
Like Monero have.
NopeDope please release it, don't hold it for closed group.
Hello! Can you elaborate on this? Is there a source code for it we can look up to? It should be here https://github.com/monero-project/bitmonero it is much better optimised for windows. Also BCN diff today reached all time high 4.27m Compiled it. No changes in hashrate detected. Ubuntu 13.10 Hey, NoodleDoodle optimized the slow hash code recently to about 225% performance. However, he has decided not to release the source code and has only released binaries. I think he is enjoying mining MRO with very high hash rates from Linux right now. Eventually we hope he will release the code. Our git repo has the same code as BCN 0.8.6, so will be the same speed. I remember times when people refused to mine BCN on MinerGate just because it was closed source. And now you have closed source binaries and are happy with it. Hypocrisy much? Where did all this “open source” fighters go? NoodleDoodle is also mining BCN with his optimized miners, so BCN has this issue too. Others probably have optimized miners as well... Define "others" please.
At least I'm not mining BCN with optimised miner and I don't have a knowledge for creating one. What should I do? |
|
|
|
|
GreekBitcoin
Legendary
Offline
Activity: 1428
Merit: 1001
getmonero.org
|
|
May 06, 2014, 03:15:59 PM |
|
We need optimized miner.
Like Monero have.
NopeDope please release it, don't hold it for closed group.
Hello! Can you elaborate on this? Is there a source code for it we can look up to? It should be here https://github.com/monero-project/bitmonero it is much better optimised for windows. Also BCN diff today reached all time high 4.27m Compiled it. No changes in hashrate detected. Ubuntu 13.10 Hey, NoodleDoodle optimized the slow hash code recently to about 225% performance. However, he has decided not to release the source code and has only released binaries. I think he is enjoying mining MRO with very high hash rates from Linux right now. Eventually we hope he will release the code. Our git repo has the same code as BCN 0.8.6, so will be the same speed. I remember times when people refused to mine BCN on MinerGate just because it was closed source. And now you have closed source binaries and are happy with it. Hypocrisy much? Where did all this “open source” fighters go? NoodleDoodle is also mining BCN with his optimized miners, so BCN has this issue too. Others probably have optimized miners as well... Define "others" please.
At least I'm not mining BCN with optimised miner and I don't have a knowledge for creating one. What should I do? Learn to code? Like i should do i guess... |
|
|
|
|
Bitcoin Fiction
Member
Offline
Activity: 138
Merit: 10
|
|
May 06, 2014, 03:39:13 PM |
|
Blame BCN developers - instamine yourself. Nice catchphrase you got here
And here i thought people went to MRO to have a “clean” start but nope! instamining it with a fast linux hash... Cool! |
|
|
|
tacotime
Legendary
Offline
Activity: 1484
Merit: 1005
|
|
May 06, 2014, 03:43:51 PM |
|
Blame BCN developers - instamine yourself. Nice catchphrase you got here
And here i thought people went to MRO to have a “clean” start but nope! instamining it with a fast linux hash... Cool! You're welcome to optimize your own miner if you're so interested; you have the source code. Artforz GPU mined Bitcoin for a long time on his private OCL code on 4870s and got thousands of them. Bitcoin survives to this day, or so I'm told. |
XMR: 44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns |
|
|
blaaaaacksuit
Sr. Member
Offline
Activity: 280
Merit: 250
Who cares?
|
|
May 06, 2014, 03:47:31 PM |
|
Ugh.
>> Instamine/Ninja launch
Translation: I didn't see this coin floating around in the ann page for days because I was not looking/paying attention or glanced at the page and my first impression was that the coin was stupid/I cant use my graphics card to mine this. The butthurt is more than I can bear.
|
|
|
|
|
Bitcoin Fiction
Member
Offline
Activity: 138
Merit: 10
|
|
May 06, 2014, 03:52:04 PM |
|
Blame BCN developers - instamine yourself. Nice catchphrase you got here
And here i thought people went to MRO to have a “clean” start but nope! instamining it with a fast linux hash... Cool! You're welcome to optimize your own miner if you're so interested; you have the source code. Artforz GPU mined Bitcoin for a long time on his private OCL code on 4870s and got thousands of them. Bitcoin survives to this day, or so I'm told. You're the developers after all. It's a good approach for a developer: we're instamining - you can too, if you're good enough! Promising coin - no shit. |
|
|
|
tacotime
Legendary
Offline
Activity: 1484
Merit: 1005
|
|
May 06, 2014, 03:53:48 PM |
|
You're the developers after all. It's a good approach for a developer: we're instamining - you can too, if you're good enough! Promising coin - no shit. I buy my coins, and so am not terribly interested in who/what is mining them. I mined a bunch of blocks initially but not any longer. If someone spends hours of their free time coding an optimized miner to reap some reward, then I applaud them. |
XMR: 44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns |
|
|
emontmon
Member
Offline
Activity: 196
Merit: 10
|
|
May 06, 2014, 04:12:08 PM |
|
I agree with this. I have 4 pentiums and old dell server. my aggregate has is around 10.
I wish I had an i7 haswell. but that is life not fair.
I wish I had million dollars and spend money on a new machine but I have more important things to put my money in.
I wish I had become a programmer...
I was a bit unhappy the way the coin was launched, but that is partly due to my ignorance. I see that now.
However, I have recieved help from everybody.
help without which i would not be mining now. however, if noodle does not share his source, then that is ok. But I also think he should not be part of the developers as this would mar the image of the coin.
as we can see, there is some kick back already. the developers should share, not that they have to, but should since they also depend on the community to adopt and carry this forward.
noodle can do as he pleases but should do so not as a member of the development team.
that would be more like insider trading. if he knows in advance the direction the coin will take.
just my thoughts on the matter.
|
|
|
|
|
|
equipoise
|
|
May 06, 2014, 04:20:18 PM |
|
What does this error mean:
2014-May-06 19:14:05.094144 [P2P7]ERROR c:\temp\bytecoin\bitmonero-master-current\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-May-06 19:14:05.102144 [P2P7]ERROR c:\temp\bytecoin\bitmonero-master-current\contrib\epee\include\net\levin_protocol_handler_async.h:638 [115.217.180.35:18080 OUT]Failed to do_send()
"Failed to do_send()"? I'm not trying to send anything.
|
|
|
|
tacotime
Legendary
Offline
Activity: 1484
Merit: 1005
|
|
May 06, 2014, 04:23:55 PM |
|
What does this error mean:
2014-May-06 19:14:05.094144 [P2P7]ERROR c:\temp\bytecoin\bitmonero-master-current\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-May-06 19:14:05.102144 [P2P7]ERROR c:\temp\bytecoin\bitmonero-master-current\contrib\epee\include\net\levin_protocol_handler_async.h:638 [115.217.180.35:18080 OUT]Failed to do_send()
"Failed to do_send()"? I'm not trying to send anything.
It's a known bug that needs to be fixed, the server send queue doesn't purge after a certain amount of time and tries to make a billion outbound connections. I'm hoping to fix it soon, but in the meantime just restart the daemon to fix it. |
XMR: 44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns |
|
|
blaaaaacksuit
Sr. Member
Offline
Activity: 280
Merit: 250
Who cares?
|
|
May 06, 2014, 05:26:10 PM |
|
Hey tacotime, do you have any sort of ETA on the pool? Days? Weeks?
|
|
|
|
|
|
trogdorjw73
|
|
May 06, 2014, 05:43:18 PM |
|
Okay, so I *think* I'm mining on all of my reasonably fast rigs, with around 115 H/s of total hash rate. However, after nearly twelve hours I apparently haven't found a single block. That's either really bad luck based on my calculations, or else my systems aren't actually mining. Here are the logs from a few systems -- if anything looks off, can someone help me out? 2014-May-06 10:10:59.325350 bitmonero v0.8.5.294(0.1-g0f42b2e)
2014-May-06 10:10:59.328353 Module folder: bitmonerod.exe
2014-May-06 10:10:59.330354 Initializing p2p server...
2014-May-06 10:10:59.332355 Binding on 0.0.0.0:18080
2014-May-06 10:10:59.334356 Net service binded on 0.0.0.0:18080
2014-May-06 10:10:59.335357 Attempting to add IGD port mapping.
2014-May-06 10:11:00.774387 ERROR c:\temp\bytecoin\bitmonero-master-current\src\p2p\net_node.inl:246 UPNP_AddPortMapping failed.
2014-May-06 10:11:00.779380 P2p server initialized OK
2014-May-06 10:11:00.780378 Initializing cryptonote protocol...
2014-May-06 10:11:00.782379 Cryptonote protocol initialized OK
2014-May-06 10:11:00.784381 Initializing core rpc server...
2014-May-06 10:11:00.786384 Binding on 127.0.0.1:18081
2014-May-06 10:11:00.789384 Core rpc server initialized OK on port: 18081
2014-May-06 10:11:00.791386 Initializing core...
2014-May-06 10:11:00.794388 Loading blockchain...
2014-May-06 10:11:01.631980 Blockchain initialized. last block: 27684, d0.h0.m1.s13 time ago, current difficulty: 3251837
2014-May-06 10:11:01.635983 Core initialized OK
2014-May-06 10:11:01.636985 Starting core rpc server...
2014-May-06 10:11:01.638985 Run net_service loop( 2 threads)...
2014-May-06 10:11:01.651994 [SRV_MAIN]Core rpc server started ok
2014-May-06 10:11:01.654997 [SRV_MAIN]Starting p2p net loop...
2014-May-06 10:11:01.656998 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-May-06 10:11:02.657757 [P2P1]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.
You can set the level of process detailization by using command "set_log <level>", where <level> is either 0 (no details), 1 (current block height synchronized), or 2 (all details).
Use "help" command to see the list of available commands.
Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-May-06 10:11:02.657757 [P2P9]Connecting to 118.68.193.206:18080(white=1, last_seen: d0.h0.m0.s32)...
2014-May-06 10:11:03.929605 [P2P0]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.
Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.
Use "help" command to see the list of available commands.
**********************************************************************
2014-May-06 10:11:03.944615 [P2P0][118.68.193.206:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:03.947616 [P2P9]Connecting to 82.32.195.63:18080(white=1, last_seen: d0.h0.m50.s40)...
2014-May-06 10:11:05.041391 [P2P6][82.32.195.63:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:05.043393 [P2P9]Connecting to 88.164.51.65:18080(white=1, last_seen: d0.h0.m0.s35)...
2014-May-06 10:11:06.329301 [P2P4][88.164.51.65:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:06.331301 [P2P9]Connecting to 198.50.239.117:18080(white=1, last_seen: d0.h0.m0.s37)...
2014-May-06 10:11:06.616512 [P2P6][198.50.239.117:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:06.619505 [P2P9]Connecting to 83.212.102.116:18080(white=1, last_seen: d0.h0.m0.s36)...
2014-May-06 10:11:07.442086 [P2P2][83.212.102.116:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:07.446090 [P2P9]Connecting to 46.249.52.137:18080(white=1, last_seen: d0.h0.m0.s37)...
2014-May-06 10:11:07.962475 [P2P2][46.249.52.137:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:07.966456 [P2P9]Connecting to 54.187.171.247:18080(white=1, last_seen: d0.h0.m0.s38)...
2014-May-06 10:11:08.089545 [P2P3][54.187.171.247:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:08.092547 [P2P9]Connecting to 113.243.176.28:18080(white=1, last_seen: d0.h0.m50.s57)...
2014-May-06 10:11:09.610621 [P2P3][113.243.176.28:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:09.612622 [P2P9]Connecting to 54.187.30.197:18080(white=0, last_seen: d0.h0.m0.s2)...
2014-May-06 10:11:09.691679 [P2P6][54.187.30.197:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:09.694680 [P2P9]Connecting to 37.229.184.145:18080(white=0, last_seen: d0.h0.m11.s22)...
2014-May-06 10:11:11.906242 [P2P1][37.229.184.145:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:11.909244 [P2P9]Connecting to 88.218.187.68:18080(white=0, last_seen: d0.h0.m0.s1)...
2014-May-06 10:11:16.175259 [P2P6][88.218.187.68:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:16.179263 [P2P9]Connecting to 94.189.155.154:18080(white=0, last_seen: d0.h0.m0.s8)...
2014-May-06 10:11:16.876770 [P2P2][94.189.155.154:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 10:11:35.184694 [RPC1]Mining has started with 4 threads, good luck!
2014-May-06 10:11:35.184694 Miner thread was started [1]
2014-May-06 10:11:35.184694 Miner thread was started [0]
2014-May-06 10:11:35.184694 Miner thread was started [3]
2014-May-06 10:11:35.184694 Miner thread was started [2]
FYI, I cleared the log right before this system was restarted. My question is the line that says: "ERROR c:\temp\bytecoin\bitmonero-master-current\src\p2p\net_node.inl:246 UPNP_AddPortMapping failed." I'm getting that on several systems, mostly Windows 8 systems I think? When I'm mining and enable show_hr, I see all of the systems hashing, but again zero blocks in half a day seems unlikely. By my math, there is a total of ~55000 H/s going on with MRO right now, which means I account for ~0.18% of the total hash rate and should thus find 2.62 blocks per day. *BREAKING NEWS* 2014-May-06 06:28:09.237734 [miner 4]Found block for difficulty: 3188836
2014-May-06 06:36:20.507771 [P2P4]Connecting to 128.71.195.108:18080(white=0, last_seen: d0.h0.m57.s5)...
2014-May-06 06:36:23.601549 [P2P0][128.71.195.108:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-06 07:16:20.417776 [miner 2]Found block for difficulty: 3155187 Apparently I found some blocks a few hours ago. But they didn't show up in my wallet at first? How many confirms does it take for found blocks to appear in your wallet, or was it because I happened to type "refresh" in my wallet a few minutes ago while trying to figure out what was going on? I guess all is well and I'm now back on track, though it's funny that only one system found any blocks and it was two blocks within 40 minutes. Anyway, I'm just looking for good information on how to mine MRO most effectively, and I may end up being the one to provide that (for Windows users at least). If I can get enough of a clear insight into how everything works, I'll see about writing a blog post on the subject. :-) |
|
|
|
|
AnonyMint
|
|
May 06, 2014, 05:48:40 PM
Last edit: May 06, 2014, 06:05:21 PM by AnonyMint |
|
Which file in the source code contains the proof-of-work algorithm?
I've tried to locate it and can't seem to find it quickly.
I want to analyze the cpu-only claim.
src/crypto/slow-hash.c On quick glance, I see AES code. Is this the MemoryCoin algorithm and not the one described in the CryptoNote whitepaper which is memory latency bound? I do not think it is the memorycoin algorithm. Analyzed it. It is employing AES as another means of defeating GPUs (in addition to the memory latency bound), similar to MemoryCoin. https://cryptonote.org/inside.php#equal-proof-of-work3. GPUs may run hundreds of concurrent instances, but they are limited in other ways See prior analysis of that strategy, which concluded that GPUs would be 2.5 to 3X faster but would perform no better in hashes per Watt: https://bitcointalk.org/index.php?topic=355532.msg3976656#msg3976656I pointed out that ASICs would implement AES much more efficiently: https://bitcointalk.org/index.php?topic=355532.msg3977088#msg3977088Here follows my conclusions. - slow and thus DDoS prevention will be hampered, which will also likely eliminate any chance of supporting 0 transaction fees
- roughly both memory latency and computation bound (instead of the ideal of being only latency bound), thus if Tilera CPUs or GPUs add dedicated AES support or if ASICs are mated to large fast SDRAM caches, the cpu-only claim will fail.
- it is not leveraging hyperthreads
In short, it is too computation heavy, not maximizing the CPU's hyperthreads, and thus not only will it not be the best cpu-only PoW algorithm possible, it will also fail to be remain cpu-only if it becomes widely adopted. Also being computation heavy, it is consuming more electricity than the ideal cpu-only PoW algorithm. There is another egregious flaw in the proof-of-work algorithm. AES encryption is being employed as the hash function and assumed to be a random oracle with perfect distribution in order to provide the randomized memory access. Problem is that AES is not suitable as a hash (certainly not when employed as encryption) for it has too small of a output space (repeating patterns will be over a few number of bits), thus it will be possible to attack this with an algorithm to reduce the scratchpad size significantly from the 2MB. |
|
|
|
|
