Search content
Sort by
Showing 20 of 20 results by minim1ner
This version doesn't seem to sync very well.
It skips between being synced and syncing with the network.
It skips between being synced and syncing with the network.
It's Ok, that's means it is ready.
I still don't know what to do. Do you know how I can fix those errors?
No, I don't. It seems that project should be recompiled with newer lib versionBtw, which linux do you have?
Ubuntu 14.04 with default setup.
I will update this as I go along.
Progress:
Delete partition and create new one: Yes
Download Ubuntu 14.04 : No - Started
Burn Ubuntu to disk : No
Start Installing Ubuntu : No
Finish Install : No
Progress Bar:
[llllll ]
I still don't know what to do. Do you know how I can fix those errors?
No, I don't. It seems that project should be recompiled with newer lib versionBtw, which linux do you have?
Ubuntu 14.04 with default setup.
I still don't know what to do. Do you know how I can fix those errors?
No, I don't. It seems that project should be recompiled with newer lib versionCan you please release this compiled version?
No problem https://github.com/minim1ner/motocoin-bot/releases/tag/1
Nope, just uploaded. You're not
How do I actually run the motocoin-qt? Now I really feel dumb.
I used the terminal but...
Code:
./motocoin-qt: error while loading shared libraries: libminiupnpc.so.8: cannot open shared object file: No such file or directory
Edit 1: I guess it is like this problem: https://bitcointalk.org/index.php?topic=192984.0Edit 2: I just ran the normal motocoin-qt and got
Code:
kyle@Kyle-Desktop-Debian:~/Downloads/motocoin/bin/64$ ./motocoin-qt
./motocoin-qt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./motocoin-qt)
./motocoin-qt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./motocoin-qt)
Edit 3: Doing instructions here: http://askubuntu.com/questions/315907/libc-so-6-version-glibc-2-16-not-found (2nd comment)./motocoin-qt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./motocoin-qt)
./motocoin-qt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./motocoin-qt)
That's why I don't like linux* and c* staff.
Can you please release this compiled version?
No problem https://github.com/minim1ner/motocoin-bot/releases/tag/1
Nope, just uploaded. You're not
Can you please release this compiled version?
No problem https://github.com/minim1ner/motocoin-bot/releases/tag/1
Now I get this error when compiling:
Code:
moto-engine.cpp:17:19: fatal error: debug.h: No such file or directory
compilation terminated.
make: *** [obj/moto-engine.o] Error 1
compilation terminated.
make: *** [obj/moto-engine.o] Error 1
It is really strange, since debug.h is in game folder. I have two qt projects: one for game and one for client. The one for game is in ./src/game folder. Hope this will help.
Interestingly it seems that, for the moment at least, everyone who is checking out your bot is now all synced up! The spammy getblocks have subsided, with the exception of a couple of nodes that keep doing getblocks from block -1, which I'm guessing is an effect of some sync bug in the reference code, or something.
I am just pushed small update, now it is less network intensive. It is still not perfect, but I think that little aggressive behavior is ok for miner, since it is not basic network node.
My patch to fix the time warp will already do this as a side effect. (Remember from our pm?)
Yes, it just was quiet for a while, I thought development is stuck, or William rejected pull request or something.Quote
On what spec cpu? That is a pretty good production rate if it is just one core!
No, I use all 4 cores @1.6 ghz.Quote
I'm not sure how those parameters would affect anything...
It will spam just to 3 connections, not to 10 or whatever.Quote
It would be interesting to release just it as a patch to the reference client, for human miners.
I'd better make a patch that prevents map brutforce, if devs agree with this idea, I could do it. With this patch map generation will take little more time, but it will be the first step to destroy bots.Quote
unfuck yourself linuxoid
Quote
Minim1ner can you adjust your patch so that it does not also do the getblocks spam during sync? From looking at logs it looks like this might be what is creating the excess chatter on the network.
I'll take a look at it later. For now run it with Code:
-maxconnections=3 -timeout=500
parameters.Quote
EDIT: On Linux it crashes while on Windows it seems to work, although it still didn't mine me any single block.
I am getting ~10 blocks per hour with this bot. Can't tell anything about crashes, it seems pretty strange.Quote
BTW how do you compile it for Linux?
I used qtcreator, thus qmake. Mostly I followed guide here https://github.com/motocoin-dev/motocoin/blob/master/doc/build-unix.md, but because of newest ubuntu version, I've got couple of problems. Maybe original one is better, since it is up to date. Quote
Yes please!! We all need this.
Devs with their "hot setup" for cross compile could do this in 5 minutes.Quote
Nice, but a little scary.
Yep, I noticed that project itself is little bit scary Quote
I still think we should not have had off-the-shelf bots readily available until after time warp is fixed.
well, now you have reason to fix it fasterQuote
I worry this may create much risk for the chain.
not that muchQuote
What "chain branching" issue are you referring to?
Well, all thous stales you complained about. I patched client so that requests current chain state from nodes every 10sec. But it is more like a temporary patch. I think there is couple of minor issues, which prevent normal message relaying&sync. Quote
Your map filter is not exactly what I expected to see, but it is short and sweet. I like it. My map selection slows down map generation quite a bit, relatively speaking. I might hybridize the two and see what happens.
It takes ~0.5sec in my solution.
Quote
Likely this sort of architecture and approach both will not last much longer, for various reasons.
Yes, it is more like quick and simple solution.I am curious about your approach. Hope to see it in future
Can you compile for win 32, please?
Ouch, it will take longer then I coded it, because of poor dependency management. I only have linux x64 for now
Maybe somebody interested, I uploaded my bot on github. https://github.com/minim1ner/motocoin-bot
Sorry for dirty-code
Dirty-fix for chain branching issue included.
It is what you name it "undeniable" one, but there is nothing special except using rand() in nonce selection.
It's seems that this bot will end it's life cycle pretty soon, but this is like first version I made and it could be easily improved to compete with current generation of bots.
Sorry for dirty-code
Dirty-fix for chain branching issue included.It is what you name it "undeniable" one, but there is nothing special except using rand() in nonce selection.
It's seems that this bot will end it's life cycle pretty soon, but this is like first version I made and it could be easily improved to compete with current generation of bots.
Quote
What do you mean?
I mean that there is not really big crowd of people with bots for now.Quote
Why on earth would you sell discounted coins to the devs to replace the coins they sold themselves??? It is not like they didn't get btc for their coins...
Coin needs support form devs, and if they made a mistake selling all coins in panic, comunity may restore part of this loss. Or maybe we could promote another bounties for coin improvement, as we definately need it.Quote
There are lots of reasons to send money to yourself. Not the least of which, in this context, would be to simply cast doubt as to whether or not you still held it. We know that the origination address was owned by the dev, but we can't say yet for certain who owns the MoLn address. (Perhaps c-cex could state if it is/isn't one of theirs?)
If it were a c-cex address I'd expect to see the coins move again at least once, to be consolidated into their backend wallets and/or portioned between hot/cold wallets. It is unusual for coins sent to an exchange to sit indefinitely at their deposit address.
If it were a c-cex address I'd expect to see the coins move again at least once, to be consolidated into their backend wallets and/or portioned between hot/cold wallets. It is unusual for coins sent to an exchange to sit indefinitely at their deposit address.
Any way I think that making this coin bot resistant is pretty difficult task and it deserves bounty whether from devs, and in case if devs have no more coins, then from community.
Quote
If devs sold all of their coins how can you explain this http://moto-explorer.fvds.ru/address.php?address=MoLnCJGJXBGLkPjFfJ9sRXVv7nEvwwEuZck. There is one transaction from address, which received 150k in #0 block http://moto-explorer.fvds.ru/transaction.php?transaction=a05b6e6a99468edf9f4b3833b63857e686e2d55de3239cd3e05a783a2defacb8. Only one transaction for this address, and it is 150k. It seems transaction to yourself. There is something unclear here...
There is no reason to send money to yourself, more likely it is c-cex addressQuote
But something should be done. While we a talking bot owners are mining. I am not very satisfied with the fact that we discussing the ways how to save the coin while bots are mining. It appears that we are now working to protect their wealth. This is not a normal situation.
I am mining almost alone now. There is not really much of coins I've got, just 70k. If you solve this bot issue, I will sell most coins I've mined to devs for price that they dumped, and hope other guys will support me.