Proof of Concept
Settling back into his creaky chair, the MetaMagician (@jadbox) gazed at your party with a puzzled look. "You guys are a bit ... young to be trekking across the Glacier. Are you really that keen on seeking the Nomic DAO? Yes, I know of its power, the ability to scale to thousands which would supercede any existing guide but it's not for the faint of heart. You really have to go back and find the original DAO and tell me why you think you can do better. Anyway, I have a bit of a soft touch for those who dare to win. Talk with the monk camping out on the ice floes but beware, it can't hold more than two people". With that he hands you a rather tacky old rope which, if you close your eyes and pray, could serve as a swing bridge.
The constraints/boundaries of this instance are:
- start off at cottage with party of 3 (others can leave/watch);
- cannot move back to shore without abandoning instance (separately or together?);
- but people standing on west mountain can see 2 hexes out including the monk's cave;
- ice near shore holds max of 3 people, the thin ice 2, and monk's cave where fire is only 1;
- if you let go of the rope (ie non-continuous) you can fall into water and suffer hypothermia damage;
- rope only extends 2 hexes from cottage (pinion) and can't go up mountain or hill to topleft;
Because this is a learn-by-doing exercise, we have to challenge the players to program the rope correctly to share and allow no more than two people to stand on ice, with all characters to be contiguous. We can increase difficulty for the players by (of course) inviting a few guests to join the campfire tea party and if they are "cheating" by communicating with voice, add a few random lurches due to ice cracking underfoot. So you can see in the above scene, players should "see" the TentacLAWS" but not the shipwreck further away. ie outside game foresight (aka cheating) should not affect game dynamics if at all possible. Here the smart contract is like enforcing the rules of chess ... I leave implementation as exercise for the reader.
The original specs postulated a zombie apocalyse scenario. Apart from the physics of frozen corpsicles, we can add a few uninvited guests to the party
-
The only sure thing in life is death and taxes, this boss combines both (eats your wallet to regenerate) -
Fortunately too large to get close to shore but suspected of disabling the first DAO -
you are more likely to see the local descendant but doesn't like exerting itself in the cold -
Nicknamed feature bloat, this fweepng creaturism easily disguises itself, appearing innocuous to eyes of non-experts
- PapaBear, MommaBear, BearCub
- Aligator - legal attack
- Giant Rat - anything to do with concurrency
- Ouroboros offspring - token engineering falures
- Real-time Attacks = Poor exception handling, deadlock, race conditions
- Spider = privacy breaches
- Locust
- Ant
- Snake = token design, miscalibration, behavioural economics, emergent properties
-
Whilst not your common brain-sucking undead, the poison is a definite party unfriend -
Fortunately short on brains themselves, they are too slow to move in the cold -
You will never think of Rover in the same light again
The ex-govt is here to "help" ... mostly themselves
-
Light infantry -
Heavy Infantry -
Officer, medic
The basic concept is that a group can make collective decisions better than an individual expert when:
- independent individuals
- diversity of opinions (even if eccentric)
- draw upon decentralised local knowledge
- mechanism to aggregate into collective action
- trust that the outcome will be fair.
Now lets consider how a swarm of insects would attack the intrepid group above. (TBC)