Liminal
People
Description / What is your motivation?
An engine for interactive cryptomedia
Team Story
Subtheme
Manager
Track
PoC (Website / Inpso / Deck)
📣 How can KB2 help? Anything goes.
Guidance, advice, most efficient route(s) of attack
Last updated on
Feb 8, 2021
Primary Track
Project (Yes)
Investable?
Mentor Connection?
My Tag
Stage | Important facts
Build Phase
Stewards Actions?
- Connect them with Angie's letter, and Astral
Related to KB2 Fellows (Related to Copy of KERNEL Adventures (People) 1)
Stewards Thoughts!
Status
Liminal is an engine for storing, engaging with, and creating Interactive Digital-Native Media (IDNM is messy, will come up with something. Maybe cryptomedia if Zora is cool with that). It utilizes cryptographic proofs to enrich storytelling in a way that is composable, trust-minimized, and opt-in.
Users will be able to engage with creators' works and tokenize (crystallize?) their actions, choices, and configurations at a given time. They'll be able to use their Web3 wallets to dynamically change the story content, thus leading to a more engaging story
Creators will be able to engage with audiences in a more interactive pattern, being able to determine more accurately what pathways users want, and build on that. Creators will also be able to tokenize their users' experiences, and eventually (given logistics + meatspace laws) let users (redeem/burn?) and print their own journeys and keep as a keepsake.
The user-facing front-end will be a UI for interacting with interactive media in a distributed fashion, in addition to track and tokenize the player's choices in the form of an NFT. This NFT may have user choices encrypted such that third parties are unable to determine the user's information without the user
The creator-facing backend will be a means to storyboard, plot, track, and version control different chapters of their work. Using a storytelling engine that's EVM-compatible and
Also a dashboard for tracking opted-in user behaviors
NFT Standard:
Options for NFT standard
- Zora
- ERC-721
- Vanilla
- Most "support"
- May be limiting
- ERC-1155
- Can bundle things
- Gives writers ability to make different interactable objects within the story "importable"
Token(?)
- PAGE (represents a page)
Scant Thoughts:
- Great for accessibility (Interactive Fiction is accessbile for sight-impaired)
- Probably a step twoards
Converting Text Adventures to ETH:
- Z-Machine (spec doesn't tell you how parser works, which was built into game)
- Building Adventure Games (Harnell)
- Inform 7 (compiles down to InfoCom )
- 3 components
- parser
- parse user inputs
- data tables
- map inputs to data tables
- subroutines
- if verb=kick and noun=can:
- do thing
- InfoCom parsers were great because it used natural language parsing
- Rooms and Objects
- They're relatively the same
- Both have attributes
- attributes have flags
- id
- holder
- name
- weight
- Have table be fixed size
- Rooms/Objects have binary properties
- Objects/rooms have spactial arrangement
- Objects also have graph tree relations
- LOTS OF TABLES (Flag this; how do I make this table as accomodating as possible?)
- Articles
- prepositions
- dictionary
- verbs
- nounsverbs with same ID number are "synonyms"
- ObjectwordTable" maps words to objects
- This lets the game associate any of the words in the item description with the specific word (???)
- Ex:
- 5023
- 5 → Data for the "Rusty Iron Lamp"
- 0 → "Rusty" from word table
- 2 → "Iron" from word table
- 3 → "Lamp" from word table
- Jump Tables
Open Answers:
Open Questions:
- Does a token need to be here?
- What are the benefits?
- What are the detriments?
- Fair launch minting would either be unfair (info asymmetry) or spam filled
- Regulations
- Bad projects being funded
- Quality control
- Should the "crown" be given to the standard, the tooling, the UI, or something else?
- Data structure
- How do we achieve parity with Web2 IF experiences in Web3?
- Platforms
- How do we ensure that all the people who want to access the book can do so?
- Parser
- Is this on-chain?
- How can we build in multi-language support?
- How do idioms work within the parser?