[ANN][MOTO] Motocoin

[Vz]

the  196000 was at Sep 3, 2014 8:32:20 PM
and 197847 was at Sep 5, 2014 3:46:01 AM

~~2580~~ min passed no matter MORE then 2000.. Sooo the TT will be larger


Last 150 block was passed for 4 hours.. I'll take a rest for some sleep)

[HunterMinerCrafter]

I'm all over this. Mining coins now!

MoXuwxSCMG2a578rvbPzMszM4WY5tKQUrMU

You don't need to post your address.  I will just send to the coin-base addresses after we get a few confirms past the fork point.

[Vz]

WOW! 2k moto!.. I accept that!

It was more difficult than it seems.. I can't got a block(



C-Cex wallet stoped.. did We inform them?

[e1ghtSpace]

Am I too late for the 2k moto? I'm at school and I don't get home for another 1.5 hours.

[Quadmium]

Hi, supporter of motocoin here. Intense mining session guys! Got block 197998 

[jw_industry]

is their a new download link?

[e1ghtSpace]

Oh god. I just got home and started the sync and estimated blocks is 197999. I am just in time!!

Edit:
Wth? The wallet got stuck and then just when I mined the next block myself the rest of the blocks started syncing. And I missed it by 68 blocks.

[Gargo]

when will be another time readjustment? it is almost impossible to do something in ~33 seconds

[e1ghtSpace]

Elasto Mania is indeed closer to lunar gravity than earth's. I remember some guys calculated it to around 1-2m/s². Anyway, the main differences in this game compared to Elasto Mania are, not taking extra features into consideration:

• Accelerating in the air doesn't cause angular momentum.
• The head is dead centered. There is no difference if you turn the head to avoid obstacles.
• The breaks have little to no grip.
• Missing faster spin. (Alovolt)
• Great angular momentum can be cancelled out with one spin in the opposite direction.

If anyone didn't know; http://wiki.elmaonline.net/Alovolt Alovolt

[unamis76]

Yes, I see... turned the game back on and blocks are taking much longer to solve, bot is probably offline now

We are doing a slightly better job of keeping hash-rates up than before, once everyone realizes that the bot is down anyway.

If we can keep hash rate consistently up whenever the bot is "down", the upcoming fork goes cleanly (c-cex and block explorer are both updated and ready to fork, now), and the bot continues to run as it has been today I think we will be nearly "out of the woods" on these hash-rate problems, and can start to approach exchanges and merchants.  (That is a lot of big caveats, so don't start holding your breath just yet, but things are looking more positive!)

Yes, things definitely look positive

[WilliamLie2]

198130 blocks on old non-forked blockchain and this number is increasing. Also I have 7 connections on old wallet.

[unamis76]

198130 blocks on old non-forked blockchain and this number is increasing.

Yes, started playing after i wrote my last post, And I think the bot is online... That's why it's going fast

[WilliamLie2]

Maybe both wallets are still compatible until next difficulty retarget.

[e1ghtSpace]

Maybe both wallets are still compatible until next difficulty retarget.

I'm pretty sure this is true. We'll see soon.
Is the difficulty retarget every 200 blocks?


My 911th post! :0

[unamis76]

Bot is still online, with some breaks between blocks... He just solved one in something like 5 seconds...

Speaking of difficulty... How can you track the difficulty of the game?

[HunterMinerCrafter]

198130 blocks on old non-forked blockchain and this number is increasing. Also I have 7 connections on old wallet.

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?

[HunterMinerCrafter]

Speaking of difficulty... How can you track the difficulty of the game?

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.

[Spiky]

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.

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.

[HunterMinerCrafter]

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.

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.

[Spiky]

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)