Home of the Logos Ecosystem Development / Integration effort.

Mandate

(wip): enable bi-directional feedback between the Logos technical stack and the Logos community/ecosystem. By:

• Identifying and evaluating the technological needs of the community and ecosystem
• Translating those needs into requirements for the technology stack and value of said requirements
• Propagating information about latest delivery, to encourage the community to use, build, remix and contribute back to the Logos Technology stack

Metholodogy

• Understand and synthetise Logos roadmap and testnet phases
• Review dependencies, in terms of technical decisions and delivery. Flag specific integrations that are blocked on progress until decision is made/clarified:
  • Infrastructure essentials (block explorer, rpc, etc): Is there a dependency on RPC format (ETH), SR vs base layer, what ecosystem can be re-used (eth vs stellar ), etc.
  • Application essentials/developer toolkit (SC toolchain, dev env, token creation, onchain primitives, UI, etc): internal requirements on blockchain and Logos Core
  • Desired projects (stablecoin, lending, entity formation, etc): getting developers to build those projects (demand validation, XPrize), and identify/onboard external projects.

Prioritization (wip)

stateDiagram-v2
	state Concerns {
		[*] --> Movement
		[*] --> Technical_Risks
		[*] --> Sustainability
		Movement --> Priorities
		Technical_Risks --> Priorities
		Sustainability --> Priorities
	}
	Priorities --> Requirements: defines
	Contributors --> Technical_Risks: define
	Requirements --> Contributors: plan
	Contributors --> Logos_Core+: delivers
	Logos_Core+ --> Concerns: solves

Feedback Cycle (wip)

stateDiagram-v2
	Community --> Winnable_Issues: Identifies
	Community --> Contributors(devs): Attracts
	Winnable_Issues --> Technical_Solutions
	Technical_Solutions --> Infrastructure_Essentials: Need
	Technical_Solutions --> Application_Essentials: Need
	Technical_Solutions --> Desired_Projects: Need
	Infrastructure_Essentials --> Requirements: Extract
	Application_Essentials --> Requirements: Extract
	Desired_Projects --> Contributors(devs)
	Desired_Projects --> XPrize
	Community --> Applications: Dogfood
	Contributors(devs) --> Applications: Build
	XPrize --> Applications: Funds
	Applications --> Winnable_Issues: help solve
	Internal_PoCs --> Requirements: Needs
	Requirements --> Logos_Stack: drives
	Logos_Stack --> Contributors(devs): used by
	Logos_Stack --> Internal_PoCs: enables
	Internal_PoCs --> Contributors(devs): Inspire
	Desired_Projects --> Internal_PoCs: Built as
	Internal_PoCs --> Community: Dogfed by

Concerns / Priorities

What drives the prioritisation of the requirements forwarded to the Logos contributors?

(1) Sustainability

Enable and drive onchain activity and value accrual to sustain the development of the technology stack for the Movement. Ensure that the L1 comes with battery included aka essentials apps are available at mainnet launch.

(2) Movement

The end goal, why we are all here. Provide the technological solutions needed by the movement, contributors and participants, circles and people to organise, identified and solve winnable issues. Make the Internet a catalyst for prosperity and emancipation. No one is free until we are all free. See Logos Manifesto for the vision, and Farewell to Westphalia to open the conversation on how we get there.

(3) Technology De-Risking

Enable early delivery and validation of technology with most unknowns and risks. Engineering teams flags the risks to get the prioritised accordingly.