What's the gas token?
What's the gas token?
What wallet should I use?
What wallet should I use?
Where can I see the ecosystem?
Where can I see the ecosystem?
What are my stablecoin options?
What are my stablecoin options?
How do I bridge and what's the best method?
How do I bridge and what's the best method?
Is on-chain IP real?
Is on-chain IP real?
My asset is off-chain. How do I register it as IP on Story?
My asset is off-chain. How do I register it as IP on Story?
I am selling an off-chain asset (eg. merch). How do I make sure that automatic royalty flow is enforced?
I am selling an off-chain asset (eg. merch). How do I make sure that automatic royalty flow is enforced?
What is a simple example?
What is a simple example?
What are the challenges?
What are the challenges?
Why not be a protocol on every existing chain?
Why not be a protocol on every existing chain?
Okay, so you need a singular blockchain. Why not use an existing blockchain?
Okay, so you need a singular blockchain. Why not use an existing blockchain?
- Existing L1s are simply not able to handle the registration of IP upon 1000s of parents - each with their own complicated licensing details - in one transaction efficiently. Gas usage on Geth EVM rapidly increases with ancestor IPs, making it impractical beyond 670 ancestors due to block gas limits. So we improved the efficiency of graph traversing and storing for our IP graph by leveraging a new stateful precompile approach, written directly in the execution client. This creates a “shortcut” around EVM to write and read certain values in the blockchain we use for our graphs, under the restrictions of PoC protocol.
- Similarly, existing L1s are not able to handle the royalty token flow between 1000s of IP Assets. Again, this was solved by making improvements directly in the execution client.
- Max composability by having license data on-chain, allows for 100s of IPs to remix at once.
- Potential rollup support with bespoke X-CHAIN data (e.g. Initia’s model) for Web2 apps with millions of transactions requiring rollups. Also support Web2 apps running their own validators for max incentive alignment.
- Future validator-enshrined L1 tech like native oracles for NFTs and off-chain RWA IPs (Cosmos SDK vote extensions).
Why not just settle for an L2?
Why not just settle for an L2?
Why is Story making improvements at the validator level?
Why is Story making improvements at the validator level?
You mentioned needing an L1 to improve the efficiency of an IP graph. Why not build an L2 with off-chain graph indexing?
You mentioned needing an L1 to improve the efficiency of an IP graph. Why not build an L2 with off-chain graph indexing?
How will Story prevent users from registering off-chain IP that isn't theirs?
How will Story prevent users from registering off-chain IP that isn't theirs?
What are the disclaimers?
What are the disclaimers?