About this page
97 questions collected from IFT All-Hands (Lisbon, March 2026). Re-categorized from scratch — original spreadsheet metadata was incomplete and inconsistently labeled. Each question has an assigned owner, response format, and status. Update the Status column as answers are delivered.
Status legend:
open·stage(answered on stage) ·wip(in progress) ·done(published/delivered)Priority legend:
H(high) ·M(medium) ·L(low)
Summary
Process
Week 1 — Triage & route
- Corey + Council sign off on category routing and nominated owners for each of the 9 buckets
- Mark questions answered on stage by changing
open→stagein the Status column- Each nominated owner acknowledges their category and agrees on a response format
- Council decides which High-priority questions need a response within 2 weeks vs. 4 weeks
Weeks 2–4 — Answer production
- Engineering & architecture — Logos Engineering FAQ doc (internal first, then public tech explainer for devs)
- Narrative & positioning — Comms drafts, Council reviews; publish key answers to Logos Press Engine as a standalone piece
- Status app — Status team dedicated recorded Q&A session (60 min); communities delivery question needs a direct, unfiltered answer
- Keycard — Council formal written statement on budget/staffing; Keycard team handles tech questions separately
- Token & economics — Council/Foundation statement; route through legal before any public phrasing
- Ecosystem dev & circles — EcoDev async written responses; publish to Circles newsletter and internal wiki
- Coordination & process — PM/Ops converts questions into tracked action items with owners; the answer is the action item
- Internal comms & tools — IT/Ops quick wins list; resolve source-of-truth and info-stack questions first as they unblock everything else
- Org & people — Council statement or policy memo; expertise/authority question warrants a principle-level response
Weeks 4–5 — Distribution
- Single “All-Hands Follow-Up” document compiled from all answers, sent to all CCs
- Public-facing subset published to Logos Press Engine (narrative, positioning, “why Logos” answers are good candidates)
- All answers archived internally with links back to source sessions or docs
- Status team Q&A and any other recorded sessions uploaded (YouTube unlisted or internal archive)
Week 6+ — Feedback & close
- Short async survey to question submitters: “Was your question answered satisfactorily?”
- Any unresolved questions rolled into the next quarterly town hall prep or All-Hands
- Process audit: did every question get a route and a response format? Anything that fell through flagged to Council
Engineering & architecture
Owner: Logos Engineering leads · 24 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| When mainnet? | H | Council / Logos Engineering | Council statement | open | |
| What exactly is Logos Chat? Is it different from Status Messenger? | H | Logos Engineering / Comms | Written FAQ | open | |
| Supporting iOS/Android in the Logos stack — when? | H | Logos Engineering | Written FAQ | open | |
| What does “identity” mean in the Logos Stack? | H | Logos Engineering | Spec doc | open | |
| What happened to operators? | H | Logos Engineering | Written FAQ | open | |
| Tech stack makes it hard to be productive | H | Logos Engineering leads | Action plan | open | |
| Uncertainty about available languages for Logos Core | H | Logos Engineering | Written FAQ | open | |
| What are the objectives of the testnet? What does success on testnet look like? | H | Logos Engineering | Written doc | open | |
| Will devs need to write/know C to deploy Logos Apps? | H | Logos Engineering | Written FAQ | open | |
| If a circle runs a node, are we actually validating transactions and earning PPoS fees, or just a light node? | H | Logos Blockchain | Written FAQ | open | |
| How do we ensure the comm system isn’t taken over or controlled by state actors? | H | Logos Messaging / Vac | Written FAQ | open | |
| Mobile resource utilization: bandwidth, battery, disk, risc0, RAM, CPU | H | Logos Engineering | Written FAQ | open | |
| Extremely ambitious goal — very complex software system with a huge attack surface | H | Logos Engineering / Vac | Written FAQ | open | |
| Middle steps to ensure all module combinations preserve decentralization, privacy, and security | H | Logos Engineering / Vac | Spec doc | open | |
| Are there plans for more execution zones after LEZ? If yes, which? | M | Logos Engineering | Written FAQ | open | |
| Steganographic transports: mimicking others’ traffic patterns to avoid censorship | M | Logos Messaging / Vac | Spec doc | open | |
| Integrating Logos Chat SDK | M | Logos Engineering | Written FAQ | open | |
| Are there preferred categories of dApps to encourage people to build on Logos? | M | EcoDev + Logos Engineering | Written FAQ | open | |
| User-friendly distributed DB for app developers | M | Logos Storage | Written FAQ | open | |
| Why 30-second block time? Can it be reduced? | M | Logos Blockchain | Written FAQ | open | |
| Will Nimbus or Status be accessible through the Logos Core app? | M | Logos Engineering / Nimbus | Written FAQ | open | |
| How will Nimbus integrate into the Logos Stack and why? | M | Nimbus / Logos Engineering | Written FAQ | open | |
| Logos website should have a copy-pastable example for common Logos operations (e.g. start a storage node) | M | Logos Engineering / Comms | Quick action | open | |
| Bot trained on specs that reviews PRs for architectural cohesion | L | Vac / Logos Engineering | Action item | open |
Ecosystem dev & circles
Owner: EcoDev team · 15 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| RFPs: what should builders focus on? Is there a list? How does the decision process work for Logos launch priorities? | H | EcoDev | Written FAQ | open | |
| How will you bridge the gap between circles and the tech stack given the late mainnet launch? | H | EcoDev + Council | Written plan | open | |
| What are the main success metrics 1 year from now? | H | Council + EcoDev | Council statement | open | |
| Planning is very endogenous — want more EcoDev and externally-informed priorities | H | Council + EcoDev | Written plan | open | |
| How many node operators do we need at mainnet launch? | H | EcoDev + Logos Engineering | Written FAQ | open | |
| Circles: how much does it contribute back to Logos tech? Is it just use case discovery? | H | EcoDev + Council | Written FAQ | open | |
| Lambda Prize: how to ensure people stay involved? | M | EcoDev | Written plan | open | |
| We need more CC involvement in social media posts, streams, and chatrooms | M | Comms + EcoDev | Quick action | open | |
| Can we collect circles stories somewhere to read and share? Blog, book — beyond Discord and X? | M | Comms + EcoDev | Quick action | open | |
| Shouldn’t we try to engage more tech people in circles, like universities? | M | EcoDev | Written plan | open | |
| EcoDev engineering needs to plug into circles more (mentoring, product, UX design, business) | M | EcoDev | Written plan | open | |
| OS contributions: how do we get everyone connecting dots and turning inquiries into actual contributions? | M | EcoDev + Council | Written plan | open | |
| RFPs for non-tech work? e.g. funding local high-impact communities | M | EcoDev | Written plan | open | |
| Public YouTube/X streams attract small audiences (10-30). How to grow engagement? | M | Comms | Written plan | open | |
| Better marketing and design for Logos Circles initiatives and projects | M | Comms + EcoDev | Action plan | open |
Narrative & positioning
Owner: Comms + Council · 13 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| 1-liner pitch / narrative? | H | Comms + Council | Quick action | open | Blocking external comms work |
| Why should people use Logos to build instead of existing tech, in 1-2 sentences? | H | Comms + Council | Quick action | open | |
| Is there a use case where Logos is clearly better than Aztec or other privacy solutions? | H | Comms + Council | Written FAQ | open | |
| How to address the general tech/crypto backlash | H | Comms | Written plan | open | |
| Can/should we lean into “sovereign tech” / US decoupling, e.g. in the EU? | H | Council + Comms | Council statement | open | |
| Re: winnable issues — why reinvent the whole stack? Why are Signal + USDT insufficient? | H | Comms + Council | Written FAQ | open | |
| From a comms perspective, are devs the main target? | H | Comms | Comms strategy doc | open | |
| How to avoid being perceived externally as “crypto bros” exploiting people for token pumps? | H | Comms | Comms strategy doc | open | |
| Are we solving common people’s problems, changing web3, or both? | H | Council + Comms | Council statement | open | |
| Our positioning: compliant privacy / cypherpunk spectrum — USDT/USDC/CEX or guerrilla liquidity rails? | H | Council + Comms | Council statement | open | |
| Privacy vs agency, tech vs activists | M | Council + Comms | Written piece | open | |
| Societal issues are political — can we solve them via tech and not just democracy? | M | Council + Comms | Written piece | open | |
| Optics of internal/external communication | M | Comms | Written plan | open |
Internal comms & tools
Owner: Ops / IT · 12 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| Information Stack: where to find what you need? Spread all over — hard for new joiners and CCs | H | Ops / IT | Quick action | open | Prerequisite for distributing answers |
| Where is the source of truth for all info? | H | Ops / IT | Quick action | open | Prerequisite for distributing answers |
| Logos formed many teams — not clear who to contact | H | Ops | Quick action | open | |
| How to improve transparency about new things happening — with CCs and communities? | H | Comms / Ops | Written plan | open | |
| Deanonymization in internal chatting software | H | Security / Ops | Policy doc | open | |
| Make instructions for using the messaging app for non-tech people | M | Ops / IT | Quick action | open | |
| Making sure that all onboarding steps and technology is still relevant | M | Ops | Quick action | open | |
| Broadcast more (internal) demos at townhall | M | Ops | Quick action | open | |
| Org-wide visibility: offsites generate great info sharing. How to share more throughout the year? | M | Ops | Written plan | open | |
| Vetting apps / 3rd party services that can be retired | M | Ops / IT | Quick action | open | |
| Ditch Discord | M | Council | Council decision | open | |
| Merge Discord channels / streamline comms channels | M | Comms / Ops | Quick action | open |
Cross-team coordination
Owner: PM / Council · 12 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| How do we align roadmap/prioritization where Status, Logos, and Status Network overlap? | H | Council / PM | Council statement | open | |
| Will there be more PM effort across Logos teams? Goals keep changing, teams not collaborating efficiently | H | Council / PM | Written plan | open | |
| Specifications: how do we communicate them? People aren’t aware — what should we do? | H | Vac / Eng leads | Written plan | open | |
| Logos Stack map should show responsible teams and be easily reachable | H | Comms / PM | Quick action | open | |
| Better coordination across desired projects | H | PM / Council | Written plan | open | |
| Clearer info pipeline from tech teams to Comms to better highlight the work being built | H | Comms + Eng leads | Written plan | open | |
| Double down on coherence | H | Council | Council statement | open | |
| More consideration when scaling/descaling teams — core team stability matters | H | Council | Council statement | open | |
| Process to determine if a PR requires notifying other teams | M | Eng leads / PM | Policy doc | open | |
| Process to discover and propose standard code practices | M | Eng leads | Policy doc | open | |
| Improve collaboration with Logos Storage | M | Logos Storage + dependent teams | Written plan | open | |
| Demo from each engineering team weekly — for EcoDev planning and broadcasts | M | Eng leads + EcoDev | Quick action | open |
Keycard
Owner: Council + Keycard team · 7 questions
Signal to pay attention to
6 of 7 questions in this category are essentially the same demand: give Keycard a marketing budget and dedicated staff. This is pressure, not questions. A single Council statement with concrete commitments will satisfy this entire bucket. Resolve it together rather than answering each individually.
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| Keycard positioning within IFT — will Keycard possibly become Logos Card? | H | Council + Keycard | Council statement | open | |
| Keycard: why is there no dedicated marketing staff? | H | Council | Council statement | open | |
| Give Keycard a real marketing budget | H | Council | Council decision | open | |
| Keycard should be given more attention | H | Council | Council decision | open | |
| Give more marketing resources to Keycard | H | Council | Council decision | open | |
| Keycard is amazing — can we help them additionally? | M | Council + Keycard | Council decision | open | |
| Will Keycard be integrated with Logos Basecamp API for key management? | M | Keycard team | Written FAQ | open |
Status app
Owner: Status team + Council · 6 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| Status: why is communities delivery still so bad? | H | Status team | Team Q&A session | open | Needs direct, unfiltered answer |
| Status: why not smaller, more frequent releases? | H | Status team | Team Q&A session | open | |
| Do you see Status as separate from Logos? Status Network not an execution zone since no more DA? | H | Council | Council statement | open | |
| Is the future of Status App to be in the Logos App? Can communities build their own and compete? | H | Council | Council statement | open | |
| Supporting Logos chain in Status — any expectations from IFT? | M | Status team + Council | Written FAQ | open | |
| Can Status App support Logos Circles? (messaging, communities, etc.) | M | Status team | Written FAQ | open |
Org & people
Owner: Council / People ops · 5 questions
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| Make sure people with expertise have sufficient authority/support — grow experts, don’t just use them | H | Council / People ops | Policy doc | open | |
| When will Logos absorb all remaining parts of IFT? | H | Council | Council statement | open | |
| Hire an engineer with 20+ years experience to act as architect and set up development guidelines | M | Council / Hiring | Council decision | open | |
| Engineers/researchers need sufficient time in the problem domain to build intuition | M | Eng leads | Policy doc | open | |
| Ways to reduce time to market should be baked into planning, implementation, and delivery | M | PM / Eng leads | Policy doc | open |
Token & economics
Owner: Council / Foundation · 3 questions
Legal review required
These questions need to be pre-cleared with legal before any public statement. Frame answers around roadmap and technical architecture, not investment timelines or tokenomics that could create securities exposure.
| Question | Pri | Owner | Format | Status | Notes |
|---|---|---|---|---|---|
| Token timeline, funding choices — VC? ICO? Presale? | H | Council / Foundation | Council statement | open | Route through legal |
| When Logos token? | H | Council / Foundation | Council statement | open | Route through legal |
| Liquidity: do we need our own if we have bridges and atomic swaps on day 1? Tap into SOL/ETH? | H | Council / Foundation | Council statement | open | Route through legal |