Topic: [ANN][MOTO] Motocoin - page 31. (Read 178273 times)

Maybe the guy with the bot waits until the anti-warp goes down and then starts again.

I think we just need to wait a few hours (or days). Anti-warp will slow down him again.

Obviosly bot is improved from time to time, I think we may experience this several times in the future.

Yep... Its pretty much impossible to mine again. 

The F* bot again start to be very fast.. 

I meant that he is showing me how to set it up a different way. I knew that btw.

The fun thing about Gitian is that once the vm is set up you can't do things a different way.  It enforces that the actual compile is done exactly the same by everyone if they end up at the same hash.  By comparing your hashes against mine, you can know if my binary matches the actual source code, and make sure there is nothing "hidden" by anyone.  At that point you could trust my build - but you still wouldn't need to because you'd have just made your own identical build.

The only thing I have compiled on ubuntu is the motocoin-qt and game (bot). I will try your tutorial but WilliamLie2 is showing me how to do it a different way.

http://gavintech.blogspot.com/2014/02/gitian-building-bitcoin-releases.html is an excellent tutorial from an excellent source.

One should know how to compile stuff, in general, if using alt-coins, IMO.  You should never trust a binary from some random person on some random forum.  (Yes, I'm saying you should not actually use my builds.  I might try to steal all your coins and format your hard drive and eject your cd tray, or something, you don't know.  I might be evil.  I'm not, I promise, but of course one would say that.)

I think both wallets are actually more or less the same wallet.  I'll double check to be sure, but you should be able to use either just the same.  The windows motogame.exe might be the only thing that actually saw any change.

I'm not sure when I'll have time to put together a new patch.

I think we just need to move fork point to 199 000 and notice C-Cex about it..

Sorry HMC, it is too hard to me to understand all source.. and too hard to set up compilers..

I was going to get gitian in a vm but I don't know what most of the stuff means. If anyone could walk me through the process I’d be happy to follow. Pm me.

Edit: WilliamLie2 is helping me set it up.

ok, a lot of words and an old wallet. What should we do now? wait while until you will have update the wallet?

It is still not very desirable to have the anti-warp use the same adjustment interval as difficulty.  It should be much more frequent to be most effective.

It should actually be shorter than our confirmation/maturation times, otherwise it offers less security than it could/should.  (If it is greater than our confirmation time the protection it offers from warp based attacks actually decreases around the difficulty re-target blocks, and maximizes at the odd 1000 intervals between targets, it seems.)

Maybe it's not necessary to fork now at all cause the situation with block generation speed resolved itself...

You didn't actually offend.  I don't take offense easily.  You amused, honestly.


Cool.  I know of at least one minor "bug" hiding in the path finding, which makes the work curve slightly inaccurate, directly.  I don't consider it a huge deal, since we already know the work curve is a best-guess approximation anyway.  It is not really a significantly exploitable problem, it just makes one coin slightly more likely to be grabbed. (hint hint ;-))

Have you spotted any others?


You're probably not wrong, but again it only would've mattered if both forks ran, and someone transacted on the wrong fork.  This is a risk with any fork, anyway!  I stand by my decision to move to 198000 (despite the setback in the end) but I think we would've been fine at either fork point.  All well, it is all just ancient history now.


It is only a problem because C-Cex and explorer are "stuck."  I've contacted C-Cex to revert, and will revert the explorer at my first available opportunity.  (I'll still send out the 10k prize coins, once c-cex is safely "unstuck."  If we find ourselves crawling toward the next fork point, I may run a similar promotional initiative again to help move things along.)

I'm quite busy for the next 24-48 hours with other obligations, so our next attempt at a fork will not be immediately coordinated unless someone else wants to handle it and commit the changes sooner.  (I should at least be able to find some time to merge a PR and sneak in a Gitian run or two.)

Sorry) I didn't want to offend you)

Actually, I'm checking your code for bugs sometimes.

I still think 196000 was too early (we had only one hour before the fork).

Current situation is not a problem at all. We just need new builds)

It is kind of humorous to me that you would be the one to post this, in particular.  I actually had good, solid, tested, correct builds set for fork at 196000.  Then someone (YOU!) came in at the last minute freaking out about the fork point being way too soon, saying it should be at least block 200000.  I rushed together a new build with the fork point at 198000, but in my haste (and being over ~48 hours without real sleep) I made a simple mistake and rebuilt with the wrong directory linked in Gitian inputs.  If even just one other person was making gitian builds and checking hashes against mine, we would've caught this immediately.  I've asked many times for someone to step up, and no-one has.

If you think I need to be more careful, don't push me for last minute changes.

If you think the project has a lack of responsibility, bring some to it yourself.  Commit to contributing to Gitian build verification, and take first hand responsibility for cross-verifying my builds.

If you think my testing process is insufficient, fire up a test-net in TESTMODE and do some testing.

If you think my builds go too unchecked, CHECK THEM YOURSELF BEFORE THE PROBLEMS ARISE.

It is an open source community project, after all.  I am not your employee, I am just a volunteer.  You can too, ask me how!

Pitch in.

Don't want to complain or offend but I think you need to be more careful and responsible. It looks like you don't even test your code properly and don't check your builds. It's a currency after all, not a homework.

TT is shown at the bottom of motogame when mining.

Anti-warp work requirement can be calculated from the 'bits' field of a block header, the lower the number the more work required.

This is why I never wanted to be the only person making builds...

Now we have a small situation.  C-cex and block explorer are the only nodes actually on the new fork.  In my lack of sleep the builds that I uploaded are not the correct builds, and still run under the old rules.

How do we want to proceed?