[ANN][MOTO] Motocoin

[kaja]

This coin will no doubt attract bots if it succeeds but at least it won't ever have ASICs. Question:

Why can't this coin support multiple games? Complex open source games never seem to take off, but having a variety of less ambitious games would be great. My computer is too slow to play this, but maybe I'd like to download an Android app and mine some coins. I'll get bored, though. Needs multiple games! Also, this would mitigate the botnet issue as it would be difficult to orchestrate your zombies to play a variety of different games, and also prevent clandestine bot developers from seizing too much of the nethash. Think of it like the Myriad coin of Proof of Play.

Also, heard of Arimaa? It is a board game designed so that a toddler could learn to play but the best human players always beat the bots. There is a $10,000 prize every year for a bot that can beat the world champions in a tournament, and they never win.

[ripplebtc]

WTB motocoin, PM your offers.

[domob]

I have to say I'm really disappointed that no code is available.  There wasn't any for the demo game, and now there isn't even one after the launch although it was stated that it will be pushed "shortly" after.  I read the reply from dev that it will be available in a few days, but this seems fishy to me - I don't really think that the risk is too high for releasing it right now.  Anyway, I'm off waiting and will take a look again when the code is there.

[eddywise]

I had add some nodes,but still no sync

[atleticofa]

About source code. A lot of effort was put in this coin. I just need a few days to see if everything works correctly (it should, it was tested before release but not on this scale) and if something goes wrong (well, it shouldn't) I want to fix it by myself, I don't want to see someone creating a fork.

Ok,, thank you for your work.

Some screenshots on the first message of the thread would be good.

[WilliamLie2]

Source code: https://github.com/motocoin-dev/motocoin

[telepatheic]

Nice code! Unfortunately, there doesn't appear to be anything securing this coin. A malicious user could simply take an existing block, change the coinbase transaction and republish it to the network. It would have the same proof of work so the network wouldn't know which block is the valid one and which is the copy.

[WilliamLie2]

Nice code! Unfortunately, there doesn't appear to be anything securing this coin. A malicious user could simply take an existing block, change the coinbase transaction and republish it to the network. It would have the same proof of work so the network wouldn't know which block is the valid one and which is the copy.

Level is generated based on information in block, if you change anything in block then you have to complete different level.

[telepatheic]

Level is generated based on information in block.

But does that information include the merkle tree hash? If yes, could you point to the line in the code.

[atleticofa]

Nice code! Unfortunately, there doesn't appear to be anything securing this coin. A malicious user could simply take an existing block, change the coinbase transaction and republish it to the network. It would have the same proof of work so the network wouldn't know which block is the valid one and which is the copy.

Level is generated based on information in block, if you change anything in block then you have to complete different level.

Maybe a whitepaper explaining this kind of things would be good.

[WilliamLie2]

Level is generated based on information in block.

But does that information include the merkle tree hash? If yes, could you point to the line in the code.

In main.cpp look at CBlock::CheckPoW() definition:
line 1492: motoCheck((const uint8_t*)&nVersion, &Nonce)
You see pointer to nVersion. If you look at CBlockHeader definition (main.h, line 1290) then you will see that nVersion is followed by all necessarry block information:

Code:

    int nVersion;
    uint256 hashPrevBlock;
    uint256 hashMerkleRoot;
    unsigned int nTime;
    unsigned int nBits;

Function motoCheck uses not only nVersion but information that follows it to generate level. This is a bit ugly but it was made in similar way in Litecoin. Actual level generation is in moto-engine.cpp:474, function motoGenerateWorld.

Maybe a whitepaper explaining this kind of things would be good.

Yes, good idea.

[telepatheic]

In main.cpp look at CBlock::CheckPoW() definition:
line 1492: motoCheck((const uint8_t*)&nVersion, &Nonce)
You see pointer to nVersion. If you look at CBlockHeader definition (main.h, line 1290) then you will see that nVersion is followed by all necessarry block information:

Code:

    int nVersion;
    uint256 hashPrevBlock;
    uint256 hashMerkleRoot;
    unsigned int nTime;
    unsigned int nBits;

Function motoCheck uses not only nVersion but information that follows it to generate level. This is a bit ugly but it was made in similar way in Litecoin. Actual level generation is in moto-engine.cpp:474, function motoGenerateWorld.

I have read all that. The check depends only on the version and the nonce not the merkle tree hash.You can't pull the wool over my eyes.

[peterpanda]

sounds quite nice, and funny, i will test it

[amiryaqot]

coin with just having fun, sound interesting

[yzhi]

The game will work with Windows XP?

It's working fine with Windows 7, but I can't run with XP

I tested it on WinXP, it works. Issue may be with too old GPU or GPU driver. Updating GPU driver may help.

Game outputs some debug info. To collect it create bat file in game directory with content

Code:

motogame > out.txt

and run it. Then just copy content of out.txt here, this may help.

This is what I get.

Code:

Initializing GLEW...
GLEW version: 1.10.0
GL venndor: Intel
GL renderer: Intel Cantiga
GL version: 2.0.0 - Build 7.15.10.5002
GLSL version: 1.10  - Intel Build 7.15.10.5002
Loading texture ground...

I like so much your project by the way.

It is working fine with Windows 7,and XP too

[MissCrypto]

Damn this game is hard  

[stompix]

Funny coin , reminds me of huntercoin...

No energy is wasted on useless computations.
It is more secure as it is almost impossible to perform 51% attack.

A lot of energy will be used to play , not talking about the stress playing this game .

2. What does it mean "almost" ? As i have no idea how this coin works , and the website didn't provide too much info.

[peterpanda]

I want to know how to control, i just know the left and right key for angle judgement, "s" for enlarge/small, and does anyone know how to turn the direction?

[yanbosmu]

It's a joke! a scam!
LOL
nice joke

[WilliamLie2]

In main.cpp look at CBlock::CheckPoW() definition:
line 1492: motoCheck((const uint8_t*)&nVersion, &Nonce)
You see pointer to nVersion. If you look at CBlockHeader definition (main.h, line 1290) then you will see that nVersion is followed by all necessarry block information:

Code:

    int nVersion;
    uint256 hashPrevBlock;
    uint256 hashMerkleRoot;
    unsigned int nTime;
    unsigned int nBits;

Function motoCheck uses not only nVersion but information that follows it to generate level. This is a bit ugly but it was made in similar way in Litecoin. Actual level generation is in moto-engine.cpp:474, function motoGenerateWorld.

I have read all that. The check depends only on the version and the nonce not the merkle tree hash.You can't pull the wool over my eyes.

Then Litecoin is also insecure as its PoW hash depends only on version:

Code:

    uint256 GetPoWHash() const
    {
        uint256 thash;
        scrypt_1024_1_1_256(BEGIN(nVersion), BEGIN(thash));
        return thash;
    }

But the truth is that if you have pointer to nVersion you can add any value to it and get information that is stored after it.