solidity

Stoke Fire

The new battle mechanics have not quite played out like I was expecting.

The problem being that knowing the total number of villagers defending takes out the strategy of raiding and you can pretty easily win even though you don't know if those villagers are defending wood or food.

The limitation being that the blockchain needs to know where villagers are at and the logic can be onchain so that number has to be public.

Will be reworking this over the coming days. Maybe even revert back to the previous battle system in the mean time.

I have a couple of ideas to pursue but If you have any, feel free to reply with them!

The goal I'm shooting for is having your village economy be connected to what you can do in battles.

The fire must continue on! 🔥

Any solidity devs have ideas for ways to keep some info secret and build logic around it at the same time?

Already using a commit reveal scheme but hit some limitations with committing data based on what state you have and keeping that secret at the same time.

Any solidity devs have ideas for ways to keep some info secret and build logic around it at the same time?

Already using a commit reveal scheme but hit some limitations with committing data based on what state you have and keeping that secret at the same time.

https://warpcast.com/nbragg/0x5c405360

Building /stokefire a mobile strategy game onchain. Run and own poolfish.xyz a calculator for LP providers. Built Potion solo and sold for $300k.

The MUD and 0xPARC fam had some good talks on zk and I guess by extension incomplete information games. They did talks at devcon and dark forest is probably one of the best examples for this kind of incomplete information on a public Blockchain I've seen to date