This page should help you understand the relationship between contracts, tables, and streams. It also provides progressive architectural development, clearly defining the tradeoff rationale while making the structure more or less complex.

Current Implementation of TSN

• 1:1 contract and stream
• Streams are deployed and composed freely
• Each wallet controls its contract
• The contract must adhere to an interface
• Taxonomy is hard coded in the contract
• Primitive events are stored in primitive contract

Drawbacks

• No governance layer
• No official streams

The One Contract Proposal

• Single Contract where every procedure is handled
• Owned by TSN

Improvements From the Previous Approach

• There are official streams
• DAO governance layer is enabled
• Fine-tuned authorization layer is enabled

Drawbacks

• Hard to test 3rd party streams
• Can’t incorporate ongoing streams into the system

The One Contract Proposal (with system streams)

• System Stream table added to flag streams as official