Submission Materials
Whitepaper
- Template: IEEE Conference & KBI Annex Format
- Format Guide: Headings Guide Overall Format Details (4.2mm columns)
- Samples: Sample Whitepaper PDF Sample Annex 1
- Limits: Max 6 pages; unlimited appendices.
- Size: A4 Portrait, Compressed PDF.
DEV ONLY
Prototype
- Nature: Proof of Concept or Product demonstration.
- Objective: Showcasing practical BCTT engineering.
- Evaluation: Complements the technical Whitepaper.
- Submission: Via digital link or recorded demo.
Pitch Deck
- Dimensions: 16:9 Landscape orientation.
- Style: Visual-first; lower text density per page.
- Length: Unlimited pages.
- Focus: Introducing the core concept and business logic.
Posterboard
- Template: KBI Conference Poster Format
- Sample: Sample Posterboard & Tips
- Dimensions: A0 Landscape.
- Content: 1 page; Concise visual overview.
- Format: Compressed PDF.
Submission Roadmap
| Phase | Requirements |
|---|---|
| Phase 0 Pre-IBCOL |
N/A |
| Phase 1 IBCOL Qualifiers |
• Whitepaper • Prototype (DEV Track ONLY) |
| Phase 2 ETO |
• Pitch Deck • Posterboard |
| Phase 3 IBCOL Finals |
• Revised Whitepaper • Prototype (DEV Track ONLY) |
Evaluation Criteria
Solution Architecture (ARC)
Design Thinking Competency40%
"How well are you solving the problem?"
- The project addresses a well-defined problem area with succinct value propositions uniquely leveraging BCTT principles.
- The project is comprehensive and complete, addressing key stakeholder requirements and challenges.
First Principles Competency30%
"Do you understand what you are doing?"
- The project team shows understanding of BCTT concepts from first principles.
- The project correctly applies BCTT principles, anticipating and managing risks.
Presentability (Explainability)20%
"Do others understand what you are doing?"
- The project's components, flow, and rationale are clearly articulated via diagrams, narratives, or visual aids.
- The project's technicality is explained in accessible language for non-experts.
Quality (Originality)10%
"How are you contributing to the frontier?"
- The project proposes a new way to solve well-established problems or addresses relatively new problems.
- The project cites prior art and improves on the state-of-the-art proportionate to problem complexity.
Solution Development (DEV)
Solution Design Competency40%
"How well are you achieving your development goal?"
- The project demonstrates quality in engineering design, such as modularity and effective use of external resources.
- The project accounts for non-tech and off-chain support systems, such as governance and trust frameworks.
First Principles Competency30%
"Do you understand what you are doing?"
- The project shows a structured approach to applying elemental BCTT principles in technical specifications.
- The project anticipates challenges of adapting BCTT elements with adaptation or mitigation strategies.
Presentability (Communication)20%
"Do others understand what you are doing?"
- The project specifications clearly communicate functionality, structure, and intended outcomes.
- The project documentation is clearly organized for comprehension by non-experts or engineers.
Quality (Completeness)10%
"How robust is your result?"
- The project excels in fulfilment of specifications, quality of functionalities, and consideration of performance and scalability.
- The project includes strategies for stress testing and edge cases, including cybersecurity and security IRL.
KBI reserves the right to amend or disqualify a team or project if these parameters are not met or if amendments are not accepted.