[ANN][MOTO] Motocoin

[HunterMinerCrafter]

Sorry) I didn't want to offend you)

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

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

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?

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

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.

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

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.)

[Spiky]

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

[HunterMinerCrafter]

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

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.)

[Gargo]

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

[e1ghtSpace]

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.

[Vz]

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..

[HunterMinerCrafter]

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

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.

[HunterMinerCrafter]

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.

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.)

[e1ghtSpace]

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.

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.)

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.

[HunterMinerCrafter]

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.

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.

[e1ghtSpace]

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.

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.

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

[Vz]

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

[Quadmium]

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

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

[Spiky]

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.

[e1ghtSpace]

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.

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

[unamis76]

Game over... The bot is completely smashing everything right now, he's been doing the last 30 or 40 blocks in less than 10 seconds (most of them in less than 5)

[Vz]

Soo let's fork from 199000 and    distress  the bot owner up to 100 000+ MOTO

[Gargo]

too much bots. Time is decreased again

[Spiky]

Soo let's fork from 199000 and    distress  the bot owner up to 100 000+ MOTO

Don't forget that he can fork too. If you fork him, he will definitely do it in return. We should play nicely.

[Vz]

Soo let's fork from 199000 and    distress  the bot owner up to 100 000+ MOTO

Don't forget that he can fork too. If you fork him, he will definitely do it in return. We should play nicely.

He can't fork.. cause community against "fastbots".. C-Cex chain is delayed until we provide the right builds for community and we may choose the point of fork..